Just for confirmation, it's always worked that way. Something else to note: if you want to transmit an individual member to VM/CMS, you also must code SEQ so it doesn't generate an IEBCOPY module. CMS's RECEIVE will say some very not-nice things if you don't code SEQ.
Later, Ray -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tony Harminc Sent: Tuesday February 20 2007 13:00 To: [email protected] Subject: Re: TSO TRANSMIT of PDS member Paul Gilmartin wrote: > transmit host.user ddname(INDD) outddname(OUTDD) > //INDD DD DISP=SHR,DSN=SYS1.MACLIB(SPLEVEL) > The logs and SYSOUT show that TRANSMIT seems to have unloaded > and transmitted all of SYS1.MACLIB, not just SPLEVEL. Has it > always worked (FSVO "work") that way? I thought that not > very long ago it would transmit only the member in the INDD > statement. > > z/OS 1.7. Does the same on z/OS 1.4. Since it appears to just pass the DDNAME directly to IEBCOPY, I would guess it's always worked this way. You can use the MEMBERS(...) keyword on XMIT. I just tried, and this does correctly insert an IEBCOPY SELECT statement when used with DDNAME(...). ---------------------------------------------------------------------- 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
