gtpm5m20Messages (Online)

NKEY-NNCS

NKEY0004WSINCE MAXSRT IS ZERO, keyword IS IGNORED BY THE SYSTEM

Where:

keyword
The keyword of the field in keypoint record 2 (CTK2).

Explanation: The value in the keyword field in the Systems Network Architecture (SNA) communications keypoint (CTK2) is not used because SNA message recovery was not invoked.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNKEY command.

NKEY0011EINVALID FORMAT

Explanation: The ZNKEY command was issued incorrectly.

System Action: The ZNKEY command is rejected.

User Response: Do the following:

  1. Determine the correct format for the command.
  2. Enter the command again by using the correct format.

See TPF Operations for more information about the ZNKEY command.

NKEY0012EINVALID PARAMETER

Explanation: The ZNKEY command was entered with a value specified for the KEYWORD parameter that is not found in the ZNKEY parameter table (CSK0).

System Action: The command is rejected.

User Response: Do the following:

  1. Determine the correct format for the command.
  2. Enter the command again by using the correct format.

See TPF Operations for more information about the ZNKEY command.

NKEY0013EINVALID ALTER REQUEST

Explanation: The ZNKEY command was entered with a value specified for the KEYWORD parameter that cannot be altered.

System Action: The ZNKEY command is rejected.

User Response: None.

See TPF Operations for more information about the ZNKEY command.

NKEY0014EINVALID VALUE PARAMETER

Explanation: The alter value specified was not valid.

System Action: The request is rejected.

User Response: Enter the command again and specify a valid parameter value.

See TPF Operations for more information about the ZNKEY command.

NKEY0015EVALUE NOT WITHIN VALID RANGE

Explanation: The ZNKEY command was entered with an alter value specified that was not within the valid range for the KEYWORD parameter.

System Action: The ZNKEY command is rejected.

User Response: Enter the command again and specify a valid parameter value.

See TPF Operations for more information about the ZNKEY command.

NKEY0016EUNABLE TO RETRIEVE ZNKEY OPERAND TABLE, CSK0

Explanation: An error was detected while trying to access the ZNKEY operand table in the CSK0 segment.

System Action: The request is rejected.

User Response: See your system programmer for more information.

See TPF Operations for more information about the ZNKEY command.

NKEY0018EUNABLE TO FILE KEYPOINT RECORD -2-, CTK2

Explanation: An error was detected while trying to file the Systems Network Architecture (SNA) communications keypoint. The in-core copy of the keypoint was altered but not the file copy.

System Action: The request is rejected.

User Response: See your system programmer for more information.

See TPF Operations for more information about the ZNKEY command.

NKEY0023ICPUID x keyword -- value

Where:

x
The CPU ID

keyword
The keyword of the field in keypoint record 2 (CTK2).

value
The value in the field in keypoint record 2 (CTK2).

Explanation: This is the normal response to the ZNKEY command that requests a display of a specific field in the keypoint record 2 (CTK2).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNKEY command.

NKEY0024ICPUID x keyword - value
·
·
·

Where:

x
The CPU ID

keyword
The keyword of the field in keypoint record 2 (CTK2).

value
The value in the field in keypoint record 2 (CTK2).

Explanation: This is the normal response to the ZNKEY command that requests a display of all of the fields in the keypoint record 2 (CTK2).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNKEY command.

NKEY0025ICPUID x keyword -- value WAS nvalue

Where:

x
The CPU ID

keyword
The keyword of the field in keypoint record 2 (CTK2).

value
The old value in the field in keypoint record 2 (CTK2).

nvalue
The new value in the field in keypoint record 2 (CTK2).

Explanation: This is the normal response to the ZNKEY command with the ALTER parameter specified. The value in the keypoint record 2 field specified is changed to the new value referenced in the message.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNKEY command.

NKEY0026ESNDWN MUST BE LESS THAN RESTART LEVEL, SNRST

Explanation: The value specified for the SNDWN parameter must be less than the value assigned to the SNRST parameter.

System Action: The ZNKEY command is rejected.

User Response: Enter the ZNKEY command again and specify the correct value.

See TPF Operations for more information about the ZNKEY command.

