Diagnose Report Failures

This section describes problems that you may encounter with reports.

Symptoms

When you click the Execute on a Run Report on Demand tab, an WRCALL* error message appears.

No report output is produced.

Possible causes

Java Task is not active.

Socket or other connection problems between the control region and the Java Task.

Action

Check the REPTEST task-related messages (messages WRSTJF*). This tests everything used by the Run Report on Demand function.
Check the NM Activity Log at the time of the attempt. This may show socket or connection error details. Determine if other activity is happening, for example, being processed.
Check the Java Task log at the time of the attempt.

Symptoms

When viewing a report, the report output contains an error message.

The report run appears in the Report Runs tab list, but with a status of failed.

The report run does not appear on the ReportCenter Home Page (because this page only contains runs with a status of OK).

Possible causes

As per the error message, frequently:

DBMS, database, or SQL errors
Java storage errors
Proceed as for problem, Resource Usage: Java Task JVM Heap Storage
Java Task is terminating and cannot generate the report

Action

Try running the same report with the same criteria to see if the problem is persistent.
Check whether all report runs are failing or only this report is failing.
Review the Java Task log at the time of the report generation for further error details.
For DBMS and database errors, review the REPTEST database-related messages (WRSTDB*).
For Java Task terminating errors, see whether the task was terminated by the user (P, CANCEL, or OCS JFSTOP)) or due to an error condition.