A fix is available
APAR status
Closed as program error.
Error description
Setting diagnostics parameter EPTT can result in a false alert SDUMP. For example, after this MODIFY command: F CANSO2,F PESERVER,F DB2A,EPTT=30 . An SVC dump with this title was taken: Dump Title: FPEVDB2I - DB2 ADDRESS SPACES FOR DB2A
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - PE Server subtask * **************************************************************** * PROBLEM DESCRIPTION: 1. When the Elapsed Processing Timeout * * Threshold (EPTT) is set for the PE * * Server subtask, message FPEV2103I is * * issued followed by message FPEV2101I * * and the corresponding dump although * * the actual data retrieval requests * * complete within the specified * * threshold. * * 2. When two OMEGAMON started tasks * * are configured to monitor the same * * DB2 subsystem on the same LPAR and * * both are started, the monitoring PE * * Server subtask which becomes attached * * last abends with system completion * * code 23E. * * * **************************************************************** * RECOMMENDATION: Apply this PTF * * * **************************************************************** PROBLEM SUMMARY: 1. Depending on the MVS dispatching sequence of the PE Server subtasks, the subtask controlling the elapsed processing time for a data retrieval request might miss the completion of the request and thus falsly report a threshold violation. 2. During termination the PE Server subtask tries to detach the DB2 interface subtask which was not attached before and is abended with S23E. PROBLEM CONCLUSION: 1. The code has been modified to become independent of the MVS dispatching sequence of the PE Server subtasks. 2. The code has been corrected. The already existing messages FPEV0164I, FPEV0015W and FPEV0224I are issued to report the situation.
Problem conclusion
1. The code has been modified to become independent of the MVS dispatching sequence of the PE Server subtasks. 2. The code has been corrected. The already existing messages FPEV0164I, FPEV0015W and FPEV0224I are issued to report the situation. KEYWORDS : FPEV2103I FPEV2101I EPTT FPEV0015W ABEND 23E
Temporary fix
Comments
APAR Information
APAR number
PM66299
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
2012-06-06
Closed date
2012-09-07
Last modified date
2012-10-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK81596 UK81597
Modules/Macros
DGOVMSTR DGOVM002 FPEVDB2I FPEVM000
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:
01 October 2012