gtpm5m2dMessages (Online)

RFPC-ROUT

RFPC0001I-- STARTED RECONCILIATION OF SON POOL COUNTS

Explanation: This is a normal response to the ZRFPC command after an entry into DYDC.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRFPC command.

RFPC0002I-- END OF JOB OF SON POOL RECONCILIATION

Explanation: This is a normal response to the ZRFPC command.

System Action: The reconciliation of the file pool directories completed successfully.

User Response: None.

See TPF Operations for more information about the ZRFPC command.

RFPC0003T-- KEYPOINT 9 FIND ERROR, JOB CANCELLED

Explanation: This is the response to the ZRFPC command when segment DYDC or DYDL is unable to retrieve keypoint 9.

System Action: If reconcile was being run while the TPF system was in 1052 state, segment DYDC was unable to retrieve keypoint 9. Reconcile was canceled, and the pool counts and shutdown and reorder indicators were not updated for any pool section.

If reconcile was being run while the TPF system was in NORM state, segment DYDL was unable to retrieve keypoint 9. Segment DYDL ends and the pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 for the long-term pool section that was being processed by DYDL are not updated. Reconcile processing for all other pool sections proceeds normally.

User Response: Do the following:

  1. Determine why keypoint 9 was not available.
  2. Correct the error.
  3. Enter the ZRFPC command again.

See TPF Operations for more information about the ZRFPC command.

RFPC0004T-- KEYPOINT 9 FILE ERROR, JOB TERMINATED ABNORMALLY

Explanation: This is a response to the ZRFPC command when segment DYDC or DYDL is unable to file keypoint 9.

System Action: If reconcile was being run while the TPF system was in 1052 state, segment DYDC was unable to file keypoint 9 and reconcile was canceled. The pool counts and shutdown and reorder indicators were not updated for any pool section.

If reconcile was being run while the TPF system was in NORM state, segment DYDL was unable to file keypoint 9 and segment DYDL ends. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 for the long-term pool section that was being processed by DYDL are not updated. Reconcile processing for all other pool sections proceeds normally.

User Response: Do the following:

  1. Correct the error.
  2. Enter the ZRFPC command again.

See TPF Operations for more information about the ZRFPC command.

RFPC0005W-- DIRECTORY dirname FIND ERROR

Where:

dirname
The name of the directory.

Explanation: This message is issued when the directory referenced in the message could not be retrieved. This message is a warning that the directory's counts will not be included in the section's total count. If this directory is subsequently made available the section counts will be adversely and incorrectly affected.

The possible causes of the error are:

System Action: None.

User Response: Do the following:

  1. Determine the reason for the lack of availability.
  2. Correct the error, if possible.
  3. Run the reconcile again.

See TPF Operations for more information about the ZRFPC command.

RFPC0007T-- MASTER CONTROL RECORD record FIND FAILED, JOB TERMINATED

Where:

record
The ordinal number of the master control record.

Explanation: This message is issued when a short-term master control header record could not be retrieved during processing in DYDS for that section.

System Action: The reconcile for the short-term pool section represented by this master control record is canceled. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 (CTK9) are not updated for this section. The reconcile for all other pool sections proceeds normally.

User Response: Do the following:

  1. Correct the error.
  2. Run the reconcile again.

See TPF Operations for more information about the ZRFPC command.

RFPC0008T-- MASTER CONTROL RECORD record FILE FAILED, JOB TERMINATED

Where:

record
The ordinal number of the master control record.

Explanation: This message is issued when a short-term master control header record could not be filed during processing in DYDS for that section.

System Action: The reconcile for the short-term pool section represented by this master control record is canceled. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 (CTK9) are not updated for this section. The reconcile for all other pool sections proceeds normally.

User Response: Do the following:

  1. Correct the error.
  2. Run the reconcile again.

It is possible that the TPF system may not cycle up to NORM state because of the configuration that is not valid. In addition, counts for this section may not reflect the sum of the individual directory's counts.

See TPF Operations for more information about the ZRFPC command.

RFPC0009T-- SUBRECORDS UNAVAILABLE FOR pooltype ON devicetype, JOB TERMINATED

Where:

pooltype
The pool type.

devicetype
The device type.

Explanation: This message is issued when subrecords for the short-term master control record or the short-term processor control record could not be retrieved for the pool type and the device type referenced in the message.

