The long output is described using an example of an outbound request and an example of an inbound request.
Example 1 (Outbound request)
Full information is to be output to SYSLST on the FT request with transfer ID 721212. If the file transfer request was issued under the same user ID as that under which the inquiry is made, then the command is as follows:
|
The recommended short form of this command is as follows:
/SHFT 721212,INF=*ALL,OUT=*SYSLST
The information output on SYSLST then has the following format, for example:
|
Example 2 (Inbound request)
Full information is to be output to SYSLST on the FT request with transfer ID 983050. If the file transfer request was issued under the same user ID as that under which the inquiry is made, then the command is as follows:
|
Meaning of the fields in the long output
The list below describes all fields which can occur in the long output (according to lines). Which fields are output in each particular case depends on the type and the parameters of the request.
TRANSFER-ID:
Transfer ID of the request
STORE:
The time at which the request was entered in the request queue
FILESIZE:
The size of the file in bytes. If the output is flagged with a "K" on the right, the output is in kilobytes. If the output is flagged with "M", the output is in megabytes. The size is only shown here if the request has already been active. In the case of receive requests, a value is only shown here if the partner also sends that value.
STATE:
State of the request
BYTECNT:
Number of bytes transferred up to the last restart form (in the case of data compression in compressed form)
INITIATOR:
Initiator of the request
TRANS:
Transfer direction, as seen from local system
PRIO:
Priority with which the request is to be started;
here: NORM for NORMAL.
WRITE:
Specifies if or when the receive file is to be overwritten or extended
START:
Requested start time of the request (SOON for “as soon as possible”).
CANCEL:
Requested abortion time
(NO for “no abortion requested”)
COMPRESS:
Specifies whether or not the file is to be transferred in compressed form
DATA:
Type of file:
CHAR
for text file
BIN
for binary file
NOT-SPECIFIED
in TRANSFER-FILE (NCOPY), no DATA-TYPE was specified
USER
for user format
GLOB-ID:
Global request identification, displayed only in the case of inbound requests from openFT and FTAM partners (INITIATOR=REMOTE). This corresponds to the request identification (=TRANSFER-ID) on the initiator system.
TRANSP:
Specifies whether the transfer is to be done in transparent format
ENCRYPT:
Specifies whether the file content is to be transferred in encrypted form
TABEX:
Specifies whether the tabulator expansion is activated.
Possible values: ON, OFF, AUTO.
TARGFORM:
Format of the transferred file in the target system:
SEQ
Sequential file format
BLOCK
Block format
TRECFRM:
Record format of the file in the target system:
STD
The same record format as in the sending system
UNDEFINED
Undefined record format
OWNER:
Owner of request in local system
DICHECK:
Specifies whether data integrity is to be checked (YES) or not (NO)
RECFORM:
Record format. Possible values: UNDEFINED, VARIABLE, FIX.
PROTECT:
Specifies whether the protection attributes of the file are transferred
PARTNER:
Symbolic name of partner system participating in the request.
If the FT request is in the STATE=WAIT state, and there is no normal internal resource bottleneck, then the partner name is preceded by one of the following characters:
* | The FT administrator of the local system has locked a resource. |
! | An attempt to set up a connection to the partner system failed (possibly because |
? | Installation error. |
The cause can be queried with the FT administrator. | |
|
FNC-MODE:
Encoding mode for remote file names and follow-up processing. Possible values:
TRANSPARENT
Encoding in transparent mode.
CHAR
Encoding in character mode (only possible for inbound requests).
PARTNER-STATE:
Status of the partner. Possible values:
ACT
Activated
DEACT
Deactivated
NOCON
No connection, for instance because the openFT server has not been started on the remote system.
INSTERR
There is an installation or configuration error (for example, the local system is not known to the partner or the address of the partner in the partner list is not valid) or authentication of one of the partners has failed or encryption is not available locally or on the partner system.
SHORT
A resource bottleneck has occurred on the partner.
PARTNER-PRIO:
Prioritization of the partner when processing requests.
Possible values:
LOW
The partner has low priority.
NORM
The partner has normal priority.
HIGH
The partner has high priority.
LOC:
Specifications on the local system (LOCAL-PARAMETER).
The entry can include more than in this example; the keywords correspond to the recommended abbreviations of the keywords of the transfer command; the meaning of the operand is also to be found there.
FILE:
Local file name
ASYN-MSG:
Specifies which request result leads to an asynchronous termination message. Possible values: ALL, FAIL.
MONJV:
Name of the job variable in the format :cat-id:$user-id.monjv-name if a job variable | |
|
Specifications on the remote system (REMOTE-PARAMETER).
The entry can include more than in this example; the keywords correspond to the recommended abbreviations of the keywords of the transfer command; the meaning of the operand is also to be found there.
FILE:
Remote file name
The following parameters are only output for locally issued requests.
TRANS-ADM:
Transfer admission (here for the remote system. Instead of the triplet user ID, account number and password where appropriate, REMOTE-PROFILE can also be output here if a remote FTAC FT profile is addressed. The equivalent also applies to entries in the local system.
CCSN:
CCS name used in the local and/or remote system when reading the file.