Parameters › List of Parameters › RELEASE

RELEASE

Specifies whether the remote z/OS partner is to release unused DASD space when creating a new file.

YES

The remote partner is to release unused DASD space.

The unused DASD space that is specified for the transfer is released when the file is closed at the end of the transfer.

NO

The remote partner is not to release unused DASD space.

Default: No

REMOTE_CHARSET

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

When the remote system is CA XCOM Data Transport for z/OS:

CCSID#nnnnn/tttttttt

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

tttttttt (optional) – specifies the technique search order IBM Unicode Services uses when performing conversion. From 1 to 8 characters are specified. Valid values to use are:

R - Roundtrip conversion

E - Enforced Subset conversion

C - Customized conversion

L - Language Environment Behavior conversion

M - Modified for special use conversion

B - Bidi transformation (Bi-directional) conversion

0-9 - User defined conversions

Note: If the technique search order is not specified, Unicode Services defaults to ‘RECLM’.

When the remote system is CA XCOM Data Transport for Windows or CA XCOM Data Transport for Linux/Unix:

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 Default Options Table/Global Parameters on the remote system.

REMOTE_DELIM

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

Used only for UNICODE transfers (CODE_FLAG=UTF8 or CODE_FLAG=UTF16).

When the remote system is CA XCOM Data Transport for z/OS:

Additionally it specifies the delimiter to use for USS-based output files when FILEDATA=TEXT.

Valid options:

EBCDIC – The specified character-set is EBCDIC encoded.

NA – Not applicable, the system default delimiter is used.

NL – New line

CR – Carriage return

LF – Line feed

CRLFL – Carriage return/Line feed

LFCR – Line feed/Carriage return

CRNL – Carriage return/New line

Note: The only valid encoding for CA XCOM Data Transport for z/OS is EBCDIC.

When the remote system is CA XCOM Data Transport for Windows or CA XCOM Data Transport for Linux/Unix:

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

EBCDIC Rules

ASCII Rules

UTF Rules

Range: 0 to 60 characters

Default: The DEFAULT_DELIM parameter specifies the default in the CA XCOM Data Transport Default Options Table/Global Parameters on the remote system.

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

Example: If REMOTE_CHARSET is not UTF based, PS and LS delimiters should not be used. Similarly if REMOTE_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 REMOTE_DELIM, delimiters will be derived as explained below.

If REMOTE_DELIM is not specified or doesn’t contain at least one valid delimiter, DEFAULT_DELIM parameter in the CA XCOM Data Transport Default Options Table/Global Parameters on the remote system 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 below,

• 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 case of Send File transfer, when REMOTE_CHARSET set to ASCII based charset and REMOTE_DELIM set to NL/CRNL, then transfer may fail. The Unicode conversion fails as ASCII based code pages may not have mapping character for NL/CRNL.