System Action: The reconcile for the short-term pool section referenced in this message is canceled. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 (CTK9) are not updated for this section. The reconcile for all other pool sections proceeds normally.

User Response: Do the following:

  1. Correct the error.
  2. Run the reconcile again.

See TPF Operations for more information about the ZRFPC command.

RFPC0010T-- SUBRECORD FILE FAILED FOR pooltype ON devicetype, JOB TERMINATED

Where:

pooltype
The pool type.

devicetype
The device type.

Explanation: This message is issued when the subrecords for the short-term master control record or the short-term processor control record could not be filed for the pool type and device type referenced in the message.

System Action: The reconcile for the short-term pool section referenced in this message is canceled. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 (CTK9) are not updated for this section. The reconcile for all other pool sections proceeds normally.

User Response: Do the following:

  1. Correct the error.
  2. Run the reconcile again.

See TPF Operations for more information about the ZRFPC command.

RFPC0011W-- DIRECTORY dirname FILE FAILED

Where:

dirname
The name of the directory.

Explanation: This message is issued when the directory referenced in the message could not be filed. This message is warning that its counts will not be included in the section's total count. If this directory is subsequently made available the section counts will be adversely and incorrectly affected.

System Action: None.

User Response: Do the following:

  1. Determine the reason for the failure.
  2. Correct the error, if possible.
  3. Run reconcile again.

See TPF Operations for more information about the ZRFPC command.

RFPC0012T--INVALID TIMESTAMPS EXIST FOR pooltype ON devicetype, JOB TERMINATED

Where:

pooltype
The pool type.

devicetype
The device type.

Explanation: A test was provided to determine whether all the directory ordinals that should be present in a short-term section master control record are present. This test is a check-summing of the ordinal numbers from the first (CY2FDR) to the last (CY2LDR). When each individual time stamp is processed, a running check sum is kept. When the section processing is completed, these two check sums (running and computed) are compared. If they are not equal, this error message is displayed.

System Action: The reconcile for the short-term pool section referenced in this message is canceled. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 (CTK9) are not updated for this section. The reconcile for all other pool sections proceeds normally.

User Response: Do the following:

  1. Determine the cause for the error. The most likely cause of the error is that there is the same directory ordinal on more than one time stamp record and one or more is missing. You may need to work with your system programmer to identify these and to correct the ordinal numbers.
  2. Correct the error, if possible.
  3. Run the reconcile again to recompute the counts.

See TPF Operations for more information about the ZRFPC command.

RFPC0014T-- DUPLICATE TIMESTAMPS FOUND FOR pooltype ON devicetype, JOB TERMINATED

Where:

pooltype
The pool type.

devicetype
The device type.

Explanation: After a short-term section has been processed, the number of directories processed is compared to the generated number. If the number of directories is greater than the generated number, this error message is issued for the pool type and device shown in the message. The most probable cause is that there are one or more duplicate time-stamp entries, representing the same short-term pool directory.

System Action: The reconcile for the short-term pool section referenced in this message is canceled. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 (CTK9) are not updated for this section. The reconcile for all other pool sections proceeds normally.

User Response: Do the following:

  1. Review the short-term master control record to identify the duplicate directories.
  2. Delete the duplicate entries and reset the pointers.
  3. Run the reconcile again to recalculate the counts.

See TPF Operations for more information about the ZRFPC command.

RFPC0015T-- TIMESTAMPS LOST FOR pooltype ON devicetype, JOB TERMINATED

Where:

pooltype
The pool type.

devicetype
The device type.

Explanation: After a short-term section has been processed the number of directories processed is compared to the generated number. If the number of directories is less than the generated number this error message is issued for the pool type and device shown in the message.

The most probable cause is that the number of time stamps in the directory does not match the number generated, indicating that time stamps have been lost.

System Action: Reconcile for the short-term pool section referenced in this message is cancelled. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 are not updated for this section. Reconcile for all other pool sections proceeds normally.

User Response: Do the following:

  1. Review the short term master control record to identify the lost directories.
  2. Include the lost directories and reset the pointers.
  3. Run the reconcile again to recompute the counts.

See TPF Operations for more information about the ZRFPC command.

RFPC0016W-- DIRECTORY dirname HAS AN INVALID CHECK SUM

