Logging File Transfer Operations

When the message level in the UDM server's configuration is set to audit, the server writes audit messages to the broker log for each file transferred.

The following is an example of the audit messages produced:

NV3950A [1110470739] Transferring from: host: 'Enderlyn.local'
(10.0.0.101), user: 'root', file: '/Volumes/Archive/VPC
Images/.DS_Store'

UNV3951A [1110470739] Transferring to:   host: 'Aluminum.local'
(10.0.0.100), user: 'kevin', file: '/Users/kevin/Desktop/tmp/.DS_Store'

UNV3952A [1110470739] Successfully transferred '/Volumes/Archive/VPC
Images/.DS_Store' on 'Enderlyn.local' to
'/Users/kevin/Desktop/tmp/.DS_Store' on 'Aluminum.local'

The first message is written when the transfer server receives a request to initiate a file transfer and contains the host name of the source machine, the IP address of the source machine, the user authenticated with UDM at the source of the transfer, and the name of the source file to be transferred.

The second message is written when the destination transfer server acknowledges the file transfer requested and contains the host name of the destination machine, the IP address of the destination machine, the user authenticated with UDM at the destination of the transfer, and the destination filename that will be used.

The third message produced indicates that the file was transferred successfully. This message contains the source and destination filenames and host names.

The UDM Manager also can produce these messages when it is involved in a two-party transfer session (though much of the information will be redundant with its standard information messages) by setting its message level to audit. The manager's audit messages are written to stderr (sysout under z/OS).

Reporting Transfer Progress

For long transfer operations, it is often useful to see periodic indications of the operation's progress.

You can get this information by turning on progress reporting using the report command:

report progress=yes

This will cause the UDM manager to issue periodic updates regarding the progress of a file being transferred. The interval these updates are given is the same as the keep alive interval.

Progress messages look as follows:

1024000 bytes processed