Any CP environment variable system needs to be initialized during system
IPL. A new SYSTEM CONFIG entry would be needed for initial variable names
and values. Again arbirary names with arbitrary string values. Through th
e
current SYSTEM CONFIG syntax, you could have different settings based on
different CPUID's. The benefit over the current situation would be that y
ou
could have a whole set of variables set rather than just one GATEWAY name
.
So for your home production system you could have settings for variables
A B
C D E, and for your home test system have the same values for A B, with
different values for C D E. At your DR TEST site, you could have just a
value for A that indicates some DR scenario, and your OPERATOR profile co
uld
inspect A and ask the operator if this is a DR TEST or a real DR and set
values for B C D E appropriately. All other SVMs, inpsect the value that
they use, if it doesn't exist, exit, if it does exist, do whatever.
/Tom Kern
/301-903-2211
On Fri, 5 Oct 2007 09:49:38 -0400, Stracka, James (GTI)
<[EMAIL PROTECTED]> wrote:
>Great, but you would like that to be set automatically somehow, not
>manually after each IPL.
>
> -----Original Message-----
> From: The IBM z/VM Operating System
> Subject: Re: D/R Code
> Personally I like the idea of being able set a CP system
>variable. CP SET SYSTEM VARIABLE 'variable name' 'variable data'.
> That way each installation could easily customize how they
>wanted to use the variables. Maybe even allow x-system variables.
>
