Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Detailed ftshwr output

&pagelevel(5)&pagelevel

Example for the detailed output of the request with request ID 131074:

Unix systems:

ftshwr -l 131074 
TRANSFER-ID =131074      STORE  =17-01-25 11:45:27  FILESIZE=514610 
   STATE    =WAIT        BYTECNT=0                  PROGRESS=NA
   INITIATOR=LOCAL       TRANS  =FROM
   WRITE    =REPLACE     START  =SOON               CANCEL  =NO
   COMPRESS =NONE        DATA   =CHAR               PRIO    =NORM
   TRANSP   =NO          ENCRYPT=NO 
   TARGFORM =BLOCK       TRECFRM=STD 
   OWNER    =maier       DICHECK=NO
   FNC-MODE =CHAR                                   RECFORM =VARIABLE
   PARTNER  =ftserv01.mycompany.net
   PARTNER-STATE = ACT
   PARTNER-PRIO  = NORM
   LOC: FILE     =/home2/memo02.txt
        TRANS-ADM=(maier)
        CCSN     =ISO88591
   REM: FILE     =/home/save/memo02.txt
        TRANS-ADM=(servelog)

Windows systems:

TRANSFER-ID =131074      STORE  =17-01-25 11:49:11  FILESIZE=514610

   STATE    =WAIT        BYTECNT=0                  PROGRESS=NA

   INITIATOR=LOCAL       TRANS  =FROM
   WRITE    =REPLACE     START  =SOON               CANCEL  =NO

   COMPRESS =NONE        DATA   =CHAR               PRIO    =NORM

   TRANSP   =NO          ENCRYPT=NO
   TARGFORM =BLOCK       TRECFRM=STD

   OWNER    =maier       DICHECK=NO

   FNC-MODE =TRANSPARENT                            RECFORM =VARIABLE
   PARTNER  =ftserv01.mycompany.net

   PARTNER-STATE = ACT

   PARTNER-PRIO  = NORM
   LOC: FILE     =E:\memo02.txt

        TRANS-ADM=(mydomain\maier)

        CCSN     =CP1252
   REM: FILE     =memo02.txt

        TRANS-ADM=(servelog)

Example of detailed output of inbound request with request ID 524410:

ftshwr -l 524410
   TRANSFER-ID =524410  STORE =17-01-25 14:33:24   FILESIZE=10485760
   STATE =ACTIVE        BYTECNT=0                  PROGRESS=NA
   INITIATOR=REMOTE     TRANS =FROM                RECSIZE =1024
   WRITE =REPLACE       START =SOON                CANCEL =NO
   COMPRESS =NONE       DATA =CHAR                 PRIO =
   TRANSP =NO           ENCRYPT=NO                 GLOB-ID =852520
   OWNER =user1         DICHECK=NO                 TABEXP =NO
   FNC-MODE =CHAR                                  RECFORM =VARIABLE
   PARTNER =ftserv.mycompany.net
   PARTNER-STATE =ACT
   PARTNER-PRIO =NORM
   FILE =par.file.S3.C31
   TRANS-ADM=(serv,)

Explanation of the output

TRANSFER-ID (transfer identification)

Request ID which openFT uses to identify file transfer requests. Requests can be canceled using the ftcanr and the request ID.

STATE

State of the request. Possible values:

ACTIVE

The request is currently being processed.

WAIT

The request is waiting. If the cause of the WAIT state is known, further information is indicated in the PARTNER-STATE field.

LOCKED

The request is temporarily excluded from processing. This status can also occur at openFT and at FTAM partners.

With openFT partners, when a resource bottleneck is encountered or if external data media must first be made available for example.

With FTAM partners, when one of the partners proposes a waiting period until the next start or recovery attempt via the FTAM protocol, and this period exceeds the delay normally permitted.

If the cause of the LOCKED state is known, further information is indicated in the PARTNER-STATE field.

CANCELLED

The request was cancelled in the local system. However, the remote system is aware of its existence because, for example, it was previously active. Therefore, the request cannot be removed from the request queue until the connection to the partner has been re-established.

FINISHED

This status occurs for requests involving FTAM partners when the request has either been completed or cancelled, but the user has not yet been informed of this.

HOLD

The start time specified when the request was issued has not yet been reached.

SUSPENDED

The request was interrupted.

INITIATOR

This specifies where the request was issued. Possible values:

LOCAL

The request was issued in the local system.

REMOTE

The request was issued in the remote system.

WRITE

This specifies whether the destination file is to be overwritten, extended or created. Possible values:

OVERWRITE (default value)

If the destination file already exists, it is overwritten; otherwise, it is created.

EXTEND

If the destination file already exists, the file sent is appended to the destination file.

If the destination file did not exist, it is created.

NEW

A new destination file is created and written.

COMPRESS

This specifies whether the file should be transferred with data compression.

Possible values: BYTE, ZIP, NONE.

TRANSP

Indicated whether the file is to be sent in transparent file format. Possible values: YES, NO

TARGFORM

Format of the file in the target system.

Possible values:

STD (default value)

The file is saved in the same format as in the sending system.

BLOCK

The file is saved in block format.

SEQ

The file is saved as a sequential file.