Where:

dirname
The name of the directory.

Explanation: This message is issued when the DYDQ calculated check sum does not match that in the check sum field of the directory. It is marked as unowned, with controls that are not valid, and it is not counted.

System Action: None.

User Response: Run a recoup or a directory update.

See TPF Operations for more information about the ZRFPC command.

RFPC0018W-- DIRECTORY dirname HAS INVALID CONTROLS

Where:

dirname
The name of the directory.

Explanation: This message is issued when DYDQ finds that directory referenced in the message is marked with controls that are not valid. This directory is not counted.

System Action: None.

User Response: Run a recoup or a directory update.

See TPF Operations for more information about the ZRFPC command.

RFPC0019T-- INVALID SHUT DOWN CONFIGURATION, FOR pooltype ON devicetype, JOB TERMINATED

Where:

pooltype
The pool type.

devicetype
The device type.

Explanation: This is the response to the ZRFPC command when the configuration table in segment DYDS does not match the values in the CY$RSx, ICY$RSN, CY1SHT, and CY1REO fields. This usually indicates a condition that reconcile would handle incorrectly if it were to continue. A 000697 system error dump is issued to display the problem areas and help correct the error. The following are possible causes:

System Action: A system error dump occurs and the ECB exits. Reconcile processing for the short-term pool section referenced in the message is ended. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 (CTK9) are not updated for the pool section. Reconcile processing for all other pool sections proceeds normally.

User Response: Do the following:

  1. Determine the cause of the error.
  2. Correct the error.
  3. Enter the ZRFPC command again.

See TPF Operations for more information about the ZRFPC command.

RFPC0021T-- POOL KEYPOINT TABLE record FIND FAILED

Where:

record
The ordinal of the fixed file copy of the pool keypoint table (CY2KT).

Explanation: This message is issued when segment DYDL is unable to find the fixed file copy of the pool keypoint table (CY2KT).

System Action: Reconcile processing for the long-term pool section represented by the pool keypoint table (CY2KT) ends. The pool count in CY2KT and the shutdown and reorder indicators in keypoint 9 are not updated for this pool section. Reconcile processing for all other pool sections proceeds normally.

User Response: Do the following:

  1. Determine why the fixed file copy of CY2KT was not available.
  2. Correct the error.
  3. Enter the ZRFPC command again.

See TPF Operations for more information about the ZRFPC command.

RFPC0022T-- PROCESSOR CONTROL RECORD record FOR PROC proc FIND FAILED

Where:

record
The record ordinal of the processor control record.

proc
The processor ID of the processor represented by the failing processor control record.

Explanation: This message is issued when segment DYDS is unable to find the short-term processor control record.

System Action: Reconcile processing for the short-term pool section represented by the processor control record ends. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 are not updated for this pool section. Reconcile processing for all other pool sections proceeds normally.

User Response: Do the following:

  1. Determine why the short-term processor control record was not available.
  2. Correct the error.
  3. Enter the ZRFPC command again.

See TPF Operations for more information about the ZRFPC command.

RFPC0023T-- PROCESSOR CONTROL RECORD record FOR PROC proc FILE FAILED

Where:

record
The ordinal of the processor control record.

proc
The processor ID of the processor represented by the failing processor control record.

Explanation: This message is issued when segment DYDS is unable to file a short-term processor control header.

System Action: Reconcile processing for the short-term pool section represented by the processor control record ends. The pool count in the pool keypoint table (CY2KT) and the shutdown and reorder indicators in keypoint 9 are not updated for this pool section. Reconcile processing for all other pool sections proceeds normally.

User Response: Do the following:

  1. Correct the error.
  2. Enter the ZRFPC command again.

See TPF Operations for more information about the ZRFPC command.

RFPC0128T-- EVENT TIMEOUT WAITING FOR RECONCILE OF pooltype ON devtype, JOB TERMINATING

Where:

pooltype
The type of pool file.

devtype
The type of the device.

Explanation: The ZRFPC command was entered but reconciliation processing timed out.

System Action: The command fails.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRFPC command again.

See TPF Operations for more information about the ZRFPC command.

RFPC0255T- TERMINAL ERRORS - RECONCILE JOB TERMINATED

Explanation: The ZRFPC command was entered but errors ocurred that caused reconciliation processing to fail.

