Why is it necessary to record CA Dispatch r11.7 events in the CA Common Services r14.1 ENF Database?

Document ID : KB000017364
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:

The CA Dispatch r11.7 Installation Guide states the following:

In order for CA Dispatch to provide complete and accurate STATUS data about information such as: Job print times, Bundle print information, and Abend information, the ENFDB must be available to record (store) the information that occurs while CA Dispatch is down for maintenance or other reasons. If the ENFDB is not available the CA Dispatch STATUS information will be compromised and incomplete.

Specifically, what STATUS information would be missing and why does it need to be recorded?

Answer:

CA Dispatch is capable of providing some functionality that is not necessarily CRITICAL to the processing of reports, but provides various features that can be exploited.

The 4 functionalities that CA Dispatch is capable of providing, that are enabled through ENF EVENTS are:

  1. Getting your CA Dispatch Bundle Queued STATUS records updated from BQ to BP and actually listing the print time. These are the records that you see when you select option 4 from the main menu.
  2. Invoking Abend Handling (As defined on the VRDMU110 - REPORT BASE DEFINITION SCREEN).
  3. Displaying abend information in the TERM field on the VOVMI200 MSGCLASS JOB SELECTION screen.
  4. Determining the generation of PC download requests for those clients who download reports from Dispatch online viewing to their PC's.

CA Dispatch also performs a "catch up" process known as the CHECKPOINT process every time it is started. The CHECKPOINT function will identify all EVENTS that have taken place while CA Dispatch was down.

In order for CA Dispatch to successfully perform the CHECKPOINT function, the Datacom/AD database (MUF) for ENF must be defined and the CA Dispatch events MUST be recorded. This will allow any/all of the CA Dispatch functionalities that are enabled through EVENTS to work correctly and consistently "all of the time" and across recycles and IPL's. Recording events allows CA Dispatch to find them when performing the CHECKPOINT function.