IBM GC28-1920-01 Server User Manual


 
2. Issue TARGET DORMANT commands from the operator's console to make all
RRSF conversations dormant:
prefixTARGET NODE(MIAMI1) DORMANT
prefixTARGET NODE(ORLANDO) DORMANT
3. Issue a TARGET command from the operator's console to make MIAMI1 the
main system on the new multisystem node MIAMI1. The old node name is
used for the new multisystem node because the existing RRSFDATA profiles
on node ORLANDO already use this node name for all automatic command
direction, automatic password direction, and RACLINK PWSYNC updates.
prefixTARGET NODE(MIAMI1) SYSNAME(SYSTEM1) LOCAL MAIN OPERATIVE
Update the corresponding command in the RACF parameter library, adding the
MAIN and SYSNAME keywords, so that the updated command will be
executed if the address space is recycled or the system is re-IPLed.
4. Issue a TARGET command from the operator's console to make MIAMI2 a
non-main system on the new multisystem node MIAMI1.
prefixTARGET NODE(MIAMI2) SYSNAME(SYSTEM2) LOCAL OPERATIVE
Add the corresponding command to the RACF parameter library, adding
SYSNAME keyword, so that the command will be executed if the address
space is recycled or the system is re-IPLed.
On MIAMI2:
1. To ensure that RACF activity is stopped, take down TSO/E and JES. This
action prevents MIAMI2 from updating the RACF database without sending the
updates to ORLANDO's RACF database.
2. Issue TARGET DORMANT commands from the operator's console to make all
RRSF connections dormant:
prefixTARGET NODE(MIAMI2) DORMANT
prefixTARGET NODE(ORLANDO) DORMANT
3. Issue TARGET DELETE commands from the operator's console to delete all
RRSF connections:
prefixTARGET NODE(ORLANDO) DELETE
prefixTARGET NODE(MIAMI2) DELETE
Update the RACF parameter library to delete the existing TARGET commands
for RRSF connections.
Another way you can do this step is to first make the updates to the RACF
parameter library, then stop and restart the RACF address space:
prefixSTOP
START subsystem-name,SUB=MSTR
4. Issue a TARGET command from the operator's console to define MIAMI2 as a
member system of the new multisystem node MIAMI1:
prefixTARGET NODE(MIAMI1) SYSNAME(SYSTEM2) LOCAL OPERATIVE
PREFIX(...) PROTOCOL(...) WORKSPACE(...)
The system that was originally single-system RRSF node MIAMI2 is now
system SYSTEM2 of multisystem node MIAMI1. Remember that this system
name, SYSTEM2, must match the CVTSNAME for the system. Also add this
command to the RACF parameter library for SYSTEM2.
62 OS/390 V1R2.0 Security Server (RACF) Planning: Installation and Migration