Data Management Library Pathmaker Messages Manual Abstract Part Number Edition Published Product Version Release ID Supported Releases This manual lists all the messages produced by Pathmaker. 067870 Third September 1993 Pathmaker D20 D20.00 This manual supports D20.00 and all subsequent releases until otherwise indicated in a new edition.
Document History Edition Part Number Product Version Earliest Supported Release Published First Second Third 15551 27452 067870 Pathmaker C20 Pathmaker C30 Pathmaker D20 C20 C20 D20.00 March 1989 June 1990 September 1993 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .
Contents About This Manual Section 1 v Pathmaker Messages Format Pathmaker Messages 1-1 PMADL Messages 1-2 GeneratedApplication Messages Utility Program Messages Section 2 1-2 1-4 Pathmaker Messages 067870 Tandem Computers Incorporated iii
Contents iv 067869 Tandem Computers Incorporated
About This Manual Pathmaker is a menu-driven Pathway application generator that lets you build a working prototype of a user interface. This manual lists all the messages produced by the Pathmaker product. This manual is for experienced programmers: you should be familiar with the Tandem NonStop Kernel and operating system. Related Documentation This manual is part of the Pathmaker library of manuals.
1 Pathmaker Messages Format This manual lists in alphabetic order the Pathmaker messages that you can receive while running the Pathmaker product. For each message, you will find: Cause. Why this message was produced. Effect. What action Pathmaker took. Recovery. Strategy suggested to correct the error or warning. This book includes messages from several sources: Pathmaker A subset of the messages given by the Pathmaker product. Confirmation messages, such as Requester added, are not included.
Pathmaker Messages Format PMADL Messages When these messages occur, the Screen Painter session is aborted and the catalog might or might not have been updated. To make these messages easier to find in this alphabetic listing, the word PAINTER has been removed from the beginning of the message.
Pathmaker Messages Format PMADL Messages CALL Messages Messages for CALL errors conform to one of the following two formats: CALL-status - message-text CALL-substatus In called-program CALL-status - message-text called-program CALL-status is an integer from 1 through 31, from 40 through 44, or from 113 to 114. The CALL-status number does not appear in this manual. CALL errors are alphabetized by message-text.
Pathmaker Messages Format Utility Program Messages Utility Program The Pathmaker product has three utility programs that issue error messages: Messages HELPUTIL PMPROJECT PMINSTAL Error messages for these utilities interrupt normal processing. That is, the program either terminates immediately or terminates after reading its input but before performing any operation; the program cancels the current operation and continues with the next operation.
2 Pathmaker Messages The Pathmaker messages are listed in the following pages in alphabetic order. A requester cannot call an initial requester: called-req-name Cause. You attempted to add a CALL to an initial requester from another Pathmaker requester. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. An initial requester is a top-level requester; it cannot be called by any other requester in the application.
Pathmaker Messages Access path name has been changed Cause. You chose an operation that does not allow the access path screen field to be changed. Effect. Operation fails. Recovery. Perform a list operation to redisplay the screen data and then repeat the desired operation. Access path name is required Cause. You tried an operation that requires an access path name, but you didn’t specify an access path. Effect. Operation fails. Recovery. Enter an access path name and repeat the operation.
Pathmaker Messages Action Object allowed only for CALL, SEND, and RETN actions Cause. You specified a requester name or service name for an action that does not allow an object. This condition is normally detected when you attempt to update the Function Key Assignments screen. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Note this error message and contact your Tandem representative.
Pathmaker Messages Actions for PA1 and PA2 can only be RETN, RCVR, and DFLT Cause. You specified an invalid action for function key PA1 or for function key PA2 on a 3270 terminal. Legal actions for these two function keys are ones that do not require data to be accepted from the screen: RETN, RCVR, and DFLT. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Change the action to RETN, RCVR, or DFLT and regenerate. Active-Term file not on release subvolume Cause.
Pathmaker Messages All pages, except one, must be deleted before deleting the paging area Cause. You selected the Delete Paging Area function, but the paging area contains more than one page of screen elements. Issued by the Pathmaker product. Effect. Operation canceled. Recovery. Move all screen elements from all pages onto one page, then delete the empty pages, or delete the screen elements from all but one page. All projects in this installation must be reconfigured Cause.
Pathmaker Messages Already at end of help for this screen Cause. You attempted to display the next page of help text and you were already at the last page of help available for this screen. Issued by the Pathmaker product and by the generated application. Effect. None. Recovery. If you are running Pathmaker, press the help key to display the paging actions available for online help. Already at the beginning of definition list Cause.
Pathmaker Messages Ambiguous reference: qualified-name Cause. You referred to a field name in the requester definition that cannot be uniquely resolved. Issued by the Pathmaker product and by PMADL. Effect. Requester generation, default screen creation, or simulation fails. Recovery. Add more qualifications to the name. Refer to the Pathmaker Reference Manual for an explanation of how to enter fully qualified names. An action path already exists with that name. Cause.
Pathmaker Messages An unrecoverable error has occurred. Cause. The Pathmaker program encountered a fatal error during server generation. Issued by the Pathmaker product and by PMADL. Effect. Server generation fails. Recovery. See the project home terminal for additional error information. Note this error message and any additional error information, including messages from the project's Pathway log file (default name: T9154LOG). Then contact your Tandem representative. An unrecoverable error occurred.
Pathmaker Messages Assigned file name is incorrect: logical-file-name Cause. A physical file name in the Pathmaker Pathway configuration is incorrect. For example, DDF-FILE might be assigned to a physical file other than \system.$vol.subvol.DICTDDF. Issued by the Pathmaker product. Effect. Operation canceled. Recovery. Correct the ASSIGN in the project Pathway configuration. Use the PMPROJECT utility to shut down the project, reconfigure the project, and cold start the project.
Pathmaker Messages At least one RETN action must be specified Cause. You did not assign the RETN (return) action to any function key for this requester. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Every requester must have at least one RETN action. Enter RETN for at least one function key. At least one space must precede each screen element Cause.
Pathmaker Messages Attribute is not consistent with the object TERMINAL-TYPE attribute Cause. You specified a requester object attribute that is not allowed, given the terminal type of the requester, or you specified a value for a requester attribute that is not compatible with the requester's terminal type. Issued by PMADL. Effect. The object description is not stored in the catalog. Recovery. Remove or correct the incompatible attribute, or specify a different terminal type for the requester.
Pathmaker Messages Attribute was previously specified in this object Cause. You specified an attribute more than once in an object description, but the attribute can be specified only once. Effect. The object description is not stored in the catalog. Recovery. Remove the duplicate attribute. AUDIT/TMF param mismatch Cause.
Pathmaker Messages Bad data in field in message to server: field-name Cause. Pathmaker encountered invalid data in the IPC message to a service. This is an internal error. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Note this error message and contact your Tandem representative. Bad hierarchy — more than one instance with no parent Cause.
Pathmaker Messages Bad program unit name; Call to called-program Cause. The called-program name is invalid or does not exist. CALL error issued by the generated application. Effect. CALL fails. Recovery. Check the user interface for the CALL name and existence of the called program. Regenerate. Bad pseudocode; P-Reg = TCP-P-reg In called-program Cause. CALL error issued by the generated application. Effect. Called program fails. Recovery.
Pathmaker Messages Bad request message Cause. The standard server received an invalid message. Issued by the generated application. Effect. Operation fails. Recovery. Check to see if the user code (in a user hook) is corrupting the message, and then correct the code and regenerate the requester. If the problem is caused by generated code, contact Tandem support. Bad request message, field BeforeImage tbl-name.fld-name Cause.
Pathmaker Messages Bad request message, reply would exceed maximum reply length Cause. The message sent back from the standard server to the requester is longer than the buffer provided for it. Issued by the generated application. Effect. Operation fails. Recovery. Check to see if the user code is corrupting the message, correct the code, and regenerate the requester. If the problem is caused by generated code, contact Tandem support. Bad TCLPROG entry; Call to called-program Cause.
Pathmaker Messages Base requester screen must include an @ADVISORY pseudofield Cause. A requester object description specifies a paging area or screen elements, but it does not specify an @ADVISORY pseudofield. The @ADVISORY pseudofield is required if the requester has a screen. Issued by PMADL. Effect. The requester description is not stored in the catalog. Recovery. Add a PSEUDOFIELD attribute for @ADVISORY to the requester object description.
Pathmaker Messages Blank server class marked active Cause. You attempted to update the server class mapping screen but a blank server class was marked as active for one of the services. Issued by the Pathmaker product. Effect. Update fails. Recovery. If the service has been assigned to a server but the server has not been assigned to a server class, you must return to the Server Class Assignment screen to assign the server to a server class.
Pathmaker Messages Boxes nested too deeply to display any item Cause. The child record boxes are so numerous that data cannot be displayed in the paging area. Issued by the Pathmaker product and by PMADL. Effect. Default screen generation fails. Recovery. Remove at least one level of box nesting. Call loop detected; initial action suppressed Cause. The Initial Actions in two requesters form a loop.
Pathmaker Messages CALL parameters listed — context and parameters changed Cause. You changed the requester context and the formal parameter list (on the Requester Parameters screen of the called requester) after you created the CALL parameter list. Issued by the Pathmaker product. Effect. Pathmaker updated the CALL parameter list, rematching parameters as needed. Recovery. This is an advisory message. No recovery is needed. CALL parameters listed — parameters changed in called requester Cause.
Pathmaker Messages CALL parameters listed — parameters have been rematched Cause. You deleted a reference object that was passed as a parameter to another requester; you then returned to the CALL Parameter Definition screen to update the CALL parameter list. Issued by the Pathmaker product. Effect. The Pathmaker program updated the CALL parameter list, deleting the parameter that was removed from the requester context. Recovery. This is an advisory message.
Pathmaker Messages Called requester has incompatible terminal type:called-reqname Cause. You attempted to add a CALL to a requester that has a different terminal type from the current requester. Issued by the Pathmaker product and by PMADL. Effect. Update or requester generation fails. Recovery. All the requesters in your application must have the same terminal type. Change the terminal type of the called requester or change the terminal type of the calling requester.
Pathmaker Messages Cannot change requester type Cause. You attempted to update the requester with a new requester type. Issued by the Pathmaker product. Effect. Update fails. Recovery. You cannot change the requester type once a requester is defined or change the requester type when copying a requester. You must recreate the requester as the new type, rebuilding the requester context and the application screen with the DDL definitions or records you used for the original requester.
Pathmaker Messages Cannot communicate with system monitor — new-process Cause. The system monitor will not start the new process, perhaps because of system loading. Issued by the Pathmaker product. Effect. New process startup fails. Recovery. Try again or contact your system manager. Refer to the Guardian Procedure Errors and Messages Manual for information about new process errors. Cannot convert projects from this release — release Cause.
Pathmaker Messages Cannot generate FUP output for DDL Record — record name Cause. PMPROJECT INSTALL received an error from DDL while attempting to generate FUP CREATE commands for the indicated DDL Record in the GENDATA file. This error may indicate that the Record does not specify a physical file name. Issued by PMPROJECT. Effect. No FUP CREATE commands are generated for the Record. Recovery. If desired, manually add commands to create a file for the Record to the GENDATA file.
Pathmaker Messages Cannot specify listing device with compilation suppressed. Cause. On the requester generation data screen, a listing device was specified and compile was set to N. Issued by the Pathmaker product. Effect. Requester generation fails. Recovery. Remove the listing device specification or change compile to Y. Cannot Update, Delete, Insert on shorthand view: view-name Cause. You attempted an Update, Delete, or Insert on a shorthand view. Issued by the Pathmaker product. Effect.
Pathmaker Messages Can't talk with sys mon, error err-num: new-process-name Cause. The CPU on which you tried to start a process is not running. Issued by the Pathmaker product. Effect. New Process startup fails. Recovery. Contact your system manager. Catalog error error-name on SQL-catalog-table-name Cause. An error has occurred in accessing an SQL catalog. Issued by the generated application. Effect. Operation fails. Recovery.
Pathmaker Messages Catalog file locked: file-name Cause. You attempted to copy either a requester, a service, or a server. The project catalog file that contains information about this requester, service, or server is locked. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Try the operation again in a few moments. If the file remains locked, try using the FUP LISTLOCKS command to see which process has the file locked. Catalog file not found: file-name Cause.
Pathmaker Messages Catalog is corrupt, bad file is: file-name. Cause. The Pathmaker program encountered an invalid value in a field in one of the project catalog files, or a link between file-name and another project catalog file is broken. Issued by the Pathmaker product and by PMADL. Effect. Requester generation, default screen creation, screen painter, or simulation fails. Recovery. Note the file name and contact your Tandem representative. Catalog volume and target volume are the same–volume Cause.
Pathmaker Messages Catalog was opened without a project name Cause. You attempted to perform an operation that requires a project name, such as generating a Pathmaker requester, service, or server, but the current catalog was opened using the ?CATALOG command, which does not indicate a project name. Issued by PMADL. Effect. The operation is ignored. Recovery. Open the catalog using the ?PROJECT command. Catalog was updated by someone else since your last update Cause.
Pathmaker Messages Column name is repeated in this list Cause. A column name cannot appear more than once in an access path. Effect. Operation fails. Recovery. Remove one of the references to the column name and repeat the operation. Column named FILLER not allowed in SQL table: table-name Cause. A user-defined column named FILLER appears in SQL table table-name. Issued by the Pathmaker product and by PMADL. Effect. Requester generation or server generation fails. Recovery.
Pathmaker Messages Configuration file exists in the software distribution subvolume Cause. The installation configuration file used by PMINSTAL resides in the target installation subvolume, and a file with the same name resides in the software source subvolume. If PMINSTAL proceeds, it will overwrite the configuration file with the file in the source subvolume. Issued by PMINSTAL. Effect. The PMINSTAL operation was canceled. Recovery. Rename the installation configuration file.
Pathmaker Messages Corrupt catalog field value detected in object — object-name Cause. During an OUTPUT statement, PMADL detected an illegal value in a catalog field of an object's catalog description, and the field corresponds to one of the object's ADL attributes. The object-name indicates the corrupt object. Issued by PMADL. Effect.
Pathmaker Messages Corrupt catalog link/too many records in object — object-name Cause. During an OUTPUT statement, PMADL detected an illegal value in a field that links records in different catalog files together in an object description. Either a record was found even though the object does not allow any records, or multiple records were found and the object allows at most one record.
Pathmaker Messages Could not obtain extended memory (ALLOCATESEGMENT error error-num) Cause. NonStop SQL could not obtain the extended memory needed to perform an SQL operation. Issued by the generated application. Effect. The operation fails. Recovery. Contact your system manager. Could not obtain extended memory (DEFINEPOOL error error-num) Cause. NonStop SQL could not obtain the extended memory needed to perform an SQL operation. Issued by the generated application. Effect. The operation fails.
Pathmaker Messages CPUs configured for process are down — new-process Cause. All CPUs configured for this process are down. Issued by the Pathmaker product. Effect. New process startup fails. Recovery. Use the Process Configuration screen to modify the configuration. Data area too small due to function key prompts Cause. Your current function key prompt display exceeds 10 lines. Issued by the Pathmaker product and by PMADL. Effect. Requester generation or default screen generation fails. Recovery.
Pathmaker Messages Data field crosses the edge of the paging area Cause. You moved a data field or defined a data field so that it overlaps the left or right edge of the paging area. Issued by the Pathmaker product and by PMADL. Effect. Operation canceled. Recovery. Choose a different location for the screen element. Data field in page page-num overflows the modified paging area Cause. You redefined the paging area so that a data field on page-num no longer fits in the paging area.
Pathmaker Messages Data field segment crosses the edge of the paging area Cause. You moved a segmented data field so that one of the segments overlaps the left or right edge of the paging area, or so that some of the segments lie outside the paging area and other segments lie inside the paging area. Issued by the Pathmaker product and by PMADL. Effect. Operation canceled. Recovery. Choose a different location for the data field. Data field segment overlaps a screen-element at location Cause.
Pathmaker Messages Data field starts at an invalid screen location — location Cause. You attempted to define a data field on, or move a data field to, an invalid screen location. Invalid positions are: Any location outside the screen Location (1,1), the uppermost-left screen position Issued by the Pathmaker product and by PMADL. Effect. Operation canceled. Recovery. Choose a different location for the data field. Data field was shortened due to insufficient space Cause.
Pathmaker Messages Data file was in use (012) Cause. The file is opened by some other user which locks out your application (file system error 12). Issued by the generated application. Effect. Open operation fails and the requester is terminated. Recovery. Retry the operation later. If the problem persists, see your system manager. Data file was not found (011) Cause. You attempted an operation on a data file that cannot be found (file system error 11).
Pathmaker Messages DB function enabled, but no associated function key: function Cause. You enabled a database service, such as DELETE, but do not have a function key specified to invoke the service. This condition is normally detected when you update the Record Instance Detail screen, the Requester Definition screen, or the Function Key Assignments screen. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery.
Pathmaker Messages DDL DEF,DDL RECORD or SQL TABLE does not exist:non-object-name Cause. You attempted to update either the Requester context, the IPC definition, the Logical File Entries, or the Display Field List screen. The DDL definition or record does not exist in the dictionary. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Correct the object name. DDL DEF/RECORD not found in dictionary: missing-name Cause.
Pathmaker Messages DDL record name or table object name required — please enter name Cause. You attempted to update the Logical File Entries screen without supplying a DDL record name or an SQL table object name in the DDL Record/Table Object Name column. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. You must supply a DDL record name or an SQL table object name for every item in the Logical File Name column. DDL RECORD/SQL TABLE not found: invalid-name Cause.
Pathmaker Messages Decoration crosses the edge of the paging area Cause. You moved a screen element or defined a screen element so that it overlaps the left or right edge of the paging area. Issued by the Pathmaker product and by PMADL. Effect. Operation canceled. Recovery. Choose a different location for the screen element. Decoration in page-num overflows the modified paging area Cause. You redefined the paging area so that a decoration on page-num no longer fits in the paging area.
Pathmaker Messages Decoration overlaps a screen-element at location Cause. You attempted to define a decoration on, or move a decoration to, a previously defined screen element. Issued by the Pathmaker product. Effect. Operation canceled. Recovery. Delete the screen element or choose a different location for the decoration. Decoration starts at an invalid screen location — location Cause. You attempted to move or define a decoration so that it begins at the uppermost-left screen location.
Pathmaker Messages DEFINE not accepted on remote system: new-process-name Cause. The new process tried to start on a remote NonStop 1+ or a system running a release earlier than B20. Issued by the Pathmaker product. Effect. New Process startup fails. Recovery. Change the New Process Configuration for new-process-name to start on a correct system. Delete All function key has no meaning on the empty display field list Cause. You pressed SF10 (Delete All) on the Display Field List screen.
Pathmaker Messages Delete fails. Record is gone Cause. The selected record was deleted from the data file by another user before your delete operation was executed. Issued by the generated application. Effect. The record was previously deleted. Recovery. No recovery is needed. Delete fails. Record is locked Cause. You attempted to delete a record that is locked. File operation error issued by the generated application. Effect. Operation canceled. Recovery.
Pathmaker Messages Delete service enabled but no delete action defined Cause. You attempted to enable the database service, DELETE, for a DB requester but do not have a function key specified to invoke the service. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Go to the Function Key Assignments screen and add a SEND to T9154DELETE, then return to the Record Instance Detail screen to enable the DELETE service.
Pathmaker Messages Display detail listed; default screen picture has been shortened Cause. The default screen picture shown in the Display Detail screen has been shortened because the field length has been changed in the Screen Painter. Issued by the Pathmaker product. Effect. New default screen picture displayed. Recovery. No recovery needed. This is an advisory message. Display field is already defined Cause.
Pathmaker Messages Display field picture must be a legal screen edit picture Cause. The edit picture specified for a display field is not a legal, Screen Cobol display field picture. Issued by PMADL. Effect. The requester description is not stored in the catalog. Recovery. Correct the display field's edit picture. Display List item is not elementary:display-list-field-name Cause.
Pathmaker Messages Duplicate screen-element defined in page-num at location Cause. You attempted to add a data field that is already defined on the application screen, or you attempted to add a pseudofield that is already defined on the application screen, or you attempted to add a point field that is already defined. Issued by the Pathmaker product and by PMADL. Effect. The Screen Painter did not add or modify the screen element. Recovery.
Pathmaker Messages Duplicate field name: field-name Cause. You attempted to update the Display Field list with duplicate field names on the list. Issued by the Pathmaker product. Effect. Update fails. Recovery. Remove or rename any duplicate field names so that each field has a unique name. Duplicate logical file name: logical-file-name Cause. You attempted to update the Logical File Entries screen with a duplicate name in the Logical File Name column.
Pathmaker Messages Duplicate request name: dup-request-name Cause. You attempted to update the request portion of the IPC definition of this service with a field name that already appears in the request column. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Remove or rename any duplicate reference objects in the request column so that each request object has a unique name. Duplicate requester parameter: parameter-name Cause.
Pathmaker Messages Duplicate SQL IO Section name Cause. SQL IO Section names must be unique within a service. Effect. Operation fails. Recovery. Choose another name and repeat the operation. Duplicate table object name: table-object-name Cause. You attempted to update the SQL Table Registration screen with a duplicate name in the Table Object Name column. Table object names must be unique. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery.
Pathmaker Messages Entry being deleted does not exist in catalog — try update or list Cause. You attempted to delete an item from the Display Field List that does not exist in the project catalog. Issued by the Pathmaker product. Effect. Delete fails. Recovery. Press F4 to list the current contents of the Display Field List. Error assigning project's help file names Cause. The Pathway PARAM contains a subvolume specification. Help server error issued by the generated application. Effect.
Pathmaker Messages Error in accessing information on User ID Cause. Pathmaker encountered an internal error while converting a user name (group-name.user-name) to a user number (group-num, user-num). Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Note this error message and contact your Tandem representative. Error in attempt to alter PARAM — contact support Cause.
Pathmaker Messages Error in creating copy library file — contact support Cause. You attempted to copy either a requester or a service. Pathmaker was unable to create a copy library file for either the requester copy library or the service custom source file. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Check to see if the disk volume is full and if you have write and create authority for the disk volume. If neither of these is the problem, contact your Tandem representative.
Pathmaker Messages Error in sending message to new process server:error-code Cause. The Screen COBOL compilation of this requester did not complete as expected. Issued by the Pathmaker product. Effect. The new process server, which is the Pathmaker server that invoked the Screen COBOL compiler, abended. Recovery. Recovery depends on error-code, the Screen COBOL error that Pathmaker encountered. If the problem persists, contact your Tandem representative. Error opening $Receive Cause.
Pathmaker Messages Error reading from file-name — contact support Cause. Pathmaker encountered an internal error. Issued by the Pathmaker product. Effect. Pathmaker might display unexpected data on the screen. The project catalog could be corrupt. Recovery. Make a note of the file name and contact your Tandem representative. Error status from FILEINFO Cause. Pathmaker was unable to obtain information about a Tandem file. The file system error number is included in the message. Effect. Operation fails.
Pathmaker Messages Exactly error-count variable-message found. Cause. You entered an illegal value entered during data entry. Requester error issued by the generated application. Effect. The cursor is placed in the first field that failed the MUST BE check. The error-count gives the number of errors found on all pages. Any other fields in error are highlighted. Recovery. Reenter data and retry the operation. Exceed table limit — only 40 entries allowed Cause.
Pathmaker Messages Field in OCCURS: Parameter object-name.field-name to servicename Cause. You specified an invalid field as a parameter to be passed to a service in the SEND Parameter Definition screen. The field is invalid as a parameter because it has an OCCURS clause or is within a group that has an OCCURS clause; therefore, the specific field you mean to pass is ambiguous. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery.
Pathmaker Messages Field not found: qualified-name Cause. You changed a DDL definition for a reference object, omitting a field that was present when you updated this requester's context. Issued by the Pathmaker product. Effect. Requester generation, default screen creation, or simulation fails. Recovery. Remove the field name from the Display Field List screen or the Requester Parameters screen, as needed. Alternatively, you can change the DDL definition to include the field name.
Pathmaker Messages File Description Error Cause. Server error issued by the generated application. Effect. An ENSCRIBE file I/O completed unsuccessfully. Recovery. Reissue the user transaction. File does not exist: file-name Cause. Pathmaker could not find a project catalog file or a skeleton file required for requester generation. Issued by the Pathmaker product. Effect. Requester generation fails. Recovery. Correct the file name if invalid.
Pathmaker Messages File operation error number (explanation) — file name Cause. PMPROJECT, PMINSTAL, PMADL, or the screen painter encountered an operating system error during I/O. The type of operation that caused the error, the error number, and the name of the file on which the error occurred, are given in the message. A short description of the error is also provided for some errors. Issued by the Pathmaker product, PMPROJECT, PMINSTAL, or PMADL. Effect. The program terminated. Recovery.
Pathmaker Messages File error err-num on program file: new-process-name Cause. The program file for new-process-name is unavailable because of a file error. Issued by the Pathmaker product. Effect. New Process startup fails. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for the recovery procedure for the particular system error. File error err-num on swap file: new-process-name Cause. The swap file for new-process-name is unavailable because of a file system error.
Pathmaker Messages File error on library file — new-process Cause. No library file can be specified in the configuration. This error should not occur. Issued by the Pathmaker product. Effect. New process startup fails. Recovery. Contact your system manager. Refer to the Guardian Procedure Errors and Messages Manual for details about new process errors. File name is not properly qualified — file name Cause.
Pathmaker Messages File operation error code (explanation) — file-name Cause. A file system error occurred on the file indicated by file-name. The operation indicates the file operation which returned the error. The code is the file system error code. The explanation describes the error code. Effect. The current PMADL operation is canceled. Any changes made to the current catalog by the operation are backed out. Recovery. Recovery depends on the nature of the file system error.
Pathmaker Messages Formal parameter is matched by more than one actual parameter — param-name Cause. A SEND or CALL action passes more than one value to a formal parameter of a service or requester. The formal parameter is indicated by param-name. Issued by PMADL. Effect. The requester description is not stored in the catalog. Recovery. Ensure that each formal parameter of the target service or requester is used only once in the CALL or SEND action.
Pathmaker Messages FROM copy library already opened: file-name Cause. You attempted to copy either a requester or a service. The requester copy library for the requester or the custom source file for the service is already open and cannot be copied. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Wait for a few moments and retry the operation. Use FUP LISTOPENS to check the FROM copy library. FROM copy library locked: file-name Cause. You attempted to copy either a requester or a service.
Pathmaker Messages FROM copy library open error: file-name Cause. You attempted to copy either a requester or a service. The Pathmaker program received a file open error while attempting to open the requester copy library file for the requester or the custom source file for the service. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Check the security of file-name. FROM project not found Cause. You attempted to copy either a requester, a service, or a server.
Pathmaker Messages FROM requester name required — please enter name Cause. You attempted to copy a requester but forgot to enter the name of the requester you meant to copy. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Enter a requester name and press SF1 to copy it. FROM requester not found Cause. The Pathmaker program could not find the requester that you tried to copy. Issued by the Pathmaker product. Effect. Copy fails. Recovery.
Pathmaker Messages FROM service name required — please enter name Cause. You attempted to copy a service but forgot to enter the name of the service you meant to copy. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Enter a service name and press SF1 to copy it. FROM service not found Cause. The Pathmaker program could not find the service that you are trying to copy. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Check the service name to see if you entered it correctly.
Pathmaker Messages Function key has no meaning on this screen Cause. This function key is not used on this screen. Issued by the Pathmaker product. Effect. None. Recovery. Position the cursor on the function key area of the screen and press F15 to see a list of available function keys. Function key has no meaning on this screen via Screen Painter Cause. You invoked the Display Detail screen from a Screen Painter session.
Pathmaker Messages Function not implemented; Call to called-program Cause. You attempted a CALL to a nonexistent run-unit (Requester). CALL error issued by the generated application. Effect. CALL fails. Recovery. Implement the called requester. Generated source and object files must be unique Cause. The same name was specified for the source and object files. Issued by the Pathmaker product. Effect. Server or service generation fails. Recovery. Change the name of either the source or the object file.
Pathmaker Messages Help text already defined for screen field — field-name Cause. The screen field was already defined in the input file of a HELPUTIL UPDATE operation. Issued by HELPUTIL. Effect. The requester was not updated in the help database. Recovery. Correct the input file. Help text line exceeds 79 characters Cause. A line of text in the source file is too long to store in the HELP database. Issued by HELPUTIL. Effect. The line is ignored and the current requester is not updated. Recovery.
Pathmaker Messages I/O error; Send to server-class system-error-num Cause. A system error occurred during an I/O operation. SEND error issued by the generated application. Effect. SEND fails. Recovery. Recovery depends on the system error reported. Refer to the Guardian Procedure Errors and Messages Manual for information about operating system error messages. Illegal call to initial requester: requester-name Cause.
Pathmaker Messages Illegal DEFMODE supplied: new-process-name Cause. new-process-name was compiled with DEFMODE=OFF. Issued by the Pathmaker product. Effect. New Process startup fails. Recovery. Recompile new-process. Illegal file format, err-num: new-process-name Cause. The file is not an object file. If err-num is an odd value, then the library file is in error. If err-num is an even value, then the program file is in error. Issued by the Pathmaker product. Effect. New Process startup fails. Recovery.
Pathmaker Messages Illegal initial action Cause. You entered an action other than CALL, SEND, or USER as the initial action of this requester, then attempted to generate the requester. This condition is normally detected when you attempt to update the Function Key Assignments screen. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Note this error message and contact your Tandem representative. Illegal logical process name Cause.
Pathmaker Messages Illegal pseudofield param, formal-parameter-name of program Cause. You specified a pseudofield in a reply parameter from a service or as a CALL parameter. This condition is normally detected when you update the Requester Parameters screen, the CALL Parameter Definition screen, or the SEND Parameter Definition screen. The program can be a requester name or a service name, depending on whether you specified a CALL or a SEND parameter. Issued by the Pathmaker product and by PMADL. Effect.
Pathmaker Messages Illegal service name for this type of requester:service-name Cause. You specified a SEND to a custom service from a DB requester, or you specified a SEND to a standard service from a TRNS requester. This condition is normally detected when you update the Function Key Assignments screen. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Note this error message and contact your Tandem representative.
Pathmaker Messages Illegal terminal for a Nowait request — new-process Cause. You tried to generate a requester or server from the project home terminal. Issued by the Pathmaker product. Effect. New process startup fails. Recovery. You cannot generate a requester or server from this terminal because it is the project's home terminal. Either change the home terminal for the project by using PMPROJECT ALTER or generate the requester or server from another terminal.
Pathmaker Messages Incorrect project installation (TMF Error 75) — contact support Cause. The Pathmaker program encountered a TMF error while attempting to read the project catalog. This is an internal error. Issued by the Pathmaker product. Effect. The Pathmaker program cannot complete the current action. Recovery. Note this error message and contact your Tandem representative. Incorrect reply from new process server Cause. Message from new process server is of incorrect length.
Pathmaker Messages INSERT enabled and linked field is a syskey: reference-object-name Cause. In a DB requester, the link field is a syskey and the insert database service is set to Y. Issued by the Pathmaker product. Effect. Requester generation fails. Recovery. On the Record Instance Detail screen, set the Insert Database Service to N or change the link field so it is not the syskey. Insert fails. Duplicate key Cause.
Pathmaker Messages Insert function not allowed — default screen creation has been disabled Cause. You attempted to insert a line in the Display Field List. You cannot modify the Display Field List because the Create Default screen field on the Requester Definition screen is set to N. Issued by the Pathmaker product. Effect. Update fails. Recovery. Add the field directly to the screen by using the Screen Painter F4 function (Data Field partial screen).
Pathmaker Messages Insert OK, but DELETE on old image failed Cause. You were updating a key value, and the new record was originally inserted, but the delete of the record with the old key value failed, so the update was canceled. Issued by the generated application. Effect. Operation fails. Insert canceled. Recovery. Try to delete the old record, then retry the INSERT operation. If the problem persists, contact your Tandem representative. Insert service enabled but no insert action defined Cause.
Pathmaker Messages Installation has one or more projects running — subvolume Cause. You attempted to redefine or move an installed version of the Pathmaker product while projects in the installation were running. All projects in an installation must be stopped when altering the installation. Issued by PMINSTAL. Effect. Operation canceled. Recovery. Shut down the projects in the installation. Installation target is not an available disk volume Cause.
Pathmaker Messages Insufficient memory to perform this operation Cause. There is not enough temporary memory to perform the operation (such as generating a requester). Issued by the Pathmaker product and by PMADL. Effect. Operation failed or was canceled. Recovery. If you tried a Screen Painter operation, then break the operation up into multiple operations, each of which manipulates only a few screen elements. Or simplify the requester by reducing the number of objects in the requester context.
Pathmaker Messages Internal error number [, number [ , number ] ] Cause. An internal error occurred. Issued by the Pathmaker product. Effect. The Screen Painter session abended. The screen being edited may or may not have been updated in the catalog. Recovery. Note this error message and contact your Tandem representative. Internal error — Exception exception-num Cause. Internal error. Issued by the Pathmaker product. Effect. Operation fails. Recovery. Note exception number and contact support.
Pathmaker Messages Internal error; Substatus= substatus Cause. An error occurred that was detected by a version of Pathway that is newer than the Pathmaker version that generated the application. CALL error issued by the generated application. Effect. SEND fails. Recovery. Use a version of Pathway that is compatible with the version of the Pathmaker product. Internal error; Termination status > 4 Cause. An error occurred that was detected by Pathway.
Pathmaker Messages Invalid action for standard service Cause. You tried to add, update, delete, or copy a standard service, or you tried to define IPCs or logical files for a standard service. Issued by the Pathmaker product. Effect. Operation fails. Recovery. You cannot perform any of these operations for a standard service. A standard service is a service provided by Pathmaker to perform basic operations on the database such as reading, writing, or updating a record or table.
Pathmaker Messages Invalid At code — please reenter Cause. You entered a value that is not one that the Pathmaker product recognizes for the At field. Issued by the Pathmaker product. Effect. Add or update fails. Recovery. Enter one of the following values: L Displays the child record at the Link field of the parent record on the application screen. E Displays the child record at the End of the parent record on the application screen. Invalid attribute selection — selection Cause.
Pathmaker Messages Invalid Before-Image Host Variable name Cause. Before-Image Host Variable names must be valid COBOL names. Effect. Operation fails. Recovery. Choose a valid name and repeat the operation. Invalid Blinking value — please reenter Cause. You entered a character other than Y or N in the Blinking field of the Display Detail screen. Case is not important; the Pathmaker product upshifts lowercase letters to uppercase. Issued by the Pathmaker product. Effect. Update fails. Recovery.
Pathmaker Messages Invalid Compile value — please reenter Cause. You entered a value other than Y or N in the Compile field. Case is not important; lowercase letters are automatically upshifted. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter Y or N to continue. Invalid copy library — please reenter Cause. You entered an invalid file name for the copy library file. Issued by the Pathmaker product. Effect. Update fails. Recovery. Correct the file name.
Pathmaker Messages Invalid cursor position for requested function Cause. Cursor is in wrong position for requested function. Issued by the Pathmaker product and by the generated application. Effect. None. Recovery. Move the cursor to the appropriate position for the function you requested. Press the function key again. Invalid data file subvolume name — please reenter Cause. You entered an invalid disk file name for storing the application's data files. Issued by the Pathmaker product and by PMADL.
Pathmaker Messages Invalid define name: define-name Cause. You attempted to update the SQL Table Registration screen, but a name in the Define Name column is not a valid DEFINE name. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Correct the DEFINE name and press F2 to update the screen. The Pathmaker Reference Manual describes the rules for DEFINE names. Invalid directory name: directory-name Cause. Required subvolume is missing. Issued by the Pathmaker product. Effect.
Pathmaker Messages Invalid Embedded SQL value — please reenter Cause. You attempted to enter a value other than Y or N into the Embedded SQL field of the Service Definition screen. Issued by the Pathmaker product. Effect. Update fails. Recovery. Change the value to either Y or N and retry the operation. Invalid field type (FILLER, REDEFINES, 66, or 88):field-name Cause.
Pathmaker Messages Invalid file type: file-name Cause. When generating a server, the specified listing file is a key-sequenced file. The COBOL85 compiler will not write out a listing to such a file. Effect. Operation canceled. Recovery. If using a listing file that is a disc file, it must be unstructured, relative, or entry sequenced. The file must already exist. Invalid Heading Default value — please reenter Cause.
Pathmaker Messages Invalid Help Text Default value — please reenter Cause. You entered a character other than Y or N in the Default column of the Help Text field on the Display Detail screen and then attempted to update the screen. Case is not important; the Pathmaker product upshifts lowercase letters to uppercase. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter either a Y or an N and press F2 to update the screen. Invalid Hidden value — please reenter Cause.
Pathmaker Messages Invalid INSPECT terminal name — please reenter Cause. You entered an invalid value into the Inspect terminal name field of the Application Installation screen. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Enter a valid Inspect terminal name. Inspect terminal names can be a maximum of eight characters.
Pathmaker Messages Invalid Key: no record found Cause. You attempted to access a record identified by a key, and that record does not exist in the file. Server error issued by the generated application. Effect. Access fails. Recovery. Use a different key and retry the operation. Invalid Key: Sequence Error Cause. A sequence error exists for the sequentially accessed Indexed file.
Pathmaker Messages Invalid logical file name: illegal-name Cause. You specified an invalid logical file name. Issued by the Pathmaker product. Effect. Update fails. Recovery. Correct the logical file name. Logical file names can be from 1 to 30 alphanumeric and hyphen (-) characters, excluding all other special characters such as pound sign (#) and dollar sign ($). Logical file names must start with a letter and cannot be a COBOL reserved word. Invalid macro name — please reenter Cause.
Pathmaker Messages Invalid name — C reserved word: invalid-name Cause. A user-specified name is the same as a C reserved word. Issued by the Pathmaker product and by PMADL. Effect. Service generation fails. Recovery. Change the specified name to a legal name. Invalid name — illegal syntax: name Cause. The name in the message does not follow the Pathmaker naming rules. All characters must be alphabetic, numeric, or a hyphen.
Pathmaker Messages Invalid name — SCREEN COBOL reserved word name Cause. name is a reserved word in Screen COBOL. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Change name, avoiding Pathway and Screen COBOL reserved words. The Data Management Reference Summary contains lists of reserved words for Pathway, DDL, Screen COBOL, COBOL, and Enform. Invalid Nowait Value — new-process Cause. The new process request does not contain Y or N in the NOWAIT-FLAG.
Pathmaker Messages Invalid object file — please reenter Cause. You forgot to specify an object file name on the Server Definition screen, or you specified an invalid disk file name for the object file. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Correct the disk file name. Invalid object type — please reenter Cause.
Pathmaker Messages Invalid Overwrite value — please reenter Cause. You entered a character other than Y or N in the Overwrite field of the Requester Generation Data screen. Case is not important; the Pathmaker product upshifts lowercase letters to uppercase. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter either a Y or an N and press F2 to update the screen. Invalid PATHMON log file name — please reenter Cause.
Pathmaker Messages Invalid PATHMON process name — please reenter Cause. You specified an invalid PATHMON process name on the Application Installation screen. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Correct the PATHMON name. PATHMON names can be a maximum of six characters. PATHMON names begin with a dollar sign ($), followed by one to five alphanumeric characters, excluding all other special characters such as pound sign (#) and dollar sign ($).
Pathmaker Messages Invalid priority — please reenter Cause. You entered an invalid value into the Priority field of the Process Configuration screen. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter a value from 1 through 199. Priority 1 is the lowest priority. Priority 199 is the highest priority. The default priority is 140. Invalid program catalog — please reenter Cause. You entered an invalid NonStop SQL catalog name into the Program Catalog field of the Server Definition screen.
Pathmaker Messages Invalid Protected value — please reenter Cause. You entered a character other than Y or N in the Protected field of the Display Detail screen. Case is not important; the Pathmaker product upshifts lowercase letters to uppercase. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter either a Y or an N and press F2 to update the screen. Invalid pseudofield: illegal-name Cause.
Pathmaker Messages Invalid record name — please reenter Cause. You entered an invalid record name into either the Record Name field or the As Copy Of field of the Record Instance Detail screen. Issued by the Pathmaker product. Effect. Update fails. Recovery. Correct the record name. Record names can have from 1 to 30 alphanumeric and hyphen (-) characters, excluding all other special characters such as pound sign (#) and dollar sign ($). The first character in the record name must be a letter.
Pathmaker Messages Invalid reply data from Pathmaker catalog server — server-name Cause. PMADL received an invalid reply message from a Pathmaker user interface server while compiling a PMADL object description. Issued by PMADL. Effect. The object description being compiled is removed from the catalog and its previous description, if any, is reinstated. Recovery. Contact your Tandem representative. Invalid reply name: invalid-name Cause.
Pathmaker Messages Invalid Request code Cause. The new process server received a request that did not have the correct REQUEST^CODE (101) in the first byte. Issued by the Pathmaker product. Effect. New process startup fails. Recovery. Check the version of the new process requester installed in the Pathmaker release subvolume. If it is the same as the version of the Pathmaker product, note the error message and contact your Tandem representative. Invalid Request length Cause.
Pathmaker Messages Invalid Requester Features value — please reenter Cause. You entered a value other than Y or N in one of the Requester Features fields. Case is not important; lowercase letters are automatically upshifted. Issued by the Pathmaker product. Effect. Add or update fails. Recovery. Enter Y or N to continue. Refer to the online help text or to the Pathmaker Reference Manual for more information about the requester features. Invalid requester name — please reenter Cause.
Pathmaker Messages Invalid Reversed value — please reenter Cause. You entered a character other than Y or N in the Reversed field of the Display Detail screen. Case is not important; the Pathmaker product upshifts lowercase letters to uppercase. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter either a Y or an N and press F2 to update the screen. Invalid screen field name: field-name Cause.
Pathmaker Messages Invalid Screen Picture clause — please reenter Cause. You attempted to update the Display Detail screen but the Screen Picture field contains an invalid picture clause. Issued by the Pathmaker product. Effect. Update fails. Recovery. The Screen Picture field must contain a valid Screen COBOL picture. Correct the screen picture and press F2 to update the screen. Invalid Screen Picture Default value — please reenter Cause.
Pathmaker Messages Invalid Server class name; Send to server-class Cause. The value you gave for the name of the server class does not appear in the Pathway configuration for the generated application. SEND error issued by the generated application. Effect. Operation canceled. Recovery. Check the Pathway configuration. You might have to regenerate the mapping requester and reinstall the test application. Invalid server name; name has been used to register a SQL table Cause.
Pathmaker Messages Invalid service type — please reenter Cause. You attempted to use a type in a service definition that is not a valid Pathmaker service type. Issued by the Pathmaker product. Effect. Operation fails. Recovery. Correct the service type and press F2 to update the screen. Invalid Service Code Cause. Generated server has received a request for a service code that does not exist. Server error issued by the generated application. Effect. Request not processed. Recovery.
Pathmaker Messages Invalid service type — please reenter Cause. You attempted to use a type in a service definition that is not a valid Pathmaker service type . Issued by the Pathmaker product. Effect. Operation fails Recovery. Correct the service type and press F2 to update the screen. Invalid skeleton — please reenter Cause. You entered an invalid disk file name for the requester skeleton or server skeleton. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery.
Pathmaker Messages Invalid SQL IO Section name Cause. A SQL IO section name must be both a valid Pathmaker name and a valid COBOL name. Effect. Operation name Recovery. Choose a valid name and repeat the operation. Invalid subscript value; In called-program Cause. The custom code contains an invalid value in a subscripted variable. CALL error issued by the generated application. Effect. CALL fails. Recovery. Check the custom code and correct the variable's value, then regenerate.
Pathmaker Messages Invalid Tab If Full value — please reenter Cause. You entered a character other than Y or N in the Tab If Full field of the Display Detail screen. Case is not important; the Pathmaker product upshifts lowercase letters to uppercase. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter either a Y or an N and press F2 to update the screen. Invalid table object name: table-object-name Cause.
Pathmaker Messages Invalid TMF On value — please reenter Cause. You entered a value other than Y or N in the TMF On field. Case is not important; lowercase letters are automatically upshifted. Issued by the Pathmaker product. Effect. Add or update fails. Recovery. Enter Y or N to continue. Invalid TO requester name — please reenter Cause. You attempted to copy a requester, but the new requester name that you supplied is not a valid requester name. Issued by the Pathmaker product. Effect. Copy fails.
Pathmaker Messages Invalid Underlined value — please reenter Cause. You entered a character other than Y or N in the Underlined field of the Display Detail screen. Case is not important; Pathmaker upshifts lowercase letters to uppercase. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter either a Y or an N and press F2 to update the screen. Invalid User Conversion value — please reenter Cause. You entered an invalid value into the User Conversion field of the Display Detail screen.
Pathmaker Messages Invalid work subvolume name — please reenter Cause. You entered an invalid volume and subvolume name into the Work Subvolume field of the Pathmaker Main Menu. Issued by the Pathmaker product. Effect. Operation fails. Recovery. Correct the work subvolume name and retry the operation. The work subvolume must be a valid volume and subvolume name. Item has unsupported data type: qualified-name Cause. A field in the requester context has an unsupported data type.
Pathmaker Messages Keys cannot be updated in views Cause. You attempted to update a key by using a view. Issued by the generated application. Effect. Operation fails. Recovery. To update a key value, access the base table containing the key column. Library conflict: new-process-name Cause. A shared program-file does not have the same library configuration for all users. Issued by the Pathmaker product. Effect. New Process startup fails. Recovery. Make sure all library configurations are consistent.
Pathmaker Messages Link field data types are incompatible:instance-field-name Cause. You specified parent and child link fields that are of different data types. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Change the Record Instance Detail of the child record or of the parent record so that the link fields match. Linked field is not a key, record instance:instance-field-name Cause.
Pathmaker Messages List file error system-error-num Cause. Pathmaker encountered a file system error while trying to create or open the file specified on the Listing Device field of the Requester Generation Data screen. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. For further information about the specific file system error you encountered, refer to the Guardian Procedure Errors and Messages Manual.
Pathmaker Messages Logic error in resolving qualified name — contact support Cause. The Pathmaker product was unable to resolve a qualified field name during a list or update operation. This is an internal error. Issued by the Pathmaker product and by PMADL. Effect. List or update fails. Recovery. Note this error message and contact your Tandem representative. Logical file name cannot be the same as the DDL record name Cause.
Pathmaker Messages Logical file name conflicts with parameter name:logical-filename or parameter-name Cause. You specified a logical file name that is the same as the name of a parameter to the service. This condition is normally detected either when you update the Logical File Entries screen or the IPC Definition screen. Issued by the Pathmaker product and by PMADL. Effect. Server generation fails. Recovery. Note this error message and contact your Tandem representative.
Pathmaker Messages Logical file name is a request param: logical-file-name Cause. You attempted to update the Logical File Entries screen, but one of the names in the Logical File Name column is a request parameter on the IPC Definition screen for this service. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Change the name in the Logical File Name column and press F2 to update the screen. Logical file name required — please enter name Cause.
Pathmaker Messages Macro is not registered Cause. You have referenced a macro that has not been registered in the project catalog. Effect. Operation fails. Recovery. Enter a macro name and repeat the operation. Macro name required — please enter name Cause. A macro name must be supplied for this operation. Effect. Operation fails. Recovery. Enter a macro name and repeat the operation. Macro not found Cause. You searched for a macro that does not exist in the project catalog. Effect. None. Recovery.
Pathmaker Messages Maximum Box Nesting (8 levels) exceeded Cause. You specified more than eight levels of child records for this requester and attempted to create a default screen. Issued by the Pathmaker product and by PMADL. Effect. Requester generation or default screen generation fails. Recovery. The default screen generator will not create a child record box that is too narrow for the data fields intended to go it.
Pathmaker Messages Missing ASSIGN parameter Cause. You did not provide a required ASSIGN parameter in the edited PATHSVRS file. Issued by the generated application. Effect. SQL standard server stops. Recovery. Use the Pathway PATHCOM command, ALTER SERVER, to provide the ASSIGN parameter in the PATHSVRS file, then restart the SQL standard server. Refer to the Pathway PATHCOM Reference Manual for more information about the ALTER SERVER command. Missing directive for first block of text Cause.
Pathmaker Messages Missing reference object in field: field-name Cause. You specified an elementary field name, but omitted the reference object for the field on the SEND Parameter Definition screen. Issued by the Pathmaker product. Effect. Update fails. Recovery. Specify a reference object for the elementary field. Mixed data item is too long to fit on line: name Cause. A data item is too long to fit on the screen and cannot be segmented.
Pathmaker Messages Must be check failed on item not being displayed. Cause. Data received by Linkage or from the server is out of range for a variable used as an outgoing parameter. Requester error issued by the generated application. Effect. CALL or SEND fails. Recovery. Check database or non-Pathmaker calling requester. Must have READ with UPDATE or DELETE, instance reference-object-name Cause.
Pathmaker Messages Name conflicts with Server or Service name: name Cause. The name of a field, logical file, or parameter is the same as the name of its service or server. Issued by the Pathmaker product and by PMADL. Effect. Server generation fails. Recovery. Change the name of the field, logical file, or parameter so it is not the same as its service or server name. Named service not found: missing-name Cause.
Pathmaker Messages No action definitions found for this requester Cause. Pathmaker did not find any function key assignments for this requester during a routine check. This condition cannot normally occur because the user interface requires that you define at least one function key when updating the Function Key Assignments screen. Issued by the Pathmaker product. Effect. Update fails. Recovery. Note this error message and contact your Tandem representative.
Pathmaker Messages No base screen displayed Cause. A print request was attempted before the screen was displayed. Print error issued by the generated application. Effect. Print fails. Recovery. Check custom code for early ACCEPT. No changes were specified. Cause. You tried an update operation without first changing the record read from the database. File operation error. Effect. Update operation fails. Recovery. Make the changes, then retry the operation.
Pathmaker Messages No custom services allowed for DB requesters Cause. You specified a custom service for a database requester. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Remove the custom service from the Function Key Assignments for this requester. If you want to invoke a custom service, you must use a TRNS requester. No DEFINE specified for table file-name Cause. You attempted a request that refers to a DEFINE that the SQL standard server cannot find.
Pathmaker Messages No help exists for this screen — contact support Cause. If you are running Pathmaker, this Pathmaker screen does not have any help text records associated with it in the help database. If you are running the generated application, this application screen does not have any help text records associated with it. Issued by the Pathmaker product and by the generated application. Effect. None. Recovery. If you are running Pathmaker, note the screen title and contact your Tandem representative.
Pathmaker Messages No HELP is available for this topic/subtopic — help-topic Cause. The keyword indicated by help-topic does not denote a help topic recognized by PMADL. Issued by PMADL. Effect. PMADL ignores the undefined help topic, and any subtopics which follow it, and displays help for the preceding, defined help topic. Recovery. Correct the help topic keyword in the ?HELP command. No help text is defined for requester — requester Cause.
Pathmaker Messages No key field was identified. Cause. You tried a read next operation before reading the first record. Issued by the generated application. Effect. Read next operation fails. Recovery. Precede a read next operation by one of the following operations: read first, read approximate, read exact, or read generic. No more assigned function keys found Cause. You are at the end of the Display Text series of screens for this requester. Issued by the Pathmaker product. Effect. None. Recovery.
Pathmaker Messages No more display details found Cause. You have reached the end of the display detail information for this reference object. Issued by the Pathmaker product. Effect. Pathmaker continues to show the Display Detail screen. Recovery. No recovery is needed. No more display fields found Cause. You are already at the end of the Display Field List for this reference object. Issued by the Pathmaker product. Effect. None. Recovery. No recovery needed.
Pathmaker Messages No more macros found Cause. You are at the end of the macro list. Effect. None Recovery. No recovery needed. No more macro parameters found Cause. You are at the end of the macro parameter list. Effect. None Recovery. No recovery needed. No more process configurations found Cause. You are already at the end of the list of processes that can be configured for Pathmaker. Issued by the Pathmaker product. Effect. None. Recovery. No recovery needed. No more projects found Cause.
Pathmaker Messages No more reference objects found Cause. You have reached the end of the list of reference objects for this project. Issued by the Pathmaker product. Effect. Pathmaker continues to display the Reference Object Value List screen. Recovery. No recovery is needed. No more reply IPCs found Cause. You are already at the end of the list of objects used in the reply message for this service. Issued by the Pathmaker product. Effect. None. Recovery. No recovery needed.
Pathmaker Messages No more requester parameters found Cause. You are at the end of the list of formal parameters for this requester. Issued by the Pathmaker product. Effect. None. Recovery. If you get this message and the Requester Parameters screen does not list any parameters, then no formal parameters have been defined for this requester. You can define them now by making the appropriate entries on the Requester Parameters screen. No more requesters found Cause.
Pathmaker Messages No more server class mappings found Cause. You are at the end of the list of server class mappings. Issued by the Pathmaker product. Effect. None. Recovery. If you want to see the list again from the beginning, clear the service name from the Service Name field and press F4. No more server classes found Cause. You are already at the end of the list of server classes for this server. Issued by the Pathmaker product. Effect. None. Recovery.
Pathmaker Messages No more service IPCs found Cause. You are already at the end of the IPC definition list. Issued by the Pathmaker product. Effect. None. Recovery. No recovery needed. No more services found Cause. You are already at the end of the list of services. Issued by the Pathmaker product. Effect. None. Recovery. To list services from the beginning, clear the Service Name field by typing spaces over the current entry.
Pathmaker Messages No more SQL table registrations found Cause. You have reached the end of the NonStop SQL table registration information for this project. Issued by the Pathmaker product. Effect. Pathmaker continues to display the SQL Table Registration screen. Recovery. No recovery is needed. No more SQL tables found Cause. You have reached the end of the list of NonStop SQL tables that exist in this NonStop SQL catalog. Issued by the Pathmaker product. Effect.
Pathmaker Messages No object defined Cause. You pressed a function key that requires a requester, service, or server to act upon. Issued by the Pathmaker product. Effect. Action fails. Recovery. Enter the object name and press F4 to list the object. If you cannot remember the object name, press F9 to see a list of available objects. No object file to contain server object specified Cause. You did not specify an object file to receive the compiled server. Issued by the Pathmaker product. Effect.
Pathmaker Messages No pages available on this screen Cause. You asked for another page from a requester that contains only a single page. Issued by the generated application. Effect. The operation is not performed. Recovery. No recovery necessary. No paging area is defined in this screen Cause. You selected Previous Page (F1), First Page (SF1), Next Page (F2), Last Page (SF2), or Delete Paging Area (SF9) but the screen does not contain a paging area. Issued by the Pathmaker product and by PMADL. Effect.
Pathmaker Messages No PMCB available; Send to server-class Cause. The request requires the TCP to communicate with an external PATHMON, but the maximum number of PATHMON processes the TCP can communicate with has been reached. Send error issued by the generated application. Effect. SEND fails. Recovery. The value specified in the SET TCP MAXPATHWAYS parameter sets the maximum number of PATHMON processes the TCP can communicate. If this parameter is less than the maximum value of 4095, then increase it.
Pathmaker Messages No parent item. Cause. You tried to perform an operation on a nested box without first performing a read or insert operation on the containing box. File operation error issued by the generated application. Effect. Operation fails. Recovery. Perform a read or insert operation on the containing box, then retry the operation. No Previous Page Cause. The displayed page is the first page in the requester. Issued by the Pathmaker product and by the generated application. Effect.
Pathmaker Messages No project or catalog is currently selected Cause. You attempted to perform an operation, such as compiling a PMADL object description, that requires a currently open catalog. However, no catalog has been specified. Issued by PMADL. Effect. The operation is ignored. Recovery. Specify a catalog using the ?PROJECT or ?CATALOG commands. No Records or Tables were specified. Cause. In a DB requester, no DDL records or SQL tables or views are defined. Issued by the Pathmaker product. Effect.
Pathmaker Messages No SEND action allowed on initial action for DB requesters Cause. You specified a SEND as an initial action for a DB requester. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Remove the SEND from the initial action for the requester. You might have received this error because you wanted to read the default values for the data fields on the application screen.
Pathmaker Messages No SHORTHAND views allowed for DB requesters: view-name Cause. You tried to include a SHORTHAND view in the requester context for the DB requester or you tried to add a SHORTHAND view in the Record Instance Detail screen for the DB requester. Issued by the Pathmaker product and by PMADL. Effect. Add or Update fails. Recovery. Exclude the SHORTHAND view for the requester context or in the Record Instance Detail screen. SHORTHAND views are not allowed for DB requesters.
Pathmaker Messages No standard services allowed for TRNS requesters Cause. You specified a SEND to a standard service on the Function Key Assignment screen of a TRNS requester. Standard services, services whose names begin with the reserved prefix T9154-, are available only for DB requesters. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Change the service name so that it refers to a service you have defined or will define. No target configuration was defined — name Cause.
Pathmaker Messages Node not available to retrieve the required data Cause. You attempted an SQL operation on a node that was not available. Issued by the generated application. Effect. Operation fails. Recovery. Retry the operation when the node is available. Non-recoverable error encountered — exiting Pathmaker Cause. Pathmaker was attempting to retrieve information from the Active Terminal file (ACTIVE). Issued by the Pathmaker product. Effect. Pathmaker start up fails. Recovery.
Pathmaker Messages Not allowed to list next — please update before listing Cause. You inserted a new line on the Display Field List screen, then attempted to list the next page before updating the screen. Issued by the Pathmaker product. Effect. Action fails. Recovery. Press F2 to update the screen, then list the next page. Not enough space to compile the screen definition Cause. The simulation server does not have enough memory to generate the current screen display. Issued by the Pathmaker product.
Pathmaker Messages Number is out of the range of values allowed in this context Cause. You used an invalid number. Issued by PMADL. Effect. The object description containing the invalid numeric value is not stored in the current catalog. Recovery. Correct the numeric value. Numeric DB error Cause. Requester error issued by the generated application. A numeric (not comp) item on the screen was returned from the server without a numeric value. Effect. The item is set to zero and highlighted.
Pathmaker Messages Object file is out of date with service definition — must compile Cause. A C server was being compiled, one of the services is defined as "Compile=N," and Pathmaker has detected that it needs to be recompiled. Issued by the Pathmaker product. Effect. Server generation fails. Recovery. Compile the service outside of Pathmaker or change the compile flag to Y and regenerate the server. Object is not defined in the catalog — object-name Cause.
Pathmaker Messages Only CALL/USER allowed for the MENU/DB requester's initial action Cause. You entered an incorrect action value in the Initial Action field on the Function Key Assignment screen for the MENU or DB requester. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Enter either CALL or USER values and retry the update. You can only enter CALL or USER action values for MENU or DB requesters in this field. Only CALL and SEND actions may have passed parameters Cause.
Pathmaker Messages Only name changes allowed — no additions Cause. You attempted to add a parameter to the CALL Parameter Definition screen or to the SEND Parameter Definition screen; the parameter does not have a corresponding formal parameter supplied by Pathmaker. Issued by the Pathmaker product. Effect. Update fails. Recovery. If you are on the CALL Parameter Definition screen, go to the Requester Parameters screen of the called requester and add the parameter to the formal parameter list.
Pathmaker Messages OPEN error: filename Data file security violation. (048) Cause. The data file is secured so that you are not able to open it through this application. (file system error 48.) Issued by the generated application. Effect. The file open operation failed and the requester was terminated. Recovery. Make sure the Pathway system supporting the Project is executing under the User ID of the owner of the Project (this is the user who created the Project).
Pathmaker Messages OPEN error: filename File name was not assigned. Cause. The logical file name specified in the requester definition is not the subject of an ASSIGN in the server configuration. Issued by the generated application. Effect. The file open operation failed and the requester was terminated. Recovery. Modify the server configuration to include an ASSIGN for the file. This will happen automatically if the application configuration is regenerated.
Pathmaker Messages OPEN error: filename Mismatch on key count Cause. The number of keys in the file as described in the application definition differs from that in the current physical file. This indicates that the current state of the file differs from that described in the DDL definition naming that file at the time the application was created. Issued by the generated application. Effect. The file open operation failed and the requester was terminated. Recovery.
Pathmaker Messages OPEN Process-Config file: error 12. Cause. Harmony cannot access the new process configuration file, DICTNPC; Harmony must open DICTNPC on the project catalog subvolume to guide new process creation. Error 12 indicates that another user opened DICTNPC with exclusive access. Issued by the Pathmaker product. Effect. Pathmaker startup fails. Recovery. Ask the other user to close DICTNPC and reopen it with shared access. You can use the FUP LISTOPENS command to determine who opened the file.
Pathmaker Messages Overlay screen in two areas; In called-program Cause. The programmer tried to display an overlay in two places on a screen at the same time. CALL error issued by the generated application. Effect. TCP stops the terminal. Recovery. Correct the program, then retry operation. Paging area overlaps a element in the base area Cause. You redefined the paging area so that it overlaps a screen element that was formerly outside the paging area. Issued by the Pathmaker product and by PMADL.
Pathmaker Messages Parameter mismatch in CALL/SEND to object-name Cause. You changed the Requester Parameters screen of a called requester or the IPC Definition of a service, or you forgot to create the CALL or SEND parameter list before attempting to generate the requester. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery.
Pathmaker Messages Parameter type clash, formal local-name of action-object Cause. You specified formal and actual parameters that are of incompatible types. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Change one of the parameter lists so that the reference objects are of compatible data types. CALL parameters are matched to formal parameters specified on the Requester Parameters screen of the called requester.
Pathmaker Messages Parent reference object name cannot be the same as the record name Cause. You specified the same record name for the Parent record field and the Record Name field. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. A record cannot be its own parent. Change the Parent record name so that another record in the requester context is this record's parent. Parent reference object not found in context:reference-object name Cause.
Pathmaker Messages Passed parameter specification missing for function key: function-key name Cause. You did not complete the CALL Parameter Definition screen or the SEND Parameter Definition screen for this requester. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery. Go to the appropriate parameter screen for this function key to update the parameter list. Pathmaker release release-number is not installed on this system Cause.
Pathmaker Messages PATHMON I/O error system-error-num; Send to server-class Cause. An I/O error occurred during the OPEN or WRITEREAD message to an external PATHMON. SEND error issued by the generated application. Effect. SEND fails. Recovery. Examine the system error and the external configuration. Contact your system administrator. Permanent error Cause. An I/O operation was unsuccessfully executed, and no further information is available concerning the operation.
Pathmaker Messages Point field in page page-num overflows the modified paging area Cause. You redefined the paging area so that a point field on page-num no longer fits in the paging area. Issued by the Pathmaker product and by PMADL. Effect. Paging area redefinition fails. Recovery. Point fields retain their relative locations on the page when the paging area is redefined. Ensure that the paging area is large enough to accommodate all screen elements on all the screen pages.
Pathmaker Messages Position the cursor on the screen element to move or delete Cause. You selected Move or Delete a Screen Element (F8), but the cursor is not positioned on a screen element to move or delete. Issued by the Pathmaker product. Effect. Operation canceled. Recovery. Move the cursor into the screen element to be deleted or moved. Previous and target subvolumes are the same Cause.
Pathmaker Messages Printer not ready Cause. The printer you specified requires attention, for example, it is in a NOT READY state. Print error issued by the generated application. Effect. Print fails. Recovery. Check the printer to see why it is not accepting jobs. Fix the problem and retry the operation or see your system manager. Printer not supported Cause. You attempted a print operation to an unsupported printer or the printer needs system manager attention.
Pathmaker Messages Process abnormal termination code (explanation) — file name Cause. A user interface server process or utility process started by PMADL terminated abnormally. The code is the completion code of the process. The explanation describes the completion code. The file name indicates the program object file of the terminated process. Issued by PMADL. Effect. The current PMADL operation is canceled. Any changes made to the current catalog by the operation are backed out. Recovery.
Pathmaker Messages Process configuration not found Cause. You searched for a process that does not exist in the preset configuration. No other process name follows the process name that you supplied. Issued by the Pathmaker product. Effect. None. Recovery. If you want to see the list again from the beginning, clear the process name from the Logical Name field. Press F4 to list the processes one by one on the Process Configuration screen. Process creation error code,detail (explanation) — file-name Cause.
Pathmaker Messages Process must be named Cause. You attempted to run Pathmaker without using the Pathmaker run command. Issued by the Pathmaker product. Effect. Pathmaker startup fails. Recovery. Run Pathmaker using the Pathmaker run command. Process name error num: new-process-name Cause. The name parameter is illegal for the new process startup. Issued by the Pathmaker product. Effect. New Process startup fails. Recovery. The process name is automatically generated.
Pathmaker Messages Program error: Corrupt data file info. Cause. The request to the standard server contains incorrect information about a data file that was previously opened successfully by the same requester. Issued by the generated application. Effect. Operation fails. Recovery. Contact your Tandem representative. Program is not configured — new-process Cause. The named program is not included in the DICTNPC file for new process configuration. Issued by the Pathmaker product. Effect.
Pathmaker Messages Project is already converted — name Cause. You attempted to convert a project that is not defined in the prior version of Pathmaker, but that is defined in the new version. Issued by PMPROJECT. Effect. PMPROJECT skips the indicated project and continues with the next project. Recovery. None required. Project is already defined — name Cause.
Pathmaker Messages Project is not defined — name Cause. You specified a project name that is not defined in the currently installed version of Pathmaker, or, for the CONVERT command, is not defined in the prior version of Pathmaker. Issued by PMPROJECT. Effect. PMPROJECT skipped the indicated project and continued with the next name. Recovery. Correct the project name. Project is not defined on system system-name — project-name Cause.
Pathmaker Messages Project or catalog was opened for read-only access Cause. You attempted to perform an operation on a Pathmaker object description, that modifies the currently open catalog, such as compiling a PMADL object description, but the current catalog was opened for read-only access. Issued by PMADL. Effect. The operation is ignored. Recovery. Open the catalog for read-write access using the ?PROJECT or ?CATALOG commands without the READ option. Project security violation — name Cause.
Pathmaker Messages Pseudocode size too big; Call to called-program Cause. The program is too large for the current version of Pathway. CALL error issued by the generated application. Effect. CALL fails. Recovery. The current version of Pathway does not support the size of the called program. Reduce the function in the called Requester and regenerate or install a newer version of Pathway. Pseudofield pseudofield-name cannot be displayed Cause.
Pathmaker Messages Pseudofield crosses the edge of the paging area Cause. You moved a pseudofield or defined a pseudofield so that it overlaps the left or right edge of the paging area. Issued by the Pathmaker product and by PMADL. Effect. Operation canceled. Recovery. Choose a different location for the pseudofield. Pseudofield in page page-num overflows the modified paging area Cause. You redefined the paging area so that a pseudofield on page-num no longer fits in the paging area.
Pathmaker Messages Pseudofield not allowed in the request copy of column Cause. You attempted to enter a pseudofield into the Copy Of column of the IPC Definition screen for a request message. Issued by the Pathmaker product. Effect. Update fails. Recovery. Remove the pseudofield from the Copy Of column and press F2 to update the screen. Pseudofield overlaps a screen-element at location Cause. You attempted to define a pseudofield on, or move a pseudofield to, a previously defined screen element.
Pathmaker Messages Pseudofields do not match: pseudofield-name Cause. You entered different pseudofields in the SEND and TO fields on the SEND Parameter Definition screen. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter the same pseudofields in these fields and retry the update. RDF record does not exist for reference object — contact support Cause. Pathmaker encountered an error while attempting to get an RDF record for an object in the Display Field List.
Pathmaker Messages Read fails. File error code = error-code Cause. A data file operation error was reported by the file system. Issued by the generated application. Effect. The read did not occur. Recovery. Consult the Guardian Procedure Error and Messages Manual for interpretation of the error code. Read fails. Record is locked Cause. The specified record is locked by another application. Issued by the generated application. Effect. The read did not occur. Recovery. Retry the operation.
Pathmaker Messages Readupdate error on Active-Term file Cause. Pathmaker encountered an error while attempting to read the active terminal file. Issued by the Pathmaker product. Effect. Pathmaker startup fails. Recovery. Check the security of ACTIVE to determine if it is secured for read-write access by your User ID. If necessary, ask your system manager to change the security. Record instance added; no new display field list created Cause.
Pathmaker Messages Record instances can be defined only for DB requesters Cause. You attempted to navigate to the Record Instance Detail screen and your current requester is not a DB requester. Issued by the Pathmaker product. Effect. None. Recovery. Enter the name of a DB requester and press F4 to list it, then press F11 again to navigate to the Record Instance Detail screen. Record is currently locked, try again later Cause.
Pathmaker Messages Record name required — please enter name Cause. You requested an action, such as Add or Delete, that Pathmaker cannot perform without a record name. Issued by the Pathmaker product and by PMADL. Effect. Action fails. Recovery. Enter the record name in the Record Name field and press the appropriate function key again. Record not found Cause. The record you tried to read does not exist in the database. Issued by the generated application. Effect. Read operation fails. Recovery.
Pathmaker Messages Reenter requester — SQL table has changed Cause. The SQL standard server and the DB requester must agree on the definition of a table. A consistency check is made when a requester is entered. If someone changes a table while the requester is being used, that requester must be re-entered so the check can be performed again. Issued by the generated application. Effect. The requester cannot access the table that has changed. Recovery. Exit and re-enter the requester.
Pathmaker Messages Reference field data type is not supported — field deleted Cause. You changed the DDL description of a data field to a data type that is not supported by Pathmaker. The unsupported data types for ENSCRIBE files are: BINARY 8 BINARY 32, -5 (or above) BINARY 64, -9 (or above) COMPLEX ENUMERATION FLOAT LOGICAL The unsupported data types for SQL tables are: FLOAT REAL DOUBLE PRECISION Issued by the Pathmaker product. Effect. The Screen Painter deleted the data field from the screen.
Pathmaker Messages Reference field is not an elementary field Cause. You specified a group field or a level 88 field in the second Reference field; the second Reference field must contain either an elementary field name or blanks. Issued by the Pathmaker product and by PMADL. Effect. The Screen Painter did not add or modify the data field. Recovery. Specify an elementary field name. Reference field is not an elementary field — field deleted Cause.
Pathmaker Messages Reference field name is ambiguous in the reference object — field-name Cause. A qualified field name, indicated by field-name, designates more than one field in the reference object which qualifies it. Issued by the Pathmaker product and by PMADL. Effect. The requester description is not stored in the catalog. Recovery. Provide additional qualification for the field name. Reference field redefines another field Cause.
Pathmaker Messages Reference object in context is currently locked — try again later Cause. Another user is concurrently updating this screen or the system response time is too slow. Issued by the Pathmaker product and by PMADL. Effect. Action fails. Recovery. Try the action again in a minute or two. If the problem persists, contact your Tandem representative. Reference object in dictionary is currently locked — try again later Cause.
Pathmaker Messages Reference object is not defined in the requester context — object name Cause. You attempted to add a data field through the Screen Painter that is not part of this requester's context, or you attempted to reference a field in a PMADL requester object description that is not declared as a reference object in the requester.. Issued by the Pathmaker product and by PMADL. Effect. If you were using the Screen Painter, it does not add or modify the data field.
Pathmaker Messages Reference object name required — please enter name Cause. You entered a DDL definition, record name, or SQL table object name in the Copy of column of the Requester Context screen without a corresponding alias name in the Reference Object column. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter an alias name in the Reference Object column. Reference object not found Cause. You attempted to delete a reference object that is not currently in the requester's context.
Pathmaker Messages Reference object not in context: name Cause. You deleted an object from the requester context that is referred to on either a Record Instance Detail screen or on the Requester Parameters screen. Issued by the Pathmaker product. Effect. Requester generation, default screen creation, or simulation fails. Recovery. Remove the reference object from the Record Instance Detail screen or from the Requester Parameters screen, as needed.
Pathmaker Messages Release D20 is already installed in subvolume Cause. You attempted to run PMINSTAL with the INITIAL option, but this version of Pathmaker has already been installed in the indicated subvolume. Issued by PMINSTAL. Effect. Operation canceled. Recovery. Use the REDEFINE or MOVE options to alter the installed version of Pathmaker. Release D20 is not installed on system name Cause.
Pathmaker Messages Renumbering context Cause. You attempted to update several objects in the Reference Object field in the Requester Context screen and Pathmaker ran out of sequence numbers. Issued by the Pathmaker product. Effect. Pathmaker is renumbering the reference objects. Recovery. This is an information message. No recovery is needed. Repetition index is missing or exceeds repetition count Cause.
Pathmaker Messages Repetition indexes are only allowed in DB record instances Cause. You attempted to supply a repetition subscript for a data field in a screen that does not belong to a DB requester record instance. Issued by the Pathmaker product and by PMADL. Effect. Operation canceled. Recovery. Eliminate the repetition index. Repetition too large instance-name, maximum is num Cause.
Pathmaker Messages Reply reference object name required — please enter name Cause. You entered a DDL definition, record name, or SQL table object name in the Reply Copy of column of the IPC Definition screen without a corresponding alias name in the Reply Reference Object column. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter an alias name in the Reply Reference Object column. Reply reference object not found Cause.
Pathmaker Messages Request name is a logical file entry: invalid-name Cause. You entered a request reference object name in the IPC Definition screen that matches a name on the Logical File Entries screen. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Enter a DDL definition, DDL record, NonStop SQL table object name, or a valid alias name and retry the update. Request or reply > maximum reply; Send to server-class Cause.
Pathmaker Messages Request reference objects exceed table limit — only 40 entries allowed Cause. You specified more than 40 Request Reference Objects on the IPC Definition screen. Issued by the Pathmaker product. Effect. Update fails. Recovery. Erase entries exceeding 40 from the screen, and press F2 to update. Requested operation would exceed limit of 40 access paths. Cause. There is a limit of 40 access paths per Pathmaker table object. Effect. Operation fails. Recovery.
Pathmaker Messages Requester has been added; no new display field list created Cause. You attempted to add a new requester and you set the create default screen field flag to N. Issued by the Pathmaker product. Effect. Requester has been added to the catalog. Recovery. No recovery required. The display field list will not be automatically created after you change the screen. Requester has been updated; no new display field list created Cause.
Pathmaker Messages Requester name cannot begin with T9154 prefix Cause. You entered a requester name that begins with T9154 on the Requester Definition screen. Issued by the Pathmaker product. Effect. Add fails. Recovery. Change the requester name and retry the add operation. Requester name is a SCOBOL reserved word — please reenter Cause. You entered a Screen COBOL reserved word in the requester name field on the Requester Definition screen. Issued by the Pathmaker product and by PMADL. Effect.
Pathmaker Messages Requester parameter not found Cause. You attempted to delete a requester parameter that does not currently exist on the Requester Parameters list. Issued by the Pathmaker product. Effect. Delete fails. Recovery. Press F4 to display the current formal parameter list. Resource unavailable; Send to server-class Cause. There is insufficient TCP Control Blocks configured. SEND error issued by the generated application. Effect. SEND fails. Recovery.
Pathmaker Messages Screen element is located outside paging area — PAGE not allowed Cause. You specified a page number in the location of a screen data field, pseudofield, point field, or decoration, but the row and column you specified are outside the requester’s paging area. Effect. The requester description is not stored in the catalog. Recovery. Remove the PAGE clause from the location specification. Screen element is located within the paging area — PAGE required Cause.
Pathmaker Messages Screen field is out of sequence — screen-field Cause. The screen field specified in a source file directive is not the next screen field defined for the current requester in the HELP database. This can be caused by rearranging directives in the source or by deleting a directive. Issued by HELPUTIL. Effect. The directive is ignored and the current requester is not updated. Recovery.
Pathmaker Messages Screen inconsistent with DDL: requester name Cause. Simulation encountered an abnormal condition while attempting to read the indicated requester screen definition. Effect. The operation is canceled. Recovery. Display the indicated requester using the Screen Painter to determine the abnormal condition. Correct the condition using the Screen Painter. Screen is inconsistent with DDL, please examine with Screen Painter Cause.
Pathmaker Messages Screen picture conflicts with the reference field — field deleted Cause. You changed the DDL description used by a data field so that the data field is no longer compatible with the reference field. Issued by the Pathmaker product and by PMADL. Effect. The Screen Painter deleted the data field from the screen. Recovery. If you want the data field to appear in the screen, exit the Screen Painter and correct the DDL description of the reference field.
Pathmaker Messages Screen recovery has occurred — verify data on screen Cause. You pressed SF14, Recover Screen. Issued by the Pathmaker product. Effect. Pathmaker redisplays the screen with the data that was on the screen before you pressed SF14. Recovery. Verify the data to determine if any data has been lost. Screen recovery. lost Some entries to this screen may have been Cause. Requester error issued by the generated application. Terminal momentarily fails. Effect.
Pathmaker Messages Security violation on SQL table: SQL-table-name Cause. Pathmaker received a security violation on an SQL table while attempting to access the SQL table. Issued by the Pathmaker product and by PMADL. Effect. Operation fails. Recovery. Check the security of the SQL table. Segment columns changed to match the display field location Cause. A REQUESTER object description contains a segmented display data field, but its first segment does not start at the same location as the data field.
Pathmaker Messages Select a previously defined page Cause. You pressed the Move Page function key (F11) or the Delete Page function key (SF11); the current page is the virtual page. The virtual page is a temporary, empty page following the last page in a screen and cannot be moved or deleted. Issued by the Pathmaker product. Effect. Operation canceled. Recovery. Use the one of the paging function keys, such as First Page (SF1) or Previous Page (F1), to select a previous page.
Pathmaker Messages Selection expression on view view-name violated Cause. You attempted an update or insert operation on a view defined with the WITH CHECK OPTION clause, producing a row that violates the view definition. The WITH CHECK OPTION clause prevents insertion of values into a view if those values would violate the view definition. Issued by the generated application. Effect. The insert or update operation fails. Recovery.
Pathmaker Messages SEND parameter not found Cause. Pathmaker could not find a SEND parameter while attempting to rematch the SEND parameter list with the formal parameters specified in the IPC Definition screen. This is an internal error. Issued by the Pathmaker product. Effect. Rematch fails. Recovery. Press F4 to list the current SEND parameters. If the problem persists, contact your Tandem representative. SEND parameters listed — context and parameters changed Cause.
Pathmaker Messages SEND parameters listed — parameters have been created Cause. Pathmaker created a SEND parameter list for this requester. Issued by the Pathmaker product. Effect. Pathmaker updated the project catalog. Recovery. This is an advisory message. No recovery is needed. SEND parameters listed — parameters have been rematched Cause.
Pathmaker Messages Send to Service: service-name Cause. You simulated a SEND to the service service-name. Issued by the Pathmaker product. Effect. The operation is not performed. Recovery. No recovery necessary. Sequence number overflow in catalog file — file-name Cause. A sequence number counter used to help generate unique key values for records in the file indicated by file-name has overflowed. If PMADL continued processing, it might reuse a sequence number value already used by an existing object.
Pathmaker Messages Server class already exists: server-class-name Cause. You specified a server class name that is already used for another server. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Change the server class name so that it is unique. Server class already used: server-class-name Cause. You entered the server class name in the Server Class Assignment screen which is not unique. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery.
Pathmaker Messages Server class not found Cause. You attempted to delete a server class that is not currently in the server class list. Issued by the Pathmaker product. Effect. Delete fails. Recovery. Press F4 to list the current objects in the server class list. Server does not include any user-specified services Cause. You attempted to generate a server that does not contain any custom services. Issued by the Pathmaker product and by PMADL. Effect. Server generation fails. Recovery.
Pathmaker Messages Server name required — please enter name Cause. You attempted to add a server but omitted the server name. Issued by the Pathmaker product. Effect. Add fails. Recovery. Enter a server name to continue. Server not found Cause. You searched for a server that does not exist in the project catalog. No other server follows the server name that you specified. Issued by the Pathmaker product. Effect. None. Recovery.
Pathmaker Messages Service — service-name is not yet implemented. Cause. Either the service did not exist when you generated the requester, or the server for the service has not yet been created. Requester error issued by the generated application. Effect. SEND fails. Recovery. If you generated the requester before generating the service, re-create the requester. Otherwise, create the server for the service and generate the mapping requester. Service already exists — cannot add Cause.
Pathmaker Messages Service is not of type custom: service-name Cause. A registered service cannot be generated because it is not a custom service. Effect. Server or service generation fails. Recovery. Change the service to a custom service or do not generate it. Service Logic Error Cause. An invalid value has been moved to T9154-REPLY-FLAG in your Procedure Division. Server error issued by the generated application. Effect. This advisory message is displayed. Recovery.
Pathmaker Messages Service name required — please enter name Cause. You attempted to add a service but omitted the service name. Issued by the Pathmaker product. Effect. Add fails. Recovery. Enter a service name to continue. Service not defined: service-name Cause. You attempted to add a service that does not exist to the service assignment list. Issued by the Pathmaker product. Effect. Update fails. Recovery. Correct the service name or define the service on the Service Definition screen.
Pathmaker Messages Service specifies the wrong language: service-name Cause. The language of the service must match the language of the server. Effect. Server generation fails. Recovery. Code either the server or the service in a different language. Setmode error on terminal — new-process Cause. An error occured while reading the block mode status of the terminal. Issued by the Pathmaker product. Effect. New process startup fails. Recovery.
Pathmaker Messages Skel-Badly nested command scopes: file name.line number Cause. The macro language processor encountered two scoped commands ( IF or ITERATE) that have scopes that intersect, but are not nested. The second command starts in the scope of the first command but ends outside the scope of the first command. Issued by the Pathmaker product. Effect. Generation fails. Recovery. Change the end-if or end-iterate to be nested and regenerate. Skel-Buffer overflow: file name.line number Cause.
Pathmaker Messages Skeleton file error file-error-num Cause. Pathmaker encountered a file system error while trying to open the skeleton file. Issued by the Pathmaker product. Effect. Requester or server generation fails. Recovery. For further information on the specific file error you encountered, refer to the Guardian Procedure Errors and Messages Manual. Skeleton file not consistent with language of server or service. Cause. The wrong skeleton file was specified. Issued by the Pathmaker product.
Pathmaker Messages Skel-Illegal Section Name: file name.line number Cause. The macro language processor encountered a section or macro name that does not follow the naming rules. Issued by the Pathmaker product. Effect. Generation fails. Recovery. Correct the name and regenerate. Skel-Illegal Syntax: file name.line number Cause. The macro language processor encountered a word it did not recognize. Issued by the Pathmaker product. Effect. Generation fails. Recovery.
Pathmaker Messages Skel-Macro not found: file name.line number Cause. The macro language processor encountered a reference to a macro that does not exist. Issued by the Pathmaker product. Effect. Generation fails. Recovery. Either register the macro on the Pathmaker macro registration screen, or specify the location of the macro. Skel-Missing end label: file name.line number Cause. The macro language processor could not find the terminating label. Issued by the Pathmaker product. Effect. Generation fails.
Pathmaker Messages Skel-Nesting of statements is too deep: file name.line number Cause. The macro language processor encountered too many IF statements nested within IF statements. Issued by the Pathmaker product. Effect. Generation fails. Recovery. Reduce the nesting depth and regenerate. Skel-No context for construct: file name.line number Cause. The macro language processor encountered a construct for which the correct context has not been defined.
Pathmaker Messages Skel-String encountered in expression: file name.line number Cause. The macro language processor encountered an identifier containing a string value in an arithmetic expression. Issued by the Pathmaker product. Effect. Generation fails. Recovery. Remove the string value from the arithmetic expression and regenerate. Skel-Too many nested INVOKE statements: file name.line number Cause. The macro language processor encountered too many INVOKE statements nested within INVOKE statements.
Pathmaker Messages Skel-Variable is not defined: file name.line number Cause. The macro language processor encountered a reference to a variable that has not been defined. Effect. Generation fails. Recovery. Define the variable or correct the reference to the non-existant variable. Software distribution subvolume is a PATHMAKER installation Cause. You specified the CLEANUP option in a PMINSTAL INITIAL or REDEFINE operation, but the source subvolume is a PATHMAKER installation subvolume.
Pathmaker Messages Source device is not an available disk volume — volume name Cause. The source device name you supplied to the PMPROJECT IMPORT command did not indicate a disk volume. The IMPORT command can only import a catalog residing on disk. Issued by PMPROJECT. Effect. Operation canceled. Recovery. Correct the volume name. Source file error file-error-num Cause. Pathmaker encountered a file system error while trying to create or open the source file. Issued by the Pathmaker product. Effect.
Pathmaker Messages Source volume resides on a remote system — subvolume Cause. You attempted to import a Pathmaker project catalog that resides on a remote system. All Pathmaker projects that are defined on a system must have catalogs that reside on that system. Issued by PMPROJECT. Effect. Operation canceled. Recovery. Transfer the catalog files to the local system, or run the PMPROJECT IMPORT command on the remote system. Specified Access Path not found Cause.
Pathmaker Messages Specified requester not found: name Cause. You attempted to generate a requester or simulate a CALL to a requester, but the requester does not exist in the project catalog. Issued by the Pathmaker product. Effect. No operation occurs. Recovery. Define the requester or change the function key action and retry the operation. Specified service not found: service-name Cause. You specified a service that has since been deleted from the project.
Pathmaker Messages SQL error error-num on table file-name Cause. An operation caused an SQL error. Issued by the generated application. Effect. Operation fails. Recovery. Use the ERROR command in SQLCI, or refer to the SQL Messages Manual to find out what the error is and how to recover. Also, see Section 8 of the Pathmaker Programming Manual for a list of common SQL errors. SQL IO Section name is a COBOL reserved word Cause. COBOL reserved words cannot be used as SQL IO section names. Effect.
Pathmaker Messages SQL table name required — please enter name Cause. You must enter an SQL table name on the SQL Table Registration screen. Issued by the Pathmaker product. Effect. Update fails. Recovery. Enter an SQL table name and retry the update. SQL TABLE not found: SQL-table-name Cause. You searched for a NonStop SQL table that does not exist in the current catalog. Issued by the Pathmaker product. Effect. Search fails. Recovery. Check the spelling of the table name.
Pathmaker Messages Standard Server version mismatch Cause. The DB requester was generated under a version of Pathmaker that is incompatible with the Pathmaker standard server currently being used. Issued by the generated application. Effect. The DB requester being executed cannot access its database files. Recovery. Generate the requester using the Pathmaker version that matches the Pathmaker standard server currently being used.
Pathmaker Messages Subvolume name is not properly qualified — subvolume Cause. You specified a partially qualified subvolume name in the installation configuration file supplied to PMINSTAL. Issued by PMINSTAL. Effect. The illegal subvolume name was ignored. PMINSTAL terminated after reading the installation configuration file. Recovery. Correct the installation configuration file. Syntax error (explanation) Cause. You supplied a command containing a syntax error to PMPROJECT or PMINSTAL.
Pathmaker Messages Syntax error in command Cause. A syntax error was detected in the command string supplied to HELPUTIL. Issued by HELPUTIL. Effect. The program terminates. Recovery. Correct the command. The syntax for HELPUTIL is described in the Pathmaker Reference Manual. Syntax error in field name: field-name Cause. You entered a qualified field name incorrectly. Issued by the Pathmaker product. Effect. Operation fails. Recovery. Enter the qualified field name again and retry the operation.
Pathmaker Messages Syntax error in requester name Cause. A requester name has invalid syntax or is too long. Issued by HELPUTIL. Effect. If the name occurs in an EXTRACT command, the program terminates. If the name occurs in an UPDATE source file directive, the directive is ignored and the current requester is not updated. Recovery. Correct the requester name and retry the operation. Syntax error in screen field name Cause. A screen field name has invalid syntax or is too long. Issued by HELPUTIL. Effect.
Pathmaker Messages Syntax error in text file directive Cause. A syntax error was detected in a help directive in the help file. The help file is an EDIT file containing help directives and help text; HELPUTIL uses the help file to update the help database. Issued by HELPUTIL. Effect. The directive is ignored and the current requester is not updated. Recovery. Correct the help directive.
Pathmaker Messages System incorrectly installed. Failed to find ACTIVE record. Cause. The Pathmaker program could not find a record describing the current user in the Pathmaker active terminal file, $SYSTEM.PATHMAKR.ACTIVE. Issued by The Pathmaker program. Effect. Server generation fails. Recovery. Note this error message and contact your Tandem representative. Table dimensions conflict with the reference field — field deleted Cause.
Pathmaker Messages Table extends beyond the right edge of the screen Cause. You attempted to move a table so that the table would extend beyond the right edge of the screen, or you defined the columns for a table so that the table would extend beyond the right edge of the screen. Issued by the Pathmaker product and by PMADL. Effect. Operation canceled. Recovery. Reduce the number of columns, or the column separation, in the table or choose a new starting location.
Pathmaker Messages Table object name is a DDL definition: invalid-name Cause. You entered a DDL definition in the SQL Table Registration screen when you should have entered an SQL table object name. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Enter an SQL table object name and retry the update. Table object name is a DDL record: invalid-name Cause. You entered a DDL record in the SQL table object field in the SQL Table Registration screen.
Pathmaker Messages Table object name is a service: invalid-name Cause. You entered a service name in the SQL Table object field in the SQL Table Registration screen. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Enter an SQL table object name and retry the update. Table/requester mismatch on define define-name, regenerate Cause. The table referred to by the define-name does not agree with the table specified when you generated the requester.
Pathmaker Messages Target device is not an available disk volume — volume name Cause. The target device name you supplied to the PMPROJECT EXPORT command did not indicate a disk volume. The EXPORT command can only export a catalog to a disk volume. Issued by PMPROJECT. Effect. Operation canceled. Recovery. Correct the target device name. Term I/O error; Error = file-error-code Cause. A file system error occurred while attempting an I/O to a terminal. CALL error issued by the generated application.
Pathmaker Messages The default value is too large for the SCOBOL item: item name Cause. The default value specified in the SQL table description is too large to fit in the Screen COBOL working storage item. Issued by the Pathmaker product. Effect. Requester generation fails. Recovery. Change the default value for the column to be within the range of the Screen COBOL item. The advisory field may not be modified or deleted Cause. You attempted to modify or delete the @ADVISORY pseudofield.
Pathmaker Messages The starting and ending locations must be on the same line Cause. You attempted to apply a video attribute to an area that includes more than one line. Issued by the Pathmaker product. Effect. Operation canceled. Recovery. Apply the video attribute to each line separately. There are no changes to undo Cause. You pressed the Undo function key, but have not yet made changes to undo during this Screen Painter session. Issued by the Pathmaker product. Effect. Operation canceled. Recovery.
Pathmaker Messages This field must contain a legal name Cause. You attempted to enter an invalid point field name. Issued by the Pathmaker product. Effect. The Screen Painter did not add or modify the point field. Recovery. Enter a valid point field name. Point field names can be from 1 to 30 alphanumeric or hyphen (-) characters, excluding all other special characters such as pound sign (#) and dollar sign ($). A point field name must begin with a letter and cannot end with a hyphen.
Pathmaker Messages This field must contain an unsigned number, or blanks Cause. You entered an invalid value into a field, such as Column Separation, that requires an unsigned number or blanks. Issued by the Pathmaker product. Effect. The Screen Painter does not add or modify the data field. Recovery. Correct the indicated field. This field must contain “Y or “N Cause. You entered a value other than Y or N into a field that can only accept one of these two values.
Pathmaker Messages This version of the catalog is not supported Cause. You attempted to access a version of the catalog that is not supported by the current version of Pathmaker. Issued by the Pathmaker product. Effect. Screen Painter startup fails. Recovery. Ensure that the project configuration designates the correct location of the catalog, and ensure that the catalog is valid. TMF is not configured; In called-program Cause. There is a BEGIN-TRANSACTION but the TMF software is not on the system.
Pathmaker Messages TMF not started Cause. There is a BEGIN-TRANSACTION but the TMF software is not installed or active on the system. TMF error issued by the generated application. Effect. SEND fails. Recovery. Contact your system administrator about restarting TMF. TMF transaction restarted Cause. The current server process has been stopped; the TMF software restarted the process. Issued by the Pathmaker product and by the generated application. Effect. Data remains intact. Recovery.
Pathmaker Messages TO requester name is a SCOBOL reserved word — please reenter Cause. You entered a requester name in the Copy To field that is a Screen COBOL reserved word. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Enter a requester name and retry the operation. TO requester name required — please enter name Cause. You attempted to copy a requester without specifying the name of the requester that you want it copied to. Issued by the Pathmaker product. Effect. Copy fails. Recovery.
Pathmaker Messages TO server name required — please enter name Cause. You must enter a server name in the Copy To field. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Enter a server name and retry the operation. TO service already exists — cannot copy Cause. You entered a service name in the Copy To field that already exists. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Enter a service name and retry the operation. TO service name cannot begin with T9154 prefix Cause.
Pathmaker Messages TO service name required — please enter name Cause. You did not enter a service name in the Copy To field. Issued by the Pathmaker product. Effect. Copy fails. Recovery. Enter a service name and retry the operation. Too many display field list entries — contact support Cause. You specified more than 700 elementary items in the Display Field List for this reference object. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery.
Pathmaker Messages Too many reply elements are defined in this service Cause. A service object description specifies more than 40 reply IPC elements. Issued by PMADL. Effect. The service description is not stored in the catalog. Recovery. Reduce the number of reply elements in the service. Too many request elements are defined in this service Cause. A service object desciption specifies more than 40 request IPC elements. Issued by PMADL. Effect. The service description is not stored in the catalog.
Pathmaker Messages Too many SQL Table DEFINEs were specified Cause. You supplied too many DEFINEs to the SQL standard server. Issued by the generated application. Effect. The SQL standard server will not run. Recovery. You can either reduce the number of DEFINEs the SQL standard server receives, by reducing the number of tables it must access, or you can change the Pathway parameter that sets the maximum number of DEFINEs. If this problem persists, contact your Tandem representative.
Pathmaker Messages Transaction send failure; In called-program Cause. CALL error issued by the generated application. Effect. The CALL fails. Recovery. The underlying TMF system could not send the TRNS-ID message; refer to the TMF Reference Manual for details about the TMF software. Transaction started or restarted Cause. The operation is either being started or restarted. TMF error issued by the generated application. Effect. This is an advisory message. Recovery. No recovery is required.
Pathmaker Messages Unable to access Macro source file. Error code = nn Cause. The source file associated with a macro could not be accessed. The specific file system error is indicated by the error code nn. Effect. Operation fails. Recovery. Correct the error and repeat the operation. Macro section not found in source file. Cause. The source file associated with macro did not contain a ?SECTION command for this macro. Effect. Operation fails. Recovery.
Pathmaker Messages Unable to allocate memory for secondary input or output file Cause. PMADL could not open a secondary input file specified in a ?SOURCE command, or a secondary output file specified in a ?OUT or ?ADLOUT command, because no memory was available for file control blocks and buffers. PMADL can have up to 12 primary and secondary input and output files open concurrently. Effect. The specified input or output file is not opened.
Pathmaker Messages Unable to configure remote program file — please reenter Cause. You specified a remote program file in the Process Configuration screen. Issued by the Pathmaker product and by PMADL. Effect. Update fails. Recovery. Enter a local system program file name and retry the update. Unable to delete ACTIVE record, error: error code Cause.
Pathmaker Messages Unable to get user's ID Cause. The USERIDTOUSERNAME procedure returned an error when Pathmaker attempted to convert the process access user id to a user name. Issued by the Pathmaker product. Effect. Pathmaker startup fails. Recovery. Contact your system manager. Unable to locate catalog file: file-name Cause.
Pathmaker Messages Unable to locate FROM copy library: file-name Cause. During the copy operation, Pathmaker could not perform the COBOL dynamic ASSIGN statements against the copy library associated with the FROM requester or the transaction library associated with the FROM service. Issued by the Pathmaker product. Effect. Copy fails. Recovery. The copy library might have been purged by someone. Do not copy the library (blank out the name on the screen).
Pathmaker Messages Unable to open DICTNPC file, error: error code Cause. Pathmaker encountered a file system error when attempting to open the DICTNPC file in the project catalog subvolume. Issued by the Pathmaker product. Effect. Pathmaker startup fails. Recovery. Correct the condition indicated by the error. If necessary, contact the owner of the project or your system manager. Unable to open PATHMON process, error: error code Cause.
Pathmaker Messages Unable to open terminal — new-process Cause. The terminal cannot be opened by the new process server while placing it in conversational mode. Issued by the Pathmaker product. Effect. New process startup fails. Recovery. Contact your system manager. Unable to read ACTIVE file, error: error code Cause. Pathmaker encountered a file system error while reading the ACTIVE file in the Pathmaker installation subvolume. Issued by the Pathmaker product. Effect. Pathmaker startup fails. Recovery.
Pathmaker Messages Unable to read PROJECTS file, error: error code Cause. Pathmaker encountered a file system error while reading the PROJECTS file in the Pathmaker installation subvolume. Issued by the Pathmaker product. Effect. Pathmaker startup fails. Recovery. Correct the condition indicated by the error. If necessary, contact your system manager. Unable to read records from temporary file — contact support Cause.
Pathmaker Messages Unable to select FILLER, LEVEL-88, or redefined field Cause. You attempted to select and return FILLER, LEVEL-88, or redefined field from the Reference Field Value List screen. Issued by the Pathmaker product. Effect. Select fails. Recovery. Choose another field to select and return. Unable to send startup message — new-process Cause. The named process will not accept the startup message. Issued by the Pathmaker product. Effect. The process abended because of CPU or program failure.
Pathmaker Messages Unable to update ACTIVE file, error: error Cause. The active terminal file must keep track of the processes open by this user. The file cannot be updated so the new process has been abended. Issued by the Pathmaker product. Effect. New process startup fails. Recovery. Check the security of $SYSTEM.PATHMAKR.ACTIVE or ACTIVE0. Unable to write ACTIVE record, error: error code Cause.
Pathmaker Messages Unaudited catalogs cannot be opened for read/write access Cause. You attempted to open a Pathmaker catalog for read-write access, but the catalog is not audited by the TMF software. The Pathmaker program requires that catalogs which may be updated be audited by the TMF software. Issued by PMADL. Effect. The previously opened catalog, if any, is closed and no new catalog is opened. Recovery. Alter the catalog files using the FUP ALTER command to enable TMF auditing.
Pathmaker Messages Undefined Server class; Send to server-class Cause. The request to PATHMON for a link to the server class has been denied because no class of that name has been defined. SEND error issued by the generated application. Effect. Operation canceled. Recovery. Add server class in Pathmaker user interface and reinstall project. Undefined system; Send to server-class Cause. A remote SEND has an undefined system name. SEND error issued by the generated application. Effect. SEND fails. Recovery.
Pathmaker Messages Unexpected ALTFILE name in catalog file — file-name Cause. The catalog you specified in a ?CATALOG or ?PROJECT command includes a file, indicated by the file-name, which does not refer to the appropriate alternate key file. This error may occur if the catalog was copied or renamed from a different location and its alternate key file names were not updated to reflect the new location. Issued by PMADL. Effect. The previously opened catalog, if any, is closed and no new catalog is opened.
Pathmaker Messages Unique key field is not on screen:qualified-field-name Cause. You specified that a unique key for this DB requester should not be displayed on the application screen; a unique key is either a primary key or a unique alternate key. The database service Insert is enabled. Issued by the Pathmaker product and by PMADL. Effect. Requester generation fails. Recovery.
Pathmaker Messages Unknown error # number internal error — Exception number Cause. The simulation server detected an unexpected condition. Issued by the Pathmaker product. Effect. Simulation fails. Recovery. Note this error message and contact your Tandem representative. Unknown FUNCTION-CODE. Cause. Modifications to either the Screen COBOL skeleton or the Screen COBOL source code have resulted in a FUNCTION-CODE that is unknown to the standard server. Issued by the generated application. Effect.
Pathmaker Messages Unsupported object version: SQL-table name Cause. You requested an SQL table or view with a version number greater than the currently supported version. Issued by the generated application. Effect. Table or view access fails. Recovery. Preferably, do not access that table or view. However, if you must access the table or view, first install a later version of the Pathmaker product. Unsupported Pathmaker catalog version — file name Cause.
Pathmaker Messages Unsupported SQL version of SQL Table — file name Cause. You attempted to reference an SQL Table, indicated by the file name, which uses a later version of SQL than the version supported by the Pathmaker product. Issued by PMADL. Effect. The current PMADL operation is canceled. Any changes made to the current catalog by the operation are backed out. Recovery. Use a later version of the Pathmaker product to reference the SQL Table. Unsupported terminal type: type code Cause.
Pathmaker Messages Unsupported version of the catalog: file name Cause. The simulation server accessed a version of the Pathmaker project catalog that it did not recognize. Issued by the Pathmaker product. Effect. Simulation fails. Recovery. Convert the project catalog to a version that is compatible with your Pathmaker software. Update conflict. Record has been reread Cause. You tried to update a record that has been modified by some other application since you last read it.
Pathmaker Messages Update fails. File error code = error-code Cause. A data file operation error was reported by the file system. Issued by the generated application. Effect. The update did not occur. Recovery. Consult the Guardian Procedure Errors and Messages Manual for interpretation of the error code. Update fails. INSERT OK, but DELETE on old image fails. Cause. File operation error. Issued by the generated application. Effect.
Pathmaker Messages Update function not allowed — default screen creation has been disabled Cause. You attempted to add a new entry in the Display Field List screen. Issued by the Pathmaker product. Effect. Update fails. Recovery. No new fields can be added after the screen has been modified. Update service enabled but no update action defined Cause. You attempted to enable the database service, UPDATE, for a DB requester but do not have a function key specified to invoke the service.
Pathmaker Messages Use SF2 again to confirm delete; ref object is a CALL/SEND parameter Cause. Confirmation message. See recovery. Issued by the Pathmaker product. Effect. Unless further action is taken, the delete will abort. Recovery. You must press SF2 again on the Requester Context screen to delete the reference object as well as the associated CALL/SEND parameter. Use SF2 again to confirm delete; ref object is a requester parameter Cause. Confirmation message. See Recovery.
Pathmaker Messages User's project not found Cause. The Pathmaker program did not find your project in the PROJECTS file. This is an internal error unless you deleted the project name record from the file. Issued by the Pathmaker product. Effect. Pathmaker startup fails. Recovery. Note this error message and contact your Tandem representative. Utility process running from previous session Cause.
Pathmaker Messages Value too large; Desc # = descriptor-num In called-program Cause. An arithmetic calculation or MOVE placed an invalid numeric in a numeric variable. CALL error issued by the generated application. Effect. CALL fails. Recovery. Check custom code for invalid data movement. Desc NUM is available in the compiler listing if ?SMAP is specified. Values must not be changed prior to DELETE. Cause. File operation error issued by the generated application. Effect. Delete operation fails.
Pathmaker Messages Wrong version of SCREEN COBOL skeleton Cause. You attempted to generate this requester with an incompatible version of the requester skeleton. Issued by the Pathmaker product. Effect. Requester generation fails. Recovery. Change the file name of the skeleton on the Requester Generation Data screen to a current version of the requester skeleton.
