The ACCOUNT control statement allows you to define:
whether the accounting or calculation phase of the UTM accounting is to be activated at the start of the UTM application,
when an accounting record is written,
the weighting with which resources are to be evaluated in the accounting phase.
If the ACCOUNT control statement is not specified, then this has the same effect as ACCOUNT ACC=NO. Only the first ACCOUNT statement of a KDCDEF run is evaluated.
UTM accounting can also be activated and deactivated via the administration, even if no ACCOUNT statement is issued in the KDCDEF generation. In this case the default values apply.
You may only specify the ACCOUNT statement once within a KDCDEF run.
|
|
ACC= | specifies which UTM accounting functions are to be executed. ACC is a mandatory operand. |
YES | openUTM is to activate the accounting phase of UTM accounting after the application start. |
NO | The accounting functions are not activated after the application start. |
CALC | openUTM is to activate the calculation phase after the application start. |
CPUUNIT= | cpuunit specifies the weighting with which a CPU second is evaluated in the accounting phase of the UTM accounting. Fractions of a CPU second are billed proportionally. Default value: 0 |
IOUNIT= | iounit specifies the weighting with which 100 disk I/Os are evaluated in the accounting phase. Fractions of 100 inputs/outputs are billed accordingly. You must enter an integer here. Default value: 0 Unix, Linux and Windows systems: This operand is not used because these operating systems do not provide information on disk I/O. |
MAXUNIT= | maxunit specifies the number of accounting units at which openUTM is to create an accounting record for a particular user (USER). You must enter an integer here. Default value: Minimum value: 1 |
OUTUNIT= | outunit specifies the weighting with which a print job (FPUT NE) is evaluated for accounting purposes. Default value: 0 |