Problems when using the Incident Log task

This topic provides troubleshooting tips for common problems that might occur while using the Incident Log task.

Troubleshooting topics are included for the following problems and scenarios:

User cannot access the Incident Log task

Symptom: On selecting the Incident Log task, the user receives an error message indicating a lack of authorization to CEA.

Probable cause: During the configuration of z/OSMF, the configuration script defines the resource CEA.CEAPDWB*. However, the resource CEA.* was already defined by your installation. Because CEA.CEAPDWB* takes priority over CEA.* no users are authorized to make CIM requests.

Corrective Action: Give z/OSMF users access to CEA.CEAPDWB*. If you have CEA security definitions configured, you might already have the CEA.* resource defined.

User encounters message ICH408I

ICH408I USER(user ) GROUP(group ) NAME(user ) 031 
CATALOG.SYVPLEX.MASTER CL(DATASET ) VOL(volser) 
INSUFFICIENT ACCESS AUTHORITY 
FROM CATALOG.*.MASTER (G) 
ACCESS INTENT(UPDATE ) ACCESS ALLOWED(NONE )

Possible Cause: A user with insufficient authority is attempting to update the master catalog while creating the data diagnostic files. As a result, an Incident Log task request to FTP materials cannot compress (terse) the diagnostic snapshot data set.

Corrective Action: Determine whether the user should be allowed to update the master catalog. If so, you can authorize the user to create entries in the master catalog through the appropriate security commands.

To authorize a user to create entries in a user catalog, use the following command:

DEFINE ALIAS(NAME(CEA) RELATE(<usercatalog name>))

CEA address space is blocking the use of the sysplex dump directory

Possible Cause: CEA holds an exclusive ENQ to serialize on the sysplex dump directory data set while processing a z/OSMF request. Usually, the ENQ is released in microseconds. But sometimes an I/O error could result in holding the ENQ for longer time periods, therefore blocking DUMPSRV from updating the dump directory with information about a new dump, or your installation from doing maintenance on the sysplex dump directory data set.

Corrective Action: Use the system console command F CEA,DROPIPCS to disconnect CEA from the IPCS sysplex dump directory data set.

CEA cannot allocate a data set for dump prepare or snapshot

Possible Cause: CEA alias is not cataloged properly.

Corrective Action: If your installation has a user catalog setup instead of using the MASTER catalog, you might need to define the CEA alias to the user catalog. For example:

DEFINE ALIAS(NAME(CEA) RELATE(YOUR_CATALOG_NAME))

Diagnostic log streams and other incident data for deleted incidents are not being deleted over time

Possible Cause: If you modified the HLQ parameter value in the CEAPRMxx parmlib member, CEA no longer detects the previously-stored diagnostic data files stored under the old high level qualifier.

Corrective Action: Carefully remove the data manually. The data exists in both log stream and data set format. Use caution as to not remove any needed data. Remove data sets and log streams manually. To list the available log streams, enter the following system console command: D LOGGER,L.

Most log streams with the status of AVAILABLE are the result of diagnostic snapshots taken at the time of the dump. The old high level qualifier appears in the log streams that were created earlier by CEA. To delete log streams, enter the following command: SETLOGR FORCE,DELETE,LSN=logstreamname.

To remove data sets, do the following:
  • List the data sets having the same HLQ as the available log streams.
  • Delete the data sets.
Parent topic: Common problems and scenarios