Old Standalone SAPOSCOL:
The old saposcol is a simple standalone program. All it does is create a shared memory segment, collect Operating System statistics and store them in shared memory (shared memory segment 99 area). The OS stats can then be read in transaction ST06. It is installed once on the physical host, and it has nothing to do with the kernel or any other program.
Up until SAP_BASIS 710 (and until you upgrade to the 720 kernel as described in note 1636252), the old standalone saposcol executable is in the kernel directory. However it has nothing to do with the kernel release of the system which means you can always use the highest release of saposcol (downward compatibility). For a 46C system, you can use the 720 saposcol for example.
Saposcol on Windows is started by a service (SAP note # 436186 - Installing saposcol as a service).
Saposcol on Unix is started in the Unix startup script.
For more information on standalone saposcol refer to the 701 online documentation at:
"Operating System Collector SAPOSCOL":
Operating System Collector SAPOSCOL - Operating System Monitor - SAP Library
SAPOSCOL in SAPHOSTAGENT:
From SAP_BASIS 710 onwards, and also when you install saphostagent with the 720 kernel (note 1636252), saposcol is contained in the saphostagent package. Saphostagent is also completely downward compatible, so again you can install saphostagent 720 on a 46C system for example.
- SAP note # 1031096 - Installing Package SAPHOSTAGENT
With saphostagent installed, saphostagent will start saposcol automatically.
On Windows with saphostagent the service is called SAPHostExec (SAP note # 1439391 - SAPOSCOL Service deleted after SAPHostAgent Installation).
On Unix, when you install SAPHOSTAGENT as described in SAP note # 1636252 (Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11):
"you must delete the call of the program SAPOSCOL from all the start profiles"
This way you will only be starting the correct SAPHOSTAGENT saposcol from the HOSTAGENT directory, and not trying to start a second standalone saposcol from the kernel directory, which can sometimes cause problems.
The dev_saphostexec trace file in /usr/sap/hostctrl/work provides details on your SAPHOSTAGENT patch version and on the saphostexec process starting up.
The saposcol trace file dev_coll is still located in the old /usr/sap/tmp directory. When saposcol is being correctly started by SAPHOSTAGENT the dev_coll should have an opening line similar to:
LOG: Profile : /usr/sap/hostctrl/exe/host_profile
on Unix, or:
LOG: "C:\Program Files\SAP\hostctrl\exe\saposcol.exe" -q -w60 pf="C:\Program Files\SAP\hostctrl\exe\host
on Windows.
When installing SAPHOSTAGENT on a remote host to monitor OS stats (for example to monitor a standalone DB server) refer to SAP KBA Note # 2164753:
- 2164753 - CCMS Monitoring of non-SAP Server (eg. Standalone DB)
For more information on saphostagent saposcol refer to the online documentation at:
"Operating System Monitor" -> "Downloading and Installing Package SAPHOSTAGENT":
http://snipurl.com/29xj1ef
More information and troubleshooting guides (including this one) on the BC-CCM-MON area are available in the CCMS Wiki space at:
Computing Center Management System (CCMS) - Technology Troubleshooting Guide - SCN Wiki
