Review the SAF profile prefix
Description
Does your security product use the SAF profile prefix BBNBASE for z/OSMF resources? If so, be aware of the following changes, which occurred with z/OSMF V2R1.
- In previous releases, the configuration variable IZU_WAS_PROFILE_PREFIX was used to identify the WebSphere® SAF profile prefix, which was BBNBASE by default. With the removal of IBM® WebSphere Application Server OEM Edition for z/OS® in z/OSMF V2R1, this variable is no longer specified.
- In z/OSMF V2R1, the configuration variable IZU_SAF_PROFILE_PREFIX is added. Use this value to specify the SAF profile prefix for a z/OSMF. By default, the prefix is IZUDFLT.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | z/OSMF |
|---|---|
| When change was introduced: | z/OS V2R1. |
| Applies to migration from: | z/OS V1R13. |
| Timing: | Before installing z/OS V2R2. |
| Is the migration action required? | Yes, if you want to use the current defaults. |
| Target system hardware requirements: | None. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | None. |
| System impacts: | None. |
| Related IBM Health Checker for z/OS check: | None. |
Steps to take
If your installation is migrating from an earlier release of z/OSMF, it is recommended that you review the use of the BBNBASE prefix and determine whether your security product definitions for z/OSMF should be revised to use the new prefix IZUDFLT.
Tip: To
identify all of the affected profiles in a RACF database, you can
use this RACF command: SEARCH ALL CLASS(ZMFAPLA) FILTER(BBNBASE.**).
Reference information
For information about configuring z/OSMF, see IBM z/OS Management Facility Configuration Guide.