Installation requirements

PSI storage requirements

• You must enable multi-volume storage because product downloads can be large. The file definitions require extended attributes (EAs).
• To download the BMC product PSI files, the receiving z/FS file system must have the VSAM data set allocated with the EA attribute and storage of 4 GB or more. Some BMC products require more than 4 GB of space. Therefore, specify DATACLAS with the extended attribute (for example, DATACLAS(EA)).

Required IBM APARs

Make sure that you apply the following APAR fixes:

DigiCert Global Root G2 certificate

Before downloading your BMC product PSIs, make sure that you have obtained the DigiCert Global Root G2 certificate. This certificate is required if you are downloading the PSI files directly from a download server to the z/OSMF host system.

1. Navigate to https://www.digicert.com/digicert-root-certificates.htm and download the DigiCert Global Root G2 certificate.
2. Add the certificate to either the Java truststore or a RACF key ring.
   By default, z/OSMF uses the Java truststore. You can update this to the RACF key ring that contains the DigiCert Global Root G2 certificate, or *AUTH*/* to search all available certificates.

BPX.SUPERUSER authority 

• The BPX.SUPERUSER authority is required only when you deploy 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.
• Make sure that you can create directories in the USS path that is specified in the IZUPRMxx TEMP_DIR value.
• For GIMUNZIP, switching to 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 on 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) requires APF, Program Control, and Share As attribute permissions for the product DLL. 

Read access to z/OSMF system variables

Make sure that you have READ access to read the z/OSMF system variables. 

To provide the required access, an administrator can perform one of the following tasks. For more information, see IBM z/OS Management Facility Programming Guide.

• Provide direct access to a resource class

  Example

  <ResourceClass> ZMFAPLA
  
  <RresourceName> <SAF-prefix>.ZOSMF.VARIABLES.SYSTEM.ADMIN
  
  <UserWhoNeedsAccess> IZUADMIN <It must be a role.>
  
  <TypeOfAccess> READ
  
  <Description> Allows the user to access the system variables in the systems task.

• Add a user to the group
  Provide permission to the z/OSMF administrator group to modify or delete system variables by using the systems task or z/OSMF REST service. 

  Example

  PERMIT IZUDFLT.ZOSMF.VARIABLES.SYSTEM.ADMIN +

  CLASS(ZMFAPLA) ID(IZUADMIN) ACCESS(READ)

   

Diagnose job failures

When you use IBM z/OSMF, it is crucial to diagnose potential job failures. To do so, make sure that the JOB JCL that you provide to z/OSMF includes an MSGCLASS with held output queue so that you can view the JOB messages and detect any errors. If the z/OSMF Job output is not held, you cannot see these errors. After you provide the JOB Card information to z/OSMF, it is retained for subsequent JOBs.