IBM Support

3270 session errors while using FTP client

Troubleshooting


Problem

An attempt to use the FTP client from TSO to a remote system produces errors associated with the 3270 protocol. This usually occurs when the client connects to the server or immediately after the logon sequence (after sending the password). Connections to other systems work with no errors.

Symptom

Messages produced can include:

  • IKT00405I SCREEN ERASURE CAUSED BY ERROR RECOVERY PROCEDURE
  • PROGxxx errors in the Operator Information Area of the terminal with the keyboard locked. PROG752 codes are the most likely.

Cause

The server is sending ASCII characters that are translated to EBCDIC codes that get interpreted as 3270 control sequences. The above errors occur as a result of these sequences not being valid in the current context. If the default translation tables are used, this condition is probably characters that are outside of the standard 7-bit ASCII character set.

Resolving The Problem

First, ensure that the correct translation table is used for the languages involved. If the proper code page sets are not defined, this can cause numerous problems with interpretation of messages sent from the server in addition to the above condition. Reference the IP Configuration Guide, IP Configuration Reference, and IP User's Guide manuals for your release for the invocation parameters, environment variables, FTP.DATA inputs, and default searches for selection of the translation tables used for the control session.

If the configuration is correct, one option is to create a modified translation table to use for the control session that translates all ASCII code points to a 3270 displayable EBCDIC character. The process to create a new table is described in the Translation Tables Appendix of the IP Configuration Reference. The HT (x'09'), LF (x'0A) and CR (x'0D') must remain translated to x'05', x'25' and x'0D' (respectively) to retain proper client operation. The following is a sample modification of the ASCII to EBCDIC section of the default translation table, which can be used for most US systems (it translates characters that cannot be displayed to question marks (?)):



The CCTRANS statement in the FTP.DATA input must specify a name by which the data set containing the updated translation table can be located. It is NOT recommended that this updated table be made the default translation table used on the system, because that can have unintended effects on other processes. Include an SBTRANS or SBDATACONN statement to ensure the data connection is not affected, such as:

    SBDATACONN FTP_STANDARD_TABLE

[{"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"All","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"1.6;1.7;1.8;1.9;1.10;1.11;1.12;1.13;2.1;2.2;2.3","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
15 June 2018

UID

swg21109052