> >Sure, there are multiple ways to avoid this issue, such as using different temp >names or using DISP=(OLD,DELETE) in steps 2 and 4. That's not the issue. >That's already taken care of. > >The issue is that the behavior is unexpected and contrary to the >documentation. Has anyone run into this before and found the behavior >documented somewhere? >
Not an answer... but we ran into a problem several weeks ago on an LPAR with the startup of one of our ISV software products. We were getting duplicate data set name on volume or VTOC (I don't recall the exact message). I couldn't understand how you get duplicate temp data names in the VTOC. I looked at the volumes I saw in the deallocation mesages, and of course found nothing. I finally looked at the PROC and saw this: //WORK DD DSN=&&WORK,UNIT=SYSDA, // DCB=BLKSIZE=6080,SPACE=(CYL,(5,5)), // DISP=(,PASS,DELETE) //WO0K DD DSN=&&WORK,UNIT=SYSDA, // DCB=BLKSIZE=6080,SPACE=(CYL,(5,5)), // DISP=(,PASS,DELETE) //WO1K DD DSN=&&WORK,UNIT=SYSDA, // DCB=BLKSIZE=6080,SPACE=(CYL,(5,5)), // DISP=(,PASS,DELETE) //WO2K DD DSN=&&WORK,UNIT=SYSDA, // DCB=BLKSIZE=6080,SPACE=(CYL,(5,5)), // DISP=(,PASS,DELETE) //WO3K DD DSN=&&WORK,UNIT=SYSDA, // DCB=BLKSIZE=6080,SPACE=(CYL,(5,5)), // DISP=(,PASS,DELETE) This "user error" had worked for years without a problem because the work files were allocated to different volumes. The change that made it fail was a DASD migration to fewer larger volumes and the SMS temp storage group on this particular (small) LPAR was only a few volumes. -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[email protected] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
