Troubleshooting HCON

In maintaining HCON, you may need to address problems with:

• Host configuration
• Host configuration and the HCON session profile
• SNA Node T2.1 emulation using LU type 1, 2, and 3
• SNA Node T2.1 sense codes
• SNA Standalone Node T2.1

Problems with Host Configuration

Problem: The following HCON problems relate to the configuration of the host system and the control unit.

Host Panel Does Not Display on the Emulator

Problem: For a coaxial connection to a control unit, the host panel does not display on the emulator screen.

Press the Clear key and then the Enter key to receive the initial screen. If the screen does not display, check for and correct the following:

• OIA contains an error code indicating a problem.
• Coaxial cable is disconnected.
• Control unit (3174, 3274, 4361, or 9370) is not operational.
• Host channel address is configured for a device model number not supported by HCON.
• Network or terminal address for the session is configured incorrectly on the host.
• Control unit is configured incorrectly.

For more information, see "Configuring Hosts for HCON".

File Transfer Time Out on a Mainframe Host

Problem: The file transfer times out on a mainframe host.

Solution: Check for and correct the following:

• The PSERVIC field of the MODEENT macro is not set correctly for HCON.
• VTAM has not been started after changing the value in the PSERVIC field.
• The control unit for the emulator is not configured to support DFT terminals.
• An insufficient number of sessions have been allocated to the control unit port.

  Note: The emulator screen displays message 0789-114 as a result of any of the preceding configuration errors, a disconnected coaxial cable, or a control unit that has been turned off.

Program Checks Occur During File Transfer

Problem: Program checks occur during a file transfer while running an application program interface (API). This problem occurs under non-SNA DFT attachments when using the pvm or pass-through facility on the host if the Maximum I/O Buffer Size characteristic is greater than 3456 bytes.

Solution: Check and correct the Maximum I/O Buffer Size in the session profile.

Time Outs When Messages Are Longer Than 4096 bytes

Problem: The API or the file transfer times out when messages longer than 4096 bytes are sent to the host computer.

Solution: Refer to "Configuring Hosts for HCON" for the type of host or control unit involved.

Problems with Host Configuration and the HCON Session Profile

The following HCON problems relate to how the host configuration is reflected in the session profile.

+z_505 or +z_504 Is Displayed in the OIA

Problem: When running a SNA standalone session, +z_505 or +z_504 is displayed in the Operator Information Area (OIA).

Solution: This can occur if the SNA Services attachment is inactive.

• Check the status of all physical connections.
• Verify that the following are correct: SSCP ID and LU Address settings in the SNA Services Local Logical Unit profile, the NOTIFY SUPPORT setting in the SNA Services Local Logical Connection profile, the Secondary Station address in the SNA Services Logical Link profile, and the XID Node ID setting in the SNA Services Control Point profile.
• Check the connection profiles activity. For information on starting and stopping SNA Services, refer to SNA documentation. If the profiles are not active, verify all profile settings and report the problem using your local problem reporting procedures.

SNA Session Handshaking (BIND) Fails

Problem: The SNA session handshaking (BIND) fails.

Solution: Review any BIND-related messages displayed on the screen or in the $HOME/hconerrors file. Report the error using your local problem reporting procedures.

Problems with SNA Node T2.1 Emulation Using LU Type 1, 2, and 3

The following HCON problems relate to SNA Node T2.1 emulation using LU type 1, 2, and 3. The diagnosis may apply to either a SNA standalone (Node T2.1) display or a printer session.

Note: Several of the following solutions require contact with the Virtual Telecommunications Access Method (VTAM) administrator.

The VTAM administrator may need to know the 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.

Problem: The emulator displays a blank screen at startup. The OIA ready indicators are 2 < .

If this is a display session, then the NOTIFY SUPPORT setting may not have been specified in the SNA Services LU Connection profile for this session. If this is a printer session, then no further action is necessary because this condition is normal when an SNA standalone printer session is in conversation with the SSCP.

Problem: For a display session, press the Enter key to see the SSCP screen. To avoid this problem in the future, set NOTIFY SUPPORT to yes in the SNA LU Connection Profile for this session. The HCON session profile (SNA Logical Connection Profile characteristic) names the corresponding SNA Services connection profile.

