Bind control file
If you generate a COBOL program that accesses an SQL table, EGL always produces a bind control file. A bind control file is meaningful only if you are generating a COBOL program that runs on z/OS® and that accesses SQL tables on DB2®. The file is equivalent to the bind control file that you would create if you accessed DB2® from a native COBOL program. In the context of EGL, the bind control file is created when you are preparing the generated source for deployment.
When source code that accesses DB2® is
prepared for z/OS®, the following
steps handle SQL statements that are in the code:
- A DB2® precompilation step uses the SQL statements to create a database request module (DBRM).
- A bind step creates a DB2® plan,
possibly by combining that DBRM with the DBRMs of other programs that
are intended for the same CICS® transaction
or job step.
The bind control file specifies what DBRMs are included in the DB2® plan created by the bind step, and the plan in turn makes DB2® access possible for each program that contributed a DBRM.