PK73310: VSAM ALLOCATE EVENTS EVENT EXCEPTIONS PE CLIENT DATASET SIZE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• If no EVENTS EXCEPTIONS dataset is defined when the OMPE Server
  starts, it allocates an EVENTS dataset "on the fly" with 5MBytes
  Primary, 10 MBytes secondary allocation, which is too large.
  .
  As a workaround customer can manually delete and re-allocate
  the EVENTS dataset before starting the OMPE Server using the
  "optimized" EVENTS dataset specifications by  IDCAMS:
  .
  //DEFINE  EXEC PGM=IDCAMS
  //SYSPRINT DD  SYSOUT=*
  //SYSIN    DD  *
    DELETE (%your EVENTS dataset e.g. TCH.OMGXE41.DP11.EVENTS%)
  CLUSTER
    DEFINE CLUSTER(NAME(%your EVENTS dataset e.g.
  TCH.OMGXE41.DP11.EVENTS%)  -
                   MEGABYTES(10 0)     -
                   VOLUMES(%your volser%)        -
                   LINEAR                   -
  )
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   PE Server subtask                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: The '<dataserverhlq>.<DB2 SSID>.EVENTS' *
  *                      dataset that is used for Event          *
  *                      Exception Processing was growing over   *
  *                      time and used more than 100 cylinders   *
  *                      after a while.                          *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  The '<dataserverhlq>.<DB2 SSID>.EVENTS'
  dataset is allocated with 20 MBytes when the OMEGAMON PE server
  is started (if it does not already exist). The dataset can not
  grow since the secondary extends are set to 0.
  
  PROBLEM CONCLUSION:
  '<dataserverhlq>.<DB2 SSID>.EVENTS' dataset
  growth issue resolved
  

Problem conclusion

• '<dataserverhlq>.<DB2 SSID>.EVENTS' dataset
  growth issue resolved
  
  KEYWORDS : EVENT EXCEPTION PROCESSING  EVENTS
  

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:

  UK40948

Modules/Macros

• DGOZFL2
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R410 PSY UK40948

     UP08/10/27 P F810

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.