PM35190: NEW FUNCTION

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • New function.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 users.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Provide the ability to SELECT from      *
    *                      directory tables SYSIBM.SYSLGRNX,       *
    *                      SYSIBM.SYSUTILX and SYSIBM.SYSUTIL.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR provides support for SQL SELECT from directory tables
    SYSIBM.SYSLGRNX, SYSIBM.SYSUTIL and SYSIBM.SYSUTILX.
    This capability and the resulting output is primarily
    intended for use by IBM support.
    The following restrictions apply:
    - The authorization rules that apply for selects against
      the catalog also apply for selects against Directory
      objects. The authority must include one of the following:
      - Install SYSADM
      - SYSADM
      - SYSCTRL
      - ACCESSCTRL
      - DATAACCESS
      - SECADM
      - SQLADM
      - System DBADM
      - DBADM on DSNDB01
      - select on a specific table
    - Only SELECT and FETCH are permitted.
    - No transaction L-locks will be acquired regardless of
    application isolation level.
    
    The example for the SQLCODE -607 has been enhanced with the
    following:
    - The operation is on a directory object and the unit of work
    could not be converted to UR.  For example: UPDATE T1 SET C1 =
    (SELECT C1 FROM T1) WHERE EXISTS(SELECT LGR SYSIBM.SYSLGRNX); In
    this case, the SELECT against a directory object can not be
    converted to UR.
    
    The ability to SELECT from Directory objects is enabled when NFM
    (New Function Mode) is entered.  The ability to SELECT from the
    Directory objects is not enabled in a new install.  For a new
    install or if DB2 is already in NFM when apar is applied it can
    be enabled by running a utility job:
    
    CATMAINT UPDATE UNLDDN PM35190
    
    
    To verify if the ability to SELECT from Directory objects has
    been enabled, a row will be returned from the following SELECT:
    
    SELECT * FROM SYSIBM.SYSDATABASE WHERE DBID=1;
    
    DSNTESQ has been updated to support this change. Without this
    APAR query7 may return rows for DBNAME DSNDB01.
    
    ***Action for PM35190:
    
    See PM35190 APAR/PTF text for additional information.
    
    This APAR/PTF changes the text of SQL code -607.  The change
    will be documented in the DB2 Codes manual and in the
    Information Management Software for z/OS Solutions Information
    Center.
    
    A new bullet under the example for SQL code -607:
    
    - The operation is on a directory object and the unit of work
    could not be converted to UR. For example:
    
    UPDATE T1 SET C1 =
    (SELECT C1 FROM T1) WHERE EXISTS(SELECT LGR SYSIBM.SYSLGRNX);
    
    in this case, the SELECT against a directory object can not
    be converted to UR.
    
    ***Action for PM35190:
    
    See PM35190 APAR/PTF text for additional information.
    
    PM35190 is the enabling APAR that introduces the new function
    support to allow selects from some Directory objects.  Earlier,
    a pre-conditioning APAR PM42331 was delivered and will be
    needed.  In a data sharing group, this pre-conditioning APAR
    should be applied to all members before applying this ENABLING
    APAR to any member.  The new function will be enabled once this
    ENABLING APAR is applied and DB2 enters NFM or once this
    ENABLING APAR is applied and a special CATMAINT is run with the
    input:
    
    CATMAINT UPDATE UNLDDN PM35190
    

Problem conclusion

Temporary fix

Comments

  • See above.
    

APAR Information

  • APAR number

    PM35190

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-18

  • Closed date

    2011-11-02

  • Last modified date

    2011-12-02

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

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

    UK73478

Modules/Macros

  •    DSNTESQ  DSNUECM0 DSNUECSE
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK73478

       UP11/11/18 P F111

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM35190

Modified date:

2011-12-02

Translate my page

Machine Translation

Content navigation