An alternative to the 'shadow ZAP' is simply to mark an element in SMPE as having been touched by a usermod. For example, we assemble and link SAMPLIB member IEECMDPF for console. We don't modify the sample, but we want to know it changes by PTF. So we run UCLIN to leave a footprint associated with the usermod that creates the load module. This technique has the advantage of working any type element.
UCLIN . REP SAMP(IEECMDPF) RMID(CONS001) . ENDUCL . . . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Greg Dorner <[email protected]> To: [email protected] Date: 07/07/2011 12:26 PM Subject: Re: SMPE how-to question Sent by: IBM Mainframe Discussion List <[email protected]> Hello David, In our company we are not allowed to have this updated code accessible to anyone other than users of Hourglass. Therefore, we copy the affected modules into separate libraries for this purpose and put the zaps directly on those copies. Then we put usermods against those modules in SMP/E so if they change we are notified and can arrange with those that support Hourglass to use the new versions when the maintenance goes active. The usermods are ++ZAP which contain only the NAME statement, therefor the code is not updated in any way. ---------------------------------------------------------------------- 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
