Beat me to it. I was going to suggest a ++MOVE usermod, provided the SSI module is SMP/E-maintained.
Ant. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Thursday, 21 September 2017 11:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Keeping SSN init modules current In poking around our stable of usermods, I find this usermod for ISPF: ++USERMOD (ISPF003) REWORK(20141710) . ++VER (Z038) FMID (HIF7N02) . ++MOVE (FLMIO24 ) SYSLIB(SISPLPA) TOSYSLIB(SISPLOAD) LMOD . .. The point of this IBM-suggested usermod is to move SCLM modules from LPA to link list for shops that don't utilize SCLM heavily. What if we created something like this: ++USERMOD (HSCxxxx) REWORK(date) . ++VER (Z038) FMID (hsc-fmid) . ++MOVE (ssn-init-module) SYSLIB(hsc-loadlib) TOSYSLIB(LINKLIB) LMOD . where LINKLIB is SYS1.LINKLIB. Future HSC maintenance, if any, would find the module in SYS1.LINKLIB and keep it up to date until the next upgrade, which would require reAPPLYing the usermod. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Brennan Sent: Wednesday, September 20, 2017 3:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Keeping SSN init modules current I was thinking of similar craziness, but I'd replace the actual HSC init program with my own. Then like you implied, that code would dynamically allocate the DSN and do a LOAD DCB= to get the real module into memory. Then deallocate, restore registers (to what they were at entry), branch, and "The OS will never know" (famous last words). This method would also mean following a convention I've argued for over many years: "Never use version numbers in production load library names". Ok! Now back to the real world and just go update the doc :) Mark Jacobs - Listserv wrote: > Here's a wild thought. Create your own dummy subsystem with its own > initialization routine that gets executed before any of the subsystems > you're concerned about. This initialization routine can load the other > modules into CSA, or even copy from one library to a linklist library. > We have an installation defined dummy subsystem that uses the > initialization routine to define system level name/token pairs during > the IPL process. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
