IBM GC28-1920-01 manual Installation Considerations, Enabling RACF, Networks, Management, Server

Chapter 5. Installation Considerations

This chapter describes changes of interest to the system programmer OS/390 Release 2 Security Server (RACF):

ŸEnabling RACF

Ÿ Considerations for RRSF networks

Ÿ Virtual storage considerations

Ÿ Customer additions to the CDT

ŸTemplates

Enabling RACF

When

you install

OS/390

Release

2,

make

sure

that

RACF

is

enabled. If

RACF

initialization

does not complete,

message

IFA104I

is

issued,

and

not

provide

security

for

the

system.

At install time, to enable RACF,

an entry must existxx memberinthe IFAPRD

pointed

to

by

the

PROD=

parameter

inxx thememberIEASYSof

SYS1.PARMLIB.

If you order RACF as part of

the Security

Server

feature

in

OS/390

IFAPRD xx entry should look like this:

PRODUCT OWNER('IBM CORP')

NAME('OS/39ð')

FEATURENAME('Security Server')

ID(5645-ðð1)

VERSION(\)

RELEASE(\)

MOD(\)

STATE(ENABLED)

If

you

make

changes

to

this

member, you must re-IPL the system for

to take effect. RACF does not

respond

to

changes

made

via

the

MVS S

command.

For more information on enabling

and

disabling OS/390RACF,

sSecurity

Server

(RACF) System Programmer's Guide, or the program directory shipped with t

product. For

general

information

on

enabling

products,OS/390 MVS seeProduct

Management .

Considerations

for

RRSF

Networks

OS/390

Release

2

Security Server (RACF)

includes

support

for

multisystem

in RRSF

networks.

(For a

description

of

this support,

see “Multisystem

RRSF

Network”

on

page 9.)

This support

required

a

change

to

the

naming

convention

for

the remote sharing workspace data sets. The

naming

conve

the

workspace

data sets created on a

node

as a

result

of a

TARGE

command

is

now:

prefix.sysname.ds_identity

where:

 Copyright IBM

Corp.

1994,

1996

27