Job usage data for charge-back accounting support

WebSphere Extended Deployment 6.1.0.1 provides charge-back accounting information for grid jobs for all operating systems. Charge-back accounting allows you to determine the computing costs of grid job execution for work that has been performed by various users and groups.

The job scheduler records usage data for charge-back accounting when enabled through the administrative console. This function is available for all operating systems and can be enabled and disabled through configuration settings. Job usage information is not enabled by default.

Accounting information for each job includes:
The DDL statements for the job scheduler JOBUSAGE table are defined in the CreateLRSCHEDTables*.ddl files of the ${install_root}/longRunning directory. An example schema definition is:
CREATE TABLE "LRSSCHEMA"."JOBUSAGE" (
"JOBID" VARCHAR(250) NOT NULL ,
"SUBMITTER" VARCHAR(256),
"CPUCONSUMEDSOFAR" BIGINT NOT NULL,
"JOBSTATE" VARCHAR(32) NOT NULL,
"SERVER" VARCHAR(250) NOT NULL,
"NODE" VARCHAR(250) NOT NULL,
"STARTTIME" VARCHAR(64) NOT NULL,
"LASTUPDATE" VARCHAR(64) NOT NULL,
"ACCNTING" CHAR(64) ) IN "USERSPACE1" ;
The table data can be accessed with an SQL query, for example:
select * from LRSSCHEMA.JOBUSAGE where JOBID='PostingSampleEar:99'

Programatic access to the scheduler job usage table data must specify an isolation level of read uncommitted, so as to impede active job execution or the recording of accounting data. The STARTTIME and LASTUPDATE represent the return value of System.currentTimeMillis(). See ++ below for more detail.

[For z/OS operating system]

Job usage SMF record layout

The purpose of the JobUsage SMF record is to record information about a WebSphere Extended Deployment grid container job inside a WebSphere Application Server for z/OS transaction server. The SMF type 120 record, subtype 20, is the WebSphere Extended Deployment Job usage record. There is one job usage section per record as shown in the following table:

Table 1. Job usage SMF record layout
Offset (decimal) Offset (hexadecimal) Name Length Format Description
0 0 SM120XVL 2 binary Length of the JobUsage section
2 2 SM120XJL 1 binary Length of the job identifier field; maximum is 250
3 3 SM120XJ 250 EBCDIC Job identifier
           
254 FE SM120XT 32 EBCDIC Job submitter
286 11E SM120XSL 1 binary Length of the job state field; maximum is 32
287 11F SM120XS 31 EBCDIC Job state (final). Can be one of: ended, execution failed, or restartable
319 13F SM120XNL 1 binary Length of the server name field; maximum is 250
320 140 SM120XN 250 EBCDIC Server name.
570 23A SM120XOL 1 binary Length of the node name field; maximum is 250
571 23B SM120XO 250 EBCDIC Node name
821 335 SM120XAL 1 binary Length of the accounting information field; maximum is 64
822 336 SM120XA 64 EBCDIC Accounting information.
886 376 SM120XBL 1 binary Length of the job start time field; maximum is 64
887 377 SM120XB 64 EBCDIC Job start time ++
951 3B7 SM120XLL 1 binary Length of the last update time field; maximum is 64
952 3B8 SM120XL 64 EBCDIC Last update time++
1016 3F8 SM120XPL 1 binary Length of the CPU consumed field; maximum is 64
1017 3F9 SM120XP 64 EBCDIC CPU consumed ^ ^

** The offsets of the fields which follow are based upon a full field. The field contains data that is the maximum field length. The actual offset in the record is the start of the field, plus the length of the field, plus one.

++ Represented as a character string that is the number of milliseconds since January 1, 1970, 00:00:00 GMT.

^ ^ Represented as a character string that is the number of units of CPU consumed, where one unit is 109 second. The symbol ^ means ten raised to the -9th power; that is, .000000001.