Re: The hardest JCL ERROR I have met
On Thu, 1 Apr 2010 18:37:05 -0500, Larry Stout lst...@fdrinnovation.com wrote: A quick way to determine the error is to submit the JCL as a batch job. If the job fails during syntax checking, it will not matter whether the data sets are cataloged or whether JES2 is already running. //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE //PEND //DOITEXEC PROC=JES2 The resulting messages are: STMT NO. MESSAGE 3 IEFC001I PROCEDURE JES2 WAS EXPANDED USING INSTREAM PROCEDURE DEFINITION 10 IEF631I NUMBER OF DDNAMES EXCEEDS MAXIMUM IN THE DDNAME FIELD 11 IEF686I DDNAME REFERRED TO ON DDNAME KEYWORD IN PRIOR STEP WAS NOT RESOLVED The second message, IEF631I, is the error. This message is not fully described in the System Messages manual: And I was wondering why those messages were not seen on the console, but there is a good chance that IEF196I is suppressed via MPF. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
In a6b9336cdb62bb46b9f8708e686a7ea005c021b...@nrhmms8p02.uicnrh.dom, on 03/29/2010 at 08:09 AM, McKown, John john.mck...@healthmarkets.com said: The STEPLIB can be anywhere within the step boundries. It is only by convention that we place it directly after the EXEC. In fact this can cause a problem. The external writer, at least back a couple of decades ago, would scan the TIOT and select the first DD found as its output DD. Did you create an ETR? It's supposed to use IEFRDER. -- 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
In 222817403-1269867357-cardhu_decombobulator_blackberry.rim.net-19525017...@bda026.bisx.prod.on.blackberry, on 03/29/2010 at 12:55 PM, Ted MacNEIL eamacn...@yahoo.ca said: Usually, if there is a parm specified on the START command, and it's not specified in the PROC statement, this generates a JCL error. Nonsense. -- 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
In a6b9336cdb62bb46b9f8708e686a7ea005c021b...@nrhmms8p02.uicnrh.dom, on 03/29/2010 at 07:56 AM, McKown, John john.mck...@healthmarkets.com said: The above just looks wrong to me for some reason. Because of the undoubled apostrophes? -- 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Shmuel Metz (Seymour J.) Sent: Thursday, April 01, 2010 11:45 AM To: IBM-MAIN@bama.ua.edu Subject: Re: The hardest JCL ERROR I have met In a6b9336cdb62bb46b9f8708e686a7ea005c021b...@nrhmms8p02.uicnrh.dom, on 03/29/2010 at 08:09 AM, McKown, John john.mck...@healthmarkets.com said: The STEPLIB can be anywhere within the step boundries. It is only by convention that we place it directly after the EXEC. In fact this can cause a problem. The external writer, at least back a couple of decades ago, would scan the TIOT and select the first DD found as its output DD. Did you create an ETR? It's supposed to use IEFRDER. -- Shmuel (Seymour J.) Metz, SysProg and JOAT This was back around 1984 or so. I don't even know if ETRs existed back then. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
This was back around 1984 or so. I don't even know if ETRs existed back then. Their equivalent did. I opened my first ticket with IBM in 1981. It was all telephone and courier, but the system still worked, sort of. The ISC wasn't that far from where I worked at the time. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
On Thu, 1 Apr 2010 12:44:56 -0400, Shmuel Metz (Seymour J.) wrote: The STEPLIB can be anywhere within the step boundries. It is only by convention that we place it directly after the EXEC. In fact this can cause a problem. The external writer, at least back a couple of decades ago, would scan the TIOT and select the first DD found as its output DD. Did you create an ETR? It's supposed to use IEFRDER. Compatibility? A couple years ago, you were uncomfortable when you learned that IBM had (quite a while previously) repaired a similar obvious error concerning the ordering of SYSIN DD overrides. The above (mis-)behavior would have been forgiving in some cases when the programmer misspelled IEFDRER; fixing it would have broken at least some existing JCL. But I support repairing such things, at least at release boundaries, and with sufficient notification. A validation tool also helps. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
A quick way to determine the error is to submit the JCL as a batch job. If the job fails during syntax checking, it will not matter whether the data sets are cataloged or whether JES2 is already running. //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE //PEND //DOITEXEC PROC=JES2 The resulting messages are: STMT NO. MESSAGE 3 IEFC001I PROCEDURE JES2 WAS EXPANDED USING INSTREAM PROCEDURE DEFINITION 10 IEF631I NUMBER OF DDNAMES EXCEEDS MAXIMUM IN THE DDNAME FIELD 11 IEF686I DDNAME REFERRED TO ON DDNAME KEYWORD IN PRIOR STEP WAS NOT RESOLVED The second message, IEF631I, is the error. This message is not fully described in the System Messages manual: Explanation: The system found the DDNAME parameter within a job step unresolved in six or more DD statements at one time. There may be no more than 5 outstanding, unresolved DDNAME parameters in a step at one time. The JCL rule that is being violated is documented under the DDNAME parameter in the MVS JCL Reference, SA22-7597-13, in topic 12.17.2 Subparameter Definition: A job step or procedure step can contain up to five outstanding, unresolved DD parameters in a step at one time. Each DDNAME parameter must refer to a different DD statement. The text of message IEF631I, and the description in the System Messages manual, refer to the first sentence, but the rule that is being violated in this example is the second sentence. Larry Stout On Mon, 29 Mar 2010 10:36:03 -0500, Ramiro Camposagrado ramiro.camposagr...@bbh.com wrote: Why not start your new JES2 proc on a system that has JES2 already started? It should go ro regular conversion and then issue the $HASP426 message. On Mon, 29 Mar 2010 09:40:01 -0500, Mark Zelden mzel...@flash.net wrote (in part): But why do you have 2 HASPLIST DDs? Lose the second one. On Mon, 29 Mar 2010 13:15:33 +, Rob Scott rsc...@rocketsoftware.com wrote: Why do you have *two* HASPLIST DD specifications ? Rob Scott Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: rsc...@rs.com Web: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ron Wells Sent: 29 March 2010 14:01 To: IBM-MAIN@bama.ua.edu Subject: Re: The hardest JCL ERROR I have met (2) HASPLIST ?? STEPLIB s/b after EXEC From: Hu Lei helite...@gmail.com To: IBM-MAIN@bama.ua.edu Date: 03/29/2010 07:45 AM Subject: The hardest JCL ERROR I have met Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1
答复: The hardest JCL ERROR I have met
It is shame to say the JCL error was caused by duplicate DD HASPLIST. Thanks again. Thanks Mark! -邮件原件- 发件人: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] 代表 Mark Zelden 发送时间: Tuesday, March 30, 2010 8:03 AM 收件人: IBM-MAIN@bama.ua.edu 主题: Re: The hardest JCL ERROR I have met On Mon, 29 Mar 2010 17:32:22 -0600, Rick Fochtman rfocht...@ync.net wrote: --snip Nothing jumps out at me. But I would suggest one change to the COMMND00 member: COM='S JES2,PARM=(WARM,NOREQ)' instead of COM='S JES2,PARM='WARM,NOREQ'' The above just looks wrong to me for some reason. --unsnip-- If you insist on using quotes, it should look like this: COM='S JES2,PARM=''WARM,NOREQ''' Doesn't anyone remember the rules concerning quotes within quoted strings? No, as already mentioned, the syntax is fine (try it yourself if you don't believe me). It isn't documented all that well, but there is a sample: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2E291/18.1?SHE LF=IEA2BK91DT=20090109041809 Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Monday, March 29, 2010 6:44 PM To: IBM-MAIN@bama.ua.edu Subject: Re: The hardest JCL ERROR I have met I was wondering if starting JES2 with SUB=MSTR be of any more help on this issue? Lizette Unnecessary. Whenever a START command is issued and the thing being started is listed in the IEFSSNnn member of PARMLIB as a subsystem, or matches the name of a dynamically installed subsystem, the START is done with an implied ,SUB=MSTR. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)
I guess you can't see the presentation if you are not a share user. It asked me for an ID and Password. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Brian Peterson Sent: Monday, March 29, 2010 11:55 AM To: IBM-MAIN@bama.ua.edu Subject: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met) I suggest that you consider removing all those statements from your JES2 proc. My production JES2 proc looks like this: BROWSESYS1.PROCLIB(JES2) - 01.02 Command === * Top of Data * //JES2PROC //JES2EXEC PGM=HASJES20,REGION=0M,TIME=NOLIMIT,PARM='NOREQ' //HASPLIST DD DDNAME=IEFRDER Bottom of Data *** The great thing about this is that there is now almost nothing that can go wrong to prevent JES2 from starting. I learned how to do this from Dave Danner in session 2667 from SHARE in San Diego from August 2007. In this session, Dave's description of how to bullet-proof JES2 starts on page 29 of the presentation. http://ew.share.org/proceedingmod/abstract.cfm?abstract_id=15825 Brian On Mon, 29 Mar 2010 20:35:38 +0800, Hu Lei wrote: Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html == This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)
Have you tried the Contact Us button on the web site? I had thought I understood that if you ask, SHARE will give you an ID for the site. Brian On Tue, 30 Mar 2010 12:54:56 -0500, Ward, Mike S wrote: I guess you can't see the presentation if you are not a share user. It asked me for an ID and Password. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)
On Tue, 30 Mar 2010 12:54:56 -0500, Ward, Mike S mw...@ssfcu.org wrote: I guess you can't see the presentation if you are not a share user. It asked me for an ID and Password. Reader's Digest version: 1) Remove all data set references from JCL. only use EXEC PGM=HASJES20 - optional parm= and //HASPLIST DD DDNAME=IEFRDER ... SYS1.SHASLNKE or SYS1.SHASLINK (older OSes) must be in the LNKLST 2) Put JES2 parm member HASJES2 in logical parmlib concatenation ... this is the default name that will be looked for if 3) Use include members if sharing parms or they are currently broken out into separate parms today. For example INCLUDE PARMLIB_MEMBER=HASSYSNAME then in HASSYSNAME you can include other members 4) Use dynamic PROCLIBs in the parms. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Zelden Sent: Tuesday, March 30, 2010 1:28 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met) snip Reader's Digest version: 1) Remove all data set references from JCL. only use EXEC PGM=HASJES20 - optional parm= and //HASPLIST DD DDNAME=IEFRDER ... SYS1.SHASLNKE or SYS1.SHASLINK (older OSes) must be in the LNKLST 2) Put JES2 parm member HASJES2 in logical parmlib concatenation ... this is the default name that will be looked for if Where is HASJES2 documented? I can't seem to find it. I tested it on my z/OS 1.10 sandbox and it does work. But it bugs me that I can't find the documentation. 3) Use include members if sharing parms or they are currently broken out into separate parms today. For example INCLUDE PARMLIB_MEMBER=HASSYSNAME then in HASSYSNAME you can include other members 4) Use dynamic PROCLIBs in the parms. Mark -- -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)
From z/OS JES2 Commands: 4. default MEMBER=HASjesx member of the default PARMLIB concatination In this case jesx is JES2. Brian On Tue, 30 Mar 2010 13:48:39 -0500, McKown, John wrote: 2) Put JES2 parm member HASJES2 in logical parmlib concatenation ... this is the default name that will be looked for Where is HASJES2 documented? I can't seem to find it. I tested it on my z/OS 1.10 sandbox and it does work. But it bugs me that I can't find the documentation. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Brian Peterson Sent: Tuesday, March 30, 2010 1:57 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met) From z/OS JES2 Commands: 4. default MEMBER=HASjesx member of the default PARMLIB concatination In this case jesx is JES2. Brian Ah. I did a find on HASJES2 and got no hits. And I only looked closely in the Initialization Reference manual. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)
On Tue, 30 Mar 2010 13:48:39 -0500, McKown, John john.mck...@healthmarkets.com wrote: snip 2) Put JES2 parm member HASJES2 in logical parmlib concatenation ... this is the default name that will be looked for if Where is HASJES2 documented? I can't seem to find it. I tested it on my z/OS 1.10 sandbox and it does work. But it bugs me that I can't find the documentation. snip Check the Initialization and Tuning Guide under How to Control JES2 initialization. The manual I am looking at has it in section 1.9.7 - Specifying the start options. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
The hardest JCL ERROR I have met
Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
Change COM='S JES2,PARM='COLD,NOREQ'' to COM='S JES2,PARM=(COLD,NOREQ)' Edouard A. Myers Senior Information Technology Specialist 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: edouard.my...@dc.gov Website: http://www.octo.dc.gov Do you have 10 minutes for better schools, public transportation and healthcare? Your 2010 Census Form has arrived. www.census.dc.gov -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hu Lei Sent: Monday, March 29, 2010 8:36 AM To: IBM-MAIN@bama.ua.edu Subject: The hardest JCL ERROR I have met Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
//JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) . . . COM='S JES2,PARM='COLD,NOREQ'' Where is your PARM= on the PROC statement? Usually, if there is a parm specified on the START command, and it's not specified in the PROC statement, this generates a JCL error. Unless, JES2 (or PARM=) is special? Also, I don't believe PARM is allowed as a PROC variable, since it's a JCL key word. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hu Lei Sent: Monday, March 29, 2010 7:36 AM To: IBM-MAIN@bama.ua.edu Subject: The hardest JCL ERROR I have met Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. Nothing jumps out at me. But I would suggest one change to the COMMND00 member: COM='S JES2,PARM=(WARM,NOREQ)' instead of COM='S JES2,PARM='WARM,NOREQ'' The above just looks wrong to me for some reason. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
(2) HASPLIST ?? STEPLIB s/b after EXEC From: Hu Lei helite...@gmail.com To: IBM-MAIN@bama.ua.edu Date: 03/29/2010 07:45 AM Subject: The hardest JCL ERROR I have met Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
COM='S JES2,PARM='WARM,NOREQ'' The above just looks wrong to me for some reason. If you are allowed to pass it, without specifying PARM= in the PROC statement, then the problem looks like quoting to me. The above should be: COM='S JES2,PARM=''WARM,NOREQ''' Or even: COM='S JES2,PARM=WARM,NOREQ' I always get quoting wrong, depending on parse levels. It's probably better to go with brackets: COM='S JES2,PARM=(WARM,NOREQ)' - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) YES COMM do not need it is above set From: Hu Lei helite...@gmail.com To: IBM-MAIN@bama.ua.edu Date: 03/29/2010 07:45 AM Subject: The hardest JCL ERROR I have met Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ron Wells Sent: Monday, March 29, 2010 8:01 AM To: IBM-MAIN@bama.ua.edu Subject: Re: The hardest JCL ERROR I have met (2) HASPLIST ?? STEPLIB s/b after EXEC The STEPLIB can be anywhere within the step boundries. It is only by convention that we place it directly after the EXEC. In fact this can cause a problem. The external writer, at least back a couple of decades ago, would scan the TIOT and select the first DD found as its output DD. I destroyed a run library by putting the STEPLIB immediately after the EXEC. This cause the external writer to open it for output as a PS file and totally destroy the directory. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
Why do you have *two* HASPLIST DD specifications ? Rob Scott Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: rsc...@rs.com Web: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ron Wells Sent: 29 March 2010 14:01 To: IBM-MAIN@bama.ua.edu Subject: Re: The hardest JCL ERROR I have met (2) HASPLIST ?? STEPLIB s/b after EXEC From: Hu Lei helite...@gmail.com To: IBM-MAIN@bama.ua.edu Date: 03/29/2010 07:45 AM Subject: The hardest JCL ERROR I have met Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
Hu Lei wrote: The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR There should be more errors shown on SYSLOG. And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE Presence of Steplib and lack of IEFRDER DD statement could be problematic. IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) Why START NO? Why not YES? COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Use brackets to simplify your COMMDxx statement. See others replies about this. Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Why is it not in Linklist, but in STEPLIB? From IEF677I, it seems system found some error and used a system default. What is RACF saying about the Started Task profile for JES2? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
You also have a symbolic 'M' to represent a membername. Where is that being provided? If you don't provide a default 'M=member' on the PROC statement, then you must provide it on the START command, i.e. 'S JES2,M=member' Brad Wissink Information Technology Services Iowa State University 515-294-3088 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Elardus Engelbrecht Sent: Monday, March 29, 2010 8:15 AM To: IBM-MAIN@bama.ua.edu Subject: Re: The hardest JCL ERROR I have met Hu Lei wrote: The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR There should be more errors shown on SYSLOG. And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE Presence of Steplib and lack of IEFRDER DD statement could be problematic. IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) Why START NO? Why not YES? COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Use brackets to simplify your COMMDxx statement. See others replies about this. Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Why is it not in Linklist, but in STEPLIB? From IEF677I, it seems system found some error and used a system default. What is RACF saying about the Started Task profile for JES2? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
On Mon, 29 Mar 2010 12:55:48 + Ted MacNEIL eamacn...@yahoo.ca wrote: ://JES2PROC M=JES2PARM : ://IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) :. :. :. :COM='S JES2,PARM='COLD,NOREQ'' :Where is your PARM= on the PROC statement? Don't think that would work. :Usually, if there is a parm specified on the START command, and it's not specified in the PROC statement, this generates a JCL error. PARM will then apply exactly to all steps. No need for the PROC to refer to PARM. :Unless, JES2 (or PARM=) is special? :Also, I don't believe PARM is allowed as a PROC variable, since it's a JCL key word. All EXEC values are valid on a START statement. -- Binyamin Dissen bdis...@dissensoftware.com http://www.dissensoftware.com Director, Dissen Software, Bar Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
Wasn't there a description of the JCL error (IEF196I?)? The COMMNDxx entry looks fine. But why do you have 2 HASPLIST DDs? Lose the second one. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Mon, 29 Mar 2010 20:35:38 +0800, Hu Lei helite...@gmail.com wrote: I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
Out JES2 proc also contains: //IEFRDER DD DUMMY Kevin. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hu Lei Sent: 29 March 2010 13:36 To: IBM-MAIN@bama.ua.edu Subject: The hardest JCL ERROR I have met Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ** This email (and any attachments) may contain privileged and/or confidential information. If you are not the intended recipient please do not disclose, copy, distribute, disseminate or take any action in reliance on it. If you have received this message in error please reply and tell us and then delete it. Should you wish to communicate with us by email we cannot guarantee the security of any data outside our own computer systems. For the protection of Legal General's systems and staff, incoming emails will be automatically scanned. Any information contained in this message may be subject to applicable terms and conditions and must not be construed as giving investment advice within or outside the United Kingdom. Legal General Group plc is registered in England under company number 1417162 and is a holding company. The registered office for all companies in the Legal General group is One Coleman Street London EC2R 5AA. The following subsidiary companies of Legal General Group Plc are authorised and regulated by the Financial Services Authority: Legal General Partnership Services Limited, Legal General Insurance Limited, Legal General Assurance Society Limited, Legal General (Unit Trust Managers) Limited and Legal General (Portfolio Management Services) Limited. Legal General International (Ireland) is incorporated in Ireland under company number 440141 with its registered office at Beaux Lane House, Lower Mercer Street, Dublin 2, Ireland and is authorised by the Financial Regulator in Ireland. Full details can be found at http://www.legalandgeneralgroup.com ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
Have you check out your MSTRJCL setup? Is the proclib that JES2 is in, in that concatenation? Lizette Hu Lei Wrote: Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
On Mon, 29 Mar 2010 20:35:38 +0800, Hu Lei helite...@gmail.com wrote: Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Why not start your new JES2 proc on a system that has JES2 already started? It should go ro regular conversion and then issue the $HASP426 message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
Take a stand alone dump of the system. Use the IPCS MTRACE (I think it is) command to view the SYSLOG in the dump. I'm pretty sure you'll see all the information you'll need to correct the problem. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hu Lei Sent: Monday, March 29, 2010 07:36 To: IBM-MAIN@bama.ua.edu Subject: The hardest JCL ERROR I have met Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. The joblog during IPL looks: IEF403I IEESYSAS - STARTED - TIME=03.47.40 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED IEF452I JES2 - JOB NOT RUN - JCL ERROR And the JES2 proc: //JES2PROC M=JES2PARM //IEFPROC EXEC PGM=HASJES20,TIME=1440,DPRTY=(15,15) //HASPLIST DD DDNAME=IEFRDER //HASPPARM DD DSN=SYS1.CPAC.PARMLIB(M),DISP=SHR //PROC00DD DISP=SHR,DSN=SYS1.CPAC.PROCLIB // DD DISP=SHR,DSN=SYS1.PROCLIB //HASPLIST DD DDNAME=IEFRDER //STEPLIB DD DISP=SHR,DSN=SYS1.SHASLNKE IEFSSNxx SUBSYS SUBNAME(JES2) PRIMARY(YES) START(NO) COMMDxx: COM='S JES2,PARM='COLD,NOREQ'' Here is what I have checked: All the datasets referred in Jes2 proc are cataloged in Master catalog by using IDCAMS listcat. SYS1.SHASLNKE has listed in PROGxx, and APFed. Storage volume has been specified in VATLSTxx. Both null SMS configuration and none SMS environment have tried. Both VLF, LLA, DLF, RACF has started. From IEF677I, it seems system found some error and used a system default. But where is it? Can we got some additional message from other ways? Thanks for your time. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
On Mon, 29 Mar 2010 11:18:46 -0400, Lizette Koehler stars...@mindspring.com wrote: Have you check out your MSTRJCL setup? Is the proclib that JES2 is in, in that concatenation? Good thought. I didn't mention it because I would that that would be obvious. Again, I'll ask about MSGIEF16I. Wouldn't you see seomthing like this on the console: IEF196I 1 //JES2 JOB MSGLEVEL=1 IEF196I 2 //STARTING EXEC JES2 IEF196I STMT NO. MESSAGE IEF196I 2 IEFC612I PROCEDURE JES2 WAS NOT FOUND IEFC452I JES2 - JOB NOT RUN - JCL ERROR 626 IEE122I START COMMAND JCL ERROR -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
(2) HASPLIST ?? STEPLIB s/b after EXEC Not necessarily. I learned years ago, by accident, that STEPLIB can be anywhere withing the step. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
You also have a symbolic 'M' to represent a membername. Where is that being provided? It's right there on the OP's original post: //JES2PROC M=JES2PARM - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
But why do you have 2 HASPLIST DDs? Except for confusion, I thought the second, and subsequent (if any), DD's with duplicate names were ignored. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
Actually, IIRC, they are not really ignored - they simply don't cause an error. They wind up in the TIOT, with all the proper resources allocated - but they are very difficult to use. Ted MacNEIL eamacn...@yahoo.ca 3/29/2010 12:19 PM But why do you have 2 HASPLIST DDs? Except for confusion, I thought the second, and subsequent (if any), DD's with duplicate names were ignored. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
Correct. And in this case since it is pointing to IEFRDER, I think that is what the problem is. Ted, regarding your ignored statement: This has been discussed at various times on this list. That trick is often used with SYSUDUMP. For example: //*NOTE THAT THE FOLLOWING, SEEMINGLY DUPLICATE LINES, //*ARE NOT IN ERROR. THEY ASSURE THAT MULTIPLE DUMPS //*WILL BE INDIVIDUALLY RELEASED TO JES. //SYSUDUMP DD SYSOUT=*,FREE=CLOSE //SYSUDUMP DD SYSOUT=*,FREE=CLOSE //SYSUDUMP DD SYSOUT=*,FREE=CLOSE -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Mon, 29 Mar 2010 12:24:36 -0400, Scott Rowe scott.r...@joann.com wrote: Actually, IIRC, they are not really ignored - they simply don't cause an error. They wind up in the TIOT, with all the proper resources allocated - but they are very difficult to use. Ted MacNEIL eamacn...@yahoo.ca 3/29/2010 12:19 PM But why do you have 2 HASPLIST DDs? Except for confusion, I thought the second, and subsequent (if any), DD's with duplicate names were ignored. - Too busy driving to stop for gas! Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
All EXEC values are valid on a START statement. You're right. I (re-)learned something. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Safeguarding your JES2 Proc (was Re: The hardest JCL ERROR I have met)
I suggest that you consider removing all those statements from your JES2 proc. My production JES2 proc looks like this: BROWSESYS1.PROCLIB(JES2) - 01.02 Command === * Top of Data * //JES2PROC //JES2EXEC PGM=HASJES20,REGION=0M,TIME=NOLIMIT,PARM='NOREQ' //HASPLIST DD DDNAME=IEFRDER Bottom of Data *** The great thing about this is that there is now almost nothing that can go wrong to prevent JES2 from starting. I learned how to do this from Dave Danner in session 2667 from SHARE in San Diego from August 2007. In this session, Dave's description of how to bullet-proof JES2 starts on page 29 of the presentation. http://ew.share.org/proceedingmod/abstract.cfm?abstract_id=15825 Brian On Mon, 29 Mar 2010 20:35:38 +0800, Hu Lei wrote: Hello world! I am trying to setup a mini system, and during IPL, I have met JES2 start error. I am suffer from this error for days, I have do all I can image to correct the error, but still no result. It would be great appreciated if any comments!! Thanks in advance. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
答复: The hardest JCL ERROR I have met
Hi all, Thanks so much for all your comments. It's appreciated that got lots of reply. Here is what I thought 1. I swear no IEF196I message occurred in the console, is any setting to turn on these kinds of message? 2. The Jes2 proclib is the very first proclib in MSTRJCL. 3. I have tried with without STEPLIB, take no effect, and SYS1.SHASLNKE is always in the LNKLST00, and can be found from D PROG,LINKLST 4. No RACF description about this issue. However it's remind me as I have copy the RACF DS directly from the current system, and I have check the STARTED CLASS CLASS NAME - STARTEDJES2.* (G) LEVEL OWNER UNIVERSAL ACCESS YOUR ACCESS WARNING - --- --- 00IBMUSER NONE NONENO USER ACCESS -- IBMUSER ALTER But it seems jes2 will be the first subsystem to start up(except SMS), if RACF can control it? Anyway, it's worth to try it. 5. I have copy the JES2 procedure from current system with minor change, and maybe M= is okay. While I am replying the mail, I have done the following change in one time, and The Jes2 is up... Delete duplicate HASPLIST DD. It's caused by duplicate paste maybe. Damn it. Delete the steplib Update COMMNDxx by replace 'cold,noreq' to (cold,noreq) I will find root cause for the JCL error later (it is about 3:00 AM here), and give the feedback to you. So many thanks for all! -邮件原件- 发件人: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] 代表 Mark Zelden 发送时间: Monday, March 29, 2010 11:47 PM 收件人: IBM-MAIN@bama.ua.edu 主题: Re: The hardest JCL ERROR I have met On Mon, 29 Mar 2010 11:18:46 -0400, Lizette Koehler stars...@mindspring.com wrote: Have you check out your MSTRJCL setup? Is the proclib that JES2 is in, in that concatenation? Good thought. I didn't mention it because I would that that would be obvious. Again, I'll ask about MSGIEF16I. Wouldn't you see seomthing like this on the console: IEF196I 1 //JES2 JOB MSGLEVEL=1 IEF196I 2 //STARTING EXEC JES2 IEF196I STMT NO. MESSAGE IEF196I 2 IEFC612I PROCEDURE JES2 WAS NOT FOUND IEFC452I JES2 - JOB NOT RUN - JCL ERROR 626 IEE122I START COMMAND JCL ERROR -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
--snip Nothing jumps out at me. But I would suggest one change to the COMMND00 member: COM='S JES2,PARM=(WARM,NOREQ)' instead of COM='S JES2,PARM='WARM,NOREQ'' The above just looks wrong to me for some reason. --unsnip-- If you insist on using quotes, it should look like this: COM='S JES2,PARM=''WARM,NOREQ''' Doesn't anyone remember the rules concerning quotes within quoted strings? Rick -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
I was wondering if starting JES2 with SUB=MSTR be of any more help on this issue? Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: The hardest JCL ERROR I have met
On Mon, 29 Mar 2010 17:32:22 -0600, Rick Fochtman rfocht...@ync.net wrote: --snip Nothing jumps out at me. But I would suggest one change to the COMMND00 member: COM='S JES2,PARM=(WARM,NOREQ)' instead of COM='S JES2,PARM='WARM,NOREQ'' The above just looks wrong to me for some reason. --unsnip-- If you insist on using quotes, it should look like this: COM='S JES2,PARM=''WARM,NOREQ''' Doesn't anyone remember the rules concerning quotes within quoted strings? No, as already mentioned, the syntax is fine (try it yourself if you don't believe me). It isn't documented all that well, but there is a sample: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2E291/18.1?SHELF=IEA2BK91DT=20090109041809 Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
