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

DB2DIAG RETURN CODE IS 0 REGARDLESS OF MATCHES WERE FOUND OR NOT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Regardless of matches were found or not, db2diag always returns 
0. 
For example: 
 
$ db2diag -l Critical 
 
$ echo $? 
0 
 
$ db2diag -l Error 
2010-01-07-15.43.23.068247-300 E5614458E495        LEVEL: Error 
PID     : 12345                TID  : 183102335328 PROC : 
db2sysc 
INSTANCE: dbguest1             NODE : 000 
EDUID   : 1                    EDUNAME: db2sysc 
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr, 
probe:50 
MESSAGE : ADM7006E  The SVCENAME DBM configuration parameter was 
not 
          configured.  Update the SVCENAME configuration 
parameter using the 
          service name defined in the TCP/IP services file. 
 
$ echo $? 
0 
 
The exit code should be 1 if no matches were found.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2diag users who use scripts to call db2diag and check      * 
* thereturn code                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2diag users who use scripts to call db2diag and check      * 
* thereturn code were not seeing proper return codes from      * 
* db2diag                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Available db2_v97fp2 onwards                                 * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Code was fixed to solve this problem
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.01.2010
19.05.2010
19.05.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList