When HiRDB is linked to OpenTP1, the statistical information collection timing and the statistics analysis utility's editing unit change if the operation mode employed is as discussed in (a) below.
Linkage of HiRDB to OpenTP1 refers to accesses from an application operating under TP1/Server Base or TP1/Message Control (version 03-06 or later).
This includes an application that accesses HiRDB from one of the OpenTP1 services, such as SPP (Service Provider Program) or MHP (Message Handling Program):
In this operation mode, a UAP in OpenTP1 can form multiple services within the same UAP, and each service can access a HiRDB that is appropriate for its purposes. In such a case, the name of the service requested to SPP or MHP (the first service within the transaction accompanying HiRDB access) is added to the statistical information as well as the UAP name of SPP or MHP (value of PDCLTAPNAME specified in the OpenTP1 user server definition for SPP or MHP). This service name is specified when SUP or TP1/Message Control issues a request using RPC; it is the name assigned to the service constituting SPP or MHP.
This service name can be used to determine the service that accessed HiRDB. It can also be used to establish correspondence with OpenTP1's transaction statistical information. Table 20-3 shows the correspondence between statistical information concerning a UAP accessing HiRDB and OpenTP1's statistical information.
Table 20-3 Statistical information for a UAP accessing HiRDB and OpenTP1's statistical information
Type of statistical information | Statistics log output timing | Statistics analysis utility's editing unit | DAT output file analysis | |||
---|---|---|---|---|---|---|
UAP statistical information | Other than OpenTP1's UAP | Each connection | Each UAP name
| Information can be analyzed using the transaction or UAP name as the key. | ||
OpenTP1's UAP | With no service name | Normal interface | ||||
XA interface | Each transaction | |||||
With service name | Normal interface | Each connection
| Each service name in UAP
| Information can be analyzed using the transaction, UAP, or service name as the key. | ||
XA interface | Each transaction
| |||||
SQL statistical information | Other than OpenTP1's UAP | Each SQL | Each UAP name
| Information can be analyzed using the UAP name as the key. | ||
OpenTP1's UAP | With no service name | |||||
With service name | Each SQL
| Each service name in UAP
| Information can be analyzed using the UAP or service name as the key. | |||
SQL optimizing information | Other than OpenTP1's UAP | Each SQL | ![]() | Information can be analyzed using the UAP name as the key. | ||
OpenTP1's UAP | With no service name | |||||
With service name | Each SQL
| ![]() | Information can be analyzed using the UAP or service name as the key. | |||
SQL object execution information | Other than OpenTP1's UAP | With no service name | Each SQL | ![]() | Information can be analyzed using the UAP name as the key. | |
OpenTP1's UAP | With service name | Each SQL
| ![]() | Information can be analyzed using the UAP or service name as the key. |
Legend:
: Not applicable
This includes an application that accesses HiRDB directly from OpenTP1's SUP (Service Utilization Program):
In this operation mode, the statistical information is the same as for a normal application that is not connected to OpenTP1. The UAP name used in the statistical information is the value of PDCLTAPNAME specified in the OpenTP1 user server definition for SUP.
When HiRDB is linked to TPBroker, TUXEDO or WebLogic Server, the statistical information collection timing and the statistics analysis utility's editing unit change. Table 20-4 shows the statistical information collection timing when HiRDB is linked to TPBroker, TUXEDO or WebLogic Server.
Table 20-4 Statistical information collection timing when HiRDB is linked to TPBroker, TUXEDO or WebLogic Server
Type of statistical information | Statistic log output timing | Statistics analysis utility's editing unit | DAT output file analysis | ||
---|---|---|---|---|---|
UAP statistical information | UAP other than TPBroker, TUXEDO or WebLogic Server | Each connection | Each UAP name
| Information can be analyzed using the transaction or UAP name as the key. | |
TPBroker, TUXEDO or WebLogic Server UAP | Normal interface | ||||
XA interface | Each transaction | ||||
SQL statistical information | UAP other than TPBroker, TUXEDO or WebLogic Server | Each SQL | Each UAP name
| Information can be analyzed using the UAP name as the key. | |
TPBroker, TUXEDO or WebLogic Server UAP | Normal interface | ||||
XA interface | |||||
SQL optimization information | UAP other than TPBroker, TUXEDO or WebLogic Server | Each SQL | Each UAP name
| Information can be analyzed using the UAP name as the key. | |
TPBroker, TUXEDO or WebLogic Server UAP | Normal interface | ||||
XA interface | |||||
SQL object execution information | UAP other than TPBroker, TUXEDO or WebLogic Server | Each SQL | Each UAP name
| Information can be analyzed using the UAP name as the key. | |
TPBroker, TUXEDO or WebLogic Server UAP | Normal interface | ||||
XA interface |