C H A P T E R 2 - 3270 Client Messages

C H A P T E R 2

3270 Client Messages

This chapter lists messages generated by the 3270 client and the 3270 client initiator.

3270 Client Messages

Messages in this section are preceded by the module name of the 3270 client, unikixb, followed by the SNA server's name, the logical unit name, and an SNA session number that identifies the session with the SNA server. The message format is as follows:

[unikixb:SNA_SERVER:SLU31:20] Message

These messages appear only on the terminal screen of the UNIX host that executed unikixb. These messages can be redirected to a log or error file by using a redirection operator (>). Refer to your UNIX command reference on the shell for more information about redirection.

In general, if a condition cannot be recovered, the 3270 terminal will return to the system services control point (SSCP) login screen.

In the description of the messages, %d is replaced by an integer value, %x by a hexadecimal value, and %s by a string of characters.

ACTLU

Description: The logical unit has received the command to activate. This message might be the result of network operator action. No action is required.

All terminals assigned

Description: The Sun MTP region has the maximum number of configured terminals logged on. This message, without the prefix, also appears on the 3270 screen.

Solution: The configuration must be changed or other users logged off to allow access.

Argument Error from parent process! narg = %d

Description: The terminal handler was unable to obtain its arguments from the unikixi command.

Solution: Report this error to your authorized service provider.

Bid -rsp %x sen %x %x

Description: The terminal handler attempted to gain control of the secondary logical unit but was denied.

Solution: No action is required. The state of the terminal might be such that it is not ready to start another transaction. If the problem persists, report this error to your authorized service provider.

Bind failed

Description: An attempt to bind the session between the Sun MTP application and the terminal handler failed.

Solution: Report this error to your authorized service provider. Retry the operation.

Close failed close LU error: errno=%d, brx5_errno=%lx

Description: A closed session to the Sun MTP region resulted in an error.

Solution: Report this error to your authorized service provider. Recover the terminal by entering a dialog with the SSCP and logging out and in. Press the SYS REQUEST key, type logoff, and press the Enter key. Then log back in.

Closedown error

Description: An error has occurred on the message flow.

DACTLU

Description: The logical unit has received the command to deactivate. This message might be the result of network operator action.

Solution: No action is required.

DFC req ru_code %x dat %x %x %x %x

Description: An unexpected data flow control command was received on the LU-to-LU session, and was ignored.

Solution: Report this error to your authorized service provider.

Error returned from read socket: %d

Description: An error, identified by %d, occurred on a socket read.

Solution: Report this error to your authorized service provider. Retry the operation.

Error Reading Piped Arguments

Description: The terminal handler was unable to obtain its arguments from the unikixi command.

Solution: Report this error to your authorized service provider.

Error Retrieving Bind data

Description: The terminal handler was unable to obtain the required bind data from the unikixi command.

Solution: Report this error to your authorized service provider.

Error sending sc_msg

Description: An error occurred attempting to send a session control message to the secondary logical unit.

Solution: Report this error to your authorized service provider.

Fail to get machine name

Description: A call to UNIX failed to make a valid return.

Solution: Report this error to your authorized service provider. Retry the operation.

Fail to create socket for host computer

Description: A request to allocate an Internet domain socket was denied.

Solution: Report this error to your authorized service provider. Retry the operation.

Fail to create socket for terminal handler

Description: A request to allocate an Internet domain socket was denied.

Solution: Report this error to your authorized service provider. Retry the operation.

Get socket failed errno %d

Description: A request to allocate an Internet domain socket was denied.

Solution: Report this error to your authorized service provider. Retry the operation.

gethostbyname failed

Description: A request to get the host name of the computer running the terminal handler failed.

Solution: Report this error to your authorized service provider. Retry the operation.

getsockname failed

Description: A request to obtain the socketname was denied.

Solution: Report this error to your authorized service provider. Retry the operation.

habtRcls kxsndts failed %d

Description: An attempted communication between the terminal handler and the region was unsuccessful. The communication path between the terminal handler and the region might no longer exist.

