This section provides a more detailed explanation of some of the terms that are relevant to UTM accounting.
Users in the sense of UTM accounting
The user of a UTM application for whom an account is to be created, is represented by the UTM user ID.
openUTM assigns the utilized resources to the LTERM partners as an alternative in UTM applications without real user IDs. The LTERM name of the connection user ID (TS applications and UPIC clients), the LU6 session name (LU6 partners) or the OSI association name (OSI TP partner) is used for applications or clients that have not explicitly signed on with a user ID.
In UTM applications without user IDs, openUTM assigns the resources used by terminals, UPIC clients or TS applications to the LTERM partners instead.
Accounting file
All information that the UTM accounting collects for the user-specific accounting of resources used is written by openUTM in the accounting file of the operating system.
The accounting file is administered by the BS2000 system administrator. The system administrator can evaluate this accounting file with the RAV tool.
Resources
This includes the following services:
Technical DP services, particularly CPU utilization and I/Os
Calling a particular program (program charge)
Calculation phase
The calculation phase is used as a starting point for the utilization of the accounting procedure.
In the calculation phase, openUTM determines the utilization of each resource for each program unit called and writes the values in the BS2000 accounting file as a calculation record. See section "Calculation phase" for more detailed information.
Calculation record
A calculation record is a record which openUTM writes in the BS2000 accounting file for each program unit run in the calculation phase. The accounting record type is UTMK. The data fields of the calculation record UTMK are described in the Appendix on "Structure of a calculation record".
Weight
A weight (factor) can be defined for each resource. This weight specifies how the resource is to be evaluated compared with other resources. The utilization of a resource is then introduced into the accounting procedure as the product “weight * resource utilization“. The weights for the individual resources are entered in the KDCDEF generation in ACCOUNT, see section "Determining the variant of the accounting procedure".
Accounting phase
openUTM determines the resource utilization for each program unit. When the program unit terminates, openUTM calculates the sum of utilization values based on the weights and the generated fixed prices.
The following resources are taken into account:
CPU utilization
Input/output to disk
Generated output jobs for printers
Fixed price for calling a program unit
The result is a number of derived accounting units that are added to the user-specific accounting unit counter.
openUTM only then writes a record with the contents of this counter in the accounting file
when the user signs off and is not signed on again to the UTM application via any other connection,
when the application is terminated normally,
or when a particular (generatable) maximum value is exceeded. You specify this maximum value in the KDCDEF generation with ACCOUNT ...,MAXUNIT= .
You must incorporate the weights in the generation of the application before the start of the accounting phase. You can choose between the following:
Fixed-price accounting
Utilization-oriented accounting
Combination of both variants
You will find a detailed description of the accounting phase in section "Accounting phase".
The accounting phase of UTM accounting can be enabled and disabled while the UTM application is running.
Accounting record
An accounting record is a record which openUTM writes to the accounting file in the accounting phase. The accounting record type is UTMA.
The data fields of the accounting record UTMA are described in the Appendix on "Structure of an accounting record".
Accounting units
Accounting units are the product of the utilization and weight of the respective resource. Only accounting units are counted in the UTM accounting facility. Using RAV, these units can be converted to costs, which are charged to the users.
Accounting unit counter
In a UTM application, openUTM keeps an accounting unit counter for each user and thereby accumulates the utilization of accounting units per user.
Fixed-price accounting
With this variant of the accounting function, a constant number of accounting units is calculated for a program unit run. This number is assigned to the transaction code when the application is generated. The weights of other resources are zero. In this manner you can also offer free services, e.g. informational functions.
Utilization-oriented accounting
With this variant of the accounting function, the current utilization of resources is calculated for a program unit run. The utilization values for the resource are weighted according to the generated weights. No fixed price is charged for calling program units.
Computer center accounting procedure (RAV)
The records written by UTM applications in the BS2000 accounting file can be processed further with RAV. The component RAV-UTM is available in RAV for this purpose.