Howdy all.. Yep that is the way I set it up (back in the day of the improper fraction) <vbg>.
I agree with Mark. The reality of the crypto domains is that they are a planning item. Just like memory on the system. Unlike memory, there is additional consideration during DR of populating the domain as a one-time (well each time there is a new symmetric/asymmetric master key) setup (if you have a dedicated DR site/hardware) or an every-time setup. I had complained in the past that the re-assigning of domains was an IPL-only procedure which is a bit painful if you get it wrong or wanted to change it in a demanding production shop. If you are heading down the z10 path, then there is some relief there. Additionally, keeping the same domain makes TKE operations easier. I personally haven't seen a good case for running multiple domains on an LPAR... but I am sure that someone out there can come up with a scenario that would justify it. The simpler you keep the configuration the better off you'll be. There are lots of fairly complicated items for encryption services and no need to make it any harder on yourself than it has to be. Rob Schramm Sirius Computer Solutions <snippage> ---------------------------------------------------------------------- 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
