You may also want to consider WLM Inits rather than JES2 Inits. You can let WLM Manage your work for running batch jobs.
Lizette -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Lizette Koehler Sent: Friday, April 17, 2020 6:39 PM To: [email protected] Subject: Re: JES2 parm change - how make sure it's right? You might want to "pop" JES2 ($PJES2) At start up, It will tell you which parms are out of sync with what it is running. $HASP442 and $HASP496 will tell you when parms are out of sync. JES2 will always use what it last knew if the parms are different. Other option is to create a Secondary JES2, and test your parms there. I have done this in the past and it is not difficult to do. Lizette -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Charles Mills Sent: Friday, April 17, 2020 12:59 PM To: [email protected] Subject: Re: JES2 parm change - how make sure it's right? Sigh. Version 2.1, and yes I know, and yes an upgrade to 2.4 is on the calendar. That is one of the reasons for wanting to make this change "persistent." Thanks all. I guess I will run the changes thru IEHEYEBALL and hope for the best. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Cieri, Anthony Sent: Friday, April 17, 2020 12:04 PM To: [email protected] Subject: Re: JES2 parm change - how make sure it's right? I should have specified that you need to be at zOS V2.3 or above......... -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Cieri, Anthony Sent: Friday, April 17, 2020 2:01 PM To: [email protected] Subject: Re: JES2 parm change - how make sure it's right? [[ SEI WARNING *** This email was sent from an external source. Do not open attachments or click on links from unknown or suspicious senders. *** ]] (1) Is this what you are looking for..........(JES2 Initialization Dataset Checker) https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ha sa300/dscheck.htm (2) It does depend on the error. In my experience with changing JES2 init parms, a syntax error can cause JES2 to issue an error message along with a WTOR asking for the correct values or to ignore the error. JES2 initialization waits in these cases for a response to the WTOR. Hth Tony -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Charles Mills Sent: Friday, April 17, 2020 1:44 PM To: [email protected] Subject: JES2 parm change - how make sure it's right? [[ SEI WARNING *** This email was sent from an external source. Do not open attachments or click on links from unknown or suspicious senders. *** ]] Humor me. I'm an experienced developer playing newbie sysprog in my spare time. I've got a JES2 system where I want to change the order of job classes for some of the initiators. I could get professional help but it is a service bureau so that involves opening a ticket, dollars, etc., etc. I have done it through SDSF and all is well. I now want to make the change persistent. I have JES2PARM open in an editor. I can make the changes *very carefully*. Questions: (1) is there any way to test it, particularly that I have not fouled it up terribly? The next IPL is probably months away, and a failure would be very unpleasant. Is there any sort of non-disruptive "TYPRUN=SCAN" sort of option to get JES2 to say the parm file is or is not okay? (2) alternatively, what would happen if it were bad? Suppose I fat-fingered a comma? Unusable system? I am not sure what I am looking at but it looks to me like TCPIP and TCAS are running under JES2. Thanks much, Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
