Chapter 3. Operating NetView FTP V2.2.1 MVS - IBM

The sequence in the case of a temporary error is:
1. ADD record
2. OBTAIN record
3. NOTIFY record DVGNTYPE=S DVGNRTYP=�
4a. NOTIFY record DVGNTYPE=S DVGNRTYP=A
4b. OBTAIN record
4c. NOTIFY record DVGNTYPE=S DVGNRTYP=�
5. NOTIFY record DVGNTYPE=F DVGNRTYP=�
In this sequence, item 4 is repeated as often as the request is restarted. The
return and reason code indicates whether the file transfer ended successfully or
not.
The sequence in the case of manual restart is:
1. ADD record
2. OBTAIN record
3. NOTIFY record DVGNTYPE=S DVGNRTYP=M
4. NOTIFY record DVGNTYPE=F DVGNRTYP=�
5. RESTART record
6. OBTAIN record
7. NOTIFY record DVGNTYPE=S
8. NOTIFY record DVGNTYPE=F
The return and reason code indicates whether the file transfer ended successfully
or not. In this case, a transfer request for the same sending and receiving data set
has been interrupted and has terminated with a return and reason code. This has
left a checkpoint-restart record at the receiving system. If the value of the Restart
from Checkpoint parameter is YES, NetView FTP V2.2.1 MVS tries to restart the
transfer from the last recorded checkpoint. This sequence corresponds to the
restart of the transfer from the last checkpoint.
The sequence in the case of a permanent error that occurs before the first checkpoint
is taken is:
1. ADD record
2. OBTAIN record
3. NOTIFY record DVGNTYPE=F DVGNRTYP=�
The return and reason code indicates an unsuccessful file transfer.
The sequence in the case of a permanent error that occurs after the first checkpoint
is taken is:
1. ADD record
2. OBTAIN record
3. NOTIFY record DVGNTYPE=S DVGNRTYP=�
4. NOTIFY record DVGNTYPE=F DVGNRTYP=�
The return and reason code indicates an unsuccessful file transfer.
When looking at the SMF records written by the server (subtype X'51'), you find a
record for each time a transfer was handled. If a transfer is restarted (more than
once), you find one record for each transfer attempt. The byte count and processor
microsecond values always denote one single transfer attempt or partial transfer.
Note that SMF records for remotely initiated transfers do not necessarily contain all
information that is available for locally initiated transfers, for example, a specified
server group name is not available on the responding system.
Appendix H. Layout of the SMF Records 225