IBM Support

PM26077: INCORRECT AUTHID OR OWNER USED FOR ALIAS RESOLUTION DURING A REMOTE PACKAGE BIND

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DB2DRDA defect pm26077 dpm26077
    Incorrect authid or owner used for alias resolution during a
    remote package bind.
    ********************************************************
    Additional symptoms and keyword:
     SQLCODE204N SQLCODE204 SQL204N SQL204 SRCN204 SRC204
     DSN6SPRM DRDA_RESOLVE_ALIAS
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users    *
    *                 running a remote package bind request and    *
    *                 DRDA_RESOLVE_ALIAS subsystem parameter is    *
    *                 set to YES on the requester subsystem.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: SQLCODE +204 or -204 returned from      *
    *                      remote system during remote package     *
    *                      bind for a reference to an object       *
    *                      that should have been found on the      *
    *                      requester system.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Remote BIND PACKAGE requests from a DB2 requester system
    (SITE1) to a remote server (SITE2) may fail with unpredictable
    errors on the server SITE2 because of faulty DRDA ALIAS
    RESOLUTION processing at the requester SITE1.  DRDA ALIAS
    RESOLUTION is a capability provided by APAR PK64045 (see NOTE
    below) for V8 and V9, and is enabled when the subsystem
    parameter DRDA_RESOLVE_ALIAS is set to YES.  DRDA ALIAS
    RESOLUTION always occurs on V10 subsystems.
    
    With DRDA ALIAS RESOLUTION enabled, when any statement being
    bound references an object using a 3-part name ALIAS, DB2 at
    SITE1 searches its catalog to resolve the 3-part name ALIAS
    into the qualified name of the object at SITE2.  DB2 then
    creates a modified statement with the resolved object
    references and sends that modified statement to SITE2 to be
    bound.
    
    If the Communication Database (CDB) on SITE1 has outbound
    userid translation definitions which are to be used when
    accessing SITE2, then DRDA ALIAS RESOLUTION for unqualified
    object references in the statement may incorrectly use the
    CDB definition to search the SITE1 catalog when resolving
    3-part name ALIASes instead of using the value of the OWNER
    bind option, if it is provided.
    
    As a result, DB2 at SITE1 generates a modified statement with
    incorrectly qualified object references and sends the incorrect
    statement to the remote server SITE2.  The results of the bind
    of the statement at SITE2 are unpredictable, but include the
    possibility of various SQL errors, such as SQLCODE +204 and
    -204, as described above.
    
    NOTE: APAR PK64045 provides tools and capabilities to aid
    customers in migrating their plans and packages from using
    private protocol to using DRDA protocol. One of the
    capabilities is DRDA ALIAS RESOLUTION.
    

Problem conclusion

  • DB2 DRDA alias resolution processing has been changed to
    to ensure that the provided value of the OWNER bind option
    or the job authid is used to qualify unqualified object
    references in SQL statements when accessing the requester
    catalog during a remote package bind.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM26077

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-05

  • Closed date

    2011-01-24

  • Last modified date

    2011-03-02

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

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

    UK64183 UK64184 UK64185

Modules/Macros

  • DSNLXRCM
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK64183

       UP11/02/09 P F102

  • R810 PSY UK64184

       UP11/02/09 P F102

  • R910 PSY UK64185

       UP11/02/09 P F102

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 March 2011