To send V/VB/VBS data from z/OS to a non-z/OS site and preserve the BDW and 
RDWs:



 A. Sending data to MXG support.

    i. ftp instructions for sending data to the MXG ftp site

       Using the IBM ftp program, you can ftp any MVS data file to the
       MXG ftp site with this syntax; do NOT change the DCB attributes
       of the //SMFFILE DD: even though it points to a VBS DSNAME, the
       RECFM=U,BLKSIZE=32760 must be used to include BDW and RDWs.

      //FTP      EXEC PGM=FTP,PARM='(EXIT=4'
      //SYSPRINT DD  SYSOUT=*
      //OUTPUT   DD  SYSOUT=*
      //SMFFILE  DD DSN=YOUR.SMF.DATA,DCB=RECFM=U,BLKSIZE=32760,DISP=SHR
      //INPUT DD *
      ftp.mxg.com
      mxgtech mxgtech
      quote PASV
      bin
      put //DD:SMFFILE  yourname.smf
      close
      quit
      /*

      IMPORTANT:  userid/password may be mixed case
                  do NOT change the DCB attributes of the //SMFFILE DD.

      IMPORTANT:  Some sites MUST use the "quote PASV" argument, so it
                  is the default, but for some sites it can NOT be use
                  and must be removed. Try both.

      IMPORTANT:  One site found that they had to use the syntax
                    [email protected]
                    mxgtech
                  for the first two lines.

      IMPORTANT:  The ftp control statements MUST BE UNNUMBERED.

      IMPORTANT:  If you do NOT see a message
                  220 Serv-U FTP Server v11.1 ready...
                  then you never connected and most likely have a
                  local installation firewall issue with your network.
      
         
                   Note: if your SMF data is on tape, you should use:
                         RCMD='SITE RDW READTAPEFORMAT=S'


      This ftp can be used for MVS files with RECFM=U,F,FB,V,VB, or VBS,
      but for F/FB files, please email us the LRECL value of each file.



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Bernd Oppolzer
Sent: Monday, September 08, 2014 6:50 PM
To: [email protected]
Subject: Re: FTP of EBCDIC file

So true!

I also had a hard time some time ago to explain this simple facts to some 
people who tried to send me a binary VB data set from a z/OS system by FTP 
across other (non-z/OS) systems. The information about record length etc. 
simply gets lost, because the VB file (if binary) will be transferred as a byte 
string without record structure (one large string of bytes), or otherwise, you 
will get record termination characters inserted, which is also plain wrong.

The problem is not EBCDIC; you can do a transmission without code translation 
by FTP by using "binary"; the problem is the record oriented file structure of 
the z system compared to the byte oriented paradigm of FTP (unix tool). This 
works fine, if you do FTP between two z systems, but if there are other systems 
in between, you're in a real mess.

"Fixed length" would be a solution, too; if FTP inserts record termination 
characters at some stage of the transmission, they all appear at fixed known 
offsets and can be easily removed at the target system. But: the sender will 
have to fill all records to the same maximum length ... don't know if the 
sending party is able to do this.

If variable length is really needed: generate fixed length records anyway, but 
put a logical length field in front of each record. This, too, has to be done 
by the sending party.

Kind regards

Bernd



Am 08.09.2014 16:25, schrieb John McKown:
> On Mon, Sep 8, 2014 at 8:46 AM, Werner Kuehnel 
> <[email protected]> wrote:
>> It's not my creation, it was delivered by a bank for a test. Thanks 
>> for your suggestions, but if there are no standard ftp commands I 
>> refuse to work with that file.
>> Anyway, I tested your way and it almost worked, Unfortunately there 
>> are packed fields in the records containing x'15' which are not a line end.
>>
>> Thanks,
>> Werner
>>
> If the bank is trying to send you EBCDIC information from a z/OS 
> system, but needs it to survive transfer across non-z/OS systems, then 
> the bank really needs to either use AMATERSE or TRANSMIT to put the 
> data into a more transportable format. Those both result in an FB 
> file, which can easily be binary ftp'ed from z/OS to Windows, then 
> back to z/OS and restored. Doing a normal BINary FTP of variable data 
> will just result in frustration and data corruption.
>


--
Bernd Oppolzer
—————————————————————
*Oppolzer-Informatik
* Dipl. Inf. Bernd Oppolzer
Bärenhofstraße 23
70771 Leinfelden-Echterdingen
—————————————————————
Tel.: +49 711 7949591 (neu!)
priv.: +49 711 7949590
eMail: [email protected] <mailto:[email protected]>
—————————————————————
Für Umsatzsteuerzwecke:
SteuerNr.: 97 076 / 29921
USt-ID-Nr.: DE 147 700 393
—————————————————————
7. April 1964: Ankündigung IBM S/360
2014: 50. Geburtstag der Plattform


----------------------------------------------------------------------
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

Reply via email to