A fix is available
APAR status
Closed as new function.
Error description
With the implementation of this APAR PK62027, the group wide shut down is no longer required in order to benefit from LOB performance improvements in V9. The V9 LOB performance improvement will take effect as soon as the system is migrated to V9 NFM and the locking protocol will remain at 2. DB2 subsystems that are already at locking protocol 3 and apply this apar will remain at protocol 3 until the next group-wide shutdown, at which point they will revert to protocol 2. This will have no impact on the LOB locking enhancements which will solely be dependent on V9 NFM once this APAR is applied. Code vehicle for DCR DK1043.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 for z/OS users of LOB data. * **************************************************************** * PROBLEM DESCRIPTION: Enable V9 LOB locking enhancements * * in a data sharing environment * * without requiring a group-wide outage. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 Version 9 introduced a new data sharing locking protocol called "locking protocol 3" (LP3) for the new LOB locking performance improvements. A group wide outage is required in order to activate LP3 in V9 NFM.
Problem conclusion
Temporary fix
Comments
With the implementation of this APAR PK62027, the group wide shut down is no longer required in order to benefit from LOB performance improvements in V9. The V9 LOB performance improvement will take effect as soon as the system is migrated to V9 NFM. DB2 subsystems that are already at locking protocol 3 will remain at protocol 3 until the next group-wide shutdown, at which point they will revert to protocol 2. This will have no impact on the LOB locking enhancements which will solely be dependent on V9 NFM once this APAR is applied.
APAR Information
APAR number
PK62027
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-03-02
Closed date
2008-08-13
Last modified date
2009-05-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK38906
Modules/Macros
DSNIDILS DSNILOBL DSNILREP DSNIRELK DSNISELL DSNISRTI DSNISUPI DSNOALLO DSNOCHLO DSNODCRL DSNOFRLC DSNOTCSO DSN7GJON
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
R910 PSY UK38906
UP08/08/28 P F808
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
08 May 2009