gtpm5m1yMessages (Online)

NCVT-NERR

NCVT0001IBEGIN 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.

NCVT0002EINVALID 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:

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

NCVT0003EINVALID 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.

NCVT0004EREQUESTED 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.

NCVT0005ENOT 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:

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

See TPF Operations for more information about the ZNCVT command.

NCVT0006EUNABLE 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.

NCVT0007IBEGIN 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.

NDLU0013ILU -- lunetid.luname PCID -- cpnetid.cpname.pcid

Where:

lunetid
The network identifier for the logical unit (LU).

luname
The name of the LU.

cpnetid
The control point network identifier for the procedure correlation identifier (PCID).

cpname
The control point name for the PCID.

pcid
The procedure correlation identifier.

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.

NDLU0014ILU 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.

NDLU0016ENO 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.

NDLU0017EMODE 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.

NDLU0018EINVALID 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.

NDLU0019EINVALID 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.

NDLU0020EINVALID 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.

NDLU0021EINVALID 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.

NDLU0022EINVALID 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.

NDLU0023EERROR 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.

NDLU0024ETHE 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.

NDLU0025ETHE 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.

NDLU0026EINVALID 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.

NDLU0027EERROR 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.

NDLU0028ETHE 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.

NDLU0029ETHE 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.

NDLU0030EREJECTED, 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:

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

See TPF Operations for more information about the ZNDLU command.

NDLU0031IBEGIN 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.

NDLU0032IBEGIN 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.

NDYN0000EPARAMETERS 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.

NDYN0004EREJECTED, 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:

  1. Wait for SNA restart to end.
  2. Enter the appropriate ZNDYN command again.

See TPF Operations for more information about the ZNDYN commands.

NDYN0005IRVTS RECYCLED FROM TERMINATION LIST - xxxxxx RVTS NOW ON AVAILABLE LIST - yyyyyy

Where:

xxxxxx
The number of resource vector table (RVT) entries removed from the RVT termination list.

yyyyyy
The number of RVT entries on the RVT available list.

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.

NDYN0006ITHERE 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.

NDYN0061ENETID 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.

NDYN0062ECANNOT 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.

NDYN0063ERESOURCE 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.

NDYN0064ISPECIFIED 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.

NDYN0065EMUST 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.

NDYN0066ESPECIFIED 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.

NDYN0070EVALUE 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.

NDYN0072ERESOURCE 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.

NDYN0073ESUBAREA 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.

NDYN0074IRESOURCE NAME oldname WAS CHANGED TO newname

Where:

oldname
The old resource name.

newname
The new resource name.

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.

NDYN0075ISUBAREA FOR name WAS CHANGED FROM oldsub TO newsub

Where:

name
The new name of the resource.

oldsub
The old subarea.

newsub
The new subarea.

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.

NDYN0077EVALUE 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.

NDYN0078EVALUE 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.

NDYN0079EVALUE 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.

NDYN0080Iresname RESOURCE ADDED SUCCESSFULLY

Where:

resname
The name of the resource.

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.

NDYN0081ESUFFICIENT 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:

  1. Increase the value assigned to the NUMALS parameter in the SNAKEY macro.
  2. Reload keypoint record 2 (CTK2).

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

NDYN0082ERESOURCE 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.

NDYN0083ERESOURCE 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.

NDYN0084ESPECIFIED 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.

NDYN0085ETHE 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.

NDYN0086ECANNOT 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:

  1. Deactivate the resource.
  2. Enter the ZNDYN CHANGE command again.

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

NDYN0087EMAXIMUM 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.

NDYN0088ERESOURCE 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.

NDYN0089ECANNOT 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.

NDYN0090EA 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.

NDYN0091ECANNOT 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:

  1. Determine the name of the CTC resources that have the same subarea as the CDRM resource that you specified.
  2. Enter the ZNDYN CHANGE command to change the name and subarea of those CTC resources.
  3. Enter the ZNDYN CHANGE command to change the name and subarea of the CDRM resource.

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

NDYN0092ESPECIFIED 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.

NERR0050INVALID 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.

NERR0055INVALID 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.

NERR0060NO 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.