Process Manager Server stores audit data in a history log file. This log file contains a record of all of the work items that run in the system. It tracks each work item as it enters the Process Manager system, is submitted to LSF® management host, and tracks its state as it completes. It records the CPU usage of each job in the system, start time, finish time, and other pertinent information.

When the history log file reaches the maximum size specified in JS_HISTORY_SIZE or the maximum number of hours of data, as specified in JS_HISTORY_LIFETIME in the js.conf file, a new history log file is created. The numeric suffix of the file increases as each new file is created.


The following is an excerpt from a history log file:

"JOB" "bhorner" "1035277212" "5:bhorner:daily:J1" "Started job" "JobId=1360" 
"JOB" "bhorner" "1035277222" "5:bhorner:daily:J1" "Execute job" "JobId=1360|Host=curie" 
"JOB" "bhorner" "1035277242" "5:bhorner:daily:J1" "Finished job" "JobId=1360|State=Done|Status
=0|StartTime=1035277208|FinishTime=1035277237|CPUUsage=0.170000 sec" 
"FLOW" "bhorner" "1035277242" "5:bhorner:daily" "Finished flow" "State=Done|Status=0|StartTime
"FLOWDEF" "bhorner" "1035309105" "bhorner:untitled1" "Remove flow definition" "" 
"FLOWDEF" "bhorner" "1035309105" "bhorner:untitled1" "Submit flow definition" "" 
"FLOWDEF" "bhorner" "1035309127" "bhorner:untitled1" "Instantiated flow definition" "FlowId=6" 
"FLOWDEF" "bhorner" "1035309127" "bhorner:untitled1" "Trigger flow definition" "" 
"FLOW" "bhorner" "1035309127" "6:bhorner:untitled1" "Start flow" "" 


Data in the file is listed from top (earliest events) to bottom (latest events).

In the above example, the first line shows when J1 in the flow daily was submitted to LSF management host. The second line indicates when LSF management host dispatched the job, and the name of the host to which it was dispatched. When the job completes, the job ID and its resulting state and CPU usage are listed, as shown in the third line.