gtpm5m1xMessages (Online)

NACT-NCNS

NACT0000IREACTIVATE OUTPUT COMPLETE

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

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNACT command.

NACT0010EINVALID NODENAME

Explanation: The node name specified in the command is not valid.

System Action: None.

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

See TPF Operations for more information about the ZNACT command.

NACT0011EDATABASE RETRIEVAL ERROR

Explanation: An input/output (I/O) problem was encountered in trying to retrieve a required table entry.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNACT command.

NACT0012EDATABASE ERROR

Explanation: The node name specified in the command was validated but an input condition that is not valid was generated by an internal conversion routine. This would imply a database problem.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNACT command.

NACT0013ENODE NOT A HARDCOPY DEVICE

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

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNACT command.

NACT0014EOUTPUT ALREADY REACTIVATED

Explanation: The device specified is already active.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNACT command.

NACT0015EREJECTED, DUPLICATE LU NAME node name, NETID REQUIRED

Where:

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

Explanation: The node name 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 node name.

See TPF Operations for more information about the ZNACT command.

NACT0016EREJECTED, SYSTEM NOT IN OR ABOVE CRAS STATE

Explanation: The TPF system must be in or above the computer room agent set (CRAS) state for Systems Network Architecture (SNA) to be activated.

System Action: The command is rejected.

User Response: Do the following:

  1. Bring the TPF system above 1052 state.
  2. Enter the command again.

See TPF Operations for more information about the ZNACT command.

NALS0001IBEGIN ZNALS DISPLAY

Explanation: This is the normal message from the ZNALS command. It is followed by a display of the ALS status.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNALS command.

NALS0003INO ALS WITH SPECIFIED STATUS

Explanation: This is a normal message from the ZNALS command. It is entered when there are no adjacent link stations (ALSs) with the specified status parameter (ACTIVE or INACTIVE).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNALS command.

NALS0050EINVALID ALS NAME

Explanation: The adjacent link stations (ALS) name specified in the command was not found in the resource vector table (RVT).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNALS command.

NALS0051EINVALID ZNALS FORMAT

Explanation: The status parameter following ALL on the command was not ACTIVE or INACTIVE.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNALS command.

NALT0001IOMT Q SWITCHED FROM nodename TO nodename

Where:

nodename
The node name.

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

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNALT command.

NALT0002EFROM OR TO nodename NOT A PRINTER

Where:

nodename
The node name.

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

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNALT command.

NALT0003EINVALID RID

Explanation: An error was returned from the RIDCC macro. This is a possible database problem.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNALT command.

NALT0004Enodename -- INVALID NODENAME

Where:

nodename
The node name.

Explanation: The node name specified in the command is not valid.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNALT command.

NALT0005EINVALID MESSAGE FORMAT

Explanation: The format of the command is not valid. The second parameter was the same as the first parameter or the second parameter was not specified.

System Action: None.

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 ZNALT command.

NALT0006Enode name -- HAS AN ALTERNATE ASSIGNED

Where:

node name
The node name.

Explanation: The TO device has an alternate assigned to it.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNALT command.

NALT0007EREJECTED, DUPLICATE LU NAME node name, NETID REQUIRED

Where:

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

Explanation: The node name 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 node name.

See TPF Operations for more information about the ZNALT command.

NALT0008EREJECTED, SYSTEM NOT IN OR ABOVE CRAS STATE

Explanation: The TPF system must be in or above the computer room agent set (CRAS) state for Systems Network Architecture (SNA) to be activated.

System Action: The command is rejected.

User Response: Do the following:

  1. Bring the TPF system above 1052 state.
  2. Enter the command again.

See TPF Operations for more information about the ZNALT command.

NAPN0001IAPPN-LEN SWITCH SET TO APPN

Explanation: This is the normal response to the ZNAPN command with the APPN parameter is specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNAPN command.

NAPN0002IAPPN-LEN SWITCH SET TO LEN

Explanation: This is the normal response to the ZNAPN command with the LEN parameter is specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNAPN command.

NAPN0003IAPPN-LEN SWITCH IS var

