Provided by: gridengine-common_6.2u4-2ubuntu1_all
accounting - Sun Grid Engine accounting file format
An accounting record is written to the Sun Grid Engine accounting file
for each job having finished. The accounting file is processed by
qacct(1) to derive accounting statistics.
Each job is represented by a line in the accounting file. Empty lines
and lines which contain one character or less are ignored. Accounting
record entries are separated by colon (’:’) signs. The entries denote
in their order of appearance:
Name of the cluster queue in which the job has run.
Name of the execution host.
The effective group id of the job owner when executing the job.
Owner of the Sun Grid Engine job.
Job identifier - job number.
An account string as specified by the qsub(1) or qalter(1) -A option.
Priority value assigned to the job corresponding to the priority
parameter in the queue configuration (see queue_conf(5)).
Submission time (GMT unix time stamp).
Start time (GMT unix time stamp).
End time (GMT unix time stamp).
Indicates the problem which occurred in case a job could not be started
on the execution host (e.g. because the owner of the job did not have a
valid account on that machine). If Sun Grid Engine tries to start a job
multiple times, this may lead to multiple entries in the accounting
file corresponding to the same job ID.
Exit status of the job script (or Sun Grid Engine specific status in
case of certain error conditions). The exit status is determined by
following the normal shell conventions. If the command terminates
normally the value of the command is its exit status. However, in the
case that the command exits abnormally, a value of 0200 (octal), 128
(decimal) is added to the value of the command to make up the exit
For example: If a job dies through signal 9 (SIGKILL) then the
exit status becomes 128 + 9 = 137.
Difference between end_time and start_time (see above).
The remainder of the accounting entries follows the contents of the
standard UNIX rusage structure as described in getrusage(2). Depending
on the operating system where the job was executed some of the fields
may be 0. The following entries are provided:
The project which was assigned to the job.
The department which was assigned to the job.
The parallel environment which was selected for that job.
The number of slots which were dispatched to the job by the scheduler.
Array job task index number.
The cpu time usage in seconds.
The integral memory usage in Gbytes cpu seconds.
The amount of data transferred in input/output operations.
A string specifying the job category.
The io wait time in seconds.
If this identifier is set the task was part of a parallel job and was
passed to Sun Grid Engine via the qrsh -inherit interface.
The maximum vmem size in bytes.
Advance reservation identifier. If the job used resources of an advance
reservation then this field contains a positive integer identifier
otherwise the value is "0" .
If the job used resources of an advance reservation then this field
contains the submission time (GMT unix time stamp) of the advance
reservation, otherwise the value is "0" .
sge_intro(1), qacct(1), qalter(1), qsub(1), getrusage(2),
See sge_intro(1) for a full statement of rights and permissions.