Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see PACLOG for DB2 13.1.

Building PACLOG jobs

Building a PACLOG job involves creating JCL that includes the following:

  • A JOB statement
  • An EXEC statement that includes a utility parameter to specify the ID of the Db2 subsystem against which the job will run
  • DD statements that specify the PACLOG and Db2 load libraries
  • DD statements that specify various optional and required data sets

The following descriptions provide more details. For a sample of PACLOG JCL, see Sample-jobs.

JOB statement

The JOB statement starts with a job name and includes standard JOB statement parameters, such as accounting information and a run identifier.

EXEC statement

The EXEC statement has the following format:

//STEP1 EXEC PGM=ALMMAIN,PARM=’<ssid>,ARMOPTS=<optionSet>’,REGION=0M

The parameters and values are as follows:

  • PGM=ALMMAIN specifies the processing module for PACLOG.
  • PARM specifies a single utility parameter, ssid, which is the ID of the Db2 subsystem against which the job will run.
  • For ARMOPTS, the variable optionSet is the name of an XML file that contains the product's configuration option values. The default option set is ARM$OPTS.
  • REGION=0M specifies zero megabytes for the region size. For PACLOG operations, REGION=3M is sufficient.

STEPLIB DD statement

The STEPLIB DD statement optionally identifies the PACLOG and Db2 load libraries that you want to use.

Example
//STEPLIB   DD DISP=SHR,DSN=BMCALM.TEST.OVERRIDE1
//          DD DISP=SHR,DSN=BMCALM.TEST.DBLINK
//          DD DISP=SHR,DSN=BMCALM.TEST.XXLINK
//          DD DISP=SHR,DSN=BMCALM.TEST.BBLINK
//          DD DISP=SHR,DSN=SYS3.DECI.DSNEXIT
//          DD DISP=SHR,DSN=CSGI.DB2V81M.DSNLOAD

Specifying the PACLOG data set DD statements

This topic describes the data sets that PACLOG uses.

Each data set is specified by a ddname (data definition name). You must specify all required data sets in the JCL.

Important

You do not need to specify DD statements for the input archive log data sets or the output copy data sets. PACLOG dynamically allocates these data sets.

  • (Required) ALMIN

    The input data set that contains one or more control statements. Attributes for this data set must be fixed-length records with a length of 80 (RECFM=F or FB, LRECL=80).

  • (Required) ALMPRINT

    The output for messages that are returned from PACLOG. PACLOG also echoes the contents of the ALMIN data set in the ALMPRINT output. ALMPRINT can be allocated to SYSOUT or to a data set with a data control block (DCB) of LRECL=121, RECFM=VBA.

  • (Required) ALMOPTS

    PACLOG reads the configuration options from the option set that the ARMOPTS parameter of the EXEC statement specifies. If you do not specify a value for that parameter, PACLOG uses the default option set (ARM$OPTS). You can temporarily override one or more configuration options by using the following ARMOPTS DD statement:

    //ARMOPTS DD

    ssid.
    configurationOption=value
    /*

Important

PACLOG and BMC AMI Recovery Manager for Db2 share the options file. If BMC AMI Recovery Manager is already installed on this subsystem, PACLOG should use the same data set as that used by BMC AMI Recovery Manager. The options file is common to all Db2 subsystems and contains the following information:

  • Names of the archive history file
  • Time stamps for each Db2 subsystem on which PACLOG is installed
  • Name of the work unit which is common to all subsystems
  • Bootstrap data set (BSDS)
  • Production DSN load library for Db2

  • (Required) ALMMSGS

    The PACLOG messages data set created during installation with the default name of hilvl.ALM.DBCNTL(ALMMSGS). The data set must be allocated with DISP=SHR.

  • (Optional) BMCERROR

    The output for compiler run time errors. If compiler errors are detected and BMCERROR is not present in the JCL, the errors are printed in the JES log. The data set can be allocated to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VBA.

  • (Optional) SYSUT1

    The BSDS (either BSDS01 or BSDS02) for the subsystem named in the EXEC statement. For example //SYSUT1 DD DISP=SHR,DSN=DB21CAT.BSDS01. If it is not specified, PACLOG gets the BSDS name from the control options and dynamically allocates the BSDS.

  • (Optional) ALMLSTAT

    A listing of the total number of records in the log for each record type. The data set can be allocated to SYSOUT or to a data set with a DCB of LRECL=133, RECFM=FBA.

  • (Optional) ALMOSTAT

    A listing of the total number of records in the log for each Db2 object. The data set can be allocated to SYSOUT or to a data set with a DCB of LRECL=133, RECFM=FBA.

  • (Required) ALMLIST1

    A listing of local primary archive log data sets that have been processed. The data set can be allocated to SYSOUT or to a data set with a DCB of LRECL=133, RECFM=FBA.

  • (Required) ALMLIST2

    A listing of local secondary archive log data sets that have been processed. The data set can be allocated to SYSOUT or to a data set with a DCB of LRECL=133, RECFM=FBA.

  • (Optional) ALMLIST3

    A listing of offsite archive log data sets for which the primary offsite copy was processed. The data set can be allocated to SYSOUT or to a data set with a DCB of LRECL=133, RECFM=FBA.

  • (Optional) ALMLIST4

    A listing of offsite archive log data sets for which the secondary offsite copy was processed. The data set can be allocated to SYSOUT or to a data set with a DCB of LRECL=133, RECFM=FBA.

  • (Required) ALMXPIRE

    A listing of all expired archive log data sets (those archive log data sets found in the archive history file but which no longer exist in the BSDS). The data set can be allocated to SYSOUT or to a data set with a DCB of LRECL=133, RECFM=FBA.

Important

Data sets that are no longer represented in the BSDS are deleted automatically from the archive history file by PACLOG. However, PACLOG does not delete the physical data set.

 

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