Re: D/R Code
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 Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/4/07 5:04 PM, Fran Hensler [EMAIL PROTECTED] wrote: We have two FLEX-ES systems on opposite ends of the campus. The DR system does not have as many tape drives as the production system. The production system has a drive at 0591 but the DR system does not. In the AUTOLOG1 DIRECT I haveDEDICATE 0591 0591 When AUTOLOG1 starts up it does a CP Q V 0591 and if it doesn't exist I know I am on the DR machine. AUOTLOG1 also has write access to TCPMAINTs 198 disk. If I am not on the production machine then an EXEC on AUTOLOG1 changes the IP address in PROFILE TCPIP, DETACHES 198 and then AUTOLOGs TCPIP. If 0591 exists I know I am on the production machine so I just DETACH it and continue with the production startup. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: D/R Code
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 IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mary Anne Matyaz Sent: Friday, October 05, 2007 9:36 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: D/R Code 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 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 Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/4/07 5:04 PM, Fran Hensler [EMAIL PROTECTED] wrote: We have two FLEX-ES systems on opposite ends of the campus. The DR system does not have as many tape drives as the production system. The production system has a drive at 0591 but the DR system does not. In the AUTOLOG1 DIRECT I haveDEDICATE 0591 0591 When AUTOLOG1 starts up it does a CP Q V 0591 and if it doesn't exist I know I am on the DR machine. AUOTLOG1 also has write access to TCPMAINTs 198 disk. If I am not on the production machine then an EXEC on AUTOLOG1 changes the IP address in PROFILE TCPIP, DETACHES 198 and then AUTOLOGs TCPIP. If 0591 exists I know I am on the production machine so I just DETACH it and continue with the production startup. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
Re: D/R Code
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: IBMVM@LISTSERV.UARK.EDU 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. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Mary Anne Matyaz Sent: Friday, October 05, 2007 8:36 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: D/R Code 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 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 Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/4/07 5:04 PM, Fran Hensler [EMAIL PROTECTED] wrote: We have two FLEX-ES systems on opposite ends of the campus. The DR system does not have as many tape drives as the production system. The production system has a drive at 0591 but the DR system does not. In the AUTOLOG1 DIRECT I haveDEDICATE 0591 0591 When AUTOLOG1 starts up it does a CP Q V 0591 and if it doesn't exist I know I am on the DR machine. AUOTLOG1 also has write access to TCPMAINTs 198 disk. If I am not on the production machine then an EXEC on AUTOLOG1 changes the IP address in PROFILE TCPIP, DETACHES 198 and then AUTOLOGs TCPIP. If 0591 exists I know I am on the production machine so I just DETACH it and continue with the production startup. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock _ ella for Spam Control has removed 13244 VSE-List messages and set aside 12637 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
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. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Mary Anne Matyaz Sent: Friday, October 05, 2007 8:36 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: D/R Code 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] mailto:[EMAIL PROTECTED] wrote: 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 Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/4/07 5:04 PM, Fran Hensler [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: We have two FLEX-ES systems on opposite ends of the campus. The DR system does not have as many tape drives as the production system. The production system has a drive at 0591 but the DR system does not. In the AUTOLOG1 DIRECT I haveDEDICATE 0591 0591 When AUTOLOG1 starts up it does a CP Q V 0591 and if it doesn't exist I know I am on the DR machine. AUOTLOG1 also has write access to TCPMAINTs 198 disk. If I am not on the production machine then an EXEC on AUTOLOG1 changes the IP address in PROFILE TCPIP, DETACHES 198 and then AUTOLOGs TCPIP. If 0591 exists I know I am on the production machine so I just DETACH it and continue with the production startup. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock _ ella for Spam Control has removed 13244 VSE-List messages and set aside 12637 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com http://www.ellaforspam.com
Re: D/R Code
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 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 Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/4/07 5:04 PM, Fran Hensler [EMAIL PROTECTED] wrote: We have two FLEX-ES systems on opposite ends of the campus. The DR system does not have as many tape drives as the production system. The production system has a drive at 0591 but the DR system does not. In the AUTOLOG1 DIRECT I haveDEDICATE 0591 0591 When AUTOLOG1 starts up it does a CP Q V 0591 and if it doesn't exist I know I am on the DR machine. AUOTLOG1 also has write access to TCPMAINTs 198 disk. If I am not on the production machine then an EXEC on AUTOLOG1 changes the IP address in PROFILE TCPIP, DETACHES 198 and then AUTOLOGs TCPIP. If 0591 exists I know I am on the production machine so I just DETACH it and continue with the production startup. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: D/R Code
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: 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. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Mary Anne Matyaz Sent: Friday, October 05, 2007 8:36 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: D/R Code 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 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 Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/4/07 5:04 PM, Fran Hensler [EMAIL PROTECTED] wrote: We have two FLEX-ES systems on opposite ends of the campus. The DR system does not have as many tape drives as the production system. The production system has a drive at 0591 but the DR system does not. In the AUTOLOG1 DIRECT I haveDEDICATE 0591 0591 When AUTOLOG1 starts up it does a CP Q V 0591 and if it doesn't exist I know I am on the DR machine. AUOTLOG1 also has write access to TCPMAINTs 198 disk. If I am not on the production machine then an EXEC on AUTOLOG1 changes the IP address in PROFILE TCPIP, DETACHES 198 and then AUTOLOGs TCPIP. If 0591 exists I know I am on the production machine so I just DETACH it and continue with the production startup. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock ella for Spam Control has removed 13244 VSE-List messages and set aside 12637 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com
Re: D/R Code
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 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: D/R Code 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: 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. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Mary Anne Matyaz Sent: Friday, October 05, 2007 8:36 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: D/R Code 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] mailto:[EMAIL PROTECTED] wrote: 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 Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/4/07 5:04 PM, Fran Hensler [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: We have two FLEX-ES systems on opposite ends of the campus. The DR system does not have as many tape drives as the production system. The production system has a drive at 0591 but the DR system does not. In the AUTOLOG1 DIRECT I haveDEDICATE 0591 0591 When AUTOLOG1 starts up it does a CP Q V 0591 and if it doesn't exist I know I am on the DR machine. AUOTLOG1 also has write access to TCPMAINTs 198 disk. If I am not on the production machine then an EXEC on AUTOLOG1 changes the IP address in PROFILE TCPIP, DETACHES 198 and then AUTOLOGs TCPIP. If 0591 exists I know I am on the production machine so I just DETACH it and continue with the production startup. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock _ ella for Spam Control has removed 13244 VSE-List messages and set aside 12637 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com http://www.ellaforspam.com/ This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
Re: D/R Code
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 application folks write ;-) Otherwise ugly things might happen when you need to move the system to a new machine or so. When I was involved with this, I tried very hard to make people use functional checks only. So if your application needs to connect to TCPIP, check for TCPIP being present and not whether you're in a situation where TCPIP should not be present (assuming something else will arrange to run the alternate stack that prevents the real network to come up in D/R testing). But I think I lost that eventually, and we settled on something in the LOGMSG iirc. Rob
Re: D/R Code
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 enable/disable values. /Tom Kern /301-903-2211 On Fri, 5 Oct 2007 16:29:36 +0200, Rob van der Heij [EMAIL PROTECTED] w rote: 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 application folks write ;-) Otherwise ugly things might happen when you need to move the system to a new machine or so. When I was involved with this, I tried very hard to make people use functional checks only. So if your application needs to connect to TCPIP, check for TCPIP being present and not whether you're in a situation where TCPIP should not be present (assuming something else will arrange to run the alternate stack that prevents the real network to come up in D/R testing). But I think I lost that eventually, and we settled on something in the LOGMSG iirc. Rob =
Re: D/R Code
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.
Re: D/R Code
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 CPUID via SYSTEM_IDENTIFIER) - Permit it to be set by SALIPL screen - Permit it to be set by as a LOADPARM from the CP IPL command - Permit it to be set as a LOADPARM by CP SHUTDOWN REIPL Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Stracka, James (GTI) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 10/05/2007 08:49 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: D/R Code 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: IBMVM@LISTSERV.UARK.EDU 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. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Mary Anne Matyaz Sent: Friday, October 05, 2007 8:36 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: D/R Code 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 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 Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/4/07 5:04 PM, Fran Hensler [EMAIL PROTECTED] wrote: We have two FLEX-ES systems on opposite ends of the campus. The DR system does not have as many tape drives as the production system. The production system has a drive at 0591 but the DR system does not. In the AUTOLOG1 DIRECT I haveDEDICATE 0591 0591 When AUTOLOG1 starts up it does a CP Q V 0591 and if it doesn't exist I know I am on the DR machine. AUOTLOG1 also has write access to TCPMAINTs 198 disk. If I am not on the production machine then an EXEC on AUTOLOG1 changes the IP address in PROFILE TCPIP, DETACHES 198 and then AUTOLOGs TCPIP. If 0591 exists I know I am on the production machine so I just DETACH it and continue with the production startup. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock ella for Spam Control has removed 13244 VSE-List messages and set aside 12637 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/ . By messaging with Merrill Lynch you consent to the foregoing. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by
Re: D/R Code
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 - On Fri, 5 Oct 2007 07:54:08 -0500 Robert P. Nix said: 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 Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/4/07 5:04 PM, Fran Hensler [EMAIL PROTECTED] wrote: We have two FLEX-ES systems on opposite ends of the campus. The DR system does not have as many tape drives as the production system. The production system has a drive at 0591 but the DR system does not. In the AUTOLOG1 DIRECT I haveDEDICATE 0591 0591 When AUTOLOG1 starts up it does a CP Q V 0591 and if it doesn't exist I know I am on the DR machine. AUOTLOG1 also has write access to TCPMAINTs 198 disk. If I am not on the production machine then an EXEC on AUTOLOG1 changes the IP address in PROFILE TCPIP, DETACHES 198 and then AUTOLOGs TCPIP. If 0591 exists I know I am on the production machine so I just DETACH it and continue with the production startup. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
CSE: It's the little things that'll get ya...
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 best that I can tell, it should be. My test systems are VMTESTP and VMTESTG. The system config file (w/o comments or other non-contributing entries) contains: System_Identifier * 025A7E GRIZZLY System_Identifier * 045A6E POLAR System_Identifier * 01 VMTESTP System_Identifier * 02 VMTESTG System_Identifier_Default ZVMV5R30 GRIZZLY: Say System Grizzly, LPAR PENG, starting up... POLAR:Say System Polar, LPAR GENT, starting up... VMTESTG: Say System Sandbox GRIZZLY, starting up... VMTESTP: Say System Sandbox POLAR, starting up... ZVMV5R30: Say UNKNOWN CPUID, PLEASE CHECK CONFIGURATION POLAR: VMTESTP: ZVMV5R30: System_Residence, Checkpoint Volid 530RES From CYL 21 For 9 , Warmstart Volid 530RES From CYL 30 For 9 GRIZZLY: VMTESTG: System_Residence, Checkpoint Volid 530RES From CYL 1 For 9 , Warmstart Volid 530RES From CYL 10 For 9 POLAR: GRIZZLY: XSPOOL_SYSTEM Slot 1 POLAR , Communications_Userid PVM Share_Spool yes POLAR: GRIZZLY: XSPOOL_SYSTEM Slot 2 GRIZZLY , Communications_Userid PVM Share_Spool YES POLAR: GRIZZLY: XSPOOL_SYSTEM Slot 3 RESERVED POLAR: GRIZZLY: XSPOOL_SYSTEM Slot 4 RESERVED VMTESTP: VMTESTG: XSPOOL_SYSTEM Slot 1 RESERVED VMTESTP: VMTESTG: XSPOOL_SYSTEM Slot 2 RESERVED VMTESTP: VMTESTG: XSPOOL_SYSTEM SLOT 3 ZVMTESTP , Communications_Userid PVM Share_Spool yes VMTESTP: VMTESTG: XSPOOL_SYSTEM Slot 4 ZVMTESTG , Communications_Userid PVM Share_Spool YES XSPOOL_XLIST_INPUT JANUS GCS PVM TCPIP RSCS OPERATOR FTPSERVE XSPOOL_XLIST_INPUT PERFSVM EREP DISKACNT OPERSYMP OPERATNS XSPOOL_XLIST_INPUT DTCVSW1 DTCVSW2 XSPOOL_XLIST_OUTPUT JANUS GCS PVM TCPIP RSCS OPERATOR FTPSERVE XSPOOL_XLIST_OUTPUT PERFSVM EREP DISKACNT OPERSYMP OPERATNS XSPOOL_XLIST_OUTPUT DTCVSW1 DTCVSW2 VMTESTP: CP_Owned Slot 2 530SPL own VMTESTP: CP_Owned Slot 3 530PAG VMTESTP: CP_Owned Slot 4 RESERVED VMTESTP: CP_Owned Slot 5 RESERVED VMTESTP: CP_Owned Slot 6 RESERVED VMTESTP: CP_Owned Slot 7 RESERVED VMTESTP: CP_Owned Slot 8 RESERVED VMTESTP: CP_Owned Slot 9 RESERVED VMTESTP: CP_Owned Slot 10 53GSPL shared VMTESTP: CP_Owned Slot 11 RESERVED VMTESTP: CP_Owned Slot 12 RESERVED VMTESTP: CP_Owned Slot 13 RESERVED VMTESTP: CP_Owned Slot 14 RESERVED VMTESTP: CP_Owned Slot 15 RESERVED VMTESTP: CP_Owned Slot 16 RESERVED VMTESTP: CP_Owned Slot 17 RESERVED VMTESTP: CP_Owned Slot 18 RESERVED VMTESTP: CP_Owned Slot 19 RESERVED VMTESTP: CP_Owned Slot 20 RESERVED VMTESTG: CP_Owned Slot 2 530SPL shared VMTESTG: CP_Owned Slot 3 RESERVED VMTESTG: CP_Owned Slot 4 RESERVED VMTESTG: CP_Owned Slot 5 RESERVED VMTESTG: CP_Owned Slot 6 RESERVED VMTESTG: CP_Owned Slot 7 RESERVED VMTESTG: CP_Owned Slot 8 RESERVED VMTESTG: CP_Owned Slot 9 RESERVED VMTESTG: CP_Owned Slot 10 53GSPL own VMTESTG: CP_Owned Slot 11 53GPAG VMTESTG: CP_Owned Slot 12 RESERVED VMTESTG: CP_Owned Slot 13 RESERVED VMTESTG: CP_Owned Slot 14 RESERVED VMTESTG: CP_Owned Slot 15 RESERVED VMTESTG: CP_Owned Slot 16 RESERVED VMTESTG: CP_Owned Slot 17 RESERVED VMTESTG: CP_Owned Slot 18 RESERVED VMTESTG: CP_Owned Slot 19 RESERVED VMTESTG: CP_Owned Slot 20 RESERVED - The only difference I see between the vmtest setup and the production setup is in the xspool_system list, where the test systems are in slots 3 and 4, reserving 1 and 2. Both RSCS and PVM are set up with the local and remote names matching the system names, VMTESTP and VMTESTG. Both RSCS and PVM link up w/o problem, other than the CSE message above. So for the brave among you... What am I overlooking? -- .~.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.
