11.07.2015 Views

NetEx EFT213 Reference Manual Rel 5.4

NetEx EFT213 Reference Manual Rel 5.4

NetEx EFT213 Reference Manual Rel 5.4

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Table 2. Supported z/OS Transfer ModesModeBACKUPCHARACTERCOPYRECORDRESTOREDescriptionThis mode is designed to allow IBM z/OS files or data sets to be backed up on somehost regardless of word size, then restored at some later time. A special header is builtaround the resulting file in order to properly restore the file. The resulting file will generallynot be usable on the destination host, but can be restored to an z/OS system withits original data and size. BACKUP mode under IBM z/OS <strong>NetEx</strong>/eFT does not savedata set characteristics as part of the backup header. It simply ensures that all databacked up can be restored without loss of data or extra data due to word size incompatibilitiesbetween hosts.This mode of file transfer is generally designed for moving text files from one host toanother. This mode performs automatic code conversion across the network and assumesthe data being transferred contains only text data. An error will usually result ifan attempt to transfer binary data is made. The qualifier MAXRECORD determines themaximum allowable record that can be read from or written to a data set. Fixed lengthrecords are padded with spaces when written to a data set and stripped of trailing spacesbefore being sent across the network.This mode is designed for peer to peer file transfers. In COPY mode, IBM z/OS filescan be moved from one z/OS system to another. Most types of file (text or binary) canbe transferred very fast in COPY mode since file access is done as efficiently as possible,without individual records having to be manipulated. The data in COPY mode istransferred as an unstructured stream of bytes.This mode transfers are designed for moving IBM z/OS record oriented binary data. Nocode conversion is performed on RECORD mode transfers. This mode would typicallybe used anytime a data set containing nontext data was to be transferred across the network.It is recommended that data sets transferred in RECORD mode have variablelength records as opposed to fixed length. Fixed length records are padded with nullswhen written, but not stripped when read back.This mode is used to restore a file previously transferred in BACKUP mode.RESTORE mode expects to find a backup header built around the file it is attempting torestore. Since BACKUP mode under IBM z/OS <strong>NetEx</strong>/eFT does not save data set characteristics,a backed up data set gets restored using the SEND/RECEIVE qualifier valuesat the time of the transfer. For instance, if a fixed blocked data set is saved usingBACKUP mode, the same data set should be restored by setting the RECFORMATqualifier to FB. Refer to the discussion on BACKUP mode above.REF-eFT213-R<strong>5.4</strong>-08 File Handling Under IBM z/OS <strong>NetEx</strong>/eFT Page 57

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

Saved successfully!

Ooh no, something went wrong!