gtpm5m21Messages (Online)

NOPL-NPRG

NOPL0001IDYNAMIC LOAD ACTIVE RESOURCE REPORT

Explanation: The ZNOPL UPDATE or ZNOPL FALLBACK command tried to delete or redefine an active logical unit (LU) resource. Following this message, there is a display that shows a list of these LU resources and the associated error.

System Action: The TPF system displays an additional message to further describe the errors that occurred.

User Response: See the additional message that is displayed for more information.

See TPF Operations for more information about the ZNOPL UPDATE and ZNOPL FALLBACK commands.

NOPL0002ISNA RESOURCE DEFINITION STATUS

Explanation: This is the normal response to the ZNOPL STATUS command. This message is followed by the time, date, and user description of the current and new (alternate) resource resolution table (RRT) sections and if the active processors are by using the current Systems Network Architecture (SNA) resource definitions.

System Action: The TPF system displays the requested information.

User Response: None.

See TPF Operations for more information about the ZNOPL STATUS command.

NOPL0003IONLINE MERGE RESOURCE REPORT

Explanation: The ZNOPL MERGE command was not successful. Following this message, there is a display that shows a list of the resources that caused the online merge function to fail and the reasons.

System Action: Processing for the online merge function ends.

User Response: Do the following:

  1. See the online merge resource report.
  2. Correct the errors that occurred.
  3. Perform another Systems Network Architecture (SNA) dynamic load to load the resource definitions to the TPF system.

See TPF Operations for more information about the ZNOPL MERGE command. See TPF ACF/SNA Data Communications Reference for more information about performing a SNA dynamic load.

NOPL0030EUNABLE TO PERFORM FUNCTION, LOAD IN PROGRESS.

Explanation: A ZNOPL command was entered when a load request was processing.

System Action: The ZNOPL command is rejected.

User Response: Enter the ZNOPL command again when the load processing is completed.

See TPF Operations for more information about the ZNOPL commands.

NOPL0031EUNABLE TO PERFORM FUNCTION, UPDATE IN PROGRESS.

Explanation: A ZNOPL command was entered when an update request was processing.

System Action: The ZNOPL command is rejected.

User Response: Enter the ZNOPL command again when the update processing is completed.

See TPF Operations for more information about the ZNOPL commands.

NOPL0032EUNABLE TO PERFORM FUNCTION, FALLBACK IN PROGRESS.

Explanation: A ZNOPL command was entered when a fallback request was processing.

System Action: The ZNOPL command is rejected.

User Response: Enter the ZNOPL command again when the fallback processing is completed.

See TPF Operations for more information about the ZNOPL commands.

NOPL0033EUPDATE IS DISABLED.

Explanation: You cannot enter the ZNOPL UPDATE command at this time. You can enter the ZNOPL UPDATE command only after you enter the ZNOPL LOAD command with the DYNAMIC parameter.

System Action: The ZNOPL UPDATE command is rejected.

User Response: Do the following:

  1. Enter the ZNOPL LOAD command and specify the DYNAMIC parameter.
  2. Wait for the load to be completed.
  3. Enter the ZNOPL UPDATE command again.

See TPF Operations for more information about the ZNOPL UPDATE and ZNOPL LOAD commands.

NOPL0034EFALLBACK IS DISABLED.

Explanation: You cannot enter the ZNOPL FALLBACK command at this time because there are no Systems Network Architecture (SNA) resource definitions in the new (alternate) resource resolution table (RRT). You can enter the ZNOPL FALLBACK command only after you perform a dynamic load by entering the ZNOPL LOAD command.

System Action: The ZNOPL FALLBACK command is rejected.

User Response: None.

See TPF Operations for more information about the ZNOPL FALLBACK and ZNOPL LOAD commands.

NOPL0035EUNABLE TO FALLBACK, ALTERNATE DEFINITIONS ARE UNUSABLE

