PM81375: BEHAVIOUR OF 'RUN SQLID' PARM ON GENERATED GRANT STATEMENTS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Administration Tool for z/OS' handling of the
  'Run SQLID' field can result in variation in GRANT statement.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration and DB2      *
  *                 Object Comparison Tool for z/OS who run      *
  *                 Compare, ALT 'Alter Table ALT', or Change    *
  *                 Management to generate an APPLY job which    *
  *                 contains GRANT statements.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using the ALT, Compare or Change   *
  *                      Management function to generate an      *
  *                      APPLY job, if option 'Run SQLID' is     *
  *                      set to 'SQLID', the SQLID is applied    *
  *                      to the DDL statements and the GRANT     *
  *                      statements in the APPLY jobs.  This     *
  *                      may cause problems because the SQLID    *
  *                      used to create the objects may not      *
  *                      be a security ID that should be used    *
  *                      as the grantor.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using the ALT, Compare or Change Management function to
  generate an APPLY job, if option 'Run SQLID' is set to 'SQLID',
  the SQLID is applied to the DDL statements and the GRANT
  statements in the APPLY jobs. This may cause problems because
  the SQLID used to create the objects may not be a security ID
  that should be used as the grantor.
  

Problem conclusion

• A new option 'Object Grantor' is now available in the Compare,
  ALT and Change Management functions to allow a choice on the
  SQLID to be used by the GRANT statements in the generated APPLY
  jobs.  This option works in conjunction with the 'Run SQLID'
  option:
  
  1. When a SQLID is specified for 'Object Grantor' and 'Run
  SQLID' is not specified as '<NONE>', then a SET CURRENT SQLID
  statement will be generated prior to each GRANT statement in
  the APPLY jobs, using the SQLID specified in the 'Object
  Grantor' field.
  
  2. When 'Run SQLID' is specified as '>NONE<', no SET
  CURRENT SQLID statement will be generated prior to the
  GRANT statements even if 'Object Grantor' is specified
  with a SQLID.
  
  3. When 'Run SQLID' is specified with a SQLID and 'Object
  Grantor' is blank, the SQLID set at 'Run SQLID' field will
  also be applied to the GRANT statements in the APPLY jobs.
  
  4. When 'Run SQLID' and 'Object Grantor' both blank, SET
  CURRENT SQLID statements will be generated as necessary.
  
  A new column GRTSQLID needs to be added to the Change
  Management table ADBCHG.
  
  For users of DB2 Administration Tool and Object Comparison
  Tool Version 10.1,  please modify the SADBSAMP member
  ADBCHG05 and submit the job to add this column.
  
  For users of DB2 Administration Tool and Object Comparison
  Tool Version 10.2,  please modify the SADBSAMP member
  ADBCHG04 and submit the job to add this column.
  
  Failure to add this column will cause a SQLCODEN206 /
  SQLCODE=-206 during Analyze.
  
  Note: When 'Run SQLID' is blank, 'Object Grantor' is set
  to the SQLID, 'Mask ignored fields' on panel GOC5
  'Generate Compare jobs' is set to 'No', and at the same
  time, Ignore is specified for SYSTABLES.OWNER or
  SYSTABLESPACE.CREATOR, the SQLID could be switched to
  the 'Object Grantor' for GRANT statements but not
  switched back. This is a known issue and will be fixed
  in APAR PM88501.
  

Temporary fix

Comments

• ×**** PE13/10/08 FIX IN ERROR. SEE APAR PM98676  FOR DESCRIPTION
  ×**** PE13/10/21 FIX IN ERROR. SEE APAR PM99573  FOR DESCRIPTION
  

APAR Information

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

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

  UK97962

Modules/Macros

• ADBCCM   ADBCHANG ADBCHG04 ADBCHG05 ADBEALT  ADBEDIAG ADBHC11A
  ADBH7P   ADBMCMA  ADBP7P   ADBSALT  ADB2CEX1 ADB2CMF  ADB2CMP
  ADB2CMR  ADB2CMT  ADB2C11A ADB2000
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK97962

     UP13/09/28 P F309

• RA20 PSY UK97937

     UP13/09/28 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.