IBM GC28-1920-01 prefix, a value, specify with the PREFIX keyword, sysname, the system, either

prefix	Is	a value	you	specify with the PREFIX keyword	on	the
	TARGET	command
sysname	Is	the system		name. This name must match the value	in	th
	CVTSNAME	field for the system it identifies.
ds_identity	Is	either	INMSG	or OUTMSG

The naming convention for the workspace data sets for remote connections

prefix.local_luname.remote_luname.ds_identity

where:

prefixIs a value you specify with the PREFIX keyword on the TARGET command

local_luname Is the LU name of the local node

remote_luname

Is

the LU name of the remote node

ds_identity

Is

either INMSG

or

OUTMSG

If

your

installation

has

configured

an

RRSF network,

you could

lose req

are in your existing workspace data sets when you

install multisystem R

support. To

avoid

losing

requests,

follow

these steps

before

you install

RRSF

node

support

on

a

system

in

an

RRSF network:

1.Warn users of this migration. Start this process at a time appropri installation. Pay particular attention to the effects of locking the R database (step 3). Updates to a locked RACF database are not all result in ABEND483 or ABEND485. SeeOS/390 Security Server (RACF)

System Programmer's Guidefor information on locking a database.

2. On

the system on which

you are

installing

multisystem

node support,

TARGET

DORMANT

commands

for

all

remote

nodes,

and wait

until

their

INMSG workspace data sets have drained. You can use

a

TARGET

LIST

command

for

each

specific

remote

node to

verify

that

the

INMSG fi

As

a

result

of

this

step:

ŸFuture requests from remote nodes are not received. They queue

OUTMSG files for this system on the remote nodes.

Ÿ Pending requests from remote nodes are processed before you loc RACF database.

3.Use the IRRUT400 utility to lock the RACF database. Specify PARM='LOCKINPUT' with no OUTDD statements in the JCL. The utility gives return code of 4, but locks the database. Locking the database pr

database from getting	out of synchronization with other RACF databas
RRSF network during the	install.

It is important to completely finish step 2 before locking the dat Otherwise, pending update requests already received from remote no result in abends, and could cause the out-of-sync condition that thi attempting to prevent.

4.Install RACF.

5.Stop the RACF subsystem address space.

If the INMSG and OUTMSG workspace data sets are empty at this tim workspace data sets can be allocated that follow the new naming con You can preallocate these data sets, or let RACF allocate them for

28 OS/390 V1R2.0 Security Server (RACF) Planning: Installation and Migration