Check the security profile for the Software Management task
Description
In z/OSMF V1R13 (prior to APAR PM73833), the deployment functions were provided in the Deployment task. In z/OSMF V2R1, the name of this task is changed to Software Management to reflect the software management functions that are provided in addition to the deployment functions.
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 your installation created a discrete profile to control access to the Deployment 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
If your installation used SAF Authorization Mode in z/OSMF V1R13 and used the following default, generic profile to control access to the Deployment task, no migration actions are required:
<safPrefix>.ZOSMF.SOFTWARE_DEPLOYMENT.**
If your installation chose not to use the generic profile and instead created a discrete profile to control access to the Deployment task, a migration action is required. For example, suppose your installation created the following profile to control access to the Deployment task in z/OSMF V1R13:
<safPrefix>.ZOSMF.SOFTWARE_DEPLOYMENT.DEPLOYMENT
Because the name changed in z/OSMF V2R1, your installation must create a generic profile like the default or a discrete profile like the following to control access to the Software Management task:
<safPrefix>.ZOSMF.SOFTWARE_DEPLOYMENT.SOFTWARE_MANAGEMENT
Reference information
For information about creating authorizations for z/OSMF plug-ins, see IBM z/OS Management Facility Configuration Guide.