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.

Continue to submit the job until one of the following is true:<br />

� The return code or reason code given in the message is nonzero and the<br />

status of the request is W or F.<br />

There was a problem. Analyze the return and reason codes, these are<br />

described in the <strong>NetView</strong> <strong>FTP</strong> Messages and Codes manual, and correct the<br />

problem.<br />

A common problem is that one or both servers are not ready.<br />

If the problem was that the session could not be established because the<br />

receiving server had not started until after the sending server tried to establish<br />

a session, wait five minutes. Five minutes after its initial attempt, the sending<br />

server tries again to establish the session.<br />

If this was not the cause of the problem, stop the two servers. How to do this<br />

is described in “Stopping a Server” on page 61. You can then read and<br />

analyze the messages that were written to the file defined to DVGLOG in the<br />

server JCL. After you have corrected the problem, restart the servers. How to<br />

do this is described in “Starting a Server” on page 47.<br />

If the status of the transfer request was:<br />

F Resubmit the job shown in Figure 23 on page 30.<br />

W The request is automatically reprocessed when the servers are restarted.<br />

� The status of the request remains W and the return and reason codes remain<br />

zero for more than two minutes.<br />

Check whether the two servers are still running and, if so, which classes they<br />

serve. Do this by entering F QH,D from the operator console. The system<br />

displays the system status.<br />

If server 01 does not serve class 1, stop server 01 as described in “Stopping a<br />

Server” on page 61, change the startup parameters accordingly, and restart<br />

server 01.<br />

If the server classes are correct, stop both servers and check the messages<br />

that were written to the file defined to DVGLOG in the server JCL. After you<br />

have corrected the problem, restart the servers. How to do this is described in<br />

“Starting a Server” on page 47.<br />

� The status of the request is F, and the return and reason codes are both zero.<br />

The file transfer was carried out successfully.<br />

For a complete description of how to create and add requests to the request queue<br />

refer to the <strong>NetView</strong> <strong>FTP</strong> V2 <strong>MVS</strong> User’s Guide.<br />

32 <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!