Explanation: The ZNOPL FALLBACK command was entered to fall back to the previous Systems Network Architecture (SNA) resource definitions contained in the new (alternate) resource resolution table (RRT). However, the new (alternate) RRT is not usable.

System Action: The ZNOPL FALLBACK command is rejected.

User Response: Enter the ZNOPL LOAD command to load the previous SNA resource definitions again.

See TPF Operations for more information about the ZNOPL FALLBACK and ZNOPL LOAD commands.

NOPL0036EPILOT ID MISMATCH, REQUESTED--x READ--y.

Where:

x
The pilot ID specified in the ZNOPL LOAD command.

y
The pilot ID of the input data set.

Explanation: The pilot ID of the input data set does not match the pilot ID specified in the ZNOPL LOAD command.

System Action: The ZNOPL LOAD command is rejected.

User Response: Verify that the correct data set is mounted and that the correct pilot ID is specified for the ZNOPL LOAD command.

See TPF Operations for more information about the ZNOPL LOAD command.

NOPL0037WRESOURCES EXCEED MAXRVT, MAXRVT-xxxx THIS LOAD-yyyy PROCESSING CONTINUES

Where:

xxxx
The maximum number of resource vector table (RVT) entries allowed.

yyyy
The number of RVT entries required for the load.

Explanation: The TPF system does not have enough space allocated in the RVT for this load.

System Action: As many resources as possible are loaded to the TPF system.

User Response: Do the following:

  1. Increase the size of the RVT.
  2. Load the Systems Network Architecture (SNA) resource definitions to the TPF system again.

See TPF ACF/SNA Network Generation for more information about increasing the size of the RVT. See the TPF ACF/SNA Data Communications Reference for more information about loading SNA resource definitions.

NOPL0039EINSUFFICIENT RRT RECORDS ALLOCATED, ALLOCATED--xxxx THIS LOAD--yyyy

Where:

xxxx
The number of records of type #RRTRI that are allocated to the online system.

yyyy
The number of records of type #RRTRI that are required for this load.

Explanation: Not enough records of type #RRTRI are allocated to the online TPF system. This load cannot be completed successfully.

System Action: Processing for the load function ends.

User Response: Do the following:

  1. Allocate more #RRTRI records.
  2. Load the Systems Network Architecture (SNA) resource definitions to the TPF system again.

See the TPF ACF/SNA Data Communications Reference for more information about loading SNA resource definitions.

NOPL0040AACTIVE DELETES--xxxx ACTIVE DEF CHANGES--yyyy, UPDATE FAILED, INACTIVATE ACTIVE RESOURCES AND RE-TRY ZNOPL UPDATE.

Where:

xxxx
The number of active resource definitions trying to be deleted.

yyyy
The number of active resource definitions trying to be changed.

Explanation: The ZNOPL UPDATE command was entered to update the resource resolution table (RRT) definitions after a dynamic load. However, update processing was not successful because the new resource definitions attempted to delete or redefine active logical unit (LU) resources.

System Action: The TPF system displays the dynamic load active resources report, which contains a list of all the active LU resources.

User Response: Do the following:

  1. See the dynamic load active resource report.
  2. Deactivate the active resources.
  3. Enter the ZNOPL UPDATE command again.

See TPF Operations for more information about the ZNOPL UPDATE command.

NOPL0042AACTIVE DELETES--xxxx ACTIVE DEF CHANGES--yyyy, FALLBACK FAILED, INACTIVATE ACTIVE RESOURCES AND RE-ENTER ZNOPL FALLBACK.

Where:

xxxx
The number of active resource definitions trying to be deleted.

yyyy
The number of active resource definitions trying to be changed.

Explanation: The ZNOPL FALLBACK command was entered to fall back to the previous resource definitions. However, fallback processing was not successful because the previous definitions attempted to delete or redefine active logical unit (LU) resources.

System Action: The TPF system displays the dynamic load active resources report, which contains a list of all the active LU resources.

User Response: Do one of the following:

