At 10:46 -0400 on 10/14/2009, Lizette Koehler wrote about Re: JES2
Parmlib inconsistent with active definitions:
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.
Do all parms that are changed by commands get logged to the
checkpoint record and thus survive a warm-start? If I alter the
settings for a printer for example, after I warm-start will it have
those settings or the ones from PARMLIB? I can think of a number of
other settings of this type where the changes are intended to not be
permanent and thus may not get logged.
----------------------------------------------------------------------
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
