We currently do not change system id's.
We do however have different IP addresses at DR now - that's fun.
Don't know the network folks's latest plans. Always changing.
They don't consider the impacts to the zVM and zOS support folks who
have to make it work.
  

-----Original Message-----
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
O'Brien, Dennis L
Sent: Friday, January 23, 2009 3:55 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Z/Linux CKD DASD migration from one DASD Subsystem to
another

Alan Altmark wrote:
>Convenience and Security are rarely bedfellows.  Hopefully you use a 
>different system ID when you're in DR.  Use it to qualify the 
>OFFLINE/ONLINE_AT_IPL so that you get the correct address range
depending
>whether you are at home or abroad.

I've seen a number of posts, either here or on IBMVM, that suggest
changing system ID's for DR.  We don't do that.  We have 18 VM systems.
They're all somewhat different, or we wouldn't have that many.  There is
far too much node-dependent code to introduce additional node names for
DR.  If the code all belonged to the systems area, we might be able to
manage it, but some of it is application code.  E.g.

Select
   When Wordpos(node,'NODE1 NODE2 NODEA NODEC') > 0
      Then Do ...
   When node = 'NODE4'
      Then Do ...
etc

There are valid reasons for this type of code.  Differences in the tape
or DR environments, for example.  These are hardware decisions over
which we have no control.  I can just imagine the havoc changing node
names would have caused when we had OfficeVision.  In the interest of
making the DR environment look as much like production as possible for
our users, we chose to keep the DR node names the same.  That decision
was made many years ago, and processes developed around it.  Changing it
now is off the table.  Even if we just starting to design DR, I don't
know if I'd go for changing node names.

I know this is the Linux list.  In a pure guest environment, this might
be less of an issue.  Some of our nodes have a CMS workload, where the
VM node name definitely matters.

                                                       Dennis O'Brien

39,650

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390
************************************************************
This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you are 
not the intended recipient, please notify the sender immediately by return 
e-mail, delete this communication and destroy all copies.
************************************************************

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to