Open topic with navigation

TIBCO® Managed File Transfer Platform Server for z/OS 8.1.0

# LOCALCTFILE={Translation_table_used_locally}

Default | Not Applicable
Allowable Values | `NULL` , `NONE`, Translation table name with 1 - 16 characters
Minimum | 1
Maximum | 16
Alternate Specification | LCT

This parameter defines the local translation table name. The translation table name can contain 1 - 16 characters.

Translation tables are defined in the CONFIG DD statement, and can be enabled at startup or enabled through the ENABLE operator command. The LOCALCTFILE translation table is used when `TYPE=TEXT` transfers are defined. This parameter is ignored when `TYPE=BINARY` is specified. A value of `NULL` or `NONE` indicates that no conversion takes place.

The LOCALCTFILE parameter on the file transfer request overrides the DEFAULT_LOCALCTFILE parameter.

To use z/OS Unicode Conversion Services, the following format of this parameter is required.

`LOCALCTFILE=CC:xxxxx:yyyyy`

Where:

xxxxx defines the CCSID of the Local data - usually the EBCDIC CCSID.

yyyyy defines the CCSID of the Remote data - usually the ASCII CCSID

For information on the CCSID values to use, see the IBM manual: z/OS Unicode Services User's Guide and Reference.

Example: `LOCALCTFILE=CC:01140:01208`

- For a Send Request, this parameter converts data from EBCDIC CCSID 1140 to ASCII UTF-8 CCSID 01208.
- For a Receive Request, this parameter converts data from ASCII UTF-8 CCSID 01208 to EBCDIC CCSID 1140.

When using this parameter, set the following parameter so that the partner does NOT perform any conversion:

REMOTECTFILE=NULL

Copyright © 2003-2021. TIBCO Software Inc. All Rights Reserved.