Re: Duplicate temporary dataset names
In [EMAIL PROTECTED], on 04/07/2008 at 03:44 PM, Myers, Edouard (OCTO) [EMAIL PROTECTED] said: It should be in upper case Why? It would still be invalid. He needs to remove it entirely. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: Duplicate temporary dataset names
In [EMAIL PROTECTED], on 04/07/2008 at 02:27 PM, Mark Zelden [EMAIL PROTECTED] said: The problem is not with the poster, It's the poster that tried to actually run the bad JCL. He needs to know how to fix the JCL, which I told him. Fixing the web site is a more difficult problem. it is with LISTSERV's web interface. Broken web sites are endemic :-( Just to prove it I'm rarely sceptical about claims that a web site is broken; I might be sceptical about claims that it is not ;-) FWIW, there are sites that are much more badly broken. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: Broken LISTSERV (was: Duplicate temporary dataset names)
In [EMAIL PROTECTED], on 04/07/2008 at 10:41 AM, Paul Gilmartin [EMAIL PROTECTED] said: Yours is fine. Apparently you posted via E-mail (I'm guessing because your Date: header indicates MDT, not CDT). I posted via the WWW interface, so that narrows the suspect list. The web interface is not LISTSERV, any more than bit.listserv.ibm-main is IBM-MAIN. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: Broken LISTSERV (was: Duplicate temporary dataset names)
In [EMAIL PROTECTED], on 04/07/2008 at 06:41 AM, Steve Comstock [EMAIL PROTECTED] said: [Now I'll wait to see how this comes through on the actual message, just to verify.] It came through just fine. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: Duplicate temporary dataset names
//SYSEXEC DD DISP=(OLD,PASS),DSN=amp;SYSEXEC Trying the amp;, I get: IEFC620I UNIDENTIFIABLE CHARACTER a ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER m ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER p ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER ; ON THE DD STATEMENT What's the secret here? -- Peter Hunkeler Credit Suisse -- 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
Re: Duplicate temporary dataset names
Hunkeler Peter (KIUK 3) wrote: //SYSEXEC DD DISP=(OLD,PASS),DSN=amp;SYSEXEC Trying the amp;, I get: IEFC620I UNIDENTIFIABLE CHARACTER a ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER m ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER p ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER ; ON THE DD STATEMENT What's the secret here? Lower case characters. Strictly forbidden in JCL. Try AMP -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2008 r. kapita zakadowy BRE Banku SA wynosi 118.642.672 zote i zosta w caoci wpacony. -- 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
Broken LISTSERV (was: Duplicate temporary dataset names)
On Mon, 7 Apr 2008 09:05:36 +0200, Hunkeler Peter (KIUK 3) wrote: //SYSEXEC DD DISP=(OLD,PASS),DSN=amp;amp;SYSEXEC Trying the amp;, I get: IEFC620I UNIDENTIFIABLE CHARACTER a ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER m ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER p ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER ; ON THE DD STATEMENT What's the secret here? SIGH Broken LISTSERV. /SIGH I had coded two-ampersands-followed -by-SYSEXEC (amp;SYSEXEC), which escaping to HTML entities should convert to amp;amp;SYSEXEC (who knows how this will appear on the LISTSERV?) Instead, the raw HTML shows: amp;amp;amp;SYSEXEC. Apparently two consecutive ampersands overstress its tiny mind. Can this be reported to L-Soft? -- gil -- 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
Re: Broken LISTSERV (was: Duplicate temporary dataset names)
Paul Gilmartin wrote: On Mon, 7 Apr 2008 09:05:36 +0200, Hunkeler Peter (KIUK 3) wrote: //SYSEXEC DD DISP=(OLD,PASS),DSN=amp;amp;SYSEXEC Trying the amp;, I get: IEFC620I UNIDENTIFIABLE CHARACTER a ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER m ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER p ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER ; ON THE DD STATEMENT What's the secret here? SIGH Broken LISTSERV. /SIGH I had coded two-ampersands-followed -by-SYSEXEC (amp;SYSEXEC), which escaping to HTML entities should convert to amp;amp;SYSEXEC (who knows how this will appear on the LISTSERV?) Instead, the raw HTML shows: amp;amp;amp;SYSEXEC. Apparently two consecutive ampersands overstress its tiny mind. Can this be reported to L-Soft? -- gil The LISTSERV doesn't process HTML; it uses plain text. I'm curious why you didn't just code SYSEXEC in the first place. [Now I'll wait to see how this comes through on the actual message, just to verify.] Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-393-8716 http://www.trainersfriend.com z/OS Application development made easier * Our classes include + How things work + Programming examples with realistic applications + Starter / skeleton code + Complete working programs + Useful utilities and subroutines + Tips and techniques == call or email to receive a free sample student handout == -- 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
Re: Duplicate temporary dataset names
-Original Message- From: IBM Mainframe Discussion List On Behalf Of R.S. Hunkeler Peter (KIUK 3) wrote: //SYSEXEC DD DISP=(OLD,PASS),DSN=amp;SYSEXEC Trying the amp;, I get: IEFC620I UNIDENTIFIABLE CHARACTER a ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER m ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER p ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER ; ON THE DD STATEMENT What's the secret here? Lower case characters. Strictly forbidden in JCL. Try AMP Better yet, remove the 'amp;' and just concatenate the SYSEXEC onto the two amphersands. -jc- -- 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
Re: Broken LISTSERV (was: Duplicate temporary dataset names)
On Mon, 7 Apr 2008 06:41:46 -0600, Steve Comstock wrote: The LISTSERV doesn't process HTML; it uses plain text. I get a pop-up selection that says: Plain Text HTML ... But I left it at the default, Plain text I'm curious why you didn't just code amp;SYSEXEC in the first place. I did exactly that. LISTSERV corrupted it. [Now I'll wait to see how this comes through on the actual message, just to verify.] Yours is fine. Apparently you posted via E-mail (I'm guessing because your Date: header indicates MDT, not CDT). I posted via the WWW interface, so that narrows the suspect list. I'll wait to see how your text that I quoted comes through. -- gil -- 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
Re: Broken LISTSERV (was: Duplicate temporary dataset names)
On Mon, 7 Apr 2008 06:41:46 -0600, Steve Comstock wrote: The LISTSERV doesn't process HTML; it uses plain text. I'm curious why you didn't just code amp;SYSEXEC in the first place. [Now I'll wait to see how this comes through on the actual message, just to verify.] Trying with a different browser. Sorry for the test. -- gil -- 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
Re: Broken LISTSERV (was: Duplicate temporary dataset names)
Paul Gilmartin wrote: On Mon, 7 Apr 2008 06:41:46 -0600, Steve Comstock wrote: The LISTSERV doesn't process HTML; it uses plain text. I get a pop-up selection that says: Plain Text HTML ... But I left it at the default, Plain text I'm curious why you didn't just code amp;SYSEXEC in the first place. I did exactly that. LISTSERV corrupted it. Whoa! I see. It came through corrupted here. [Now I'll wait to see how this comes through on the actual message, just to verify.] Yours is fine. Apparently you posted via E-mail (I'm guessing because your Date: header indicates MDT, not CDT). I posted via the WWW interface, so that narrows the suspect list. I'll wait to see how your text that I quoted comes through. Yes, I use the email connection. OK. Interesting. Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-393-8716 http://www.trainersfriend.com z/OS Application development made easier * Our classes include + How things work + Programming examples with realistic applications + Starter / skeleton code + Complete working programs + Useful utilities and subroutines + Tips and techniques == call or email to receive a free sample student handout == -- 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
Re: Duplicate temporary dataset names
In [EMAIL PROTECTED], on 04/07/2008 at 09:10 AM, R.S. [EMAIL PROTECTED] said: Lower case characters. Strictly forbidden in JCL. Try AMP That's just as illegal. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: Duplicate temporary dataset names
In [EMAIL PROTECTED], on 04/07/2008 at 09:05 AM, Hunkeler Peter (KIUK 3) [EMAIL PROTECTED] said: //SYSEXEC DD DISP=(OLD,PASS),DSN=amp;SYSEXEC Trying the amp;, I get: IEFC620I UNIDENTIFIABLE CHARACTER a ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER m ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER p ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER ; ON THE DD STATEMENT What's the secret here? Use HTML syntax for HTML and JCL syntax for JCL. That 'amp;' is HTML syntax and has no place in JCL. Use //SYSEXEC DD DISP=(OLD,PASS),DSN=SYSEXEC or //SYSEXEC DD DISP=(OLD,PASS),DSN=SYSEXEC -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: Duplicate temporary dataset names
In [EMAIL PROTECTED], on 04/05/2008 at 09:10 AM, Paul Gilmartin [EMAIL PROTECTED] said: Yeah. Right. And how may the programmer refer in one step to a PDS, and in another to one of its members? I regularly do: //GENER EXEC PGM=IEBGENER //SYSUT2 DD DISP=(,PASS),DSN=amp;SYSEXEC(PROGRAM),... I doubt it. JCL doesn't use HTML syntax. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: Duplicate temporary dataset names
On Mon, 7 Apr 2008 14:02:19 -0300, Shmuel Metz (Seymour J.) [EMAIL PROTECTED] wrote: //SYSEXEC DD DISP=(OLD,PASS),DSN=amp;amp;SYSEXEC Trying the amp;, I get: IEFC620I UNIDENTIFIABLE CHARACTER a ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER m ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER p ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER ; ON THE DD STATEMENT What's the secret here? Use HTML syntax for HTML and JCL syntax for JCL. That 'amp;' is HTML syntax and has no place in JCL. Use The problem is not with the poster, it is with LISTSERV's web interface. I've seen the problem happen a few times with me also since I post from there. I think there was mention in another thread recently about the same or similar problem with IBMLINK 2000 (that will be fixed IIRC in the next IBMLINK update). Just to prove it... the line below has DSN=%%TEMP but change the percents to ampersands. DSN=amp;TEMP Mark -- 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
Re: Duplicate temporary dataset names
It should be in upper case Edouard A. Myers Acting Manager of Technical Services Office of the Chief Technology Officer DC Government 222 Massachusetts Ave, NW, Suite 200 Washington, DC 20001 Phone : 202-727-4017 Fax: 202-727-3880 Email: [EMAIL PROTECTED] Website: http://www.octo.dc.gov -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark Zelden Sent: Monday, April 07, 2008 3:27 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Duplicate temporary dataset names On Mon, 7 Apr 2008 14:02:19 -0300, Shmuel Metz (Seymour J.) [EMAIL PROTECTED] wrote: //SYSEXEC DD DISP=(OLD,PASS),DSN=amp;amp;SYSEXEC Trying the amp;, I get: IEFC620I UNIDENTIFIABLE CHARACTER a ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER m ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER p ON THE DD STATEMENT IEFC620I UNIDENTIFIABLE CHARACTER ; ON THE DD STATEMENT What's the secret here? Use HTML syntax for HTML and JCL syntax for JCL. That 'amp;' is HTML syntax and has no place in JCL. Use The problem is not with the poster, it is with LISTSERV's web interface. I've seen the problem happen a few times with me also since I post from there. I think there was mention in another thread recently about the same or similar problem with IBMLINK 2000 (that will be fixed IIRC in the next IBMLINK update). Just to prove it... the line below has DSN=%%TEMP but change the percents to ampersands. DSN=amp;TEMP Mark -- 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 -- 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
Re: Duplicate temporary dataset names
On Fri, 4 Apr 2008 09:31:03 -0700, Ulrich Krueger wrote: If you check the JCL Reference manual, chapter 12.22.2.6 Data Set Name for Temporary Data Set, you will find the sentence To ensure that a temporary data set name is unique, do not code a temporary data set name. Allow the system to assign one. To make the system generate a truly unique temp DSname, remove the ... name and change any references to it in later steps to use a STEPNAME.DDNAME referback. This should solve your problem. Yeah. Right. And how may the programmer refer in one step to a PDS, and in another to one of its members? I regularly do: //GENER EXEC PGM=IEBGENER //SYSUT2 DD DISP=(,PASS),DSN=amp;SYSEXEC(PROGRAM),... //SYSUT1 DD * ... //REXXEXEC PGM=IRXJCL,PARM=PROGRAM //SYSEXEC DD DISP=(OLD,PASS),DSN=amp;SYSEXEC Can I do the equivalent with a system-assigned data set name? -- gil -- 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
Re: Duplicate temporary dataset names
Gil, You might be able to solve your problem like this: (Note: JCL not tested, may need tweaking) //GENER EXEC PGM=IEBUPDTE,PARM=NEW //SYSPRINT DD DUMMY //SYSUT2 DD DISP=(,PASS),...alloc your temp PDS //SYSINDD * ./ADD NAME=PROGRAM your REXX Exec goes here /* //REXXEXEC PGM=IRXJCL,PARM=PROGRAM //SYSEXEC DD DISP=(OLD,PASS),DSN=*.GENER.SYSUT2 For more information on using referbacks in JCL, please dust off the JCL Reference Manual. Regards, Ulrich Krueger -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin Sent: Saturday, April 05, 2008 07:11 To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Duplicate temporary dataset names snipped Yeah. Right. And how may the programmer refer in one step to a PDS, and in another to one of its members? I regularly do: //GENER EXEC PGM=IEBGENER //SYSUT2 DD DISP=(,PASS),DSN=amp;SYSEXEC(PROGRAM),... //SYSUT1 DD * ... //REXXEXEC PGM=IRXJCL,PARM=PROGRAM //SYSEXEC DD DISP=(OLD,PASS),DSN=amp;SYSEXEC Can I do the equivalent with a system-assigned data set name? -- gil -- 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
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
Re: Duplicate temporary dataset names
Wow, the jobs must be submitted awfully close together and the dataset allocated close together also. Isn't the first to levels of the DSN SYSyyddd.Thhmmss where yyddd is the date the dataset was allocated and hhmmss the time? Isn't that naming convention supposed to prevent this situation. Tom Kelman Commerce Bank of Kansas City (816) 760-7632 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of David Andrews Sent: Friday, April 04, 2008 10:42 AM 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 * If you wish to communicate securely with Commerce Bank and its affiliates, you must log into your account under Online Services at http://www.commercebank.com or use the Commerce Bank Secure Email Message Center at https://securemail.commercebank.com NOTICE: This electronic mail message and any attached files are confidential. The information is exclusively for the use of the individual or entity intended as the recipient. If you are not the intended recipient, any use, copying, printing, reviewing, retention, disclosure, distribution or forwarding of the message or any attached file is not authorized and is strictly prohibited. If you have received this electronic mail message in error, please advise the sender by reply electronic mail immediately and permanently delete the original transmission, any attachments and any copies of this message from your computer system. * -- 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
Re: Duplicate temporary dataset names
On Fri, 2008-04-04 at 10:48 -0500, Kelman, Tom wrote: Wow, the jobs must be submitted awfully close together and the dataset allocated close together also. Isn't the first to levels of the DSN SYSyyddd.Thhmmss where yyddd is the date the dataset was allocated and hhmmss the time? Isn't that naming convention supposed to prevent this situation. Supposed to, but a second is a lot of time. -- 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
Re: Duplicate temporary dataset names
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
Re: Duplicate temporary dataset names
David, On second thought ... (I do that a lot ...:-) If you check the JCL Reference manual, chapter 12.22.2.6 Data Set Name for Temporary Data Set, you will find the sentence To ensure that a temporary data set name is unique, do not code a temporary data set name. Allow the system to assign one. Your JCL, across all these jobs, currently uses a DD statement like the one below to create a temp dataset: //ddname DD DSN=SB250DD1, DISP=(,PASS),...etc. And you refer to this dataset in the next step(s) using DSN=SB250DD1 referback, correct? To make the system generate a truly unique temp DSname, remove the ... name and change any references to it in later steps to use a STEPNAME.DDNAME referback. This should solve your problem. Regards, Ulrich Krueger -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ulrich Krueger Sent: Friday, April 04, 2008 09:04 To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Duplicate temporary dataset names 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
Re: Duplicate temporary dataset names
David Andrews wrote: 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)? I thought the RA000 and H01 are counters dedicated to the situation, so if RA000 already exist then RA001 is used. BTW: Maybe the above is true, but the message is issued before new name is used ? It would be reasonable. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237 NIP: 526-021-50-88 Według stanu na dzień 01.01.2008 r. kapitał zakładowy BRE Banku SA wynosi 118.642.672 złote i został w całości wpłacony. -- 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
Re: Duplicate temporary dataset names
On Fri, 4 Apr 2008 10:48:02 -0500, Kelman, Tom wrote: Wow, the jobs must be submitted awfully close together and the dataset allocated close together also. Isn't the first to levels of the DSN SYSyyddd.Thhmmss where yyddd is the date the dataset was allocated and hhmmss the time? Isn't that naming convention supposed to prevent this situation. I thought it was the job submission time, so all data sets in a single job would have the same Thhmmss. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of David Andrews 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 I encountered this problem years ago with started tasks. A colleague told me he had experienced it even earlier and reported it. WAD. Isn't NODELAY a recent innovation? IBM should have thought the consequences through and generated a collateral requirement to change the convention so data set names would remain unique. -- gil -- 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
Re: Duplicate temporary dataset names
On Fri, 4 Apr 2008 11:41:45 -0400, David Andrews wrote: How can I influence the system's selection of a temporary dataset name (by e.g. replacing the jobname with the JES2 jobid)? From the FM: To ensure that a temporary data set name is unique, do not code a temporary data set name. Allow the system to assign one. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B670/12.22.2.6?SHELF=EZ2ZO10JDT=20070427231644CASE= ... and code a backward reference (dsn=*.ddname) in later steps if necessary. Norbert Friemel -- 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
Re: Duplicate temporary dataset names
On Fri, 4 Apr 2008 11:26:15 -0500, Paul Gilmartin [EMAIL PROTECTED] wrote: I encountered this problem years ago with started tasks. A colleague told me he had experienced it even earlier and reported it. WAD. Isn't NODELAY a recent innovation? IBM should have thought the consequences through and generated a collateral requirement to change the convention so data set names would remain unique. Too bad every programmer can't imagine all the possible consequences of the code changes they make and how they might affect all other programs and downstream processes. -- 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
Re: Duplicate temporary dataset names
Norbert Friemel wrote: On Fri, 4 Apr 2008 11:41:45 -0400, David Andrews wrote: How can I influence the system's selection of a temporary dataset name (by e.g. replacing the jobname with the JES2 jobid)? From the FM: To ensure that a temporary data set name is unique, do not code a temporary data set name. Allow the system to assign one. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B670/12.22.2.6?SHELF=EZ2ZO10JDT=20070427231644CASE= ... and code a backward reference (dsn=*.ddname) in later steps if necessary. Maybe this is WAD, but this is silly design. Why don't they choose any random value instead of RA000 or H01 ? IDCAMS does it for decades. tempname is IMHO much more convenient than *.STEP.DDNAME. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2008 r. kapita zakadowy BRE Banku SA wynosi 118.642.672 zote i zosta w caoci wpacony. -- 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
Re: Duplicate temporary dataset names
On Fri, 2008-04-04 at 09:31 -0700, Ulrich Krueger wrote: On second thought ... (I do that a lot ...:-) Me too. That's when I make the *other* half of my mistakes.;-) To make the system generate a truly unique temp DSname, remove the ... name and change any references to it in later steps to use a STEPNAME.DDNAME referback. This should solve your problem. Good catch, Ulrich (and Norbert). Wouldn't have thought of that. Thanks! -- 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
