Whenever I have to use an IBM module in a library other than where IBM put it (++SAMP is just one example), I copy it to a private TXLIB, modify it if necessary, and then create a USERMOD with both the original data element type (e.g., ++SAMP) and the desired element type (e.g., ++EXEC), both using the original name of the module and both referencing the TXLIB. The desired element type also references the correct SYSLIB where I want the module to end up. If the original element type is correct but doesn't support the ++MOVE statement, then I use ++USER1.
The end result is both the original IBM element and my usable copy are both flagged with the USERMOD which generates the appropriate SMPE diagnostic if I ever attempt to apply an IBM update. -----Original Message----- From: Jeffery Swagger Sent: Thursday, July 02, 2009 5:48 PM To: [email protected] Subject: Re: SMPE usermod sample Yes, but this strikes me as incomplete. I did try an APPLY CHECK of the proposed USERMOD (minus the JCLIN) and it appeared to produce the desired result. In that a ++EXEC element would be created (target library SISPEXEC) with an ALIAS of ONLY copied from SISPSAMP. However, here's the problem. The shipped IBM element ++SAMP(ISRONLY) has no updates associated with it. This is telling me, and I could be wrong, that IBM could ship a PTF to ISRONLY, and then my ++EXEC is out-of-sync because IBM knows nothing of a ++EXEC(ISRONLY). Uh Oh It seems to me that a complete solution to this problem requires that the ++SAMP(ISRONLY) must have the RMID updated. That way, if there is an IBM PTF, then SMP/E will detect a MODID error. ---------------------------------------------------------------------- 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
