When using an SNA standalone session with HCON, problems associated with the emulator may occur. Determine the source of a problem by reading the error message and finding the description in the "Error Messages for SNA Standalone Node T2.1,". The list of error messages also contains suggested remedies for each problem.
If the e789 program stops unexpectedly, look for a message beginning with the number 0789 displayed at the terminal. The message number is followed by text describing the error. If no message is displayed, look for a message in the $HOME/hconerrors file. The last (most recent) entry in the file contains the error message.
If an error message is displayed in the hconerrors file, find the message number in the following list and take the indicated action to remedy the error. If the message number is not described in the list, contact system support.
Note: The text of an error message may include the following types of numbers:
This list describes causes and remedies for errors that may occur when using SNA Services with HCON.
The list is divided into two types of messages:
0789-002 through 126Note: Several of the following solutions require contact with the Virtual Telecommunications Access Method (VTAM) administrator. The VTAM administrator may need to know the logical unit (LU) name, LU address, or station address for your session. This information can be obtained using SMIT to examine pertinent SNA Services profiles.The HCON session profile (SNA Logical Connection Profile characteristic) names the corresponding SNA Services Connection profile. The SNA Services connection profile names a local LU profile that in turn contains the LU address or LU name associated with your HCON session. The connection profile also names an attachment profile that in turn names a logical link profile. The Logical Link profile contains the Secondary Station address associated with your HCON session.
The (BIND failure) errors are designated by message numbers:
0789-129 through 192.Cause: The session names on the e789 command line are separated by blanks or additional characters follow the session names; for example:
e789 ab cd
e789 abcd%%
Remedy: Ensure all session names appear contiguously and no extraneous characters (other than shell operators, such as & (ampersand)) follow the session names; for example:
e789 abcd
e789 abcd &
Cause: An internal error occurred during HCON execution.
Remedy: Record the internal error code and contact system support.
Cause: More than 26 session names were entered on the e789 command line; for example:
e789 abcdefghijklmnopqrstuvwxyza
Remedy: Specify no more than 26 sessions on the e789 command line.
Cause: The fork, execl, or wait subroutine failed to initiate the HCON emulator session child process.
Remedy: The remedy depends on the error number specified in the error message:
Try the operation again. If the problem persists, record the error number and contact system support.
Note: The ls command will display the permissions of a file or directory. The chmod command can be used to change permissions.
Change the operating system parameters for user process limits or available memory (using smit).
Cause: The e789x or e789lus process for the indicated session exited abnormally. This error may be a side effect of another primary cause. This error may also arise from improper installation of the HCON program.
Remedy: Look for other messages just prior to 0789-010 in the $HOME/hconerrors file.
Verify that the e789x and e789lus files reside in the /usr/bin directory, that both files have read and execute permission, and that the /usr and /usr/bin directories have read and execute permission.
Try the operation again. If the problem persists, record the error number and exit code, and contact system support.
Cause: The shmat subroutine returned a negative value.
Remedy: If the error number is 12 (ENOMEM), there is not enough memory on the system to run HCON.
Change the operating system parameters for available memory (using smit) and try the operation again. If the problem persists, record the shared memory key and error number, and contact system support.
Cause: The execl subroutine failed to initiate the HCON utility (hconutil) child process.
Remedy: The remedy depends on the error number specified in the error message:
Use smit to change the operating system parameters (such as available memory).
Cause: The hconutil process ended with an unexpected exit code. This error is either due to program malfunction (from nonexistent or corrupted keyboard or color table files) or due to usage error.
Remedy: Stop and start the emulator and try the operation again. If the problem persists, record the exit code and contact system support.
Cause: Refer to message 0789-011.
Cause: The open subroutine returned a negative value. The message usually refers to the color table, keyboard mapping table, screen save, or screen replace files.
Remedy: The remedy depends on the error number specified in the error message:
For modifiable files (such as hconutil operations on the color and keyboard mapping table files), verify that the parent directory for the file has create and write permissions.
Cause: The ioctl subroutine was unsuccessful while attempting device driver status inquiry.
Remedy: Stop and start SNA Services again. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If this problem persists, record the error number and contact system support.
Cause: Refer to message 0789-026.
Cause: The malloc subroutine failed to obtain memory. The system has insufficient memory to run HCON.
Remedy: Use smit to change the operating system parameters (such as available memory).
Cause: The readx subroutine was unsuccessful.
Remedy: Try the operation again. If the problem persists, record the error number and contact system support.
Cause: The writex subroutine was unsuccessful.
Remedy: Try the operation again. If the problem persists, record the error number and contact system support.
Cause: A logical terminal interface (LTI) message that did not meet length criteria was sent to the e789x file.
Remedy: Stop and start the emulator and any LTI clients (for example, the fxfer command or API). If the problem persists, record the error number and contact system support.
Cause: An error occurred while retrieving an LTI message. For example, the msgrcv subroutine may have been unsuccessful. Necessary interprocess communication (IPC) resources may have been removed by either the e789cln or ipcrm command.
Remedy: Stop and start the emulator and any LTI clients (for example, the fxfer command or API). If the problem persists, record the error number and contact system support.
Cause: An error occurred while sending an LTI message. For example, the msgsnd subroutine may have been unsuccessful. Necessary IPC resources may have been removed by either the e789cln or ipcrm command.
Remedy: Stop and start the emulator and any LTI clients (such as, the fxfer command or API). If the problem persists, record the error number and contact system support.
Cause: The ioctl subroutine was unsuccessful while attempting to send sense code data to the host. This may have occurred while attempting to send an inbound Function Management (FM) header or a LUSTAT request to the host.
Remedy: Stop and start SNA Services again. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: The poll subroutine was unsuccessful.
Remedy: Stop and start the emulator. If the problem persists, record the error number and contact system support.
Cause: The maximum size of the inbound data buffer was computed incorrectly.
Remedy: Contact system support.
Cause: Neither a printer queue name nor a print file name was specified in the HCON profile for the indicated session.
Remedy: Provide a valid printer queue name or file name for the session profile and stop and start the emulator.
Cause: The open subroutine on the printer spooler file or on the print file name was unsuccessful.
Remedy: The remedy depends on the error number specified in the error message:
Try the operation again. If the problem persists, Record the file name and error number, and contact system support.
Cause: The new virtual terminal window size is too small to accommodate the alternate screen size.
Remedy: Size or open the window with a different font size. Ensure the number of rows and columns in the display space can accommodate the alternate screen size, given in the BIND (bytes 22-23 of the BIND image). Stop and start the emulator and try the operation again.
Cause: Unable to locate a stanza in the /etc/qconfig file that names the specified print spooler.
Remedy: Ensure the print spooler has been properly configured and is available for use. A stanza in the /etc/qconfig file contains the name of the print spooler. For additional information, refer to the "Printer Overview" in AIX Version 4.3 Guide to Printers and Printing.
Cause: The /etc/qconfig file is inaccessible to HCON.
Remedy: Ensure the /etc/qconfig file exists and has read permission.
Cause: The msgrcv subroutine was unsuccessful during the processing of a keyboard or Operator Information Area (OIA) event.
Remedy: Stop and start the emulator. If the problem persists, record the error number and contact system support.
Cause: The open subroutine was unsuccessful while attempting to access the device driver.
Remedy: Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: The SNA Services Logical Connection profile, named in the SNA profile of the indicated HCON session, does not exist.
Remedy: Verify that the SNA profile named is a valid Logical Connection profile.
Cause: The indicated file is not a valid color table definition file. The file is corrupted.
Remedy: Using the hconutil command, generate the color table file specified. Stop and start the emulator session. See the hconutil command for more information.
Cause: The read subroutine was unsuccessful, or the HCON keyboard-mapping or color-table file specified is not in a valid format. The file is corrupted.
Remedy: Using the hconutil command, generate either the keyboard-mapping or color table file specified. Stop and start the emulator session. See the hconutil command for more information.
If the error number is 4 (EINTR), 5 (EIO), 11 (EAGAIN), or 45 (EDEADLK), stop and start the emulator session.
For other errors, or if the message continues, record the error number and contact system support.
Cause: The indicated file is not a valid keyboard mapping definition file. The file is corrupted.
Remedy: Using the hconutil command, generate the specified keyboard mapping file. Stop and start the emulator session. See the hconutil command for more information.
Cause: The file system containing the directory for the session print file does not have enough space for the incoming print data.
Remedy: Extend the file system or remove unneeded files to free space. Examine the end of the print file. Ensure all data is intact. If not, submit the print job from the host again. Stop and start the emulator session and try the operation again.
Cause: This error arises when the pipe subroutine fails to create a pipe structure. For slow display devices, HCON attempts to create a pipe to buffer traffic between the emulator and the display.
The error is not fatal to HCON execution, but the integrity of the display may be compromised. Unreadable data may appear on slow display devices.
Remedy: If the error number is 23 (ENFILE) or 24 (EMFILE), stop and start the emulator. If the problem persists, record the error number and contact system support.
Cause: The close or dup subroutine was unsuccessful while performing operations associated with a slow display device pipe.
Remedy: If the error number is 24 (EMFILE), stop and start the emulator. If the problem persists, record the error number and contact system support.
Cause: The read subroutine was unsuccessful while attempting to get data from a pipe created to buffer output to a slow display device. This problem may arise from file-system damage.
Remedy: Stop and start the emulator and try the operation again. If the problem persists, record the error number and contact system support.
Cause: The write subroutine was unsuccessful while attempting to send data obtained from the output buffer pipe to the display. This problem may arise from file-system damage.
Remedy: Stop and start the emulator and try the operation again. If the problem persists, record the error number and contact system support.
Cause: The getch curses subroutine was unsuccessful while attempting to get data from the keyboard.
Remedy: Stop and start the emulator to reset the curses state that lead to the error. If the problem persists, record the error number and contact system support.
Cause: The msgsnd subroutine was unsuccessful while attempting to send an IPC message to the e789x file. This error may arise during procedures to show or hide a session displayed on the screen; for example, during processing for the NEXT key.
The error may also occur while handling a change in the virtual terminal window size, or while performing internal emulator shutdown protocols.
The necessary IPC resources may have been removed with either the e789cln or ipcrm command.
Remedy: Stop and start the emulator. If the problem persists record the error number and contact support personnel.
Cause: An open or dup subroutine was unsuccessful while attempting to open terminal standard in and out (file descriptors for input and output). The open was attempted in order to start an shell or to invoke the hconutil command.
Remedy: The remedy depends on the error number specified in the error message:
Cause: The ioctl subroutine was unsuccessful while attempting to initiate an SSCP-LU session (ALLOCATE) in response to a host ACTLU request.
Remedy: Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: The readx subroutine was unsuccessful while attempting to accept a host BID to begin a bracket.
Remedy: Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: The ioctl subroutine was unsuccessful while attempting to obtain a Resource ID (RID) from the SNA Services device driver. This error arises during the processing of control information:
Remedy: Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: The ioctl subroutine was unsuccessful while attempting to stop or recycle the SSCP-LU session (RSHUTD).
Remedy: Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: The ioctl subroutine was unsuccessful while attempting to return a RID to the SNA Services device driver. This error arises during the processing of control information:
Remedy: Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: The ioctl subroutine was unsuccessful while attempting to respond positively (CONFIRMED) to host data.
Remedy: Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: The ioctl subroutine was unsuccessful while attempting to flush the inbound data buffer and give execute permission to the host (PREPARE_TO_RECEIVE).
Remedy: Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: The half-duplex, flip-flop protocol was violated while in bracket state and during the LU-LU session. Host data arrived before HCON gave permission with a change-direction request.
Remedy: Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: An attempt was made to give the host execute permission while half-duplex, flip-flop protocol was not in effect (that is, outside bracket state).
Remedy: Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: The physical display space is too small to accommodate the default or alternate screen size specified in the BIND (bytes 20-23 of the BIND image).
Remedy: Enlarge the virtual terminal window or use a smaller font. Adjust the display space to have at least the number of rows and columns indicated in the text of the message. Stop and start the emulator and try the operation again. If the problem persists, contact system support.
Cause: The SNA Services server is not active.
Remedy: Ensure the SNA Services server is active. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the server is active, verify that the SNA profile named is a valid logical connection profile. Stop and start the emulator and try the operation again. If the problem persists, contact system support.
Cause: An unrecognized option on the e789 command line has been specified.
Remedy: Ensure only supported flags are used on the e789 command line, and try again.
Cause: The fork subroutine failed to initiate a child process for use as a shell.
Remedy: The remedy depends on the error number specified in the error message:
Change the operating system parameters for user process limits or available memory (using smit) and try the operation again. If the problem persists, record the error number and contact system support.
Cause: The fork subroutine failed to initiate a child process to execute the hconutil command.
Remedy: The remedy depends on the error number specified in the error message:
Change the operating system parameters for user process limits or available memory (using smit) and try the operation again. If the problem persists, record the error number and contact system support.
Cause: The pipe subroutine was unsuccessful while attempting to create a pipe to buffer screen data sent to the printer.
Remedy: If the error number is 23 (ENFILE) or 24 (EMFILE), stop and start the emulator.
If the problem persists, record the error number and contact system support.
Cause: The fork subroutine failed to initiate a child process to execute a print spooler queuing request.
Remedy: The remedy depends on the error number specified in the error message:
Change the operating system parameters for user process limits or available memory (using smit) and try the operation again. If the problem persists, record the error number and contact system support.
Cause: The print spooler queueing request was unsuccessful.
Remedy: Ensure the printer device file is correctly configured:
Test the configuration by using the print command, specified in the error message, to operate on a trial print file (explicitly from an shell prompt). If the print request is successful, the printer device file is correctly configured.
Stop and start the emulator and try the operation again. If the problem persists, record the print command and error number, and contact system support.
Cause: A QUIT key sequence has been issued. This message is a prompt to confirm an intent to stop the emulator session.
Remedy: Press the Ctrl-D key sequence to confirm the exit. Press any other key to resume the emulator session.
Cause: The tcgetattr, tcsetattr, or initscr subroutine was unsuccessful during the screen initialization procedure.
Remedy: If the error number is 19 (ENODEV) or 25 (ENOTTY), ensure the input device for the HCON utility is a valid, accessible terminal (not redirected from a pipe or file). Stop and start the emulator and try the operation again. If the problem persists, record the error number and contact system support.
Cause: The msgsnd subroutine failed to communicate with the hcondmn system while attempting to stop the session.
Remedy: Ensure the hcondmn system is active before starting any further emulator sessions. Enter:
'lssrc -s hcon'
from an shell prompt. If the problem persists, contact system support.
Cause: The msgsnd subroutine failed to communicate with the hcondmn system while attempting to initiate sessions.
Remedy: Ensure the hcondmn system is active. Enter:
lssrc -s hcon
from an shell prompt. If the problem persists, contact system support.
Cause: The access subroutine was not permitted to access the HCON terminfo file or the specified debug trace file.
Remedy: The remedy depends on the error number specified in the error message:
Try the operation again. If the problem persists, record the file name and error number, and contact system support.
Cause: The fstat subroutine failed to obtain the size of the HCON keyboard table file named.
Remedy: If the error number is 2 (ENOENT) or 14 (EFAULT), ensure the file exists in the directory specified in the session profile. Record the file name and error number, and try again. If the problem persists, contact system support.
Cause: The open subroutine was interrupted while attempting to access the device driver. This error may also be the result of a time out during an attempt to establish connections with communications equipment; for example, modems or controllers attached to the system.
Remedy: Verify that the interruption was not caused by process management functions (for example, a kill command or the Ctrl-C key sequence). Verify that the attached communication equipment is configured and functioning properly.
Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: Due to memory constraints, the open subroutine failed to access the device driver. There is not enough memory on the system to perform the open request.
Remedy: Change the operating system parameters for available memory (using smit), stop and start the emulator session, and try the operation again. If the problem persists, contact system support.
Cause: The open subroutine failed to access the device driver.
Remedy: Ensure the /dev/sna file exists and has read and write permissions.
Cause: The asynchronous terminal carrier has been dropped.
Remedy: Ensure the terminal being used is operational. Before trying the operation again, issue the e789cln command to stop the HCON sessions that were active on the ASCII terminal. This remedy will release the HCON resources.
Cause: The write subroutine failed to write data to the indicated HCON save file.
Remedy: The remedy depends on the error number specified in the error message:
Try the operation again. If the problem persists, record the file name and error number, and contact system support.
Cause: The write subroutine failed to write data to the indicated HCON replace file.
Remedy: The remedy depends on the error number specified in the error message:
Try the operation again. If the problem persists, record the file name and error number, and contact system support.
Cause: The write subroutine failed to write data to the print file for this session.
Remedy: The name of the print file is specified in the File to Store Printer Output characteristic in the HCON printer session profile.
The file is located in the user's home directory and is named e789pnn_xxxxx, where nn is the session number and xxxxx is the e789 process ID number.
The remedy depends on the error number specified in the error message:
Try the operation again. If the problem persists, record the file name and error number, and contact system support.
Cause: The shmat subroutine failed to attach to a shared memory segment while communicating with an LTI client (the fxfer command or API).
Remedy: If the error number is 12 (ENOMEM), there is not enough memory on the system to run the HCON utility.
Change the operating system parameters for available memory (using smit) and try the operation again. If the problem persists after starting the emulator and any LTI client, record the shared memory key and error number and contact system support.
Cause: The ioctl subroutine was unsuccessful while processing an attention request (REQUEST_TO_SEND).
Remedy: Try the operation again.
Stop and start SNA Services. Refer to SNA documentation on starting and stopping SNA Services before attempting to invoke the emulator.
If the problem persists, record the error number and contact system support.
Cause: Byte 1 of the BIND image is not set to 0x01.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Byte 2 of the BIND image is not set to 0x03.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Byte 3 of the BIND image is not set to 0x03.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 1 of byte 4 of the BIND image is set to B`1'. It should be set to B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bits 2 and 3 of byte 4 of the BIND image are set to B`00'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 6 of byte 4 of the BIND image is set to B`1'. It should be set to B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 7 of byte 4 of the BIND image is set to B`0'. It should be set to B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bits 2 and 3 of byte 5 of the BIND image are set to B`00'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 2 of byte 6 of the BIND image is set to B`0'. It should be set to B`1'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 3 of byte 6 of the BIND image is set to B`0'. It should be set to B`1'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 4 of byte 6 of the BIND image is set to B`1'. It should be set to B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bits 0 and 1 of byte 7 of the BIND image are not set to B`10'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 2 of byte 7 of the BIND image is set to B`1'. It should be set to B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 3 of byte 7 of the BIND image is set to B`1'. It should be set to B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 0 of byte 10 of the BIND image is set to B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 0 of byte 11 of the BIND image is set to B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: The HCON profile for the indicated session specifies a display session, and byte 14 of the BIND image is not 0x02 (LU type 2). The LU type and the HCON session type do not agree.
Remedy: Perform one of the following actions:
Remove the session from the HCON profiles and configure the session as a printer session.
Have the host VTAM administrator correct the LU type in the BIND image. Stop and start the emulator session indicated.
Cause: The HCON profile for the indicated session specifies a printer session, and byte 14 of the BIND image is 0x02 (LU type 2). The LU type and the HCON session type do not agree.
Remedy: Perform one of the following actions:
Cause: Byte 26 of the BIND image is not set to 0x00.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 0 of byte 5 of the BIND image is set to B`0' for LU type 2. It should be B`1'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Byte 10 of the BIND image specifies a maximum inbound RU request or response unit size less than 64 for LU type 2.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Byte 14 of the BIND image specifies a value other than 0x01, 0x02, or 0x03 (LU type 1, 2, or 3, respectively).
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 1 of byte 6 of the BIND image is set to B`1' for LU type 2 or 3. It should be B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Byte 24 of the BIND image is set to 0x01 for LU type 2 or 3.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Byte 24 of the BIND image is set to 0x03 for LU type 2 or 3 (screen size convention 03), and bit 0 of byte 15 of the BIND image is set to B`0'.
Remedy: Set Bit 0 of byte 15 to B`1' whenever screen size convention 03 is used. This convention determines the alternate screen size by query reply, which is only available in the 3270 extended data stream.
Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Byte 20 of the BIND image is set to a decimal value less than 24 for LU type 2 or 3.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Byte 21 of the BIND image is set to a decimal value less than 80 for LU type 2 or 3.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Byte 24 of the BIND image is set to a value other than 0x00, 0x02, 0x03, 0x7E (decimal 126), or 0x7F (decimal 127) for LU type 2 or 3.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 1 of byte 5 of the BIND image is set to B`1'. It should be B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 6 of byte 5 of the BIND image is set to B`1'. It should be B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.
Cause: Bit 7 of byte 5 of the BIND image is set to B`1'. It should be B`0'.
Remedy: Have the host VTAM administrator correct this value. Stop and start the emulator session indicated.