Where:

var
This is APPN or LEN.

Explanation: This is the normal response to the ZNAPN command with the STATUS parameter is specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNAPN command.

NAPN0004ICP-CP SESSIONS EXIST ON PROCESSOR x

Where:

x
The CPU ID of the TPF processor with the C-CP sessions.

Explanation: This is the normal response to the ZNAPN command with the STATUS parameter is specified, the TPF system is running in APPN mode, and CP-CP sessions exist.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNAPN command.

NAPN0005WAPPN-LEN SWITCH ALREADY SET TO var

Where:

var
This is either APPN or LEN.

Explanation: One of the following errors occurred:

System Action: The ZNAPN command is rejected.

User Response: None.

See TPF Operations for more information about the ZNAPN command.

NAPN0006EREJECTED, APPN SUPPORT NOT AVAILABLE

Explanation: The ZNAPN command was entered with the APPN parameter specified but APPN support has not been incorporated in the TPF system. This indicates that no local:

System Action: The ZNAPN command is rejected.

User Response: Do the following:

  1. Define a local CP or local TPF/APPC LU with the MSGRTA macro in SIP.
  2. Run SIP to create a new ANT deck.
  3. Run OSTG by using the new ANT deck.
  4. Load the new OSTG to the TPF system.
  5. Enter the ZNAPN command again.

See TPF Operations for more information about the ZNAPN command. See TPF ACF/SNA Network Generation for more information about the OSTG deck.

NAPN0007EREJECTED, LEN SUPPORT NOT AVAILABLE

Explanation: The ZNAPN command was entered with the LEN parameter specified but LEN support has not been incorporated in the TPF system. This indicates that no local control point logical units (CLUs) have been included in the OSTG deck.

System Action: The ZNAPN command is rejected.

User Response: Do the following:

  1. Define CLUs in the OSTG deck.
  2. Load the new OSTG to the TPF system.
  3. Enter the ZNAPN command again.

See TPF Operations for more information about the ZNAPN command. See TPF ACF/SNA Network Generation for more information about the OSTG deck.

NAPN0008EREJECTED, SNA RESTART HAS NOT COMPLETED

Explanation: The ZNAPN command was entered before Systems Network Architecture (SNA) restart processing completed.

System Action: The ZNAPN command is rejected.

User Response: Enter the ZNAPN command after SNA restart processing ends.

See TPF Operations for more information about the ZNAPN command.

NAPN0009EREJECTED, UNABLE TO ACCESS APPN TAPST RECORD

Explanation: An I/O or FACS program error occurred while trying to access the TAPST file record.

System Action: The ZNAPN command is rejected.

User Response: Review the system error dump that precedes this message to determine the cause of the error.

See TPF Operations for more information about the ZNAPN command.

NAPN0010EREJECTED, CP-CP SESSIONS ACTIVE ON PROCESSOR x

Where:

x
The CPU ID of the TPF processor with the CP-CP sessions.

Explanation: The ZNAPN command was entered with the LEN parameter specified while APPN CP-CP sessions were active.

System Action: The ZNAPN command is rejected.

User Response: Do the following:

  1. Enter the ZNETW INACT command to deactivate the CP-CP sessions.
  2. Enter the ZNAPN command again.

See TPF Operations for more information about the ZNAPN and ZNETW INACT commands.

NAPN0011IBEGIN ZNAPN TOPOLOGY DISPLAY

Explanation: This is the normal response to the ZNAPN command with the TOPOLOGY parameter specified. It is followed by a display of one or more active links.

System Action: None.

User Response: None.

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

NAPN0013EREJECTED, CPU ID SPECIFIED IS NOT VALID

Explanation: The ZNAPN command was entered with a CPU ID that is not valid.

System Action: The ZNAPN command is rejected.

User Response: Enter the ZNAPN command again and omit the CPU parameter or specify a valid CPU ID.

See TPF Operations for more information about the ZNAPN command.

NAPN0014EREJECTED, CP NAME SPECIFIED IS NOT VALID

