On Thursday, 01/25/2007 at 08:34 CST, Mary Anne Link <[EMAIL PROTECTED]> wrote: > We are trying to get to a > point where we can quickly copy the res pack to other systems, and, based on > the system config fn specified on salipl, ipl a copy of that res pack to > bring up different systems.
You want to be a bit careful with IDENTIFY. The value it returns is based on CPUID and SYSTEM NETID. If the CPU id is not present in SYSTEM NETID, it will return the System_Identifier from SYSTEM CONFIG. So if you're going get IDENTIFY to change what it returns based on the fn on salipl, you can't use SYSTEM NETID. If you don't use RSCS, no big deal, but if you do, then you'll need to play games with SET CPUID and SYSTEM NETID for the users who need RSCS. (With no matching entry in SYSTEM NETID, IDENTIFY will return "VIA *"; SENDFILE, etc. won't work correctly.) > Also, aside from system config, the tcpip files (which use system name), the > autologs, and having to keep all users in the user direct, can anyone think > of any snags in my plan? Copying the res pack (IPL volume w/PARM disk and directory) to another system is fine, but what are you doing for the remaining volumes that comprise the system? Alan Altmark z/VM Development IBM Endicott
