I took a little trip in the Wayback Machine. Once upon a time, you could check out the *syntax* of your JES2 init deck by simply issuing S JES2. The whole init deck would be read and syntax checked. Messages issued for any errors. Finally you would get the message 'Subsystem not dormant' and the new task would end. I seem to remember that this little trick stopped working some time back; it depended on JES2 going all the way through the deck and not checking for duplicate until the very end.
However, even when it worked, it flagged only syntax errors. More subtle problems would go unnoticed: inconsistencies among statements and even more insidious, differences between the deck and the running system. These days a whole slew of parameters can be changed dynamically with or without supporting edit(s) in the init deck. I'd say that a majority of parms are not even examined on a hot or warm start, only on a cold start. That's a particularly awkward moment to discover a change that cannot work properly in the current environment. At most non-terminating messages may be issued that must be sifted through in syslog. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Cieri, Anthony Sent: Friday, April 17, 2020 12:04 PM To: [email protected] Subject: (External):Re: JES2 parm change - how make sure it's right? CAUTION EXTERNAL EMAIL 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.hasa300/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
