JES2 allows almost everything to be altered by a JES2 command with the execption of the length of the spool volume name. That one still takes a cold start.
What you might do is create an automation process that at JES2 startup sees the HASP442 and HASP496 messages the indicates the parms are not in sync with what she knew from the last warm/cold start. Then you could know well before an issue occurs if anything has changed. If that message does appear, send your group an email to that effect. You will then be able to find out the answer to the questions What was changed When was it changed And what group /person changed it. Lizette > Hi guys, > we recently had some incidents which caused us a lot of debugging before we > noticed what was going one. > Some JES2 parmlib definitions did not correspond with the actual state of the > definitions in JES2. > I'm wondering if someone has had already the same problem, and is having an > automated way to check for differences between parmlib and actual jes2 defs > (which have been dynamically changed). > We are thinking on querying all jes2 defs, and checking then with defs in > parmlib. Should someone has already written this and willing to share, that > would be very much appreciated. > Any other ideas are also welcome. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
