That seems a lot of work, when you could just ask the system who it is, and
set the system's name based on its serial number.
On the TCPIP front, again, you can just have two config files w/ the system
name as the FN, and be done with it. No editing at startup.
--
.~.Robert P. Nix
That is why we have our users run an exec that tests the CPUID and
System Configuration file name. You need to distinguish among: Normal
production, Test CNR and Production CNR. We want it to be completely
automated once the system is IPLed.
-Original Message-
From: The
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
[mailto:[EMAIL PROTECTED] On Behalf Of Huegel, Thomas
Sent: Friday, October 05, 2007 9:43 AM
To:
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.
-Original Message-
From: The IBM z/VM
We run a lot of things off of the system name, so it needs to be the same,
whether we are on processor A, processor B as real dr or processor B as test
DR.
MA
On 10/5/07, RPN01 [EMAIL PROTECTED] wrote:
That seems a lot of work, when you could just ask the system who it is,
and
set the
How about a CP SET/QUERY UPSI like they have in DOS :-)
Huegel, Thomas [EMAIL PROTECTED]
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
10/05/2007 09:43 AM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re:
Wow, the UPSI switch in DOS JCL! I have not used that since 1976. That
brings back some memories. Thanks
-Original Message-
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday, October 05, 2007 9:50 AM
Following this thread, it looks like I am the only one who has
concerns about code in the system that will distinguish between
production, DR (and maybe even DR test). Most certainly you want such
checks only in your own code (which has no errors and does not need
testing) and not in the code that
I don't think this would be for application level usage but only for syst
em
initialaztion, SVM configuration, etc, before real users/apps get started
.
I don't know if I would want a SAS covering exec to query a system variab
le
to see if it should run, but a SAS SVM should check its PRODUCT
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
IMHO, such a command needs to be set in many ways, including but not
limited to:
- Permit it to be set as an authorized/restricted CP command (perhaps
permitting a limited number of Privclass G SET commands for apps to
use?)
- Permit it to be set by the SYSTEM CONFIG file (perhaps based on
Robert -
No, it's not a lot of work. it's all automatic thru one EXEC on
AUTOLOG1. No manual intervention of any kind.
My DR FLEX-ES system has the same serial number as my production
system so checking the CPUID is not an option.
/Fran
I¹m in the process of building our z/VM 5.3 systems, and I think I¹m down to
the last hurdle I can¹t get CSE to fire up across PVM. The message I¹m
getting in PVM is:
DVMISG864E CSE is not authorized
The description of the message says that CSE is not available or not set up,
but, to the
13 matches
Mail list logo
