Updates to Tools Base Autonomics Director V1.4 User's Guide

Product documentation


Abstract

Updates that apply to Tools Base Autonomics Director V1.4 User's Guide (SC19-3765-04) for APAR PI10966.

Content

Update 4
Date of change:
September 2, 2014
Topic:
Chapter 3. Creating skeleton JCL for use with DB Sensor
Change description:
Changed topic for APAR PI24201 and PI24263

Creating skeleton JCL for use with DB Sensor
Stand-alone DB Sensor jobs can be run automatically by using the scheduling functions of Autonomics Director. Before you schedule DB Sensor jobs by using Autonomics Director, you must create skeleton JCL jobs.

From the skeleton JCL, Autonomics Director substitutes all occurrences of the defined variable names in the control statement and submits the JCL.

The information in this section describes the procedure for creating skeleton JCL for stand-alone DB Sensor jobs.

The following products provide a stand-alone DB Sensor:

  • IBM IMS Database Solution Pack for z/OS
  • IBM IMS Fast Path Solution Pack for z/OS


Update 3
Date of change:
September 2, 2014
Topic:
Chapter 3. Skeleton JCL of stand-alone full-function DB Sensor
Change description:
Changed topic for APAR PI24201

Creating skeleton JCL for the full-function stand-alone DB Sensor
You must prepare skeleton JCL for both HALDB and non-HALDB full-function databases to submit stand-alone FF DB Sensor jobs by using Autonomics Director. The FF DB Sensor is a component of IBM IMS Database Solution Pack for z/OS.

About this task
This procedure refers to the BBESJCL2 sample skeleton JCL member in the hlq.SHPSSAMP library file. (Substitute the hlq variable with the installation data set high-level qualifier.)

Important: If you code a job name label in your skeleton JCL, all stand-alone DB Sensor jobs that are generated from the skeleton will use the same job name and those sensor jobs will be serialized. If you want to avoid this, you can use the symbol $DBNAME$ for a non-HALDB database and $PANAME$ for a HALDB partition. You can also use the $USNAME$ symbol, which identifies the owner of the DB resource or group resource.

Procedure
1. Copy member BBESJCL2 to your data sets and customize the parameters to conform to your standards and environment. The sample member contains descriptive customization information.
The JCL can be created as skeletal JCL by using symbolic variables. When the JCL is submitted, Autonomics Director substitutes each symbolic variable with a value.

Table 1. Symbolic variables for sample member BBESJCL2

Symbolic variable
Value
$DBNAME$ The name of the database that sensor data is being collected for.
$PANAME$ The name of the HALDB (PHDAM or PHIDAM) partition that sensor data is being collected for.

2. Optional: If you want to process a non-HALDB or process all partitions in a HALDB, create a second version of the skeleton JCL and delete the partition parameter ( PART=$PANAME$) from the new version.

Examples
In the following example of a control statement, Autonomics Director requests sensor data for the PHDAM1A partition of the PHDAM1 database. The symbolic variables are replaced by database PHDAM1 and partition PHDAM1A.

