gtpm5m1y | Messages (Online) |
NCVT0001I | BEGIN ZNCVT DISPLAY |
Explanation: This is the normal response to the ZNCVT command. This message is followed by a display of the Systems Network Architecture (SNA) resource address or identification.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZNCVT command.
NCVT0002E | INVALID DATA FORMAT |
Explanation: The format of the command is not correct, for example, an incorrect length, hexadecimal format, or missing delimiters.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZNCVT command.
NCVT0003E | INVALID REQUEST TYPE |
Explanation: The request data type is not one of the 6 valid types.
System Action: None.
User Response: Enter the command again and specify a valid data type.
See TPF Operations for more information about the ZNCVT command.
NCVT0004E | REQUESTED DATA NOT FOUND |
Explanation: The input data could not be found in the data retrieval tables.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZNCVT command.
NCVT0005E | NOT IN 1052 STATE |
Explanation: The ZNCVT command was issued prior to 1052 state.
System Action: The ZNCVT command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZNCVT command.
NCVT0006E | UNABLE TO COMPLETE -- DATA NOT AVAILABLE |
Explanation: The requested data cannot be retrieved by using the given input. For example:
System Action: None.
User Response: None.
See TPF Operations for more information about the ZNCVT command.
NCVT0007I | BEGIN ZNCVT DISPLAY |
Explanation: This is the normal response to the ZNCVT command when the resource to be displayed is a high-performance routing (HPR) LU-LU session. This message is followed by information about the resource.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZNCVT command.
NDLU0013I | LU -- lunetid.luname PCID -- cpnetid.cpname.pcid |
Where:
Explanation: This is the normal response to the ZNDLU command when the command was entered to display information about a particular logical unit (LU) that contain in their associated resource vector table (RVT) entry a procedure correlation identifier (PCID).
System Action: None.
User Response: None.
See TPF Operations for more information about the ZNDLU command.
NDLU0014I | LU NOT FOUND |
Explanation: There are no logical units (LUs) that match the LU selection criteria specified in the ZNDLU command.
System Action: None.
User Response: Enter the ZNDLU command again, and specify different LU selection criteria.
See TPF Operations for more information about the ZNDLU command.
NDLU0016E | NO SESSION CONTROL BLOCKS EXIST FOR THIS LU |
Explanation: The ZNDLU command was entered with the MODE parameter specified but there are nospecified for the session control blocks (SCBs) associated with the specified logical unit (LU).
System Action: None.
User Response: Enter the ZNDLU command again and do not specify the MODE parameter.
See TPF Operations for more information about the ZNDLU command.
NDLU0017E | MODE KEYWORD NOT VALID EXCEPT WITH UNIQUE LUNAME |
Explanation: The ZNDLU command was entered with the MODE parameter specifed. This parameter can be specified only when the ID parameter is specified, followed by a unique logical unit (LU) name. A unique LU name is one that does not contain any wildcard characters.
System Action: None.
User Response: Do one of the following:
See TPF Operations for more information about the ZNDLU command.
NDLU0018E | INVALID NETID LENGTH IN ID PARAMETER |
Explanation: The ZNDLU command was entered with the ID parameter specified. However, the network identifier specified for the ID parameter contains more than 8 characters.
System Action: None.
User Response: Enter the ZNDLU command again, ensuring that the network identifier specified for the ID parameter contains no more than 8 characters.
See TPF Operations for more information about the ZNDLU command.
NDLU0019E | INVALID NODENAME LENGTH IN ID PARAMETER |
Explanation: The logical unit (LU) name specified for the ID parameter in the ZNDLU command contains more than 8 characters.
System Action: None.
User Response: Enter the ZNDLU command again ensuring the LU name specified for the ID parameter contains between 1 and 8 characters.
See TPF Operations for more information about the ZNDLU command.
NDLU0020E | INVALID PROCEDURE PARAMETER SPECIFIED |
Explanation: The ZNDLU command was entered with a value for the PROCEDURE parameter that is not valid. The value must be either BIND or UNBIND.
System Action: The ZNDLU command is rejected.
User Response: Enter the ZNDLU command and specify BIND or UNBIND for the PROCEDURE parameter.
See TPF Operations for more information about the ZNDLU command.
NDLU0021E | INVALID TYPE PARAMETER SPECIFIED |
Explanation: The ZNDLU command was entered with a value for the TYPE parameter that is not valid. The value must be 0, 1, 2, 3, 6.2, ANY, or PLU.
System Action: The ZNDLU command is rejected.
User Response: Enter the command again and specify a valid value for the TYPE parameter.
See TPF Operations for more information about the ZNDLU command.
NDLU0022E | INVALID ALS PARAMETER SPECIFIED |
Explanation: The ZNDLU command was entered with a value for the ALS parameter that is not valid.
System Action: None.
User Response: Enter the ZNDLU command again ensuring the name of an adjacent link station (ALS), network control program (NCP), or channel-to-channel (CTC) resource is specified for the ALS parameter.
See TPF Operations for more information about the ZNDLU command.
NDLU0023E | ERROR RETRIEVING ALS PARAMETER RVT ENTRY |
Explanation: An error occurred while trying to retrieve the resource vector table (RVT) entry associated with the adjacent link station (ALS) name, network control program (NCP) name, or channel-to-channel (CTC) name that was specified for the ALS parameter in the ZNDLU command.
System Action: None.
User Response: Check the RVT1 area for possible corruption.
See TPF Operations for more information about the ZNDLU command.
NDLU0024E | THE SPECIFIED ALS PARAMETER RESOURCE IS NOT ACTIVE |
Explanation: The adjacent link station (ALS), network control program (NCP), or channel-to-channel (CTC) resource specified for the ALS parameter in the ZNDLU command is not active.
System Action: None.
User Response: Enter the ZNDLU command again, ensuring that the ALS, NCP, or CTC resource specified for the ALS parameter is active.
See TPF Operations for more information about the ZNDLU command.
NDLU0025E | THE SPECIFIED ALS RESOURCE IS NOT AN NCP, ALS OR CTC |
Explanation: The value specified for the ALS parameter in the ZNDLU command is a valid resource name, but it is not the name of an adjacent link station (ALS), network control program (NCP), or channel-to-channel (CTC) resource.
System Action: None.
User Response: Enter the ZNDLU command again ensuring the name of an ALS, NCP, or CTC resource is specified for the ALS parameter.
See TPF Operations for more information about the ZNDLU command.
NDLU0026E | INVALID APPL PARAMETER SPECIFIED |
Explanation: The ZNDLU command was entered with a value for the APPLICATION parameter that is not valid.
System Action: None.
User Response: Enter the ZNDLU command again ensuring the name of a TPF application program or the value NS is specified for the APPLICATION parameter.
See TPF Operations for more information about the ZNDLU command.
NDLU0027E | ERROR RETRIEVING APPL PARAMETER RVT ENTRY |
Explanation: An error occurred while trying to retrieve the resource vector table (RVT) entry associated with the TPF application program that was specified for the APPLICATION parameter in the ZNDLU command.
System Action: None.
User Response: Check the RVT1 area for possible corruption.
See TPF Operations for more information about the ZNDLU command.
NDLU0028E | THE SPECIFIED APPL RESOURCE IS NOT AN APPLICATION |
Explanation: The ZNDLU command was entered with a value specified for the APPLICATION parameter that is a valid resource name but is not the name of a TPF application program.
System Action: The ZNDLU command is rejected.
User Response: Enter the ZNDLU command again ensuring the name of a TPF application program is specified for the APPLICATION parameter.
See TPF Operations for more information about the ZNDLU command.
NDLU0029E | THE SPECIFIED RTP INDEX IS NOT VALID |
Explanation: The ZNDLU command was entered with the RTP parameter specified, but the rapid transport protocol control block (RTPCB) index was not valid.
System Action: The ZNDLU command is rejected.
User Response: Enter the ZNDLU command again, specifying a valid value for the RTP parameter.
See TPF Operations for more information about the ZNDLU command.
NDLU0030E | REJECTED, SYSTEM IS BELOW 1052 STATE |
Explanation: You can enter the ZNDLU command only in 1052 state or higher.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZNDLU command.
NDLU0031I | BEGIN ZNDLU DISPLAY |
Explanation: This is the normal response to the ZNDLU command. This message is followed by a display of information about one or more logical units (LUs).
System Action: None.
User Response: None.
See TPF Operations for more information about the ZNDLU command and its display.
NDLU0032I | BEGIN ZNDLU DISPLAY |
Explanation: This is the normal response to the ZNDLU command when the command was entered to display information about a particular remote LU that has TPF Advanced Program-to-Program Communications (TPF/APPC) sessions.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZNDLU command.
NDYN0000E | PARAMETERS SPECIFIED FOR ZNDYN ARE NOT VALID |
Explanation: One or more of the parameters specified for the ZNDYN command are not valid.
System Action: The ZNDYN command is rejected.
User Response: Enter the ZNDYN command again specifying the correct parameters.
See TPF Operations for more information about the ZNDYN commands.
NDYN0004E | REJECTED, SNA RESTART IS NOT COMPLETE |
Explanation: You cannot enter the ZNDYN command until Systems Network Architecture (SNA) restart ends.
System Action: The ZNDYN command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZNDYN commands.
NDYN0005I | RVTS RECYCLED FROM TERMINATION LIST - xxxxxx RVTS NOW ON AVAILABLE LIST - yyyyyy |
Where:
Explanation: This is the normal response to the ZNDYN RECYCLE command.
System Action: The TPF system removes the RVT entries that are on the RVT termination list and places them on the RVT available list.
User Response: None.
See TPF Operations for more information about the ZNDYN RECYCLE command. See TPF ACF/SNA Data Communications Reference for more information about the RVT available list and the RVT termination list.
NDYN0006I | THERE ARE NO RVTS ON THE TERMINATION LIST |
Explanation: The ZNDYN RECYCLE command was entered when there were no resource vector table (RVT) entries on the RVT termination list to recycle.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZNDYN RECYCLE command. See TPF ACF/SNA Data Communications Reference for more information about the RVT termination list.
NDYN0020I | *** ZNDYN DISPLAY ALL *** |
Explanation: This is the normal response to the ZNDYN DISPLAY command with the ALL parameter specified. This message is followed by a display of statistical information about the distribution of resources in the resource name hash (RNH) tables.
System Action: The TPF system displays the requested information.
User Response: None.
See TPF Operations for more information about the ZNDYN DISPLAY command and an example of the informational display. See TPF ACF/SNA Data Communications Reference for more information about the RNH tables.
NDYN0030I | *** ZNDYN DISPLAY NAME *** |
Explanation: This is the normal response to the ZNDYN DISPLAY command with the NAME parameter specified. This message is followed by a display of information from the resource name hash (RNH) tables about the specified resource.
System Action: The TPF system displays the requested information.
User Response: None.
See TPF Operations for more information about the ZNDYN DISPLAY command and an example of the informational display. See TPF ACF/SNA Data Communications Reference for more information about the RNH tables.
NDYN0040I | *** ZNDYN DISPLAY RID *** |
Explanation: This is the normal response to the ZNDYN DISPLAY command with the RID parameter specified. This message is followed by a display of information from the resource name hash (RNH) tables about the specified resource.
System Action: The TPF system displays the requested information.
User Response: None.
See TPF Operations for more information about the ZNDYN DISPLAY command and an example of the informational display. See TPF ACF/SNA Data Communications Reference for more information about the RNH tables.
NDYN0050I | *** ZNDYN DISPLAY SYNONYM *** |
Explanation: This is the normal response to the ZNDYN DISPLAY command with the SYNONYM parameter specified. This message is followed by a display of information from the resource name hash (RNH) tables about the resources on the RNHET synonym chain for the specified resource.
System Action: The TPF system displays the requested information.
User Response: None.
See TPF Operations for more information about the ZNDYN DISPLAY command and an example of the informational display. See TPF ACF/SNA Data Communications Reference for more information about the RNH tables and the RNHET synonym chain.
NDYN0061E | NETID OR RESOURCE NAME CONTAINS TOO MANY CHARACTERS |
Explanation: The resource specified for the ZNDYN command contains too many characters in either the network identifier or the resource name.
System Action: The ZNDYN command is rejected.
User Response: Enter the ZNDYN 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 ZNDYN commands.
NDYN0062E | CANNOT LOCATE THE RNHPT FOR THE SPECIFIED RESOURCE |
Explanation: An error occurred while trying to locate the resource name hash prime table (RNHPT) entry for the specified resource.
System Action: The ZNDYN command is rejected.
User Response: See your system programmer for more information.
See TPF ACF/SNA Data Communications Reference for more information about the RNHPT entries.
NDYN0063E | RESOURCE NAME DOES NOT EXIST |
Explanation: The specified resource is not defined on this TPF processor. However, it may be defined on another processor in the loosely coupled TPF system.
System Action: The ZNDYN request is rejected.
User Response: Enter the ZNDYN command again and specify the name of a resource that is defined on this processor.
See TPF Operations for more information about the ZNDYN commands.
NDYN0064I | SPECIFIED RID IS FOR A SPARE RVT |
Explanation: The resource identifier (RID) specified for the ZNDYN DISPLAY command is the RID of a resource vector table (RVT) entry that is not currently assigned to a resource on this processor. It is a spare RVT entry.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZNDYN DISPLAY command. See TPF ACF/SNA Data Communications Reference for more information about spare RVT entries.
NDYN0065E | MUST SPECIFY A RID, SCBID NOT VALID |
Explanation: The value specified for the RID parameter in the ZNDYN DISPLAY command was a session control block identifier (SCBID), not a resource identifier (RID).
System Action: The ZNDYN DISPLAY command is rejected.
User Response: Enter the ZNDYN DISPLAY command again and specify a valid RID for the RID parameter.
See TPF Operations for more information about the ZNDYN DISPLAY command.
NDYN0066E | SPECIFIED RID IS NOT VALID |
Explanation: The resource identifier (RID) specified for the RID parameter in the ZNDYN DISPLAY command is not valid.
System Action: The ZNDYN DISPLAY command is rejected.
User Response: Enter the ZNDYN DISPLAY command again and specify a valid RID for the RID parameter.
See TPF Operations for more information about the ZNDYN DISPLAY command.
NDYN0070E | VALUE SPECIFIED FOR SUBAREA PARAMETER IS NOT IN THE RANGE OF 1-255 |
Explanation: The value specified for the SUBAREA parameter is not valid. It is not in the 1-255 range.
System Action: The ZNDYN request is rejected.
User Response: Enter the ZNDYN ADD or ZNDYN CHANGE command again and specify a valid subarea.
See TPF Operations for more information about the ZNDYN ADD and ZNDYN CHANGE commands.
NDYN0072E | RESOURCE IS NOT AN ALS, CTC, CDRM, OR NCP |
Explanation: The ZNDYN CHANGE command can be used to change the resource name of only an adjacent link station (ALS), channel-to-channel (CTC), cross-domain resource manager (CDRM), or network control program (NCP) resource.
System Action: The ZNDYN CHANGE command is rejected.
User Response: Enter the ZNDYN CHANGE command again and specify the name of an ALS, CTC, CDRM, or NCP resource for the OLD parameter.
See TPF Operations for more information about the ZNDYN CHANGE command.
NDYN0073E | SUBAREA PARAMETER NOT VALID WHEN CHANGING AN ALS RESOURCE |
Explanation: You cannot specify the SUBAREA parameter when changing the name of an adjacent link station (ALS) resource. ALS resources do not have a subarea.
System Action: The ZNDYN CHANGE command is rejected.
User Response: Enter the ZNDYN CHANGE command again and do not specify the SUBAREA parameter if you are changing the name of an ALS resource.
See TPF Operations for more information about the ZNDYN CHANGE command.
NDYN0074I | RESOURCE NAME oldname WAS CHANGED TO newname |
Where:
Explanation: This is the normal response to the ZNDYN CHANGE command.
System Action: The TPF system changes the name of the resource.
User Response: None.
See TPF Operations for more information about the ZNDYN CHANGE command.
NDYN0075I | SUBAREA FOR name WAS CHANGED FROM oldsub TO newsub |
Where:
Explanation: This is the normal response to the ZNDYN CHANGE command when it is entered to change the subarea as well as the name of a resource.
System Action: The TPF system changes the subarea of the resource.
User Response: None.
See TPF Operations for more information about the ZNDYN CHANGE command.
NDYN0077E | VALUE SPECIFIED FOR WINSIZE PARAMETER IS NOT IN THE RANGE OF 1-255 |
Explanation: The value specified for the WINSIZE parameter is not valid. It is not in the 1-255 range.
System Action: The ZNDYN ADD command is rejected.
User Response: Enter the ZNDYN ADD command again, and specify a valid value for the WINSIZE parameter or use the default value.
See TPF Operations for more information about the ZNDYN ADD command.
NDYN0078E | VALUE SPECIFIED FOR VRTO PARAMETER IS NOT IN THE RANGE OF 0-65535 |
Explanation: The value specified for the VRTO parameter is not valid. It is not in the 0-65 535 range.
System Action: The ZNDYN ADD command is rejected.
User Response: Enter the ZNDYN ADD command again, and specify a valid value for the VRTO parameter or use the default value.
See TPF Operations for more information about the ZNDYN ADD command.
NDYN0079E | VALUE SPECIFIED FOR VRILTO PARAMETER IS NOT IN THE RANGE OF 0-255 |
Explanation: The value specified for the VRILTO parameter is not valid. It is not in the 0-255 range.
System Action: The ZNDYN ADD command is rejected.
User Response: Enter the ZNDYN ADD command again, and specify a valid value for the VRILTO parameter or use the default value.
See TPF Operations for more information about the ZNDYN ADD command.
NDYN0080I | resname RESOURCE ADDED SUCCESSFULLY |
Where:
Explanation: This is the normal response to the ZNDYN ADD command.
System Action: The TPF system creates a resource definition for the specified resource.
User Response: None.
See TPF Operations for more information about the ZNDYN ADD command.
NDYN0081E | SUFFICIENT NON-LU RESOURCES ARE NOT AVAILABLE FOR ZNDYN ADD |
Explanation: The specified resource could not be added because the non-LU section in the resource vector table (RVT) is full.
System Action: The ZNDYN ADD command is rejected.
User Response: Increase the size of the non-LU section in the RVT by doing the following:
See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.
NDYN0082E | RESOURCE NOT ADDED, COULD NOT UPDATE NAT |
Explanation: The network address table (NAT) could not be updated with information about the specified resource. Therefore, the resource was not added to the TPF system.
System Action: The ZNDYN ADD command is rejected.
User Response: See your system programmer for more information.
See TPF ACF/SNA Data Communications Reference for more information about adding resources to the TPF system.
NDYN0083E | RESOURCE NAME ALREADY EXISTS |
Explanation: The specified resource name is already defined for another resource on this processor.
System Action: The ZNDYN command is rejected.
User Response: Enter the ZNDYN ADD or ZNDYN CHANGE command again and specify a unique resource name.
See TPF Operations for more information about the ZNDYN ADD and ZNDYN CHANGE commands.
NDYN0084E | SPECIFIED SUBAREA IS ALREADY IN USE |
Explanation: The specified subarea is already being used by another resource on this processor.
System Action: The ZNDYN command is rejected.
User Response: Enter the ZNDYN ADD or ZNDYN CHANGE command again and specify a subarea that is not already in use.
See TPF Operations for more information about the ZNDYN ADD and ZNDYN CHANGE commands.
NDYN0085E | THE SPECIFIED RESOURCE NAME WAS NOT FOUND |
Explanation: The old resource name specified for the ZNDYN CHANGE command does not exist on this processor.
System Action: The ZNDYN CHANGE command is rejected.
User Response: Enter the ZNDYN CHANGE command again and specify the name of a resource that exists on this processor.
See TPF Operations for more information about the ZNDYN CHANGE command.
NDYN0086E | CANNOT CHANGE THE NAME OF AN ACTIVE RESOURCE |
Explanation: The resource specified for the ZNDYN CHANGE command is active.
System Action: The ZNDYN CHANGE command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZNDYN CHANGE command.
NDYN0087E | MAXIMUM NUMBER OF CTC LINKS ALREADY DEFINED FOR THE SPECIFIED SUBAREA |
Explanation: The maximum number of channel-to-channel (CTC) links, which is 2, is already defined for the specified subarea.
System Action: The ZNDYN command is rejected.
User Response: Enter the ZNDYN ADD or ZNDYN CHANGE command again and specify a subarea that does not have the maximum number of CTC links defined.
See TPF Operations for more information about the ZNDYN ADD or ZNDYN CHANGE commands.
NDYN0088E | RESOURCE NAME CHANGED, BUT COULD NOT UPDATE NAT |
Explanation: An error occurred while changing the name of a resource. Although the resource name and subarea (if a new subarea was specified) were changed, the network address table (NAT) could not be updated.
System Action: Processing continues for the ZNDYN CHANGE command.
User Response: See your system programmer for more information.
See TPF ACF/SNA Data Communications Reference for more information about changing the name and subarea of a resource. See TPF Operations for more information about the ZNDYN CHANGE command.
NDYN0089E | CANNOT CHANGE THE NAME OF THE LOCAL SSCP |
Explanation: You cannot use the ZNDYN CHANGE command to change the name of the local system services control point (SSCP).
System Action: The ZNDYN CHANGE command is rejected.
User Response: None.
See TPF Operations for more information about the ZNDYN CHANGE command.
NDYN0090E | A CDRM RESOURCE IS NOT DEFINED FOR THE SPECIFIED SUBAREA |
Explanation: A cross-domain resource manager (CDRM) resource must be defined for the subarea that you specified when adding or changing the channel-to-channel (CTC) resource.
System Action: The ZNDYN command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZNDYN ADD and ZNDYN CHANGE commands.
NDYN0091E | CANNOT CHANGE THE SUBAREA OF A CDRM THAT HAS CTC LINKS DEFINED |
Explanation: The subarea for the specified cross-domain resource manager (CDRM) has channel-to-channel (CTC) links defined. Therefore, you cannot change the subarea for that CDRM resource.
System Action: The ZNDYN CHANGE command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZNDYN CHANGE command.
NDYN0092E | SPECIFIED RESOURCE NAME IS NOT VALID |
Explanation: The specified resource name contains characters that are not valid.
System Action: The ZNDYN command is rejected.
User Response: Enter the ZNDYN ADD or ZNDYN CHANGE command again and specify a valid resource name.
See TPF Operations for more information about the ZNDYN ADD and ZNDYN CHANGE commands.
NERR0050 | INVALID REQUEST TYPE USE EITHER DSPY OR ZERO |
Explanation: One of the following errors occurred:
System Action: The command is rejected.
User Response: Enter the command again and specify the correct request type or format.
See TPF Operations for more information about the ZNERR command.
NERR0055 | INVALID INPUT NSC ADDR |
Explanation: The native subchannel address (NSC) specified in the command could not be found in the 3705 keypoint record.
System Action: The command is ignored.
User Response: Verify that the NSC address was specified correctly. If it was not, enter the command again with the correct NSC address. If the NSC address was specified correctly, contact your system programmer about the problem.
See TPF Operations for more information about the ZNERR command.
NERR0060 | NO 3705S DEFINED TO SYSTEM |
Explanation: No 3705s were generated for this TPF system.
System Action: The input message is ignored.
User Response: None.
See TPF Operations for more information about the ZNERR command.