See TPF Operations for more information about the ZNOPL FALLBACK command.

NOPL0043EGDS ERROR, REASON CODE x

Where:

x
The reason code.

Explanation: An error occurred while accessing the input general data set (GDS).

System Action: None.

User Response: See TPF General Macros for more information about the GDSNC macro to interpret the reason code.

NOPL0044EINSUFFICIENT NCBS. NUMBER NEEDED THIS LOAD -- nnnnnnnn, GENNED -- mmmmmmmm, MAXRVT -- pppppppp

Where:

nnnnnnnn
The number of fixed file node control block (NCB) records required for this load.

mmmmmmmm
The number of fixed file NCB records generated in the TPF system.

pppppppp
The number of entries in the resource vector table (RVT).

Explanation: The number of fixed file NCB records generated in the TPF system is not sufficient to load the current Systems Network Architecture (SNA) resource definitions. The number of fixed file NCB records generated should exceed the maximum number of resources that you plan to define to the TPF system by using the offline ACF/SNA table generation (OSTG) program.

System Action: Load processing ends.

User Response: Do the following:

  1. Increase the number of fixed file NCB records in the TPF system.
  2. Load the SNA resource definitions to the TPF system again.

See TPF ACF/SNA Data Communications Reference for more information about loading SNA resource definitions to the TPF system.

NOPL0045EOPERATION FAILED. POSSIBLE ACTIVE RID--xxxxxxxx, MAXRVT yyyyyyyy

Where:

xxxxxxxx
The resource identifier (RID) where the error occurred.

yyyyyyyy
The number of entries in the resource vector table (RVT).

Explanation: The RVT on the processor from which the ZNOPL UPDATE command was entered is not large enough to load the Systems Network Architecture (SNA) resource definitions.

System Action: Processing for the update function ends.

User Response: Do one of the following:

See TPF Operations for more information about the ZNOPL UPDATE command. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

NOPL0046EDDNAME SNA NOT DEFINED. USE ZDSMG TO DEFINE

Explanation: The ZNOPL LOAD command was entered but the Systems Network Architecture (SNA) data definition name was not defined to the TPF system.

System Action: The ZNOPL LOAD command is rejected.

User Response: Do the following:

  1. Enter the ZDSMG DEFINE command to define the SNA data definition name to the TPF system.
  2. Enter the ZNOPL LOAD command again.

See TPF Operations for more information about the ZDSMG DEFINE and ZNOPL LOAD commands.

NOPL0047EDDNAME SNA DEFINED INCORRECTLY, REDEFINE

Explanation: The ZNOPL LOAD command was entered but the device type specified for the Systems Network Architecture (SNA) data definition name was not correct.

System Action: The ZNOPL LOAD command is rejected.

User Response: Do the following:

  1. Enter the ZDSMG RELEASE command to remove the incorrect SNA data definition name from the TPF system.
  2. Enter the ZDSMG DEFINE command to redefine the SNA data definition name to the TPF system and specify a device type of either GFDS or TAPE.
  3. Enter the ZNOPL LOAD command again.

See TPF Operations for more information about the ZDSMG DEFINE, ZDSMG RELEASE, and ZNOPL LOAD commands.

NOPL0052AFALLBACK COMPLETE ON CPU--cpuid, DISPLAY STATUS AND ZRIPL IF NECESSARY.

Where:

cpuid
The name of the processor.

Explanation: This is the normal response to the ZNOPL FALLBACK command when the FRESH parameter is specified. A fresh fallback was completed on the processor referred to in the message.

System Action: This message is sent to all active processors in the loosely coupled TPF system to notify you of the completed fallback.

User Response: Do the following:

  1. Enter the ZNOPL STATUS command to determine the processors where you must perform an initial program load (IPL) to incorporate the previous resource definitions.
  2. Enter the ZRIPL command on the processors that require an IPL.

See TPF Operations for more information about the ZNOPL FALLBACK and ZRIPL commands.

