05.02.2013 Views

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

NAME<br />

The cluster name shown is a sample only.<br />

VOLUMES<br />

If you are not using SMS, include the VOLUMES parameter.<br />

SHAREOPTIONS<br />

To allow servers to share the same checkpoint data set, each server startup<br />

job (procedure) must specify DISP=SHR in the checkpoint data set’s DD statement.<br />

The servers serialize access to the checkpoint data set by using ENQ/DEQ.<br />

The SEQOUT DD statement defines the sequential file that IEBDG initializes with<br />

the initial checkpoint record.<br />

CRRDATA Defines the sequential file that is used in this step to load the<br />

checkpoint data set. It must be the same name you specified in the<br />

SEQOUT DD statement.<br />

What to Do when the Checkpoint Data Set Becomes Full<br />

<strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> automatically deletes each checkpoint record that corresponds<br />

to a successful file transfer. However, if many file transfers are interrupted<br />

and not restarted, the checkpoint data set can become full. When the checkpoint<br />

data set is full, only receiving servers conducting file transfers for which there is<br />

already a checkpoint record in the checkpoint data set can take checkpoints—other<br />

receiving servers cannot.<br />

The file-transfer reports that the other receiving servers create each contain a<br />

message indicating that the checkpoint data set is full. These messages are also<br />

sent to the operator console to enable automated operations to commence. Refer<br />

to message DVG670I for information about CLISTs.<br />

If <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> detects an overflow during a file transfer, it does not<br />

interrupt the file transfer, but continues the transfer. However, no additional<br />

recovery information can be stored. In the case of an interrupt, <strong>NetView</strong> <strong>FTP</strong><br />

<strong>V2.2.1</strong> <strong>MVS</strong> restarts the file transfer from an earlier checkpoint or from the beginning<br />

of the file. The <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> report files created for each file<br />

transfer contain an I/O error message for the <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> checkpoint<br />

data set, indicating the overflow condition.<br />

When all transfers that are currently being processed have finished, the server that<br />

detected the overflow condition automatically terminates. If all of your servers<br />

share the same checkpoint data set you should stop <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong><br />

without interrupting the file transfers that are currently being processed. Otherwise<br />

you should stop those servers that access the checkpoint data set in error.<br />

76 <strong>NetView</strong> <strong>FTP</strong> V2 <strong>MVS</strong> Installation, Operation, and Administration

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!