timmzzz 060000RTR7 Visits (4212)
Having a robust preventive maintenance process is a best practice in managing any IT
environment including z/OS. By avoiding known defects, which can have a major impact on
the functioning of the system, preventive maintenance improves availability. Having a
proactive preventive service strategy reduces the number of rediscovered defects and avoids
unplanned outages. IBM recommends that preventive maintenance be installed at least two to
four times a year. In addition, IBM recommends that HIPER, PE Fix, Security/Integrity and
Pervasive PTFs be installed more frequently.
Read more about a solid preventive maintenance strategy here.
Additional information about the RSU and CST, can be found at the CST website at:
flodubois 270000K6H5 Visits (3609)
Fix Category HOLDDATA (FIXCAT)
What is a fix category? A fix category is an identifier used to group and associate PTFs to a particular category of software fixes. A fix category might be used to identify a group of fixes that are required to support a particular hardware device, or to provide a particular software function. Fix categories are supplied to you in the form of SMP/E FIXCAT HOLDDATA statements. Each FIXCAT HOLDDATA statement associates an APAR and its related fixing PTF to one or more fix categories.
For more information , please refer to http
Current list of FIXCAT HOLDs for DB2 for z/OS
SYSPLEXDS Fixes that enable the sysplex data sharing function or fixes required for data sharing
DB2COEXIST/K Fixes that enable DB2 releases to coexist when in data sharing mode
DB2PARALL/K Fixes for problems with the DB2 parallelism function
DB2STGLK/K Fixes for DB2 storage leak problems
DB2OVRLAY/K Fixes for DB2 storage overlay problems
DB2INCORR/K Fixes for DB2 SQL incorrect output problems
DB2MIGV9/K Fixes that allow the prior release of DB2 to migrate to or fall back from DB2 V9
DB2MIGV10/K Fixes that allow prior releases of DB2 to migrate to or fall back from DB2 V10
ISAOPT/K Fixes required for z/OS software products to support the IBM Smart Analytics Optimizer
agburke 060001QPDN Visits (1872)
Several customers have asked about how the Consolidated Service Test and Recommended Service Upgrades are handled once a release goes out of service.
The CST testing only runs for N and N-1 releases, so when DB2 10 GAed in October of 2010, DB2 V8 was removed from the CST cycle.
For the RSUs we will continue bundling PTFs quarterly with monthly updates for a release even after the end of support date, as long as PTFs are still closing.
As an exmple, due to customers purchasing extended support for the release V7 had PTFs close almost 2 years after the end of service. Those eventually got rolled up into an RSU. As long as the customer is still paying their Monthly License Charge for the release they are eligible to pull the newest RSU down from Shopz.
agburke 060001QPDN Visits (1623)
The DB2 10 for z/OS and IRLM 2.3 product tapes have been refreshed. All DB2 10 for z/OS and IRLM 2.3 PTFs that were closed and available up to and including December 1, 2011, (Service level PDO 1148) have been integrated into refreshed product tapes. These product tapes are available for new orders placed on or after January 27, 2012.