Controlling SAPOSCOL from the Operating System (SAP Library

Controlling SAPOSCOL from the Operating System

Use

You can start saposcol from the operating system command prompt with the following options:

-i <interval(sec)> | -u [<interval(sec)>] | -e [<interval(sec)>]

For all three of these options, SAPOSCOL must already be running. Alternatively, SAPOSCOL can be started using the -l option placed before any of these options.

For example, if SAPOSCOL is not already running, -l -i 20 -e 400 -u 90 will set the intervals successfully. Without the -l option, SAPOSCOL must already be running.

Option	Argument
-d	Dialog mode
-k	Kills the running collector
-r	Kills the running collector and print results
-l	Launches the collector
-f	Launches the collector in all cases
-s	Displays the status of the collector
-i	Sets a new interval for collecting data in normal mode (default is every 10 seconds)
-v	Displays the version of the collector
-u	Sets a new interval so that if no data is collected during that interval, the collector mode changes from normal to idle mode. The default interval is 300 seconds or 5 minutes. Example: SAPOSCOL - u 600 means that if after ten minutes there is no input to get data (either from a user or a process), the collector goes into idle mode.
-e	Sets a new interval for collecting data in idle mode (default is every 60 seconds)
-c	Cleans shared memory
-p	Puts shared memory to file
-g	Gets shared memory from file
-t	Sets debug trace level
-n	Sets normal trace level
-o	Prints all data
-m	Prints all snapshot data
-x	Tests background process running and answers

Dialog Mode

Running saposcol in dialog mode allows you to display from the OS prompt any data in shared memory. This data is collected by a different saposcol running in the background. You can run saposcol in dialog mode both from the command prompt and from the CCMS operating system monitor.

Procedure

To start saposcol in dialog mode from the command prompt, use the following command: saposcol -d.

saposcol does not attempt to start a second collector. saposcol then displays a new command prompt: Collector>

You can enter several saposcol commands at this prompt. To display a list of possible commands, use the help command.

In dialog mode, you can control and monitor saposcol running in the background. To display the status of the saposcol that collects data in the background, use the command status or stat You can display the data that saposcol has collected directly from shared memory.

To display OS performance data stored in shared memory, at the Collector> prompt, enter the command:

dump memory all

The following information is displayed:

Collector > dump memory all
Pages paged in / sec 1
Pages paged out / sec 0
KB paged in / sec 4
KB paged out / sec 0
freemem [KB] 13312
physmem [KB] 65536
swap configured [KB] 76348
swap total size [KB] 76348
swap free inside [KB] 72556

Unlike in the SAP System, data that is not available is NOT marked by N/A.

These are the most important combinations of the command dump :

dump cpu single	snapshot details for each CPU
dump cpu all	general snapshot details for all CPUs
dump cpu sum	mean values from data collected every hour for all CPUs

dump memory all	snapshot details of the memory
dump memory sum	mean values from data collected every hour for the whole memory

dump top

snapshot details of top cpu consuming processes

dump disk single	snapshot details of each individual disk
dump disk sum	mean values for every hour for every disk

dump filesystem single	snapshot details of each file system
dump filesystem sum	mean values for every hour for each file system

dump lan single	snapshot details of every network interface
dump lan sum	mean values for every hour for every network interface

dump parameter configured	operating system parameters configured
dump parameter used	operating system parameters currently being used

dump hour

Displays the following list, which shows the hour (0 to 23) and the day when the data was collected. The format is year/month/day with no separator. Data collected at a certain hour marked with the number 2 is inconsistent. Data marked with the number 1 is for the current hour. Data marked with the number 0 is unavailable.

-------------------------------------------------------
hour: 0 of day 19950814 hour: 1 of day 19950814
hour: 2 of day 19950814 hour: 3 of day 19950814
hour: 4 of day 2 hour: 5 of day 19950814
hour: 6 of day 19950814 hour: 7 of day 19950814
hour: 8 of day 19950814 hour: 9 of day 19950814
hour: 10 of day 19950814 hour: 11 of day 19950814
hour: 12 of day 1 hour: 13 of day 19950813
hour: 14 of day 19950813 hour: 15 of day 19950813
hour: 16 of day 19950813 hour: 17 of day 19950813
hour: 18 of day 19950813 hour: 19 of day 19950813
hour: 20 of day 2 hour: 21 of day 0
hour: 22 of day 2 hour: 23 of day 19950813
-------------------------------------------------------

You can also control the background saposcol in dialog mode at the Collector> prompt using the following commands:

detailson	sets the details flag
detailsoff	reverses the details flag
interval 5	changes the collection interval to 5 seconds (default 10)
kill	stops the background process
launch	starts a new collector
force	forces a new collector to start (only in emergencies)

The changed values are written to the shared memory and saposcol reads them before more data is collected. For example, if the collection interval is changed from 10 to 2 seconds, it can take up to 8 seconds before the collector switches to the new interval.

You can also add comments in lines beginning with #.

To exit saposcol ’s dialog mode, use the quit command.

See also:

Starting SAPOSCOL

Stopping SAPOSCOL

Reducing CPU Load

Collector Home Directory, Paths and Profile Parameters

Collector Status

Displaying Collector Data

Interpreting the Data