I'm finding an unexpected allocation situation that maybe someone can explain.
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 Job runs fine and creates the new file. Now I run it again; I expect it to fail with 'DUPLICATE DATA SET NAME' - but it doesn't. Instead, it goes ahead and allocates the file on a storage volume and gives me a zero completion code; just doesn't catalog the data set. I find this a change (but maybe it's been that way for some time). And potentially disasterous: suppose a multi-step job creates a file in the first step, and it gets created but not cataloged; but the completion code is zero. Second step references the new dataset, but it gets the old version because that's what's in the catalog. Any hints or insights here? -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-355-2752 http://www.trainersfriend.com * To get a good Return on your Investment, first make an investment! + Training your people is an excellent investment * Try our tool for calculating your Return On Investment for training dollars at http://www.trainersfriend.com/ROI/roi.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
