FW: is there a way to automatically select a certain system config based on second level vs. first level ipls?

Thanks, Mike and Robert! That sounds perfect for our situation (and handy, too, for our later DR discussions)... Shannon Collinson shannon.collin...@suntrust.com Tel: 404.827.6070 Mobile: 404.642.1280 Fax: 404.581.1688 LEGAL DISCLAIMER The information transmitted is intended solely

is there a way to automatically select a certain system config based on second level vs. first level ipls?

We'd like to be able to switch between two sets of ipl-volumes (respack + spool + paging, I'd guess) to be able to switch between releases of the operating system. Of course, we'd hopefully only go one-way, but we'd want the ability to swap back. I was thinking we could set up the system config

Re: is there a way to automatically select a certain system config based on second level vs. first level ipls?

One of perhaps many possibilities: Include in the 2nd level userid directory entry something like: CPU 00 CPUID 00DEAF (where 00DEAF can be any hexadecimal cpu serial number, I just like DEAF because it's DEAF to the world. You your heximagination). Let's use an example of your production

Re: is there a way to automatically select a certain system config based on second level vs. first level ipls?

The CPOWNED list is exactly the place where I resort to: Imbed -SYSTEM- CPOWNED Where -SYSTEM- gets parsed as the nodeid of the running system. So make sure to include a PRODVM CPOWNED and 2NDLEVEL CPOWNED file there on the CFx disk. -- Jay Brenneman