Configuring coprocessor mode (program BNDAVB4)
With Bind Avoidance coprocessor support, Bind Avoidance functionality extends to operate in the coprocessor environment so that Bind Avoidance continues to be supported.
About this task
In the traditional operating environment, the DB2® precompiler runs as a separate job step, and DB2 Bind Manager intercepts the source code after the precompiler modifies it and before the language compiler sees it. Bind Avoidance operates on this intermediate source code before passing it to the compiler.
In a coprocessor environment, the precompiler and the language compiler are combined into a single step. Therefore, the intermediate source code is unavailable for manipulation.
Configuring for coprocessor support requires different JCL than operating Bind Avoidance in a traditional environment. The program name and the required DD statements are different. Coprocessor support adds two additional job steps: one before the compiler step and one after the compiler step.
Because of the methods that are used for compiler optimization, BNDAVB4 is required to run as a preprocessor to the present coprocessor. You must run the processes in the following order:
- BNDAVB4. This program determines whether bind avoidance is possible.
- The coprocessor. The coprocessor creates the executable and the DBRM.
- BNDAVB1. This program post-processes the executable and the DBRM to complete the analysis and bypass the bind, if possible.