*
I do not think there is a simple or a right or wrong way to do your typical 
usermods, as long as the data in the CSI correctly inventories your software.
*
The crux of the problem is installing the usermod is not the same process as 
maintaining the usermod. I think blending the two into one process is not 
practical.
*
Reinstalling the same usermod is not the same as reinstalling an updated 
usermod.
*
I am diligent to the extreme in maintaining CSI correctness simply because I do 
not want to spend time diagnosing discrepancies. I avoid APPLY REDO because 
I want to test RESTORE processing when I reinstall or update a USERMOD.
*
There is a large population of SMP/E users who do not understand what 
restore processing does. 
*
On the other hand, z/OS engineers/professionals very often have to create 
procedures that z/OS adminstrators/employees have to be able to use.
*
I think the clearest solution is to provide four sets of JCL:
(01). Original install of a usermod.
(02). Install of a usermod update.
(03). Reinstall of an unchanged usermod.
(04). Removal and retirement of a usermod.
*
The differences in initial conditions and processing requirements make the four 
sets of JCL necessary.
*
So in the case of the JCLIN of the source code, which is designed to let SMP/E 
know which SRC entries must be reassembled when a MAC entry changes, the 
JCLIN needs only to be processed when the SRC is changed, and really only 
when a new MACRO is included in the SRC.
*
My goal always is to have SMP/E do the inventory, keep the inventory, and 
process the inventory as it was designed. It is not nice to lie to SMP/E.
*
Someone mentioned UCLIN regarding SDSF maintenance. Some of those UCLIN 
statements are required only if maintaining SDSF and JES2 in separate target 
zones.
*

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to