The structure of a traditional GDG catalog entry doesn't have any place for the necessary VSAM information. On the other hand, the new extended GDG does. In fact, it should be able to support GDGs of anything, including sub-GDGs... how's that for a questionable idea?
Nevertheless, to the extent those work, it's off the reservation, and IBM certainly would have more work to do to support them. Btw, a GDG is a generic container... individual GDSes are not required to all be the same type. Model DSCBs are archaic, and I don't think they've been required for a long time. sas On Wed, Jun 21, 2017 at 11:11 PM, Wayne Bickerdike <[email protected]> wrote: > Just take off the LIKE parameter. The GDG should have a model DSCB. Why > make things so hard? > > > > On Thu, Jun 22, 2017 at 12:03 PM, Steve Beaver <[email protected]> > wrote: > > > Was it done in the same job? > > > > Steve > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of Frank Swarbrick > > Sent: Wednesday, June 21, 2017 4:11 PM > > To: [email protected] > > Subject: Re: VSAM file as GDS > > > > Developer did more testing and found that even though it successfully > > created generation 1 when an attempt was made to create an additional > > generation it failed. :-( > > > > IEF344I TESTREP STEP01 FILEOUT - ALLOCATION FAILED DUE TO DATA FACILITY > > SYSTEM ERROR > > > > IGD17101I DATA SET PROD.CONNDEF.PATM.BKP.G0001V00 > > > > NOT DEFINED BECAUSE DUPLICATE NAME EXISTS IN CATALOG > > > > RETURN CODE IS 8 REASON CODE IS 38 IGG0CLEH > > > > IGD17219I UNABLE TO CONTINUE DEFINE OF DATA SET > > > > ________________________________ > > From: IBM Mainframe Discussion List <[email protected]> on behalf > > of > > Frank Swarbrick <[email protected]> > > Sent: Wednesday, June 21, 2017 2:24 PM > > To: [email protected] > > Subject: VSAM file as GDS > > > > Learn something new every day. Another developer created a GDG > > (PROD.CONNDEF.PATM.BKP) and then a job step that has the following: > > //STEP02 EXEC PGM=IDCAMS,COND=(4,LT) > > //FILEIN DD DSN=PROD.ONLINE.CONNDEF.PATM, > > // DISP=SHR > > //FILEOUT DD DSN=PROD.CONNDEF.PATM.BKP(+1), > > // LIKE=PROD.ONLINE.CONNDEF.PATM, > > // DISP=(NEW,CATLG,DELETE) > > //SYSIN DD DSN=PROD.PARM(REPRO), > > // DISP=SHR > > //SYSPRINT DD SYSOUT=* > > I though for sure this would not work, as PROD.ONLINE.CONNDEF.PATM is a > > VSAM > > KSDS. But it appears it in fact did work: > > PROD.CONNDEF.PATM.BKP > > PROD.CONNDEF.PATM.BKP.G0001V00 > > PROD.CONNDEF.PATM.BKP.G0001V00.DATA > > PROD.CONNDEF.PATM.BKP.G0001V00.INDEX > > > > > > I'm not sure how comfortable I am with it, though. Any harm in doing > this? > > > > Frank > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > email > > to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > email > > to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > > -- > Wayne V. Bickerdike > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
