The code I use is: /* Identify which system we're running on */ 'Pipe CP Q GATEWAY' , '| Specs word 2 1' , '| Var SYSNAME'
Fairly concise and seems to cover most of the possibilities. We run a CSE complex from a single SYSRES, so the system IDs are vastly important. AUTOLOG1 checks, and performs differently on the individual systems, and various other home-grown tools also have system-specific behavior. Our SYSTEM CONFIG accounts for the two paired production LPARs, two paired test systems, and an ³other² to catch any additional CPUids that might fall our way.... Such as a disaster recovery site. -- .~. Robert P. Nix Mayo Foundation /V\ RO-OE-5-55 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ ----- "In theory, theory and practice are the same, but ³Join the story... Ride Ural.² in practice, theory and practice are different." On 10/4/07 5:42 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > How about having the AUTOLOGx userid's PROFILE EXEC issue a 'CP QUERY USERID > AUTOLOGx' command, parse the output for the system id you're running on, and > test whether you're running on your normal system or another (disaster > recovery) system and act accordingly.
