The calculation phase provides approximate values that you can use to determine the weights and fixed prices for the utilization of a service. openUTM determines the resource utilization for each program unit run, creates a calculation record of type UTMK at the end of the program run and writes this record in the accounting file.
The calculation phase can also be enabled or disabled at any time via the UTM administration during live operation to check the generated weights and possibly to update them when regenerating, for example.
You should note, however, that openUTM writes a record in the accounting file after every program unit run when the calculation phase is activated. This has a negative impact on the performance of the application.
Activating the calculation phase
The calculation phase can be activated during KDCDEF generation or by administration, see openUTM manual “Generating Applications” and openUTM manual “Administering Applications”:
KDCDEF statement ACCOUNT ACC=CALC
or via UTM administration:
using the KDCAPPL CALC=ON command
or using WinAdmin/WebAdmin
or using the KDCADMI program call KC_MODIFY_OBJECT with obj_type=KC_DIAG_AND_ACCOUNT_PAR
Deactivating the calculation phase
The calculation phase can only be deactivated by UTM administration:
using the KDCAPPL CALC=OFF command
or using WinAdmin/WebAdmin
or using the KDCADMI program call KC_MODIFY_OBJECT with obj_type=KC_DIAG_AND_ACCOUNT_PAR
Data of a calculation record
A calculation record contains the following data:
name of the UTM application
transaction code (TAC) of the program unit
CPU utilization in the UTM task (msec)
length of the input message in bytes
length of the output message in bytes
number of output jobs to printers (Unix and Linux systems)
accounting units for LTAC calls
UTM users that have called the service
name of the LTERM partner through which the user is signed on
real time of the program unit run (msec)
Output messages that are intended for a follow-up program unit (e.g. after PEND ER) are also counted.