Building the ARMBGRP JCL

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

JOB statement for ARMBGRP

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

The JOB statement should include the REGION parameter that specifies the amount of virtual storage that the job requires. If you omit the REGION parameter from the JOB statement, you can include it in the EXEC statement.

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

EXEC statement for ARMBGRP

The EXEC statement has the following format:

The variable ssid is the Db2 subsystem or object set attach name where the BMC AMI Recovery Manager object sets reside. If you do not provide a subsystem ID, the program uses the subsystem ID indicated in the DSNHDECP module found in the STEPLIB or link list.

The variable optionSet is the name of a PDS member in the CNTL file that contains all of the product’s configuration option values. The default option set for BMC AMI Recovery Manager is ARM$OPTS.

STEPLIB DD statement for ARMBGRP

The STEPLIB DD statement identifies the BMC AMI Recovery Manager load library and Db2 load libraries that you want ARMBGRP to use. See the following example:

ARMBGRP data set DD statements

ARMBGRP 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) 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). The data set must be allocated with DISP=SHR.

• (Optional) ARMOPTS

  The configuration options are read from the option set named in the EXEC statement parameters (PARM=). If an option set name is not specified there, ARM$OPTS is used as the default option set name.

  You can temporarily override one or more configuration options using the following ARMOPTS DD statement:

  //ARMOPTS  DD *
  ssid.configurationOption=value
  /*

• (required) ARMPRINT

  The output for messages that are returned from BMC AMI Recovery Manager. BMC AMI Recovery Manager also echoes the contents of the ARMIN data set in the ARMPRINT output. ARMPRINT may be allocated to SYSOUT or to a data set with a data control block (DCB) of LRECL=121, RECFM=VB.

  The following figure shows sample ARMPRINT for the EXPORT OBJECTSET command with a wildcard pattern:

  EXPORT OBJECTSET PUBLIC.Q187*;                        
  BMC80591I PROCESSING OBJECTSET PUBLIC.Q1876526        
  BMC80591I PROCESSING OBJECTSET PUBLIC.Q1878348        
  BMC80591I PROCESSING OBJECTSET PUBLIC.Q1878802        
  BMC80591I PROCESSING OBJECTSET PUBLIC.Q1878802_IX     
  BMC80591I PROCESSING OBJECTSET PUBLIC.Q1878802_IXONLY
  BMC80570I COMMAND COMPLETE RC = 0

• (required) 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. This data set might be allocated to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VB.

• (optional) ARMEXPRT

  This data set to which CREATE OBJECTSET syntax for one or more data sets is written. The ARMEXPRT data set is required for using the EXPORT OBJECTSET or MIGRATE_TO_OBJECTSET ssid commands. This data set can be either sequential or a partitioned data set (PDS). If it is a PDS, you must specify the member name. Attributes for this data set must be fixed-length records, with a length of 80 (RECFM=F or FB, LRECL=80).

• (required) ARMIN

  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).

• (optional) ARMOBJS

  The output for the Object Set Object report. This data set might be allocated to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VB.

• (optional) ARMAUTH

  The output for the Object Set Authorization report. This data set might be allocated to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VB.

• (optional) ARMDEFN

  The output for the Object Set Definition Report. This data set might be allocated to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VB.

• (optional) ARMRCVR

  The output for the Recover Utility Options Report. This data set might be allocated to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VB.

• (optional) ARMCOPY

  The output for the Copy Utility Options Report. This data set might be allocated to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VB.

• (optional) ARMQUERY

  The output for query functions. This data set might be allocated to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VB.

• (optional) ARMRENAM

  The output data set that stores the new and old object set names when the RENAME command is used. This data set might be allocated to SYSOUT or to a data set with a DCB of LRECL=121, RECFM=VB.

• (required for creating object sets with user-defined SQL) ARMSQL

  The input for object sets created with user-defined SQL. Attributes for this data set must be fixed length records, with a length of 80 (RECFM=F or FB, LRECL=80). However, SQL syntax is limited to the first 72 bytes.

  The following example of how you can set up ARMSQL is taken from the ARMBGRP member in the .ARMSAMP data set that was created during installation:

  //* FILE USED TO CREATE OBJECTSET VIA SQL
  //ARMSQL    DD *
    SELECT DBNAME, NAME FROM SYSIBM.SYSTABLESPACE
    WHERE DBNAME LIKE 'ARMDB%'
  /*
  //* OR PDS FILE USED TO CREATE OBJECTSET VIA SQL
  //ARMSQL    DD DISP=SHR,DSN=YOURPDS.FILE(YOURSQL)         
  //* OR SEQ FILE USED TO CREATE OBJECTSET VIA SQL
  //ARMSQL    DD DISP=SHR,DSN=YOURSEQ.FILE

When you use ARMSQL and SQL, follow these guidelines:

• To create an object set by partition, select from SYSIBM.SYSTABLEPART or SYSIBM.SYSINDEXPART.
• To create an object set that is not by partition, select from SYSIBM.SYSTABLE or SYSIBM.SYSINDEX.
• Specify TS, IX, or SG as the first variable. BMC AMI Recovery Manager checks to ensure that 'TS', 'IX', or 'SG' follows the SELECT statement.
• Blank lines are excluded.
• You can enter up to 16,000 characters.
• Only one SQL statement is accepted.
• Semicolons are not allowed.
• If not specified, the partition number is set to 0.
• The IX name length and number of partitions follow the rules of the Db2 version that you are using.

• The SQL statements must be exactly as shown in the examples in the following table and cannot deviate except in the WHERE clause.

  Object type	SQL statement
  TS	SELECT 'TS', DBNAME, NAME FROM SYSIBM.SYSTABLESPACE WHERE DBNAME LIKE ‘QZU%’
  	SELECT 'TS', DBNAME, TSNAME, PARTITION FROM SYSIBM.SYSTABLEPART WHERE DBNAME='QZUDPT22' AND TSNAME='QZUS0122' AND PARTITION IN (4090, 4092, 4094, 4096)
  IX	SELECT 'IX', CREATOR, NAME, CREATOR, NAME FROM SYSIBM.SYSINDEXES WHERE DBNAME = 'R92DB59'
  	SELECT 'IX', IXCREATOR, IXNAME, IXCREATOR, IXNAME, PARTITION FROM SYSIBM.SYSINDEXPART WHERE IXCREATOR='QZU' AND PARTITION > 100 AND PARTITION <= 200
  SG	SELECT ‘SG', CREATOR, NAME, CREATOR, NAME FROM SYSIBM.SYSSTOGROUP WHERE NAME ='SG1234'

  For more information, see CREATE-OBJECTSET.

• Vvvvvvv (required for the volume VVDS method only)

  Required when you use the VVDS method to create volume object sets. The ddname must be V vvvvvv where the variable vvvvvv is the volume name. The data set name must be the volume’s VVDS name. The data set should be allocated with DISP=SHR.