The problem that you've described is far more complicated that it may first 
seem.  If I understand correctly what you want to do is keep the original 
CEEPLPKA in use and in the normal production library, while also creating a 
duplicate CEEPLPKA in a separate library.  In effect, you would have two 
versions of CEEPLPKA with different modifications, so the UCLIN approach will 
absolutely NOT work for you.

In effect, what you need to do is "hijack" this module into your usermod.  The 
point is to create a different TARGET/DLIB zone with a user FMID which then 
"owns" this module.  Once this is done, then the USERMOD (zap) can be coded 
against the user FMID.  By keeping them in separate TARGET/DLIB zones, then 
SMP/E won't complain about the duplicate names because they aren't seen, nor 
are they part of the same FMID.

If maintenance comes in against the production CEEPLPKA, then there is no way 
(in my view) to trigger a regression message unless there is some way to create 
a cross zone FMID pre-requisite situation.  Without checking into this, I don't 
know how this would be accomplished.  (It may be reasonable to create a dummy 
USERMOD against the production that would simply trigger the regression message 
without actually changing anything in the production module).

It is also possible that you could create an artificial notification by using 
the SMP/E exit to review SYSMODS coming into the system, although this may be 
more than you had in mind.

Good luck

Adam

>And how do I code the actual usermod to pull in CEEPLPKA, zap it, and 
>stick it in an application-specific library?  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).  I was 
>thinking of setting the usermod element up with a different name and 
>giving it the alias of CEEPLPKA, but wasn't sure how "aware" SMP/e's alias 
>processing was in v3.4.

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