Control Statements and Tables › CA JARS Control Statements › PRIORITY Statement

PRIORITY Statement

This statement is optional. It serves as a mechanism for adjusting the accounting algorithm defined on the corresponding RATE statement. The PRIORITY statement factors the various dollar charge fields for a given report according to a requested job class and priority. The PRIORITY statement can be omitted when no factoring of charges is desired for a given report.

The CPU identification code on the PRIORITY statement performs the same function as it does on the RATE statement. The two statements act as a set and should have the same CPU identification to be associated with the appropriate input accounting record. Multiple PRIORITY statements may be required (matching the corresponding multiple RATE statements) for a given report so that data collected by different computers may be processed simultaneously, each using a different accounting algorithm.

The CPU identification on the PRIORITY statement must match the corresponding CPU identification on the accounting records for the charge factors to apply. If an accounting record is encountered that contains a CPU identification other than the one found on any PRIORITY statement for a given report, then the parameters default to the values on the first PRIORITY statement defined for that report. (Unless it has been altered by use of the grouping feature, the CPU identification is the first character of the system identification field in the SMF record for z/OS; and the CPU identification of the VSE record as placed there by the $JOBACCT data collection routine.

The charge flags on the PRIORITY statement indicate which of the computed charges based on the accounting algorithm defined on the corresponding RATE statement are to be factored by job class and priority. A blank flag suppresses any further factoring and a nonblank character (1) indicates that the corresponding charge is to be adjusted accordingly.

The priority factors on the PRIORITY statement enable you to define a factor for each priority level (0 through 9) which is used to weigh the individual charges in accordance with the charge flags. The priority factors are percentages; that is, 125 = 125%. Any blank entry in the Priority Factor Table defaults to the straight or unweighted factor of 100 (100%).

The class/partition factors on a PRIORITY statement enable you to define a factor for as many as seven different job classes for z/OS data, or partition IDs for VSE data. Each entry in the Class/Partition Factor Table is in the format xxnnn where:

xx

is the literal identifying the Job Class or Partition, F1, F2, A , B , and so forth.

nnn

is the Class/Partition Factor for xx

The class/partition factors are percentages; that is, 090 = 90%. If an accounting record is encountered with a job class or partition ID that does not match one of the entries in the Class/Partition Factor Table, the factor defaults to the straight or unweighted value of 100 (100%).

If a combination of class and priority factors are used, then they both factor the dollar charges simultaneously in accordance with the charge flags. The following is an example of a typical PRIORITY statement setup:

position   1         2         3         4         5                 8
  1........0.........0.........0.........0.........0....          ...0
  APRIORITY6111 070075080085090095   110120130J 050M 200

This PRIORITY statement defines the job class and priority factors for Report A to be used against all input records with the CPU identification 6.

The priority factors in this example are as follows:

Priority    Factor
0            .70
1            .75
2            .80
3            .85
4            .90
5            .95
6           1.00 (default)
7           1.10
8           1.20
9           1.30
all others  1.00 (default)

The job class factors in this example are as follows:

Class       Factor
J            .50
M           2.00
all others  1.00 (default)

For example, the net factor for a class J job with a priority 9 would be .65 to be multiplied against the following computed dollar charges as per the corresponding RATE statement at the job and step level:

• Processor Charge
• I/O Charge
• U/R Charge

The setup charge flag has not been turned on; therefore, the setup charge is not adjusted further.

Note: Use a blank in the flag fields to suppress factoring charges. Use a 1 to factor charges according to priority and class factors.