Explanation: The ZNAPN command was entered specifying a CP name containing a network ID or name that is more than 8 characters.

System Action: The ZNAPN command is rejected.

User Response: Enter the ZNAPN command again and omit the CP parameter or specify a valid CP name.

See TPF Operations for more information about the ZNAPN command.

NAPN0015INO ACTIVE LINKS MEETING THE SEARCH CRITERIA

Explanation: The ZNAPN command was entered with the TOPOLOGY parameter specified, but there were no active links meeting the search criteria specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNAPN command.

NCCB0000EINVALID NODENAME

Explanation: The ZNCCB function issues this message when you specify a node name that is not valid in the command.

System Action: None.

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

See TPF Operations for more information about the ZNCCB command.

NCCB0001EREJECTED, MULTIPLE LUS WITH SAME NAME

Explanation: More than one logical unit (LU) matches the node name specified in the ZNCCB command.

System Action: The ZNCCB command is rejected.

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

See TPF Operations for more information about the ZNCCB command.

NCCB0005ECCB ORDINAL OUT OF RANGE

Explanation: The ZNCCB function issues this message when you specify an ordinal number that is zero or exceeds the total number of conversation control blocks (CCBs).

System Action: The ZNCCB command is rejected.

User Response: Enter the command again and specify a valid CCB ordinal number.

See TPF Operations for more information about the ZNCCB command.

NCCB0006ETHERE ARE NO CCBS DEFINED IN THE SYSTEM

Explanation: The ZNCCB function issues this message when you try to process the command in a TPF system that does not have any conversation control blocks (CCBs) defined.

System Action: None.

User Response: The ZNCCB command is valid only in conjunction with TPF Advanced Program-to-Program Communications (TPF/APPC) support. To use this support, you must define the maximum number of CCBs to be used in the TPF system by specifying the MAXCCB parameter on the SNAKEY macro.

See TPF Operations for more information about the ZNCCB command. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro. See TPF ACF/SNA Data Communications Reference for more information about the TPF/APPC support in general.

NCCB0007EINVALID CONVERSATION STATE

Explanation: The ZNCCB function issues this message when you specify an incorrect state value on the ZNCCB DC command.

System Action: None.

User Response: Enter the command again with a valid state code.

See TPF Operations for more information about the ZNCCB command.

NCCB0008INO ACTIVE CONVERSATIONS

Explanation: The ZNCCB function issues this message when you specify a logical unit (LU) that has no associated active conversations.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCCB0020ICCB CONTENTS FORMATTED

Explanation: This is the normal response to the ZNCCB command with the DF parameter specified. This message is followed by a formatted display of the content of the TPF/APPC conversation control block (CCB).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCCB0021ICCB CONTENTS

Explanation: This is the normal response to the ZNCCB command with the DU parameter specified. This message is followed by an unformatted display of the content of the TPF/APPC conversation control block (CCB).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCCB0022ICCB INITIALIZATION COMPLETE

Explanation: This is the normal response to the ZNCCB command with the INIT parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCCB0023ICCB SUMMARY INFORMATION

Explanation: This is the normal response to the ZNCCB command with the DC SUM parameters specified. This message is followed by a display of the number of active and inactive conversation control blocks (CCB).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCCB0024ICCB CONVERSATION STATES

Explanation: This is the normal response to the ZNCCB command with the DC ALL parameters specified. This message is followed by a display of the number of conversation control blocks (CCB) in each conversation state.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCCB0025Inumber CCBS IN STATE num -- state

Where:

number
The number of conversation control blocks (CCBs) currently in the specified state.

num
The state specified on the command.

state
The state name.

Explanation: This is the normal response to the ZNCCB command with the DC parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCCB0026ICCBID LIST FOR net ID.node name

Where:

net ID
The network ID.

node name
The node name.

Explanation: This is the normal response to the ZNCCB command with the DC N parameters specified. This message is followed by a list of conversation control block identifiers (CCBIDs) for the conversations associated with the specified remote LU.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCCB0027ESYSTEM NOT IN NORM STATE

