SAPOSCOL: Working Directory and Profile Parameters (SAP Library

SAPOSCOL: Working Directory and Profile Parameters

Definition

Working Directory

The SAPOSCOL working directory is the directory to which the collector writes its data and in which it searches for the log file dev_coll and the shared memory backup file coll.put. It is not the directory, in which SAPOSCOL itself is stored.

Default SAPOSCOL Working Directory

Operating System

Path of the Working Directory

Microsoft Windows NT

\\host\saploc\prfclog or (if this does not exist) c:\temp

Note

saploc must be released as a share.

UNIX

usr/sap/tmp or (if this does not exist) /tmp

Set a profile parameter if you want to use a different directory. In this case, start SAPOSCOL with a profile (saposcol -l pf=<file path/-name>), where the specified file contains only the following line:

DIR_PERF = <Path of the desired working directory>

Note

· If a CCMS agent is also working on the host on which the operating system collector is running, note that the profile parameter DIR_PERF also determines the working directory of the agent. The working directory of the agent should be a folder in the working directory of the operating system collector (see Working Directory and Log Files of the CCMS Agents).

· Since you can also access the dev_coll file from the SAP system, you should also maintain the profile parameter DIR_PERF at the same time for all SAP instances of the affected host.

Example

Start SAPOSCOL with the command:

saposcol -l pf=/usr/sap/C11/SYS/profile/saposcol.pfl

The file /usr/sap/C11/SYS/profile/saposcol.pfl contains the line:

DIR_PERF = /usr/sap/my_saposcol_dir

Result: The directory /usr/sap/my_saposcol_dir is the working directory of SAPOSCOL.

The Profile Parameter exe/saposcol

The SAP profile parameter exe/saposcol (which is not a SAPOSCOL profile parameter) contains the complete name of the program SAPOSCOL (which should not be confused with the SAPOSCOL working directory). To start or stop SAPOSCOL, or to display its status from the SAP system or with a CCMS agent, the parameter must point to a correctly installed SAPOSCOL.

If multiple SAP instances are running on a host, for example, each with a different releases, ensure that each instance uses the same (newest) version of SAPOSCOL.

Example

The system XYZ and the system C11 have different releases, and both systems are on the same host. The profile parameter exe/saposcol should point to the same, current SAPOSCOL in both systems. Ensure that you set the authorizations so that the SAPOSCOL directory can be accessed by both systems, so that SAPOSCOL can be started by both systems. However, only one SAPOSCOL runs for each host at any one time.