Bind a COBOL DB2 Program End to End

The COBOL Db2 bind pipeline

A COBOL program with EXEC SQL does not talk to Db2 merely because it compiled. The SQL must be extracted, bound, and reachable through an application plan. Treat the following stages as one release unit.

The consistency token stamped into the DBRM and load module is how Db2 proves that the running program matches the bound package. If you promote a new load module without the matching package, or bind an old DBRM against a new load module, runtime SQL fails even when every JCL step reports return code zero in isolation.

Prerequisites

Include DCLGEN or equivalent host declarations when the shop standard requires them. Confirm APPLCOMPAT and SQL level expectations for new syntax. For promotion pipelines, identify whether test and production use different collections with the same plan name pattern or different plans entirely.

Steps: bind the COBOL program

1. Precompile and build the load module

Run the Db2 precompiler or SQL statement coprocessor so the DBRM member is written to the DBRM library and the modified COBOL source is ready to compile. Compile and link-edit into the application load library. Do not discard the DBRM after a successful compile; bind needs that exact member.

2. BIND PACKAGE for the DBRM

Bind the program DBRM into the target collection. Keep OWNER, QUALIFIER, ISOLATION, and VALIDATE aligned with shop standards.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
//BINDPKG  EXEC PGM=IKJEFT01,DYNAMNBR=20
//STEPLIB  DD DISP=SHR,DSN=DSN.V12R1M0.SDSNEXIT
//         DD DISP=SHR,DSN=DSN.V12R1M0.SDSNLOAD
//DBRMLIB  DD DISP=SHR,DSN=APP.TRAIN.DBRMLIB
//SYSTSPRT DD SYSOUT=*
//SYSTSIN  DD *
  DSN SYSTEM(DB2T)
  BIND PACKAGE(TRAINCOLL) MEMBER(EMPRPT01) -
       ACTION(REPLACE) -
       OWNER(APPTRAIN) -
       QUALIFIER(TRAINING) -
       ISOLATION(CS) -
       VALIDATE(BIND) -
       RELEASE(COMMIT) -
       EXPLAIN(YES)
  END
/*

3. BIND PLAN with PKLIST when needed

If the plan already lists TRAINCOLL.*, a package replace is usually enough. For a new collection or first-time plan, bind or rebind the plan explicitly:

1
2
3
4
5
6
7
8
9
10
11
12
13
//BINDPLN  EXEC PGM=IKJEFT01,DYNAMNBR=20
//STEPLIB  DD DISP=SHR,DSN=DSN.V12R1M0.SDSNEXIT
//         DD DISP=SHR,DSN=DSN.V12R1M0.SDSNLOAD
//SYSTSPRT DD SYSOUT=*
//SYSTSIN  DD *
  DSN SYSTEM(DB2T)
  BIND PLAN(TRAINPLN) -
       PKLIST(TRAINCOLL.*) -
       ACTION(REPLACE) -
       ISOLATION(CS) -
       RETAIN
  END
/*

RETAIN preserves existing plan authorizations when your shop uses that option. Some sites bind package and plan in one SYSTSIN stream; others separate them for clearer promotion control. Either approach is fine when the final catalog state is correct.

4. Document the release set

Record program name, DBRM member, collection, package version if used, plan name, bind job name, and load library dataset. That checklist is the fastest way to diagnose -805 and -818 later.

Verify results

• Confirm BIND PACKAGE and BIND PLAN return codes and message text.
• Query SYSIBM.SYSPACKAGE for the collection and member name; note BINDTIME and VALID.
• Confirm the plan lists the collection in SYSIBM.SYSPACKLIST or local reports.
• Run a smoke test through the intended attachment (batch DSN RUN, CICS, or TSO) and check SQLCODE after the first SQL statement.
• If EXPLAIN(YES) was specified, review access paths for the critical statements before promoting to production.

1
2
3
4
5
6
7
8
9
SELECT COLLID, NAME, VERSION, OWNER, QUALIFIER, BINDTIME, VALID
  FROM SYSIBM.SYSPACKAGE
 WHERE COLLID = 'TRAINCOLL'
   AND NAME   = 'EMPRPT01';
 
SELECT PLANNAME, LOCATION, COLLID, NAME
  FROM SYSIBM.SYSPACKLIST
 WHERE PLANNAME = 'TRAINPLN'
 ORDER BY SEQNO;

Common errors

Also watch for QUALIFIER mistakes that bind successfully against the wrong schema. VALIDATE(BIND) catches missing objects in the intended qualifier, but it cannot stop you from intentionally pointing at an incorrect yet existing schema. Review QUALIFIER in the bind skeleton as carefully as MEMBER.

Explain It Like I'm Five

Your COBOL program is a robot with a shopping list of Db2 questions. Precompile copies the shopping list onto a special paper (the DBRM). Binding is when Db2 reads that paper, decides the fastest aisles to walk, and files the finished plan in a binder. Running the robot only works when the robot you start is the same one that wrote that paper, and when the classroom plan says it may open that binder.

Exercises

1. Draw the artifact flow from COBOL source to runnable batch step for program PAYRPT01.
2. Write BIND PACKAGE and BIND PLAN commands for collection PAYCOLL and plan PAYPLAN.
3. Explain the difference between replacing one package and rebinding an entire plan MEMBER list of twenty DBRMs.
4. Given SQLCODE -818, list the three artifacts that must share one precompile generation.
5. Write catalog queries you would use to prove a package is present and listed on a plan.