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

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

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

File Transfer Examples to a Remote IBM z/OS HostExample 1:To receive the file ABC.FOR from the remote host as described above into an existing partitioned data setnamed ‘EFT.SRC.FOR’, the following command is issued:eFT> receive -create replace abc.for 'EFT.src.for'eFT: SOURCE DESTINATION SIZEeFT: ---------------------------------------------eFT: ABC.FOR EFT.SRC.FOR(ABC) 32100Notice that the TSOPREFIX was not added to the destination data set name since it was enclosed in singlequotes. Also, since ‘EFT.SRC.FOR’ was a partitioned data set and no member name was given, <strong>NetEx</strong>/eFTused the file name portion of ABC.FOR (which is ABC) as the member name to create in the data set. The –CREATE REPLACE option tells <strong>NetEx</strong>/eFT to replace an existing member, should one exist.Example 2:To send a local file called MYFILE.TMP from a non-z/OS system to a IBM z/OS host, forcing CRC on thetransfer, the following command is issued:eFT> send myfile.tmp -crceFT: SOURCE DESTINATION SIZEeFT: -----------------------------------------------eFT: MYFILE.TMP SMITHX.MYFILE.TMP 232100Since no destination file or data set name was specified, the data set was given the same name as the sourcefile name and created with the current value of TSOPREFIX (e.g., SMITHX) prefixed to it.Converting from File Names to Data Set NamesTo convert from standard file name syntax FILE.EXT (FILENAME followed by EXTENSION, as used byVAX/VMS, UNIX, PC-DOS, IBM VM, etc.) to z/OS data set names, and back again, <strong>NetEx</strong>/eFT makes someassumptions about data set naming conventions. In order to satisfy a wide range of z/OS users, <strong>NetEx</strong>/eFTtries to conform to the ISPF library convention which names individual qualifiers asPROJECT.GROUP.TYPE followed by an optional member name for partitioned data sets. The conversionthen is straight forward. That is, file EXTENSION maps to data set TYPE, and file NAME maps to theGROUP name for sequential data sets, or MEMBER name for partitioned data sets. Pictorially, the mappingis:Conversion to/from a Sequential Data Set Name:and,REF-eFT213-R<strong>5.4</strong>-08 File Handling Under IBM z/OS <strong>NetEx</strong>/eFT Page 53

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

Saved successfully!

Ooh no, something went wrong!