System Action: The command fails.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRFPC command again.

See TPF Operations for more information about the ZRFPC command.

RHLD0000ILOCK DELETIONS COMPLETE

Explanation: This is the normal response to the ZRHLD DELETE command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRHLD DELETE command.

RHLD0001ILOCK DISPLAY COMPLETE

Explanation: This is the normal response at the end of the display generated by the ZRHLD DISPLAY command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRHLD DISPLAY command.

RHLD0002IHOLDERS AND WAITERS INFORMATION NOT AVAILABLE

Explanation: This message is issued when the TPF system is unable to display the holders and waiters information returned because the TPF system has not cycled high enough to fill in the PI1DT table.

System Action: None.

User Response: None.

RHLD0003EPROCESSOR SPECIFICATION NOT IN PIDT

Explanation: The command contains an incorrect processor specification. It does not match any processor known in the processor table (PIDT).

System Action: None.

User Response: Enter the command again and specify a valid CPU ID.

See TPF Operations for more information about the ZRHLD DISPLAY command.

RHLD0005ESPECIFIED PROCESSOR HAS NO LOCK ID IN PIDT

Explanation: The processor specification that is given by the CPU ID in the command is not valid because no corresponding lock ID exists in the processor table (PIDT).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRHLD DISPLAY command.

RHLD0006ESPECIFIED CONTROL UNIT OUTSIDE LEGAL DEVICE LIMITS

Explanation: The specified device is greater than the highest device address found at IPL time.

System Action: None.

User Response: Enter the command again and specify a valid device address.

See TPF Operations for more information about the ZRHLD commands.

RHLD0007ESPECIFIED CONTROL UNIT IS INACTIVE.

Explanation: The control unit specified in the ZRHLD command is not presently active.

System Action: None.

User Response: Do the following:

  1. Determine that the control unit is active.
  2. Enter the command again.

See TPF Operations for more information about the ZRHLD commands.

RHLD0008ESONIC RETURNED SPECIFIED FILE ADR AS INVALID

Explanation: The specified file address is not valid.

System Action: None.

User Response: Enter the command again and specify a valid file address.

See TPF Operations for more information about the ZRHLD commands.

RHLD0009ESPECIFIED FILE ADR CANNOT BE DECODED BY CSONC

Explanation: The specified file address cannot be resolved into a file address for the module.

System Action: None.

User Response: Enter the command again and specify a file address that can be resolved.

See TPF Operations for more information about the ZRHLD commands.

RHLD0010ETHIS FUNCTION IS PERMITTED ONLY IN THE BSS

Explanation: This variation of the ZRHLD command may not be entered except from the basic subsystem (BSS).

System Action: None.

User Response: Enter the command again from the BSS.

See TPF Operations for more information about the ZRHLD commands.

RHLD0011ELOCK HARDWARE NOT INSTALLED

Explanation: The ZRHLD command was entered to display or delete locks but no lock hardware is installed within the processing complex.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRHLD commands.

RHLD0016EI/O ERROR READING LOCKS FROM SDA sda

Where:

sda
The symbolic device address (SDA) that received the input/output (I/O) error.

Explanation: A ZRHLD command was entered to read locks from the displayed SDA but an I/O error occurred.

System Action: None.

User Response: Take the appropriate action to recover from this hardware error.

See TPF Operations for more information about the ZRHLD commands.

RHLD0017EI/O ERROR PURGING LOCK lockname FROM SDA sda

Where:

lockname
The lock name.

sda
The symbolic device address (SDA) that received the input/output (I/O) error.

Explanation: RHLD processing encountered an I/O error while trying to access the device to delete the displayed lock name.

System Action: The command is rejected.

User Response: Using the information the system module support should have displayed on the console, you should take the appropriate action to recover the device.

See TPF Operations for more information about the ZRHLD commands.

RHLD0021ILOCK DELETION COMPLETE, CTL-38 MAY OCCUR

Explanation: This message indicates that the requested delete function was performed successfully. However, it warns that some of the deleted locknames may be owned by active ECBs which, now being deprived of their locknames, may incur unpredictable results in so far as ongoing input/output (I/O), possibly a CTL-38 system error for attempting to unlock a lock just deleted from the control unit.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRHLD commands.

RHLD0022EMODULE CONTAINING REQUESTED FILE ADDRESS NOT ONLINE

