pdstbegin (Start output of statistical information)

Function

The pdstbegin command outputs to the statistics log file statistical information about a unit located at the server machine with a specified host name. When output of statistical information is to be stopped, the pdstend command must be executed.

The statistical information is output to the statistics log file named pdstj1 or pdstj2 at each host.

The obtained statistical information can be read by the statistics analysis utility. For details about the statistics analysis utility, see Chapter 14. Statistics Analysis Utility (pdstedit).

Executor

HiRDB administrator

Format

HiRDB/Single Server

pdstbegin [-k statistical-information-type[,statistical-information-type]...]
         [-m interval] [-a|-s server-name[,server-name]...}]

HiRDB/Parallel Server

pdstbegin [-k statistical-information-type[,statistical-information-type]...]
         [-m interval] [{-x host-name|-u unit-identifier}]
         [{-a|-s server-name[,server-name]...}]

Options

Specifies the type of statistical information to be output:

sys
System activity statistical information
uap
UAP statistical information
sql
SQL statistical information
sqh
SQL statement statistical information (statistical information about issued data manipulation SQL, definition SQL, and the LOCK statement and SQL)
This statistical information is output when the output of SQL statistical information is specified.
buf
Global buffer pool statistical information
fil
Statistical information on HiRDB files for database manipulation
dfw
Deferred write processing statistical information
idx
Index statistical information
sop
SQL static optimization information
dop
SQL dynamic optimization information
pcd
SQL object execution information
obj
Statistics on SQL object transmission (applicable to HiRDB/Parallel Server only)
fsv
Statistical information about the activities of external servers
hba
Statistical information about the utilization status of external servers
all
All statistical information except sqh, pcd, obj, fsv, and hba

When system activity statistical information (-k sys specified) is to be output to the statistics log file, specifies in minutes the interval at which the information is to be output.

Specifies the identifier of the unit or the name of the host for which statistical information is to be output. If this option is omitted, statistical information for the entire HiRDB system is output to the statistics log file.

-x host-name[Figure]<identifier> ((1-32))
Specifies the name of the host for which statistical information is to be output. If the standby-less system switchover (1:1) facility is used and the alternate system is in use, the command starts output of statistical information about both hosts, whether the specified host name belongs to the normal BES or to the alternate BES.
-u unit-identifier[Figure]<identifier> ((4 characters))
Specifies the identifier of the unit for which statistical information is to be output. If the standby-less system switchover (1:1) facility is used and the alternate system is in use, the command starts output of statistical information about both units, whether the specified unit identifier belongs to the normal BES or to the alternate BES.

Specifies the servers for which statistical information is to be output. When this option is omitted, the statistical information to be output depends on the server type, as shown in Tables 2-20 and 2-21.

-a
Specifies that statistical information about the entire system and all servers is to be output.
This option and the -s option are mutually exclusive.
-s server-name[, server-name][Figure]<identifier> ((1-8))
Specifies the name of a server for which statistical information is to be output.
This option and the -a option are mutually exclusive. If the standby-less system switchover (1:1) facility is used and the alternate system is in use, the command starts output of statistical information about both servers, whether the normal BES or the alternate BES is specified.

Rules

  1. The pdstbegin command can be executed only while HiRDB is active.
  2. The pdstbegin command must be executed at the server machine containing the single server or the server machine where the system manager is located.
  3. Once output of statistical information begins, it continues until HiRDB is shut down or the pdstend command is executed.
  4. The type of statistical information to be output depends on the specification of the -s option. Table 2-20 (for a HiRDB/Single Server) and Table 2-21 (for a HiRDB/Parallel Server) show the relationship between the statistical information to be output and the specification of the -s option.

    Table 2-20 Relationship between statistical information output and s option specification: HiRDB/Single Server

    Types of statistical informationServers specified with -s option (Single Server)
    sysY
    uapY
    sqlY
    sqhY
    bufY
    filY
    dfwY
    idxY
    sopY
    dopY
    pcdY
    obj[Figure]
    fsv[Figure]
    hba[Figure]

Y:Statistical information is output.

[Figure]: statistical information is not output.

Table 2-21 Relationship between statistical information output and -s option specification: HiRDB/Parallel Server

