Selecting Operating System Data of Systems, Instances, and Hosts

Use

In the operating system monitor, you can centrally display operating system data in the SAP system for various hosts. The data for the corresponding hosts is collected by the operating system collector SAPOSCOL. The following rules apply:

With hosts on which an SAP NetWeaver instance is running, this data is stored in the monitoring segment of the corresponding instance. In this case, the operating system data is therefore assigned to the corresponding system and instance in the operating system monitor. To display the operating system data for the relevant hosts, you therefore select the desired system ID and desired instance in the Systems subtree.

Note

The icons and are displayed next to instances and hosts; these have the following meanings:

Icon	Meaning
	The instance or host (or, more precisely, the agent that is monitoring that host) is set to ONLINE in the monitoring infrastructure.
	The instance or the corresponding agent is not set to ONLINE in the monitoring infrastructure.

With hosts without an SAP NetWeaver instance, you can display the operating system data by choosing the relevant host name in the Hosts subtree.
If you use the option to display platform-specific data for IBM z/OS, the monitored sysplexes and their logical partitions are also displayed in the navigation bar. More information: SAP Note 1236078.

A summary of the screen elements in the operating system monitor is provided in Structure of the Display in the Operating System Monitor.

Activities

To define the host from which you want to display operating system data, choose the corresponding entry in the data source subtrees.

Possible Error Messages

Error Message	Diagnosis
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.

Error Message

Diagnosis

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.

More information: Error Analysis: Operating System Collector..

Operating System Monitor start page