PQ82150: The Scheduler function fails when using DB2 UDB for z/OS.

 Fixes are available

5.1.0.5: WebSphere Application Server V5.1.0 Cumulative Fix 5
5.1.1: WebSphere Application Server Version 5.1 Fix Pack 1 (Version 5.1.1)



APAR status
Closed as program error.

Error description
When using the scheduler function on DB2 UDB for z/OS the
following error occurs:

Initialize Database helper: Could not detect database vendor.
Vendor String was DSN07010.

This is also reported in btop defect 185403 and zwas defect
MD18825.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Enterprise      *
*                 users of DB2 UDB for z/OS and the            *
*                 Scheduler function.                          *
****************************************************************
* PROBLEM DESCRIPTION: The scheduler function fails when       *
*                      using DB2 UDB for z/OS with the         *
*                      following error:                        *
*                      Could not detect database vendor.       *
*                      Vendor string was DSN07010              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the scheduler function initializes, it retrieves the
database vendor name from the database and performs a series
of checks on this vendor name to determine the database type.
The DB2 UDB database returns the following string for vendor:
The information has the form pppvvrrm, where:
ppp is:
DSN for DB2 UDB for z/OS and OS/390

QSQ for DB2 UDB for iSeries

SQL for DB2 UDB for UWO

vv is a two-digit version identifier such as '07'.
rr is a two-digit release identifier such as '01'.
m is a one-digit modification level such as '0'.

The code was not checking for this type of vendor name.
While the problem was reported on z/OS, it appears this
problem may occur on other platforms.
Problem conclusion
The code was fixed to check if the vendor name starts with
DSN, QSQ, or SQL.
Temporary fix Comments
APAR information
APAR number PQ82150
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 10W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-12-12
Closed date 2003-12-19
Last modified date 2003-12-19

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EXTHELPR          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 10W
Software edition:
Reference #: PQ82150
IBM Group: Software Group
Modified date: Dec 19, 2003