LSF Version 7.3 - Using Platform LSF HPC

Using SGI Comprehensive System Accounting facility
(CSA)
The SGI Comprehensive System Accounting facility (CSA) provides data for collecting
per-process resource usage, monitoring disk usage, and chargeback to specific login
accounts. If is enabled on your system, LSF writes records for LSF jobs to CSA.
SGI CSA writes an accounting record for each process in the
pacct file, which is
usually located in the
/var/adm/acct/day directory. SGI system administrators then
use the
csabuild command to organize and present the records on a job by job basis.
For each job running on the SGI system, LSF writes an accounting record to CSA when
the job starts and when the job finishes. LSF daemon accounting in CSA starts and stops
with the LSF daemon.
See the SGI resource administration documentation for information about CSA.
Setting up SGI CSA
Set the following parameters in /etc/csa.conf to on:
❖ CSA_START
❖ WKMG_START
Run the csaswitch command to turn on the configuration changes in
/etc/csa.conf.
See the SGI resource administration documentation for information about the
csaswitch command.
Information written to the pacct file
LSF writes the following records to the pacct file when a job starts and when it exits:
◆ Job record type (job start or job exit)
◆ Current system clock time
◆ Service provider (LSF)
◆ Submission time of the job (at job start only)
◆ User ID of the job owner
◆ Array Session Handle (ASH) of the job (not available on Altix)
◆ SGI job container ID (PAGG job ID on Altix)
◆ SGI project ID (not available on Altix)
◆ LSF job name if it exists
◆ Submission host name
◆ LSF queue name
◆ LSF external job ID
◆ LSF job array index
◆ LSF job exit code (at job exit only)
◆ NCPUS—number of CPUs the LSF job has been using
Viewing LSF job information recorded in CSA
Use the SGI csaedit command to see the ASCII content of the pacct file. For
example: