> Dave, > > The crypto-stuff is lots of fun. > > I am going to ask you some questions... the answers will help > you "lay-out" your system. > > 1. Are you going to have any crypto co-processors online to TEST? > 2. Are you going to share any crypto co-processors between > TEST and PROD? > 3. Is the lpar CF1 a coupling facility?
I don't intend to use the crypto processors for TEST at all. We only bring TEST lpar up as a sandbox. CF1 is our coupling facility which is currently not in use. > Co-processors, useage domains and control domains are very > different things. > > In your case you have 4 co-processors (aka 2 CEC2C features). > > Each co-processor has domains 0 - 15. > > An lpar can have "control" over multiple domains (i.e. > administration.. > this becomes very important with Trusted Key Entry Workstations). > > A domain on a co-processor cannot be shared with multiple lpars. > > You might ... > - take 1 co-processor and assign (aka ONLINE) it to TEST. > Useage Domain 0, control domain 0. I did this for the TEST lpar and it worked. ICSF recognized the coprocessor and the SE showed it as online. > - take 3 co-processors and assign (aka ONLINE) them to PROD. > Useage Domain 1, control domain 1,0. Because I'm not concerned with sharing, I would think setting control and usage domain to 0,1,2,3 would be ok. But the SE will not let me configure the coprocessors online to PROD for some reason. ---------------------------------------------------------------------- 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
