Clarification on REWORK. Besides documenting the APPLY date (which SMPE shows anyway), it obviates the need to first RESTORE/REJECT the usermod before re-RECEIVE/APPLY, a hassle I don't see the point of for a usermod whose sysmod structure never changes. For re-RECEIVE to work, REWORK must be 'higher' than the previous value. Current date in YYYYDDD format is obviously higher each day. The final digit is for multiple retries in a single day. ROT: if you've tried 10 times and still haven't got it right, it's time to knock off for the day and try again tomorrow. ;-)
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: "Hardee, Chuck" <[email protected]> To: [email protected], Date: 05/15/2014 11:07 AM Subject: Re: SMP/E Question regarding automatically relinking a load module with maintenance Sent by: IBM Mainframe Discussion List <[email protected]> Thanks Skip, I'll look it over and compare it to mine. Mine's working now but your process may be easier than what I've set up. Charles (Chuck) Hardee Senior Systems Engineer/Database Administration CCG Information Technology Thermo Fisher Scientific 300 Industry Drive Pittsburgh, PA 15275 Direct: 724-517-2633 FAX: 412-490-9230 [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Skip Robinson Sent: Thursday, May 15, 2014 1:53 PM To: [email protected] Subject: Re: SMP/E Question regarding automatically relinking a load module with maintenance Here's how we handle our usermod for SMF exit IEEACTRT. The usermod also marks the corresponding SAMPLIB member so as to cause a regression message if IBM's version changes. REWORK documents the date of last APPLY. This job assembles our source and links everything together. //STEP1 EXEC SMPR13 //SYSIN DD * SET BDY (GLOBAL) . RECEIVE SYSMODS . SET BDY (MVST100) . APPLY S(SMFACT2) REDO . UCLIN . REP SAMP(IEEACTRT) RMID(SMFACT2) /* IN CASE SAMPLE CHANGES */ . ENDUCL . //SMPPTFIN DD DATA,DLM=$$ ++USERMOD (SMFACT2) REWORK(20133432) . ++VER (Z038) FMID (HBB7780) . ++JCLIN . //SMFACT2 EXEC LINKS,PARM='XREF,LIST,LET,NCAL,RENT' //SYSLMOD DD DISP=SHR,DSN=SYS1.LINKLIB //AOSB3 DD DISP=SHR,DSN=SYS1.AOSB3 //SYSLIN DD * ORDER SCEACTMS INCLUDE AOSB3(SCEACTMS) INCLUDE AOSB3(IEFTB724) /* CONTAINS IEFYS */ ENTRY SCEACTMS MODE AMODE(31) RMODE(ANY) NAME SCEACTMS(R) ++SRC(SCEACTMS) DISTLIB(ASAMPLIB) . <Our modification of SAMPLIB source> $$ . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: "Hardee, Chuck" <[email protected]> To: [email protected], Date: 05/15/2014 10:08 AM Subject: Re: SMP/E Question regarding automatically relinking a load module with maintenance Sent by: IBM Mainframe Discussion List <[email protected]> Thanks! I added GROUP to one of the APPLY REDOs for one of the exit usermods and now the user mod gets assembled and the table module gets relinked. Exactly what I wanted. Charles (Chuck) Hardee Senior Systems Engineer/Database Administration CCG Information Technology Thermo Fisher Scientific 300 Industry Drive Pittsburgh, PA 15275 Direct: 724-517-2633 FAX: 412-490-9230 [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of CM Poncelet Sent: Thursday, May 15, 2014 12:47 PM To: [email protected] Subject: Re: SMP/E Question regarding automatically relinking a load module with maintenance If your APPLY REDO was for the usermod only, I would suggest that you do another APPLY REDO for the "table" module and/or for the final load module too if you created your final load module via SMP/E. Failing that, have you tried an APPLY REDO GROUP for your usermod? Hardee, Chuck wrote: >I have a vendor product that provides for a customization of the product via a load module. >The load module is a "table" of exits that are called at certain points in the product to allow the user to make decision, perform additional functions, etc. > >At our site, this module had been set up to take advantage of 5 different exit points. >I have created the 5 different exit modules and successfully set them up in SMP/E as usermods. >I have also created the vendor's required "table" module defining the 5 different modules as a usermod and have successfully created the final load module. > >All looks as it should, however, if I change the source of one of the exit modules and perform an APPLY REDO, the exit is assembled and saved, but the "table" module is not linked. > >The "table" module's linked command includes an INCLUDE for each of the required exit modules, which I thought was how SMP/E knew to monitor those modules for change and perform the relink should any one of them change. > >I am a bit rusty on creating SMP/E from scratch so I believe I am missing something. > >Any ideas of what I may have missed in the usermod(s)? > >Thanks, >Chuck ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
