This step lists the requirements for running any BMC product workflow.
| |
|---|
Required IBM z/OSMF APARs and PTFs | - APAR PH61123 has fixed the following issue on z/OSMF:
THE WORKFLOW ZFS DATA SET IS NOT DESCRIBED IN THE IZUD-DATASETS VARIABLE DURING THE PERFORM WORKFLOWS STEP OF A DEPLOYMENT.
The following PTFs are available for APAR PH61123:- R314 PSY UI97242 (for z/OS 3.1)
- R254 PSY UI97243 (for z/OS 2.5)
- R244 PSY UI97248 (for z/OS 2.4)
- APAR PH57903 fixed the following issue on z/OSMF:
UNMOUNTING ZFS DATA SET FAILS AFTER THE WORKFLOW DEFINITION FILE IN IT HAS BEEN USED BY Z/OSMF WORKFLOWSThe following PTFs are available for APAR PH57903:- R317 PSY UI94885 (for z/OS 3.1)
- R257 PSY UI94886 (for z/OS 2.5)
|
Security requirements and considerations | - BPX.SUPERUSER authority (https://www.ibm.com/docs/en/zos/3.1.0?topic=uids-superuser-authority)
- The authority BPX.SUPERUSER is required only when deploying an SI or PSI containing USS files with extended attributes (APF, Program Control) for products such as BMC AMI Ops Insight or BMC AMI Ops Infrastructure. If you are deploying any BMC AMI Ops Monitor product PSIs via IBM z/OSMF, make sure that you have READ access to the BPX.SUPERUSER facility on their LPARs. For more information about the superuser authority, see the IBM documentation.
- For GIMUNZIP, switching to a superuser is optional. If a user is authorized, GIMUNZIP switches to superuser and UNIX updates are performed with UID=0. If the user is not authorized to switch to a superuser, GIMUNZIP performs as the current user identity. Running as the current user might be acceptable, depending on whether the UNIX files are unzipped and their attributes. For example, if any files need the APF attribute set, the current user ID is set to zero (UID=0). However, if no UNIX files require such attributes to be set, setting UID to zero is not required and you can unzip the files under the current user identity.
- To deploy the BMC AMI Ops Insight product via IBM z/OSMF, you must have the BPX.SUPERUSER permission.
- Common REST API (CRA) is included in the BMC AMI Common Code which is required by BMC AMI Ops Insight and BMC AMI Ops User Interface products. CRA requires APF, Program Control, and Share As attribute permissions for the product DLL. Therefore, BPX.SUPERUSER permission is a prerequisite for deploying BMC AMI Ops Common Code.
- The z/OSMF System variables are used with the BMC Common Repository. To access the z/OSMF System variables, you must fulfill the following requirements:
- READ access to resource class ZMFAPLA
- Resource name—<SAF-prefix>.ZOSMF.VARIABLES.SYSTEM.ADMIN
- Role—IZUADMIN
For more information about getting access to the z/OSMF system variables, see the IBM z/OS Management Facility Configuration Guide.
- To run the BMC Common Repository, authority to create temporary files and directories at root: /etc
|
Miscellaneous requirements and considerations | When a step runs JCL, z/OSMF requires the job output to determine if the step is completed successfully. Make sure that the JOB JCL you provide to z/OSMF includes a MSGCLASS defined to the held output queue so you can see the JOB messages. If the MSGCLASS does not refer to a held output queue, z/OSMF might not be able to determine if the step is completed successfully. If there was an error, z/OSMF might not be able to display the errors in the step output. |