EPIO files for use on or created on mainframes
should have fixed length blocks.
On VAX/VMS you can use the default settings.
On CERNVM the user should issue a filedef specifying RECFM F
or RECFM U
and the correct blocksize, which most applications are doing already.
If not, a correct filedef is
FILEDEF IOFILE11 DISK MYEPIO TESTDATA A1 ( RECFM F BLOCK 3600The files can then be transferred using FTP. The most convenient way is to use the ZFTP utility and a good description of a session is given in Computer Newsletter 200. This avoids the need to convert the data file or to modify the EPIO application. The actual transfer is performed by the command
putb, e.g.-
putb myepio.testdata test1 3600
If ZFTP is not available on your system then you must use ftp directly specifying the qualifier ``binary''.
For files created on a workstation for transfer to a mainframe it is essential to create them as a byte stream. Although it is clearly inefficient, conversion utilities between the two formats will be provided.
A typical CERNVM ftp session would be
tcpipibm ftp hostnm > hostname > password > cd wdir > binary fixed 3600 for a blocksize of 3600 bytes > put file.iofile epio11 or > get epio11 file.iofile > quit
On VAX, the session is similar except that the EPIO file names
are of the form FOR0nn.DAT.