Types of statistical informationServers specified with -s option
FESDSBES
sysYYY
uapY[Figure][Figure]
sqlY[Figure][Figure]
sqhY[Figure][Figure]
buf[Figure]YY
fil[Figure]YY
dfw[Figure]YY
idx[Figure]YY
sopY[Figure][Figure]
dopY[Figure][Figure]
pcdYYY
obj[Figure]YY
fsv[Figure][Figure]Y
hba[Figure][Figure]Y

Y: Statistical information is output.

[Figure]: Statistical information is not output.

FES: Front-end server

DS: Dictionary server

BES: Back-end server

Notes

  1. The following are the pdstbegin command's return codes:
    0: Normal termination
    8: Abnormal termination (such as an invalid option or rsh error)
  2. The pdstbegin command can also be executed using pdststart as the command name.
  3. If none of the servers in the unit has started, statistical information about the unit is not acquired.
  4. When acquisition of a server's sys (statistical information about system activities) is started, acquisition of the unit's sys also begins.
  5. When HiRDB is terminated and then restarted, the statistical information output operation is not inherited. To output statistical information after HiRDB has started, you must re-execute the pdstbegin command.
  6. Once a server is terminated, the statistical information output operation is not inherited when the server is started normally. To output statistical information for a server that was terminated, the pdstbegin command must be re-executed after the server has been started normally.
  7. Execute the pdls -d stj command to determine whether statistical information is being output.
  8. UAP-related statistical information is output only for UAPs that executed between the time the pdstbegin command was entered and the time the pdstend command was entered. For UAPs executing in the OLTP environment, UAP-related statistical information is output only for transactions that executed between the time the pdstbegin command was entered and the time the pdstend command was entered.
  9. SQL-related statistical information is output only for SQLs that executed between the time the pdstbegin command was entered and the time the pdstend command was entered.
  10. UAP-related statistical information and SQL-related statistical information may not be in agreement, depending on the timing of the pdstbegin command and pdstend command entry, as shown in Figure 2-11.

    Figure 2-11 Relationship between output statistical information and entry of pdstbegin and pdstend commands

    [Figure]

  11. Following are the times at which the different types of statistical information are output:
    sys
    Output at the time interval specified in the -m option
    uap
    Output when connected to HiRDB and when disconnected from HiRDB
    sql
    Output when SQL execution starts and when SQL execution terminates
    sqh
    Output information during PREPARE and during execution of an embedded data-type SQL statement.
    buf, fil, dfw, idx
    Output at synchronization points
    sop
    Output when the specified SQL object was not found in the SQL object buffer during dynamic and static SQL preprocessing
    dop
    Output when an SQL statement other than FETCH or CLOSE was executed
    pcd
    Output when an SQL object is executed
    obj
    Output when an SQL object execution request is issued at the dictionary server and back-end server.
    fsv
    Output when the transaction has terminated.
    hba
    Output when an SQL statement is executed on an external server.
  12. The statistical information listed below is collected at synchronization points, and the information that exists between synchronization points is edited. Therefore, this statistical information is not collected unless there are at least two synchronization points:
    • Global buffer pool statistical information
    • Statistical information on HiRDB files for database manipulation
    • Deferred write processing statistical information
    • Index statistical information
      To collect this statistical information, synchronization points must be created by executing the pdlogswap command immediately after the pdstbegin command and immediately before the pdstend command.
  13. SQL statement statistical information is output when the output of SQL statistical information is specified.
  14. When the standby-less system switchover (effects distributed) facility is used, if restart occurs after execution of the pdstbegin command but before execution of the pdstend command, the same statistical information is output after the restart as before the restart. If system switchover occurs after execution of the pdstbegin command but before execution of the pdstend command (as in the case of a server that was being used as the running system on the erroneous unit), the same statistical information is output after the switchover at the target accepting unit as before the switchover. To stop output of statistical information, you must execute the pdstend command.
  15. When the standby-less system switchover (effects distributed) facility is used and the -x or -u option is specified, the target of the pdstbegin command execution is different before and after system switchover, as shown below:
    Server typeServer statusTarget
    Host BESExecutingY
    StandbyN
    Guest BESExecutingY
    Acceptable statusN
    Legend:
    Y: Can be executed
    N: Cannot be executed
  16. You should note the following when the standby-less system switchover (effects distributed) facility is used and the -x or -u option is specified together with the -s option:
    • Acquisition of statistical information begins if the back-end server specified in the -s option on the unit specified in the -x or -u option is running when the pdstbegin command is executed.