PH06133: ADDITIONAL OR INCORRECT SET CURRENT SQLID STATEMENT GENERATED IN WORKLIST SQLCODE -551 / SQLCODEN551 RUN SQLID OBJECT GRANTOR

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR addresses two issues in which an incorrect SET
  CURRENT SQLID statement may be generated for a job submitter in
  a WSL:
  1.  If a RUN SQLID, different from the SQLID of the job
  submitter, is specified on a change where an object needs to be
  dropped and recreated, a 'SET CURRENT SQLID' statement for
  the job submitter, instead of for the RUN SQLID,  may be
  generated in the WSL for the CREATE' statement.
  2.  If two different SQLIDs are specified for
  RUN SQLID and OBJECT GRANTOR, and both are different from the
  job submitter, a 'SET CURRENT SQLID' statement for the job
  submitter may be generated after the correct 'SET CURRENT SQLID'
  statement for the RUN SQLID before a CREATE statement.
  In either case, if the job submitter does not have the
  privileges required to execute the change, the result may be an
  error such as SQLCODE -551 /SQLCODEN551, auth-id DOES NOT HAVE
  THE PRIVILEGE TO PERFORM OPERATION operation ON OBJECT
  object-name.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool for     *
  *                 Z/os.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: An incorrect SET CURRENT SQLID          *
  *                      statement may be generated in a         *
  *                      WSL, possibly leading to a SQLcode      *
  *                      -551 / SQLCODEN551 error when the       *
  *                      WSL is executed.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR addresses two issues in which an incorrect
  SET CURRENT SQLID may be generated in a WSL:
  
  1. If a RUN SQLID, different from the SQLID of the job
  submitter, is specified on a change where an object needs to be
  dropped and recreated, a 'SET CURRENT SQLID' statement for
  the job submitter, instead of for the RUN SQLID, may be
  generated in the WSL for the CREATE statement.
  
  2. If two different SQLIDs are specified for RUN SQLID
  and OBJECT GRANTOR, and both are different from the
  job submitter, an additional 'SET CURRENT SQLID'
  statement (for the job submitter) may be generated after
  the correct 'SET CURRENT SQLID' statement (for the
  RUN SQLID) before a CREATE statement.
  
  In either case, if the job submitter does not have the
  privileges required to execute the change, the result may
  be an error such as SQLCODE -551 /SQLCODEN551, auth-id
  DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation
  ON OBJECT object-name.
  

Problem conclusion

• Problem has been resolved.
  

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:

Modules/Macros

•    ADB2CME  ADB2CMF  ADB2CMO  ADB2CMP  ADB2CMR
  ADB2CMS  ADB2CMT  ADB2CMU  ADB2CM1  ADB2CM2  ADB2CM3
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RB20 PSY UI60203

     UP18/12/14 P F812

• RC10 PSY UI60204

     UP18/12/14 P F812

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.