PM93384: BIND FAILS W/DSNT212I,REBIND FAILS W/DSNT235I,WHEN USR W/EXPLAIN BUT NOT BIND PRIVILEGE ISSUES (RE)BIND WITH EXPLAIN(ONLY)...

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• 1. When a user with EXPLAIN privilege, but not BIND privilege,
  issues a BIND/REBIND command with option EXPLAIN(ONLY) or
  SQLERROR(CHECK) , the BIND fails with DSNT212I and REBIND fails
  with DSNT235I. But in this case, BIND/REBIND should not fail.
  2. When a user with BIND or BINDAGENT privilege issues a
  BIND/REBIND command with option EXPLAIN(ONLY), the BIND/REBIND
  runs successfully. This is also wrong. The BIND/REBIND should
  fail.                                                 (d167561)
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 11 for z/OS users who BIND/REBIND    *
  *                 packages                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: There are two problems fixed in this    *
  *                      APAR:                                   *
  *                      1. BIND PACKAGE with SQLERROR(CHECK) or *
  *                         EXPLAIN(ONLY) fails when the binder  *
  *                         has EXPLAIN privilege                *
  *                      2. BIND/REBIND PACKAGE with EXPLAIN     *
  *                         (ONLY) succeeds when the binder does *
  *                         not have EXPLAIN privilege.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  There are two problems fixed in this APAR:
  1. BIND PACKAGE with SQLERROR(CHECK) or EXPLAIN(ONLY) fails when
     the binder has EXPLAIN privilege
  2. BIND/REBIND PACKAGE with EXPLAIN (ONLY) succeeds when the
     binder does not have EXPLAIN privilege.
  The root cause is DB2 does not check the authority of the binder
  correctly for the two cases.
  
  Additional Keywords: SQLEXPLAIN MSGDSNT212I MSGDSNT235I
  

Problem conclusion

• Code has been changed to check the authority correctly.
  

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:

  UK97064

Modules/Macros

• DSNTBCM2 DSNTBMSG DSNTBRB2
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UK97064

     UP13/09/12 P F309

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.