PK47712: FPEV0169E WITH MON TRACE NOT AUTOSTARTED SITUATION.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Omeg Performance Expert on z/OS.
  When Omegamon DB2 PE is started, it issues the error message:
  FPEV0169E  MSTR SERVER INSTANCE FOR DB2 SUBSYSTEM DSNV STOPPED
  WITH ERROR CODE 8
  On the other hand, the problem doesn't arise in case the DB2
  trace was manually started previously.
  .
  So far PE Server relied on the start up of the trace performed
  by another task out of the Omegamon address space.
  As we can see from different PMRs there are conditions where the
  traces have not been started automatcially and that the clients
  are not willing to start the traces manually or update the DB2
  configuration to have the traces stated automatically in the
  course of the DB2 start up.
  We will add functionality to the PE Server code to have the
  traces started upon PE server start up in case they are not
  running already.
  .
  Circumvention:
  Configure DB2 to start the traces automatically during start up
  of the DB2 subsystem.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   PE Server                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the OMEGAMON Server subtask        *
  *                      PESERVER starts a monitoring PESERVER   *
  *                      instance for a DB2 subsystem and the    *
  *                      DB2 monitor trace is not started, the   *
  *                      PESERVER instance issues message        *
  *                      FPEV0128S followed by message FPEV169E  *
  *                      and stops.                              *
  *                                                              *
  *                      for V310                                *
  *                      The service level of the                *
  *                      OMEGAMON server subtask PESERVER        *
  *                      FPEV0000I  DATA SERVER INITIALIZATION   *
  *                      FPEV0114I  PTF BUILD IS 07.248          *
  *                                                              *
  *                      for V410                                *
  *                      The service level of the                *
  *                      OMEGAMON server subtask PESERVER        *
  *                      FPEV0000I  DATA SERVER INITIALIZATION   *
  *                      FPEV0114I  PTF BUILD IS 07.248          *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF.                              *
  ****************************************************************
  When the OMEGAMON Server subtask PESERVER starts a monitoring
  PESERVER instance for a DB2 subsystem and the DB2 monitor trace
  is not started, the PESERVER instance issues message FPEV0128S
  followed by message FPEV0169E and stops.
  

Problem conclusion

• When the OMEGAMON Server subtask PESERVER starts a monitoring
  PESERVER instance for a DB2 subsystem and the DB2 monitor trace
  is not started, the PESERVER instance starts the monitor trace
  by issuing the DB2 command '-start trace(mon)' with scope local
  or group depending on whether monitoring of a data sharing
  group is configured. The issued DB2 command and corresponding
  response from DB2 is written to the server log.
  DB2 will just start monitor trace class 01. Additional classes
  are not started automatically by PESERVER because they might
  cause undesired overhead. Additional trace classes (2,3,7,8)
  have to be started manually when desired.
  
  KEYWORDS :
  FPEV0128S FPEV0169E PESERVER MONITOR TRACE NOT STARTED
  

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:

  UK28910 UK28911

Modules/Macros

•    DGOVMIDI DGOVMSTR DGOVM001
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSY UK28910

     UP07/09/07 P F709

• R410 PSY UK28911

     UP07/09/07 P F709

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.