List of fields considered for job accounting¶
GlobalJobId¶
The global job identifier as assigned by a metascheduler or federation scheduler.
Example
Comments:¶
LocalJobId¶
The local job identifier as assigned by the batch queue
Example
Comments:¶
ProcessId¶
The process id of the jobs (PID).
Example
Comments:¶
JobName¶
The job or application name. For example, this could be the name of the executable that
ran, or the name of the batch queuing system’s name for the job.
Example
Comments:¶
Charge¶
This property represents the total charge of the job in the system’s allocation unit. For
example 100, 200, or 3000. The meaning of this charge will be site dependent. The value
for this property MAY include premiums or discounts assessed on the actual usage
represented within this record. Therefore, the reported charge might not be directly
reconstructable from the specific usage reported.
Note that “Charge” does not necessarily refer to a currency-based unit unless that is what
members of the grid virtual organization agree to as the definition. If charge denotes a
value in currency, standard currency codes should be used to indicate the currency unit
being reported.
Example
Comments:¶
Status¶
This property will represent the completion status of the job. For example, this may
represent the exit status of an interactive running process or the exit status from the batch
queuing system’s accounting record. The semantic meaning of status is site dependent.
Example
Comments:¶
JobDuration or WallDuration¶
Wall clock time that elapsed while the job was running.
Example
Comments:¶
EndTime¶
The time at which the usage consumption (i.e. “job”) completed. The value of this
property may depend on the selected queue system. For example some systems include
time to stage files, others do not.
Example
Comments:¶
StartTime¶
The time at which the usage consumption (i.e. “job”) started. The value of this property
may depend on the selected queue system. For example, some systems include time to
stage files, others do not.
Example
Comments:¶
MachineName¶
A descriptive name of the machine on which the job ran. This may be a system hostname,
or may be a site’s name for a cluster of machines. The identification of the machine by
name may assume the context of the grid in which the machine participates; i.e. machine
names may be unique within a specific grid, but do not need to be unique across the set of
all grids.
Example
Comments:¶
Host or DestinationResource¶
The system hostname on which the job ran.
Example
Comments:¶
SubmitHost or SourceResource¶
The system hostname from which the job was submitted.
Example
Comments:¶
Queue¶
The name of the queue from which the job was executed or submitted.
Example
Comments:¶
JobServiceLevel or ServiceLevel¶
This property identifies the quality of service associated with the resource consumption.
For example, service level may represent a priority associated with the usage.
Example
h3 Comments:
- JKN: This should perhaps be present in each block?
ALL OK:¶
JobUsageBlock¶
This is the block property of the job related fields.
Example
<ur:JobUsageBlock> <!—Job Record properties go in here --> </ur:JobUsageBlock>