//DELFILES EXEC PGM=IEFBR14 //FILE1 DD DSN=FILE1,UNIT=SYSDA,SPACE=(0,0),DISP=(MOD,DELETE,DELETE)
Works every time. HTH Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Clifford Sent: Tuesday, October 14, 2014 3:15 PM To: [email protected] Subject: Re: Force DISP=(NEW,CATLG)? Paul, We use a pile of IEFBR14's in out nightly batch procs and first use DISP=(mod,catlg) then a second step with (old,delete). The first step will allocate a 1 trk dataset and the second will just delete & uncatalog it if it does NOT exist. If it DOES exist the MOD just finds it and then it gets deleted normally in the second step. Then normal batch allocations should work correctly . I hope this makes sense. John Clifford GTSG (IBM consultant) On Tue, Oct 14, 2014 at 3:07 PM, Paul Gilmartin < [email protected]> wrote: > Non-SMS. > > I ran last week's JCL, but neglected to change a DSN qualifier. > It allocates several data sets with DISP=(,CATLG). The DSNs > were already catalogued, so they were created with KEEP,noCATLG. > All over our storage packs. I'd much rather have got a JCL error. > Is there any way to force this? > > Not very satisfactory/convenient answers: > > o Convert to SMS. > > o Specify VOL=SER. > > Others? > > Thanks, > gil > > ---------------------------------------------------------------------- > 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 This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
