IBM GC28-1920-01 manual RACF Diagnosis, Security, Server, On ORLANDO, Delete

5.Issue a TARGET command from the operator's console to define syste SYSTEM1 as the MAIN system for the multisystem node. (Issuing this command allows you to reconfigure the node to make SYSTEM2 the main system at some future time.)

prefixTARGET NODE(MIAMI1) SYSNAME(SYSTEM1) LOCAL MAIN OPERATIVE￿ PREFIX(...) PROTOCOL(...) WORKSPACE(...)

Add	this command to the		RACF parameter library	for SYSTEM2.
On ORLANDO:
1. If	MIAMI2	is the chosen destination of any		autodirected output
change this		destination	to be node MIAMI1. For	example:

SET AUTODIRECT(NOTIFY(FAILURES(MIAMI1.ADMIN))

OUTPUT(FAILURES(MIAMI1.ADMIN)))

All autodirected output and notifications are sent to the main sys multisystem node.

2. Issue	a TARGET	DORMANT	command from	the operator's			console		to	make
the connection with MIAMI2 dormant:
prefixTARGET NODE(MIAMI2) DORMANT
3. Ensure	that the	INMSG	and OUTMSG	workspace	data sets for node MI
are empty. Automatic command direction and					automatic			password		direc
should have been directed to MIAMI1. But					if	the		workspace		data
empty, use the RACF VSAM file browser utility,						IRRBRW00,			to	record
remaining	command	requests. (SeeOS/390		Security	Server		(RACF) Diagnosis

Guide and the RACJCL member of SYS1.SAMPLIB for information on IRRBRW00.)

Note: Rerun the remaining commands after you complete step 5.

4. Issue		a TARGET	DELETE	command from the operator's console to delete
RRSF	connections		with	MIAMI2:
prefixTARGET NODE(MIAMI2) DELETE
Update		the RACF parameter library to delete the existing TARGET c
for	RRSF	connections.

Another way you can do this step is to first make the updates parameter library, then stop and restart the RACF address space:

prefixSTOP

START subsystem-name,SUB=MSTR

5.Issue TARGET commands from the operator's console for the new multisystem node, MIAMI1:

prefixTARGET NODE(MIAMI1) DORMANT

prefixTARGET NODE(MIAMI1) SYSNAME(SYSTEM1) MAIN OPERATIVE

prefixTARGET NODE(MIAMI1) SYSNAME(SYSTEM2) OPERATIVE PREFIX(...) PROTOCOL(...) WORKSPACE(...)

Add these commands to the RACF parameter library for ORLANDO.

Remember to rerun remaining commands as noted in step 3.

Chapter 13. Scenarios63