NOPL0060AFRESH LOAD COMPLETE ON CPU--cpuid, ZRIPL TO INCORPORATE NEW DEFINITIONS.

Where:

cpuid
The name of the processor.

Explanation: This is the normal response to the ZNOPL LOAD command with the FRESH parameter specified. A fresh load completed on the processor referred to in the message.

System Action: This message is sent to all active processors in the loosely coupled TPF system to notify you of the completed load.

User Response: Enter the ZRIPL command on each processor in the TPF system to incorporate the latest resource definitions.

See TPF Operations for more information about the ZNOPL LOAD and ZRIPL commands.

NOPL0061ASUCCESSFUL DYNAMIC LOAD, UPDATE ENABLED.

Explanation: This is the normal response to the ZNOPL LOAD command with the DYNAMIC parameter is specified. The dynamic load was completed.

System Action: Update processing is enabled.

User Response: Enter the ZNOPL UPDATE functional from any processor in the loosely coupled TPF system to continue the dynamic load function.

See TPF Operations for more information about the ZNOPL LOAD and ZNOPL UPDATE commands.

NOPL0062AUPDATE COMPLETE ON CPU--cpuid. ENTER ZNOPL MERGE TO INCORPORATE NEW DEFINITIONS.

Where:

cpuid
The name of the processor.

Explanation: This is the normal response to the ZNOPL UPDATE command. Update processing was completed on the processor referred to in the message.

System Action: This message is sent to all active processors to notify you that update processing is completed and they need to enter the ZNOPL MERGE command to incorporate the latest resource definitions.

User Response: Enter the ZNOPL MERGE command on each processor in the TPF system to incorporate the latest resource definitions and complete the dynamic load function.

See TPF Operations for more information about the ZNOPL UPDATE command.

NOPL0063AFALLBACK COMPLETE ON CPU--cpuid DISPLAY STATUS AND ENTER ZNOPL MERGE IF NECESSARY

Where:

cpuid
The name of the processor.

Explanation: This is the normal response to the ZNOPL FALLBACK command. Fallback processing completed on the processor referred to in the message.

System Action: This message is sent to all active processors in the loosely coupled TPF system to notify you that fallback processing is completed and they need to enter the ZNOPL MERGE command to incorporate the previous resource definitions.

User Response: Do the following:

  1. Enter the ZNOPL STATUS command to determine the processors where you must enter the ZNOPL MERGE command to incorporate the previous resource definitions.
  2. Enter the ZNOPL MERGE command on those processors.

See TPF Operations for more information about the ZNOPL FALLBACK and ZNOPL MERGE commands.

NOPL0064IONLINE MERGE STARTED.

Explanation: This is the normal response to the ZNOPL MERGE command. It indicates that the online merge function was started.

System Action: The TPF system starts merging the current resource resolution table (RRT) with the resource vector table (RVT).

User Response: None.

See TPF Operations for more information about the ZNOPL MERGE command.

NOPL0065IONLINE MERGE COMPLETE.

Explanation: This message is displayed when the online merge function ends.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the online merge function.

NOPL0066EONLINE MERGE NOT ALLOWED, NO PREVIOUS UPDATE EXISTS

Explanation: You cannot enter the ZNOPL MERGE command at this time. You can enter the ZNOPL MERGE command only after you enter the ZNOPL UPDATE or ZNOPL FALLBACK command.

System Action: The ZNOPL MERGE command is rejected.

User Response: None.

See TPF Operations for more information about the ZNOPL MERGE, ZNOPL UPDATE, and ZNOPL FALLBACK commands.

NOPL0067EUNABLE TO PERFORM FUNCTION, ONLINE MERGE IN PROGRESS

Explanation: You cannot enter a ZNOPL command while the online merge function is in progress.

System Action: The ZNOPL command is rejected.

User Response: Do the following:

  1. Wait until the online merge function ends.
  2. Enter the ZNOPL command again.