NKEY0027ESNRST MUST BE GREATER THAN SHUTDOWN LEVEL, SNDWN

Explanation: The ZNKEY command was entered with the SNRST parameter specified. An error occurred because the value specified must be greater than the value specified for the SNDWN parameter.

System Action: The ZNKEY command is rejected.

User Response: Enter the ZNKEY command again and specify the correct value for the SNRST parameter.

See TPF Operations for more information about the ZNKEY command.

NKEY0121ESINCE THERE ARE NO CCBS AND NO SOCKETS DEFINED, MAXSDD CAN NOT BE ALTERED

Explanation: The ZNKEY command was entered with a request to change the value of the MAXSDD parameter, but there are no conversation control blocks (CCBs) defined; that is, the MAXCCB parameter equals 0, and there are no sockets defined; that is, the MAXSOCK parameter equals 0.

System Action: The ZNKEY command is rejected.

User Response: Do the following:

  1. Do one of the following:
  2. Load the new Systems Network Architecture (SNA) keypoint record 2 (CTK2).
  3. IPL the TPF system.
  4. Enter the ZNKEY command again.

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

NKEY0122ESINCE MAXCCB PLUS 2 PLUS MAXSOCK MUST EXCEED MAXHCT, MAXHCT CAN NOT BE UPDATED

Explanation: The ZNKEY command was entered, but the value specified on a request to change the MAXHCT parameter was too high compared to the value of the MAXCCB parameter and to the value of the MAXSOCK parameter. The value of MAXHCT must be less than the MAXCCB parameter -2 plus the MAXSOCK parameter.

System Action: The ZNKEY command is rejected.

User Response: Do one of the following:

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

NLM00001ILM COMMAND ACCEPTED

Explanation: The ZNLM command was entered.

System Action: Processing continues.

User Response: None.

See TPF Operations for more information about the ZNLM command.

NLM00004EREJECTED, SYSTEM IS BELOW CRAS STATE

Explanation: The ZNLM command was entered when the TPF system was not in CRAS state or above. You can only enter the ZNLM command when the TPF system is in CRAS state or above.

System Action: The ZNLM command is rejected.

User Response: Do the following:

  1. Ensure the TPF system is in CRAS state or above.
  2. Enter the ZNLM command again.

See TPF Operations for more information about the ZNLM command.

NLM00010ELM COMMAND REJECTED--NO CLU_CLU SESSION ACTIVE

Explanation: The ZNLM command was entered but there is no CLU-CLU session available to handle the request.

System Action: The ZNLM command is rejected.

User Response: Do the following:

  1. Activate a CLU-CLU session.
  2. Enter the ZNLM command again.

See TPF Operations for more information about the ZNLM command. See TPF ACF/SNA Data Communications Reference for more information about activating sessions.

NLM00011ELM COMMAND REJECTED--INVALID NAME ENTERED

Explanation: The ZNLM command was entered, however, the name specified is not a valid control LU (CLU) or adjacent link station (ALS).

System Action: The request is rejected.

User Response: Enter the ZNLM command with a valid name or do not specify a name. In this case TPF will select an active CLU_CLU session to use.

See TPF Operations for more information about the ZNLM command.

NLM00012ELM COMMAND REJECTED--INVALID INPUT

Explanation: The ZNLM command was entered, however, the message parser determined that the message format was incorrect.

System Action: The request is rejected.

User Response: Verify that the ZNLM command was entered with an optional name, followed by a required comma, followed by the message for the remote CLU to process.

See TPF Operations for more information about the ZNLM command.

NMON0002IBEGIN ZNMON DISPLAY

Explanation: This is the normal response to the ZNMON command with the ALS parameter specified. This message is followed by a display of statistical information about the sessions through each adjacent link station (ALS), Network Control Program (NCP), and channel-to-channel (CTC) resource in the network.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNMON command.

NMON0004INO ACTIVE ALS FOUND

Explanation: There are currently no active adjacent line station (ALS), Network Control Program (NCP), or channel-to-channel (CTC) resources.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNMON command.

NMON0006EREJECTED, SYSTEM IS BELOW 1052 STATE

