David, I don't remember if there's a system option that would allow you to change the jobname in the generated temp DSname to use the JOBID instead, but ... These jobs are submitted in bulk, several at the same second, right? And they all use the exact same skeleton JCL, including the same DSN=&&SB250DD1 DD statement? Is there something that you can easily do to vary that DSN=&&... name to use something different from one job to the next? That generates a temp DSname that, even though it may have the same timestamp and jobname parts, will differ in the next level of the DSname, thus avoiding the ENQ conflict
Regards, Ulrich Krueger -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of David Andrews Sent: Friday, April 04, 2008 08:42 To: IBM-MAIN@BAMA.UA.EDU Subject: Duplicate temporary dataset names I have several jobs submitted simultaneously, with the same job name, in a jobclass with DUPL_JOB=NODELAY. They allocate temporary datasets, and sometimes we see: IGD17204I UNABLE TO ENQUEUE ON DATA SET SYS08095.T105633.RA000.ODSB267S.SB250DD1.H01 ENQUEUE RETURN CODE IS 0 ENQUEUE REASON CODE IS 528 How can I influence the system's selection of a temporary dataset name (by e.g. replacing the jobname with the JES2 jobid)? -- David Andrews A. Duda and Sons, Inc. [EMAIL PROTECTED] ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
