Filter
Top Products
Chapter 5. Installation Considerations
This chapter describes changes of interest to the system programmer installing
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 it is not,
RACF initialization does not complete, message IFA104I is issued, and RACF does
not provide security for the system.
At install time, to enable RACF, an entry must exist in the IFAPRD
xx
member
pointed to by the PROD= parameter in the IEASYS
xx
member of SYS1.PARMLIB.
If you order RACF as part of the Security Server feature in OS/390 release 2, the
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 the changes
to take effect. RACF does not respond to changes made via the MVS SET PROD
command.
For more information on enabling and disabling RACF, see
OS/390 Security Server
(RACF) System Programmer's Guide
, or the program directory shipped with the
product. For general information on enabling products, see
OS/390 MVS Product
Management
.
Considerations for RRSF Networks
OS/390 Release 2 Security Server (RACF) includes support for multisystem nodes
in RRSF networks. (For a description of this support, see “Multisystem Nodes in an
RRSF Network” on page 9.) This support required a change to the naming
convention for the remote sharing workspace data sets. The naming convention for
the workspace data sets created on a node as a result of a TARGET LOCAL
command is now:
prefix.sysname.ds_identity
where:
Copyright IBM Corp. 1994, 1996 27