PM07261: OMPE DOESN'T RECOGNIZE DB2 AFTER STARTING DB2 WITH ACCESS(MAINT)AND RESTARTING IN FULL ACCESS MODE AFTER MAINTENANCE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• OmPE doesn't recognize DB2 after starting DB2 with ACCESS(MAINT)
  and restarting in full ACCESS mode after maintenance: DB2 starts
  with ACCESS(MAINT), OmPE receives ' 00F30056 'x (rc00F30056) and
  stops monitoring this DB2, even when DB2 is re-started again in
  full access mode. DB2 is Not Active on ZRLOG panel.
  

Local fix

• /F <STC_name>,F PESERVER,S <DB2_SSID> to start the PE Server
  subtask
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   PE Server subtask                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a DB2 Subsystem is started with    *
  *                      option ACCESS(MAINT), the OMEGAMON      *
  *                      Collector subtask PE Server does not    *
  *                      recognize the restart of the DB2        *
  *                      Subsystem in full access mode.          *
  *                      Monitoring for this DB2 Subsystem is    *
  *                      not started.                            *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  *                                                              *
  ****************************************************************
  PROBLEM SUMMARY:
  When a DB2 Subsystem is started with option ACCESS(MAINT), the
  PE Server main task receives reason code '00F30056' as response
  to an identify request and does not start a monitoring PE
  Server subtask. The restart of the DB2 Subsystem in full access
  mode is not recognized because the PE Server main task could
  not subscribe to the DB2 start ECB.
  
  PROBLEM CONCLUSION:
  When the PE Server main task receives reason code '00F30056' as
  response to an identify request, it tries to connect to the DB2
  Subsystem in intervals of 5 minutes. When the DB2 Subsystem is
  restarted in full access mode, the identify request of the PE
  Server main task completes successful and a monitoring PE Server
  subtask is started.
  DB2 Subsystems started in restricted access mode are indicated
  with status RESTRICT in message FPEV0187I, which is issued to
  the PE Server log as response to a display command.
  

Problem conclusion

• When the PE Server main task receives reason code '00F30056' as
  response to an identify request, it tries to connect to the DB2
  Subsystem in intervals of 5 minutes. When the DB2 Subsystem is
  restarted in full access mode, the identify request of the PE
  Server main task completes successful and a monitoring PE Server
  subtask is started.
  DB2 Subsystems started in restricted access mode are indicated
  with status RESTRICT in message FPEV0187I, which is issued to
  the PE Server log as response to a display command.
  
  KEYWORDS :
  DB2 MAINTENANCE RESTART PE SERVER SUBTASK NOT STARTED
  NO MONITORING
  

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:

  UK59362

Modules/Macros

• DGOVISI  DGOVISIT DGOVMDSP DGOVMSTR DGOVPIG1
  DGOVPP1  DGOVRTG0 DGOVRTG1 DGOVRTG2
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R420 PSY UK59362

     UP10/08/06 P F008

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.