|
|
|
Reason:
The value, P1 , specified for the CMD operand of TNCMD is not supported.
System Action:
The command is ignored
User Action:
Correct the CMD operand to specify one of the following values:
AYT - Are You There
AO - Abort Output
BRK - Break
IP - Interrupt Process
Reason:
The value, P1 , specified for the COMMAND operand of $TNCALL is not supported.
System Action:
The command is ignored
User Action:
Correct the COMMAND operand to specify one of the following values:
TELNET - Start a TELNET session
TNSEND - Send data on a session
TNCMD - Send a TELNET command
TNDISC - Terminate a session
Reason:
The value, P1 , specified for an operand of $TNCALL is not supported.
System Action:
The command is ignored
User Action:
Correct the operand to specify one of the following values:
COMMAND=TELNET - Start a TELNET session
COMMAND=TNSEND - Send data on a session
COMMAND=TNCMD - Send a TELNET command
COMMAND=TNDISC - Terminate a session
Reason:
A null value has been specified for the operand.
System Action:
The command is ignored
User Action:
Specify a value for the named keyword.
Reason:
The port number is not an integer in the range 1 to 65535.
System Action:
The port number is set to 23 (TELNET).
User Action:
If a port other the TELNET standard port number of 23 is to be used then the PORT keyword value must be an integer in the range 1 to 65535.
Reason:
The control character cannot be an alphabetic or numeric character.
System Action:
The control character is set to › (cent sign).
User Action:
Restart the session using a special character that will not be required to be sent to the remote host.
Reason:
A TELNET command has specified a session ID that is not active.
System Action:
The command is ignored
User Action:
Correct the ID to specify an active session.
Reason:
A send to the TELNET process has failed. This is most likely due to a
short on storage condition.
System Action:
The command is ignored
User Action:
Retry the command.
Reason:
The command keywords contain a syntax error. The following message (prefix N23I) indicates the reason.
System Action:
The command is rejected
User Action:
Correct the operands to specify a keyword=value syntax. Use 'command ?' to display the command syntax.
Reason:
The command keyword does not specify a valid partitioned dataset member name.
System Action:
The operand is ignored. The default TRTAB will be used. If the call is ACTION=INIT then the value is set to 'US'.
User Action:
Correct the operand to specify a valid member name.
Reason:
The value, P1 , specified for the ACTION operand of $TNCALL is not supported.
System Action:
The command is ignored
User Action:
Correct the ACTION operand to specify one of the following values:
TELNET - Start a fullscreen Telnet session
COMMAND - Perform a Telnet command
Reason:
A TELNET request has specified an operand with a value that is not supported. P1 is the keyword and P2 is the unrecognized value.
Valid values for the COLOUR or COLOR keyword are: RED WHITE BLUE GREEN YELLOW PINK TURQUOISE
Valid values for the HLIGHT or HLITE keyword are: NONE USCORE BLINK REVERSE
Valid values for the MODAL, TRACE keywords are: YES NO
The valid value for the ENTER keyword is: CRLF CR
System Action:
The parameter is ignored.
User Action:
Reissue the command with a valid value for keyword P1 .
Reason:
A TNSHOW command has been issued and there are no active Telnet sessions or there are no sessions that match the selection criteria.
System Action:
None
User Action:
None
Reason:
A TNSHOW command has been issued. This is the first heading line.
System Action:
None
User Action:
None
Reason:
A TNSHOW command has been issued. This is the second heading line.
System Action:
None
User Action:
None
Reason:
A TNSHOW command has been issued. The Telnet session details are:
P1 UserID
P2 IP address
P3 session duration
P4 bytes received from host
P5 bytes sent from user to host
P6 The session ID
System Action:
None
User Action:
None
Reason:
A TNSHOW command has been issued. This line displays the full host name of the host.
System Action:
None
User Action:
None
Reason:
The user identified by P1 is not authorized to use the NetMaster TELNET component.
System Action:
The TELNET request is rejected.
User Action:
Contact your security administrator.
Reason:
The TRTAB keyword has been specified and no partitioned dataset has been defined for the location of translate table members.
System Action:
The operand is ignored. Default ASCII/EBCDIC translation will occur.
User Action:
You can use the Miscellaneous Parameters option of the NetMaster for TCP/IP Administration menu to define a dataset that contains translation table members.
Reason:
A Telnet request cannot proceed. The target address is IPv6, but the sockets API on region P1 supports IPv4 addresses only.
System Action:
The action terminates.
User Action:
Check the SOCKETS parameter group (/PARMS) on region P1. For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
This the end of output message for a Telnet show command.
System Action:
None
User Action:
None
Reason:
A TELNET process has been started using translate table P1. The member has been read from the translate table dataset P2 and is being processed.
System Action:
The ASCII to EBCDIC table and EBCDIC to ASCII table are built.
User Action:
Use the TRTAB operand on the TELNET command to select the translation table to use for each session. TCP/IP stack contains translate tables for common languages and code pages.
Reason:
A TELNET process has been started using translate table P1. The member read from the translate table dataset P2 does not contain sufficient data to build the necessary tables. The member should contain the source form of tables used for TCP/IP.
System Action:
The ASCII to EBCDIC table and EBCDIC to ASCII table are built using default values.
User Action:
1. Check that the TRTAB on the TELNET command is correct.
2. Verify the translation dataset specified during initialization is correct.
3. Check the log for messages indicating that the dataset could not be processed.
Reason:
The TELNET translation table dataset, p1 , has been allocated using the specified DDname, p2 .
System Action:
The dataset is opened and the TRTAB member read.
User Action:
None
Reason:
The TELNET translation table dataset has not been unallocated. P1 indicates the reason.
System Action:
None
User Action:
Use the reason to determine why the dataset failed to unallocate.
Reason:
An error occurred reading the translation dataset. The dataset services feedback code is indicated by P1 . P2 is the dataset services error message.
System Action:
The member is not processed and default ASCII to EBCDIC and EBCDIC to ASCII translation tables are built.
User Action:
Use the error information to determine why the dataset read failed.
1. Check that the TRTAB on the TELNET command is correct.
2. Verify the translation dataset specified during initialization is correct.
Reason:
An MDO error occurred using map P1 . P2 is the MDO return code and
P3 is the feedback.
System Action:
Dataset Services actions are not performed.
User Action:
1. Report the failure to your system administrator.
2 Use the error information to determine why the MDO usage failed. Check that Dataset Services maps are available - Use option D.M and list $DS maps. $DSCBD1Z, $DSCBD2Z and $DSCBD3Z should appear in the list. If not, Management Services maintenance should be applied.
3. If necessary contact your product support representative.
Reason:
An attempt has been made to start a TELNET session with an ID that is already in use.
System Action:
The session is not started
User Action:
Use the ID operand of the TELNET command to specify a unique session identifier. Use this identifier on the TNSEND, TNCMD and TNDISC commands
Reason:
A TELNET process has been started for host P2 using session ID P1.
System Action:
TCPIP services are allocated and the host is contacted.
User Action:
Use TNSEND, TNCMD and TNDISC commands with the session identifier to manage the session.
Reason:
A TELNET process has been started using TRACE=YES. The message text is one of the three indicated formats. The first two formats are heading lines that display the direction relative to the terminal of the data flow and P1 its length. The third format is a dump of the datastream that is repeated until the entire datastream is displayed. The fields are:
P1 - the offset into the datastream
P2-P5 - the hexadecimal display of the ASCII characters
P6 - the EBCDIC character form of the data
Note: Where data has been entered using the Hide function of the fullscreen interface or using TRACESUP=YES then the datastream is replaced by the characters '**SUPPRESSED**'.
System Action:
None
User Action:
Use the trace output to verify session operation is as desired.
Reason:
A TELNET process has received an error indication while freeing TCPIP resources. P1 and P2 are the return values from SOCKET DEALLOCATE.
System Action:
Processing continues
User Action:
Report the error to your product support representative
Reason:
A TELNET process has ended.
System Action:
None
User Action:
None
Reason:
A TELNET process is about to connect to host P1 using port P1.
System Action:
SOCKET CONNECT is issued
User Action:
None
Reason:
A Telnet process has connected to host P1.
System Action:
SOCKET RECEIVE is issued to receive data from the host.
User Action:
Wait for the host to prompt for input.
Reason:
A TELNET process has connected to a host. P1 is the IP address of the remote host and P2 is the full name.
System Action:
None
User Action:
None
Reason:
A TNDISC command has been processed by TELNET.
System Action:
The session is terminated.
User Action:
None
Reason:
The value, P1 , received by the TELNET process for CMD is not supported.
System Action:
The command is ignored
User Action:
Contact your product support representative.
Reason:
The data received by the TELNET process is not recognized.
System Action:
The data is ignored
User Action:
Contact your product support representative.
Reason:
The TELNET translate table in use has produced a character of 'FF'X. This is treated as an error indication.
System Action:
A dump of the original datastream is written to the log with message ID TNVT0113. The invalid characters are translated to blanks. (ASCII '20'X)
User Action:
Use the trace output to verify session operation is as desired.
Reason:
This message follows a TNVT012 message in the activity log. An invalid ASCII character has been detected. This message contains a dump of the datastream before translation. The second form of the message is repeated until the entire datastream is displayed. The fields are:
P1 - the offset into the datastream
P2-P5 - the hexadecimal display of the ASCII characters
P6 - the EBCDIC character form of the data
System Action:
The invalid characters are replaced by spaces.
User Action:
Refer to the earlier TNVT0112 message which indicates the offset into the datastream of the character in error. If necessary specify a different translate table on the Telnet invocation.
Reason:
A TELNET SOCKET verb has indicated an error condition. P1 is the verb which failed. P2, P3 and P4 indicate the error received. P5 is the vendor-specific error information which further qualifies ERRNO ( p4 ).
P6 and P7 are interpretations of the error codes indicating the reason for the failure.
System Action:
The TELNET process is terminated.
User Action:
Use the error information to determine the cause of the error. If necessary restart the session.
Reason:
A TELNET process could not be started because TCP/IP services are not active.
System Action:
None.
User Action:
Use SHOW TCPIP STATUS to determine the interfaces state. If necessary issue TCPIP START to activate the interface.
Reason:
The TELNET connection request was not responded to by the peer host within one minute.
System Action:
The TELNET process terminates.
User Action:
Use the PING command to determine if the peer host is reachable.
Reason:
The Telnet connection was closed by the peer host. This is a normal message if you have logged off from a host.
System Action:
The Telnet process terminates.
User Action:
Check that SYSPARMS TELNET=YES is set on the remote SOLVE region.
Reason:
An invalid command has been entered.
System Action:
The process waits for input from the terminal.
User Action:
Correct the command and retry or clear the command field.
Reason:
A backward scroll was requested but the display is already positioned at the top of the data.
System Action:
None.
User Action:
None.
Reason:
A forward scroll was requested but the display is already positioned at the bottom of the data.
System Action:
None.
User Action:
None.
Reason:
An invalid value has been entered in a field capable of accepting a valid scroll amount value.
System Action:
None.
User Action:
Correct the error and retry. Valid scroll values are P(age), H(alf), C(ursor), D(ata) and any positive numeric value up to 100000.
Reason:
An &NTSVIEW verb has been used to obtain APPN session route data for a specified session. The &NTSVIEW verb has failed due to the view being invalid.
System Action:
None.
User Action:
Return to a higher level view and retry.
Reason:
A request to display information about an active session has been rejected because the session is no longer active. All information about the session has been removed from storage.
System Action:
None.
User Action:
View the session using a History display which shows information stored in the NTSLOG file.
Reason:
An &NTSREAD verb has been used to obtain APPN session route data for a specified session. The &NTSREAD verb has failed due to the view being invalid.
System Action:
None.
User Action:
Return to a higher level view and retry.
Reason:
A request to display APPN session route information for a session has failed because there is no such information available. This indicates that the information provided by VTAM indicates that the session does not involve any APPN networks.
System Action:
None.
User Action:
None.
Reason:
A request to display APPN session route information for a session has resulted in an incomplete display because no RSCV information has been provided by VTAM. The session awareness information indicates that the session does involve APPN, and a Route Selection Control Vector was expected because the session involves more than one Control Point. This can occur if the session was active before NTS was started - VTAM does not actually remember the RSCV for any session so if NTS is started after the session VTAM cannot supply this information.
System Action:
The APPN session route display shows as much information as it can without the additional data from the RSCV.
User Action:
None.
Reason:
This line precedes a hex/character dump of a Route Selection Control Vector which was used to build an NTS APPN Session Route Display. The display is terminated by message TSAR11. This display is sent to the SOLVE activity log when the RSCVDUMP command is entered in the command line of the APPN Session Route display. It may be used to obtain the RSCV for problem determination purposes at the request of your product supplier.
System Action:
None.
User Action:
None.
Reason:
This line terminates a hex/character dump of a Route Selection Control Vector which was used to build an NTS APPN Session Route Display. The display is headed by message TSAR10.
System Action:
None.
User Action:
None.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |