A command sequence can also be input for SUCCESS-PROCESSING and FAILURE-PROCESSING.
The individual commands must be separated by a semicolon. If a character string is enclosed in single or double quotes (’ or ") within a command sequence, openFT will not interpret any semi-colon present within this character string as a separator.
Example
SUCC=’command1;command2;command3’
The entries for the operands SUCCESS-PROCESSING and FAILURE-PROCESSING may total up to 1000 characters. If the length limit for follow-up processing data is exceeded due to variable replacement, openFT ends the request and returns an error message.
The commands/JCL statements must comply with the z/OS syntax rules; openFT does not check the syntax of the commands and statements specified for follow-up processing, see Syntax rules for follow-up processing on z/OS.
Please refer to section “Follow-up processing” for details on follow-up processing like using variables, for example.
SUCCESS-PROCESSING =
Follow-up processing to be executed in the remote system after a successful file transfer.
FTP partners do not support follow-up processing.
REMOTE-PARAMETER = | *BS2000 | *MSP | *ANY |
relevant for: | X | X | X |
default value: | *NONE | *NONE | *NONE |
SUCCESS-PROCESSING = *NONE
No follow-up processing is to be executed.
SUCCESS-PROCESSING = <c-string 1..1000 with-low>
Command to be executed in the remote system after a successful file transfer. It must be specified in quotes according to the syntax and conventions of the remote system.
When in the form of a c-string, follow-up processing is enclosed in quotes.
In the case of a BS2000 partner, each command begins with a slash ('/command'). It is also possible to specify a sequence of commands separated from one another by semicolons.
In the case of z/OS partners (*MSP), the comments relating to follow-up processing in the local system apply, i.e. every command starts without a backslash ('command'). You can also specify a sequence of commands separated by semicolons (see Follow-upprocessing in the remote system).
For all other partner systems (*ANY), the rules applying to the remote system in question apply.
When entering the follow-up processing specifications, you may also use variables provided that these are supported by the remote system (see also Follow-upprocessing).
FAILURE-PROCESSING =
Follow-up processing to be executed in the remote system after an unsuccessful file transfer. This follow-up processing is only started if a file transfer that has already commences is terminated due to an error.
FTP partners do not support follow-up processing.
REMOTE-PARAMETER = | *BS2000 | *MSP | *ANY |
relevant for: | X | X | X |
default value: | *NONE | *NONE | *NONE |
FAILURE-PROCESSING = *NONE
No follow-up processing is to be executed.
FAILURE-PROCESSING = <c-string 1..1000 with-low>
Command to be executed in the remote system if the file transfer is aborted because of an error. It must be specified in quotes according to the syntax and conventions of the remote system.
The same specifications are valid for FAILURE-PROCESSING as for SUCCESS-PROCESSING, see above.
CODED-CHARACTER-SET=
Coding (character set) that is to be used to read or write the remote file.
CODED-CHARACTER-SET= *STD
The character set used by default to read or write the remote file is the character set defined as the default in the remote system.
CODED-CHARACTER-SET= <alphanum-name 1..8> / <c-string 1..8 with-low>
Coding (CCS) that is to be used to read or write the remote file. The character set must be known in the remote system.