IBM Support

PI99075: UNLOAD SHRLEVEL CHANGE ISOLATION UR FOUND 0 ROWS

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • SHRLEVEL CHANGE  ISOLATION UR currently defaults to REGISTER NO.
    
    This default means that only rows that have been externalized to
    dasd will be read for the unload. Any rows that are in buffers,
    either local or group will not be unloaded.  This behavior for
    the new version 12 keyword is a change from version 11 behavior
    that has no such keyword.
    
    In order for an unload in version 12 to have the same results as
    an unload in version 11, then REGISTER YES must be specified.
    This can be problematic for a data sharing group that is in
    co-existence mode since the keyword is not recognized by version
    11.
    
    This apar is to change the default to REGISTER YES.
    

Local fix

  • Specify REGISTER YES for version 11 behavior in version 12.  In
    co-existence data sharing groups, the unload using the REGISTER
    keyword must run on a version 12 member.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 users of the UNLOAD utility with                  *
    * SHRLEVEL CHANGE ISOLATION UR                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * For UNLOAD SHRLEVEL CHANGE ISOLATION                         *
    * UR, the default value for the                                *
    * REGISTER keyword is NO.                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    The keyword REGISTER was added to the UNLOAD utility in
    Db2 12 with the default REGISTER NO.  The default in
    Db2 12 is causing a difference in behavior from Db2 11 and
    the resulting SYSREC is missing expected records.  The
    behavior of REGISTER NO is working as designed, but users
    have no easy way to force REGISTER YES unless they modify
    every UNLOAD statement.
    
    PI99075 introduces the following changes to externals:
    Utility Guide and Reference
    Changed option for utility UNLOAD:
       .-SHRLEVEL--CHANGE--ISOLATION--CS--+------------------+----.
       |                                  '-SKIP LOCKED DATA-'    |
    >--+----------------------------------------------------------+
       |                                  .-REGISTER--YES-----.   |
       '-SHRLEVEL-+-CHANGE--ISOLATION-UR--+-------------------+-+-'
                  |                       '-REGISTER--NO------' |
                  '-REFERENCE-----------------------------------'
    
    >>Remove the following Note, the default is always REGISTER YES
    >>Notes:
    >>  REGISTER YES is the default for base table spaces with LOB
    >>  or XML columns.
    
    
    REGISTER
    Specifies whether, when ISOLATION UR and SHRLEVEL
    CHANGE behaviors are in effect, pages that are read by
    the UNLOAD utility in a data sharing environment are
    >>       registered with the coupling facility.  The default is
    >>       REGISTER YES.
    
    NO
    Indicates that pages that are read by the UNLOAD
    utility are not registered with the coupling
    facility. Use of this option reduces data sharing
    overhead, but might cause UNLOAD utility
    processing to miss data changes that are present
    >>          in the group buffer pool or the local buffer pool,
    >>          as only data written to dasd is unloaded.  Missed
    data changes result in reduced data currency in the
    result data set.
    
    REGISTER NO is not supported for base table spaces
    with LOB or XML columns. If REGISTER NO is not
    specified explicitly for a base table space with
    LOB or XML columns, Db2 sets the REGISTER value to
    YES. If REGISTER NO is explicitly
    specified for a base table space with LOB or XML
    columns, Db2 issues an error.
    
    YES
    Indicates that pages that are read by the UNLOAD
    utility are registered with the coupling facility.
    
    Information about this changed function will be
    included soon in IBM Knowledge Center:
    http://www.ibm.com/support/knowledgecenter/SSEPEK/
    db2z_prodhome.html
    

Problem conclusion

  • Modified UNLOAD to make the default REGISTER YES.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI99075

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-06-12

  • Closed date

    2018-07-03

  • Last modified date

    2018-08-02

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

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

    UI57005

Modules/Macros

  • DSNUGDDS
    

Publications Referenced
SC278860        

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI57005

       UP18/07/18 P F807

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.



Document information

More support for: DB2 for z/OS

Software version: 12.0

Reference #: PI99075

Modified date: 02 August 2018


Translate this page: