Registered Client Log List Display utility

Acquires the log records from a specified client and outputs the records in CSV format to the standard output.

Usage

Send Log and Receive Log

utlhubclientloglist -h hostname[:servicename] [-s | -r] 
  [-fromdate d1] [-todate d2] [-f fileid] [-host hostname] [-notitle]

Request Acknowledge Log

utlhubclientloglist -h hostname[:servicename] -o 
  [-fromdate d1] [-todate d2] [-service name] [-notitle]

Schedule Log

utlhubclientloglist -h hostname[:servicename] -sc 
  [-fromdate d1] [-todate d2] [-id schedule] [-notitle]

Send and Receive Status and Resend Queue Status

utlhubclientloglist -h hostname[:servicename] {-t | -rs} 
  [-fromdate d1] [-notitle]

Today's Schedule

utlhubclientloglist -h hostname[:servicename] -sd 
  [-fromdate d1] [-notitle]

Post-send Job Execution Log and Post-receive Job Execution Log

utlhubclientloglist -h hostname[:servicename] {-js | -jr} 
  [-fromdate d1] [-todate d2] [-f fileid] [-host hostname] [-notitle]

Explanation of parameters

-h hostname[:servicename]

Host name and service name (Mandatory)

Specifies the host name and service name of the client from which you want to acquire the log records.

If you specify a host for which no service name is set, specify only a host name, and do not specify a service name that includes a colon (:).

= Remarks =

If the service name is omitted, it will not be possible to make more than one host with the same host name a target.

[-s | -r | -o | -sc | -t | -rs | -sd | -js | -jr]

Log Type (Optional)

Specify the type of the log records to acquire.

-s:

Send Log

-r:

Receive Log

-o:

Request Acknowledge Log

-sc:

Schedule Log

-t:

Send and Receive Status

-rs:

Resend Queue Status

-sd:

Today's Schedule

-js:

Post-send Job Execution Log

-jr:

Post-receive Job Execution Log

If omitted, -s is assumed to be specified.

Note

