We have a bunch of extract jobs that each run their own procs. I created a new JCL that called several procs in succession.
Each proc starts off sorting a finder file, creating a temporary file: //QA04#01 EXEC PGM=SORT CLEAN UP FILES //PERSONS DD DSN=&SYSTEM..QA04.C&IDENT..D&TODAY, // DISP=(MOD,DELETE),SPACE=(TRK,0) //DISPLAY DD DSN=&SYSTEM..QA04.CPRINT.D&TODAY, // DISP=(MOD,DELETE),SPACE=(TRK,0) //SORTIN DD DSN=&FINDER,DISP=SHR //SORTOUT DD DSN=&&FINDERS, // UNIT=&UNIT1, // LRECL=80, // AVGREC=U,SPACE=(080,(1234844,10000)), 1234844 // DISP=(NEW,PASS) The first two procs ran fine - the 3rd proc aborted with a duplicate name on direct access volume. Checking, I see that this is the 2nd proc that is running with: // UNIT1='3390,VOL=SER=DBS504', So, &&FINDERS is SYS09148.T083746.RA000.ZHBBIOD.FINDERS.H01 in each proc for this run, which is OK as long as they are on different packs. I could hard code a different pack for each &&FINDERS, or I could actually make the job more efficient by getting rid of the procs altogether (they all use the same finder file, sorted the same way). Any other options that I should consider? ---------------------------------------------------------------------- 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
