If you then need to upload that "RECFM=U" file back to z/os, you would upload into a z/OS file with BLKSIZE=32760 and that file's BDW and RDWs can be read and deblocked to create valid V/VB/VBS files on z/OS from the RECFM=U format6 MXG provides both a SAS (UDEBLOCK) and an ASM program (ASMDBLKU) to do that deblocking.
Barry -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Tuesday, September 09, 2014 9:39 AM To: [email protected] Subject: Re: FTP of EBCDIC file On Tue, 9 Sep 2014 09:16:44 -0500, John McKown wrote: >On Tue, Sep 9, 2014 at 9:01 AM, Barry Merrill wrote: >> To send V/VB/VBS data from z/OS to a non-z/OS site and preserve the BDW and >> RDWs: >> >> //FTP EXEC PGM=FTP,PARM='(EXIT=4' >> //SMFFILE DD DSN=YOUR.SMF.DATA,DCB=RECFM=U,BLKSIZE=32760,DISP=SHR >> //INPUT DD * >> bin >> put //DD:SMFFILE yourname.smf > >That is interesting. What about if you then needed to upload that file >back to z/OS? I was thinking you could use RECFM=U, but then realized >that the RECFM=U still has block boundries which would make reading the >file difficult. That is you could not upload as RECFM=U, then just use >JCL DCB=(RECFM=VBS) to read it. > Yup. I've decoded such with a Rexx program. Particularly ugly since prior to z/OS 2.1 Rexx couldn't handle RECFM=U (I haven't tried 2.1). I REPROed it from RECFM=U to RECFM=V and processed that. An alternative might be IEBGENER to a UNIX file, then parse with Rexx. BTW, this is the format used by GIMZIP for RELFILEs. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
