Preparing for configuration


(BMC.DB2.SPE2304)

Before configuring and running the BMC AMI DevOps container application, perform the following steps:

  1. Create partitioned data sets (PDSs).
    If they do not already exist, create PDSs with unique names on the mainframe for the following items:

    • CDL file
    • DDL file
    • Execution JCL
    • Analysis impact report
    • Worklist

    Also, create rollback PDSs with unique names on the mainframe for the following items:

    • CDL file
    • Execution JCL
    • Analysis impact report
    • Worklist

    Important

    •  Create PDSs with LRECL=80.
    • For PDSs that receive a large number of artifacts from pipelines or workflows, consider using a PDSE so that you do not exceed limits for the directory block.
  2. Customize the plug-in variables file. 
    In the plug-in variables file that we have provided, customize the following variable values.

    Important

    • Do not enclose the variable values in single or double quotation marks.
    • Comment out any variables in the plug-in variables file that you do not plan to use.
    • The default name of the plug-in variables file is AMI_DevOps.properties. The plug-in variables file can have any name, but the file name extension must be .properties.

    Variable type

    Variable

    SSL certificate validation

    • TSFLAG

    Limit settings

    (BMC.DB2.SPE2307)

    • maxlimit
    • dsrecalltime

    LPAR/Subsystem information

    • acctno
    • lpar1
    • dsnexit 
    • dsnload

    Installation information

    • rtehlq
    • usrhlq
    • proclib
    • joblib1
    • joblib2

    Schema Management

    • dopts
    • pofdsn

    Schema Standards

    • gudplan

    Data set names

    • ddlpds
    • cdlpds
    • wlpds
    • execpds
    • irpds

    Data set names for rollback

    • rbcdl
    • rbwl
    • rbexec
    • rbir

    GUID-47E5A770-A760-442A-9F5A-06872981813D-low.png

    For more information, view the Quick Course BMC AMI DevOps for Db2 - Configuring the AMI_DevOps.properties file.

    Tip

    For reference, see the sample plug-in variables file in Sample-plug-in-variables-file-AMI_DevOps-properties.

  3. Make sure that the plug-in variables file is available in the environment in which you run the deployment.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*