Chapter 3. Operating NetView FTP V2.2.1 MVS - IBM
Chapter 3. Operating NetView FTP V2.2.1 MVS - IBM
Chapter 3. Operating NetView FTP V2.2.1 MVS - IBM
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
If you request a restart from a checkpoint but the checkpoint record cannot be<br />
found, <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> does the following:<br />
– If the requesting system is <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> or <strong>NetView</strong> <strong>FTP</strong> for<br />
Workstations, <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> ends the file transfer with an error.<br />
– If the requesting system is <strong>NetView</strong> <strong>FTP</strong> V2.1 <strong>MVS</strong>, <strong>NetView</strong> <strong>FTP</strong> VM,<br />
<strong>NetView</strong> <strong>FTP</strong> VSE, or <strong>NetView</strong> <strong>FTP</strong>/400, <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> restarts<br />
the file transfer from the beginning of the data set.<br />
Special Considerations for Using Checkpoints during a Manual<br />
Restart of a File Transfer<br />
You can perform a manual transfer restart from checkpoint for most errors.<br />
However, there can be error situations, where <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> cannot<br />
perform exceptional checkpointing, for example, if the server subtask that processes<br />
the file transfer terminates abnormally.<br />
In these situations <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> can only use the regularly written<br />
checkpoint record when it restarts a file transfer.<br />
If an error occurs during the transfer of a temporary data set, a restart from checkpoint<br />
fails if the data set no longer exists.<br />
In the following situations <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> may not be able to close a<br />
data set:<br />
� The system terminates.<br />
� The system detects an overflow condition for the data set.<br />
� The server subtask that is performing the file transfer terminates abnormally.<br />
Under any of these circumstances, <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> tries to close the data<br />
set, but special error conditions in the system can prevent it from succeeding.<br />
When, due to an interruption, <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> cannot close a PDS<br />
member, the PDS directory is not updated, and so does not reflect the changes<br />
that the transfer has effected. It is possible that, although records have been<br />
written to a new member of a PDS, the member cannot be found after an interrupt<br />
in the transfer. In this case a restart from the recorded checkpoint does not work.<br />
If you encounter such a problem, submit the file-transfer request again.<br />
When, due to the interruption, <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> is not able to close a<br />
VSAM data set, you may have to use the Access Method Services (AMS) VERIFY<br />
command to close the data set manually before you let <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong><br />
continue the file transfer.<br />
192 <strong>NetView</strong> <strong>FTP</strong> V2 <strong>MVS</strong> Installation, Operation, and Administration