DB2 Bind Manager Return codes

These topics describe the return codes when a module completes a process. Refer to the corresponding table for the module you are running for a description of the return code.

DB2 Bind Manager return codes

On normal completion of DB2® Bind Manager processing, one of the codes described in the following table is returned. The codes are the same whether you are using traditional DB2 Bind Manager (program BNDAVB) or coprocessor DB2 Bind Manager (program BNDAVB1).

Table 1. DB2 Bind Manager return codes

Return Code	Meaning
0	DB2 Bind Manager has completed successfully. The new source has passed SQL validation checks and a DB2 bind is not required.
4	DB2 Bind Manager has determined that either the SQL validation has failed or an error has occurred. Diagnostic messages have been issued. A DB2 bind is required.
16	DB2 Bind Manager has encountered a severe error and cannot make a bind or no bind determination. This return code is accompanied by a message describing the specific error.

DBRM Cross-reference return codes

On normal completion of DBRM cross-reference processing, one of the codes described in the following table is returned.

Table 2. DBRM Cross-Reference return codes

Return Code	Meaning
0	DBRM Cross-Reference has completed successfully.
4	There is an error in the input syntax.
12	Fatal error. Contact your IBM® representative.

DBRM Checker return codes

On normal completion of DBRM Checker processing, one of the codes described in the following table is returned.

Table 3. DBRM Checker return codes

Return Code	Meaning
0	DBRM Checker processing has completed successfully. The DBRMs pointed to by the DBRMLIB DD statement are consistent with the DB2 Catalog tables. A DB2 bind is not required.
4	DBRM Checker has determined that either the DBRMs did not match the DB2 catalog tables or the plan was not found. A DB2 bind is required.

BNDAVB3 return codes

On normal completion of BNDAVB3 program processing, one of the codes described in the following table is returned.

Table 4. BNDAVB3 return codes

Return Code	Meaning
0	At least one BIND command needs to be processed.
4	No bind commands need to be processed - skip the bind step 16.
16	Fatal error - see SYSPRINT for error messages. Unable to connect to DB2 or missing ddname.

BNDAVB4 return codes

On normal completion of BNDAVB4 program processing, one of the following codes is returned:

Table 5. BNDAVB4 return codes

Return Code	Meaning
0	Processing is complete.
16	Processing failed. Review the JCL and the output.