Since you are dealing with non-IBM updates, I assume you will be using different target and DLIB zones. This eliminates any problems with duplicate MOD or LMOD names.
To get SMPE to copy the member form the IBM library to your work library, create a USERMOD with a ++MOD MCS and specify the destination in the SYSLIB operand and the source in the LKLIB operand. If you want the LMOD CEEPLPKA from IBM, then the source is CEE.SCEELPA. If you just want the MOD CEEPLPKA, then the source is the distribution library where the MOD is kept after being accepted. You can then create a second USERMOD to apply the vendor updates. If you copied the LMOD, you will need to use UCL to create a MOD entry for each MOD the vendor updates. Each of these MOD entries should point to the LMOD. -----Original Message----- From: Collinson.Shannon [mailto:snip] Sent: Tuesday, March 13, 2007 1:21 PM To: [email protected] Subject: SMP/e usermod coding question I need to create a usermod to handle a non-IBM product zap to an LE module that I do NOT want hitting the actual production LE module. Instead, I want to be able to copy the module (or use some other SMP/e controlled method) from the current CEE.SCEELPA library into a product-specific library and apply the zap. If any maintenance comes in for the LE module (CEEPLPKA), I want the usermod to get regressed, so we'll know the product-specific copy needs to get updated. This is for a date-simulation product, which apparently is handling the ability to override LE-calls to date routines in much the same way as any other date-simulation product, so I'm hoping that someone else has hit the same requirement in the past. ---------------------------------------------------------------------- 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
