Creating and running apply requests

The tasks for initiating an apply request vary with the target database type.

Use the procedures in this section to:

  • Help you write apply requests that fit your requirements
  • Manage the requests that you create

You can create and save an apply request for Db2 in the same way that you write any batch job. You can use any editor to create and save an apply request. The job steps that you include in the apply request depend on the type of apply processing that you want to perform. Use the procedure in this section to create a basic apply request.

Related topics

The-Configuration

Defining-configurations

Specifying-restart-parameters

Data-set-and-file-names-in-configuration-files

Restarting-an-apply-request

Before you begin

Before you can run an apply request, the target tables must exist if you are using [ObjectMap] parameters. The High-speed Apply Engine load libraries and any libraries referenced in the STEPLIB DD statements must be APF-authorized.

You should also become familiar with the HLQ.DBSAMP library. This library contains a sample configuration file and apply request. HLQ represents a high-level qualifier that you specified when you installed High-speed Apply Engine.

For more information about apply requests, see Apply-requests.

To create an apply request for Db2

  1. Create a job that runs an apply request.One method of doing this is to use a sample apply request job as a template. (A sample job is stored in the APTSAMP member in the HLQ.DBSAMP library). If you use this template, copy the file, renaming it according to your site requirements. Edit the file with any standard editor.
  2. Edit the job statement to conform to your site requirements.
  3. Verify that the EXEC statement invokes APTBMAIN.
  4. Specify your configuration information. You can specify a single configuration file, multiple configuration files, or no configuration file.

    1. To specify a single configuration file, specify the name of your configuration file in the default DD statement SYSIN. For example:

      //HSAESQL  EXEC PGM=APTBMAIN,
      //         PARM='SSID=DBAT',REGION=0M
                       .
                       .
      //*
      //SYSIN    DD DISP=SHR,DSN=APT.CNFG.FILE(CONFIG)
    2. To specify multiple configuration files, specify the names of your configuration files in the default DD statement SYSIN (For example, see Sample apply request for mainframe targets (JCL)).

    3. To specify no configuration file, enter None as the value of the FileName (CFN) parameter within the PARM parameter of the EXEC statement in your JCL. For example:

      //APPLYSQL EXEC PGM=APTBMAIN,
      //         PARM='SSID=DBAT,CFN=NONE',REGION=0M

  5. Add any configuration overrides required for the request.You can specify the overrides within the PARM parameter of the EXEC statement, or with a separate DD statement that includes configuration sections. For example:

    //APPLYSQL EXEC PGM=APTBMAIN,
    //   PARM='SSID=DBAT,InputType=SQL,IFN=APT.INPUT.SQLFILE2'
  6. Save the job if you want to reuse it in the future.
  7. Run the job to start processing the apply request.

Verifying High-speed Apply Engine maintenance

In some situations, you might need to verify maintenance that has been applied to the High-speed Apply Engine. If an apply request does not complete successfully, you might need to provide this information to BMC Support.

Use one of the following methods to obtain maintenance information:

  • Run a normal apply request

    Examine the output of an apply request in your environment. Message BMCAPT0215 displays a list of the maintenance fixes that have been applied to the High-speed Apply Engine and its components. This method requires a connection to Db2.

  • Run a maintenance job

    Use the special EXEC statement parameter called MAINT. An apply request with this parameter prints information from the control sections (CSECT) that track maintenance applied to High-speed Apply Engine and its components. High-speed Apply Engine performs no other processing. You do not need a connection to Db2.

    Sample maintenance job for mainframe targets (JCL) shows sample JCL that you can modify to run a maintenance job. 

    //APTMAIN  JOB STATEMENT
    //*
    //APPLY    EXEC PGM=APTBMAIN,REGION=0M,
    //         PARM='MAINT'
    //STEPLIB  DD DISP=SHR,DSN=product.libraries
    //         DD DISP=SHR,DSN=DB2.DSNEXIT
    //         DD DISP=SHR,DSN=DB2.DSNLOAD
    //APTERR   DD SYSOUT=*
    //APTPRINT DD SYSOUT=*
    //

    Sample maintenance output shows the output information that you can use to verify maintenance.

    BMCAPT0000I High-speed Apply Engine V13.01.00                                                                              
    Copyright (c) 1999-2023 BMC Software, Inc. as an unpublished licensed work.  All rights reserved.              
    BMCAPT0001I Date: Thu Jan 06, 2022                                                                                         
    BMCAPT0215I MAINT: High-speed Apply Engine V13.01.00                                                                       
    BMCAPT0215I MAINT: NONE APPLIED
    BMCAPT0215I MAINT: SOLUTION COMMON CODE V13.01.00                                                                          
    BMCAPT0215I MAINT: BPJ1541  BPJ1713  BPJ1727  BPJ2211                                                                      
    BMCAPT0215I MAINT: BMCSORT ENGINE V02.04.01                                                                                
    BMCAPT0215I MAINT: BPJ0691  BPJ0718  BPJ0881  BPJ0922  BPJ0996  BPJ1164  BPJ1309                                           
    BMCAPT0215I MAINT: BPJ1386  BPJ1497  BPJ1594  BPJ1724  BPJ1809  BPJ1833  BPJ1891                                           
    BMCAPT0215I MAINT: BPJ1905  BPJ2109  BPJ2232  BPJ2297

 

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