On Sat, Sep 3, 2016 at 2:05 PM, Tom Conley <[email protected]> wrote:
> Brain dead implementation. If you don't have a pre-allocated target with > the correct DCB attributes, garbage. Supposably z/OS V2R1 added MVSGET and > MVSPUT commands, but they didn't think it important enough to rollback. > BTW, this blurb in the manual is a lie: You must log in to a z/OS V2R1 or > later FTP server to use the MVSGet and MVSPut subcommands. Enhhhh, thank > you for playing. Both the client and server have to be at V2R1. > Actually, if you do a z/OS to z/OS FTP, this is not true. The normal setup for such an FTP is to have the SENDSITE active. This causes the PUT / GET command to generate and send a SITE LRECL=... and so on automatically for you. And if you FTP to a UNIX file instead of a z/OS data set, this is not needed and the FTP "works correctly". The entire problem appears to me that you somehow want z/OS to just magically "know" what the DCB attributes should be when data is coming in from something like a Windows or Linux system. How? The other site is too "brain dead" to even understand the concept. I can envision an FTP exit which do something like autogenerating a SITE command. But what should it be? In my case, for BINary transfers, I use RECFM=U,LRECL=0,BLKSIZE=27998 . For ASCII, my "standard" for true text files is RECFM=VB,LRECL=32756,BLKSIZE=32760. That works fairly well, FOR ME. > > There, I feel better. > > Regards, > Tom Conley > -- Unix: Some say the learning curve is steep, but you only have to climb it once. -- Karl Lehenbauer Unicode: http://xkcd.com/1726/ Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