See TPF Operations for more information about the ZNOPL commands.

NOPL0068EBUILD ALREADY IN EFFECT, ZRIPL REQUIRED

Explanation: The ZNOPL BUILD command was already entered for this processor. A fresh load will be performed on this processor during the next initial program load (IPL).

System Action: The ZNOPL BUILD command is rejected.

User Response: Enter the ZRIPL command to force a fresh load.

See TPF Operations for more information about the ZNOPL BUILD and ZRIPL commands.

NOPL0069ABUILD COMPLETE, ZRIPL TO FORCE FRESH LOAD FROM CURRENT RRT.

Explanation: This is the normal response to the ZNOPL BUILD command. A fresh load will be performed on this processor during the next initial program load (IPL).

System Action: None.

User Response: Enter the ZRIPL command to force a fresh load.

See TPF Operations for more information about the ZNOPL BUILD and ZRIPL commands.

NOPL0072EONLINE MERGE NOT ALLOWED ON GENERAL FILE LOAD

Explanation: You cannot enter the ZNOPL MERGE command while the TPF system is loading a general file.

System Action: The ZNOPL MERGE command is rejected.

User Response: Do the following:

  1. Perform an initial progral load (IPL) on the prime module.
  2. Enter the ZNOPL MERGE command again.

See TPF Operations for more information about the ZNOPL MERGE command.

NOPL0073EONLINE MERGE FAILED, NO MORE RESOURCE NAMES CAN BE INCORPORATED DUE TO INSUFFICIENT RESOURCE

Explanation: The online merge function was not successful because there are no spare entries in the resource vector table (RVT) to add more resources.

System Action: Processing for the online merge function ends.

User Response: Do one of the following:

See TPF Operations for more information about the ZNDYN RECYCLE command. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

NOPL0074EFACS/FIND ERROR OCCURRED ON RRT FILE, ONLINE MERGE FAILED

Explanation: A file address retrieval program (FACS) or FIND error occurred while retrieving the resource resolution table (RRT) record during the online merge function.

System Action: Processing for the online merge function ends.

User Response: See your system programmer for more information.

See TPF ACF/SNA Data Communications Reference for more information about the online merge function.

NOPL0075EONLINE MERGE IS DISABLED IN THIS PROCESSOR.

Explanation: You cannot enter the ZNOPL MERGE command at this time because the processor is already using the current resource resolution table (RRT) definitions.

System Action: The ZNOPL MERGE command is rejected.

User Response: None.

See TPF Operations for more information about the ZNOPL MERGE and ZNOPL UPDATE commands.

NOPL0076EUNABLE TO PERFORM FUNCTION, ZRIPL IS REQUIRED TO INCORPORATE NEW DEFINITIONS.

Explanation: You cannot enter a ZNOPL command at this time because a fresh load was performed and this processor has not incorporated the most recent Systems Network Architecture (SNA) resource definitions.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZRIPL command to incorporate the most recent resource definitions.
  2. Enter the appropriate ZNOPL command again.

See TPF Operations for more information about the ZNOPL and ZRIPL commands.

NOPL0077ELOCAL DELETES--xxxx ACTIVE DELETES/DEF CHANGES--yyyy, UPDATE FAILED, BAD OSTG WAS LOADED.

Where:

xxxx
The number of local resource definitions trying to be deleted.

yyyy
The number of active resource definitions trying to be changed or deleted.

Explanation: The ZNOPL UPDATE command was entered to update the resource resolution table (RRT) definitions after a dynamic load. However, update processing was not successful because the new resource definitions attempted to delete a local resource. The new resource definitions may have also attempted to delete or change active logical unit (LU) resources.

System Action: The TPF system displays the dynamic load active resources report, which contains a list of all the local and active LU resources.

