Corrected. RECEIVEd --> APPLied . . . 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: Skip Robinson <[email protected]> To: [email protected], Date: 05/15/2014 01:58 PM Subject: Re: SMP/E Question regarding automatically relinking a load module with maintenance Sent by: IBM Mainframe Discussion List <[email protected]> REWORK has no effect on APPLY, only on RECEIVE. Absent a higher REWORK value, re-RECEIVE will fail with a very descriptive message to the effect that the REWORK value is not higher than the old one. Re-APPLY will fail without REDO if the sysmod already exists in the target zone regardless of whether the latest version of the sysmod differs from one previously *APPLied*. No comparison is done. You have to be careful that the new sysmod has the same structure (same combination of elements in the same relationship) in order to do what we do. It's our usermod; we haven't changed it for years. Occasionally a sysmod will come from IBM that explicitly instructs the user to first RESTORE/REJECT a previous version of it. Do it. If a sysmod is *not* present in the global and/or target zones, it will RECEIVE and/or APPLY without REWORK or REDO. If you're uncomfortable with REWORK/REDO, then by all means do RESTORE/REJECT first. The key is to get the JCLIN right because that's how SMPE knows how to 'fully install' your sysmod. . . 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: Jon Perryman <[email protected]> To: [email protected], Date: 05/15/2014 01:06 PM Subject: Re: SMP/E Question regarding automatically relinking a load module with maintenance Sent by: IBM Mainframe Discussion List <[email protected]> There is an error in your usermod. Using group temporarily corrected your problem but you still have a problem. If you change this exit again, you may not get the expected results from APPLY GROUP REDO. Without specifics, we can only guess at the error. For example, if this module was auto linked with the load module instead of SMP/E replacing the module within the load module.In this case, the first APPLY would have assembled the module. The second apply with GROUP would have linked it. If this is the problem, then SMP/e won't specify REPLACE for the binder. Skip's recommendation is good example. Just be aware that you need to ensure the JCLIN matches existing definitions. Your description of the modules and load module structure is not clear so you may have additional modules that are affected. Check with the vendor for a sample on how they recommend installing this as a usermod. Jon Perryman On Thursday, May 15, 2014 10:08 AM, "Hardee, Chuck" <[email protected]> wrote: 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. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
