A fix is available
APAR status
Closed as program error.
Error description
IN ISPF OLM periodic EXCP is running and the user exit is active. Thus, Exception messages appear in the OM PE server's started Task informing me about the periodic exceptions which occurred. But when the REINIT command is used in ISPF OLM then the User Exit becomes disabled. So no exception messages appear in the OM PE server's started task anymore. If you open the Exception configuration panel in ISPF OLM then the user exit flag is set to active. But there are no exception messages in the started task. If you deactiveate the user exit in that exception configuration panel and activate it again then the exception messages start to appear in the OM PE server's started task. The problem is that the REINIT command does re-init the periodic exception processing, but it disregards the setting of the user exit.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - PE Server subtask * * - ISPF Monitoring dialogs * **************************************************************** * PROBLEM DESCRIPTION: The ISPF OLM command REINIT deactivates * * the PEServer AUTOEXCEPTION User-Exit. * * After the REINIT command no more * * periodic exceptions are written to the * * PEServer log JESYSMSG. * **************************************************************** * RECOMMENDATION: Apply this PTF * **************************************************************** PROBLEM SUMMARY: The ISPF OLM command REINIT deactivates the PEServer AUTOEXCEPTION User-Exit. After the REINIT command no more periodic exceptions are written to the PEServer log JESYSMSG. PROBLEM CONCLUSION: If the PEServer parameter for Periodic Exception User Exit is set to AUTOEXCPEXIT=Y then the periodic exceptions are written to the PEServer log JESYSMSG after the ISPF OLM command REINIT. KEYWORDS: REINIT-CMD AUTOEXCEPTION PERIODIC-EXCEPTION USER-EXIT
Problem conclusion
If the PEServer parameter for Periodic Exception User Exit is set to AUTOEXCPEXIT=Y then the periodic exceptions are written to the PEServer log JESYSMSG after the ISPF OLM command REINIT. KEYWORDS: REINIT-CMD AUTOEXCEPTION PERIODIC-EXCEPTION USER-EXIT
Temporary fix
Comments
APAR Information
APAR number
PK76970
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
2008-12-05
Closed date
2009-04-28
Last modified date
2009-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK46004
Modules/Macros
DGOVMSTR DGOVUM00 FPEUFLSP FPEUFLS2
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSY UK46004
UP09/05/01 P F904
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:
02 May 2009