Explanation: This message indicates that the specified file address resides on a module that is not online. Therefore, the ZRHLD command is unable to determine which control unit might contain the lock for the specified file address.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRHLD commands.

RHLD0024WECB ecb FORCED TO EXIT DUE TO HOLDING SPECIFIED RECORD

Where:

ecb
The ECB.

Explanation: This message indicates that the requested delete function completed successfully and that the deleted lock name was owned by an active entry control block (ECB) that was forced to exit.

System Action: Processing is continued.

User Response: Check the ECB that was forced to exit.

See TPF Operations for more information about the ZRHLD commands.

RHLD0025ESPECIFIED LOCKS MAY BE FOUND IN COUPLING FACILITY

Explanation: This message indicates that the requested ZRHLD command is referring to a set of locks that are not set in multi-path lock facility (MPLF) or limited lock facility (LLF) control units (CUs). Rather, the set of locks is associated with records residing on a set of modules that use the coupling facility (CF) for external locking.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZCFLK DISPLAY command to determine which modules are using a CF as an external locking device.
  2. Enter the appropriate ZDLCK command to perform actions on the locks associated with the records that reside on these modules.

See TPF Operations for more information about the ZCFLK and ZDLCK commands.

RHLD0026ENO OUTSTANDING DISPLAY TO BE CONTINUED

Explanation: The ZRHLD command was entered to continue a previous lock display but one of the following errors occurred:

System Action: None.

User Response: Check and correct the situations listed in the explanation.

See TPF Operations for more information about the ZRHLD commands.

RHLD0027ISPECIFIED LOCKS NOT FOUND

Explanation: The ZRHLD DELETE or ZDLCK DELETE command was entered to delete a lock, but an error occurred because the lock was not found in the external lock facility (XLF) (either the multi-path lock facility (MPLF) or the coupling facility (CF)).

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZRHLD DELETE and ZDLCK DELETE commands.

RHLD0029ETHE SPECIFIED DEVICE IS NOT ONLINE

Explanation: The device specified on the ZRHLD DISPLAY command with the DEVICE parameter specified is currently not online to the TPF system.

System Action: None.

User Response: Enter the command again and specify an online device.

See TPF Operations for more information about the ZRHLD DISPLAY command.

RHLD0030EINCONSISTENT OPTIONS ON DISPLAY REQUEST, SL/PR/VSYNC

Explanation: The ZRHLD DISPLAY command was entered with the SL, PR, and VSYNC parameters specified. Only one parameter can be specified at a time.

System Action: The command is rejected.

User Response: Do the following:

  1. Determine which parameter is required.
  2. Enter the command again and specify the correct parameter.

See TPF Operations for more information about the ZRHLD DISPLAY command.

RHLD0037ETHE SPECIFIED LOCK NAME IS LESS THAN 16 CHARACTERS IN LENGTH

Explanation: The lock name specified on the ZRHLD command was not valid because the name contained fewer than 16 characters. The lock name must contain at least 16 characters.

System Action: The command is rejected.

User Response: Enter the ZRHLD command again specifying a valid lock name.

See TPF Operations for more information about the ZRHLD command.

RHLD0038ILOCK DELETION COMPLETE, CTL-4627 MAY OCCUR

Explanation: The ZRHLD DELETE command was entered to delete locks from the coupling facility (CF) lock tables.

System Action: The locks are deleted from the CF lock tables.

User Response: None.

See TPF Operations for more information about the ZRHLD DELETE command.

RHLD0040ETHE SPECIFIED FILE ADDRESS IS NOT 16 OR 8 CHARACTERS IN LENGTH

Explanation: The file address specified for a ZRHLD command does not contain 16 or 8 characters. A valid file address must have a length of 16 or 8 characters.

System Action: The command is rejected.

User Response: Enter the ZRHLD command again and specify a file address that contains 16 or 8 characters.

See TPF Operations for more information about the ZRHLD commands.


RHLD0111I

Explanation: This is the normal response to the ZRHLD DISPLAY command. As many as 22 lines of lock table entries are displayed. The text MORE LOCKS LEFT is included in the message when more locks are left to display.

System Action: None.

User Response: If the text MORE LOCKS LEFT is included in the message, enter the ZRHLD DISPLAY command with the CONTINUE parameter specified to continue to the next group.