User Response: Enter the ZNOPL LOAD command with the FRESH parameter to perform a fresh load or do the following:

  1. See the dynamic load active resources report.
  2. Correct the offline ACF/SNA table generation (OSTG) so that it no longer deletes the local resources.
  3. Deactivate the active resources.
  4. Enter the ZNOPL LOAD command again with the DYNAMIC parameter.
  5. Enter the ZNOPL UPDATE command again.
Note:
The FRESH parameter will end all of the active sessions on all of the processors in the loosely coupled TPF system.
See TPF Operations for more information about the ZNOPL UPDATE and ZNOPL LOAD commands.

NOPL0078EREJECT, THE SYSTEM IS BELOW 1052 STATE

Explanation: You cannot enter the ZNOPL MERGE command when the TPF system is below 1052 state.

System Action: The ZNOPL MERGE command is rejected.

User Response: Do the following:

  1. Ensure the TPF system is in 1052 state.
  2. Enter the ZNOPL MERGE command again.

See TPF Operations for more information about the ZNOPL MERGE command.

NOPL0148EINSUFFICIENT RV1RU. NUMBER NEEDED THIS LOAD--xxxx, GENNED--yyyy.

Where:

xxxx
The number of records currently allocated.

yyyy
The number of records required to complete the load.

Explanation: You did not allocate enough #RV1RU fixed file records to the online system. This load cannot complete successfully.

System Action: Processing for the load function ends.

User Response: Do the following:

  1. Allocate more #RV1RU fixed file records in the TPF system.
  2. Enter the ZNOPL LOAD command again.

See TPF Operations for more information about the ZNOPL LOAD command.

NOPL0149EINSUFFICIENT RV2RU. NUMBER NEEDED THIS LOAD--xxxx, GENNED--yyyy.

Where:

xxxx
The number of records currently allocated.

yyyy
The number of records required to complete the load.

Explanation: You did not allocate enough #RV2RU fixed file records to the online system. This load cannot complete successfully.

System Action: Processing for the load function ends.

User Response: Do the following:

  1. Allocate more #RV2RU fixed file records in the TPF system.
  2. Enter the ZNOPL LOAD command again.

See TPF Operations for more information about the ZNOPL LOAD command.

NPIU0004IPIU TRACE TABLE

Explanation: This is the normal response to the ZNPIU command with the COMPACT parameter specified. This message is followed by a display of the path information unit (PIU) trace table.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNPIU command and for an example of the informational display.

NPIU0005IPIU TRACE TABLE

Explanation: This is the normal response to the ZNPIU command with the FORMAT or LONG parameter specified. This message is followed by a display of the path information unit (PIU) trace table.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNPIU command and for an example of the informational display.

NPIU0050EILLEGAL PARAMETER -- MUST BE A NUMBER BETWEEN 1 AND 999

Explanation: The value specified for the ZNPIU command was not between 1 and 999

System Action: None.

User Response: Enter the ZNPIU command again and specify ALL or a value between 1 and 999.

See TPF Operations for more information about the ZNPIU command.

NPIU0051ENOT ACTIVE BELOW 1052 STATE

Explanation: You can enter the ZNPIU command only in 1052 state or above.

System Action: None.

User Response: Do the following:

  1. Ensure the TPF system is in 1052 state.
  2. Enter the ZNPIU command again.

See TPF Operations for more information about the ZNPIU command.

NPIU0052EUNABLE TO MALLOC STORAGE FOR ZNPIU DISPLAY

Explanation: An attempt to obtain malloc storage in order to copy the PIU trace table failed.

System Action: None.

User Response: Enter the ZNPIU command again. If the error occurs again, check the size of the PIU trace table specified in the TRACSZ parameter of the SNAKEY macro.

See TPF Operations for more information about the ZNPIU command.

NPOL0001Ixxxx STARTED

Where:

xxxx
The symbolic device address (SDA) for which polling was started.

Explanation: This is the normal response to the ZNPOL START command.

System Action: The TPF system starts polling the specified device.

User Response: None.

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

NPOL0003EADDRESS NOT FOUND

