Re: DAILY changes to your System Values and IBM commands

[CRPence <crp@xxxxxxxxxxxxxxxxxxxx>]

  A script such as that would be part of appropriate change management, 
to ensure such customizations were in place again after updates; i.e. 
upgrade to a new release, and on the rare occasion for when it might be 
required after a PTF [cumulative] package has been applied -- some 
requests could be categorized as to when a group of updates should run. 
 Including the comments for the change management in the script is good 
as well, although I see comments that are similar to some horrible 
comments I have seen before both in code and controlled system change 
management... What the value or setting /was xxx before/ as a comment is 
meaningless, and should explain *why* it was changed to the current 
value, for what it intends to accomplish for what business rule or 
requirement or to circumvent what?

  Having such a script [compiled CLP, or REXX or //BCHJOB interpreted] 
initiated from the QSTRUPPGM when as compared to a prior setting in a 
data area [or that the data area does not exist] to see if the release 
or the cumulative PTF level has changed, would then process the 
appropriate groups of commands for the activity which deems the new run 
of the change script was required.

  Note:  As coded, to ignore all errors, the CLP could replace each of 
the MONMSG with one global MONMSG.  Additionally if monitoring for 
CPF0000, there is no point to monitor any other error, because any error 
outside of CPFxxxx will effect CPF9999 which is in the range CPF0000. 
Rarely will a CPDxxxx or CPCxxxx be used as an Escape which is normally 
what is being monitored in such a script; i.e. those are generally Diag 
and Comp messages, neither of which as a message type, is capable of 
being monitored.

Regards, Chuck