MainframeKit

+204

SQLSTATE 01532POSITIVE SQLCODE (WARNING)

At bind time a table, view or other object named in the SQL did not exist; the package was still built but the statement will be bound at run time.

MOST LIKELY

A typo in a table, view or alias name.

FIRST CHECK

Check the object name and qualifier in the bind listing against the catalog (SYSIBM.SYSTABLES).

TRY IT ▸

MainframeKit assistant

What it means

Db2 could not find the object the statement refers to while binding. When the bind allows it (VALIDATE(RUN)), the plan or package is created anyway and the statement is checked again every time it runs.

If the object still does not exist when the program runs, the statement fails with an error at that point. Fixing the cause also avoids the extra run-time bind work.

Typical causes

  • A typo in a table, view or alias name.
  • A missing or wrong qualifier, or the wrong QUALIFIER bind option.
  • Binding in an environment where the table has not been created yet.
  • Binding against the wrong Db2 subsystem.

How to fix it

  1. Check the object name and qualifier in the bind listing against the catalog (SYSIBM.SYSTABLES).
  2. Check the QUALIFIER and OWNER bind options.
  3. Create the missing object, or correct the name, then rebind.
  4. Make sure the package is bound on the subsystem where the tables exist.