Emulator Displays a Blank Screen

The emulator displays a blank screen. The OIA ready indicators are 2 ? or 2B? . An X -f (unavailable function) indicator appears whenever an AID key is pressed. The communications link may have been varied off by the host.

Contact the VTAM administrator to check the line status and to vary it on, if necessary.

LU Definition Messages and OIA Indicators (2B<) Are Displayed

Problem: The SNA standalone display session shows the following messages and OIA indicators:

This LU is defined as a printer (LU 1 or LU 3). On a display
enter command with an override for the log mode name.

Enter application access code or logon command.

The OIA ready indicators are:

2B<

The host VTAM configuration and HCON session type disagree.

Solution: Perform one of the following operations:

• Remove this session profile from the HCON profiles and reconfigure it as a printer session.
• Contact the host VTAM administrator to change the host VTAM definition to LU type 2.

084B0000 Sense Code Received

Problem: The host indicates that a 084B0000 sense code was received for certain LUs while initiating communication with SNA Services.

The message displayed at the host will be similar to:

ERROR FOR ID=NDMLU - REQUEST: ACTLU, SENSE: 084B0000

In this example, the host sent an ACTLU to LU name NDMLU, whose LU address was not defined in any of the SNA Local Logical Unit profiles associated with the attachment (PU).

Solution: This is a normal occurrence. The host sends ACTLUs to request activation of each LU defined for a given PU (as determined by the VTAM definition).

In the event that some of these LUs do not have a corresponding Local Logical Unit and connection profile definitions for the attachment in SNA Services, the host ACTLU requests for these LUs are rejected by SNA with a 084B sense code.

Note: The error does not affect the HCON SNA standalone session operation.

0831 Sense Code Received During Printer Session

Problem: The host's print spooler indicates a 0831 sense code was received from an HCON SNA standalone printer session.

Solution: The independent LU setting in the SNA Services Local LU profiles is incorrect for the HCON printer session.

Perform one of the following operations:

1. Export your SNA profiles. From a local system prompt, enter:

   exportsna -f /tmp/snaprofs

   Substitute the name of any desired file to hold the exported data for /tmp/snaprofs .
2. Edit the exported profiles using a text editor. Change all occurrences of independent_lu = yes in your LU 1, 2, and 3 Local Logical Unit profile descriptions to independent_lu = no .

   If you have no LU6.2 logical units, use the global search and replace options. For example,

   %s/independent_lu = yes/independent_lu = no/g

   can be entered from the vi : (colon) line.
3. Import your modified profiles. At the local system prompt, enter:

   importsna -l /tmp/snaprofs

   Substitute the file name used in step 1 for the /tmp/snaprofs portion.
4. Verify your imported profiles. At the local system prompt, enter:

   verifysna

5. To activate the changes, restart the SNA server. For information on starting and stopping SNA Services, refer to the SNA documentation.

Invalid Session Parameter Specified

Problem: Host print spooler encounters an error similar to the following while attempting to send data to an HCON SNA standalone session:

INVALID SESSION PARAMETER PSERVIC SPECIFIED

The host VTAM configuration and HCON session type disagree.

Solution: Perform one of the following operations:

• Remove this session profile from the HCON profiles and reconfigure it as a display session.
• Contact the host VTAM administrator to change the host VTAM definition for this LU to be LU type 1 or 3.

Host Data Rejected

Problem: HCON SNA Standalone LU type 1 (standard character set (SCS)) printer session rejects host data. The OIA ready indicators 2B" and the 756 program check, X PROG756 , can be seen briefly before the printer session unbinds (returning to the SSCP session).

The host print spooler may indicate the print request was rejected with a 1003 sense code.

The host VTAM definition for the printer session LU may have specified Function Management Header (FMH) support while the host print application did not properly format SCS printer data for FMH transmission.

Solution: Perform one of the following operations:

• Contact the VTAM administrator to change the VTAM definition for the LU so that the FMH support will be disabled.
• Use a host print application that sends properly formatted SCS data and the FMHs.

SNA Node T2.1 Sense Codes

The sense codes in the following table describe SNA standalone (Node T2.1) conditions only.