Filter
Top Products
Chapter 4. Planning Considerations
This chapter describes the following high-level planning considerations for
customers upgrading to Security Server (RACF) Release 2 from Security Server
(RACF) Release 1:
Migration strategy
Migration paths
Hardware requirements
Software requirements
Compatibility
Migration Strategy
The recommended steps for migrating to a new release of RACF are:
1. Become familiar with the release documentation.
2. Develop a migration plan for your installation.
3. Install the product using the program directory shipped with the product.
4. Use the new release before initializing major new function.
5. Customize the new function for your installation.
6. Exercise the new function.
Migration Paths for OS/390 Release 2 Security Server (RACF)
From OS/390 Release 1 Security Server (RACF) or RACF 2.2
If you are an OS/390 Release 1 Security Server (RACF) or RACF 2.2
customer, you can migrate to OS/390 Release 2 Security Server (RACF) if you
meet the OS/390 release requirements and the other software requirements.
(OS/390 Release 1 Security Server (RACF) and RACF 2.2 are functionally
equivalent.)
From RACF 1.9.2 or RACF 2.1
If you are a RACF 1.9.2 or 2.1 customer, you can migrate to OS/390 Release 2
Security Server (RACF) if you meet the OS/390 release requirements and the
other software requirements. If you have RACF 2.1 installed, in addition to this
book you should read:
–
OS/390 Security Server (RACF) Planning: Installation and Migration
for
OS/390 Release 1.
If you have RACF 1.9.2 installed, in addition to this book you should read:
–
OS/390 Security Server (RACF) Planning: Installation and Migration
for
OS/390 Release 1, and
–
RACF Planning: Installation and Migration
for RACF 2.1.
From RACF 1.9
If you are a RACF 1.9 customer, you can migrate to OS/390 Release 2
Security Server (RACF) if you are running with the restructured database and
meet the OS/390 release requirements and the other software requirements. If
your database is not restructured, you must restructure it and perform
appropriate testing of any installation-supplied code that uses ICHEINTY or
Copyright IBM Corp. 1994, 1996 23