The ZDVT.MGDC001.IDCUT1 data set is being allocated with a DISP=OLD, but it does not look like it exists.
By the way, I have not used internal IDCAMS sort in years. You will get better performance removing the IDCAUT1 and IDCUT2 DD statements and using your installed SORT product instead of IDCAMS sort. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tommy Tsui Sent: Thursday, August 31, 2006 5:32 AM To: [email protected] Subject: Define and build alternative index path error under SMS-managed volume Hi, Anyone try before , define an alternative index path under SMS managed volume, a JCL error "data set not found" will issue, why? DDVT12 is under SMS managed volume... /* DEFINE & BUILD ALTERNATIVE INDEX PATH */ //BUILDIDX EXEC PGM=IDCAMS,COND=(8,LE),REGION=6M //SYSPRINT DD SYSOUT=* //IDCUT1 DD DSN=ZDVT.MGDC001.IDCUT1,DISP=OLD, // UNIT=SYSDA,VOL=SER=DDVT12,AMP='AMORG' //IDCUT2 DD DSN=ZDVT.MGDC001.IDCUT2,DISP=OLD, // UNIT=SYSDA,VOL=SER=DDVT12,AMP='AMORG' //SYSIN DD DSN=&LBMGD..BAT.PARMLIB(DEFFILEB),DISP=SHR // DD DSN=&LBMGD..BAT.PARMLIB(DEFTDGPA),DISP=SHR IEF212I ZSMD117B BUILDIDX IDCUT1 - DATA SET NOT FOUND Many thanks Tommy ---------------------------------------------------------------------- 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
