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 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=HAS&SYSNAME then in HAS&SYSNAME 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) > > 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=HAS&SYSNAME > then in HAS&SYSNAME 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 wrote: >> 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. > 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