Explanation: This message occurs when you enter a ZNCCB INIT command while the TPF system is below NORM state.

System Action: The ZNCCB INIT command is rejected.

User Response: Do the following:

  1. Cycle the TPF system to NORM state.
  2. Enter the command again.

See TPF Operations for more information about the ZNCCB command.

NCCB0028IACTIVE TPF MAPPED CONVERSATIONS

Explanation: This is the normal response to the ZNCCB command with the DC ALL MAPPED parameters specified. This message is followed a display of all active mapped conversation control blocks (CCBs) by state.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCCB0040EINVALID STATE state IN CCB ORDINAL NUMBER ordnum

Explanation: The ZNCCB DC ALL function enters this message when the conversation control block (CCB) with the specified ordinal number is in an incorrect conversation state.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCCB0041EINVALID MAPPED STATE state IN CCB ORDINAL NUMBER ordnum

Where:

state
The state of the TPF system.

ordnum
The ordinal number.

Explanation: The ZNCCB DC ALL MAPPED function enters this message when the conversation control block (CCB) with the specified ordinal number supports an active mapped conversation and is in an incorrect mapped conversation state.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCCB command.

NCNS0001IREQUEST COMPLETED FOR LU-luname MODE-modename

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

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

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0002IREQUEST COMPLETED FOR LU-luname MODE-modename LIMIT-totsess, CONW-winners, CONL-losers

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

totsess
The total number of sessions.

winners
The total number of contention winners.

losers
The total number of contention losers.

Explanation: This is the normal response to the ZNCNS command. This command completed successfully but the values were negotiated. The new values are displayed in this message.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0003IREQUEST ACCEPTED FOR LU-luname MODE-modename

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: This is the normal response to the ZNCNS command, indicating that the request was accepted and processing started.

System Action: Another message follows when processing is complete.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0004EREQUEST REJECTED FOR LU-luname MODE-modename ALLOCATION ERROR, RETRY LATER

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the control operator conversation cannot be allocated successfully.

System Action: The ZNCNS command is rejected.

User Response: Enter the command again later.

See TPF Operations for more information about the ZNCNS commands.

NCNS0005EREQUEST REJECTED FOR LU-luname MODE-modename ALLOCATION ERROR, NO RETRY

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the control operator conversation cannot be allocated successfully.

System Action: The ZNCNS command is rejected.

User Response: Do not enter the ZNCNS command again.

See TPF Operations for more information about the ZNCNS commands.

NCNS0006EREQUEST REJECTED FOR LU-luname MODE-modename COMMAND RACE REJECT

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the source logical unit (LU) or the target LU is currently processing another CNOS transaction for the same mode name.

System Action: The ZNCNS command is rejected.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0007EREQUEST REJECTED FOR LU-luname MODE-modename LIMIT PARAMETER MUST BE GREATER THAN ZERO

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the value specified for the LIMIT parameter is less than or equal to zero.

System Action: The ZNCNS command is rejected.

User Response: Enter the command again specifying a LIMIT parameter with a value greater than zero.

See TPF Operations for more information about the ZNCNS commands.

NCNS0008EREQUEST REJECTED FOR LU-luname MODE-modename SUM OF CONW AND CONL CANNOT EXCEED SESSION LIMIT

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the sum of the values specified for the CONW and CONL parameters is greater than the value specified for the LIMIT parameter.

System Action: The ZNCNS command is rejected.

User Response: Enter the command again specifying the CONW and CONL parameter with values less than or equal to the LIMIT parameter value.

See TPF Operations for more information about the ZNCNS commands.

NCNS0009EREQUEST REJECTED FOR LU-luname MODE-modename RESP PARAMETER INVALID

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the value specified for the RESP parameter is not valid.

System Action: The ZNCNS command is rejected.

User Response: Enter the ZNCNS command again specifying SOURCE or TARGET for the RESP parameter.

See TPF Operations for more information about the ZNCNS commands.

NCNS0011EREQUEST REJECTED FOR LU-luname MODE-modename INSUFFICIENT RESOURCES - NO RETRY

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when a resource failure causes the control operator conversation to be deallocated prematurely. This might be caused by a session outage, a protocol error, or other errors.

