PM68880: OMEGAMON DB2 Near Term History file management and initialization improvements

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Message KO2Z999E "OMPE V510 Service Error XSM=*UNKNOWN/ZSHIFT
  ABEND=S878 RSN=000E0000 MODE=ABEND"
  or Message KO2Z999E "OMPE V510 Service error SSM=OMPEXCF
  /OMPEXCF  ABEND=.S878 RSN=0000000C MODE=ABEND"
  
  
  
  Performance improvements:
  1. Ensure all NTH tasks are ready before accepting DB2
     instrumentation records reducing exposure to S878
     abends at NTH initialization
  2. Reduce below-the-line storage related to NTH VSAM
     file allocations for z/OS 1.12 users
  

Local fix

• The following options have provided relief until the PTF for
  this APAR can be applied
  
  - Edit the OMPE start-up member. This is the member by the same
    name as the started task in the RKD2PAR library.
    Move the command that opens the VTAM interface to the last
    command in the list - this commmand is of the form
    EXEC RVTMxxxxx
    Insert a line prior to EXEC RVTMxxxx that reads WAIT 30
    This will delay users ability to logon until all
    initialization is complete
  
  - Edit the OMPE00 member of RKD2PAR
    Add or change the following line
    XCFTASKS=4
    The default is 16 and may be changed to 4.  This would help
    reduce storage usage.
  
  - Reduce BUFSIZE from 4 meg to 2 meg.
    This is the size of the OPx buffers,   This is specified in
    the COPTxxxx members as BUFSIZE(2048).
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component                           *
  *                 - NTH - Near Term History                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Abend S878 and high CPU observed        *
  *                      shortly after NTH started.              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  1. A CPU HOTSPOT IS OBSERVED WHICH DOES NOT APPEAR TO
     ACTUALLY BENEFIT THE PROCESSING OF NTH VSAM IO.
  2. SMF RECORDING OF DD-RELATED STATISTICS IS AN UNNECESSARY
     OVERHEAD WHICH MAY BE ELIMINATED DURING STARTUP PROCESSING.
  3. ALLOCATION-RELATED CONTROL BLOCKS OCCUPY VERY LIMITED
     BELOW-THE-LINE STORAGE AREAS.
  4. DATA RECORDED FROM THE DB2 IFI TRACES MAY BUILD UP IN
     STORAGE IF THE OUTPUT PROCESS IS BLOCKED OR SLOWED IN
     ANY WAY.
  5. POSSIBLE UNLIMITED STORAGE CONSUMPTION CAUSING ABEND S878.
  
  PROBLEM CONCLUSION:
  1. REMOVE THE CPU HOTSPOT.
  2. FOR ZOS V1.12 AND ABOVE, SPECIFY AN ALLOCATION PARAMETER
     WHICH WILL ELIMINATE DD-RELATED SMF ACCOUNTING FOR THE NTH
     VSAM FILES.
  3. SPECIFY ALLOCATION PARAMETERS WHICH WILL CAUSE
     ALLOCATION-RELATED CONTROL BLOCKS TO BE PLACED IN
     31-BIT STORAGE.
  4. WAIT UNTIL THE OUTPUT PROCESS IS FULLY INITIALIZED BEFORE
     ISSUING THE DB2 -START TRACE COMMANDS.  THIS WILL HELP TO
     PREVENT THE BUILD UP OF DATA WAITING TO BE OUTPUT TO THE
     VSAM LINEAR DATASETS.
  5. PLACE A HARD LIMIT ON STORAGE OCCUPIED BY THE DATA
     WAITING TO BE WRITTEN TO THE VSAM FILES.
  
  KEYWORDS:
  ABEND878 CPU
  

Problem conclusion

• 1. REMOVE THE CPU HOTSPOT.
  2. FOR ZOS V1.12 AND ABOVE, SPECIFY AN ALLOCATION PARAMETER
     WHICH WILL ELIMINATE DD-RELATED SMF ACCOUNTING FOR THE NTH
     VSAM FILES.
  3. SPECIFY ALLOCATION PARAMETERS WHICH WILL CAUSE
     ALLOCATION-RELATED CONTROL BLOCKS TO BE PLACED IN
     31-BIT STORAGE.
  4. WAIT UNTIL THE OUTPUT PROCESS IS FULLY INITIALIZED BEFORE
     ISSUING THE DB2 -START TRACE COMMANDS.  THIS WILL HELP TO
     PREVENT THE BUILD UP OF DATA WAITING TO BE OUTPUT TO THE
     VSAM LINEAR DATASETS.
  5. PLACE A HARD LIMIT ON STORAGE OCCUPIED BY THE DATA
     WAITING TO BE WRITTEN TO THE VSAM FILES.
  
  KEYWORDS:
  ABEND878 CPU
  

Temporary fix

Comments

APAR Information

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

  PM62281

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

  UK82400

Modules/Macros

• KO2HDTPB KO2HINTB KO2HSQIB KO2PLIOF KO2PUTLF
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R511 PSY UK82400

     UP12/10/10 P F210

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.