DB2 CONNECT / DB2CONNCT / 970 - DB2

When AUTH_ID is used as a part of the filter in the Activity 
Monitor tool the error is being reported back: 
 
"AUTH_ID" is not valid in the context where it is used 
 
The SQL statement generated by Activity Monitor is failing as 
well: 
 
C:\Program Files\IBM\SQLLIB_02\BIN>db2 CALL 
SYSPROC.AM_GET_RPT(-2, 3, 'AUTH_ID = ''DB2INST2''', 10) 
 
SQL0206N  "AUTH_ID" is not valid in the context where it is 
used.  SQLSTATE=42703 
 
The reason for this is: v8 is using AUTH_ID in the call of 
SYSPROC>AM_GET_RPT, but starting from v9.1 we started to use 
PRIMARY_AUTH_ID. 
 
GUI part of Activity Monitor has to be changed to use 
PRIMARY_AUTH_ID instead of AUTH_ID while calling 
SYSPROC.AM_GET_RPT SP.  Description of SYSPROC.AM_GET_RPT  on 
Infocenter also needs to be changed. This APAR will address 
those changes.

User's affected: All 
Problem Sumamry: When AITH_ID is used as a part of the filter in 
the Activity 
Monitor tool the error is being reported back: 
 
"AUTH_ID" is not valid in the context where it is used

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
 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
 

Problem was first fixed in Version 9.7 Fix Pack 1

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

02.07.2009
21.12.2009
21.12.2009

9.7.FP1