Hello, Mike. I'm the author of the APAR/PTF in question as well as some of the wording the canned DYNACT hold text. I can try to explain.
DYNACT is intended to provide for non-disruptively reloading modules used by the ICSF address space (CSFINPVT, CSFINPV2) and the ICSF LPA modules should they be impacted by service. MIGLIB is used only for IPCS formatters and models, which are not involved in DYNACT. The same is true for load modules in SCSFSTUB (where the ICSF callable service stubs exist) and ICSF dialog modules (which happen to live in SCSFMOD0 as well). All these load modules would be brought in using the normal service method (at the next IPL or via dynamic LNKLST). I understand the confusion about this and we are working on making the wording clearer. Eric Rossman, CISSP® ICSF Cryptographic Security Development z/OS Enabling Technologies [email protected] Mike Martin <[email protected]> wrote: > I'm a little surprised that IBM's HOLD(DYNACT) doesn't speak to MIGLIB. > Hi all, > > We need additional ICSF capability (CVN18) so we are applying a PTF (UJ03312) to our z/OS V2.4 ISCF (HCR77D0). > > There is an SMP/E HOLD(DYNACT) which tells us how to dynamically update the ICSF code from libraries CSFMOD0 and IEALNKE. > > But, we noticed that SYS1.MIGLIB was also updated during the SMP/E apply. We don't apply to a running system, so I'm wondering how we handle the updates to MIGLIB as there is no mention of it in the ISCF doc for dynamic service update. > > Mike Martin ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