Explanation: You can enter the ZNMON 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 ZNMON command again.

See TPF Operations for more information about the ZNMON command.

NNCB0001IINITIALIZATION COMPLETE

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

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNNCB command.

NNCB0006EINVALID MOD NUMBER

Explanation: The ZNNCB command was entered with a module number that is not valid.

System Action: The ZNNCB command is rejected.

User Response: Enter the ZNNCB command again and specify a valid module number.

See TPF Operations for more information about the ZNNCB command.

NNCB0007EINVALID NODENAME

Explanation: The ZNNCB command was entered with a resource name that is not valid.

System Action: The ZNNCB command is rejected.

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

See TPF Operations for more information about the ZNNCB command.

NNCB0008EMOD OFFLINE

Explanation: The ZNNCB command was entered with the MOD parameter specified but the module name specified is not online.

System Action: The ZNNCB command is rejected.

User Response: Do the following:

  1. Bring the module online.
  2. Enter the ZNNCB command again with the MOD parameter specified.

See TPF Operations for more information about the ZNNCB command.

NNCB0010IINITIALIZATION COMPLETE -- ACTIVE NODES SKIPPED

Explanation: This is a normal response to the ZNNCB command. Only the node control block (NCB) records for the logical unit (LU) resources that do not have active sessions were initialized.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNNCB command.

NNCB0012INCB NOT INITIALIZED -- SESSION ACTIVE

Explanation: The TPF system cannot initialize the specified node control block (NCB) record because the logical unit (LU) has one or more active sessions.

System Action: The ZNNCB command is rejected.

User Response: Do the following:

  1. Wait until the LU sessions end.
  2. Enter the ZNNCB command again with the NAME or NOD parameter specified.

See TPF Operations for more information about the ZNNCB command.

NNCB0013EDUPLICATED NODE NAMES EXIST

Explanation: More than one logical unit (LU) matches the resource name specified for the ZNNCB command.

System Action: The ZNNCB command is rejected.

User Response: Include the network identifier in the ZNNCB command to distinguish the multiple resource names.

See TPF Operations for more information about the ZNNCB command.

NNCB0015EREJECTED, SYSTEM IS BELOW 1052 STATE

Explanation: You can enter the ZNNCB command only in 1052 state or higher.

System Action: The ZNNCB command is rejected.

User Response: Do the following:

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

See TPF Operations for more information about the ZNNCB command.

NNCB0016ISTART INITIALIZING NCB

Explanation: This is the normal response to the ZNNCB command. This message is also displayed when the TPF system begins initializing node control block (NCB) records during a fresh load.

System Action: The TPF system initializes the NCB records.

User Response: None.

See TPF Operations for more information about the ZNNCB command. Also see TPF ACF/SNA Data Communications Reference for more information about fresh loads.

NNCB0018ERESOURCE NAME WAS NOT FOUND

Explanation: The resource specified for the ZNNCB command does not exist.

System Action: The ZNNCB command is rejected.

User Response: Enter the ZNNCB command again and specify the name of a resource that exists in the TPF system.

See TPF Operations for more information about the ZNNCB command.

NNCB0019EAN ERROR OCCURRED INITIALIZING luname NCB

Where:

luname
One of the following:

Explanation: The TPF system could not initialize the NCB record for the specified LU resource.

System Action: Processing for the NCB initialization function ends.

User Response: See your system programmer for more information.

See TPF ACF/SNA Data Communications Reference for more information about the NCB initialization function.

NNCB0020EAN ERROR OCCURRED RETRIEVING THE NCBCR

Explanation: The TPF system cannot retrieve the NCB control record.

System Action: The ZNNCB command is rejected.

User Response: See your system programmer for more information.

See TPF ACF/SNA Data Communications Reference for more information about the NCB control record. See TPF Operations for more information about the ZNNCB command.

NNCB0021ECANNOT INITIALIZE NCBS WHILE REORG IS ACTIVE

Explanation: An attempt was made to initialize one or more node control block (NCB) records while the NCB reorganization function was active.

System Action: The ZNNCB REORG command is rejected.

User Response: Do the following:

  1. Do one of the following:
  2. Enter the ZNNCB REORG command again to initialize the NCB records.

