Why should changing the SYSTEM NETID on 190 have to be disruptive? Make
the change to that file only and do a SAVESYS CMS. To keep things in
step, copy the new SYSTEM NETID to 490 with OLDD. Anything that's using
SYSTEM NETID will still be seeing the "old" info but that old file
relates to the system in use at the moment.
Jim
On 8/12/2010 2:40 PM, David Boyes wrote:
Would this be done with the SYSTEM_IDENTIFIER statement in the SYSTEM CON=
FIG=20
For the SYSTEM CONFIG changes, yes. for SYSTEM NETID, you need to make the =
changes on MAINT 490 and then DDR 490 to 190. Note: disruptive, so do durin=
g a maintenance window.=20
and if so, how do I find my current model and cpuid?
Looks like the 'q cupid' will give it to me.
Yep. Read the notes in the CP Commands manual.=20
Note that multiple CPUIDs can map to the same node id in the case where you=
could end up on one of several CECs at the recovery site. =
--
James Bohnsack
(972) 596-6377 home/office
(972) 342-5823 cell
