Sample JCL for use with Bind Manager

Answer

The following describes sample JCL for DB2 Bind Manager and contains a brief description of its capabilities in order to demonstrate the product. These jobs can be used to test the product after an install.

BNDAVBTS - This job simulates running a precompile, compile, and bind which would be part of an application migration. Change the userid to your own TSO/DB2 Authorization id. You must preallocate a DBRM library; that is, point the pre-compile step to the DBRM library, in order to build the DBRM in question. When you run this job for the first time, STEP1 will generate a RC 4 which indicates that a BIND is required (there is no DBRM in your DBRMLIB). STEP2 will generate a RC 0 (the DBRM matches so there is no BIND required).

To run this job repeatedly, you may need to delete the member DSN8EC2 from the DBRM library in order to recreate the scenario.

//BNDAVBTS JOB
//*
//STEP1 EXEC PGM=BNDAVB,PARM='HOST(COB2),APOST',REGION=0M
//STEPLIB DD DISP=SHR,DSN=DB2BM.V2R1.SBNDLOAD
// DD DISP=SHR,DSN=DB2.V6R1M0.SDSNLOAD
//SYSLIB DD DSN=DB2.V6R1M0.SDSNSAMP,DISP=SHR
//DBRMLIB DD DSN=userid.DBRMLIB.DATA(DSN8EC2),DISP=SHR
//SYSCIN DD DISP=(,PASS),DSN=&&COMPIN,UNIT=SYSDA,SPACE=(CYL,(5,2))
//SYSIN DD DISP=SHR,DSN=DB2.V6R1M0.SDSNSAMP(DSN8EC2)
//SYSUT1 DD SPACE=(CYL,(4,2)),UNIT=SYSDA
//SYSUT2 DD SPACE=(CYL,(4,2)),UNIT=SYSDA
//SYSPRINT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//*
//STEP2 EXEC PGM=BNDAVB,PARM='HOST(COB2),APOST',REGION=0M
//STEPLIB DD DISP=SHR,DSN=DB2BM.V2R1.SBNDLOAD
// DD DISP=SHR,DSN=DB2.V6R1M0.SDSNLOAD
//SYSLIB DD DSN=DB2.V6R1M0.SDSNSAMP,DISP=SHR
//DBRMLIB DD DSN=userid.DBRMLIB.DATA(DSN8EC2),DISP=SHR
//SYSCIN DD DISP=(,PASS),DSN=&&COMPIN,UNIT=SYSDA,SPACE=(CYL,(5,2))
//SYSIN DD DISP=SHR,DSN=DB2.V6R1M0.SDSNSAMP(DSN8EC2)
//SYSUT1 DD SPACE=(CYL,(4,2)),UNIT=SYSDA
//SYSUT2 DD SPACE=(CYL,(4,2)),UNIT=SYSDA
//SYSPRINT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//

BNDA006 - This job executes the Batch DBRM Cross-Reference report. This sample compares the DBRMs to the load library members for the DB2 Administration Tool (prefix ADM*). SYSPRINT shows the selected DBRMs, the excluded DBRMs, the selected load modules, and the excluded load modules. The cross-reference report shows the DBRM name and the timestamp in the DBRM. If there is a matching load module, the report references the load module name and the CSECTs within the load module. If the DBRM is found in the DB2 subsystem by name, YES appears under the DBRM Present.

//BNDA006 JOB
//RUN EXEC PGM=BNDA006
//STEPLIB DD DISP=SHR,DSN=DB2BM.V2R1.SBNDLOAD
// DD DISP=SHR,DSN=DB2.V6R1M0.SDSNLOAD,DISP=SHR
//DBRMLIB DD DISP=SHR,DSN=DB2ADMIN.V2R1M0.SADBDBRM
//LOADLIB DD DISP=SHR,DSN=DB2ADMIN.V2R1M0.SADBLLIB
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
SSID=DB2P SUBSYSTEM ID REQUIRED
DBRM=ADB* DBRM NAME(S) OPTIONAL
LMOD=ADB* LOAD MODULE NAME(S) OPTIONAL
*
* NOTE: DBRM AND LOAD MODULE NAMES
* MAY INCLUDE WILDCARDS
/*
//

BNDA007 - This job executes the Load Module Static SQL report. This job compares the load library members for the DB2 Administration Tool (prefix ADM*). The Static SQL Load module (BNDA007) shows which load module and CSECTs within the load module call Static SQL. This can be useful when attempting to match a DBRM with a load module.The Static SQL load module reads all members in a load library and examines each CSECT within each load module. If a CSECT uses Static SQL, the report shows the load module name and the CSECT name, and also places a YES in the SQL column. If no SQL use is found, a NO is placed in the SQL column.

//BNDA007 JOB
//STEP1 EXEC PGM=BNDA007
//STEPLIB DD DISP=SHR,DSN=DB2BM.V2R1.SBNDLOAD
// DD DSN=DB2.V6R1M0.SDSNLOAD,DISP=SHR
//LOADLIB DD DISP=SHR,DSN=DB2ADMIN.V2R1M0.SADBLLIB
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*

BNDCKBTS - This job executes the DBRM checker report comparing the load library members in the DB2 Administration Tool SADBLLIB. It can be used to verify consistency between a DBRMLIB and a DB2 subsystem. It can check either one plan or several plans during its execution. DBRM Checker can also be used as part of the DB2 application compile procedure to ensure that a DBRM created during pre-compile is consistent with the associated plan in DB2.

The DBRMLIB DD statement should point to the PDS library containing all changed and unchanged DBRMs referenced by the plan. DBRM Checker will then compare the consistency token information in the DBRMLIB to that in the DB2 catalog.

//BNDCKBTS JOB
//STEP1 EXEC PGM=BNDCKB,PARM='DB2CAT(DSNBCAT),PLAN(ADB*)',REGION=0M
//STEPLIB DD DISP=SHR,DSN=DB2BM.V2R1.SBNDLOAD
// DD DSN=DB2.V6R1M0.SDSNLOAD,DISP=SHR
//DBRMLIB DD DISP=SHR,DSN=DB2ADMIN.V2R1M0.SADBDBRM
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//