Chapter 118 TELSERV Messages

Cause  The internal allocation of memory buffers (MBUFs) has failed.

Effect  Data transfer may be slowed or may fail completely when memory cannot be allocated for data structures.

Recovery  Limit the data traffic or reduce the maximum number of windows allowed in the system. If the problem is recurrent, use the BIND program to rebind the Telserv process with a larger heap space.

file-number	is the file number of the TCP/IP or IPX/SPX process being accessed by the Telserv process for transmitting and receiving data when the read operation has failed. This file number is a temporary identification number used by system procedures to access the open file.
error	is the number of the TCP/IP socket error that has occurred. For a brief description of the error, at the TACL prompt, enter: > ERROR error For a more complete description of the error, see the TCP/IP Management Programming Manual.
win-spec	contains the name of the TELNET window that is the subject of this error message.

Cause  A read operation to the TCP/IP or IPX/SPX process has failed.

Effect  The window that attempted the read operation goes down and the connection to the remote system is severed.

Recovery  None. Establish a new connection.

file-number	is the file number of the TCP/IP or IPX/SPX process being accessed by the Telserv process for transmitting and receiving data when the write operation has failed. This file number is a temporary identification number used by system procedures to access the open file.
error	is the number of the TCP/IP socket error that has occurred. For a brief description of the error, at the TACL prompt, enter: > ERROR error For a more complete description of the error, see the TCP/IP Management Programming Manual.
win-spec	is the name of the TELNET window that is the subject of this message.

Cause  A write operation to the TCP/IP or IPX/SPX process has failed.

Effect  An error is reported to the application and the connection to the remote system is severed.

Recovery  None. Establish a new connection.

Cause  The Telserv process called the AWAITIO procedure during communication with the TCP/IP process, but an error occurred while the Telserv process was waiting for the operation to be completed on the socket.

Effect  The window goes down and the connection to the remote system is severed.

Recovery  If the window was added dynamically at the time the connection was established, you must establish a new connection. If the window was added with the ADD command, recovery is automatic and the window will be available to the next user who logs on.

Cause  The summary state of the Telserv process or TELNET window changed as a result of an operator command or an error.

Effect  If the summary-state change is the result of an error, one of Telserv operator messages 1 through 4 also occurs and provides additional information on the cause of the error.

Recovery  If a command caused the summary-state change, no corrective action is needed. If the state changed for any other reason, note the other error messages returned and contact your service HP representative. Provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The Telserv process detected an internal error and has halted.

Effect  The Telserv process no longer exists and must be restarted.

Recovery  Restart the Telserv process using the RUN command with SAVEABEND ON. Send the saveabend file to your HP representative for analysis.

Cause   An End-Of-File indication (socket error 0) was received on a read operation to the TCP/IP or IPX/SPX process.

Effect   The remote client has disconnected, causing the session to end and terminal win-spec to close.

Recovery   None. Establish a new connection.

Cause  The TELNET server process encountered an inconsistency in its internal program logic or data structures.

Effect  The TELNET server process will abend, leading to a loss of all on-going sessions with clients.

Recovery  If a backup process exists, it will take over processing. Otherwise, a new process will have to be started. In the former case, the backup process will automatically reconfigure itself with the latest PROCESS, SERVICE, and WINDOW configuration. In the latter case, existing SERVICE and WINDOW object configurations, other than the default, will have to be re-entered using SCF.

Cause  A connection was made to the host TELNET server process from a remote client.

Effect  Connection was successful.

Recovery  Not applicable.

Cause  A remote client has disconnected from the TELNET server process.

Effect  A disconnect has occurred and the session is now terminated.

Recovery  Not applicable.

Cause  Primary TELSERV process was forcefully brought down, aborted abnormally, or brought down with the CPU.

Effect  The primary TELSERV process went down, resulting in loss of all on-going sessions with clients.

Recovery  None. Establish a new connection. The backup process will automatically reconfigure itself with the latest PROCESS, SERVICE, and WINDOW configuration.

Cause  The login server failed due to reasons specified in the error and proc‑error fields of the message.

Effect  The user may be unable to login or the session may be terminated.

Recovery  Proc-errors 309 and 310 indicate login problems. Proc error 323 indicates that the time to login has expired; it is an informational message only and requires no user action. Proc-errors 315, 316, 317, 318, 319, 320, 321, and 322 indicate there is a problem with the password. For other proc-errors, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the number and versions of all related products as well.

Cause  An error occurred in an attempt to open the banner file.

Effect  The Telserv Welcome banner is not displayed.

Recovery  Examine the error code and correct the error condition, then restart the Telserv process.

Cause  An error occurred when an attempt was made to access the PROTOCOL or SERVICES file.

Effect  If Telserv was started on a TCP/IPv6 dual stack, Telserv switches to IPv4-only mode.

Recovery  Make sure that the PROTOCOL file or the SERVICES file is located in the $SYSTEM.ZTCPIP subvolume.

The message is logged once per hour during periods when an input or output operation is being retried.

Cause  Telserv detected an error when communicating with the OSS terminal helper server identified as objectname. If the error reported by errno is retryable, the most likely cause is either a system resource shortage on the processor used by either the OSS terminal helper server or the Telserv terminal process.

Effect  Applications that perform OSS file system input or output with terminals might not function properly.

If the error reported by errno is retryable, the communication is retried indefinitely, with increasing delays of up to 60 seconds between attempts. The message is logged once per hour during periods when an input or output operation is being retried.

Recovery  If the error reported by errno is retryable, stop other applications on the processors running the Telserv terminal process and the OSS terminal helper server to free resources. If the situation does not improve, then the processors running the Telserv terminal process and the OSS terminal helper server should be reloaded.