What are some common factors that can lead to a CAIENF database space problem and how can it be avoided?
search cancel

What are some common factors that can lead to a CAIENF database space problem and how can it be avoided?

book

Article ID: 30162

calendar_today

Updated On:

Products

CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services Datacom/AD CA ECOMETER SERVER COMPONENT FOC Easytrieve Report Generator for Common Services INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware Compress Data Compression for MVS Compress Data Compression for Fujitsu

Issue/Introduction

  • The CA Common Services for z/OS r15.0 ENF component may be used to record events for various CA products. 
    • CA products such as CA-7, Scheduler, CA-11, etc may require event recording
  • ENF writes these events to a Datacom/AD MUF exclusive to ENF
  • Occasionally, the ENF MUF will run short of space
    • ENF will display messages from both CA Datacom and CA Common Services indicating an "X37" abend and that the table is full
    • The X37 abend will generate messages like the following (using an event named STEPTERM as an example): 

        DATACOME:DB04206I – PXX END – EXTEND FAILURE DUE TO X37 ABEND
        DATACOME:DB01702I – DYNAMIC  EXTEND OF AREA ENF00700 HAS FAILED
        CAS9316E – STEPTERM “Insert  “ failed – rc(-258) r/s (X’F5F7E2F0F6)
        CAS9340I – TABLE  FULL – DBID=700 INTERNAL  NAME B22
        *CAS9208E –  CA-ENF DB:  DB Insert error SQLCODE=-258  SQLSTATE=57S06
        CAS9303E – Event STEPTERM no longer recorded due to DB error 0008

  • This article will discuss the reasons why a problem with the space can occur and describe methods to both resolve the immediate problem and avoid a future occurrence.


 

What can cause the ENF MUF to run out of space and what methods are available to resolve the problem?   
 

Environment

  • Common Services for z/OS r15.0 ENF Component used for Event recording
  • Datacom/AD r14.0, r15.0, or r15.1 
  • Various CA products such as CA-7, Scheduler, CA-11 requiring Event Recording 

Cause

Possible reasons why the database may encounter a space problem:

  • Initial space allocation was too small   
    • Recommendation is to initially allocate 500 cylinders for IXX700 and 1500 cylinders for ENF700 datasets.
    • Monitor the usage for a representative work cycle and adjust if necessary
  • ENF parms are not set correctly

Resolution

  • Proper settings of ENF parms to prevent space problems:
    • ARCHIVE and EVENT parms work together to keep the MUF a self-sustaining entity
    • 5 key statements used to purge records
      • ARCHIVE(hhmm) or ARCHIVE(AUTO)
      • Runs once daily  
      • hhmm – execute based upon a time using the 24 hour clock (0100 or 1:00 am the default)
        • hhmm the recommended method under your control 
      •  AUTO – purge records when the database reaches a specified percentage of capacity (80% the default)
        • Check of percentage run daily
        • Nothing purged until percentage full is reached
        • Not under user control 
      • 4 EVENT statements for every recorded record – STEPTERM used as example
        • EVENT(STEPTERM,ACT)             – Enables the event
        • EVENT(STEPTERM,REC)             – Record the event to the database
        • EVENT(STEPTERM,RP=nn)         – The number of days to retain the records
          • RP - abbreviation for Retention Period
          • Span of RP=1 - RP=3 most commonly used   
        • EVENT(STEPTERM,PURGE=Y)    – Purge the records when RP value is met  
      • ENF parms listed above prevent the database from reaching capacity
        • Delete records when no longer needed by individual CA product
          • If PURGE and/or RP omitted:
            • Records will remain on database indefinitely
            • Can lead to possible space problem 
        • Run on a scheduled basis
        • Eliminate user intervention


Should space problems be encountered despite the parms it is possible to dynamically purge events by using an ENF PURGE(event)  console command.   Follow these steps:

    • Execute a Datacom CXX report against the ENF Database, DBID=700
      • Using the STEPTERM event as an example
    • Issue the ENF PURGE(event) command using one of two formats
      • ENF PURGE(STEPTERM)
      • F ENF,PURGE(STEPTERM)
    • Another possibility to clear space is to force an immediate backup which serves to clear the database all at once.
      • ENF,ARCHIVE(NOW)
      • F ENF,ARCHIVE(NOW) 

  • If the CAS9303E message was issued for the named event (STEPTERM)
    • Necessary to re enable recording
      • Accomplished with ENF EVENT(event,REC) command
        • ENF EVENT(STEPTERM,REC)
        • F ENF,EVENT(STEPTERM,REC)   

Additional Information

Refer to the Common Services for z/OS r15.0 Product Documentation for details on the specific ENF parms and commands. 

 

Powered by Wolken Software