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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

If an error occurred while processing one of these steps, the corresponding<br />

error handling mechanisms are started. Specifying the function code COPY<br />

means to transfer a file between the local and the remote system. After a successful<br />

copy, the file is stored in <strong>MVS</strong> and registered in the OSI/File Services<br />

filestore at both the sending and receiving systems.<br />

<strong>3.</strong> After OSI/File Services has finished the transfer, the result is available at the<br />

OSI/File Services interface (success or failure of the transfer). The OSI server<br />

converts the format of the result to the format needed by the queue handler,<br />

and then passes the result to the queue handler. Therefore, OSI/File Services<br />

terminology is used in some situations rather than <strong>NetView</strong> <strong>FTP</strong> terminology.<br />

4. Further processing is done asynchronously. After one request is passed to<br />

OSI/File Services, the OSI server is ready to process the next request. This is<br />

done independently of completion of the previous request.<br />

5. When an OSI/File Services activity is completed, the result is available via the<br />

GET_RESULT command at the OSI/File Services interface. The server keeps<br />

the information necessary to obtain the result, and continues processing the<br />

current request. For further information, refer to either the OSI/File Services<br />

System/370 Programming Guide or the OSI/File Services System/370 User’s<br />

Guide.<br />

6. The OSI server asks for the result in the next processing cycle. The result of<br />

the transfer includes detailed information about the success or failure of the<br />

transfer, and the number of bytes transferred. This information is passed to the<br />

queue handler.<br />

If the function specified is MOVE, the same steps as for function COPY are performed<br />

to process the MOVE request. After a successful MOVE:<br />

� The file is removed from the sending system<br />

� The file entry is removed from the filestore at the sending system.<br />

Stopping <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> Running<br />

You stop <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> running by stopping the queue handler using<br />

the STOP command.<br />

When you stop the queue handler, all running servers are stopped immediately.<br />

The file transfers that are currently being processed are interrupted and checkpoints<br />

are taken for the SNA file transfers. When you restart the queue handler,<br />

any file-transfer request that specified automatic transfer restart is rescheduled<br />

when a server that serves its request class becomes available.<br />

You can also stop the queue handler by stopping the server first, using the<br />

MODIFY command, and then stopping the queue handler. The file transfers that<br />

are currently being processed are either completed or not, depending on the<br />

command options you used. For further information, refer to <strong>Chapter</strong> 3, “<strong>Operating</strong><br />

<strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong>” on page 4<strong>3.</strong><br />

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