Planning

This section describes the prerequisites for using the BMC AMI DevOps for Db2 product.

• To use the product, make sure that you have the following products installed on your system:
  • IBM z/OS Management Facility (z/OSMF)
  • IBM z/OS JES2 or JES3 system
  • IBM Db2 12 for z/OS or later
  • Version 13.1.00 or later of BMC AMI Change Manager for Db2
  • Version 13.1.00 or later of BMC AMI Command Center for Db2
  • (BMC.DB2.SPE2407) JDK17 is supported for Jenkins.
  • One of the following CI/CD tools:
    • (BMC.DB2.SPE2407) The current version of Jenkins.
    • (BMC.DB2.SPE2304) The current version of Azure DevOps.
    • Version 20.10.17 and later of Docker is supported for BMC AMI DevOps for Db2 with Azure DevOps, GitHub Actions, and (BMC.DB2.SPE2504) GitLab CI/CD.
    • (BMC.DB2.SPE2307) The current version of GitHub Actions.
    • (BMC.DB2.SPE2504) The current version of GitLab CI/CD.

• Configure security authorization for z/OSMF
  For more information, see the IBM z/OS Management Facility Configuration Guide in the IBM documentation.

  Warning

  Important

  You might need to create authorizations for z/OSMF core functions. To create these authorizations:

  1. Use the IZUSEC job to set up the following accesses:
     • SERVAUTH resource class for CEA.CEATSO.TSOREQUEST
     • TSOPROC resource class for IZUFPROC
  2. Follow the procedure to use the default Language Environment MSGFILE of SYSOUT. For more information, see the section about IBM PI86429 in the IBM documentation.
• Create the required partitioned data sets (PDSs) on the mainframe.

• Customize the plug-in variables file.

  Warning

  Important

  For more information about how to create PDSs and customize plug-in variables file for Jenkins, see step 1 and 2 of the procedure to prepare for a project.

  For more information about how to create PDSs and customize plug-in variables file for Universal Connector, see step 1 and 2 of the procedure to Prepare for configuration.

• For each project, pipeline, or workflow, during configuration, specify the following details for the LPAR in the sysplex on which z/OSMF is running:
  • Mainframe IP address or host name
  • Port number for z/OSMF

       Use the following procedure to determine the IP address or host name and port number:

1. Identify the Db2 subsystem to which schema changes are applied.
2. Identify the LPAR and sysplex on which this Db2 subsystem resides.
3. Verify that z/OSMF is running on an LPAR in this sysplex.
4. Determine the IP address or host name for this LPAR.
5. Determine the port number for z/OSMF running on this LPAR.

• To use BMC AMI DevOps features in Jenkins pipelines, make sure that the following plug-ins are installed on Jenkins:
  • Pipeline Utility Steps
    This plug-in is a suite of plug-ins that supports implementing and integrating continuous delivery pipelines into Jenkins.
  • Pipeline: Build Step
    This plug-in is a component of the Pipeline Utility Steps plug-in. You must install this plug-in on Jenkins to use BMC AMI DevOps features in Declarative Pipelines using other jobs (projects).
• To use the step BMC AMI DevOps Common – Authentication (Credential Store), make sure that the following plug-ins are installed on Jenkins:
  • Credentials
    This plug-in allows you to store credentials in Jenkins.
  • Structs
    This is a library plugin for DSL plug-ins that need names for Jenkins objects.  This is a dependent plug-in for the Credentials plug-in.