Explanation: The symbolic device address (SDA) specified for the ZNPOL START or ZNPOL STOP command was not found.

System Action: None.

User Response: Do the following:

  1. Verify the SDA.
  2. Enter the ZNPOL START or ZNPOL STOP command again.

See TPF Operations for more information about the ZNPOL START or ZNPOL STOP command.

NPOL0004ESDA xxxx IS INVALID

Segment Reference: CSNF

Where:

xxxx
The symbolic device address (SDA).

Explanation: A symbolic device address (SDA) of zero was specified on a ZNPOL START or STOP command. An SDA of zero is not valid.

System Action: The ECB is exited.

User Response: Enter the ZNPOL START or STOP command again and specify a valid SDA value.

See TPF Operations for more information about the ZNPOL START or ZNPOL STOP command.

NPOL0005Ixxxx STOPPED

Where:

xxxx
The symbolic device address (SDA).

Explanation: This is the normal response to the ZNPOL STOP command.

System Action: The TPF system stops polling the specified device.

User Response: None.

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

NPOL0006ELOAD/DUMP IN CONTROL

Explanation: The specified device cannot handle the request because the device is currently being loaded or a dump is occurring on the device.

System Action: None.

User Response: Do the following:

  1. Wait for the load or dump to complete.
  2. Enter the ZNPOL START or ZNPOL STOP command again.

See TPF Operations for more information about the ZNPOL START and ZNPOL STOP commands.

NPOL0009EREJECTED, SYSTEM IS BELOW 1052 STATE

Explanation: You can enter the ZNPOL command only in 1052 state or above.

System Action: None.

User Response: Do the following:

  1. Ensure the TPF system is in 1052 state.
  2. Enter the ZNPOL START or ZNPOL STOP command again.

See TPF Operations for more information about the ZNPOL START or ZNPOL STOP command.

NPRG0002IQUEUE FOR nodename PURGED TO TAPE PLM, MSG CT -- xx

Where:

nodename
The node name.

xx
The message count.

Explanation: The node control block (NCB) message queue for the requested resource was purged to the PLM tape.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNPRG command.

NPRG0003INO MESSAGES ON QUEUE

Explanation: There are no messages on the node control block (NCB) queue to purge or repeat.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNPRG command.

NPRG0010WNOT ALLOWED BELOW CRAS STATE

Explanation: The TPF system must be in the computer room agent set (CRAS) state or above before the request can be processed.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNPRG command.

NPRG0013EINVALID RID

Explanation: The output message transmitter (OMT) message purge routines detected a resource identifier (RID) error. This can indicate a possible database problem.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNPRG command.

NPRG0014EINVALID NODENAME

Explanation: The node name specified in the command is not valid or could not be found in the system network tables.

System Action: The command is rejected.

User Response: Enter the command again and specify a valid node name.

See TPF Operations for more information about the ZNPRG command.

NPRG0015ENODE NOT A PRINTER

Explanation: The node specified in the command is not a printer.

System Action: The command is rejected.

User Response: Enter the command again and specify a valid node name.

See TPF Operations for more information about the ZNPRG command.

NPRG0016ECONVERSION ERROR

Explanation: A RIDCC macro error occurred, which indicates a possible database problem.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNPRG command. See TPF General Macros for more information about the RIDCC macro.

NPRG0018TUNABLE TO RETRIEVE NCB FOR nodename

Where:

nodename
The name of the node for the node control block (NCP).

Explanation: The node control block (NCB) for the requested resource could not be retrieved.

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

User Response: None.

See TPF Operations for more information about the ZNPRG command.

NPRG0020EREJECTED, DUPLICATE LU NAME nodename, NETID REQUIRED

Where:

nodename
The name of the node for the logical unit (LU).

Explanation: The node referenced in the command is not a qualified name and a duplicate name exists in the network.

System Action: The command is rejected.

User Response: Enter the command again and specify a fully-qualified LU name.

See TPF Operations for more information about the ZNPRG command.