Why am I getting a -812 on my Easytrieve compile?

Document ID:  TEC1294905
Last Modified Date:  08/11/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Easytrieve Report Generator

Releases

  • CA Easytrieve Report Generator:Release:11.5
  • CA Easytrieve Report Generator:Release:11.6

Components

  • CA-Pan/SQL (DB2 Interface):PANSQL
  • Pan/SQL DB2 for OS/390:PSDB2M
Introduction:

Upgrading to DB2v10 doing a Bind Plan

Question:

Why am I getting a -812 recompiling an Easytrieve program that has SQL code?

Environment:
DB2v10, doing a Bind Package, and a Bind Plan.
Answer:

The Bind syntax for the PLAN that results in the SQLCODE -812 is:
BIND PLAN(DOETPC1) PKLIST(*.DONOCOL) -
DEGREE(1) VALIDATE(BIND) ISOLATION(CS) -
FLAG(E) CURRENTDATA(NO) RELEASE(COMMIT) -
RETAIN CACHESIZE(0) ACQUIRE(USE) -
EXPLAIN(NO) ACTION(REPLACE)

The Bind syntax for the PLAN that results in clean run is:
BIND PLAN(DOETPC1) PKLIST(*.DONOCOL.*) -
DEGREE(1) VALIDATE(BIND) ISOLATION(CS) -
FLAG(E) CURRENTDATA(NO) RELEASE(COMMIT) -
RETAIN CACHESIZE(0) ACQUIRE(USE) -
EXPLAIN(NO) ACTION(REPLACE)

Additional Information:

The difference is very slight - PKLIST(*.collid) results in SQL -812 Execution. PKLIST(*.collid.*) results in clean run.

What a difference an additional '*' makes!

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >