IBM Support

PI63011: REMOTE BIND PACKAGE SUCCESSFUL BUT CALLED PACKAGE GETS SQLCODE805 WITH PI53960 APPLIED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • SAP SQLCreatePkgW( ) seems to run, but after successful
    bind, the sqlcode805n is received
    DDFD8B0.JCMTEST.SYSLH100.5359534C564C3031;DISTSERV;04 happens.
    
    Keywords:
    SQLCODE805 BIND REMOTE
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 for z/OS users of Remote BIND        *
    *                 PACKAGE when PI53960 (UI36585 for V10;       *
    *                 UI36586 for V11) is applied                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: User may receive SQLCODE -805 after     *
    *                      binding a package from a DB2 remote     *
    *                      client which is connected to DB2 for    *
    *                      z/OS server.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After PTF UI36585/UI36586 (PI53960), a remote BIND PACKAGE from
    client may fail to clean up an internal record, which
    results in SQLCODE -805 error when executing the package.
    

Problem conclusion

  • DB2 has been changed to remove the internal record as a result
    the package can be executed successfully after bind.
    
    Once APAR fix is applied and DB2 is restarted, those records
    will be gone. Before applying the apar, bind/rebind locally can
    get rid of those records.
    
    Additional keyword:  SQLCODE805,SQLBIND,SQLREMOTE
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI63011

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-25

  • Closed date

    2016-08-12

  • Last modified date

    2016-09-02

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

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

    UI40075 UI40076

Modules/Macros

  • DSNGEPIS DSNTBBP2
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI40075

       UP16/08/27 P F608 Ø

  • RB10 PSY UI40076

       UP16/08/27 P F608 Ø

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 September 2016