TCP Translation Table (TCPXLATE) Definitions

In addition to supporting its own internal translation tables, the Platform Server supports the Single Byte Character Set (SBCS) and Double Byte Character Set (DBCS) translation tables supplied by IBM TCPIP.

To activate these translation tables, you must define and enable a TCPXLATE member within the CONFIG DD statement. Translation tables must be enabled at startup or through the ENABLE operator command. You can refresh translation tables by using the REFRESH command, but you cannot disable them.

Translation is defined by the LOCALCTFILE parameter on the batch interface, or by the DEFAULT_LOCALCTFILE parameter on the node definition. Translation is only performed when TYPE=TEXT is defined.

See the following table for parameters that are required by the translation table configuration. Comments are defined with an asterisk (*) in column 1.

Parameter Description
TYPE Distinguishes between NODE, COS, XLATE, and TCPXLATE entries.

This is a required parameter. You must set the value as TCPXLATE to indicate that you want to configure the Platform Server to use the TCP SBCS and DBCS translation tables. It must be the first parameter defined.

SBCS Defines the SBCS member that is used when performing translation.

The member defined must be a valid member of the TCPIP.SEZATCPX library defined by the TCPSBCS DD statement. This is a required parameter and it has no default value.

DBCS Defines the DBCS ddname and the relative number of the DBCS translation tables.

Note: The DBCS translation files can contain more than one DBCS translation table.
This is a required parameter and it has no default value. You must define a valid value in this format: DBCS ddname,relative_number.

See the following list of the translation tables that are supplied by TCPIP and can be set using this parameter.

  • TCPCHBIN,1   Traditional Chinese
  • TCPCHBIN,2   Big5 Chinese
  • TCPSCBIN,1   Simplified Chinese
  • TCPHGBIN,1   Korean
  • TCPHGBIN,2   Korean Hangeul
  • TCPKJBIN,1   JIS Japanese
  • TCPKJBIN,4   EUK Japanese

SOSIDefines the type of ShiftOutShiftIn characters that are used by the remote system.

This is a required parameter. It has no default value. The parameter applies only when DBCS has been coded. It is not valid when SBCS has been coded.

Valid values are:

  • SPACE: An ASCII space character (0x20) is the SOSI character. Whether data is converted depends on the character following 0x20. If the following character is a valid DBCS character, then DBCS translation is performed. If the following character is not a valid DBCS character, then standard SBCS conversion is performed on this character.
  • ASCII: The SOSI characters are the hex values 0x1e and 0x1f.
  • EBCDIC: The SOSI characters are the hex values 0x0e and 0x0f.
  • NONE: No SOSI characters. Whether DBCS conversion is performed depends on the characters. If the characters are valid DBCS characters, then DBCS conversion is performed. If the characters are not valid DBCS characters, then SBCS conversion is performed.

Note:  
  • The local SOSI characters are always the EBCDIC SOSI characters. When data is sent to the remote system, only data within the EBCDIC SOSI characters (0x0e and 0x0f) are converted. The EBCDIC SOSI characters are converted to the format specified in the SOSI parameter.
  • When DBCS conversion is being performed, the Platform Server turns checkpoint restart off, because checkpoint restart is not supported when DBCS conversion is being performed.