home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC99344 Status: Closed

DB2PDCFG -FODC[DBCFG|DBMCFG|TRAPRESILIENCE] STATUS DOES NOT WORK FOR USER
WITH ONLY SYSMON AUTHORITY

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If user has SYSMON authority only, the user won't be able to 
alter any db2pdcfg flags through following db2pdcfg options: 
-catch 
-cos 
-dbcfg 
-dbmcfg 
-fodc 
-trapresilience 
This is expected, but the user should be able to query the 
status of these options 
by specifying status sub-option. E.g. 
db2pdcfg -fodc status 
The problem is that, only 
db2pdcfg -catch status 
& 
db2pdcfg -cos status 
works for user with only SYSMON authority. The expected 
behaviour should be that other options with status sub-option 
should also work for user with only SYSMON authority.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.1 Fixpack 5                            * 
****************************************************************
Local Fix:
Solution
First Fixed in version 10.1 Fixpack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.02.2014
27.11.2015
27.11.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList