Cisco Cisco Process Orchestrator 3.1 User Guide

User—User Name. The effective user name of the task owner.

PR—Priority. The priority of the task.

NI—Nice value. The value of the task. A negative nice value means high priority, whereas a positive 
nice value means lower priority. Zero in this field simply means priority will not be adjusted in 
determining a task’s dispatchability.

VIRT—Virtual Image (kb). The total amount of virtual memory used by the task. It includes all 
code, data and share plus pages that have been swapped out. VIRT = SWAP + RES.

RES—Resident size (kb). The non-swapped physical memory a task has used. RES = CODE + 
DATA.

SHR—Shared Memory size (kb). The amount of shared memory used by a task. It simply reflects 
memory that could be potentially share with other processes.

S—Process status. The status of the task, which can be one of the following:

D = uninterruptible sleep

R = running

S = sleeping

T = traced or stopped

Z = zombie

Tasks shown as running should be more properly thought of as “ready to run”; the task_struct is 
simply represented on the Linux run-queue. Even without a true SMP machine, you may see 
numerous tasks in this state depending on top’s delay interval and nice value.

%CPU—CPU usage. The task’s share of the elapsed CPU time since the last screen update, 
expressed as a percentage of total CPU time. In a true SMP environment, if “irix mode” is Off, top 
will operate in “solaris mode” where a task’s CPU usage will be divided by the total number of 
CPUs. You can toggle Irix/Solaris modes with the “I” interactive command.

%MEM—Memory usage (RES). A task’s currently used share of available physical memory.

TIME+—CPU Time, hundredths. Total CPU time the task has used since it started, reflecting more 
granularity through hundredths of a second.

Command—Command line or Program name. Display the command line used to start a task or the 
name of the associated program. You can toggle between command line and name with “c”, which 
is both a command-line option and an interactive command.

Use the HANA Log information activity to retrieve detailed information about HANA logs, including 
log file size.

Use the HANA Log Operations activity to execute a specified operation against a HANA log file. For 
example, ‘Backup’ to force log backup or ‘Release’ to release log segments.

Log Operation—Enter the log operation to execute. For example, enter ‘Backup’ to force log backup 
or enter ‘Release’ to release log segments.