User Exits › The Rate Determination Exit (SJEX201) › The Split Job Exit (SPLITJOB)

The Split Job Exit (SPLITJOB)

A split job exit lets you distribute the proportional costs of a given job among two or more accounting units. It is identified as Exit 2 on the EXITS control statement.

In the sample source code provided, a table is constructed consisting of the following elements:

1. JOBNAME (KEY) corresponding to the name of the job for which costs are to be shared.
2. ACCNTNO (USER INFO) corresponding to the account to which part of the cost is to be charged.
3. PERCENTAGE indicating the portion of the cost for the job that is to be charged to this ACCNTNO.

For each job that is to have its cost split, one CREDIT control statement and multiple DEBIT control statements are produced by the exit. The value in the CREDIT control statement is equal to the sum of the values in the DEBIT control statements for a given job. One DEBIT control statement is generated for each of the account codes for that job based on the corresponding percentages. The account code is put into the first eight (8) positions of the user information field of the DEBIT control statements.

Normally, the exit is called by the first user-defined report in a CA JARS run and the generated CREDIT and DEBIT control statements are applied to the next report. The exit deletes all the records in the first report so that a report will not be produced. This will not affect any subsequent reports.

The report that uses the CREDIT and DEBIT control statements generated by the exit should be sorted by the user information field, causing the distributed charges to accumulate to the various account codes. This sample exit must be modified to accommodate your installation's accounting conventions.

This charge distribution capability is useful because:

• The costs of a job can be distributed to the individual accounting groups responsible for its use.
• These split costs can be displayed separately on one report.
• The TOTAL COST for an accounting group can be summarized and a bill produced.
• Utilization statistics for each job are retained even if its cost is split.

When assembling the source code for this exit, CAJRMAC must be concatenated to the SYSLIB DD statement. There is additional documentation in the source code itself.

Note: The split job exit is run with raw SMF data. If you want to use a history file, the source must be changed and reassembled.