REMOTE-PARAMETER =
Contains information about or for the remote system. This entry specifies the type of remote system. It also defines the syntax in which the remote system expects the value assignments.
REMOTE-PARAMETER = *BS2000 (...)
The value assignments for the remote system are given in BS2000 syntax. The local system checks whether the specified values conform to this syntax.
In this case the default values of the operands for the remote system correspond to those specified for the local system. LOGON passwords are not defaulted, however.
REMOTE-PARAMETER = *MSP(...)
The value assignments for the remote system are in the syntax of the z/OS system. The local system checks if the values specified conform to this syntax.
REMOTE-PARAMETER = *ANY(...)
The local system does not check the syntax in which the value assignments for the remote system are specified. Value assignments for the local system cannot be used as default values for the remote system. The value assignments must be in single quotes. The single quotes within a value assignment must be doubled (e.g. PASSWORD= ’C’’ABCD’’’).
FILE-NAME =
Name of the file or the library in the remote system (send file or receive file). It must be specified in the syntax and conform to the conventions of the remote system.
REMOTE-PARAMETER= | *BS2000 | *MSP | *ANY |
relevant for: | X | X | X |
default value: | *SAME | *NOT-SPECIFIED | *NOT-SPECIFIED |
openFT partners offer an option with which unique file names can be generated automatically in order to easily prevent conflict situations. This is achieved specifying the string %UNIQUE in the file name.
FILE-NAME = *SAME
relevant for *BS2000.
The file or the library member in the remote system has the same name as the file in the local system.
FILE-NAME = *NOT-SPECIFIED
relevant for *BS2000, *MSP and *ANY:
Only if FTAC functionality is used in the remote system can the file name be predefined, either partially or completely, in an FT profile. The file name or partial file name does not then have to be known to the request submitter. The file name may not be specified in the command.
relevant for *MSP:
The entry FILE-NAME=*NOT-SPECIFIED is only useful if an exit routine is installed in the remote system and the TRANSFER-ADMISSION for the remote system is an FT transfer admission. *NOT-SPECIFIED means in this case that the file name is taken from this exit routine and must not be specified in the command.
Default value if the remote system is an z/OS computer.
FILE-NAME = <filename 1..54> / <c-string 1..512 with-low> /
*POSIX(NAME = <posix-pathname 1..510>)
Name of the file or preprocessing command, when receiving, or of the postprocessing command, when sending. The specifications differ for with and without pre- and postprocessing.
Specifications without pre- or postprocessing on FILE-NAME
relevant for *BS2000 and *ANY
*POSIX syntax can only be used for BS2000 partners.
For DVS file names in the remote BS2000 system (send or receive file), the following applies:
With *BS2000, this file name can be specified without a user ID if the file is cataloged under the user ID for which the file transfer is performed (TRANSFER-ADMISSION operand).
This file name must be specified with a user ID ($userid.filename) if the file is not cataloged under the user ID for which the file transfer is performed (TRANSFER-ADMISSION operand).
If an FT product is used in the remote BS2000 and this product carries out the customary BS2000 extension of file names of the form $filename to include the standard user ID, the file name may be specified in this form. If this is not the case an error will result.
For POSIX file names in the remote BS2000 system (send or receive file), the following applies:
The POSIX file name can be specified relative to the HOME directory (entry: ./file) if the file is cataloged in the directory associated with the user ID for which the file transfer is being performed. If the file for which the file transfer is being executed is not cataloged in the directory of the user ID, the POSIX file name must be entered with the full pathname (entry: /file) (see also the TRANSFER-ADMISSION operand).
Specifications with pre- and postprocessing on FILE-NAME
If you specify a preprocessing command when receiving, the result from the preprocessing command is sent to the remote system’s standard output (BS2000 systems: SYSLST; z/OS: SYSPRINT) before being transferred. You can also address the output from the preprocessing command via the %TEMPFILE variable. The advantage of this is that the output can have any file format and the file is transferred in this format. If you do not specify %TEMPFILE then the output must have a format which is permitted at the remote system’s standard output, i.e. in BS2000 systems it must take the form of a SAM-V file. On z/OS, this is a PS file with a variable block size.
Since the file attributes are not known at the time the request is accepted, you should note the following if using %TEMPFILE:
either the future file attributes must be specified as request attributes,
or the file must be transferred in transparent format (homogeneous).
If you specify a postprocessing command when sending, the transferred file is used as input for the postprocessing command. This file can be addressed with the variable %TEMPFILE. If %TEMPFILE is not specified, read-in is done via the standard input (BS2000: SYSDTA, z/OS:SYSUT1). If the remote system is a BS2000-System, the file must be a SAM-V or ISAM-V file. On z/OS, this is a PS file with a variable block size.
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 (’;’). If the pre/postprocessing is running in BS2000, a slash ‘/’ must be placed in front of each individual command. There must not be any blanks between the semicolon and the slash.
Example
FILE-NAME=C‘| / Command1; / Command2; / Command3; ...‘
The maximum length of the entire command is limited to the maximum length of the file name. You will find more detailed information on this see section “Examples of the TRANSFER-FILE command”.
If an error occurs while executing the individual commands (in BS2000 /JOB-STEP), the transfer is aborted and the message FTR2206 or FTR2207 appears.
If a transfer request with preprocessing and postprocessing is to be restartable, the characters ‘|&’ must be specified instead of ‘|’. For more detailed information, also see section “Preprocessing and postprocessing”.
Example
FILE-NAME = C‘|& / Command1; / Command2; / Command3; ...‘
FILE-NAME = <text 1..56>
relevant for *MSP.
Name of the file in remote z/OS system (send or receive file):
This file name can be specified without a user ID if the file is cataloged under the user ID for which the file transfer is performed (TRANSFER-ADMISSION operand).
This file name must be specified with a user ID ($userid.filename) if the file is not cataloged under the user ID for which the file transfer is performed (TRANSFER-ADMISSION operand).
With FILE-NAME =<text 1..56>, library members in z/OS can also be addressed, if the FT products used in the partner system support the transfer of library members.
FILE-NAME = *LIBRARY-ELEMENT(...)
REMOTE-PARAMETER = | *BS2000 | *MSP | *ANY |
only relevant for: | X | 1 | X |
default value: | *SAME | *NOT-SPECIFIED |
Specifies that a library member is to be transferred. *NOT-SPECIFIED for all three operands is invalid, because the entry would not guarantee access to a library member in the remote system.
If library members are transferred onto library members, and if these members are administered in both systems with the library management program LMS, then the FT request must contain the same member type for both the local and the remote system.
Furthermore, the remote system must be capable of processing library members.
LIBRARY =
Name of the library in the remote system.
For file transfer with FTAM partners, only library members in the local BS2000 system can be accessed.
LIBRARY = *SAME
relevant for BS2000.
The library name in the remote system is the same as the library name in the local system. This entry is only permitted if the operand LIBRARY-ELEMENT was specified in the local system.
LIBRARY = *NOT-SPECIFIED
relevant for *BS2000 and *ANY.
Only when FTAC functionality is used in the remote system can the name of the library be predefined in an FT profile. The name of the library must not then be made known to the request submitter, nor may it be specified in the command.
LIBRARY = <filename 1..64> / <c-string 1..512 with-low>
relevant for *ANY.
Name of the library in the remote system. It must be specified in the conventions of the remote system.
LIBRARY = <filename 1..54> / <c-string 1..512 with-low>
relevant for *BS2000.
Name of the library in the remote system. It must be specified in the conventions of the remote system.
ELEMENT =
Name of the library member in the remote system.
ELEMENT = *SAME
relevant for *BS2000.
The member name in the remote system is identical to the member name in the local system. This entry is only permitted for BS2000 systems, and only if the operand LIBRARY-ELEMENT was specified in the local system.
ELEMENT = *NOT-SPECIFIED
relevant for *BS2000 and *ANY.
Only when FTAC functionality is used in the remote system can the name of the library member be predefined in an FT profile. The name of the library member must not then be made known to the request submitter, nor may it be specified in the command.
ELEMENT = <filename 1..64 without-gen-vers>(...) /
<composed-name 1..64 with-under>
relevant for *BS2000.
Name of the library member in the remote system. It must be specified in the conventions of the remote system.
ELEMENT = <c-string 1..64 with-low>(...)
relevant for *ANY.
Name of the library member in the remote system. It must be specified in the conventions of the remote system.
VERSION =
Version of the member in the remote system.
VERSION = *SAME
relevant for *BS2000.
The version in the remote system is identical to the version in the local system. If a file name has been specified in the local system, then the highest version of the member is assumed as the entry for the remote system.
VERSION = *NONE
relevant for *ANY.
No specification of the version in the remote system must be made.
VERSION = *STD
relevant for *BS2000 and *ANY.
Highest version of the member
VERSION = <text 1..24>
relevant for *BS2000.
Version of the member.
VERSION = <c-string 1..24 with-low>
relevant for *ANY.
Version of the member. It must conform to the conventions of the remote system.
TYPE =
Member type in the remote system.
TYPE = *SAME
relevant for *BS2000.
The member type in the remote system is identical to the member type in the local system. If a file name is specified in the local system, then TYPE must not be specified.
TYPE = *NONE
relevant for *ANY.
The member type does not have to be specified in the remote system.
TYPE = *NOT-SPECIFIED
relevant for *BS2000 and *ANY.
Only when FTAC functionality is used in the remote system can the library member type be predefined in an FT profile. The type of the library member must not then be made known to the request submitter, nor may it be specified in the command.
TYPE = <name 1..8>
relevant for *BS2000.
Member type in the remote system. It must be specified in the conventions of the remote system.
TYPE = <c-string 1..8 with-low>
relevant for *ANY.
Member type in the remote system. It must be specified in the conventions of the remote system.
PASSWORD =
REMOTE-PARAMETER = | *BS2000 | *MSP | *ANY |
relevant for: | X | X | X |
default value: | *SAME | *NONE | *NONE |
Password authorizing access to the file in the remote system. The file password must be specified in the remote system’s syntax and conform to the conventions of the remote system.
If the file in the remote system is protected with a password, 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, or
a password for the execution of a send or receive file that is protected neither by a read nor by a write password but by an execute command.
Newly-created receive files are not given a password by this operand. PASSWORD is ignored in such cases.
PASSWORD = *SAME
relevant for *BS2000.
The same password applies in the remote system as in the local system.
PASSWORD = *NONE
relevant for *BS2000, *MSP and *ANY.
Access is possible without a password.
PASSWORD = *SECRET
relevant for *BS2000, *MSP and *ANY.
The system prompts you to enter the password. However, this does not appear on the screen.
PASSWORD = <c-string 1..4> / <x-string 1..8> /
<integer -2147483648..2147483647>
relevant for *BS2000.
BS2000 file password.
PASSWORD = <alphanum-name 1..8>
relevant for *MSP.
z/OS file password.
PASSWORD = <c-string 1..64 with-low> / <x-string 1..128>
relevant for *ANY.
With *ANY, the file password must always be in inverted commas.
TRANSFER-ADMISSION =
Contains information on authorization to perform file transfers in the remote system.
REMOTE-PARAMETER = | *BS2000 | *MSP | *ANY |
relevant for: | X | X | X |
default value: | *SAME | 1 | *NONE |
TRANSFER-ADMISSION = *SAME
relevant for *BS2000.
The relevant values from the local system apply. A password, however, is only accepted if it is explicitly specified in the LOCAL-PARAMETER structure.
TRANSFER-ADMISSION = *NONE
relevant for *ANY.
The remote system does not require/recognize any transfer admission.
TRANSFER-ADMISSION = *SECRET
relevant for *BS2000, *MSP and *ANY.
The system prompts you to enter the transfer admission. However, the input is not displayed on the screen.
TRANSFER-ADMISSION = <alphanum-name 8..32> / <x-string 15..64> /
<c-string 8..32 with-low>
relevant for *BS2000, *MSP and *ANY.
When FTAC functionality is used in the remote system, only the TRANSFER-ADMISSION predefined in the admission profile may be specified. The alphanumeric entries are converted internally to lowercase letters.
If an exit routine exists in the remote z/OS system which offers an FTAC transfer admission, this can be specified using TRANSFER-ADMISSION.
TRANSFER-ADMISSION = *PARAMETERS(...)
Identification, account number and password of the user in the remote system for which the follow-up processing is to be performed. The operands in parentheses can be used as positional operands without their keywords.
REMOTE- | *BS2000 | *MSP | *ANY |
USER- | <alphanum-name 1..8> | <name 1..7> | <c-string 1..67 withlow> |
ACCOUNT= | *NONE | *NONE | *NONE |
PASSWORD= | *NONE | *NONE | *NONE |
USER-IDENTIFICATION =
relevant for *BS2000, *MSP and *ANY.
Identification of the user (user ID) in the remote system.
ACCOUNT =
relevant for *BS2000, *MSP and *ANY.
Account number of the user in the remote system.
ACCOUNT = *NONE
relevant for *BS2000, *MSP and *ANY.
The remote system does not require an account number.
PASSWORD =
relevant for *BS2000, *MSP and *ANY.
Password authorizing the user to access the remote system.
PASSWORD = *NONE
relevant for *BS2000, *MSP and *ANY.
Access is possible without a password.
PASSWORD = *SECRET
relevant for *BS2000, *MSP and *ANY.
The system prompts you to enter the password. However, the entry does not appear on the screen.
PROCESSING-ADMISSION =
relevant for *BS2000, *MSP and *ANY.
Contains information about a user’s authorization to perform follow-up processing in the remote system.
In file transfer with FTAM partners follow-up processing cannot be started in the remote system. Exception: an admission profile defines follow-up processing and is addressed via the TRANSFER-ADMISSION. Thus the PROCESSING-ADMISSION operand is not effective for FTAM partners.
PROCESSING-ADMISSION = *SAME
The relevant REMOTE TRANSFER-ADMISSION values apply.
PROCESSING-ADMISSION = *NONE
relevant for *ANY.
No transfer admission is required for follow-up processing. See also the description of PROCESSING-ADMISSION=*NOT-SPECIFIED.
PROCESSING-ADMISSION = *NOT-SPECIFIED
Only if FTAC functionality is used in the remote system can the PROCESSING-ADMISSION be predefined in an FT profile. It must not then be made known to the request submitter, nor may it be specified in the command.
PROCESSING-ADMISSION = *PARAMETERS(...)
Identification, account number and password of the user in the remote system, for which the follow-up processing is to be performed. The parameters in parentheses can be used as positional operands without their keywords.
REMOTE- | *BS2000 | *MSP | *ANY |
USER- | <alphanum-name 1..8> | <name 1..7> | <c-string 1..67 withlow> |
ACCOUNT = | *NONE | *NONE | *NONE |
PASSWORD = | *NONE | *NONE | *NONE |
USER-IDENTIFICATION =
Identification of the user (user ID) in the remote system.
ACCOUNT =
Account number of the user in the remote system.
ACCOUNT = *NONE
relevant for *BS2000, *MSP and *ANY.
The remote system does not require an account number.
PASSWORD =
Password authorizing the user to access the remote system.
PASSWORD = *NONE
relevant for *BS2000, *MSP and *ANY.
Access is possible without a password.
PASSWORD = *SECRET
The system prompts you to enter the password. However, the entry does not appear on the screen.