Peter Hunkeler wrote: >>You could review your SYSLOG to see what things are started before your ESM >>started. >IMHO, the ESM (Enterprise Security Manager?) is started before any address >space is built. The ESM is initialized as part of NIP processing.
When I (and John McKown) referred to ESM, we are referring to RACF and similar products. For RACF, several STCs like 'MASTER SCHEDULER JCL' and subsystem services are started BEFORE RACF is started, but the SAF interface is already in place at that stage of IPL. >At least for RACF, don't misinterpret the non-existence of the RACF STC to >mean RACF is not active. It is! True. >>Some of these STCs are started with something like S <STC>,SUB=MSTR , so you >>will not see the Owner. >As I wrote, this is *not* dependent on being started with SUB=MSTR alone. If >the STC registers with JESx later on, SDSF will display the owner. This is why I said *some* of them. >At least here, the RACF address space is started with "S RACF,SUB=MSTR", but >SDSF happily shows the owner of the STC (and its JESx jobid). I know that very well. >>Very true. Thanks for the detailed explanation. Those address spaces are also >>running with AC(1) programs, usually sitting in a LINKLIST and/or APF list, >>depending on how+when they're started in the first place. >STC job step programs do not need to, but can run APF authorized. They can >also run in key 0-7 via SCHEDxx PPT. Those are authorized as well. True. I hope your comments will help the OP. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