See TPF Operations for more information about the ZRHLD DISPLAY command.

RIPL0000IZRIPL--OK

Explanation: This is the normal response to the ZRIPL command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRIPL command.

RIPL0009EZRIPL--INVALID PARAMETER

Explanation: A parameter other than BP was specified with the ZRIPL command.

System Action: ZRIPL processing is exited.

User Response: Enter the command again and specify a valid parameter or allow it to default.

See TPF Operations for more information about the ZRIPL command.

RIPL0010EZRIPL--INHIBITED ON LOADER GENERAL FILE

Explanation: The ZRIPL command is not allowed when the last IPL of the TPF system was from the loader general file.

System Action: ZRIPL processing is exited.

User Response: Initiate a hardware IPL if desired.

See TPF Operations for more information about the ZRIPL command.

RIPL0011EZRIPL ALREADY IN PROGRESS

Explanation: A ZRIPL command was entered while another is in progress.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZRIPL command.

RLMT0001IMESSAGE REPEATED TO lniata

Where:

lniata
The line number, interchange address, and terminal address (LNIATA)/logical end -point identifier (LEID).

Explanation: The last message sent to the requested LNIATA/LEID was resent.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRLMT command.

RLMT0003INO MESSAGES ON QUEUE

Explanation: There are no messages on the XLMA queue to purge or repeat.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRLMT command.

RLMT0010WNOT ALLOWED BELOW CRAS STATE

Explanation: The TPF system must be in computer room agent set (CRAS) state or above before the request can be processed. This only applies when the input is a pseudo line number, interchange address, and terminal address (LNIATA).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRLMT command.

RLMT0011EINVALID LNIATA -- lniata

Where:

lniata
The line number, interchange address, and terminal address (LNIATA)/logical end-point identifier (LEID).

Explanation: The LNIATA/LEID specified in the command is not valid or could not be found in the system network tables.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRLMT command.

RLMT0012EINVALID FORMAT

Explanation: The format of the ZRLMT command is not correct or the input line number, interchange address, and terminal address (LNIATA) contains characters that are not valid.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRLMT command.

RLMT0015ENODE NOT A PRINTER

Explanation: The pseudo line number, interchange address, and terminal address (LNIATA) specified in the command is not a printer.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRLMT command.

RLMT0017ENODE UNABLE TO RECEIVE

Explanation: The pseudo line number, interchange address, and terminal address (LNIATA) is in STOP stage.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRLMT command.

RLMT0019TUNABLE TO RETRIEVE XLMA FOR lniata

Explanation: The XLMA record for the requested line number, interchange address, and terminal address (LNIATA) could not retrieved.

System Action: The message queue is not purged and processing is ended.

User Response: None.

See TPF Operations for more information about the ZRLMT command.

ROUT0002EINVALID REQUEST, SYSTEM BELOW 1052 STATE

Explanation: A ZROUT command can only be entered when the TPF system is not below 1052 state.

System Action: The command is rejected.

User Response: Do the following:

  1. Check the state of the TPF system.
  2. Enter the command again.

See TPF Operations for more information about the ZROUT commands.

ROUT0003EAPPLICATION applname NOT IN RCAT

Where:

applname
The name of the application program.

Explanation: The application program name specified in the ZROUT command is not defined in the routing control application table (RCAT).

System Action: None.

User Response: Do the following:

  1. Check the name of the application program.
  2. Enter the command again.

See TPF Operations for more information about the ZROUT commands.

ROUT0004EAPPLICATION applname IS NOT IN THIS PROCESSOR

Where:

applname
The name of the application program.

Explanation: The application name specified in the ZROUT command does not reside in the processor where the command is entered.

System Action: None.

User Response: Do the following:

  1. Enter the ZDRCT command to display the name of the program.
  2. Enter the ZROUT command again from the processor where the application program resides.

See TPF Operations for more information about the ZROUT and ZDRCT commands.

ROUT0005ESS/SSU FOR APPLICATION applname IS NOT AVAILABLE

Where:

applname
The name of the application program.

Explanation: The subsystem or the subsystem user (SSU) for the specified application program is not active.

System Action: None.

User Response: Do the following:

  1. Enter the ZDRCT command to display the name of the program.
  2. Enter the ZROUT command again from the processor where the application program resides.

