I agree with John. TERSE is the simplest. You just terse the file on the source z/OS system, then use binary for all transfers. Then there is no problem of EBCDIC/ASCII, or RDW. The binary file arrives unchanged. Then use TERSE to unpack it and it automatically restores the correct DCB attributes. The only thing I have ever had to remember to do was specify directory blocks when untersing a PDS and no directory blocks for a sequential file.
If the file gets to an intermediate server where you can use FTP from your target z/OS system to get it directly, then you can do this: BINARY < don't forget this. ASCII mode by default does not work for traces> LOCSITE recfm=fb lrecl=1024 cylinders primary=100 secondary=10 blksize=0 <this is the key to doing this from my MVS> mget Pxxxxx.* ( replace <case sensitive on the file names> quit < to get out of FTP> Roger Bolan AFP Infoprint Software on z/OS, z/VM, z/VSE Phone: 303-354-2134, tieline 419-2134, local x62134 Fax: 1-800-=865-9053/1-303-354-2036 e-mail: [EMAIL PROTECTED] infoprint.com 6300 Diagonal Highway Bldg 004, G8 Boulder CO, 80301 IBM Mainframe Discussion List <[email protected]> wrote on 01/09/2008 02:28:55 PM: > The simpliest thing, in my opinion, is to use TERSE on both ends and do > binary transfers. > > -- > John McKown > Senior Systems Programmer > HealthMarkets > Keeping the Promise of Affordable Coverage > Administrative Services Group > Information Technology ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