System Action: The ZNCNS command is rejected.

User Response: Do not enter the ZNCNS command again.

See TPF Operations for more information about the ZNCNS commands.

NCNS0012EREQUEST REJECTED FOR LU-luname MODE-modename CHANGE LIMIT REQUEST FOR SNASVCMG NOT ALLOWED

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when you specify the SNASVCMG mode name on a change request.

System Action: The ZNCNS command is rejected.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0013EREQUEST REJECTED FOR LU-luname MODE-modename SYSTEM MUST BE IN CRAS STATE OR ABOVE

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The TPF system must be in or above computer room agent set (CRAS) state to enter this command.

System Action: The command is rejected.

User Response: Do the following:

  1. Bring the TPF system above 1052 state.
  2. Enter the command again.

See TPF Operations for more information about the ZNCNS commands.

NCNS0014EREQUEST REJECTED FOR LU-luname MODE-modename VERB ONLY VALID FOR PARALLEL SESSIONS

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when you issue the CHANGE verb and specify a single session mode name.

System Action: The ZNCNS command is rejected.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0015EREQUEST REJECTED FOR LU-luname MODE-modename INVALID OR UNKNOWN LU NAME

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the value specified on the LU parameter is not the name of a remote LU that is type LU62 or type ANY. This message is also issued when a remote APPN control point (CP) is specified because CNOS requests are not valid for these LUs.

System Action: The ZNCNS command is rejected.

User Response: Enter the command again specifying a valid logical unit (LU) name.

See TPF Operations for more information about the ZNCNS commands.

NCNS0016EREQUEST REJECTED FOR LU-luname MODE-modename SESSION LIMIT NOT INITIALIZED

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS CHANGE command issues this message when the limits for the (logical unit (LU), mode name) pair specified were never initialized.

System Action: The ZNCNS CHANGE command is rejected.

User Response: Initialize the session limits.

See TPF Operations for more information about the ZNCNS CHANGE command.

NCNS0017EREQUEST REJECTED FOR LU-luname MODE-modename INVALID OR UNKNOWN MODENAME

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the TPF system or the target logical unit (LU) does not recognize the mode name. This message is also issued when reserved mode name CPSVCMG is specified because this mode name is reserved for APPN CP-CP sessions and is not valid for CNOS requests.

System Action: The ZNCNS command is rejected.

User Response: Enter the ZNCNS command again specifying a valid mode name.

See TPF Operations for more information about the ZNCNS commands.

NCNS0018EREQUEST REJECTED FOR LU-luname MODE-modename DRAIN PARAMETER INVALID

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the value specified for the DRAIN parameter is not valid.

System Action: The ZNCNS command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNCNS commands.

NCNS0019EREQUEST REJECTED FOR LU-luname MODE-modename RESP PARAMETER INVALID FOR INITIALIZE VERB

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when you specify the RESP parameter with the INITIALIZE function.

System Action: The ZNCNS command is rejected.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0020EREQUEST REJECTED FOR LU-luname MODE-modename SESSION LIMIT ALREADY RESET

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when you specify RESET when the session limit is already zero.

System Action: The ZNCNS command is rejected.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0021EREQUEST REJECTED FOR LU-luname MODE-modename MAX SESSION LIMIT IS 64K

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the LIMIT parameter is greater than 64 KB. The maximum session limit value is 64 KB.

System Action: The ZNCNS command is rejected.

User Response: Enter the ZNCNS command again specifying a lower session limit.

See TPF Operations for more information about the ZNCNS commands.

NCNS0022EREQUEST REJECTED FOR LU-luname MODE-modename LOCAL PARAMETER NOT VALID FOR THIS VERB

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the LOCAL parameter is issued for this verb. The LOCAL parameter is only valid with the INITIALIZE verb.

System Action: The ZNCNS command is rejected.

User Response: Enter the ZNCNS command again without specifying the LOCAL parameter.

