Check out the IBM-MAIN thread " What is IKJEFXSR?" I started in April 2013. Lizette pointed us to CA article
https://communities.ca.com/kbtech?docid=570878&searchID=TEC570878 Which does explain how CAMASTER and CAHCHECK get going. It seems newer than ACF2 or Top-Secret, so I suspect those products "hook in" elsewhere. I found this module by checking my total LPA/Link concatenation for duplicates. I do find ICHALTSP as a in CAW0LINK, but I don't find any such module as a duplicate in the IBM libraries. It must be optional :) I am RACF, so this is likely all the light I have to shed here. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Storr, Lon A CTR USARMY HRC (US) > Sent: Friday, May 30, 2014 12:53 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: CA Common Services (and RACF too?) hook into Master Scheduler > Initialization (UNCLASSIFIED) > > Classification: UNCLASSIFIED > Caveats: NONE > > Hello List, > > I've recently had cause to look into how CA-ACF2 gets started very early in > the > system initialization process. It apparently gets started by the CA Common > Services (CCS) component but, as far as I can tell, this processing occurs > before the CAS9 address space (PGM=CAIRIM) starts. > > CA documentation refers to two members of PARMLIB (i.e. CAISECnn and > CAIACFnn) which, among other things, may be used to start up ACF2. It took a > lot of research to figure out what (program) is reading those members and > how it gets control. I stumbled across a mechanism that I was not aware of; I > believe that it belongs to RACF. > > I'm hoping that some of you may be able to elaborate on the information I > have so far, which is as follows: > > MSTJCLnn starts PGM=IEEMB860 > The Master Scheduler apparently ATTACHes PGM=ICHALTSP (which then runs > in the *MASTER* address space) CA has intercepted this by assigning > alias=ICHALTSP to their LMOD (in CAW0LINK) called CCSALTSP Hence, the > Master Scheduler starts CCS (via EP=ICHALTSP) > > LMOD=CAMSIPLX is invoked, which somehow starts CAMSINIT (aka > CAMASTER) > I believe that it is the aforementioned process that builds an SSCVT for CA > products, reads CA PARMLIB members and, if specified, starts ACF2. > > As you can see, the information I currently have is sparse and mostly > conjecture. Can somebody please add to the above outline and/or correct > errors? > > Thanks, > Alan > > > > > Classification: UNCLASSIFIED > Caveats: NONE > > ---------------------------------------------------------------------- > 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
