Event Notification Facility › CAIENF Customization Considerations

CAIENF Customization Considerations

CAIENF runs on all IBM-supported releases of z/OS.

CAIENF can record system- and CA Technologies product-generated events in CAIENF database event tables. Two reasons exist to record events:

• Catch up on previous events. If a CA Technologies product is down while CAIENF is running, the product that listen for CAIENF events can catch up on past events. This process is named event checkpointing or event recovery. As the CA Technologies products start up and initialize with CAIENF, they can request that events from a past date and time be posted to the CA Technologies product CAIENF listening task before new events are posted. The CA Technologies products that take advantage of event checkpointing have installation steps to update CAIENF parameters so that specific events are recorded.
• Capture specific events for analytical reporting purposes. You can interrogate the event database using a SQL report.

CAIENF event recording requires CA Datacom/AD at Version 12.0 or above. CAIENF requires that a CA Datacom MUF (Multi-User facility) house the CAIENF database on each system that is running CAIENF. You can run the MUF within the CAIENF address space or external to the CAIENF address space. We recommend that you run the MUF internal to the CAIENF address space. This setup makes CAIENF run more self-contained and similar to the way it ran before Version 12.

The CAIENF event data is unique to each system. Therefore, sharing a CA Datacom/AD MUF with other CA Technologies products is not practical because:

• other CA Technologies products generally share data across systems using a cross-system MUF
• maintenance and backup configurations.

Only share the MUF with other CA Technologies products if the product documentation specifically states otherwise. A CAIENF MUF can be shared with the Event Management common service. If you are using Event Management message actions or calendars, we expect that CAIENF and Event Management share a MUF.

Started Task Procs ENFIMUF uses an internal MUF. ENFXMUF uses an external MUF. Both are delivered in the CCS CAW0PROC data set to serve as a basis for your customization.

If you do not require event recording, you can customize the CAW0PROC data set delivered member ENF to run without a database.