On 6/18/2015 5:11 AM, [email protected] wrote:
Now that CAMASTER has become a mandatory address space, I am asking myself how
that address is actually started. The CA documentation makes it sound as if it
were magic that starts it, but I don't believe in magic. There are knowledge
base articles out there that say that starting CAMASTER at the SSI is too late
(which makes sense, especially if a customer uses TSS or ACF2 for security). I
would still like to know *how* it is started. Is IBM checking for the presence
of certain modules in lpa and then start it during MSI? Does anyone know?
What I dislike is also the fact that CA states that absolutely no security
definitions are required, since the address space is TRUSTED. Sounds like they
give themselves the TRUSTED attribute, since no entry in STARTED is required
and my default userid without any rights for non-defined STCs was not taken.
The address space has all kinds of priviledges via SCHEDxx and is obviously APF
authorized.
Barbara
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
Hi Barbara,
I did a Bit Bucket presentation at SHARE on this a few years back.
CAMASTER at the time used IKJEFXSR as a front-end. CA is supposed to
have changed it to use a supported z/OS interface. Open a case with
them and ask. That's how I found out about IKJEFXSR.
Regards,
Tom Conley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
