A fix is available
APAR status
Closed as program error.
Error description
When OMPE is configured with TCMDSECU=USER and a user that does not have DB2 authority to cancel a thread issues the TCMD command to cancel a thread, the OMPE task will lose its authority to issue IFI READS and READA commands. . User will see the following at the screen where the TCMD command was issued . =============================================================== tcmd . + Cancel Thread has been issued for Token=004374 + + -CANCEL THREAD(004374) + + <<< error issuing db2 command >>> . Afterwards Classic Interface shows no active thread. . ================================================================ . The SYSPRINT will show something like this FPEV0567W DATA FOR THIS MEMBER DB1U ****************************************************** DB1U DB2 Auth Signon failed (RRSAF): DB1U Return code .......... : 8 ( 00000008x) DB1U Reason code .......... : 15925300 ( 00F30034x) DB1U Detecting module ..... : FPEVDB22 DB1U Error message ........ : DB1U +-------------------------------------------------- DB1U | PLAN DB2PM DOES NOT EXIST OR IS NOT AUTHORIZED. DB1U +-------------------------------------------------- DB1U User action .......... : DB1U +-------------------------------------------------- DB1U | PLAN DB2PM IS CREATED IF IT DOES NOT EXIST. IF T DB1U | PROBLEM PERSISTS, ENSURE THE USER/GROUP ID DB2PM DB1U | IS ALLOWED TO ACCESS PLAN. THEN RESTART PE SERVE DB1U +-------------------------------------------------- DB1U ****************************************************** . When TCMDSECU=USER the DB2 authorization is obtained for the logged on USER. When TCMDSECU=STC the DB2 authorization is obtained for the OMPE Started Task (STC). When the TCMD command is issued to cancel a thread, the DB2 CANCEL THREAD command is issued under the DB2 authority identified by the TCMDSECU value. If the appropriate DB2 authority is not held, the DB2 CANCEL THREAD command will fail. .
Local fix
Recycle the montoring of the OMPE STC . To STOP a DB2 instance, please issue: . F cccccccc,F PESERVER,P db2ssid . To START a DB2 instance, please issue: . F cccccccc,F PESERVER,S db2ssid . where cccccccc is the OMPE STC name and db2ssid is the DB2 subsystem name
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - OMEGAMON collector * * - PE Server subtask * * - Classic Interface * * - ISPF Monitoring dialogs * * - Performance Expert Client * **************************************************************** * PROBLEM DESCRIPTION: CANCEL THREAD (TCMD) command issued * * under unauthorized userid in Classic * * Interface fails and makes PE Server * * Subtask inoperative. * * * **************************************************************** * RECOMMENDATION: Apply this PTF * * * **************************************************************** PROBLEM SUMMARY: When OMEGAMON Collector is configured with TCMDSECU=USER and a user that does not have DB2 authority to cancel a thread issues the TCMD command to cancel a thread, the PE Server subtask loses its authority to perform IFI READS and READA commands under OMPEUSER or other designated userid. User will see the following at the screen where the TCMD command was issued: =============================================================== tcmd + Cancel Thread has been issued for Token=nnnnnn + + -CANCEL THREAD(nnnnnn) + + <<< error issuing db2 command >>> Afterwards the Classic Interface, Performance Expert Client and ISPF Monitoring dialogs show no active thread. The SYSPRINT of OMEGAMON STC may show messages like below: FPEV0567W DATA FOR THIS MEMBER DB1U ****************************************************** DB1U DB2 Auth Signon failed (RRSAF): DB1U Return code .......... : 8 ( 00000008x) DB1U Reason code .......... : 15925300 ( 00F30034x) DB1U Detecting module ..... : FPEVDB22 DB1U Error message ........ : DB1U +-------------------------------------------------- DB1U | PLAN DB2PM DOES NOT EXIST OR IS NOT AUTHORIZED. DB1U +-------------------------------------------------- DB1U User action .......... : DB1U +-------------------------------------------------- DB1U | PLAN DB2PM IS CREATED IF IT DOES NOT EXIST. IF T DB1U | PROBLEM PERSISTS, ENSURE THE USER/GROUP ID DB2PM DB1U | IS ALLOWED TO ACCESS PLAN. THEN RESTART PE SERVE DB1U +-------------------------------------------------- DB1U ****************************************************** PROBLEM CONCLUSION: The code of PE Server Subtask has been modified to solve this problem. The Classic Interface, Performance Expert Client and ISPF Monitoring dialogs must show active threads when an unauthorized user tries to cancel a thread. The warning messages "error issuing db2 command" and "DB2 Auth Signon failed..." should appear in exactly the same circumstances as it was before applying this PTF. Comment. When TCMDSECU=USER is specified, the DB2 authorization is obtained for the logged on USER. When TCMDSECU=STC is specified, the DB2 authorization is obtained for the OMPE Started Task. When the TCMD command is issued to cancel a thread, the DB2 CANCEL THREAD command is issued under the DB2 authority identified by the TCMDSECU value. If the appropriate DB2 authority is not held, the DB2 CANCEL THREAD command fails.
Problem conclusion
The code of PE Server Subtask has been modified to solve this problem. The Classic Interface, Performance Expert Client and ISPF Monitoring dialogs must show active threads when an unauthorized user tries to cancel a thread. The warning messages "error issuing db2 command" and "DB2 Auth Signon failed..." should appear in exactly the same circumstances as it was before applying this PTF. Comment. When TCMDSECU=USER is specified, the DB2 authorization is obtained for the logged on USER. When TCMDSECU=STC is specified, the DB2 authorization is obtained for the OMPE Started Task. When the TCMD command is issued to cancel a thread, the DB2 CANCEL THREAD command is issued under the DB2 authority identified by the TCMDSECU value. If the appropriate DB2 authority is not held, the DB2 CANCEL THREAD command fails. KEYWORDS : CANCEL THREAD UNAUTHORIZED USER CLASSIC INTERFACE 00F30034
Temporary fix
Comments
APAR Information
APAR number
PM48916
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
510
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-28
Closed date
2011-11-29
Last modified date
2011-12-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK74297 UK74298
Modules/Macros
DGOVMSTR DGOZCAFM FPE@DB2I FPEVDB2I FPEVZRAC
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 December 2011