See TPF Operations for more information about the ZNNCB REORG command.

NNCB0022ESPECIFIED RESOURCE IS NOT AN LU

Explanation: You can enter the ZNNCB command only for a logical unit (LU) resource because only LU resources use node control block (NCB) records.

System Action: The ZNNCB command is rejected.

User Response: Enter the ZNNCB command again and specify the name of an LU resource.

See TPF Operations for more information about the ZNNCB command.

NNCB0023EAN ERROR OCCURRED RETRIEVING THE NCBDR

Explanation: The TPF system cannot retrieve an NCB directory record.

System Action: Processing for the ZNNCB command ends.

User Response: See your system programmer for more information.

See TPF ACF/SNA Data Communications Reference for more information about NCB directory records. See TPF Operations for more information about the ZNNCB command.

NNCB0024ECANNOT INITIALIZE NCBS WHILE RECON IS ACTIVE

Explanation: An attempt was made to initialize one or more node control block (NCB) records while the NCB reconciliation function was active.

System Action: The ZNNCB RECON command is rejected.

User Response: Do the following:

  1. Do one of the following:
  2. Enter the ZNNCB RECON command again to initialize the NCB records.

See TPF Operations for more information about the ZNNCB RECON command.

NNCB0026EPARAMETERS SPECIFIED FOR ZNNCB ARE NOT VALID

Explanation: One or more of the parameters specified for the ZNNCB command are not valid.

System Action: The ZNNCB command is rejected.

User Response: Enter the ZNNCB command again and specify the correct parameters.

See TPF Operations for more information about the ZNNCB command.

NNCB0027EREJECTED, GFS IS NOT ACTIVE

Explanation: The ZNNCB RECON command was entered when the get file storage (GFS) function was not active.

System Action: The ZNNCB RECON command is rejected.

User Response: Do the following:

  1. Enter the ZCYCL command to cycle the TPF system above 1052 state.
  2. Enter the ZNNCB RECON command again.

See TPF Operations for more information about the ZNNCB RECON and ZCYCL commands.

NNCB0028ECPU HAS NOT INCORPORATED CURRENT RRT DEFINITIONS

Explanation: The ZNNCB command was entered to initialize node control block (NCB) records on a processor that has not incorporated the latest resource definitions.

System Action: The ZNNCB command is rejected.

User Response: Do the following:

  1. Enter the ZRIPL or the ZNOPL MERGE command to incorporate the new RRT definitions.
  2. Enter the ZNNCB command again.

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

NNCB0029INO NCBS EXIST FOR THE SPECIFIED RESOURCE

Explanation: The ZNNCB DISPLAY command was entered for a resource that does not have any node control block (NCB) records.

System Action: None.

User Response: None.

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

NNCB0030ENETID OR RESOURCE NAME CONTAINS TOO MANY CHARACTERS

Explanation: The resource specified for the ZNNCB command contains too many characters in either the network identifier or the resource name.

System Action: The ZNNCB command is rejected.

User Response: Enter the ZNNCB command again and specify no more than 8 characters each for the network identifier and resource name.

See TPF Operations for more information about the ZNNCB command.

NNCB0031ENCB INITIALIZATION IS ACTIVE

Explanation: An attempt was made to start the node control block (NCB) reorganization function or the NCB reconciliation function while the NCB initialization function was active.

System Action: The ZNNCB RECON or ZNNCB REORG command is rejected.

User Response: Do the following:

  1. Wait until the NCB initialization function ends.
  2. Enter the ZNNCB RECON or ZNNCB REORG command.

See TPF Operations for more information about the ZNNCB command.

NNCB0032ENCB REORGANIZATION IS ACTIVE

Explanation: An attempt was made to start the node control block (NCB) reconciliation function while the NCB reorganization function was active.

System Action: The ZNNCB REORG command is rejected.

User Response: Do the following:

  1. Do one of the following:
  2. Enter the ZNNCB RECON command again.

See TPF Operations for more information about the ZNNCB command.

NNCB0033ENCB RECONCILIATION IS ACTIVE

Explanation: An attempt was made to start the node control block (NCB) reorganization function while the NCB reconciliation function was active.

System Action: The ZNNCB RECON command is rejected.

User Response: Do the following:

  1. Do one of the following:
  2. Enter the ZNNCB REORG command again.

See TPF Operations for more information about the ZNNCB command.

NNCB0034EERROR FROM DHASHC MACRO

Explanation: An error was returned by the DHASHC macro while trying to locate a node control block (NCB) directory record.

System Action: Processing for the ZNNCB RECON command ends.

User Response: See your system programmer for more information.

See TPF System Macros for more information about the DHASC macro. See TPF Operations for more information about ZNNCB RECON command.

NNCB0035ENCB INITIALIZATION COMPLETE, BUT CANNOT RESET CONTROL BIT IN NCBCR

Explanation: The node control block (NCB) records were initialized; however, the TPF system could not reset the NCB initialization bit in the NCB control record.

System Action: The TPF system cannot start the NCB reorganization or NCB reconciliation functions until the NCB initialization bit is reset in the NCB control record.

User Response: See your system programmer for more information.

See TPF ACF/SNA Data Communications Reference for more information about the NCB control record and NCB initialization.

NNCB0070Irectype DATABASE INITIALIZATION STARTED

Where:

rectype
The type of record being initialized, either NCBN4 or NCBN5.

Explanation: This message is displayed when the TPF system begins initializing the NCBN4 or NCBN5 node control block (NCB) directory records.

System Action: The TPF system begins to initialize the NCBN4 or NCBN5 NCB directory records.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the NCB directory records.

NNCB0071Irectype DATABASE INITIALIZATION COMPLETED

Where:

rectype
The type of record being initialized, either NCBN4 or NCBN5.

Explanation: This message is displayed when the TPF system completes initializing the NCBN4 or NCBN5 node control block (NCB) directory records.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the NCB directory records.

NNCB0072EFACS ERROR ON RECORD TYPE rectype

Where:

rectype
The type of record being initialized, either NCBN4 or NCBN5.

Explanation: A file address retrieval program (FACS) error occurred while initializing the NCBN4 or NCBN5 node control block (NCB) directory records.

System Action: The ZNNCB command is rejected.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the NCB directory records. See TPF Operations for more information about the ZNNCB command.

NNCB0073WMUST SPECIFY BP PARAMETER TO ABORT RECON FROM THIS CPU

Explanation: The ZNNCB RECON command was entered with the ABORT parameter from a processor that did not start the node control block (NCB) reconciliation function.

System Action: The ZNNCB RECON command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNNCB RECON and ZNNCB DISPLAY commands.

NNCB0074INCB RECONCILIATION ABORT INITIATED

Explanation: This is the normal response to the ZNNCB RECON command with the ABORT parameter specified.

System Action: The TPF system starts ending the NCB reconciliation function.

User Response: None.

See TPF Operations for more information about the ZNNCB RECON command.

NNCB0075INCB RECONCILIATION ABORTED

Explanation: This message is displayed when the node control block (NCB) reconciliation function is canceled by specifying the ABORT parameter in the ZNNCB RECON command.

System Action: Processing for the NCB reconciliation function ends.

User Response: None.

See TPF Operations for more information about the ZNNCB RECON command.

NNCB0076INCB RECONCILIATION STARTED

Explanation: This is the normal response to the ZNNCB RECON command with the ALL, NAME, or NOD parameters specified.

System Action: The TPF system begins the node control block (NCB) reconciliation function.

User Response: None.

See TPF Operations for more information about the ZNNCB RECON command.

NNCB0077INCB RECONCILIATION COMPLETED

Explanation: This message is displayed when the node control block (NCB) reconciliation function is completed. Following this message is a display of information about the results of the NCB reconciliation function.

System Action: None.

User Response: None.

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

NNCB0078INCB RECONCILIATION RESTARTED

Explanation: This message is displayed when the node control block (NCB) reconciliation function is restarted because an initial program load (IPL) was performed before the NCB reconciliation function could end.

System Action: The TPF system starts the NCB reconciliation function again.

User Response: None.

See TPF Operations for more information about the ZNNCB RECON command.

NNCB0079ERECON IS NOT ACTIVE

Explanation: The ZNNCB RECON command was entered with the ABORT parameter specified when the node control block (NCB) reconciliation function was not running.

System Action: The ZNNCB RECON command is rejected.

User Response: None.

See TPF Operations for more information about the ZNNCB RECON command.

NNCB0080ENO ENTRY EXISTS IN THE NCBDR FOR THE SPECIFIED RESOURCE

Explanation: The ZNNCB RECON command was entered for a logical unit (LU) resource that does not have an entry in the node control block (NCB) directory records.

System Action: The ZNNCB RECON command is rejected.

User Response: None.

See TPF Operations for more information about the ZNNCB RECON command.

NNCB0083WMUST SPECIFY BP PARAMETER TO ABORT REORG FROM THIS CPU

Explanation: The ZNNCB REORG command was entered with the ABORT parameter from a processor that did not start the node control block (NCB) reorganization function.

System Action: The ZNNCB REORG command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNNCB REORG and ZNNCB DISPLAY commands.

NNCB0084IABORT INITIATED FOR NCB DATABASE REORG

Explanation: This is the normal response to the ZNNCB REORG command with the ABORT parameter specified.

System Action: The TPF system starts ending the NCB reorganization function.

User Response: None.

See TPF Operations for more information about the ZNNCB REORG command.

NNCB0085INCB REORG DATABASE SWITCH INITIATED

Explanation: This is the normal response to the ZNNCB REORG command with the SWITCH parameter specified.

System Action: The TPF system switches the current and staged node control block (NCB) directory records.

User Response: None.

See TPF Operations for more information about the ZNNCB REORG command.

NNCB0086INCB REORG DATABASE SWITCH COMPLETED

Explanation: This message is displayed when the node control block (NCB) directory records are switched during the NCB reorganization function.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the NCB reorganization function.

NNCB0087EREORG IS NOT ACTIVE

Explanation: The ZNNCB REORG command was entered with the ABORT parameter when the node control block (NCB) reorganization function was not running.

System Action: The ZNNCB REORG command is rejected.

User Response: None.

See TPF Operations for more information about the ZNNCB REORG command.

NNCB0088EREORG IS ABORTING

Explanation: The ZNNCB REORG command was entered with the ABORT parameter when the node control block (NCB) reorganization function was already in the process of being canceled.

System Action: The ZNNCB REORG command is rejected.

User Response: None.

See TPF Operations for more information about the ZNNCB REORG command.

NNCB0089EREORG COPY FAILED

Explanation: An error occurred while copying the current node control block (NCB) directory records to the staged NCB directory records.

System Action: Processing for the NCB reorganization function ends.

User Response: See your system programmer for more information.

See TPF ACF/SNA Data Communications Reference for more information about the NCB reorganization function.

NNCB0090ERECOUP IS ACTIVE

Explanation: An attempt was made to start the node control block (NCB) reorganization function while the online file recoup function was active

System Action: The ZNNCB REORG command is rejected.

User Response: Do the following:

  1. Do one of the following:
  2. Enter the ZNNCB REORG command again.

See TPF Operations for more information about the ZNNCB REORG and ZRECP ABORT commands.

NNCB0091ENCBDR INITIALIZATION ERROR

Explanation: An error occurred while initializing the node control block (NCB) directory records.

System Action: Processing for the NCB reorganization function ends.

User Response: See your system programmer for more information.

See TPF ACF/SNA Data Communications Reference for more information about the NCB directory records and the NCB reorganization function.

NNCB0092EREORG COPY NOT COMPLETED

Explanation: The ZNNCB REORG command was entered with the SWITCH parameter before the current node control block (NCB) directory records were copied to the staged NCB directory records.

System Action: The ZNNCB REORG command is rejected.

User Response: Enter the ZNNCB REORG command again with the SWITCH parameter when you are prompted to do so by the TPF system.

See TPF Operations for more information about the ZNNCB REORG command. Also see TPF ACF/SNA Data Communications Reference for more information about the NCB reorganization function.

NNCB0093INCB REORG DATABASE COPY TASK BEGUN

Explanation: This is the normal response to the ZNNCB REORG command with the START parameter specified.

System Action: The TPF system begins copying the current node control block (NCB) directory records to the staged NCB directory records.

User Response: None.

See TPF Operations for more information about the ZNNCB REORG command.

NNCB0094WA STAGED NCB DIRECTORY RECORD IS FULL

Explanation: The current node control block (NCB) directory records cannot be copied to the staged NCB directory records because a staged NCB directory record is full.

System Action: The ZNNCB REORG command is rejected.

User Response: Do the following:

  1. Enter the ZNNCB DISPLAY command with the ALL parameter specified to determine the record type for the staged NCB directory records.
  2. Increase the number of staged NCB directory records that are defined in the TPF system.
  3. Enter the ZNNCB REORG command again.

See TPF Operations for more information about the ZNNCB DISPLAY and ZNNCB REORG commands.

NNCB0096EFACS ERROR CURRENT NCBDR ordnum

Where:

ordnum
The ordinal number of the node control block (NCB) directory record.

Explanation: A file address retrieval program (FACS) error occurred while trying to locate the specified NCB directory record.

System Action: Processing for the NCB reorganization command ends.

User Response: See your system programmer for more information.

See TPF ACF/SNA Data Communications Reference for more information about NCB directory records and the NCB reorganization function.

NNCB0097INCB REORG DATABASE COPY COMPLETED ENTER ZNNCB REORG SWITCH

Explanation: This message is displayed after the current node control block (NCB) directory records are copied to the staged NCB directory records.

System Action: None.

User Response: Enter the ZNNCB REORG command with the SWITCH parameter to switch the current and staged NCB directory records. This will complete the NCB reorganization function.

See TPF Operations for more information about ZNNCB REORG command.

NNCB0098INCB REORG ABORTED

Explanation: This message is displayed when the node control block (NCB) reorganization function is canceled by specifying the ABORT parameter in the ZNNCB REORG command.

System Action: Processing for the NCB reorganization function ends.

User Response: None.

See TPF Operations for more information about the ZNNCB REORG command.

NNCB0099INCB REORG COPY RESTARTED AT ORDINAL ordnum

Where:

ordnum
The ordinal number of the node control block (NCB) directory record.

Explanation: This message is displayed when the NCB reorganization function is restarted because an initial program load (IPL) was performed before the NCB reorganization function could end.

System Action: The TPF system starts the NCB reorganization function again.

User Response: None.

See TPF Operations for more information about the ZNNCB REORG command.

NNCB0100EREORG SWITCH IS IN PROGRESS - ABORT COMMANDS ARE NOT ALLOWED

Explanation: You cannot cancel the node control block (NCB) reorganization function while the current and staged NCB directory records are being switched.

System Action: The NCB reorganization function continues.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about the NCB reorganization function.

NNCB0110I*** NCB CONTROL RECORD DISPLAY ***

Explanation: This is the normal response to the ZNNCB DISPLAY command with the ALL parameter specified. This message displays information contained in the node control block (NCB) control record.

System Action: The TPF system displays the requested information.

User Response: None.

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

NNCB0130INCB INFORMATION FOR netid.name

Where:

netid
The network ID of the resource.

name
The name of the resource.

Explanation: This is the normal response to the ZNNCB DISPLAY command with the NAME or NOD parameter specified. This message is followed by a display of information about the NCB records for the resource.

System Action: The TPF system displays the requested information.

User Response: None.

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

NNCS0000IBEGIN ZNNCS DISPLAY

Explanation: This is the normal response to the ZNNCS command. This message is followed by a display of the network command status table (NCST).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNNCS command.

NNCS0001INO ACTIVITY IN NETWORK COMMAND STATUS TABLE

Explanation: No network addressable units (NAU) are in the process of being activated or deactivated.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNNCS command.

NNCS0016EREJECTED, SYSTEM IS BELOW 1052 STATE

Explanation: The ZNNCS command was entered when the TPF system was not in 1052 state or above.

System Action: The ZNNCS command is rejected.

User Response: Do the following:

  1. Ensure the TPF system is in 1052 state or above.
  2. Enter the ZNNCS command again.

See TPF Operations for more information about the ZNNCS command.