The name of the file on the local system that is being transferred. At the command prompt or in a script, if this variable is null or unset, standard input is read. In this manner, CA XCOM Data Transport commands can be used in a pipeline or with redirection. All Windows and UNC file naming conventions apply. If more than one file is included in the transfer, L_FILE must include wildcard characters (*).
Note: If QUEUE=YES, user must specify full path name.
Range: 0 to 256 characters
Default: None
LOCAL_CHARSET specifies the local character set CA XCOM Data Transport uses for Unicode transfers (CODE_FLAG=UTF8 or CODE_FLAG=UTF16).
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 in the CA XCOM Data Transport Global Parameters specifies the default.
LOCAL_DELIM 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, a colon separated list of record delimiters can be specified 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).
|
Record Delimiter Option |
Mutually exclusive with |
|
CR |
CRLF, CRNL |
|
LF |
LFCR |
|
NL |
|
|
CRLF |
CR |
|
LFCR |
LF |
|
CRNL |
CR |
|
FF |
|
|
NA |
|
|
Record Delimiter Option |
Mutually exclusive with |
|
CR |
CRLF, CRNL |
|
LF |
LFCR |
|
NL |
|
|
CRLF |
CR |
|
LFCR |
LF |
|
CRNL |
CR |
|
VT |
|
|
FF |
|
|
Record Delimiter Option |
Mutually exclusive with |
|
CR |
CRLF, CRNL |
|
LF |
LFCR |
|
NL |
|
|
CRLF |
CR |
|
LFCR |
LF |
|
CRNL |
CR |
|
VT |
|
|
FF |
|
|
LS |
|
|
PS |
|
Range: 0 to 60 characters
Default: The DEFAULT_DELIM parameter 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 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, 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 below,
Note: During Unicode conversion some of the delimiters may fail to convert to some code pages.
For example, In case of Receive File transfer, when LOCAL_CHARSET set to ASCII based charset and LOCAL_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.
| Copyright © [set copyright date variable] CA. All rights reserved. |
|