PI14309: SQLCODE 525 WHILE EXECUTION, PACKAGE has a SQL statement that reference an ALIAS of REMOTE TABLE and a non-exist table

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• If a package contains SQL statement that match below
  specifiction, and bind with VALIDATE(BIND) SQLERROR(CONTINUE)
  will issue SQLCODE 204. SQLCODE 525 was issued during execution.
  The specification of the problem SQL statemnt is:
  If a SQL statement referencing both an alias for a remote table
  and a non exist table.
  Example:
  SELECT C1,C2 from T1, T2 where T1.C3=T2.C4;
  T1 is the alias for a remote table and T2 is the table not
  exist on current server.
  PLEASE NOTE: the sequence is crucial. If T1 and T2 switch
  position, there's no problem.
  
  
  
  
  Additional keywords and symptoms:
  **********************************
  DDF connections may experience
  Abend 04E-00D34424 DSNLXGLM.DSNLXRAX 000A
  00D34424 DSNLXRAX ABNDID000A
  

Local fix

• BIND with VAL(R) SQLERROR(CONTINUE) can by pass this issue
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
  *                 users of three-part object name or           *
  *                 an ALIAS for a three-part object name        *
  ****************************************************************
  * PROBLEM DESCRIPTION: SQLCODE525 during execution of a        *
  *                      package that includes an SQL statement  *
  *                      that references both a three-part name  *
  *                      table and a table that does not exist   *
  *                      (in that order)                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A package with SQL statement referencing both a three-part
  table name and a table that does not exists (has to be in that
  order) was bound with VALIDATE(BIND) and SQLERROR(CONTINUE).
  During BIND of this package, SQLCODE204 was encountered for the
  table that does not exists.  After the BIND of this package, the
  user ran the application that invoked this package and
  encountered SQLCODE525.
  
  The abend occurred because DB2 incorrectly built an internal
  control block.
  
  Further investigation showed that during BIND of this package,
  DB2 created 2 entries in the internal control block for the
  same SQL statement that references a three-part table name
  and a table that is not defined.  As a result, during execution
  time, the SQL statement following the SQL statement that
  references a three-part table name and a table that is not
  defined was mapped to the incorrect entry in the internal
  control block and encountered SQLCODE525.
  

Problem conclusion

• DB2 was modified to correctly build an internal control block
  for a package bound with VALIDATE(BIND) and references an SQL
  statement with a three-part table name and a table that is not
  defined.
  
  Additional Keywords:  SQLCODE204 SQLCODE525
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI17179 UI17180

Modules/Macros

• DSNXEPP
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI17179

     UP14/05/03 P F405

• RB10 PSY UI17180

     UP14/05/03 P F405

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.