I have multiple configuration files on my sysres for use in Standalone mo
de
or at our hotsite, etc. I found that the System_Identifier entry in the
system config file will set the GATEWAY name in CP. You can then use CP
QUERY GATEWAY and look for the entry whose OWNER = SYSTEM. That GATEWAY
name
will correspond to the System_Identifier in the system config file that w
as
used at IPL. This lets me have a name for production config on production
hardware, production config on hotsite hardware, standalone config on
production hardware, standalone config on hotsite hardware, etc. In OPERA
TOR
and AUTOLOG1, a gateway name of 'SYSPROG' starts very little and a name o
f
'SA-SYSP' exits as fast as possible.
In SA-SYS CONFIG on MAINT CF1
System_Identifier_Default SA-SYSP
System_Identifier 2086 xxxxxx SYSPROG
CP QUERY GATEWAY
Gateway: U-AOSS Owning Userid: SYSTEM
Gateway: DOEVM01 Owning Userid: AVS
/Tom Kern
On Thu, 25 Jan 2007 08:34:04 -0600, Mary Anne Link <[EMAIL PROTECTED]
M>
wrote:
>Does anyone have an autolog profile exec that contains some logic to aut
olog
>different servers based on what system you are on? We are trying to get
to a
>point where we can quickly copy the res pack to other systems, and, base
d on
>the system config fn specified on salipl, ipl a copy of that res pack to
>bring up different systems.
>
>Ideally what I'm looking for is a command that will retrieve the system
name
>(which I can't seem to find) and then I can start different linux guests
>based on that system name.
>
>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 th
ink
>of any snags in my plan?
>
>Thanks,
>Mary Anne (A VM newbie)
>========================
=========================
=======================
