On Thu, 6 Jul 2006 15:48:50 -0600, Paul Gilmartin <[EMAIL PROTECTED]> wrote:
>I deliberately [over]simplified my example. When I wish either to >create a new data set, or re-use the existing one, I often use the >following to avoid adding a job step: > > //STEP EXEC PGM=IEBGENER > //ALLOC DD DISP=(MOD,CATLG),UNIT=&DASD,DSN=...,SPACE=... > //SYSUT2 DD DISP=OLD,DSN=*.ALLOC,VOL=REF=*.ALLOC,UNIT=&DASD > >Specifying VOL (with a referback) and UNIT permits accessing DSN >before it is catalogued. Would similar work for deleting and >creating in a single job step: > > //STEP EXEC PGM=IEBGENER > //ALLOC DD DISP=(MOD,DELETE),UNIT=&DASD,DSN=...,SPACE=... > //SYSUT2 DD DISP=OLD,DSN=*.ALLOC,UNIT=&DASD > >...? I believe the ALLOC data set is uncatalogued before SYSUT2 is >catalogued (order of DD statements?). Of course this requires an >elegible storage volume in addition to the one used by the ALLOC DD. > >If responses are vague or contradictory I'll try a test. > I don't think so. In an SMS environment I believe the data set is cataloged when it is created. Even if not, you run the risk of trying to allocate it on the same volume. Tom Marchant ---------------------------------------------------------------------- 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
