A fix is available
APAR status
Closed as program error.
Error description
PE ISPF OLM and OmPE show different Status for DBAT Thread: PE ISPF OLM: Thread Identification Primauth . . . . . . : SIEBSSO Correlation Name . . : siebmtsh Planname . . . . . . : DISTSERV Connection type . . . : DRDA Connection ID . . . : SERVER Type . . . . . . . . : DBAT Requesting Location : 145.72.217.20 Status . . . . . . . : I/O OmPE: Thread Activity K User Defined Functions K ---------------------- ------------K ---------------------- -------------K DB2 Status WAIT-REMREQK TCB Time (SQL) 00:00:00.000K MVS Status K Wait for TCB Time 00:00:00.000K The APAR will fix WAIT-LOCK or WAIT-SERVICE incorrect status also.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - Classic Interface * **************************************************************** * PROBLEM DESCRIPTION: Wrong status for distributed threads * * without AUTO-COMMIT is shown while DB2 * * is waiting for commit after SQL * * processing. Its status is shown as * * WAIT-SEVICE or WAIT-LOCK or * * WAIT-LOGQSCE. That takes place after * * PK89237/UK49941 application. * **************************************************************** * RECOMMENDATION: Apply this PTF * * * **************************************************************** PROBLEM SUMMARY: Incorrect status of distributed threads is shown (WAIT-SEVICE or WAIT-LOCK or WAIT-LOGQSCE) while DB2 is waiting for commit after SQL processing. PROBLEM CONCLUSION: Change code to display correct thread status while DB2 is waiting for commit.
Problem conclusion
Change code to display correct thread status while DB2 is waiting for commit. KEYWORDS : AUTO-COMMIT WAIT-SEVICE WAIT-LOCK WAIT-LOGQSCE
Temporary fix
Comments
APAR Information
APAR number
PM00760
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-10
Closed date
2009-11-16
Last modified date
2010-01-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK51911 UK51912
Modules/Macros
B390SPA1 B390SPA2
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":"410","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":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
29 January 2010