See TPF Operations for more information about the ZNCNS commands.

NCNS0023EREQUEST REJECTED FOR LU-luname MODE-modename LOCAL LU SPECIFIED CANNOT BE USED

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS INIT function issues this message under one of the following conditions:

System Action: The ZNCNS command is rejected.

User Response: Enter the ZNCNS command again specifying a valid LU name for the LOCAL parameter.

See TPF Operations for more information about the ZNCNS commands.

NCNS0024EREQUEST REJECTED FOR LU-luname MODE-modename INVALID OR UNKNOWN CDRM NAME

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS INIT function issues this message when you specify a cross-domain resource manager name that is not valid on the CDRM parameter.

System Action: The ZNCNS INIT command is rejected.

User Response: Enter the ZNCNS INIT command again specifying a valid cross-domain resource manager (CDRM) name.

See TPF Operations for more information about the ZNCNS commands.

NCNS0025EREQUEST REJECTED FOR LU-luname MODE-modename CDRM PARAMETER NOT VALID FOR THIS VERB

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when you specify the CDRM parameter with a function other than INITIALIZE. The CDRM parameter is valid only for the INITIALIZE function.

System Action: The ZNCNS command is rejected.

User Response: Enter the ZNCNS command again without specifying the CDRM parameter.

See TPF Operations for more information about the ZNCNS commands.

NCNS0026EREQUEST REJECTED FOR LU-luname MODE-modename CDRM SESSION NOT ACTIVE

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS INIT function issues this message when there is no active cross-domain resource manager-cross-domain resource manager (CDRM-CDRM) session with the CDRM name specified.

System Action: The ZNCNS INIT command is rejected.

User Response: Do the following:

  1. Activate the CDRM-CDRM session.
  2. Enter the command again.

See TPF Operations for more information about the ZNCNS commands.

NCNS0027EREQUEST REJECTED FOR LU-luname MODE-modename CP PARAMETER NOT VALID FOR THIS VERB

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when you specify the CP parameter on a ZNCNS command other than the ZNCNS INITIALIZE command. The CP parameter is valid only for the ZNCNS INITIALIZE command.

System Action: The ZNCNS command is rejected.

User Response: Enter the appropriate ZNCNS command again and do not specify the CP parameter.

See TPF Operations for more information about the ZNCNS commands.

NCNS0028EREQUEST REJECTED FOR LU-luname MODE-modename CP NAME NOT VALID

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when you enter the ZNCNS INITIALIZE command with a control point (CP) name specified that is not valid on the CP parameter.

System Action: The ZNCNS INITIALIZE command is rejected.

User Response: Enter the ZNCNS INITIALIZE command again and specify a valid CP name.

See TPF Operations for more information about the ZNCNS INITIALIZE command.

NCNS0029EREQUEST REJECTED FOR LU-luname MODE-modename REMOTE CP NOT AVAILABLE

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS INITIALIZE function issues this message when there is no active adjacent link station (ALS) between the TPF system and the control point (CP) specified on the CP parameter.

System Action: The ZNCNS INITALIZE command is rejected.

User Response: Do the following:

  1. Activate an ALS between the TPF system and remote CP.
  2. Enter the ZNCNS INITIALIZE command again.

See TPF Operations for more information about the ZNCNS INITIALIZE command.

NCNS0030EREQUEST REJECTED FOR LU-luname MODE-modename CDRM AND CP NOT ALLOWED

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS INITIALIZE function issues this message when you specify both the CDRM and CP parameters.

System Action: The ZNCNS INITIALIZE command is rejected.

User Response: Enter the ZNCNS INITIALIZE command again and specify the CDRM parameter, the CP parameter, or neither parameter.

See TPF Operations for more information about the ZNCNS INITIALIZE command.

NCNS0038EREQUEST REJECTED FOR LU-luname MODE-modename SESSION LIMIT ALREADY INITIALIZED

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: This message is issued when you enter the ZNCNS INITIALIZE command for a (logical unit (LU), mode name) pair that is already initialized.

System Action: The ZNCNS command is rejected.

