I normally start CAS9 first through the subsystem name table member. Then have CAS9 start TSS, then have TSS start everything else, including JES2.
On Wed, 11 Apr 2007 16:28:46 -0400, Craddock, Chris <[EMAIL PROTECTED]> wrote: >> We use Top Secret. A consultant made a recommendation late last year >> that Top Secret should be the first task started during the IPL >> procedure. The Security Administrator has requested this change. >> >> Currently, we start Top Secret after JES2 completes its start >procedure. >> I really don't see the merit in moving the start of Top Secret earlier >> in the IPL procedure. >> >> Can anyone explain why starting Top Secret/security product is more >> advantageous? > >Well the security product can't protect anything when the security >product itself isn't present in the system right? That would take a >certain amount of voodoo that (as far as I know) TSS doesn't have. >Everything that gets started early in the IPL, i.e. started tasks >started with "SUB=MSTR" before the JES is started, presumably are >tightly controlled by the installation. They can be trusted to do >whatever they need to, or you would not start them that way. > >But once the JES is up, the flood gates can open and all of the "normal" >work can run. Your security system must be up for that work to run. The >security system is intended to be able to run under the master subsystem >before the JES is up and after the JES has gone. There's certainly no >harm in starting it first in the IPL and there may be some benefit in >not delaying later work. I certainly would not wait until after the JES >was up, even though nothing much may be going on that early. And if it >makes your security auditors feel happy... > >CC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
