PK37807: RESTART OF AUTOEXCEPTION OR PERIODIC EXCEPTION STOPS AGAIN IMMEDIATELY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After AUTOEXCEPTION experienced a DB2 timeout, the OM PE server
  should restart it. This does not work. The server only states
  the following messages 3 times for each monitored DB2 subsystem:
  FPEV0409I  PERIODIC EXCEPTION PROCESSING TASK STARTED FOR USER
  FPEV0413I  PERIODIC EXCEPTION PROCESSING ACTIVATED FOR USER
  FPEV0410I  PERIODIC EXCEPTION PROCESSING TASK STOPPING FOR USER
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 _   PE Server                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: After AUTOEXCEPTION experienced a DB2   *
  *                      timeout, the OM PE Server should        *
  *                      restart it. This does not work. The     *
  *                      server only states the following        *
  *                      messages 3 times for each monitored     *
  *                      DB2 subsystem:                          *
  *                      FPEV0409I  PERIODIC EXCEPTION           *
  *                      PROCESSING TASK STARTED FOR USER        *
  *                                                              *
  *                      FPEV0413I  PERIODIC EXCEPTION           *
  *                      PROCESSING ACTIVATED FOR USER           *
  *                                                              *
  *                      FPEV0410I  PERIODIC EXCEPTION           *
  *                      PROCESSING TASK STOPPING FOR USER       *
  ****************************************************************
  * RECOMMENDATION: APPLY this ptf                               *
  ****************************************************************
  After a DB2 timeout the OM PE server is stopped. This is
  the expected behaviour. But after detaching the pEXCP task the
  variable that remembers the timeout is not reset. Thus, after
  restarting the OM PE server the server thinks that another
  timeout occurred and so pEXCP is stopped again and again
  without resetting the timeout variable. This happens 3 times
  before the OM PE server finally stops restarting pEXCP.
  

Problem conclusion

• Variable that remembers error conditions is reset after detach
  of exception processing.
  -------------------------------------------
  KEYWORDS: FPEV0409I FPEV0413I FPEV0410I TIMEOUT EXCEPTION
            PROCESSING AUTOEXCEPTION AUTOMATIC
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK21468 PK39690 PK40348

Modules/Macros

•    DGOVUM00
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSY UK21468

     UP07/01/26 P F701

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.