The name of the file on the local system that is being transferred. 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 UNIX or Linux file naming conventions apply.
For wildcard transfers, use an asterisk as a file name to indicate that all files within the specified directory are to be transferred. For example, the statement "LOCAL_FILE=/NAMES/*" indicates that all files under the NAMES directory are to be transferred.
When a prefix is followed by an asterisk (*), all members beginning with a specific prefix are to be transferred. For example, LOCAL_FILE=/NAMES/AL* requests that files AL, ALEX, and ALICE are all to be transferred. The same rules apply if an asterisk is followed by a suffix.
The actual file name range (not including its path) for wildcard transfers can be between 0 and 71 characters. This also includes the file extension where applicable. File names over 71 characters are truncated. However, when sending files to a mainframe PDS, any file name over 8 characters in length is truncated. These systems do not recognize file extensions. For example, a file called longfilename.txt will be truncated to longfile and a file called file.txt will be truncated to file.
Note: If QUEUE=YES, user must specify full path name.
Range: 0 to 256 characters
Default: None
| Copyright © [set copyright date variable] CA. All rights reserved. |
|