Gil, I meant remove the DDDEF. I don't use UNIX for SMPPTS storage. This is straight from the SMP/E reference manual:
<quote> Do not concatenate SMPPTS spill data sets. The first SMPPTS spill data set must be specified with a ddname of SMPPTS1, the second SMPPTS2, and so on, up to a maximum of SMPPTS99. Do not skip any ddnames in this sequence; if a spill data set is omitted, SMP/E ignores any data sets that may follow the omitted data set. (For example, if you specify only SMPPTS1 and SMPPTS3, then SMP/E uses only SMPPTS1 and ignores SMPPTS3.) </quote> Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Friday, March 17, 2017 10:46 AM To: [email protected] Subject: Re: Can SMPPTS datasets be consolidated? On 2017-03-17, at 08:06, Pommier, Rex wrote: > > -----Original Message----- > From: Kurt Quackenbush > Sent: Friday, March 17, 2017 8:51 AM > > Yes, ever since we added the SMPPTS spill data set function (year 2000) SMP/E > has allowed you to merge data sets, move PTFs from data set to data set, add > data sets, whatever you want to do, as long as the SMPPTSnn DDDEF entries in > your global, target, and dlib zones point to your current set of SMPPTS data > sets. > Alternatively, might the programmer specify (override) SMPPTS in a JCL DD statement as a concatenation of UNIX directories rather than in a DDDEF? (from Rex, who didn't properly quote Kurt's remarks:) > And one other - albeit minor - caveat to the SMPPTS spill datasets is that > you can't skip one. IF you're consolidating them down and you have, for > example SMPPTS1,2,3 and 2 empties out, if you just remove SMPPTS2, SMP/E > won't use SMPPTS3 either. > Do you mean remove the DDDEF or delete the corresponding UNIX directory? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
