LOCAL-PARAMETER = *PARAMETERS(...)
Specifications for the local system.
FILE-NAME =
Name of the file in the local system (send file or receive file).
FILE-NAME = *NOT-SPECIFIED
The name of the file is known locally because it has already been completely defined in the FTAC admission profile addressed locally.
FILE-NAME = <filename 1..59> / <c-string 1..512 with-low>
When sending, the name of the file or preprocessing command, or, when receiving, the name of the postprocessing command. The specifications differ for with and without pre- and postprocessing.
Specifications without pre- or postprocessing on FILE-NAME
All types of filename can be either fully qualified or partially qualified:
Fully qualified specification: the filename is enclosed in single quotes; the "first level qualifier" is the user ID or the alias under which the file is or will be cataloged.
Partially qualified specification: the filename is not enclosed in single quotes; in this case, openFT adds the user ID for which the file transfer is being performed (TRANSFER-ADMISSION operand) as the "first level qualifier".
If you use the c-string data type for a partially qualified filename, you must specify it in the form C’FILE.XYZ’.
If complete PO or PDSE data sets are to be transferred, the receive file only needs to be specified in the request with the corresponding type :O: or :E: openFT with a version < 10 is running on the partner system.
openFT permits the automatic generation of unique filenames as a simple way of preventing conflicts. You do this by entering %UNIQUE in the filename.
Specifications with pre- or postprocessing on FILE-NAME
If you specify preprocessing commands on a send operation, the specified commands are first started as a TSO job. The data is output via the %TEMPFILE variable or via SYSPRINT to a temporary file ("preprocessing")
If you specify postprocessing commands on a receive operation, openFT provides the first command with the transferred data via the %TEMPFILE variable or via SYSUT1 and waits until processing is concluded ("postprocessing").
For both pre- and postprocessing, a c-string must be specified on FILE-NAME. The first character must be a pipe symbol ‘|’, followed by the command string. If several commands are specified, they must be separated by a semicolon (‘;’).
Example
FILE-NAME=C‘|Command1;Command2;Command3; ...‘
You should construct command sequences using the TSO WHEN command, e.g.:
command1;WHEN SYSRC(< 12) command2;WHEN SYSRC(< 12) command3;...
The total maximum length of commands is restricted to the maximum file name length. For more information refer to the section “Preprocessing and postprocessing”. Also refer to the topic “Preprocessing” at the example in section “Examples of the NCOPYcommand”.
If an error occurs during command execution, transfer is aborted with message FTR2206 or FTR2207.
If a transfer request with preprocessing and postprocessing is to be restartable, the characters ‘|&’ must be specified instead of ‘|’. For more details, also see section“Preprocessing and postprocessing”.
Example
FILE-NAME = C‘|&command1;command2;command3; ...‘
To prove admission for preprocessing or postprocessing, the local TRANSFER-ADMISSION must either be explicitly supplied with USER-ID, ACCOUNT and PASSWORD or implicitly supplied with these specifications via a transfer admission belonging to an admission profile that contains them.
PASSWORD =
Password authorizing access to the file in the local system. If the file in the local system is password-protected (by means of the TSO command "PROTECT"), the password must be specified in this operand as:
a write password for a receive file, or
a read password for a send or receive file that is not protected by a write password but by a read password,
Newly created receive files are not given a password by this operand. PASSWORD is ignored in such cases.
PASSWORD = *NONE
Access is possible without a password.
PASSWORD = <alphanum-name 1..8>
Password authorizing access to the file in the local system.
TRANSFER-ADMISSION =
Transfer admission of the user for the local system.
TRANSFER-ADMISSION = *SAME
The ID of the user entering the command is valid for the file transfer.
TRANSFER-ADMISSION = <alphanum-name 8..32> / <c-string 8..32 with-low> / <x-string 15..64>
If the FTAC functionality is used the file name for the local system can be defined in an FT profile. The transfer admission defined in the FT profile must be specified here. From this transfer admission the access rights in the local system can be defined. These access rights are also defined in the FT profile. The alphanumeric entry is converted internally to lowercase characters.
The alphanumeric entries are converted internally to lowercase characters.
When entering the transfer admission in the form of a c-string you must remember that in z/OS a transfer admission defined as a c-string is stored using uppercase characters in the profile. To go with this you must also enter it in the NCOPY command, to ensure that conversion to lowercase is avoided. Here, you should bear in mind the notes regarding the distinction between uppercase and lowercase characters which can be found on section “Entering FT commands”.
TRANSFER-ADMISSION = *PARAMETERS(...)
User ID, account number and password under which file transfer in the local system is to be performed. The operands in parentheses can also be used a positional operands without their keywords.
USER-IDENTIFICATION = <name 1..8>
User ID in the local system.
ACCOUNT =
Account number under which file transfer is performed in the local system.
ACCOUNT = *NONE
The default account number of the user ID is used.
ACCOUNT = <alphanum-name 1..40> / <c-string 1..40>
Account number of the user in the local system.
PASSWORD =
Password authorizing the user to access the local system.
PASSWORD = *NONE
Access is possible without a password.
PASSWORD = <alphanum-name 1..8>
Password that authorizes the user to access the local system.
PROCESSING-ADMISSION =
Contains information concerning the authorization of a user in the local system to perform follow-up processing.
PROCESSING-ADMISSION = *SAME
The relevant TRANSFER-ADMISSION values (see above) of the local system apply. This specification is only of value if the local TRANSFER-ADMISSION has either been explicitly supplied with USER-ID, ACCOUNT and PASSWORD or has been supplied implicitly via the transfer admission of an admission profile that contains these specifications. Otherwise the PROCESSING-ADMISSION must itself explicitly contain these specifications, either through their entry in this NCOPY command or through the use of a corresponding admission profile.
PROCESSING-ADMISSION = *NOT-SPECIFIED
Only if FTAC functionality is used can the entry for PROCESSING-ADMISSION be predefined by an FT profile. This entry must not be specified in the FT request.
PROCESSING-ADMISSION = *PARAMETERS(...)
User ID, account number and password of the user for whom the follow-up processing is to be performed. The operands in parentheses can also be used as positional operands without their keywords.
USER-IDENTIFICATION = <name 1..8>
User ID in the local system. This ID must be specified in the syntax of the local z/OS system.
ACCOUNT = *NONE
Access is possible without a password.
The default account number of the user ID specified in the USER-IDENTIFICATION is used.
ACCOUNT = <alphanum-name 1..40> / <c-string 1..40>
Account number or "accounting information" of the user in the local system. The account number must be specified in the syntax of the local system.
PASSWORD =
Password authorizing the user to access the local system.
PASSWORD = *NONE
Access is possible without a password.
PASSWORD = <alphanum-name 1..8>
Password that authorizes the user to access the local system.