Solution: Report this error to your authorized service provider.

hread_sockm: kxsndts failed

Description: An attempted communication between the terminal handler and the region was unsuccessful. The communication path between the terminal handler and the region might no longer exist.

Solution: Report this error to your authorized service provider. Retry the operation.

Ign SC req ru_code %x

Description: An unexpected command has been received on the SSCP-to-LU session and has been ignored.

Solution: Report this error to your authorized service provider.

Ign unknown req ru_code %x

Description: An unknown command has been received on the LU-to-LU session and has been ignored.

Solution: Report this error to your authorized service provider.

Ign req ru_code %x

Description: An unexpected command has been received on the LU-to-LU session and has been ignored.

Solution: Report this error to your authorized service provider.

Invalid FD For Piped Arguments

Description: The terminal handler was unable to obtain its arguments from unikixi.

Solution: Report this error to your authorized service provider.

Invalid KXmsg type %d

Description: The terminal handler received a message of an unknown type %d, which has been ignored.

Solution: Report this error to your authorized service provider. Retry the operation.

Logo file error

Description: The logo file is invalid. The terminal handler will not start until this condition is corrected.

Solution: Make sure that you have a logo file in $UNIKIX/lib/logofile, and that the permissions on it are set so that the processes can read it. If the problem persists, report this error to your authorized service provider.

Memory allocation failed

Description: The terminal handler was denied a request to allocate memory.

Solution: Report this error to your authorized service provider. Retry the operation.

Nonzero return code from kxsndts: %d

Description: An attempt to communicate from the terminal handler to Sun MTP has been unsuccessful.

Solution: Report this error to your authorized service provider.

Open LU, internal error = %d

Description: An internal error in the SNA server has been detected.

Open failed

Description: An open session to the TPS PU5 server resulted in an error.

Solution: If this message is received immediately after starting unikixi, the applid specified on the command line (-u xxxx) was not defined in the TPS PU5 configuration file. Please verify your configuration file and command line arguments before restarting unikixi.

If unikixi is started successfully and the error is displayed after connecting a 3270 terminal, recover the terminal by entering a dialog with the SSCP and logging out and in. Press the SYS REQUEST key, type logoff, and press the Enter key. Then log back in.

If the problem persists, report this error to your authorized service provider.

Protocol error state %d event %d

Description: An error has occurred on the message flow.

Read command error

Description: An error has occurred on the message flow.

Req -rsp %x sen %x %x

Description: The terminal handler made a request of the secondary logical unit, which was refused.

Solution: Report this error to your authorized service provider.

Select rcode %d errno %d

Description: A UNIX call to wait for activity on file descriptors failed.

Solution: Report this error to your authorized service provider. Retry the operation.

Send_dfc_msg failed

Description: An error occurred attempting to send a data flow control message to the secondary logical unit.

Solution: Report this error to your authorized service provider.

Send_fmd_data failed

Description: A send of data to the Sun MTP system resulted in an error.

Send_ru failed Write to brxPU5 error: errno=%d, brx5_errno=%lx

Description: A send of data to the Sun MTP system resulted in an error.

Serial file error

Description: The serial number control file is invalid. The terminal handler will not start until this condition is corrected.

Solution: Report this error to your authorized service provider.

Server Disconnected

Description: The SNA server disconnected unexpectedly.

Solution: Report this error to your authorized service provider.

SIGINT

Description: The terminal handler received an interrupt signal requesting that it exit. This message will occur if the unikixi process is killed.

Solution: No action is required.

Socket read returned zero length

Description: A read from a socket returned no data.

Solution: Report this error to your authorized service provider. Retry the operation.

Socket read returned %d

Description: An error, identified by %d, occurred on a socket read.

Solution: Report this error to your authorized service provider. Retry the operation.

SSCP-LU req ru_code %x

Description: An unexpected command has been received on the SSCP-to-LU session and has been ignored.

Solution: Report this error to your authorized service provider.

Start up error

Description: An error has occurred on the message flow.

Terminal closed by host

