Troubleshooting tips

1. Connecting to z/OS console via Z and I Emulator for Windows 62x160 screen size results in error IEE938I

Problem
IEE936I CONSOLE HHSP0141 INITIALIZATION ERROR - RC:01 - 3277-2 IS ASSUMED is logged by z/OS console when using HCL Z and I Emulator for Windows version 6.0.2 with a 62x160 screen size.
Cause

z/OS console connection is being made through the OSA-ICC telnet server. This server does not support the Terminal Type of IBM-DYNAMIC.

APAR IC71220 changed the default Terminal Type string passed to the telnet server for screen sizes greater than 27x132.

Resolution

To use 62x160 screen size display sessions with OSA-ICC telnet servers, take the following steps:

  1. Edit the WS session profile.
  2. Add the following statements under the Telnet3270 stanza to force HCL Z and I Emulator for Windows to use the original default string:
    [Telnet3270]
    TerminalTypeString=IBM-3278-2-E

2. Z and I Emulator for Windows TCP/IP Data Transfer fails with terminated transfer function

Problem
TCP/IP Data Transfer might fail with the error "Transfer function will be terminated". This message provides a checklist for iSeries or AS/400 host requirements.
Resolution

To resolve this problem, take the following steps to check the status of the iSeriesTM or AS/400® host requirements:

  1. Confirm that the iSeries or AS/400 host has the following required licensed program(s) installed (type GO LICPGM and select Option 10 - Display Installed Licensed Programs: ):
    For V5Rx:
    5722TC1 *BASE iSeries TCP/IP Connectivity Utilities/400
    5722SS1 Option 12 OS/400 ® - Host Servers
    
    For V4R5:
    5769TC1 *BASE TCP/IP Connectivity Utilities for AS/400
    5769SS1 Option 12 OS/400 - Host Servers
  2. Verify that you have a Relational Database entry for YOURSYSTEM at REMOTE Location = *LOCAL (issue the command WRKRDBDIRE to "Work with Relational Database Directory Entries"):
    RELATIONAL DATABASE . . . . . . : YOURSYSTEMNAME
    REMOTE LOCATION:
    REMOTE LOCATION . . . . . . . : *LOCAL
    TEXT . . . . . . . . . . . . . . :
  3. Verify that user ID QUSER is enabled (issue the following command for profile QUSER):
    WRKUSRPRF USRPRF(QUSER)
  4. Verify that TCP/IP is active, using the following command (This is required before any TCP/IP processing):
    START TCP/IP (STRTCP) COMMAND
  5. If you have not already done so, issue the following "Start Host Server" command:
    STRHOSTSVR SERVER(*ALL)
    RQDPCL(*TCP) 

The following sets of instructions are to verify that the required server daemon and prestart server jobs are active for DDM, Database, and File Transfer functions.

  1. For DDM, take the following steps:
    1. Verify that the DDM daemon is active. Use WRKACTJOB to find the QRWTLSTN job under QSYSWRK. This daemon is automatically started when the STRTCP command is run, if the AUTOSTART parameter is set to *YES on the CHGDDMTCPA command <F4>. If the daemon does not start when the STRTCP command is run, you can start the daemon by issuing the following command:
      STRTCPSVR SERVER(*DDM)
      Note:
      If the DDM daemon still fails to start with error message CPF3E30, refer to APAR SA81267.
    2. Verify that the DDM prestart server jobs are active. Use WRKACTJOB to find the server jobs named QRWTSRVR. For V5R2 and newer releases, the prestart jobs run in the QUSRWRK subsystem, but can be configured to run under other subsystems. They are automatically started with the subsystem. If these jobs are not active, you can issue the start prestart job command STRPJ <F4>. For host versions prior to V5R2, these jobs runs in the QSYSWRK subsystem.
  2. For Database, take the following steps:
    1. Verify that the subsystem for the Database server daemon is active. The subsystem is QSERVER, and the daemon job is named QZDASRVSD.
    2. Verify that the Database prestart server jobs are active. For V5R1 and newer releases, the prestart jobs are QZDASOINIT and QZDASSINIT. Both jobs run in the QUSRWRK subsystem, but can be configured to run under other subsystems. As with the DDM prestart jobs, these jobs are automatically started with the subsystem, but if they are not active, they can be started with the STRPJ command.
    3. If port 8478 is not active, end and restart the Database server job QZDASRVSD using the following commands:
      ENDHOSTSVR *DATABASE
      STRHOSTSVR *DATABASE
  3. For File Transfer, take the following steps:
    1. Verify that the subsystem for the transfer function server is active. The subsystem is QSERVER, and the daemon job is named QZDASRVSD.
    2. Verify that the transfer function prestart server jobs are active. The prestart job is QTFPJTCP. This job runs in the QSERVER subsystem.

3. Z and I Emulator for Windows Telnet connection timeout with error 657

Problem
Keyword for Telnet timeout.
Resolution

Z and I Emulator for Windows uses non-blocking sockets when connecting to a remote system. By default, Z and I Emulator for Windows waits for 3 seconds to establish the socket connection. When accessing remote terminals over a dialup network, this default wait time might not be sufficient and could lead to a connection failure and return the error 657.

The default time can be changed by adding the following keyword to the Telnet3270 or Telnet5250 stanza of the workstation profile:

[Telnet3270]
InactiveTimeout=xx

The value xx is the time in seconds and can take any positive numerical values.

4. PCSXFER041 timeout during Z and I Emulator for Windows file transfer TSO session

Problem
Three situations might cause a timeout at the Z and I Emulator for Windows client and a solution is provided for each case.
Cause
Resolution

CUT mode transfer

By default, Z and I Emulator for Windows uses DFT mode for transfers to and from a TSO host. When using Dial to connect to TSO, the host might be configured to do the transfer in CUT mode, while Z and I Emulator for Windows is still in DFT mode.

You can modify the workstation profile that you use to dial the TSO session. To manually change the DFT/CUT setting, add the following case-sensitive line to the Transfer stanza of the workstation file:

[Transfer]
CUTprotocol=Y

You can also change the LU description on the zSeries host. Change the VTAM BIND image so that the Write Structured Field query support bit is set in the PSERVIC. Refer to the VTAM documentation for more information.

Using \FT trigger in SuperSession Manager

If you encounter the timeout problem when using Supersession, you can use the \FT trigger before logon. This can be applied on an individual user and session basis.

The \FT trigger invokes the file transfer script KLSXFER, which enables query passthru. It also inhibits immediate broadcasts and session locking.

Document mode and Word Wrap mode

If Document mode or Word Wrap mode is enabled, the file transfer will fail. If you have a key mapped to toggle this feature on or off, turn it off before initiating the file transfer. If you want to disable this feature, change the following case-sensitive line in the ENTRYASSIST stanza of the workstation file:

[ENTRYASSIST]
DocmodeWordWrap=N

Appendixes