Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC62872 Status: Closed

SUPPORT FOR DB2_WORKLOAD=WMQWF TO BE ADDED FOR IBM WEBSPHERE MQ WORKFLOW
ENVIRONMENTS

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
A WMQWF option is going to be added to the DB2_WORKLOAD 
aggregrate 
registry variable for use in IBM WebSphere MQ Workflow 
environments.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 LUW server environments                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* WMQWF is not a valid option for the DB2_WORKLOAD aggregrate  * 
* registry variable.                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.5 FP6 or higher                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
WMQWF is a valid option for DB2_WORKLOAD registry variable as of 
DB2 V9.5 FP6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC62879 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.08.2009
22.04.2010
22.04.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)