On Thu, Nov 19, 2015 at 9:59 AM, J O Skip Robinson <[email protected] > wrote:
> I haven't experimented with this, but going with NOSCRATCH is likely to > cause big problems with DASD GDGs. A data set residing on an SMS-managed > volume must be cataloged. It cannot just sit there uncataloged. > Irresistible force meets unmovable object. > I just tested the following on z/OS 1.12. With SMS managed disk data sets, if the GDS "rolls off" the GDG base and NOSCRATCH is in effect, then the GDS simply becomes a non-GDS entry which "just happens" to look like a member of a GDG. I.e. it is not concatenated in with DSN=GDG.BASE nor can it be referenced via DSN=GDG.BASE(-n), but can be via GDG.BASE.GnnnnV00. > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] > > -- Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
