Calling the Operating System Monitor
Calling the Operating System Monitor
Use
You can use the operating system monitor to monitor the system resources that the operating system provides. The collector SAPOSCOL collects these resources. You can call the monitor for the server on which you are currently logged on, or for another service.
You can also monitor operating system data using the CCMS monitor Operating System (transaction RZ20). However, the data displayed there is, in principle, only complete if the monitored servers belong to SAP systems. This restriction does not apply to the operating system monitor.
Prerequisites
SAPOSCOL must be running so that the data is available.
Procedure
To call the individual functions shown in the table, choose CCMS → Control/Monitoring → Performance Menu → Operating System.
|
Function |
Menu Path |
Transaction |
|
Call operating system monitor for the local server |
→ Local → Activity |
OS06 |
|
Call operating system monitor for another server |
→ Remote → Activity, then select the desired server on the SAPOSCOL Destination screen |
OS07, then select the desired server on the SAPOSCOL Destination screen |
In both cases, the system displays performance indicators for the operating system of the desired server.
For information specific to the OS/400 operating system monitor, see
To display additional information about the individual areas, choose the corresponding row.
Data for the last 24 hours is displayed for the CPU, the memory, and the swap space. For the hard disk and the LAN, the system displays a list of the current data for each hard disk and LAN interface. If problems occur, the system displays appropriate messages.
To update the data displayed on the screen, choose Refresh. As SAPOSCOL collects data by default in 10 second intervals, you do not always obtain new data by choosing Refresh.
Possible Error Messages
|
Shared memory not available |
SAPOSCOL has not created a shared memory segment. This is usually due to the fact that the SAPOSCOL program has not been started. |
|
Collector not running |
SAPOSCOL was started and created a shared memory segment, but was later terminated. |
For more information about this topic, see
Error Analysis: Operating System Collector.See also:
Operating System Monitor: Detailed Data Operating System Monitor Data: CPU Operating System Monitor Data: Memory Management Operating System Monitor Data: File System and LAN