IBM Support

PH39573: INCORRECT TEXT IN SQLCODE805 AND SQLCODE4706

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • SQLCODE805 and SQLCODE4706 are not up-to-date.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Db2 12 for z/OS users, who use CREATE                        *
    * statements, ALTER statements, or packages.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The SQL text messages -805 and -4706                         *
    * are not up-to-date with the                                  *
    * current Db2 support.                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    - Db2 plans can no longer be bound directly to a DBRM or
    member. However, the current SQLCODE -805 still contains
    a reference to a DBRM.
    - We have implemented support for "CREATE OR REPLACE"
    for native SQL procedures and advanced triggers - the
    error message -4706 can also be issued for CREATE
    statements. However, the current SQLCODE -4706 is too specific
    for ALTER statement.
    

Problem conclusion

  • In response, the SQL message text for the following SQLCODEs
    are modified.
    
    1. -805
       from:
         DBRM OR PACKAGE NAME
         location-name.collection-id.dbrm-name.consistency-token
         NOT FOUND IN PLAN plan-name. REASON reason-code
       to:
         PACKAGE NAME
         location-name.collection-id.dbrm-name.consistency-token
         NOT FOUND IN PLAN plan-name. REASON reason-code
    2. -4706:
       from:
         ALTER STATEMENT FOR AN SQL ROUTINE OR ADVANCED TRIGGER
         CANNOT BE PROCESSED BECAUSE THE OPTIONS CURRENTLY IN
         EFFECT (ENVID current-envid) ARE NOT THE SAME AS THE ONES
         THAT WERE IN EFFECT (ENVID defined-envid) WHEN THE
         ROUTINE OR VERSION WAS FIRST DEFINED
       to:
         THE STATEMENT FOR AN SQL ROUTINE OR ADVANCED TRIGGER
         CANNOT BE PROCESSED BECAUSE THE OPTIONS CURRENTLY IN
         EFFECT (ENVID current-envid) ARE NOT THE SAME AS THOSE
         THAT WERE IN EFFECT (ENVID defined-envid) WHEN THE OBJECT
         OR VERSION WAS FIRST DEFINED
    Additional Keywords:
    SQLCODE805
    SQLCODE4706
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH39573

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-08-04

  • Closed date

    2021-10-06

  • Last modified date

    2021-11-01

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

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

    UI77477

Modules/Macros

  • DSNTIAM
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI77477

       UP21/10/14 P F110

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0"}]

Document Information

Modified date:
02 November 2021