|
|
This chapter describes messages issued by Server Telnet. These messages include T01ST000 through T01ST999.
The TERMPROF logmode entry (LOGMODENAME) specified for this application either contains invalid, conflicting, or incompatible session parameters, or the entry does not exist in the ACF/VTAM xxxx.
The VTAMLIB data set name is the name of the logmode entry in error. Telnet session setup fails.
Recommended Action
Do one of the following:
Explanation The SIMPCS interface module could not be loaded. The session proceeds as if SIMPCS did not exist.
Recommended Action Check the log for the name of the module to be loaded and verify that the name was specified correctly in the SIMPCS parameter. Make sure the SIMPCS load module resides in either the Cisco IOS for S/390 JOBLIB/STEPLIB data set or in the system link list concatenation.
Explanation The SIMPCS interface loaded but would not honor the startup request from Cisco IOS for S/390. The session is terminated.
Recommended Action Check the log for SIMPCS-issued messages that may explain the cause of the failure.
Explanation The SIMPCS interface is operational and ready to accept logon requests. The session proceeds normally.
Explanation A SIMPCS interface request failed. The session is terminated.
Recommended Action Check the log for SIMPCS-issued messages that may explain the cause of the failure.
Explanation The Telnet client chose not to proceed with the SIMPCS session; in other words, the user entered L (logoff) to the SIMPCS request for the user's terminal type. The session proceeds as if SIMPCS did not exist, but in line mode only.
Explanation A network write request (ATPUTM), issued after recovery from a previous TERMINIT call, failed. The session is terminated.
Recommended Action Check the Cisco IOS for S/390 log for messages that may explain the cause of the failure.
Explanation A network solicit request (ATGET), issued after recovery from a previous TERMINIT call, failed. The session is terminated.
Recommended Action Check the Cisco IOS for S/390 log for messages that may explain the cause of the failure.
Explanation A network write request (ATPUT), issued after recovery from a previous TERMINIT call, failed. The session is terminated.
Recommended Action Check the Cisco IOS for S/390 log for messages that may explain the cause of the failure.
Explanation A client has signed on to the Sim3278/TCPIP facility. The local ACF/VTAM network name assigned by Cisco IOS for S/390 on behalf of the client is represented by lu_name; the client's IP address is represented by IPaddr. The session setup proceeds normally.
Explanation A Telnet open request for the specified host failed. The module that made the call is represented by mod_name; the completion code value indicates the cause of the failure and can be one of the following:
Explanation The attempt to open a server Telnet session with a VTAM application failed to complete successfully. Register 15 and 0 values are options fields.
These are the possible error codes:
| code1 | VLT applid. |
| code2 | ACB error code. |
| code3 | VLT error code (in hexadecimal):
|
|
code4 | Register 15 after OPEN request. |
| code5 | Register 0 after OPEN request. |
Recommended Action If the ACB error code is nonzero, read the IBM manual VTAM Reference Summary.
Explanation A VLT attempted an RPL-based VTAM request but the request failed. Destination applid (code6), register 15 (code2), and 0 (code3) values are option fields.
| code1 | RPL request type. |
| code2 | Register 15 after RPL request. |
| code3 | Register 0 after RPL request. |
| code4 | RPL return code. |
| code5 | RPL sense. |
| code6 | Destination applid. |
| code7 | VLT return code (refer to VLT codes defined in message T01ST013I). |
Recommended Action Verify that VTAM is functioning properly. Use the VTAM Reference Summary manual for an explanation of RPL codes.
Explanation A VTAM BIND was received but failed VLT's bind validity checking. The user session is terminated.
Recommended Action Verify that VTAM is functioning properly. Use the IBM manual, SNA Reference Summary, for a description of a bind format. Refer to message T01ST013I for an explanation of VLT return codes.
Explanation A VLT error was detected.
Recommended Action Verify that VTAM is functioning properly. Refer to message T01ST013I for an explanation of VLT return codes.
Explanation This message indicates a configuration error. A SERVICE statement has been defined for port port_num as AUTOlogon. However, no APPL statement has been defined for the AUTOlogon application.
Recommended Action Contact the Cisco IOS for S/390 administrator. An APPL statement must be defined to match the SERVICE statement. The APPL NAME must match the SERVICE AUTO parameter and the APPL PORT parameter must match the SERVICE PORT.
Explanation The LU pool facility attempted to acquire an LU name from and LU pool (lupool_name) for a user (user_id) from a remote host (remoteIP). All LU names identified in the pool are already allocated to other users. The request to access the VTAM application is denied and the user is returned to the Telnet prompt.
Recommended Action User may retry the Telnet command to acquire any deallocated LU name. The system administrator may add additional LU names to the LU pool identified in the message.
Explanation The LU pool facility was attempting to acquire an LU name for a user (user_id) from a remote host (remoteIP). The remote user could not match the criteria for any LURULE rule. The request to access the VTAM application is denied and the user is returned to the Telnet prompt.
Recommended Action Contact the system administrator and request a rule to access host applications.
Explanation During initialization of the APP task group, an error was encountered during LU pool processing of the LU pool configuration file APPLUPxx. No users are allowed access to host applications until the problem with the LU pool configuration is resolved. Other messages are displayed prior to this message describing the error(s) encountered while processing the configuration file.
Recommended Action Contact the system administrator to request correction of the problem. The system administrator must review the operator console log for messages describing the reason for initialization failure. After the problem has been resolved, from the operator console issue APP REFRESH LUPARM(mem_name).
Explanation An attempt to log user user_id in to the TCP/IP Telnet Server has failed.
Explanation When the module mod_name is VTAMTERM, the rest of the message describes information returned from VTAMTERM to STELTSO during a VTAM application session startup. This message, along with related message T01ST024I, only comes out when VLT ON has been set under ACTEST. These messages help debug VTAM session startup problems occurring between STELTSO and VTAMTERM.
The hex_vlt_code variable is the hexadecimal VLT return code in message T01ST013I.
Explanation User user_id (user_id may be Unknown) attempted to start a VTAM application session value1 with LU lu_name. The local host IP number and port follows the Local field; the remote host IP number and port follows the Remote field. This message only comes out when VLT ON has been set under ACTEST. These messages help debug VTAM session startup problems occurring between STELTSO and VTAMTERM.
Explanation A problem is encountered with the Telnet session during termination. The session is in graceful termination and is attempting to complete pending VTAM Queued Elements (VQE). A VQE did not complete the operation within a specific time interval. The session was then terminated without completing the VQE.
Recommended Action Review previous error messages for additional information. This is not a serious problem and generally no action is required.
Explanation A problem is encountered with the Telnet session and cannot be resolved. The Telnet session with the user is terminated.
Recommended Action Verify that the remote host is available and retry Telnet function.
Explanation Telnet attempts to negotiate a terminal as a 3278 and fails. The Telnet session with the user is terminated.
Recommended Action Verify that VTAM is working properly and that the terminal is capable of 3270 support.
Explanation The Telnet session exceeds the time allowed for remaining idle. The Telnet session with the user is terminated.
Recommended Action The terminal was allowed to remain idle for an excessive amount of time. The user must begin a new Telnet session.
Explanation The VTAM operator has canceled the user's Telnet session. The Telnet session with the user is terminated.
Recommended Action The VTAM operator probably is performing maintenance. Wait a few minutes and attempt another Telnet session.
Explanation The VTAM operator has canceled the user's Telnet session. The Telnet session with the user is terminated.
Recommended Action The VTAM operator probably is performing maintenance. Wait a few minutes and attempt another Telnet session.
Explanation The user explicitly requests termination of the Telnet session. Typically sessions are terminated with PF-keys or with the END command. The Telnet session with the user is terminated.
Explanation An attempt to read from the Telnet is unsuccessful. The return code from ATGET displays (code). (The definitions for the hexadecimal VLT error codes are included in the description of T01ST013I.) The user Telnet session terminates.
Recommended Action Verify that the remote host is functioning properly and retry Telnet session.
Explanation An attempt to write to the Telnet is unsuccessful. The return code from ATPUT is displayed (code).
Recommended Action Verify that the remote host is functioning properly and retry Telnet session.
Explanation VTAM message and error displays cannot be completed in a reasonable amount of time, causing the Telnet session to be found in error. The Telnet session with the user is terminated.
Recommended Action Verify that the remote host is functioning properly and retry Telnet session.
Explanation VTAM output queue cannot be processed within a reasonable amount of time, causing the Telnet session to be in error. The Telnet session with the user is terminated.
Recommended Action Verify VTAM is functioning properly.
Explanation While attempting to negotiate a 3278 terminal, a binary EOB control is encountered. The Telnet session with the user is terminated.
Recommended Action Verify that the terminal is capable of supporting the desired Telnet mode of operation. Verify that the remote host is capable of supporting this mode of operation.
Explanation While attempting to negotiate a 3278, an unidentified control code is encountered. The Telnet session with the user is terminated.
Recommended Action Verify that the terminal is capable of supporting 3270 protocols. Verify that the remote host is capable of supporting 3270 protocols.
Explanation An error is encountered while attempting to establish a Telnet connection. The return code from the ATOPEN is displayed (code). Refer to message T01ST011I for a detailed explanation of the return (reason) code.
Recommended Action Verify that the remote host is functioning properly.
Explanation The losterm exit was driven for the terminal. The Telnet session and user terminate.
Explanation A problem is encountered with the Telnet session during termination. The session is in graceful termination and is attempting to complete pending VTAM Queued Elements (VQE). A VQE did not complete the operation within a specific time interval. The session was then terminated without completing the VQE.
Recommended Action Review previous error messages for additional information. This is not a serious problem and generally no action is required.
Explanation The VTAMAPPL program in session with LU lu_name posted an error condition. The error code is given in post_code. The session is terminated.
Recommended Action Recurrence of this message may indicate an internal error. Save all output and contact Customer Support.
Explanation User user_id has successfully logged in to the TCP/IP Telnet Server.
Explanation User user_id has successfully logged in to the TCP/IP Telnet Server.
Failed, IMP down Explanation A user attempted to access the system through VTAM. The user access attempt failed.
Recommended Action The hardware interface to the product may be experiencing problems. Save all output from the job. Check the JES and T01LOG log files for related messages; check for any SVC dumps that may have been issued. Contact Customer Support.
Failed, Host hostname is down Explanation A user attempted to access the specified host (hostname) through the system via VTAM. The user access attempt failed.
Recommended Action Have your local network administrator verify status of the host.
logger is disabled Explanation A user attempted to access the system through VTAM. The user access attempt failed. The APP logger function has been disabled. This message is indicative of other problems inside the APP.
Recommended Action Save all output from the production job. Check the JES and T01LOG log files for related messages. Check for any SVC dumps that may have been issued. Contact Customer Support.
User protocol closed - protocol Explanation A user attempted to access the system through VTAM. The user requested the use of a protocol that was not available at the time. The user access attempt failed.
Recommended Action Have your local network administrator verify status of the specified protocol on the host. Save all output from the production job. Check the JES and T01LOG log files for related messages. Check for any SVC dumps that may have been issued. Contact Customer Support.
Unknown host number -> addressExplanation The user requested access to IP address address that was not known to the system. The user access attempt failed.
Recommended Action If this was a typing error, retry the correct IP address. If the IP address is valid, have your local network administrator verify the specified address with DNR. Issue the following TSO command and examine its output:
DNRGET HOST BYVALUE addressSave all output from the production job. Check the JES, SYSPRINT, and T01LOG log files for related messages. Check for any SVC dumps that may have been issued.
Unknown internet host -> hostname Explanation The user requested access to host (hostname) that was not known to the system. The user access attempt failed.
Recommended Action If this was a typing error, retry the correct host name. If the host name is valid, have your local network administrator verify The host name with DNR. Issue the following TSO command and examine its output:
DNRGET HOST BYNAME hostnameSave all output from the production job. Check the JES, SYSPRINT, and T01LOG log files for related messages. Check for any SVC dumps that may have been issued.
Error unknown name -> hostnameExplanation The user requested access to host (hostname) that was not known to the system. The user access attempt failed.
Recommended Action If this was a typing error, retry the correct host name. If the host name is valid, have your local network administrator verify the host name with DNR. Issue this TSO command and examine its output:
DNRGET HOST BYNAME hostnameSave all output from the production job. Check the JES, SYSPRINT, and T01LOG log files for related messages. Check for any SVC dumps that may have been issued.
Number out of range-> number Explanation The user requested access to the system but attempted access with a bad value (number). The user access attempt failed.
Recommended Action If this was a typing error, retry the correct host name. If the number is valid, contact your local network administrator. Save all output from the production job. Check the JES and T01LOG log files for related messages. Check for any SVC dumps that may have been issued.
outlog error -> message Explanation The user requested access to the system. The message request was in an incorrect format. The specified message (message) defines the error type. The user access attempt failed.
Recommended Action Retry the correct full syntax.
Syntax error -> parameter Explanation The user requested access to the system. The message request was in an incorrect format. The specified parameter (parameter) was found in error. The user access attempt failed.
Recommended Action Retry the correct full syntax.
Too many gateways Explanation The user requested access to a system via a gateway list. There were too many gateways in the list. The user access attempt failed.
Recommended Action Retry using a shorter list.
Refused by host -> hostname Explanation The user requested access to the specified host (hostname), the host refused access. The user access attempt failed.
Recommended Action Have your local network administrator verify that the specified host accepts logons from your node.
Outlog timeout Explanation The user requested access to a system but a timeout occurred before a connection could be made. The user access attempt failed.
Recommended Action Repeat the attempted access.
Explanation The user requested access to a system but failed. The specified message (message) may be indicative of the failure reason.
Recommended Action Have your local network administrator gather information on the problem.
Ambiguous name -> hostname Explanation The user requested access to the specified host (hostname) that was ambiguous. The user access attempt failed.
Recommended Action If this was a typing error, retry the correct host name. Have your local network administrator verify the host with DNR. Issue the following TSO command and examine its output:
DNRGET HOST BYNAME hostnameModify host definitions as necessary.
AHHP illegal Explanation The user access attempt failed.
Recommended Action Have your local network administrator save all output from the production job. Check the JES and T01LOG log files for related messages. Check for any SVC dumps that may have been issued. Contact Customer Support.
Invalid internal module name parm -> parameter Explanation The user attempted access to a module (parameter) but this module is not defined in the product as accessible. The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct syntax.
Syntax error, missing delimiter -> parameter Explanation The user requested access to host via a gateway list with a missing delimiter. The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct gateway list format.
Syntax error, bad port number syntax -> parameter Explanation The user requested access to a host on port parameter. The parameter was not a decimal number. The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct port number.
Syntax error, unknown keyword parameter -> parameter Explanation The user requested access utilizing keywords. The specified keyword (parameter) is not supported. The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct syntax.
Syntax error, PID parm is not decimal -> parameter Explanation The user requested access utilizing the PID keyword. The PID keyword (parameter) must be decimal. The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct syntax.
Syntax error, unknown HLP parameter -> parameter Explanation The user requested access utilizing the HLP keyword but used an unknown HLP (parameter). The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct HLP entry.
Syntax error, unsupported HLP protocol -> parameter Explanation The user requested access using the HLP keyword but attempted an unsupported protocol. The user used an unknown HLP (parameter). The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct HLP protocol.
Syntax error, IP parm is not decimal -> parameter Explanation The user requested access using the IP keyword. The IP keyword (parameter) has to be decimal. The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct syntax.
Syntax error, MYNET parm is not decimal -> parameter Explanation The user requested access using the MYNET keyword. The MYNET keyword (parameter) has to be decimal. The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct syntax.
Syntax error, Bad trailing characters -> parameter Explanation The user attempted access to a host but the specified characters (parameter) are in error. The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct syntax.
Syntax error, unknown host specified -> hostnameExplanation The user requested access to the specified host (hostname) that was not resolved. The user access attempt failed.
Recommended Action If this was a typing error, retry using the correct host name. Have your local network administrator verify the host with DNR. Issue the following TSO command and examine its output:
DNRGET HOST BYNAME hostnameModify host definitions as necessary.
Total gateways exceeded maximum Explanation Access was requested via a gateway list. The product only supports access via a gateway list up to five gateways only. The user access attempt failed.
Recommended Action Re-attempt access with fewer gateways.
Total source routes exceeded Explanation The user requested access via source routes. The product only supports access via one source route. The user access attempt failed.
Recommended Action Re-attempt access with one source route.
Syntax error, bad host specified -> hostnameExplanation The user requested access to the specified host (hostname) that was not resolved. The user access attempt failed.
Recommended Action If this was a typing error, the user should re-attempt using the correct host name. Have your local network administrator verify the host with DNR. Issue this TSO command and examine its output:
DNRGET HOST BYNAME hostnameModify host definitions as necessary.
APP option specified, but no application name entered Explanation A user invoked one of the client programs (TCPEEP, FTP, FTP2, or TELNET) utilizing the APP invocation option but no VTAM application name was entered. Client programs TCPEEP, FTP, or FTP2 then terminate. Client program TELNET uses the default VTAM application name.
Recommended Action Read the Cisco IOS for S/390 User's Guide for the syntax of the invocation option on the FTP and FTP2 commands; read the Cisco IOS for S/390 System Management Guide for information about the ACPEEP command. A user can issue the APPLID command under Client Telnet to change the VTAM application name.
APP name is longer than 8 characters vtam_app_name Explanation A user invoked one of the client programs (TCPEEP, FTP, FTP2, or TELNET) utilizing the APP invocation option, but the VTAM application name (vtam_app_name) was longer than eight characters. Client programs TCPEEP, FTP, or FTP2 then terminate. Client program TELNET uses the default VTAM application name.
Recommended Action Read the Cisco IOS for S/390 User's Guide for the syntax of the invocation option on the FTP and FTP2 commands; read the Cisco IOS for S/390 System Management Guide for information about the TCPEEP command. A user can use the APPLID command under Client Telnet to change the VTAM application name.
APP and SYS options specified, SYS option ignored Explanation A user invoked a client program (TCPEEP, FTP, FTP2, or TELNET) utilizing both the APP and SYS invocation options. The client program ignored the SYS option and used the APP option.
Recommended Action Read the Cisco IOS for S/390 User's Guide for the syntax of the invocation option on the FTP and FTP2 commands; read the Cisco IOS for S/390 System Management Guide for information about the TCPEEP command.
Explanation The service name entered at the Server Telnet prompt is not defined in the APPCFGxx member. If a TELNET DEFAULT statement has been coded, the name entered will be used as a VTAM APPLLID. A T01ST014 message will follow if the request fails.
Recommended Action If this is not a VTAM APPLID, check the spelling of the TELNET command. Also, verify that the service name is defined in your APPCFGxx member.
Connection Refused: Server Telnet port ppp not configured Explanation This message indicates a configuration error. A SERVICE statement has been defined for port ppp as AUTOlogon. However, no APPL statement has been defined for the AUTOlogon application.
Recommended Action Contact the Cisco IOS for S/390 administrator. An APPL statement must be defined which matches the SERVICE statement: the APPL NAME must match the SERVICE AUTO parameter and the APPL PORT parameter must match the SERVICE PORT.
NO LU AVAILABLE IN LUPOOL:lupool_name FOR USER:userid IP=ip_addr Explanation The LU pool facility was attempting to acquire an LU name for a user from a remote host. All LU names identified in the pool are already allocated to other users. The request to access the VTAM application is denied and the user is returned to the Telnet prompt.
| lupool_name | The pool from which the LU pool facility was attempting to acquire an LU name. |
| userid | The local logon ID used by the remote user to identify himself or herself to the local security system. |
| ip_addr | The IP address of the remote host. |
Recommended Action You can retry the TELNET command to acquire any deallocated LU name. The system administrator can add additional LU names to the LU pool identified in the message.
NO APPLICABLE LURULE FOR LU ASSIGNMENT FOR USER:userid IP=ip_addr Explanation The LU pool facility was attempting to acquire an LU name for a user from a remote host. The remote user could not match the criteria for any LURULE rule. The request to access the VTAM application is denied and the user is returned to the Telnet prompt.
| userid | The local logon ID used by the remote user to identify himself or herself to the local security system. |
| ip_addr | The IP address of the remote host. |
Recommended Action Contact the system administrator and request a rule to access host applications.
LUPOOL FACILITY NOT ACTIVE DUE TO INITIALIZATION ERROR Explanation During initialization of the APP task group, an error was encountered during LU pool processing of the LU pool configuration file APPLUPxx. No users are allowed access to host applications until the problem with the LU pool configuration is resolved. Other messages are displayed prior to this message describing the error(s) encountered while processing the configuration file.
Recommended Action Contact the system administrator to request correction of the problem. The system administrator must review the operator console log for messages describing the reason for initialization failure. After the problem has been resolved, the APP REFRESH LUPARM(member_name) must be issued from the operator console.
Explanation Program SPOOL#4 reads files off the JES spool destination defined on the REMOTE parameter in the SMTP statement in APPCFGxx. While attempting to read a record it discovered that the record length returned was larger than the LRECL of the JES data set. This is a permanent error preventing the full delivery of the mail message.
SPOOL#4 places error message T01ST084E into the truncated mail output data set in an attempt to inform the user that there was a problem in the delivery of this message.
Cisco IOS for S/390 issues messages T01S4004 and T01S4005 in T01LOG when this error occurs. Message T01S4005 will have the same JES data set name as in this message. Check for any related SVC dumps that may have been issued.
Recommended Action Look for defects in the application that places data sets on the JES spool. Specifically, look for instances where it could write blocks of data in which a record may be larger than the LRECL of the data set.
ENTER PASSWORD Explanation A TSO command is prompting for a password.
|
|