Building the ARMBGNR JCL

ARMBGEN is followed by a step that conditionally executes the ARMBGNR program to copy the JCL that is created in ISPFILE to its final destination.

ARMBGNR is used instead of IEBGENER because it provides ENQ/DEQ (enqueue/dequeue) support when copying data sets.

Building your own ARMBGNR job involves creating JCL that includes the following statements:

Related topics

ARMBGEN—Backup and recovery JCL

BMC-AMI-Recovery-Manager-batch-programs

  • An EXEC statement
  • Data definition (DD) statements that specify the use of the following libraries and data sets:
    • BMC AMI Recovery Manager and Db2 load libraries
    • Input data sets
    • Output data sets

EXEC statement for ARMBGNR

The EXEC statement has the following format:

//ARM00003 EXEC PGM=ARMBGNR,COND=(4,LT),PARM='MEMBER'
//              REGION=0M

The COND parameter ensures that the step will run only if the previous ARMBGEN step has been completed with a condition code of 4 or less.

The EXEC statement should include the REGION parameter that specifies the amount of virtual storage that the job requires.

We recommend that you specify REGION=0M to make the amount of virtual storage needed to run the job automatically available when the ARMBGNR job is executed. If REGION=0M is not allowed by your organization, specify REGION=4M.

The MEMBER parameter is optional and causes each generated job to be copied into separate members. This option only works for certain types of job streams and might impact performance. For more information, see Separating jobs from a multi-job batch job stream.

STEPLIB DD statement for the ARMBGNR JCL

The STEPLIB DD statement identifies the BMC AMI Recovery Manager load library that you want ARMBGEN to use.

Example
//STEPLIB DD DISP=SHR,DSN=PRODUCT.LOAD.LIBS
// DD DISP=SHR,DSN=DSNEXIT
// DD DISP=SHR,DSN=DSNLOAD

ARMBGNR data set DD statements

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

  • (Required) ARMPRINT

    The output for messages returned from BMC AMI Recovery Manager. BMC AMI Recovery Manager also echoes the contents of the ARMIN data set in the ARMPRINT output. You may allocate ARMPRINT to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VB.

  • (Required) ARMMSGS

    The BMC AMI Recovery Manager messages data set created during BMC AMI Recovery Manager installation with the default name of hilvl.RMGR.ARMCNTL(ARMMSGS). You must allocate the data set with DISP=SHR.

  • (Optional) ARMERROR

    The output for compiler run time errors. If compiler errors are detected and ARMERROR is not present in the JCL, the errors are printed in the JES log. You may allocate the data set to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VB.

  • (Required) SYSUT1

    The temporary sequential data set (PS) is referenced in the ARMBGEN step with the ISPFILE DD statement.

  • (Required) SYSUT2

    Contains the backup or recovery JCL that is created by ARMBGEN. The data set should be LRECL=80,RECFM=FB, BLKSIZE with space sufficient to hold the generated JCL. You may allocate the data set to SYSOUT.

  • (Optional) SYSUT3

    The temporary PDS that is referenced in the ARMBGEN step with the ISPBKUP DD statement for mirrored systems.

  • (Optional) SYSUT4

    Contains the alternate recovery JCL that is created by ARMBGEN for mirrored systems. The data set should be LRECL=80,RECFM=FB, BLKSIZE with space sufficient to hold the generated JCL. You may allocate the data set to SYSOUT.

 

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