OpenTP1 Version 7 Operation
Uptime statistics can be collected, edited, and output from an unload journal file by the jnlstts command. The uptime statistics that can be edited and output by the jnlstts command include system statistics, transaction statistics, statistics about response, and statistics about communication delay. The uptime statistics that can be edited and output by the jnlmcst command are MCF uptime statistics.
You can use the following commands to output uptime statistics without using an unload journal file:
Executing the jnlstts command with sys specified in the -e option (edit item) edits and outputs collected the system statistics chronologically. Only a needed range of information can be edited and output by specifying the editing range.
The contents of system statistics are the same as those which can be output to system journal files. For details, see Table E-2.
Executing the jnlstts command with trn specified in the -e option (edit item) edits and outputs collected transaction statistics chronologically on the basis of the names of, or service names for, the user servers originating transaction branches. Only a needed range of information can be edited and output by specifying the editing range.
Note that, before obtaining transaction statistics, any other than nothing must be specified in trn_statistics_item in the user service definition.
The following table shows the edited contents of transaction statistics.
Table 4-8 Edited contents of transaction statistics
Edited contents | Unit | ||||
---|---|---|---|---|---|
Item | Occurrences | Edited values | |||
Average | Maximum | Minimum | |||
Transaction branch execution time (including time for synchronization point processing) | N | Y | Y | Y | Microseconds |
Transaction branch execution time for synchronization point processing | N | Y | Y | Y | Microseconds |
Transaction branch determinations | Y | N | N | N | Events |
Transaction branch and child-branch determinations | Y | N | N | N | Events |
Process type for transaction branch determination | Y | N | N | N | Events |
Executing the jnlstts command with rsp specified in the -e option (edit item) edits and outputs the collected statistics about response chronologically on the basis of service names. Only a needed range of information can be edited and output by specifying the editing range.
Note that, before obtaining statistics about response, Y must be specified in rpc_response_statistics in the user service definition.
To obtain the RPC type and response time shown in Table 4-9, specify Y for the rpc_response_statistics operand in the user service definition for the client UAP, that is, the caller of dc_rpc_call. If not specified, the jnlstts command outputs zero as the edited results without obtaining these information items.
To obtain the service execution time and service wait time, specify Y in the rpc_response_statistics operand in the user service definition for the client or server.
The following table shows the edited contents of statistics about response.
Table 4-9 Edited contents of statistics about response
Edited contents | Unit | ||||
---|---|---|---|---|---|
Item | Occurrences | Edited values | |||
Average | Maximum | Minimum | |||
RPC type | Y | N | N | N | Events |
Response time | Y | Y | Y | Y | Microseconds |
Service execution time | Y | Y | Y | Y | Microseconds |
Service wait time | Y | Y | Y | Y | Microseconds |
Executing the jnlstts command with dly specified in the -e option (edit item) edits and outputs collected statistics about communication delay chronologically on the basis of destination node identifiers. Only a needed range of information can be edited and output by specifying the editing range.
The following table shows the edited contents of statistics about communication delay.
Table 4-10 Edited contents of statistics about communication delay
Edited contents | Unit | ||||
---|---|---|---|---|---|
Item | Occurrences | Edited values | |||
Average | Maximum | Minimum | |||
Communication delay | Y | Y | Y | Y | Microseconds |
The jnlmcst command edits and outputs the MCF statistics about the send and receive messages. Statistics can be edited and output on the basis of logical terminal names or application names. In either case, only a needed range of information can be output by specifying the editing range and journal collection mode.
The jnlmcst command edits and outputs the MCF uptime statistics created from the statistical journals collected by MCF (IJ, GJ, OJ, and AJ). Therefore, to edit and output the MCF uptime statistics, perform the following definitions in advance:
The following table shows the edited contents of MCF uptime statistics.
Table 4-11 Edited contents of MCF uptime statistics
Information type | Edited contents | Unit | |||||
---|---|---|---|---|---|---|---|
Event | Output format | Edited values | |||||
Minimum | Maximum | Average | Total | ||||
Information relating to receiving messages | Number of inquiry message inputs | 0 to 4294967295 or * | Y | Y | Y | Y | Inputs |
Number of receive-only message inputs | 0 to 4294967295 or * | Y | Y | Y | Y | Inputs | |
Number of receive request inputs | 0 to 4294967295 or * | Y | Y | Y | Y | Inputs | |
Receive message size | 0 to 4294967295, * or - | Y | Y | Y | N | Bytes | |
Information relating to sending messages | Number of priority branch send request issues | 0 to 4294967295 or * | Y | Y | Y | Y | Issues |
Number of general branch send request issues | 0 to 4294967295 or * | Y | Y | Y | Y | Issues | |
Number of response send request issues | 0 to 4294967295 or * | Y | Y | Y | Y | Issues | |
Number of outputs (segments) | 0 to 4294967295 or * | Y | Y | Y | Y | Outputs |
By using the dcreport command, you can edit the system statistics collected into shared memory, and output them to the standard output in real time.
For details about the system uptime statistics that can be edited and output using this command and the items to be edited, see Table E-1 and Table E-2. When you use this command to edit and output system uptime statistics, you need to specify set statistics=Y in the system common definition beforehand.
The mcfstats command acquires the MCF statistics. The mcfreport command edits and outputs the acquired MCF statistics.
The following table lists the types of the MCF statistics that these commands can acquire, edit and output. To acquire, edit and output the MCF statistics by these commands, specify mcfmcomn -w stats=yes first in the MCF manager definition.
Table 4-12 Types of MCF statistics
Type | Description | Usage |
---|---|---|
Receive message information (for a service group) |
|
Tuning related to service groups |
Send message information (for a logical terminal) |
Tuning related to logical terminals | |
Connection wait information (for a communication server) |
Tuning for the maximum processing multipliers (mcfttred -m) |
The opportunities to start and terminate outputting the statistics are:
The following table lists the contents of the MCF statistics edited by the mcfreport command.
Table 4-13 Edited contents of the MCF statistics (mcfreport command)
Edited values | Unit | |||||
---|---|---|---|---|---|---|
Edit type | Obtained value | Occurrences | Edited values | |||
Average | Maximum | Minimum | ||||
Information about messages to receive | Number of messages in the schedule queue | Y | Y | Y | Y | Requests |
Scheduling wait time | N | Y | Y | Y | Seconds | |
Information about messages to send | Number of messages in the schedule queue | Y | Y | Y | Y | Requests |
Scheduling wait time | N | Y | Y | Y | Seconds | |
Information about wait for connection | Number of messages in the schedule queue | Y | Y | Y | Y | Requests |
Scheduling wait time | N | Y | Y | Y | Seconds |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.