SBCS translation table hierarchy

Different programs look for special translation tables to use. The program chooses one of the customized tables, as described in Table 1. The program first searches for a customized table that you have built. If the program fails to find one of the customized tables, it uses the default table supplied in hlq.STANDARD.TCPXLBIN. Table 1 provides the customized translation tables and default table names for the programs.

Guideline: FTP server and FTP client optionally use iconv instead of the external tables for single-byte conversion. The use of iconv is specified in FTP.DATA or by SITE/LOCSITE commands.

Table 1. SBCS translation table hierarchy
Program Customized translation tables Default translation table
FTP client control connection when no TRANSLATE parameter is specified on the ftp command
  1. EXTENSIONS UTF8
  2. Data set specified in the CTRLCONN configuration statement in FTP.DATA
  3. Data set specified in the CCTRANS configuration statement in FTP.DATA
  4. user_id.FTP.TCPXLBIN
  5. hlq.FTP.TCPXLBIN
  6. user_id.STANDARD.TCPXLBIN
  7. hlq.STANDARD.TCPXLBIN
  8. 7-bit ASCII - (ISO8859-1 for the network code page and IBM-1047 for the file system code page)
  9. FTP internal 7-bit tables
 The default should be number 8 for most all cases.
FTP client data connection when no TRANSLATE parameter is specified on the ftp command
  1. Data set specified in the SBDATACONN configuration statement in FTP.DATA
  2. Data set specified in the SBTRANS configuration statement in FTP.DATA
  3. user_id.FTP.TCPXLBIN
  4. hlq.FTP.TCPXLBIN
  5. user_id.STANDARD.TCPXLBIN
  6. hlq.STANDARD.TCPXLBIN
  7. The same translation tables established for the control connection
 The default is number 7.
FTP client when TRANSLATE parameter is specified on the ftp command for both control connections and data connections1
  1. If the client is started in the z/OS® UNIX System Services shell: $HOME/data_set.tcpxlbin
  2. user_id.data_set.TCPXLBIN
  3. hlq.data_set.TCPXLBIN
 There is no default.
FTP server control connections
  1. EXTENSIONS UTF8
  2. Data set specified in the CTRLCONN configuration statement in FTP.DATA
  3. Data set specified in the CCXLATE configuration statement in FTP.DATA
  4. jobname.SRVRFTP.TCPXLBIN
  5. hlq.SRVRFTP.TCPXLBIN
  6. jobname.STANDARD.TCPXLBIN
  7. hlq.STANDARD.TCPXLBIN
  8. 7-bit ASCII - (ISO8859-1 for the network code page and IBM-1047 for the file system code page)
  9. FTP internal 7-bit tables
 The default should be number 8 for most all cases.
FTP server data connections
  1. Data set specified with DD: SYSFTSX in the FTP start procedure
  2. Data set specified in the SBDATACONN configuration statement in FTP.DATA
  3. Data set specified in the XLATE configuration statement in FTP.DATA
  4. jobname.SRVRFTP.TCPXLBIN
  5. hlq.SRVRFTP.TCPXLBIN
  6. jobname.STANDARD.TCPXLBI
  7. hlq.STANDARD.TCPXLBIN
  8. The same translation tables established for the control connection
 The default is number 8.
LPR Client
  1. user_id.LPR.TCPXLBIN
  2. hlq.LPR.TCPXLBIN
  3. user_id.STANDARD.TCPXLBIN
 hlq.STANDARD.TCPXLBIN
LPR Client (TRANSLATE)
  1. user_id.data_set.TCPXLBIN
  2. hlq.data_set.TCPXLBIN
  3. user_id.LPR.TCPXLBIN
  4. hlq.LPR.TCPXLBIN
  5. user_id.STANDARD.TCPXLBIN
 hlq.STANDARD.TCPXLBIN
LPD Server jobname.data.STANDARD.TCPXLBIN hlq.STANDARD.TCPXLBIN
LPD Server (TRANSLATE)
  1. jobname.data_set.TCPXLBIN
  2. hlq.data_set.TCPXLBIN
 None. Printer services cannot be used.
PORTMAP
  1. user_id.STANDARD.TCPXLBIN
  2. jobname.STANDARD.TCPXLBIN
 hlq.STANDARD.TCPXLBIN
REXEC user_id.STANDARD.TCPXLBIN hlq.STANDARD.TCPXLBIN
SMTP
  1. jobname.SMTP.TCPXLBIN
  2. hlq.SMTP.TCPXLBIN
  3. jobname.STANDARD.TCPXLBIN
 hlq.STANDARD.TCPXLBIN
Telnet Client
  1. user_id.TELNET.TCPXLBIN
  2. hlq.TELNET.TCPXLBIN
  3. user_id.STANDARD.TCPXLBIN
 hlq.TELNET.TCPXLBIN
Telnet Client (TRANSLATE)
  1. user_id.data_set.TCPXLBIN
  2. hlq.data_set.TCPXLBIN
 None. Program Halts.
Notes:
  1. jobname is the name specified either on the PROC or JOB statement.
  2. user_id is the ID of the user who issued the command.
  3. data_set is the name entered on the TRANSLATE parameter for the program. See z/OS Communications Server: IP User's Guide and Commands for information about specifying the TRANSLATE parameter for the required program.
  4. High Level Qualifier (hlq) specified in the TCPIP.DATA configuration statement, DATASETPREFIX.

The Telnet client requires translation tables that are different from the default table hlq.STANDARD.TCPXLBIN. Customized translation tables for Telnet clients are provided in the install libraries as hlq.TELNET.TCPXLBIN and hlq.TELNETSE.TCPXLBIN. If these data sets are not found, the Telnet client uses the default table.

Telnet (for Linemode) uses iconv services with the CODEPAGE statement in the TELNETPARMS block to specify country and region translation tables. TCPXLBIN translation tables are not used. If CODEPAGE is in error or not specified, see CODEPAGE statementfor default values used. If custom code pages are required, see the information about globalization in the z/OS XL C/C++ Programming Guide for details about how to create your own conversions.

Parent topic: Translation tables
1 Do not use the TRANSLATE option for the FTP client if the SBCS table you need for data transfer does not support standard encodings for the portable character set. Such a translation table can adversely affect the EBCDIC to ASCII conversion of commands sent over the control connection.