Producing Reports › Troubleshoot the Reporting Facility

Troubleshoot the Reporting Facility

The reporting facility is dependent on the events database, EVNTDB. It cannot operate if the following conditions apply:

• The EVNTDB database has not been allocated.
• The EVNTDB database is full.

In either case an error message appears.

If the EVNTDB Database Is Not Allocated

If the error message says that the EVNTDB database is not allocated, then you need to allocate this database before reselecting a reporting option.

If the EVNTDB Database Is Full

If the error message says that logging has stopped, the EVNTDB database may be full. If automatic reorganization is not set, complete the following steps:

1. Check the activity log (=H.L) for more messages about what is happening.
2. Extract the data currently in the EVNTDB database.
3. If the EVNTDB database is full, delete and redefine the EVNTDB database.

Note: For information about how to perform these steps, see the message help.

If the Automatic Reorganization Fails

If the error message says that the automatic reorganization has failed, you may need to redo the reorganization. The reorganization occurs in two phases, an unload phase and a reload phase. The error message gives details of where the reorganization failed and the required action.

There are two ways to fix a failed reorganization: by using a batch job or by using the EVENTLOG parameter group.

Fix a Failed Reorganization by Using a Batch Job

To fix a failed reorganization using a batch job

1. Determine the phase of the reorganization when the failure occurred.
2. Issue the following command:

   DEALLOC DD=EVNTDB

   If the failure occurred during the UNLOAD phase, complete step 3; otherwise, skip this step and go to step 4.

3. (Optional) Submit a batch job that executes an IDCAMS REPRO, for example:

   REPRO INDATASET(EVNTDB dataset name) OUTDATASET(Reorg dataset name)

   Note: Allocate enough space for the REORG data set to contain all the records from the EVNTDB.

4. Submit a batch job to define a new EVNTDB database (optionally giving it more space).
5. Submit a batch job that executes an IDCAMS REPRO, for example:

   REPRO INDATASET(EVNTSEQ dataset name from UNLOAD phase)
         OUTDATASET(new EVNTDB dataset name)
   

6. Update the EVENTLOG parameter group from the Customization Parameters panel (/PARMS) specifying the following parameters:

   Enable Event Logging

   Enter YES.

   EVNTDB Database Name

   Enter the EVNTDB data set name used in step 5.

   EVNTSEQ Reorg Dataset

   Leave blank.

7. Press F6 (Action).

   The changes are applied.

8. (Optional) If you require automatic reorganization, specify a data set name in the EVNTSEQ Reorg Dataset field and press F3 (File).

   The parameter settings are saved.

Fix a Failed Reorganization via the EVENTLOG Parameter Group

To fix a failed reorganization using the EVENTLOG parameter group

1. Determine the phase of the reorganization when the failure occurred.

   If the failure occurred during the UNLOAD phase, complete step 2; otherwise, go to step 3.

2. Update the EVENTLOG parameter group from the Customization Parameters panel (/PARMS) specifying the following parameters:

   Enable Event Logging

   Enter NO.

   EVNTDB Database Name

   Enter the EVNTDB data set name.

   EVNTSEQ Reorg Dataset

   Enter the EVNTSEQ data set name.

   Note: Allocate enough space for the reorganization data set to contain all the records from the EVNTDB database.

3. Press F6 (Action).

   The EVNTDB database is unloaded to the EVNTSEQ reorganization data set.

4. Submit a batch job to define a new EVNTDB database (optionally giving it more space).
5. Update the EVENTLOG parameter group from the Customization Parameters panel (/PARMS) specifying the following parameters:

   Enable Event Logging

   Enter YES.

   EVNTDB Database Name

   Enter the new EVNTDB data set name defined in step 4.

   EVNTSEQ Reorg Dataset

   Enter the ENVTSEQ data set name from the UNLOAD phase.

6. Press F6 (Action).

   The changes are applied.

7. Press F3 (File).

   The current parameter settings are saved.