User Response: Enter the ZNCNS CHANGE command to change the session limits to the desired values.

See TPF Operations for more information about the ZNCNS INITIALIZE and ZNCNS CHANGE commands.

NCNS0039EREQUEST REJECTED FOR LU-luname MODE-modename SESSION LIMIT CLOSED

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS INITIALIZE command was entered to raise the limit of the number of sessions for a specified (logical unit (LU), mode name pair) but the remote LU rejects the request and the limit remains zero.

System Action: The ZNCNS INITIALIZE command is rejected.

User Response: None.

See TPF Operations for more information about the ZNCNS INITIALIZE command.

NCNS0040EREQUEST REJECTED FOR LU-luname MODE-modename INVALID OR UNKNOWN LOCAL LU NAME

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: This message is issued when the ZNCNS INITIALIZE command is entered with a local LU name that is not valid specified on the LOCAL parameter.

System Action: The ZNCNS INITIALIZE command is rejected.

User Response: Enter the ZNCNS INITIALIZE command again specifying a valid local LU name.

See TPF Operations for more information about the ZNCNS INITIALIZE command.

NCNS0041EREQUEST REJECTED FOR LU-luname MODE-modename SESSIONS EXIST WITH REMOTE LU ON ANOTHER PROCESSOR

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the remote LU specified by the LU parameter already has sessions with another processor in the loosely coupled complex.

System Action: The ZNCNS command is rejected.

User Response: Do the following:

  1. Enter the ZNDLU command and specify the remote LU name on the ID parameter to see which TPF host in the loosely coupled complex has sessions with this remote LU.
  2. Enter the ZNCNS command on the TPF host that was returned in the ZNDLU display.

See TPF Operations for more information about the ZNCNS and ZNDLU commands.

NCNS0042EREQUEST REJECTED FOR LU-luname MODE-modename LOCAL LU NOT ACTIVE

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when the local LU specified (or the default LU, if none was specified) is not active.

System Action: The ZNCNS command is rejected.

User Response: Do the following:

  1. Enter the ZNETW ACT and ZROUT START commands to activate the local LU.
  2. Enter the ZNCNS command again.

See TPF Operations for more information about the ZNCNS, ZNETW ACT, and ZROUT START commands.

NCNS0046IREQUEST COMPLETED FOR LU-luname MODE-modename RESP NEGOTIATED TO SOURCE

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: This is the normal response to the ZNCNS command with the RESET parameter specified.

System Action: The command completed successfully and the source (TPF) logical unit (LU) is now responsible for deactivating sessions.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0047IREQUEST COMPLETED FOR LU-luname MODE-modename FORCE AS SPECIFIED

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: This is the normal response to the ZNCNS command with the RESET FORCE parameters and the source (TPF) logical unit (LU) specified as responsible for deactivating sessions.

System Action: The CNOS request or reply completes successfully.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0048IREQUEST COMPLETED FOR LU-luname MODE-modename FORCE AS SPECIFIED, RESP FORCED TO SOURCE

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: This is the normal response to the ZNCNS command with the RESET FORCE parameters and the target (remote) logical unit (LU) specified as responsible for deactivating sessions.

System Action: The session limit is reset to zero for the specified (LU, mode name) pair and the source (TPF) LU is now responsible for deactivating the sessions.

User Response: None.

See TPF Operations for more information about the ZNCNS commands.

NCNS0056EREQUEST REJECTED FOR LU-luname MODE-modename CANNOT RESET SNASVCMG UNLESS ALL OTHER MODES RESET TO ZERO

Where:

luname
The logical unit (LU) name specified on the LU parameter.

modename
The mode name specified on the MODE parameter.

Explanation: The ZNCNS function issues this message when you try to reset the session limit and contention polarities for the SNASVCMG mode name before all the other mode names for the specified logical unit (LU) are reset.

System Action: The ZNCNS command is rejected.

User Response: Do the following:

  1. Reset the session limits for all other mode names to zero.
  2. Enter the command again for the SNASVCMG mode name.

See TPF Operations for more information about the ZNCNS commands.