Diagnosing an empty Monitor III JES Delays report

Use this procedure when no data appears in a Monitor III JES delays report.

If there are no jobs delayed by JES, RMF™ generates an empty Monitor III JES delays report. In this case, an empty report is not considered a problem.

Table 1. Diagnostic Procedure for Empty Monitor III JES Delays Report
Diagnostic Procedure References
1. Find out if the JES2 or JES3 control blocks have changed at your installation. If so, Monitor III modules might be affected. For the RMF/JES interface module installation procedures, see z/OS Program Directory
2. If the JES control blocks have changed, you must reassemble and link-edit the RMF source modules that map offsets to the JES control block fields sampled by Monitor III using the new JES macros. If the problem occurs again, continue with the next step.  
3. Report the problem to IBM®. Provide the following problem data:
  • Accompanying messages
  • RMF version and release
  • Installed JES level
  • Hardcopy of the report
  • VSAM data set contents
  • Name and level of the operating system with a list of program temporary fixes (PTF) applied at the time of the problem and all installation modifications, exits, and products with other than Class A service.
 Reporting a problem to IBM
Parent topic: Diagnosing problems in RMF