On Sat, 20 May 2017 10:18:40 -0700, Lizette Koehler wrote: > >TSO XMIT (Transmit) takes a file and compresses it (if possible) > I was unaware of a compression facility, and I don't see it mentioned in the Ref., so I remain skeptical. But I noticed an ENCIPHER option of which I had previously been unaware.
But I believe OUTDDNAME can be ALLOCATEd to a POSIX pipe that could feed compress. >Note: Some shops restrict the number or amount of data that can be XMIT'd via >Spool. So using OUTDSN is preferred mechanism > I thought this restriction applied even with OUTDD/OUTDSN specified. And TRANSMITting a PDS involves an IEBCOPY unload which could exhaust space and I see no way the programmer can control that. I could imagine TRANSMIT OUTDDNAME() | compress | ssh user@node "cat >file". The Ref. mentions that VSAM, ISAM, keyed, and user labels are not supported. I don't understand "user labels". Is this this the exception that proves the rule, implying that other sorts of labels are supported? The output of TRANSMIT is not suitable for use as SYSIN because "/*" may occur in columns 1-2 of OUTDSN. >Here is a nice write up of TRSMAIN > >http://jensd.be/271/linux/terse-unterse-and-transfer-datasets-between-zos-and-other-platforms-via-ftp > > >Here is some helpful tips on VSAM > >http://www.mainframetips.com/transfer-zos-vsam-file-via-internet/ > Good sumary of TRANSMIT and TRSMAIN. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
