Runtime Diagnostics is not a monitor. It is a point-in-time diagnostics tool that you use when there is a problem on your system as an aid to diagnosing the problem. The fact that you are using runtime diagnostics when there are no issues on your system and it is returning no events is good! See "How Runtime Diagnostics Works" in z/OS Problem Management for more information.
Also, from the redbook "Extending IBM z/OS System Management Functions with IBM zAware:" If you choose to automate calls to Runtime Diagnostics, such as invoking it every hour, it is likely that events will be issued even though you are not experiencing soft failures. Some of the events also occur when the system is behaving normally, but they are not a real issue unless you have noticed that the system is having problems. These events are probably not indicative of a system problem at that time and you might waste time investigating these events when no system problem is occurring. This point is especially true for the address space execution and global resource contention categories. For more information about starting and controlling Runtime Diagnostics, refer to z/OS Problem Management, G325-2564. Karla Arndt z/OS Predictive Failure Analysis and Runtime Diagnostics ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
