The following table shows the statistical information collection timing related to a UAP accessing HiRDB.

Table 22-3 Statistical information collection timing related to a UAP accessing HiRDB

Statistical information type	Statistics log output timing	Statistics analysis utility's editing unit	DAT output file analysis
Statistical information about UAPs	For each connection	For each UAP name UAP execution count, UAP average execution time, execution count of each SQL statement, and so on Total and average for each item for each UAP execution	Can be analyzed using a UAP name as the key.
Statistical information about SQL code	For each SQL statement	For each UAP name Total and average lengths of SQL objects Total and average number of times objects are sent from the front-end server to the back-end server SQL execution count, processing time, and the number of rows processed	Can be analyzed using the UAP name as the key.
Statistical information about SQL optimization information	For each SQL statement	For each UAP name Average of count, execution time, and so on	Can be analyzed using the UAP name as the key.
Statistical information about SQL object execution	For each SQL statement	For each UAP name Average of count, execution time, and so on	Can be analyzed using the UAP name as the key.

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.

Here, linkage to OpenTP1 means accessing HiRDB from a TP1/Server Base or TP1/Message Control (version 03-06 or later) application.

(a) Operation mode in which a UAP in a client/server environment accesses HiRDB as part of the server UAP's service execution

In this mode of application, HiRDB is accessed from an SPP (service provider program) of OpenTP1, or from a service of a 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. The following table shows the correspondence between statistical information on a UAP accessing HiRDB, and OpenTP1's statistical information.

Table 22-4 Statistical information for a UAP accessing HiRDB and OpenTP1's statistical information

Statistical information type			Statistics log output timing	Statistics analysis utility's editing unit	DAT output file analysis
Statistical information about UAPs	Does not have a service name.	Normal interface	For each connection	For each UAP name UAP execution count, UAP average execution time, execution count of each SQL statement, and so on Total and average for each item for each UAP execution	Can be analyzed using a transaction or UAP name as the key.
		XA interface	For each transaction
	Has a service name.	Normal interface	For each connection Adds the first service name in the connection during log output.	For each service name in the UAP Execution count of each SQL statement, and so on	Can be analyzed using a transaction, UAP name, or service name as the key.
		XA interface	For each transaction Adds a service name from the first access within the log output timing.
Statistical information about SQL code	Does not have a service name.		For each SQL statement	For each UAP name Total and average lengths of SQL objects Total and average number of times objects are sent from the front-end server to the back-end server SQL execution count, processing time, and the number of rows processed	Can be analyzed using a UAP name as the key.
	Has a service name.		For each SQL statement Adds the first service name in the transaction during log output.	For each service name in the UAP Tally of the above information by service	Can be analyzed using a UAP name or service name as the key.
Statistical information about SQL optimization information	Does not have a service name.		For each SQL	For each UAP name Average of SQL execution count, execution time, and so on	Can be analyzed using a UAP name as the key.
	Has a service name.		For each SQL statement Adds the first service name in the transaction during log output.	For each service name in the UAP Tally of the above information by service	Can be analyzed using a UAP name or service name as the key.
Statistical information about SQL object execution	Does not have a service name.		For each SQL statement	For each UAP name Average of SQL execution count, execution time, and so on	Can be analyzed using a UAP name as the key.
	Has a service name.		For each SQL statement Adds the first service name in the transaction during log output.	For each service name in the UAP Tally of the above information by service	Can be analyzed using a UAP name or service name as the key.

(b) Operation mode in which HiRDB is accessed directly from the main routine

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 for C++, TUXEDO or WebLogic Server, the statistical information collection timing and the statistics analysis utility's editing unit vary. The following table shows the statistical information collection timing when HiRDB is linked to TPBroker for C++, TUXEDO or WebLogic Server.

Table 22-5 Statistical information collection timing when HiRDB is linked to TPBroker, TUXEDO or WebLogic Server

Statistical information type		Statistics log output timing	Statistics analysis utility's editing unit	DAT output file analysis
Statistical information about UAPs	Normal interface	For each connection	For each UAP name UAP execution count, UAP average execution time, execution count of each SQL statement, and so on Total and average for each item for each UAP execution	Can be analyzed using a transaction or UAP name as the key.
	XA interface	For each transaction
Statistical information about SQL code	Normal interface	For each SQL statement	For each UAP name Total and average lengths of SQL objects Total and average number of times objects are sent from the front-end server to the back-end server SQL execution count, processing time, and the number of rows processed	Can be analyzed using a UAP name as the key.
	XA interface
Statistical information about SQL optimization information	Normal interface	For each SQL statement	For each UAP name Average of count, execution time, and so on	Can be analyzed using a UAP name as the key.
	XA interface
Statistical information about SQL object execution	Normal interface	For each SQL statement	For each UAP name Average of count, execution time, and so on	Can be analyzed using a UAP name as the key.
	XA interface