Compatibility
This section describes considerations for compatibility between OS/390 Release 4
Security Server (RACF) and OS/390 Release 3 Security Server (RACF).
OpenEdition MVS
If you are an OpenEdition MVS user, be sure to review carefully the following
information on possible changes.

For Auditability of Superusers

If you are not already auditing the PROCESS class, you need to decide whether
you want to receive the audit records. If you do decide you wish to audit the
OpenEdition spawn service, issue SETROPTS LOGOPTIONS(xxxx(PROCESS)) to
obtain the SMF TYPE80 record ck_priv in order to audit superuser use. If you are
auditing the PROCESS class, you do not need to issue that command.
You need to change any programs reporting from the unloaded data if you want the
spawn audit information.

For Default USER/GROUP OpenEdition Segment

The existing type 317 relocate section appears on any SMF TYPE80 records
written by the RACF callable services for users running with any default
OpenEdition information.
You need to change any programs reporting from the unloaded data if you use this
support.
Program Control by System ID
If users are already allowed access through the standard access list, they must be
removed from these lists so the conditional access list entry is used. In-storage
program profiles must be refreshed with SETROPTS WHEN(PROGRAM)
REFRESH to activate the updated PROGRAM profiles.
RELEASE=2.4 Keyword on Macros
You should only specify RELEASE=2.4 and reassemble if you intend to use the
new keywords. If you use the new keywords, you need to run the program on an
OS/390 Release 4 system to get the expected results.
Chapter 4. Planning Considerations 23