-sc (Schedule Log) and -sd (Today's Schedule) can be specified when the host type of the client is Windows.

[-fromdate d1] [-todate d2]

Range of date and time to be output (Optional)

Specify the date and time of the records to be output.

d1 and d2 must be 14-byte numeric values (yyyymmddhhmmss), or 8-byte numeric values (yyyymmdd). If the date is specified with 8-byte numeric values, all the log records in the specified date range are targeted for output.

If -todate is omitted, all the log records on or after the date and time specified by -fromdate are targeted for output.

If -fromdate is omitted, all the log records on or before the date and time specified by -todate are targeted for output.

-todate cannot be specified when Log Type is specified as one of -t (Send and Receive Status), -rs (Resend Queue Status), or -sd (Today's Schedule).

= Remarks =
  • If you specify -fromdate and -todate at the same time, d1 must be equal to or smaller than d2.

  • -fromdate and -todate can have a different date format (14 bytes and 8 bytes).
    Example: -fromdate 20080101 -todate 20080930123000

[-f fileid]

File ID (Optional)

Specify the File ID of the file to be output.

If the targeted client is HULFT8, the ID must be no more than 50 bytes. If the targeted client is HULFT8 or earlier, the ID must be no more than 8 bytes.

If specified, only the log records whose File ID match fileid are targeted. If omitted, all the File IDs are targeted.

This parameter can be specified when the log type is specified as one of -s (Send Log), -r (Receive Log), -js (Post-send Job Execution Log), or -jr (Post-receive Job Execution Log).

[-host hostname]

Name of the remote host (Optional)

Specify the name of the remote host for transfer processing.

If the log type is specified as either -s (Send Log) or -js (Post-send Job Execution Log), only the log records whose receiving side matches hostname are targeted.

If the log type is specified as either -r (Receive Log) or -jr (Post-receive Job Execution Log), only the log records whose sending side matches hostname are targeted.

-host cannot be specified if the log type is none of the above.

[-service name]

Service Name (Optional)

Specify a Request Acknowledge service name to be output.

If specified, only the log records whose service name matches name are targeted. If omitted, all the service names are targeted.

This parameter can be specified when the log type is specified as -o (Request Acknowledge Log).

[-id schedule]

Schedule ID (Optional)

Specify the Schedule ID to be output.

If the targeted client is HULFT8, the ID must be no more than 50 bytes. If the targeted client is HULFT8 or earlier, the ID must be no more than 8 bytes.

If specified, only the log records whose Schedule ID matches schedule are targeted. If omitted, all the Schedule IDs are targeted.

This parameter can be specified when the log type is specified as -sc (Schedule Log).

[-notitle]

Suppression of Title Output (Optional)

If you specify "-notitle", the title line of the CSV header is not output.

If you do not specify "-notitle", a field name is displayed as the header. For details about field names, see Displayed fields.

Status code

0:

The utility was executed successfully.

10:

The specified options are incorrect.

11:

A termination instruction was detected.

12:

Failed to allocate memory.

13:

A system error occurred.

40:

The acquisition was not performed, because the client referred to is outside of control.

41:

The client referred to does not support the length of the specified ID.

60:

An error occurred during the acquisition of the log records.

100:

The relevant Registered Client does not exist.

101 or above:

An SQL error occurred.

Notes on using the utilities

For details about the operation environment for using the utilities, see Notes on execution of utilities (commands).

For this utility, also note the following:

  • The Log records are output using the Kanji code specified with Kanji Code Type (KnjCode) in the System Environment Settings.

  • Request Acknowledge Log records of a client are added each time the utility is executed.

  • If 1000 or more log records are output per second, log records 1 to 999 are output and records 1000 or above are skipped.

  • A large number of trace log records are output when Post-send Job Execution Log or Post-receive Job Execution Log is acquired. Specify a date range, File ID, or host name to narrow down the log records.

  • When acquiring Post-send Job Execution Log or Post-receive Job Execution Log, according to the number of logs stored in the targeted client, it may take substantial time.

Output example

Send Log

"File ID","Send Host Name","Receive Host Name","Start Date","Start Time","End Da 
te","End Time","Send File Name","Status Code","Detail Code","Record Count","Data 
Size","Transmission Rate","Connection Type","Volume Serial","UNIT","Interface D 
BID","Compression Ratio","IP Version","Message 0","Message 1","Message 2","Messa 
ge 3","Message 4","Message 5","Mailbox Use","Send Acknowledge Date","Send Acknow 
ledge Time","Latest Identifier","Starting Identifier","Transfer Block Length","T 
ransfer Block Count","Long Message 0","Long Message 1","Encryption Used","Transf 
er ID","Compression Preference","Code Converted By","Comment"
"FILE01","HOST01","HOST02","2015/09/27","20:16:05","2015/09/27","20:16:09","C:\D
Ata\testdata\snd\test2.txt","000000","00000","454","37682","9420","LAN","","",""
,"0","IPv4","","","","","","","No","2015/09/27","20:16:05","8E49C9451CE0BA19E555
C3B14B6D34B861","8E49C9451CE0BA19E555C3B14B6D34B861","32768","1","","","HULFT","
B120F1DA757382A16A543279343248D781000200000000000000000000000000","None","Sendin
g Side","TEST"

Figure 3.21 Output example of Send Log

Receive Log

"File ID","Send Host Name","Receive Host Name","Start Date","Start Time","End Da 
te","End Time","Receive File Name","Status Code","Detail Code","Record Count","D 
ata Size","Transmission Rate","Connection Type","Volume Serial","UNIT","Interfac 
e DBID","Compression Ratio","IP Version","Message 0","Message 1","Message 2","Me 
ssage 3","Message 4","Message 5","Mailbox Use","Send Acknowledge Date","Send Ack 
nowledge Time","Latest Identifier","Starting Identifier","Transfer Block Length" 
,"Transfer Block Count","Long Message 0","Long Message 1","Encryption Used","Tra 
nsfer ID","Compression Preference","Code Converted By","Comment"
"FILE02","HOST01","HOST02","2013/09/27","20:16:05","2013/09/27","20:16:09","C:\D
Ata\testdata\rcv\moya\rcv02.txt","000000","00000","454","37682","9420","LAN","",
"","","IPv4","","","","","","","No","","","8E49C9451CE0BA19E555C3B14B6D34B861","
8E49C9451CE0BA19E555C3B14B6D34B861","","","","","C4S","6D110461DE9F99883DE3118CD
62665DD81000100000000000000000000000000","None","","TEST"

Figure 3.22 Output example of Receive Log

Request Acknowledge Log

"Service Name","Host Name","Direction Host Name","Direction Acknowledge Date","D 
irection Acknowledge Time","Status Code","Detail Code","Latest Identifier","Star
ting Identifier" 
"HULADMIN","HOST01","HUBSVR","2015/11/11","17:26:41","000735","00000","00D5F51D5 
9BC9A5726877BD1F006955281","00D5F51D59BC9A5726877BD1F006955281"

Figure 3.23 Output example of Request Acknowledge Log

Schedule Log

"Schedule ID","Host Name","Start Date","Start Time","End Date","End Time","Statu 
s Code","Detail Code","Latest Identifier","Starting Identifier" 
"TEST","HOST01","2015/11/11","22:45:00","2015/11/11","22:45:14","000709","00002" 
,"ACD9C7BDC5E0CE76B61182748D357F6041","ACD9C7BDC5E0CE76B61182748D357F6041"

Figure 3.24 Output example of Schedule Log

Send and Receive Status

"Type","File ID","Host Name","Send/Receive Host Name","Direction Date","Directio 
n Time","Status","Connection Type","Size","Total Size","Latest Identifier","Star 
ting Identifier","SEQ No.","File Name","Transfer ID" 
"Send","FILE01","HOST01","HOST02","2015/09/27","20:16:05","Auto Resend Queue","L 
AN","0","37682","8E49C9451CE0BA19E555C3B14B6D34B861","8E49C9451CE0BA19E555C3B14B 
6D34B861","","C:\Data\testdata\snd\Sample.txt","AA5BE71E7E19EE57E822EE567E479FBE
81000100000000000000000000000000"

Figure 3.25 Output example of Send and Receive Status

Resend Queue Status

"File ID","Host Name","Send Host Name","Date","Time","Send File Name","Status Co 
de","Detail Code","Record Count","Total Record Count","Data Size","Total Data Si 
ze","Connection Type","Volume Serial","UNIT","Resend Queue List No.","Message 0" 
,"Message 1","Message 2","Message 3","Message 4","Message 5","Latest Identifier" 
,"Starting Identifier","Long Message 0","Long Message 1" 
"FILE03","HOST01","HOST02","2015/08/27","09:42:10","C:\Data\testdata\snd\test2.t
xt","331701","00003","0","0","0","0","LAN","","","","","","","","","","C12AA2F81
EEF3B279E9031378825C41561","C12AA2F81EEF3B279E9031378825C41561","",""

Figure 3.26 Output example of Resend Queue Status

Today's Schedule

"Status","Schedule ID","Host Name","Execution Date","Start Time","End Time","Sta 
tus Code","Detail Code" 
"Waiting","TEST","HOST01","2015/11/12","22:45:00","","",""

Figure 3.27 Output example of Today's Schedule

Post-send Job Execution Log and Post-receive Job Execution Log

"File ID","Send Host Name","Receive Host Name","Start Date","Start Time","End Ti 
me","Library Name","Job Name","Message ID","Severity","Status","Latest Identifie 
r","Starting Identifier" 
"FILE01","HOST01","HOST02","2013/09/27","20:16:09","20:16:12","","c:\tools\batfi
le\set_exitcode.bat 0","","","0","8E49C9451CE0BA19E555C3B14B6D34B861","8E49C9451
CE0BA19E555C3B14B6D34B861"

Figure 3.28 Output example of Post-send Job Execution Log

Displayed fields

The following table lists and describes the fields shown in the output example.

Legend:

Y:

Available in all versions

7.0:

Available on a client whose version is Ver.7.0 or above.

(In a client whose version is earlier than Ver.7.0, "" is always output.)

8.0:

Available on a client whose version is Ver.8.0 or above.

(In a client whose version is earlier than Ver.8.0, "" is always output.)

8.1:

Available on a client whose version is Ver.8.1 or above.

(In a client whose version is earlier than Ver.8.1, "" is always output.)

8.4:

Available on a client whose version is Ver.8.4 or above.

(In a client whose version is earlier than Ver.8.4, "" is always output.)

-:

Unavailable for the host type ("" is always output.)

Table 3.21 Displayed fields of the Send Log

Type

Field name

Description

Host type of the client

Mainframe

Linux

Windows

IBMi

1

File ID

File ID

Y

Y

Y

Y

2

Send Host Name

The host name of the client specified by -h.

Y

Y

Y

Y

3

Receive Host Name

Host name of the receiving host

Y

Y

Y

Y

4

Start Date

Date when Send processing started (yyyy/mm/dd format)

Y

Y

Y

Y

5

Start Time

Time when Send processing started (hh:mm:ss format)

Y

Y

Y

Y

6

End Date

Date when Send processing completed (yyyy/mm/dd format)

Y

Y

Y

Y

7

End Time

Time when Send processing finished (hh:mm:ss format)

Y

Y

Y

Y

8

Send File Name

Mainframe: Data set name of the Send file

Other than mainframe: File name of the Send file

Y

Y

Y

Y

9

Status Code

Completion code of send processing

Y

Y

Y

Y

10

Detail Code

Detail code of send processing

Y

Y

Y

Y

11

Record Count

Record Count of the Send file

Y

Y

Y

Y

12

Data Size

Data Size of the Send file

Y

Y

Y

Y

13

Transmission Rate

Data transfer length per second (bytes)

Y

Y

Y

Y

14

Connection Type

Connection type with the receiving host

"LAN" or "SAN" (always "LAN" for IBMi)

Y

Y

Y

Y

15

Volume Serial

Volume serial of the Send file

Y

-

-

-

16

UNIT

UNIT name where the Send file is stored

6.0

-

-

-

17

Interface DBID

Interface DBID which is registered in the Send Management Information

Y

Y

Y

Y

18

Compression Ratio

Data compression ratio at the time of compression

6.0

6.0

6.0

6.0

19

IP Version

IP Version used for communication

"IPv4" or "IPv6"

Y

Y

Y

Y

20

Message 0

Messages 0 to 5 specified by the Send File command or Send Request command of HULFT

6.0

6.0

6.0

6.0

21

Message 1

6.0

6.0

6.0

6.0

22

Message 2

6.0

6.0

6.0

6.0

23

Message 3

6.0

6.0

6.0

6.0

24

Message 4

6.0

6.0

6.0

6.0

25

Message 5

6.0

6.0

6.0

6.0

26

Mailbox Use

Whether the mailbox is used or not

"Yes" or "No"

-

-

6.2

-

27

Send Acknowledge Date

The date when the Send File is acknowledged (yyyy/mm/dd format)

6.3

6.3

6.3

6.3

28

Send Acknowledge Time

The time when the Send File is acknowledged (hh:mm:ss format)

6.3

6.3

6.3

6.3

29

Latest Identifier

Latest Identifier

7.0

7.0

7.0

7.0

30

Starting Identifier

Starting Identifier

7.0

7.0

7.0

7.0

31

Transfer Block Length

Transfer Block Length at the time of Send File

8.1

8.0

8.0

8.1

32

Transfer Block Count

Transfer Block Count at the time of Send File

8.1

8.0

8.0

8.1

33

Long message 0

Long Messages 0 to 1 specified by the Send File command or Send Request command of HULFT

8.1

8.0

8.0

8.1

34

Long message 1

8.1

8.0

8.0

8.1

35

Encryption Used

Encryption Scheme used in the encryption of the Send file.

"-" (no encryption), "HULFT", "C4S", "AES", or "OTHER"

8.1

8.1

8.1

8.1

36

Transfer ID

The unique identifier issued for each file transfer

8.4

8.4

8.4

8.4

37

Compression Preference

The compression preference of the Send file

'None', 'Horizontal', 'Vertical', 'DEFLATE', or 'Zstandard'

8.4

8.4

8.4

8.4

38

Code Converted By

Detects the existence of a host that carries out the code conversion of files or detects the existence of code conversion

8.4

8.4

8.4

8.4

39

Comment

Comments for the Send Management Information

8.4

8.4

8.4

8.4

Table 3.22 Displayed fields of the Receive Log

Type

Field name

Description

Host type of the client

Mainframe

Linux

Windows

IBMi

1

File ID

File ID

Y

Y

Y

Y

2

Send Host Name

Host name of the sending host

Y

Y

Y

Y

3

Receive Host Name

The host name of the client specified by -h.

Y

Y

Y

Y

4

Start Date

Date when Receive processing started (yyyy/mm/dd format)

Y

Y

Y

Y

5

Start Time

Time when Receive processing started (hh:mm:ss format)

Y

Y

Y

Y

6

End Date

Date when Receive processing completed (yyyy/mm/dd format)

Y

Y

Y

Y

7

End Time

Time when Receive processing completed (hh:mm:ss format)

Y

Y

Y

Y

8

Receive File Name

Mainframe: Data set name of the Receive file

Other than mainframe: File name of the Receive file

Y

Y

Y

Y

9

Status Code

Completion code of receive processing

Y

Y

Y

Y

10

Detail Code

Detail code of receive processing

Y

Y

Y

Y

11

Record Count

Number of records of the Receive file

Y

Y

Y

Y

12

Data Size

Data Size of the Receive file

Y

Y

Y

Y

13

Transmission Rate

Data transfer length per second (bytes)

Y

Y

Y

Y

14

Connection Type

Connection type with the sending host

"LAN" or "SAN" (always "LAN" for IBMi)

Y

Y

Y

Y

15

Volume Serial

Volume serial of the Receive file

Y

-

-

-

16

UNIT

UNIT name where the Receive file is stored

Y

-

-

-

17

Interface DBID

Interface DBID which is registered in the Send Management Information

-

Y

Y

-

18

Compression Ratio

Always ""

-

-

-

-

19

IP Version

IP Version used for communication

"IPv4" or "IPv6"

Y

Y

Y

Y

20

Message 0

Messages 0 to 5 specified by the Send File command or Send Request command of HULFT

6.0

6.0

6.0

6.0

21

Message 1

6.0

6.0

6.0

6.0

22

Message 2

6.0

6.0

6.0

6.0

23

Message 3

6.0

6.0

6.0

6.0

24

Message 4

6.0

6.0

6.0

6.0

25

Message 5

6.0

6.0

6.0

6.0

26

Mailbox Use

Whether the mailbox is used or not

"Yes" or "No"

-

-

6.2

-

27

Send Acknowledge Date

Always ""

-

-

-

-

28

Send Acknowledge Time

Always ""

-

-

-

-

29

Latest Identifier

Latest Identifier

7.0

7.0

7.0

7.0

30

Starting Identifier

Starting Identifier

7.0

7.0

7.0

7.0

31

Transfer Block Length

Always ""

8.1

8.0

8.0

8.1

32

Transfer Block Count

Always ""

8.1

8.0

8.0

8.1

33

Long message 0

Long Messages 0 to 1 specified by the Send File command or Send Request command of HULFT

8.1

8.0

8.0

8.1

34

Long message 1

8.1

8.0

8.0

8.1

35

Encryption Used

Encryption Scheme used in the decryption of the Receive file

"-" (no encryption), "HULFT", "C4S", "AES", or "OTHER"

8.1

8.1

8.1

8.1

36

Transfer ID

The unique identifier issued for each file transfer

8.4

8.4

8.4

8.4

37

Compression Preference

The compression preference of the Receive file

'None', 'Horizontal', 'Vertical', 'DEFLATE', or 'Zstandard'

8.4

8.4

8.4

8.4

38

Code Converted By

Always ""

-

-

-

-

39

Comment

Comments for the Receive Management Information

8.4

8.4

8.4

8.4

Table 3.23 Displayed fields of the Request Acknowledge Log

Type

Field name

Description

Host type of the client

Mainframe

Linux

Windows

IBMi

1

Service Name

Service name of the acknowledged request

Y

Y

Y

Y

2

Host Name

The host name of the client specified by -h.

Y

Y

Y

Y

3

Direction Host Name

Name of the host that issued the request

Y

Y

Y

Y

4

Direction Acknowledge Date

Date when the request is acknowledged (yyyy/mm/dd format)

Y

Y

Y

Y

5

Direction Acknowledge Time

Time when the request is acknowledged (hh:mm:ss format)

Y

Y

Y

Y

6

Status Code

Status Code of request acknowledge processing

Y

Y

Y

Y

7

Detail Code

Detail Code of request acknowledge processing

Y

Y

Y

Y

8

Latest Identifier

Latest Identifier

7.0

7.0

7.0

7.0

9

Starting Identifier

Starting Identifier

7.0

7.0

7.0

7.0

Table 3.24 Displayed fields of Schedule Log

Type

Field name

Description

Host type of the client

Windows

1

Schedule ID

Schedule ID

Y

2

Host Name

The host name of the client specified by -h.

Y

3

Start Date

The date when the scheduled execution started (yyyy/mm/dd format)

Y

4

Start time

The time when the scheduled execution started (hh:mm:ss format)

Y

5

End Date

The date when the scheduled execution ended (yyyy/mm/dd format)

Y

6

End Time

The time when the scheduled execution ended (hh:mm:ss format)

Y

7

Status Code

Status Code of the schedule processing

Y

8

Detail Code

Detail code of the schedule processing

Y

9

Latest Identifier

Latest Identifier

7.0

10

Starting Identifier

Starting Identifier

7.0

Table 3.25 Displayed fields of the Send and Receive Status

Type

Field name

Description

Host type of the client

Mainframe

Linux

Windows

IBMi

1

Type

Transfer type

"Sending" or "Receiving"

Y

Y

Y

Y

2

File ID

File ID

Y

Y

Y

Y

3

Host Name

The host name of the client specified by -h.

Y

Y

Y

Y

4

Send/Receive Host Name

Name of the remote host for transfer processing

Y

Y

Y

Y

5

Direction Date

Date when the direction is acknowledged (yyyy/mm/dd format)

Y

Y

Y

Y

6

Direction Time

Time when the direction is acknowledged (hh:mm:ss format)

Y

Y

Y

Y

7

Status

Status of transfer

"Send Queue", "Connecting", "Standby", "Sending File", "Auto Resend Queue", "Receiving File", "Job in Execution", "Outputting CSV", "Interfacing with DB", "Outputting XML", or "Disconnecting"

Y

Y

Y

Y

8

Connection Type

Connection type between the sending host and receiving host

"LAN" or "SAN" (always "LAN" for IBMi)

Y

Y

Y

Y

9

Size

Mainframe:

For sending, total number of records of the Send File

For receiving, total number of records that have been received.

Linux and Windows:

Data size of transferred data

Y

Y

Y

-

10

Total Size

Windows:

For Send operation, total size of the Send File

For Receive operation, 0

-

-

Y

-

11

Latest Identifier

Latest Identifier

7.0

7.0

7.0

7.0

12

Starting Identifier

Starting Identifier

7.0

7.0

7.0

7.0

13

SEQ No.

For sending, a send sequence number

For receiving, a receive sequence number

8.1

-

-

-

14

File Name

For sending, the Send File Name

For receiving, the Receive File Name

8.4

8.4

8.4

8.4

15

Transfer ID

The unique identifier issued for each file transfer

8.4

8.4

8.4

8.4

Table 3.26 Displayed fields of the Resend Queue Status

Type

Field name

Description

Host type of the client

Mainframe

Linux

Windows

IBMi

1

File ID

File ID

Y

Y

Y

Y

2

Host Name

The host name of the client specified by -h.

Y

Y

Y

Y

3

Send Host Name

Host name of the receiving host

Y

Y

Y

Y

4

Date

Date when sending error occurred (yyyy/mm/dd format)

Y

Y

Y

Y

5

Time

Time when sending error occurred (hh:mm:ss format)

Y

Y

Y

Y

6

Send File Name

Time when the direction is acknowledged (hh:mm:ss format)

Y

Y

Y

Y

7

Status Code

Completion code of send processing

Y

Y

Y

Y

8

Detail Code

Detail code of send processing

Y

Y

Y

Y

9

Record Count

Number of records that have been sent

Y

Y

Y

Y

10

Total Record Count

Total number of records in the entire Send files

Y

Y

Y

Y

11

Data Size

Data size of sent data

Y

Y

Y

Y

12

Total Data Size

Total data size of the entire Send files

Y

Y

Y

Y

13

Connection Type

Connection type with the receiving host

"LAN" or "SAN" (always "LAN" for IBMi)

Y

Y

Y

Y

14

Volume Serial

Volume serial of the send file

Y

-

-

-

15

UNIT

UNIT name where the send file is stored

6.0

-

-

-

16

Resend Queue List No.

Serial number added when registered in the Resend Queue

6.3

-

-

-

17

Message 0

Messages 0 to 5 specified by the Send File command or Send Request command of HULFT

6.0

6.0

6.0

6.0

18

Message 1

6.0

6.0

6.0

6.0

19

Message 2

6.0

6.0

6.0

6.0

20

Message 3

6.0

6.0

6.0

6.0

21

Message 4

6.0

6.0

6.0

6.0

22

Message 5

6.0

6.0

6.0

6.0

23

Latest Identifier

Latest Identifier

7.0

7.0

7.0

7.0

24

Starting Identifier

Starting Identifier

7.0

7.0

7.0

7.0

25

Long message 0

Long Messages 0 to 1 specified by the Send File command or Send Request command of HULFT

8.1

8.0

8.0

8.1

26

Long message 1

8.1

8.0

8.0

8.1

Table 3.27 Displayed fields of Today's Schedule

Type

Field name

Description

Host type of the client

Windows

1

Status

Execution status of the schedule

"Waiting", "In Execution", "Terminated", or "Cancel"

Y

2

Schedule ID

Schedule ID

Y

3

Host Name

The host name of the client specified by -h.

Y

4

Execution Date

The date when the scheduled execution started or the scheduled start date (yyyy/mm/dd format)

Y

5

Start Time

The time when the scheduled execution started or the scheduled start time (hh:mm:ss format)

Y

6

End Time

The time when the scheduled execution ended (hh:mm:ss format)

If the Status is "Waiting" or "In Execution", "".

Y

7

Status Code

Status Code of the schedule processing

If the Status is "Waiting" or "In Execution", "".

Y

8

Detail Code

Detail code of the schedule processing

If the Status is "Waiting" or "In Execution", "".

Y

Table 3.28 Displayed fields of the Post-send Job Execution Log

Type

Field name

Description

Host type of the client

Mainframe

Linux

Windows

IBMi

1

File ID

File ID

Y

Y

Y

Y

2

Send Host Name

The host name of the client specified by -h.

Y

Y

Y

Y

3

Receive Host Name

Host name of the receiving host

Y

Y

Y

Y

4

Start Date

The date when the job execution started (yyyy/mm/dd format)

Y

Y

Y

Y

5

Start Time

The time when the job execution started (hh:mm:ss format)

Y

Y

Y

Y

6

End Time

The time when the job execution ended (hh:mm:ss format)

Y

Y

Y

Y

7

Library Name

The name of the data set where the job is stored.

Y

-

-

-

8

Job Name

Job started after Send operation is completed

Y

Y

Y

Y

9

Message ID

Message ID at the time when the job ends

-

-

-

Y

10

Severity

Severity of message at the time when the job ends

-

-

-

Y

11

Status

Mainframe:

"0" (Waiting), "1" (In Execution),

"2" (Ended Unsuccessfully), "3" (Ended Successfully),

"4" (Error)

Linux and Windows:

exit code of a job

IBMi:

"0" (Waiting), "1" (In Execution),

"2" (End), "3" (Non-executable)

Y

Y

Y

Y

12

Latest Identifier

Latest Identifier

7.0

7.0

7.0

7.0

13

Starting Identifier

Starting Identifier

7.0

7.0

7.0

7.0

Table 3.29 Displayed fields of the Post-receive Job Execution Log

Type

Field name

Description

Host type of the client

Mainframe

Linux

Windows

IBMi

1

File ID

File ID

Y

Y

Y

Y

2

Send Host Name

Host name of the sending host

Y

Y

Y

Y

3

Receive Host Name

The host name of the client specified by -h.

Y

Y

Y

Y

4

Start Date

The date when the job execution started (yyyy/mm/dd format)

Y

Y

Y

Y

5

Start Time

The time when the job execution started (hh:mm:ss format)

Y

Y

Y

Y

6

End Time

The time when the job execution ended (hh:mm:ss format)

Y

Y

Y

Y

7

Library Name

The name of the data set where the job is stored.

Y

-

-

-

8

Job Name

Job that started after Receive operation is completed

Y

Y

Y

Y

9

Message ID

Message ID at the time when the job ends

-

-

-

Y

10

Severity

Severity of message at the time when the job ends

-

-

-

Y

11

Status

Mainframe:

"0" (Waiting), "1" (In Execution),

"2" (Ended Unsuccessfully), "3" (Ended Successfully),

"4" (Error)

Linux and Windows:

exit code of a job

IBMi:

"0" (Waiting), "1" (In Execution),

"2" (End), "3" (Non-executable)

Y

Y

Y

Y

12

Latest Identifier

Latest Identifier

7.0

7.0

7.0

7.0

13

Starting Identifier

Starting Identifier

7.0

7.0

7.0

7.0