//BBESIN DD *
GLOBAL
DBRC=Y,HPIO=Y,
TOSIXCFGRP=TOISYS01,ITKBSRVR=FPQSRV01,
ADXCFGRP=ADSRV01
DATABASE DBD=PHDAM1,PART=PHDAM1A
/*


In the following example of a control statement, Autonomics Director requests sensor data for all partitions of the HDAM1 database. The symbolic variable is replaced by HDAM1.

//BBESIN DD *
GLOBAL
DBRC=Y,HPIO=Y,
TOSIXCFGRP=TOISYS01,ITKBSRVR=FPQSRV01,
ADXCFGRP=ADSRV01
DATABASE DBD=HDAM1
/*


Update 2
Date of change:
September 2, 2014
Topic:
Chapter 3. Skeleton JCL for a stand-alone Fast Path DB sensor job
Change description:
Changed topic for APAR PI24263

Creating skeleton JCL for a Fast Path stand-alone DB Sensor
You must prepare skeleton JCL for a stand-alone Fast Path DB Sensor job to be tailored and submitted by Autonomics Director. The Fast Path DB Sensor is a component of IBM IMS Fast Path Solution Pack for z/OS.

About this task
This procedure refers to the HFPOJCL2 sample skeleton JCL member, which contains sample skeleton JCL. The HFPOJCL2 sample member is in the hlq.SHFPSAMP library of IMS Fast Path Solution Pack V1.3. (Substitute the hlq variable with the installation data set high-level qualifier.)
Important: If you code a job name label in your skeleton JCL, all stand-alone DB Sensor jobs that are generated from the skeleton will use the same job name and those sensor jobs will be serialized. If you want to avoid this, you can use the symbol $DBNAME$ for a database and $ARNAME$ for a DEDB area. You can also use the $USNAME$ symbol for the owner of the DB resource or group resource.

Procedure
Copy member HFPOJCL2 to your data sets and customize the parameters to conform to your standards and environment. The sample member contains descriptive customization information.

The JCL can be created as skeletal JCL by using symbolic variables. When the JCL is submitted, Autonomics Director substitutes each symbolic variable with a value.

Table 1. Symbolic variables for sample member HFPOJCL2

Symbolic variable
Value
$DBNAME$ The name of the database that sensor data is being collected for.
$ARNAME$ The name of the DEDB area that sensor data is being collected for.


Example
In the following example of a control statement, Autonomics Director requests sensor data for the AREANAME1 area of the DEDB1 database. The symbolic variables are replaced by database AREANAME1 and partition DEDB1.
//HFPSYSIN DD *                                      
 GLOBAL                                                                
     DBRC=YES,                                                        
     ADXCFGRP=ADSERV01,                                                
     ITKBSRVR=FPQSRV01,                                                
 DATABASE                                                              
     DBD=DEDB1,                                                    
     IAREA=AREANAME1                                                    
/*


Update 1
Date of change:
June 3, 2014
Topic:
Chapter 3. Skeleton JCL for an IMS Online Reorganization Facility reorganization job
Change description:
New topic for APAR PI10156

Skeleton JCL for an IMS Online Reorganization Facility reorganization job

You must prepare skeleton JCL to submit the IMS™ Online Reorganization Facility reorganization job by using Autonomics Director.

For more information about creating JCL for IMS Online Reorganization Facility, see the IMS Online Reorganization Facility User's Guide.

Restriction: IMS Online Reorganization Facility does not support the reorganization of databases that have external logical relationships. To use group-managed reorganization with databases that have external logical relationships, you must prepare JCL for IMS Database Reorganization Expert.

Important: The ADXCFGRP keyword must be specified in the JCL so that IMS Online Reorganization Facility can notify Autonomics Director of the results of the reorganization.

IMS Online Reorganization Facility skeleton JCL for a HALDB database

//ORF     EXEC PGM=HRFREORG,REGION=80M
//STEPLIB  DD DISP=SHR,DSN=DBSP.SHRFLOAD
//         DD DISP=SHR,DSN=DBSP.SHPSLMD0
//         DD DISP=SHR,DSN=IMST.SFOILOAD
//         DD DISP=SHR,DSN=IMST.SHKTLOAD
//         DD DISP=SHR,DSN=IMS.SDFSRESL
//IMS      DD DISP=SHR,DSN=IMS.DBDLIB
//IMSDALIB DD DISP=SHR,DSN=IMS.MDALIB
//HRFSYSIN DD *
 REORG    DBD($DBNAME$) PARTITION($PANAME$) -
          ADXCFGRP(ADSERVER) ITKBSERVER(ITKBSRVR) -
          LOG1DSN(YOUR.LOGHLQ.&DBD.&DATE1.&TIME2) -
          ICDYN(Y) IC1DSN(YOUR.ICHLQ.&DDNAME.&DATE1.&TIME2)
/*      

From the skeleton JCL, Autonomics Director creates the control statement by replacing the symbolic variables with their associated values.

Table 1. Symbolic variables for the reorganization job that is used with HALDB databases

Symbolic variable
Value
$DBNAME$ The name of the master DBD.
$PANAME$ The name of the partition. This variable is required for HALDB databases.


IMS Online Reorganization Facility skeleton JCL for a non-HALDB full-function database

//ORF     EXEC PGM=HRFREORG,REGION=80M
//STEPLIB  DD DISP=SHR,DSN=DBSP.SHRFLOAD
//         DD DISP=SHR,DSN=DBSP.SHPSLMD0
//         DD DISP=SHR,DSN=IMST.SFOILOAD
//         DD DISP=SHR,DSN=IMST.SHKTLOAD
//         DD DISP=SHR,DSN=IMS.SDFSRESL
//IMS      DD DISP=SHR,DSN=IMS.DBDLIB
//IMSDALIB DD DISP=SHR,DSN=IMS.MDALIB
//HRFSYSIN DD *
 REORG    DBD($DBNAME$) -
          ADXCFGRP(ADSERVER) ITKBSERVER(ITKBSRVR) -
          LOG1DSN(YOUR.LOGHLQ.&DBD.&DATE1.&TIME2) -
          ICDYN(Y) IC1DSN(YOUR.ICHLQ.&DDNAME.&DATE1.&TIME2)
/*

From the skeleton JCL, Autonomics Director completes the control statement during JCL job submission by replacing the $DBNAME$ symbolic variable with the name of the DBD.

Publication number

SC19-3765-04

Copyright date

2014

Original publication date

2014/5/30

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tools Base for z/OS
Autonomics Director

Software version:

1.4.0

Operating system(s):

z/OS

Reference #:

7040574

Modified date:

2014-09-08

Translate my page

Machine Translation

Content navigation