Description of the short output of SHOW-FILE-TRANSFER

Example 1

Information is to be output to SYSOUT on those FT requests submitted by the remote system ALFRED which require access to the file DRAISINE and are currently active. The required command is as follows:

/SHOW-FILE-TRANSFER                                                    -

/                  SELECT=(INITIATOR=*REMOTE,                          -
/                  PARTNER=ALFRED,                                     -

/                  FILE-NAME=DRAISINE,                                 -

/                  STATE=*ACTIVE)

The recommended short form of this command is as follows:

/SHFT SEL=(INIT=*REM,PART-NAME=ALFRED,FILE=DRAISINE,STATE=*ACT)

or

/NSTATUS SEL=(INIT=*REM,PART-NAME=ALFRED,FILE=DRAISINE,STATE=*ACT)

The FT administrator must specify the operand OWNER=*ALL by SELECT if he/she is not the owner of the file DRAISINE.

The information is then output in the following format, for example:

%TRANS-ID %528184

INI STATE PARTNER REM ACT ALFRED

DIR TO

BYTE-COUNT 14760

FILE-NAME DRAISINE

The information is output to SYSOUT, since this is the default value for the output of inquiry information.

Description of the output columns:

TRANS-ID:

Transfer ID of the file transfer request

INI:

Initiator of the file transfer request : REM for REMOTE, LOC for LOCAL

STATE:

State of the request (here ACT for ACTIVE), other outputs:

SUSP for SUSPEND,
Inbound request suspended, e.g. due to higher priority requests.

LOCK for LOCKED,

WAIT for WAIT,

FIN for FINISHED,

HOLD for HOLD

PARTNER:

Symbolic name of the relevant partner system.

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 the remote system is not running, for example, or because FT has not been started there or, in the case of TCP/IP connections, because the port specification contains *BY-TRANSPORTSYSTEM and there is no BCMAP). This can also occur, if openFT has discovered an error during the internal check of transferred data integrity.
?	Installation error.
	The cause can be queried with the FT administrator. Possible reasons:
	The PORT in BCMAP does not correspond to that in the partner entry. Check the installation. The authentication of the local or remote system has failed due to an unsuitable public key.

DIR:

Transfer direction

BYTE-COUNT:

Number of bytes transferred up to the last restart point (in the case of data compression this is the number of bytes of compressed data)

FILE-NAME:

Name of the relevant file or library member in the local system