PK25976: FPEV0263E DB2Z AUTOMATIC EXCP NOT STARTED - NO VALID THRESHOLD RECORDS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When starting the OMEGAMON XE/PE server with an empty threshold
  dataset or if the dataset has been populated with the contents
  of RKO2DATA(DGOETV41) (as per Ch6 of the Monitoring from ISPF
  Monitor manual.) we get message
  FPEV0263E DB2Z AUTOMATIC EXCP NOT STARTED - NO VALID THRESHOLD
  RECORDS
  It has been found member DGOETV41 has invalid records.
  

Local fix

• After ensuring the threshold dataset is empty, create an
  exception record using the ISPF PE panel option 4. Restart
  OMEGDB2 and the the automatic exception processing should start
  ok. IE message FPEV0261I  DB2Z AUTOMATIC EXCP STARTED will be
  received
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM V310            *
  *                 users of component:                          *
  *                 -   OMEGAMON Server                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using the example threshold        *
  *                      dataset RKO2DATA(DGOETV41)              *
  *                      the server considers all                *
  *                      thresholds within that dataset          *
  *                      to be invalid. Comments in the          *
  *                      dataset also result in incorrect        *
  *                      messages. Thus the server               *
  *                      does not start AutoException.           *
  *                                                              *
  *                      Automatic Exception Processing ends     *
  *                      with the message:                       *
  *                                                              *
  *                      "FPEV0263E DB2Z AUTOMATIC EXCP NOT      *
  *                       STARTED"                               *
  *                      - NO VALID THRESHOLD RECORDS"           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• 1. Now the server works correctly with comments included in a
     threshold dataset.
  
  2. The example threshold dataset has been replaced, and does
     not contain asterisks for warning- or problem thresholds.
     Thus performing "Exception Profiling" is no longer required
     to make all thresholds within the example threshold dataset
     valid.
  
  * The components of                                            *
  * IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS    *
  * V310 and IBM Tivoli OMEGAMON XE for DB2 Performance Monitor  *
  * on z/OS V310 have the following service level:               *
  *                                                              *
  * OMEGAMON Server:                                             *
  *    FPEV0000I  DATA SERVER INITIALIZATION BEGINS              *
  *    FPEV0114I  PTF BUILD IS 06.216                            *
  
  SYSMOD TITLE : AUTOEXCEPTION -  example threshold dataset
                 DGOETV41 does not work
  KEYWORDS     : AUTOEXCEPTION   dataset DGOETV41
  

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:

Modules/Macros

•    DGOETV41 DGOMEXA0 DGORPSCA DGOVEPAI DGOVMSTR
  KD260HZ  KD260HZA KD260HZB KD260HZC
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSY UK16875

     UP06/08/08 P F608

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.