Don't how I overlooked these messages all these years. Thanks Lizette, that's exactly what I need!
. . 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 [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Wednesday, January 31, 2018 4:26 PM To: [email protected] Subject: (External):Re: Syntax check for JES2 INIT deck So anytime you IPL, JES2 will tell you at start up what is not the same as the init deck. You just need to trap those messages and put them in the queue to update. Look for $HASP442 messages at JES2 startup time On a JES2 warm start, JES2 detected that certain initialization parameters do not match the settings saved in the JES2 checkpoint. This could be the result of an operator command that updated the parameters while the system was running or because an incorrect attempt was made to update the initialization statement. Following $HASP442, the $HASP496 message displays each incorrect initialization parameter, the value specified on the initialization statement, and the value saved in the checkpoint. Lizette A theory can never be proven, but it can be falsified. Karl Raimund Popper > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Jesse 1 Robinson > Sent: Wednesday, January 31, 2018 4:33 PM > To: [email protected] > Subject: Re: Syntax check for JES2 INIT deck > > This looks verrrry nice. I can't tell from the doc linked to: will it > flag discrepancies between the running system and the init deck? Ever > since JES2 went 'mostly dynamic' years ago, there has been a risk of > failing to update the deck to match a dynamic change. A shop could go > years without realizing that the deck is severely out of date--until a > cold start resets all values back to the init deck specifications. > > . > . > 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 [mailto:[email protected]] > On Behalf Of Ed Jaffe > Sent: Tuesday, January 30, 2018 10:17 PM > To: [email protected] > Subject: (External):Re: Syntax check for JES2 INIT deck > > On 1/30/2018 3:51 PM, Jesse 1 Robinson wrote: > > (It must be JES2zday). There used to a trick to get a JES2 INIT deck > > syntax > check. You would 'S JES2' with the system running. JES2 would > eventually say 'SUBSYSTEM NOT DORMANT' and quit, but along the way > read the INIT deck and flag any syntax errors. We tried that today > with a deliberate syntax error, but no complaints during startup. Did > this trick stop working somewhere along the way? > > One of the recent JES2 enhancements, intended to help entice JES3 > customers accept JES2, was a JES3-like initialization stream syntax > checker: > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3. > hasa300/dscheck.htm > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > http://www.phoenixsoftware.com/ > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
