On Tue, 13 Mar 2007 16:13:25 -0500, Shannon Collinson
<[EMAIL PROTECTED]> wrote:

>Would the regressed-usermod message still pop up if one of the 347 other
>modules in lmod CEEPLPKA besides CEEPLPKA itself was hit by maintenance?
>Supposedly, an ADD LMOD(CEEPLPKA) UMID(usermod) UCLIN is an option, but
>since that field doesn't show up in a list of an LMOD, I wonder if it
>really works.
>

No, that is not an option.  There is no UMID field on the LMOD.  You
could change LASTUPD, but that won't do anything.  You are correct that
you would have to use UCLIN to update the MOD entries for all of the
MODs in CEEPLPKA in order to get the warning from SMP/E if there was
any maintenance at all that hit CEEPLPKA.     

>And how do I code the actual usermod to pull in CEEPLPKA, zap it, and
>stick it in an application-specific library?

You could clone your TGT zone / libs or build a new zone just for the LE
fmid (and libraries) and put the usermod on that zone.  You would then
have to apply any LE maintenance to both zones.   

>I'm pretty sure SMP/e will
>frown upon me trying to use the same name for the mod while sticking it in
>a different library (without hurting the production CEEPLPKA).

It will.

Go back to the beginning.  Why do you need to use SMP/E for this zap if
you only want it for this one application library?  Just copy the 
library and zap the module outside of SMP/E.   If you are worried about
losing some other maintenance to that module just for this one application,
then whenever you apply z/OS maintenance add a post apply step to 
re-copy SCEERUN and apply the zap again. This is a manual procedure, but
so is cloning after you apply maintenance.   So add the step to your 
cloning procedures documentation / JCL.   

We also run an ISV product (perhaps the same one) that requires a zap to a 
module that is part of CEEPLPKA.  Even though we only run the product
on one LPAR, I still maintain the zap as a usermod.  The sysres is
used on many other LPARs that don't run the product, but the modification
done by the ISV is such that if their product isn't running or activated
it doesn't affect normal LE behavior.  Perhaps this would be an option
for you also. 

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group:  G-ITO
mailto:[EMAIL PROTECTED]
z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/
Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

----------------------------------------------------------------------
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

Reply via email to