Application Programming Interface › Using API Member Names › lear_key

lear_key

Indicates the symmetric encryption key that is used to encrypt/decrypt.

Range: 0 to 128 characters

Default: None

Example:

lear_key=025BD5549BF743D99D86A2752019BCF48CC14AD5A16E0110

Notes:

• The key value specified in this example is a key for the 3DES encryption algorithm.
• CA XCOM Data Transport accepts the hexadecimal value of the actual key and the specified value must be in upper case.

local_charset

This parameter specifies the local character set CA XCOM Data Transport uses for Unicode transfers (CODE_FLAG=UTF8 or CODE_FLAG=UTF16).

CCSID#nnnnn

nnnnnn - specifies the CCSID number that corresponds to the character set. Valid values are 1 - 65535.

Alternatively, can be specified as an IANA character set name, or (ICU) acceptable alias name.

Range: 0 to 60 characters

Default: The DEFAULT_CHARSET parameter specifies the default in the CA XCOM Data Transport Global Parameters.

local_delim

This parameter specifies an optional encoding for which the specified LOCAL_CHARSET is based. The encoding can be either ASCII or EBCDIC. If specified, the encoding must be the first option in the list. If LOCAL_CHARSET is UTF based charset, UTF rules will be applied disregarding encoding specified in LOCAL_DELIM.

Additionally, specifies a colon separated list of record delimiters that are used to mark and detect the end of a record.

This parameter is used only for UNICODE transfers (CODE_FLAG=UTF8 or CODE_FLAG=UTF16).

EBCDIC Rules

NOTE: The NA is only used by XCOM z/OS to indicate that the file format attribute should not be set.

ASCII Rules

UTF Rules

Range: 0 to 60 characters

Default: The DEFAULT_DELIM parameter specifies the default in the CA XCOM Data Transport Global Parameters specifies the default.

The tables indicate valid record delimiters for various encodings. If a record delimiter is not applicable for encoding on which the LOCAL_CHARSET is based, it should not be used.

Example: If LOCAL_CHARSET is not UTF based, PS and LS delimiters should not be used. Similarly if LOCAL_CHARSET is EBCDIC based, VT, PS, and LS delimiters should not be used.

In these cases, these delimiters will be treated as invalid and disregarded if used. If no valid delimiter is found in LOCAL_DELIM, delimiters will be derived as explained below.

If LOCAL_DELIM is not specified or doesn’t contain at least one valid delimiter, the DEFAULT_DELIM parameter in the CA XCOM Data Transport Global Parameters is considered. If DEFAULT_DELIM is also not specified or doesn’t contain at least one valid delimiter, platform default values are used as shown:

• Default for ASCII: ‘LF,CRLF’
• Default for EBCDIC: ‘NL’

Note: During Unicode conversion some of the delimiters may fail to convert to some code pages.

For example, in the case of a Receive File transfer, when LOCAL_CHARSET is set to an ASCII based charset and LOCAL_DELIM is set to NL/CRNL, then the transfer may fail. The Unicode conversion fails as ASCII based code pages may not have a mapping character for NL/CRNL.