Remove the APF authorization for SYS1.MIGLIB(AMATERSE)
Description
Beginning in z/OSMF V2R1, the Incident Log task no longer requires that your SYS1.MIGLIB data set be APF-authorized. If no other programs or functions on your system require SYS1.MIGLIB to be APF-authorized, you can remove this authorization when you are satisfied with z/OSMF V2R1, and have no plans to fall back to an earlier release. Otherwise, leave this authorization in place.
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 the only reason you had APF authorized SYS1.MIGLIB was for the Incident Log task. |
| 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
APF authorizations are defined in the PROGxx member of SYS1.PARMLIB, if your site follows IBM recommendations. If you added SYS1.MIGLIB to the APF list for z/OSMF or the Incident Log task, it is recommended that you remove the explicit authorization. To do so, locate the appropriate PROGxx member and edit it to remove the APF ADD statement associated with SYS1.MIGLIB.
Reference information
For information about configuring z/OSMF, see IBM z/OS Management Facility Configuration Guide.