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.

When files are transferred using OSI protocols, only information that complies with<br />

the FTAM standard can be sent to the remote system. Because of this, the following<br />

is not available for an OSI file transfer:<br />

� Automatic generation of a report about the transfer for a specified TSO user ID<br />

on the remote system.<br />

� Automatically submitting a job on the remote system after the file transfer.<br />

� Remote checking of a request before the file transfer is started.<br />

� Pre-transfer and post-transfer user exits and user-written file handlers.<br />

For more information, refer to the OSI/File Services System/370 User’s Guide. This<br />

guide also describes how to create the LRD and its entries.<br />

Deleting Entries from the OSI/File Services Results File<br />

OSI/File Services records the results of file transfers in the Activity Control File.<br />

To delete entries from the Activity Control File, results must be retrieved using the<br />

OSI/File Services function GET-RESULT. If the originator of the request and the<br />

filestore owner are the same, the result is deleted from the file. If the originator of<br />

the request and the filestore owner are not the same, the result is only deleted after<br />

both the request originator and filestore owner have issued a GET-RESULT.<br />

The filestore owner may not know about requests initiated by other users and may<br />

be prohibited from looking into the results file because he has no access to<br />

OSI/File Services. In this case, the OSI/File Services administrator must delete<br />

these entries on a regular basis. If the result file becomes full, all subsequent filetransfer<br />

requests are rejected by OSI/File Services.<br />

When a file transfer is initiated from the remote system and a file is created locally,<br />

the OSI server cannot inform the owner of the filestore in which a new file has been<br />

created that a result record was written into the Activity Control File. The filestore<br />

owner or the administrator must check the Activity Control File regularly and delete<br />

such entries.<br />

For more information about administering OSI/File Services, refer to the OSI/File<br />

Services System/370 User’s Guide.<br />

<strong>Chapter</strong> 9. Administering OSI File Transfers 93

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

Saved successfully!

Ooh no, something went wrong!