OWNER

Local login name.

FNC-MODE

Encoding mode for remote file names and follow-up processing. Possible values:

TRANSPARENT

Encoding in transparent mode.

CHAR

Encoding in character mode.

PARTNER

Name or address of the partner, see also section “Specifying partner addresses”.

PARTNER-STATE

Status of the partner. Possible values:

ACT

Activated

DEACT

Deactivated

NOCON

No connection, for example because the openFT server has not been started in the remote system.

INSTERR

An installation or configuration error has occurred (the local system is not known to the partner, for instance), authentication of one of the partners has failed, or the encryption is local, or the encryption is not available at 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

Properties in the local system:

FILE

File name in the local system

TRANS-ADM

Transfer admission for the local system

CCSN

CCS name used in the local system. The CCSN is only output for text files.

SUCC-PROC

Local follow-up processing commands if successful (if specified in the request).

FAIL-PROC

Local follow-up processing commands if unsuccessful (if specified in the request).

REM

Properties in the remote system:

FILE

File name in the remote system

TRANS-ADM

Transfer admission in the remote system. Possible values:

REMOTE-PROFILE

request with FTAC transfer admission

TRANS-ADM=(user ID)

request with user ID,,password

CCSN

CCS name used in the remote system

SUCC-PROC

Remote follow-up processing commands if successful (if specified in the request).

FAIL-PROC

Remote follow-up processing commands if unsuccessful (if specified in the request).

STORE

Indicates the time at which the request was entered in the request queue.

BYTECNT

This value is output only if the request is currently active or if it was already active and the file transfer has been interrupted. BYTECNT indicates the number of bytes transferred and saved up to now. The counter is updated regularly.

TRANS

This shows the direction of transfer. Possible values are:

TO

The file is sent.

FROM

The file is received.

START

Indicates the time at which the request is to be started. Possible values:

Date / Time

The date and time at which the request is to be started is output.

SOON

The request should be started as soon as possible.

No entry

The request was issued in the remote system.

DATA

Indicates the file type. Possible values:

CHAR (default value for openFT partners)

The file contains text with variable record lengths.

BIN

The file contains an unstructured sequence of binary data.

USER

The file contains structured binary data with variable record length.

ENCRYPT

Indicates whether data encryption was specified.

Possible values: NO, YES.

TRECFRM

Record format of the file in the target system

Possible values:

STD (default value)

The file is saved with the same record format as in the sending system.

UNDEFINED

The file is saved with an undefined record format.

DICHECK

Specifies whether the integrity of the data is to be checked.

Possible values: NO, YES.

FILESIZE

Size of the file in bytes. If the output is followed by a "K", the output is in kilobytes. If it is followed by an "M", the output is in megabytes. The size is indicated here only if the request was already active. For receive requests, a value is indicated here only if the partner has sent one with the request.

PROGRESS

In case of directory transfer this column indicates the progress of directory transfer in the format mm/nn where mm is the number of subdirectories and files already transferred and nn is the total number of subdirectories and files to be transferred.

NA (not applicable)

indicates that either the directory transfer has not yet been started or a single file is to be transferred.

RECSIZE

Maximum record size, if specified.

CANCEL

If the "Cancel-Timer" was set, the time at which the request is deleted from the request queue is indicated here. If no cancel time was specified in the request, NO is output.

PRIO

Request priority. Possible values:

NORM

The request has normal priority

LOW

The request has low priority

No entry

The request was issued in the remote system.

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.

TABEXP

Tabulator expansion and the conversion of blank lines into lines with one character activated/deactivated, only relevant for outbound send requests.

Possible values: YES, NO

RECFORM

Record format.

Possible values: UNDEFINED, VARIABLE, FIX.

DIAGCODE

This column is usually empty. Otherwise, it provides further diagnostic information on operational states in the form of a CMX return code or an FTAM or openFT diagnostic code. FTNEA diagnostic codes have the format NEBFnnnn (NEABF) or NEBDnnnn (NEABD). The following openFT diagnostic codes have been defined:

Value

Meaning

0

No cause specified.

1

Connection setup normal.

2

There is a resource bottleneck.

3

There is a resource bottleneck; the connection will be set up later by the rejecting
entity.

4

Initialization is not yet complete.

5

SHUTDOWN is in progress.

6

The requesting entity is unknown.

7

A protocol error has occurred.

8

A transport error has occurred.

9

A system error has occurred.

10

This code is reserved (for SN77309 part 5).

11

The connection is not accepted without encryption.


FTAM diagnostic codes have the format FTAMnnnn and values from the ISO 8571-3 standard. An extract of possible diagnostic codes taken from the standard can be found in the section “FTAM diagnostic codes as per ISO 8571-3”.

The following values are only output for FTAM partners:

STOR-ACCOUNT

Account number; is output only if specified by the user.

AVAILABILITY

Possible values: IMMEDIATE, DEFERRED.

Is output only if specified by the user.

ACCESS-RIGHTS

Access mode

Possible values: combinations of r, i, p, x, e, a, c, d.

Is output only if specified by the user.

LEGAL-QUAL

Legal qualification

Is output only if the local system is the initiator and the value is specified by the user.