See TPF Operations for more information about the ZROUT and ZDRCT command.

ROUT0006EAPPLICATION applname STOP IN PROGRESS

Where:

applname
The name of the application program.

Explanation: The application program referenced in the message is in shutdown mode, for example, the stop request is in progress. The application program will be stopped when the 15 minutes waiting time is expired.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZROUT commands.

ROUT0007EAPPLICATION applname ALREADY ACTIVE

Where:

applname
The name of the application program.

Explanation: The application program referenced in the message and specified in the ZROUT START command is already active.

System Action: None.

User Response: Enter the ZDRCT command to display the status of the application program.

See TPF Operations for more information about the ZROUT START command.

ROUT0008IAPPLICATION applname MADE ACTIVE

Where:

applname
The name of the application program.

Explanation: The application program referenced in the message and specified in the ZROUT START command was made active.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZROUT START command.

ROUT0009ESTOP PROHIBITED FOR PERMANENT APPLICATION

Explanation: The application name specified in the ZROUT STOP command is a permanent application such as SMPx and CLGx.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZROUT STOP command.

ROUT0010EAPPLICATION applname ALREADY STOPPED

Where:

applname
The name of the application program.

Explanation: The application program referenced in the message and specified in the ZROUT STOP command is already stopped.

System Action: None.

User Response: Enter the ZDRCT STOP command to display the status of the application program.

See TPF Operations for more information about the ZROUT STOP command.

ROUT0011EAPPLICATION applname STOP ALREADY REQUESTED

Where:

applname
The name of the application program.

Explanation: The TPF system was IPLed while a previous ZROUN STOP request was in progress. The application program is still marked as ACTIVE in the routing control application table (RCAT) because the system was IPLed before the RCAT was keypointed.

System Action: The application program is marked as SHUTDOWN. The application program is stopped when the 15 minutes waiting time is expired.

User Response: None.

See TPF Operations for more information about the ZROUT STOP command.

ROUT0012EFACS ERROR DURING RCST CALCULATION

Explanation: FACS returned an error during file address calculation of the application stop table (record type #IBMM4, ordinal 53 -- #RCSTSTP).

System Action: The error message is displayed and the ECB is exited.

User Response: Enter the ZDREC command to display the application stop table.

If the problem continues, see your system administrator who can check the CRAA program where the FACS is invoked.

See TPF Operations for more information about the ZROUT and the ZDREC commands.

ROUT0013EFIND ERROR IN RCAT STOP TABLE

Explanation: FIWHC returns an error while retrieving the application stop table (record type #IBMM4, ordinal #RCSTSTP).

System Action: Display the error message and exit the ECB.

User Response: Enter the ZDREC command to display the application stop table.

If the problem continues, see your system programmer who can check the CRAA program where the FIWHC is issued.

See TPF Operations for more information about the ZROUT and the ZDREC commands.

ROUT0014IAPPLICATION applname STOPPING

Where:

applname
The name of the application program.

Explanation: All validation of the ZROUT STOP request is completed.

System Action: The application program is marked as SHUTDOWN in the routing control application table (RCAT), and an entry is added to the application stop table.

User Response: None.

See TPF Operations for more information about the ZROUT STOP command.

ROUT0015EAPPLICATION applname NOT IN RCST

Where:

applname
The name of the application program.

Explanation: The CRAA program cannot find the application program in the application stop table (record type #IBMM4, ordinal #RCSTSTP).

System Action: The error message is displayed and the ECB is exited.

User Response: See your system programmer who can determine the cause of the error by examining the CRAA program, the application stop table, and the system console log.

See TPF Operations for more information about the ZROUT STOP command.

ROUT0016EAPPLICATION applname IN RCST BUT NOT IN RCAT

Where:

applname
The name of the application program.

Explanation: The CRAA program cannot find the application program in the routing control application table (RCAT).

System Action: The error message is displayed and the ECB is exited.

User Response: See your system programmer who can determine the cause of the error by examining the CRAA program, the application stop table, and the system console log.

See TPF Operations for more information about the ZROUT commands.

ROUT0017IAPPLICATION applname STOPPED

Where:

applname
The name of the application program.

Explanation: The application program referenced in the message and specified in the ZROUT STOP command is stopped.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZROUT STOP commands.