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 IC87379 Status: Closed

ERRONEOUS MESSAGE "ENSURE APAR PM24292 IS INSTALLED" WHILE
CONNECTING TO ISERIES SERVER

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
FUNCTION: DB2 UDB, DRDA Application Requester, 
sqljrParseMgrLvls, 
probe:488 
 
MESSAGE : Downlevel member cannot be used for transaction-level 
workload 
          balancing or automatic client reroute. If you are 
accessing a 
          DB2 for z/OS sysplex, ensure APAR PM24292 is installed 
on that system.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All connecting to iSeries servers                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 fp3 or just ignore this message             * 
****************************************************************
Local Fix:
Catalog DCS entry for the database without 6th SYSPLEX 
parameter. This will explicitly disables SYSPLEX support on db2 
connect server and eliminates the error message.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in v10.1 fp3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.10.2012
18.10.2013
18.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList