20.1.5 When linked to an OLTP system

Organization of this subsection
(1) When linked to OpenTP1
(2) When linked to TPBroker, TUXEDO or WebLogic Server

(1) When linked to OpenTP1

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).

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

This includes an application that accesses HiRDB from one of the OpenTP1 services, such as SPP (Service Provider Program) or MHP (Message Handling Program):

[Figure]

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 informationStatistics log output timingStatistics analysis utility's editing unitDAT output file analysis
UAP statistical informationOther than OpenTP1's UAPEach connectionEach UAP name
  • UAP executions count, average UAP execution time, executions count for each SQL statement, etc.
  • Total and average values for each item per UAP execution
Information can be analyzed using the transaction or UAP name as the key.
OpenTP1's UAPWith no service nameNormal interface
XA interfaceEach transaction
With service nameNormal interfaceEach connection
  • During log output, name of the first service in the connection is added.
Each service name in UAP
  • Executions count for each SQL statement, etc.
Information can be analyzed using the transaction, UAP, or service name as the key.
XA interfaceEach transaction
  • Name of the first service in the log output period is added.
SQL statistical informationOther than OpenTP1's UAPEach SQLEach UAP name
  • Total and average lengths of SQL objects
  • Total and average number of object transmissions from front-end server to back-end server
  • SQL executions count, processing time, number of rows processed
Information can be analyzed using the UAP name as the key.
OpenTP1's UAPWith no service name
With service nameEach SQL
  • During log output, name of the first service in the transaction is added.
Each service name in UAP
  • Summary of the above information for each service
Information can be analyzed using the UAP or service name as the key.
SQL optimizing informationOther than OpenTP1's UAPEach SQL[Figure]Information can be analyzed using the UAP name as the key.
OpenTP1's UAPWith no service name
With service nameEach SQL
  • During log output, name of the first service in the transaction is added
[Figure]Information can be analyzed using the UAP or service name as the key.
SQL object execution informationOther than OpenTP1's UAPWith no service nameEach SQL[Figure]Information can be analyzed using the UAP name as the key.
OpenTP1's UAPWith service nameEach SQL
  • During log output, name of the first service in the transaction is added.
[Figure]Information can be analyzed using the UAP or service name as the key.

Legend:

[Figure]: Not applicable

(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):

[Figure]

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.

(2) When linked to TPBroker, TUXEDO or WebLogic Server

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 informationStatistic log output timingStatistics analysis utility's editing unitDAT output file analysis
UAP statistical informationUAP other than TPBroker, TUXEDO or WebLogic ServerEach connectionEach UAP name
  • UAP executions count, average UAP execution time, executions count for each SQL, etc.
  • Total and average values for each item per UAP execution
Information can be analyzed using the transaction or UAP name as the key.
TPBroker, TUXEDO or WebLogic Server UAPNormal interface
XA interfaceEach transaction
SQL statistical informationUAP other than TPBroker, TUXEDO or WebLogic ServerEach SQLEach UAP name
  • Total and average lengths of SQL objects
  • Total and average number of object transmissions from front-end server to back-end servers
  • SQL executions count, processing time, number of rows processed
Information can be analyzed using the UAP name as the key.
TPBroker, TUXEDO or WebLogic Server UAPNormal interface
XA interface
SQL optimization informationUAP other than TPBroker, TUXEDO or WebLogic ServerEach SQLEach UAP name
  • Average executions count and execution time
Information can be analyzed using the UAP name as the key.
TPBroker, TUXEDO or WebLogic Server UAPNormal interface
XA interface
SQL object execution informationUAP other than TPBroker, TUXEDO or WebLogic ServerEach SQLEach UAP name
  • Average executions count and execution time
Information can be analyzed using the UAP name as the key.
TPBroker, TUXEDO or WebLogic Server UAPNormal interface
XA interface