Description: Advisory message indicating that the Sun MTP system has closed the session with the terminal. This might be at the terminal operator's request. This message without the prefix also appears on the 3270 screen.

Solution: No action is required.

Unable to locate GTA

Description: The Sun MTP system has been unable to locate an internal control structure for the terminal. This message, without the prefix, also appears on the 3270 screen.

Solution: Report this error to your authorized service provider. Retry the operation.

Unable to connect to LU

Description: The SNA server denied connection to the requested LU.

Solution: Report this error to your authorized service provider. Retry the operation.

Unable to open file: %s

Description: The terminal handler was unable to open a required file.

Solution: Make sure that the user ID that started the unikixi process has write permission to the directory where the file is being opened. If the problem persists, report this error to your authorized service provider.

Unavailable LU

Description: An open session to the SNA server resulted in an error.

MTP already running on this terminal

Description: This terminal was previously connected to Sun MTP and has been disconnected in an abnormal manner. This message without the prefix also appears on the 3270 screen.

Solution: Execute the CEMT SET TERM ( . . . ) OUTSERVICE transaction. Wait and retry the login operation. This condition should clear.

3270 Client Initiator Messages

Messages in this section are preceded by the module name of the 3270 client initiator, unikixi. Following this is the name of the Sun MTP host and the name of the SNA server. The error message format is:

[unikixi:KIXHOST:SNA_SERVER] Error message

If the names of KIXHOST and SNA_SERVER are unknown at the time the error occurs, the name fields are filled with question marks. For example:

[unikixi:?????:?????].

These messages are displayed only on the screen of the UNIX host that is executing the 3270 client initiator. They are output to standard error, but you can redirect them to a log or error file by using a redirection operator (>). Refer to your UNIX command reference on the shell for more information about redirection.

In the description of the following error messages, %d will be replaced by an integer value, %x by a hexadecimal value, and %s by a string of characters. In addition to the symbols, certain messages are followed by system-dependent descriptive messages that further identify the error condition.

CINIT User-Data Length Too Long: Truncating

Description: The UDATA field of the SNA CINIT message received was larger than the maximum expected.

Solution: Resubmit the login command. Limit the number of characters in the UDATA field to eight.

CLOSE ERROR %d

Description: A file close error was detected while closing a pipe between the unikixi and unikixb processes.

Solution: Report this error to your authorized service provider.

Could Not Acquire Memory for Child Process Table Entry: %s

Description: The malloc() system call failed due to the reason shown in %s.

Solution: Report this error to your authorized service provider.

Could not open socket to SNA Server %s

Description: The unikixi process was unable to open a socket to connect to the SNA server.

Cause: The TCP/IP process on the local system is not behaving properly, or has too many connections currently established.

Solution: Verify that the SNA server is executing and functioning properly. Retry the operation. If the problem persists, report it to your authorized service provider

Disconnecting SNA Interface

Description: Notification to terminal users that the Sun MTP region is not available.

Cause: An error in the connection between the KIXHOST system and the unikixi process has forced the unikixi process to disconnect the SNA server.

Solution: Restart the Sun MTP region.

dup() call: %s

Description: The dup() system call failed for the reason shown in %s.

Solution: Report this error to your authorized service provider.

Error %d Reading KIXHOST Socket

Description: An error was detected while reading the socket connection to KIXHOST.

Error Received Sending KX-message = %d

Description: An internal error occurred while trying to send a message to the KIXHOST system.

Solution: Report this error to your authorized service provider.

Error in -C confirm option

Description: The -C confirm option allows one of three parameters: Display, Printer, or Both.

Error Reading KIXHOST Socket!

Description: An error occurred while attempting to read the socket connected to the system named in the KIXHOST environment variable.

Solution: Make sure that the system named in $KIXHOST is a valid system and is operational.

Error Sending INIT-SELF: errno %d

Description: An error was detected while trying to send an INIT_SELF SNA message to the PU5 software.

Solution: Make sure that the PU5 software is running properly.

execlp(): %s

Description: The execlp() function failed due to the reason shown in %s.

fork() failed: %s

Description: The fork() system call failed due to the reason shown in %s.

gethostbyname() failed: %s

Description: The gethostbyname() function failed due to the reason shown in %s.

gethostname() failed: %s

Description: The gethostname() system call failed due to the reason shown in %s.

getsockname() failed %s

Description: The getsockname() system call failed due to the reason shown in %s.

Illegal Command Line Argument Detected

Description: An unknown command line argument was used when starting the unikixi process. Refer to the Sun Mainframe Transaction Processing Software Reference Guide for a list of command line arguments.

Internal Error In remove_child_pid(). No such pid as %d

Description: An internal unrecoverable error was detected within the unikixi process. The process automatically kills itself.

Solution: Report this error to your authorized service provider.

Internal Error in sna_open_request() brx5_errno= %d

Description: An internal error has occurred within the unikixi process.

Solution: Report this error to your authorized service provider.

IP bind failed: %s

Description: The bind() system call failed due to the reason shown in %s.

KIXHOST %s Has Established Connection!

Description: This message appears after the unikixi process establishes a connection to the system named in $KIXHOST.

LU not active on open reply

Description: An unexpected error occurred during the opening of a PU5 SSCP port.

Solution: Report this error to your authorized service provider.

NEGATIVE RESPONSE RECEIVED

Description: A negative response was received from the PU5 software.

No Response from KIXHOST %s. Waiting...

Description: When the $KIXHOST system specified in %s is determined to be down, the unikixi process continually attempts to reestablish the connection. This message appears periodically until the connection is reestablished.

Open LU, internal error = %d

Description: An internal error occurred in the PU5 software.

Solution: Verify that the APPLID specified on the command line for Sun MTP
(-u sextets) is defined to the TPS PU5 server. Restart the PU5 software.

If this problem persists, report the error to your authorized service provider.

pipe() failed: %s

Description: The pipe() system call failed due to the reason shown in %s.

[remove_child_pid] INTERNAL ERROR pid = %d hashslot = %d

Description: A catastrophic, unrecoverable error occurred within the unikixi process. The process automatically kills itself.

Solution: Report this error to your authorized service provider.

Secondary LU-LU sess msg rcved

Description: An unexpected LU-LU message was received by the unikixi process.

Signal() failed: %s

Description: The signal() system call failed due to the reason shown in %s.

SNA Server %s is Unknown

Description: The SNA server system named in %s (either the local system or the system specified with the -b command line option) is not known to TCP/IP.

SNA Server %s not a registered service

Description: The SNA server software was not properly installed on the specified system (either the local system or the system specified with the -b command line option).

SNA Server %s Has Not Responded in %d Minutes. Waiting...

Description: When the unikixi process detects that the SNA server is no longer communicating, it attempts to reestablish a connection at some predetermined interval.

SNA Server %s Not Responding. Waiting...

Description: The SNA server PU5 software is not responding to requests being made by the unikixi process.

Solution: Restart the PU5 software.

SNA interface disconnected

Description: The PU5 SSCP has disconnected abruptly without warning.

Solution: Restart the PU5 software.

socket() failed: %s

Description: The socket() system call failed for the reason shown in %s.

SSCP Port Unavailable

Description: An attempt to open a connection to the PU5 SSCP failed because the port for the SSCP was unavailable. The port for the PU5 SSCP is probably hung.

Solution: Stop and restart the PU5 software.

SSCP-LU sess msg rcved

Description: An unexpected SSCP-LU message has been received from the PU5 software.

Unexpected msg %x received from MTP

Description: An unexpected message was received by the unikixi process. The message is discarded and normal operation continues.

Unexpected Error from select() %s

Description: The select() system call failed for the reason shown in %s.

Write to child pipe failed: %s

Description: The write() system call failed for the reason shown in %s.

Solution: Report this error to your authorized service provider.

Retry the operation. Recover the terminal by entering a dialog with the SSCP and logging out and in. Press the SYS REQUEST key, type logoff, and press the Enter key. Then log back in.