On Thu, 31 May 2012 21:45:54 +0000, Gibney, Dave wrote: >There is a parmlib option to abend NOT CATLG 2. I recommend using it. > Would this cause the ABEND at the beginning or at the end of the job step? The latter would be suboptimal.
>IMO, SMS should be set up for all allocations and the fallback pathway to >storage volumes blocked. Back in the "old days", we did experience the >scenario you describe. After the same dataset name appeared on all available >volumes, then the abend would occur. > >I am also a strong believer in the philosophy "If it ain't cataloged, it >doesn't exist". I feel free to whack any such I find in the application >storage pools. They have always (so far) been the result of an error. > Sounds good. >> On Thu, 31 May 2012 15:25:04 -0600, Steve Comstock wrote: >> >> >I run a job that creates a new data set using >> >this DD statement: >> > >> >//NEWMAST DD DISP=(NEW,CATLG),DSN=&SYSUID..WORK.NEW.ZINPUTA, >> >// LIKE=STNT329.TRAIN.ZINPUTA >> > Something has to specify the UNIT. Does "LIKE" establish the UNIT but not the VOL? Strange. On occasion, when I want to create a data set if it doesn't exist or reuse it if it does, I code, e.g.: //ALLOC DD DISP=(MOD,CATLG),DSN=&SYSUID..WORK.NEW.ZINPUTA, // LIKE=STNT329.TRAIN.ZINPUTA //* //NEWMAST DD DISP=SHR,DSN=*.ALLOC,VOL=REF=*.ALLOC Would this fail if SMS-managed or "ABEND on NOT CATLGD 2" were in effect? I could use the well-known trick of "DISP=(MOD,DELETE)" in a previous IEFBR14 step, but that would lose existing members if the data set is a PDS. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
