Appendix E.5 Real-time statistics

Organization of this subsection
(1) Details about real-time statistics
(2) Details about real-time statistics (when a target is specified)

(1) Details about real-time statistics

The following table shows the details about real-time statistics.

Table E-6 Details about real-time statistics

Type (type of real-time statistics)Edited informationDetails
Event (real-time statistics item name)Acquired information
CPD (checkpoint dump information)Collection of cpdNumber of itemsNumber of events that caused the collection of checkpoint dumps
Length of timeInterval between the previous checkpoint and the current checkpoint (interval of events that cause checkpoint collection). Since a checkpoint is collected after the output of a preset number of journal blocks, the frequency of collecting checkpoint dumps is expressed as a time value here.
Validation of cpdNumber of itemsNumber of events that caused the collection of checkpoint dumps
Length of timeLength of time from an event that collects a checkpoint dump and the startup of collection processing in each system server to the completion of validation of the checkpoint dump
JNL (journal information)Buffer full occurrencesNumber of itemsBuffering is disabled because the free area in the buffer was too small when an attempt was made to store a journal record in the current buffer. There are three journal buffers in the system, of which one is the current buffer.
Waits for an available bufferNumber of itemsThe system is waiting for a free buffer. Journals cannot be buffered because all three journal buffers are full or journals are being output.
Journal outputNumber of timesNumber of times journal blocks are output
Data lengthData length in a journal block. You can make an assumption about the probable number of journals that are generated during a unit of time based on this value.
I/O waitsNumber of timesNumber of times journal output is completed
Number of buffers x 100Number of buffers waiting for output when journal output is completed. The number of buffers is multiplied by 100 to prevent truncation of the decimal part of the average value.
WriteNumber of timesNumber of outputs, including journal outputs and outputs of file management information when journal swapping occurs.
Length of timeLength of time required for writing journal files.
SwapNumber of timesNumber of times journal files are swapped
Length of timeLength of time required for swapping journal files
Journal inputNumber of timesNumber of times data is input from a journal file
Data lengthLength of data input from a journal file
ReadNumber of timesNumber of inputs, including journal inputs and inputs of file management information when journal swapping occurs.
Length of timeLength of time required for reading journal files.
LCK (lock information)Lock acquisitionNumber of itemsNumber of waits for a lock
Length of timeLength of time from the occurrence of a lock wait and entry into the wait status to release of the wait status. The lock described here indicates the internal locks set by the lock service issued by the dc_lck_get function, DAM, TAM, and MQA.
Lock waitNumber of itemsNumber of waits for a lock
Queue lengthLength of the wait queue when lock waits are generated
DeadlockNumber of itemsNumber of deadlocks that occurred. The deadlocks detected by the system server are not acquired in the real-time statistics of each service.
NAM (name information)Global Cache hitsNumber of timesNumber of times the information about the service group stored in the global cache area is referenced during a search for information about the service group. Note that the number of references may not match the number of communications.#1
Local Cache hitsNumber of timesNumber of times the information about the service group stored in the local cache area is referenced during a search for information about the service group. Note that the number of references may not match the number of communications.#1
LookupNumber of timesNumber of times the information about the service group stored in the global cache area or the local cache area is referenced when a UAP executes an RPC.
When the information about the applicable service group is not stored in the global cache area or the local cache area, global cache hits or local cache hits are not counted. However, the number of searches for service information is counted. As a result, the number of global cache hits and the number of local cache hits may not match the number of searches for service information.
OSL (shared memory management information)Common static memory(acquired)Number of timesNumber of times the function for allocating or releasing static shared memory is issued plus 1
Memory block sizeTotal size of static shared memory blocks used after static shared memory blocks are allocated or released
Common static memory(pool)Number of timesNumber of times the pool size is updated plus 1
Memory block sizeMaximum size of static shared memory blocks in use (size up to the highest memory block currently in use). This information is acquired if the previous pool size is updated after the allocation or release of blocks.
The pool size is the total size of the shared memory in use, including empty areas in the pool created by releasing the allocated shared memory.
Accordingly, specify a value larger than this size in the static_shmpool_size operand in the system environment definition.
This information is the total size from the beginning of acquisition, not the size acquired during the preset length of time for acquisition specified in the rts_trcput_interval operand in the real-time statistics service definition.
Common dynamic memory(acquired)Number of timesNumber of times the function for allocating or releasing the dynamic shared memory is issued plus 1
Memory block sizeTotal size of dynamic shared memory blocks in use after allocating or releasing the dynamic shared memory blocks
Common dynamic memory(pool)Number of timesNumber of times the pool size is updated plus 1
Memory block sizeMaximum size of dynamic shared memory blocks in use (size up to the lowest memory block currently in use). This information is acquired if the previous pool size is updated after allocation or release of blocks. Specify a value larger than this size in the dynamic_shmpool_size operand in the system environment definition.
This information is the total size from the beginning of acquisition, not the size acquired during the preset length of time for acquisition specified in the rts_trcput_interval operand in the real-time statistics service definition.
PRC (process information)Process generationsNumber of timesNumber of processes started by the OpenTP1 system. This number includes the number of processes of non-resident servers.Because only the number of processes started by the process service is counted, the process service itself and the processes that are not started by the process service are not included.
UAP abnormal terminationsNumber of timesNumber of times UAP processes terminate abnormally for each user server. This number includes cases when a user server goes down but does not include processes that terminate abnormally after dc_rpc_close. For details about the relationship between process termination and item counts, see Table E-7.
System server abnormal terminationsNumber of timesNumber of times the system server terminates abnormally. This information may not be acquired if the system server terminates abnormally and the OpenTP1 system goes down.
Note
If OpenTP1-provided servers that operate as SPPs (such as TP1/EE, the RAP-processing server, and RTSSUP) go down, those terminations are included in UAP abnormal terminations, not System server abnormal terminations.
For details about the relationship between process termination and item counts, see Table E-7.
Process terminationsNumber of timesNumber of times processes terminate, including normally terminated processes, processes that are stopped by the dcsvstop command with the -f option or by the prckill command, and by processes that are forcibly stopped due to an actual time-monitoring timeout error. This information does not include the counts of UAP abnormal terminations and System server abnormal terminations. For details about the relationship between process termination and item counts, see Table E-7.
Number of processesNumber of timesNumber of observations (monitoring) during a preset length of time. Monitoring is usually performed every 60 seconds. Monitoring is performed every 2 seconds when the dcstart, dcstop, dcsvstart, dcsvstop, eesvstart, or eesvstop command is executed.
Number of processesNumber of system services and UAP processes started in the OpenTP1 system. Because this information includes only the number of processes started by the process service, the process service itself and the processes that are not started by the process service are not included in the count. This information is the total number from the beginning of acquisition, not the number acquired during the preset length of time for acquisition specified in the rts_trcput_interval operand in the real-time statistics service definition.
QUE (message queue information)Read messageNumber of timesNumber of times messages are read from the queue file
Message lengthLength of a message read from the queue file
Write messageNumber of timesNumber of times messages are written into the queue file
Message lengthLength of a message written into the queue file
Read errorsNumber of itemsNumber of cases where errors occurred during input from a physical file (abnormal-condition cases)
Write errorsNumber of itemsNumber of cases where errors occurred during output to a physical file (abnormal-condition cases)
Waits for an available bufferNumber of itemsNumber of cases where required I/O buffers became insufficient due to congestion of requests for the target queue file. Use this value to check the number of I/O buffers in the message queue service definition.
Real readsNumber of timesNumber of inputs generated from a physical file when the I/O buffer contains no messages. To decrease this value, increase the number of I/O buffers in the message queue service definition.
Real writesNumber of timesNumber of outputs generated for a physical file. When you compare this value and the value for Write message, you can determine how many write requests were input and output at one time. To decrease the number of inputs and outputs, increase the number of I/O buffers in the message queue service definition. When you use the deferred write facility, the number of outputs to a physical file is included in the count of Number of delay writings. Therefore, Hitachi recommends that you set 0 for Real writes.
Number of delay writingsNumber of timesNumber of deferred write requests that are generated when the deferred write facility is used
Number of timesNumber of writes (Real writes) to a physical file per deferred write request when the deferred write facility is used
Number of delay writing recordsNumber of timesNumber of times deferred write requests are generated for each physical file when the deferred write facility is used
Number of recordsNumber of records whose writing is deferred. Although this information is acquired for each physical file, the information is displayed for all the physical files and not for each physical file. Use this value to tune the number of I/O buffers in the message queue service definition.
Delay writing record rateNumber of timesNumber of times deferred write requests are generated for each physical file when the deferred write facility is used
Percentage of messagesPercentage of all messages whose writing is deferred. Although this information is acquired for each physical file, the information is displayed for all the physical files and not for each physical file. Use this value to tune the number of I/O buffers in the message queue service definition.
RPC (RPC information)RPC callsNumber of timesNumber of times synchronous-response dc_rpc_call and dc_rpc_call_to are called. This information is acquired when synchronous-response dc_rpc_call and dc_rpc_call_to are successful.
Length of timeLength of time between sending a request from the client to the server in synchronous-response dc_rpc_call and dc_rpc_call_to, and receiving a response from the server. This value is acquired when synchronous-response dc_rpc_call and dc_rpc_call_to are successful. The time includes the length of time for retries if the transmission of a request to the server in synchronous-response dc_rpc_call and dc_rpc_call_to fails and the transmission of the request to the server is retried.
RPC calls(chained)Number of timesNumber of times chained dc_rpc_call and dc_rpc_call_to are called between the start and end of a chained RPC. This information is acquired when chained dc_rpc_call and dc_rpc_call_to are successful.
Length of timeLength of time between sending a request from the client to the server in a chained dc_rpc_call and dc_rpc_call_to, and receiving a response from the server between the start and end of a chained RPC. This value is acquired when a chained dc_rpc_call and dc_rpc_call_to is successful.
Execution of user serviceNumber of timesNumber of times service functions requested by dc_rpc_call and dc_rpc_call_to are executed. When the service retry facility is used to retry service functions, the number of times the service functions are retried is not included.
Length of timeLength of time between the start of the execution of service functions requested by dc_rpc_call and dc_rpc_call_to and the point at which the service functions issue return values. This value is obtained in dc_rpc_mainloop. When the service retry facility is used to retry service functions, the length of time required to retry the service functions is included.
RPC overtimesNumber of itemsNumber of timeout errors that are generated during the response wait processing of the RPC
SCD (schedule information)Schedule WaitsNumber of timesNumber of times service requests (dc_rpc_call) are issued by the client to the applicable user server
Queue lengthNumber of service requests remaining in the schedule queue of the applicable user server (SPP).
When this value is too large, increase the value specified in the parallel_count operand in the user service definition. When non-resident processes exist, decrease the value specified in the balance_count operand so that the non-resident processes can be easily started.
When this value is too small, if necessary, decrease the number of resident processes specified in the parallel_count operand in the user service definition. When non-resident processes exist, increase the value specified for the balance_count operand as necessary so that the non-resident processes are not easily started.
When the difference between the average and the maximum value is too great, adjust the ratio of the resident process count and the non-resident process count specified in the parallel_count operand and the maximum number of processes.
ScheduleNumber of timesNumber of times service requests (dc_rpc_call) are issued by the client to the applicable user server
Message lengthLength of the service request message received by the applicable user server (SPP). The message length includes the control information (512 bytes) added by the system.#2
Size of using bufferNumber of timesNumber of times service requests (dc_rpc_call) are issued by the client to the applicable user server
Buffer pool sizeSize of the buffer pool being used to store messages for the applicable user server (SPP). However, if a shared buffer pool is used, the size of the shared buffer pool is acquired.
Message size in case of lack of bufferNumber of timesOf the service requests (dc_rpc_call) that are issued by the client to the applicable user server, the number of service requests that cannot be scheduled due to the insufficient size of the buffer pool for storing messages
Message lengthOf the service requests to the applicable user server (SPP), the length of the service request message that cannot be scheduled due to the insufficient size of the buffer pool for storing messages
Schedule StayNumber of timesNumber of times service requests are fetched from the schedule queue
Length of timeLength of time between the storage in the schedule queue of service requests (dc_rpc_call) that are sent to the applicable user server and fetching of those service requests
Schedule Waits of serviceNumber of timesNumber of times clients have issued service requests (dc_rpc_call) to the applicable user server. This information is acquired only if the scdsvcdef definition command is specified in the user service definition.
Queue lengthNumber of service requests that have been in the schedule queue of the applicable user server (SPP). This information is acquired only if the scdsvcdef definition command is specified in the user service definition.
Size of using buffer of serviceNumber of timesNumber of times clients have issued service requests (dc_rpc_call) to the applicable user server. This information is acquired only if the scdsvcdef definition command is specified in the user service definition.
Buffer pool sizeSize of the buffer pool being used to store messages for the applicable user server (SPP). However, if a shared buffer pool is used, the size of the shared buffer pool is acquired. This information is acquired only if the scdsvcdef definition command is specified in the user service definition.
Parallel ServiceNumber of timesNumber of times service requests are fetched from the schedule queue. This information is acquired only if the scdsvcdef definition command is specified in the user service definition.
Number of servicesThe number of service requests that the applicable user server (SPP) is executing concurrently. This information is acquired only if the scdsvcdef definition command is specified in the user service definition.
TRN (transaction information)CommitsNumber of itemsNumber of transactions that are committed
RollbacksNumber of itemsNumber of transactions that are rolled back
Commit settlement by commandNumber of itemsNumber of transactions that are committed by commands
Rollback settlement by commandNumber of itemsNumber of transactions that are rolled back by commands
Hazard settlement by commandNumber of itemsNumber of transactions that are heuristically settled as hazards by commands
Mixed settlement by commandNumber of itemsNumber of transactions that are heuristically settled as mixed by commands
Branch execution timeNumber of timesNumber of times transaction branches are executed
Length of timeActual length of time between the start of services as transactions and the completion of synchronous point processing
Branch synchronous point processing timeNumber of timesNumber of times synchronous point processing is executed
Length of timeActual length of time required for synchronous point processing that is executed after the termination of services executed as transactions (this time is included in Branch execution time shown above)
RTS (real-time statistics)Arbitrary sectionNumber of timesNumber of times dc_rts_utrace_put is called
Length of timeLength of time between calling of dc_rts_utrace_put with the DCRTS_START flag and calling of dc_rts_utrace_put with the DCRTS_END flag. Statistics for Arbitrary section are not acquired as the statistics for the entire system.
DAM (DAM information)ReadNumber of timesNumber of times dc_dam_read is called. This information is acquired when dc_dam_read is successful.
Data lengthBuffer length specified in the argument of dc_dam_read.
Read errorsNumber of itemsNumber of times errors are detected in DAM cache blocks and the DAM blocks read from a disk and the number of read errors on a disk. Errors such as invalid API arguments are not included in this count.
WriteNumber of timesNumber of times dc_dam_write and dc_dam_rewrite are called. This information is acquired when dc_dam_write and dc_dam_rewrite are successful.
Data lengthBuffer length specified in the arguments of dc_dam_write and dc_dam_rewrite.
Write errorsNumber of itemsNumber of errors that occurred while the data in DAM cache blocks was written to a disk. Depending on the time when a transaction is committed, this information may not be acquired for each service. Errors such as invalid API arguments are not included in this count.
FJ output frequencyNumber of timesNumber of times recovery journals (FJ) are output. Depending on the time when a transaction is committed, this information may not be acquired for each service.
Journal sizeNumber of recovery journals (FJ). Depending on the time when a transaction is committed, this information may not be acquired for each service.
Number of DAM transaction branchesNumber of timesNumber of transaction branches related to the DAM
Number of transactionsNumber of transaction branches related to the DAM that are executed by the first DAM service function executed in the transaction. If the number of transaction branches related to the DAM is less than the value specified in the dam_tran_process_count operand in the DAM service definition, the system outputs the value specified in the dam_tran_process_count operand. The maximum value for this item is the maximum number of transaction branches related to the DAM that are simultaneously executed. When you specify this value in the dam_tran_process_count operand in the DAM service definition or use it in the formula for the dam_cache_size operand or the dam_cache_size_fix operand, the shared memory for the DAM cache is optimized.
DAM cache-block securing frequencyNumber of timesNumber of times DAM cache blocks are allocated
Common memory for DAM use rateNumber of timesNumber of transactions that updated the DAM file specified for deferred update divided by 10
Usage rate of shared memory poolUsage rate of the shared memory for the DAM cache. Note that this value is updated only within the transactions that update the DAM files specified for deferred update.
TAM (TAM information)Table file real renewalNumber of timesNumber of times data is updated in a TAM file. Timer-start, cpd, and the tamhold command are available as events for updating a TAM file. When multiple TAM files are updated for one update event, the count increases only by one.
Number of data bytesNumber of bytes in the data that is actually updated in a TAM file during online operation. This value includes all the data written for one update event. When multiple TAM files are updated, this value is the total number of bytes updated in those TAM files.
Table file real renewal timeNumber of timesNumber of times data is updated in a TAM file. Timer-start, cpd, and the tamhold command are available as events for updaing a TAM file. When multiple TAM files are updated for one update event, the count is increased only by one.
Length of timeProcessing time required for a TAM file update. This information indicates the length of time, in microseconds, required for one update event.
Number of tam record referencesNumber of timesNumber of commits and rollbacks related to the TAM
Number of recordsNumber of records that are referenced in one transaction. The number of records is counted, regardless of whether dc_tam_read is called, because this value is determined and output by the commit processing of the TAM server. Therefore, in a system that does not call dc_tam_read, only the number of records is counted, and the maximum value, minimum value, and average are all 0.
Number of tam record renewalNumber of timesNumber of commits and rollbacks related to the TAM
Number of recordsNumber of records updated in one transaction. The number of records is counted, regardless of whether dc_tam_write is called, because this value is determined and output by the commit processing of the TAM server. Therefore, in a system that does not call dc_tam_write, only the number of records is counted, and the maximum value, minimum value, and average are all 0.
ReadNumber of timesNumber of times dc_tam_read is called. This information is acquired when dc_tam_read is successful.#3
Data lengthLength of data input to a TAM file each time dc_tam_read is read.#3
Read errorsNumber of itemsNumber of errors that occurred in dc_tam_read in the interface with the OS. Errors such as invalid API arguments are not included in this count.#3
WriteNumber of timesNumber of times dc_tam_write and dc_tam_rewrite are called. This information is acquired when dc_tam_write and dc_tam_rewrite are successful.#4
Data lengthLength of data output from a TAM file each time dc_tam_write or dc_tam_rewrite is called#4
Write errorsNumber of itemsNumber of errors that occurred in dc_tam_write and dc_tam_rewrite in the interface with the OS. Errors such as invalid API arguments are not included in this count.#4
XAR (XA resource service information)Start() requestNumber of timesNumber of times transaction start requests are sent from an application server to the RAP-processing server
Length of timeLength of time from the start to the end of execution by the RAP-processing server of the transaction start requests sent from an application server
Start() request errorNumber of itemsNumber of errors that occurred in the transaction start requests sent from an application server to the RAP-processing server
Call() requestNumber of timesNumber of times service requests are sent from an application server to the RAP-processing server
Length of timeLength of time from the start to the end of execution by the RAP-processing server of the service requests sent from an application server
Call() request errorNumber of itemsNumber of errors that occurred in the service requests sent from an application server to the RAP-processing server
End() requestNumber of timesNumber of times transaction end requests are sent from an application server to the RAP-processing server
Length of timeLength of time from the start to the end of execution by the RAP-processing server of the transaction end requests sent from an application server
End() request errorNumber of itemsNumber of errors that occurred in the transaction end requests sent from an application server to the RAP-processing server
Prepare() requestNumber of timesNumber of times transaction preparation processing requests are sent from an application server to the RAP-processing server
Length of timeLength of time from the start to the end of execution by the RAP-processing server of the transaction preparation processing requests sent from an application server
Prepare() request errorNumber of itemsNumber of errors that occurred in the transaction preparation processing requests sent from an application server to the RAP-processing server
Commit() requestNumber of timesNumber of times transaction commit processing requests are sent from an application server to the RAP-processing server
Length of timeLength of time from the start to the end of the execution by the RAP-processing server of the transaction commit processing requests sent from an application server
Commit() request errorNumber of itemsNumber of errors that occurred in the transaction commit processing requests sent from an application server to the RAP-processing server
Rollback() requestNumber of timesNumber of times transaction rollback processing requests are sent from an application server to the RAP-processing server
Length of timeLength of time from the start to the end of execution by the RAP-processing server of the transaction rollback processing requests sent from an application server
Rollback() request errorNumber of itemsNumber of errors that occurred in the transaction rollback processing requests sent from an application server to the RAP-processing server
Recover() requestNumber of timesNumber of times transaction notification requests that have been prepared or heuristically determined are sent from an application server to the RAP-processing server
Length of timeLength of time from the start to the end of execution by the RAP-processing server of the transaction notification requests that have been prepared or heuristically determined and sent from an application server
Recover() request errorNumber of itemsNumber of errors that occurred in the transaction notification requests that have been prepared or heuristically determined and sent from an application server to the RAP-processing server
Forget() requestNumber of timesNumber of times transaction abort requests are sent from an application server to the RAP-processing server
Length of timeLength of time from the start to the end of execution by the RAP-processing server of the transaction abort requests sent from an application server
Forget() request errorNumber of itemsNumber of errors that occurred in the transaction abort requests sent from an application server to the RAP-processing server
MCF (MCF information)Schedule StayNumber of timesNumber of times the MHP retrieved messages from the input queue
Length of timeWait time until the MHP retrieves a message after it is placed in the input queue by the MCF communication process
Execution of user serviceNumber of timesNumber of times MHP executed services
Length of timeTime from the start of service function execution to issuance of return by the service function
#1
The name service stores information in the global cache area about the service group running on the nodes specified in the all_node operand in the system common definition, and stores information in the local cache area about the service group running on the local node. When a UAP or a command executes an RPC, the required information about the service group is searched for in the global cache area and the local cache area.
#2
For the message_buflen operand in the user service definition, Hitachi recommends that you set the value of the message size (maximum). For the message_store_buflen operand in the user service definition, Hitachi recommends that you specify a value within the following range:
Message length (average) x schedule wait queue length (maximum) <= message_store_buflen <= message length (maximum) x schedule wait queue length (maximum)
#3
Includes dc_dam_read that accesses TAM tables.
#4
Includes dc_dam_write and dc_dam_rewrite that access TAM tables.

The following table shows the relationship between process termination and the applicable item counts in the real-time statistics.

Table E-7 Process termination and applicable item counts

Process and terminationApplicable item count
When a UAP process terminates with a CPU time monitoring timeout errorUAP abnormal terminations
When OpenTP1-provided servers operating as SPPs (TP1/EE, RAP-processing server, RTSSUP, RTSSPP) go down
When a UAP process goes down
When the system server goes down but the system does not go down (trnrvd (transaction recovery service) and clttrnd (client-executed process))System server abnormal terminations
When a UAP process terminates normallyProcess terminations
When a UAP process is forcibly terminated by using the dcsvstop command with the -f option specified or the prckill command
When a UAP process terminates due to an actual time-monitoring timeout error

The following table shows the real-time statistics information that is edited.

Table E-8 Edited real-time statistics information

Type (type of real-time statistics)Edited informationItem ID
(Event ID)
Operand nameAcquisition target
Event (real-time statistics item name)Unit (acquired information)Value to be outputSVCSRVSYS
TtlMax, Min, Avg
CPD (checkpoint dump information)Collection of cpdevents (number of items)YesNo1000rts_cpd_collct_cpdNNY
microsec (length of time in microseconds)NoYes
Validation of cpdevents (number of items)YesNo1001rts_cpd_validt_cpdNNY
microsec (length of time in microseconds)NoYes
JNL (journal information)Buffer full occurrencesevents (number of items)YesNo1100rts_jnl_buf_fullNNY
Waits for an available bufferevents (number of items)YesNo1101rts_jnl_wait_bufNNY
Journal outputtimes (number of times)YesNo1102rts_jnl_jnl_outputNNY
bytes (data length in bytes)NoYes
I/O waitstimes (number of times)YesNo1103rts_jnl_io_waitNNY
surfaces (number of buffers x 100)NoYes
Writetimes (number of times)YesNo1104rts_jnl_writeNNY
microsec (length of time in microseconds)NoYesNNY
Swaptimes (number of times)YesNo1105rts_jnl_swapNNY
microsec (length of time in microseconds)NoYes
Journal inputtimes (number of times)YesNo1106rts_jnl_jnl_inputNNY
bytes (data length in bytes)NoYes
Readtimes (number of times)YesNo1107rts_jnl_readNNY
microsec (length of time in microseconds)NoYesNNY
LCK (lock information)Lock acquisitionevents (number of items)YesNo1200rts_lck_lock_acqstYYY
microsec (length of time in microseconds)NoYes
Lock waitevents (number of items)YesNo1201rts_lck_lock_waitYYY
events (queue length)NoYes
Deadlockevents (number of items)YesNo1202rts_lck_deadlockYYY
NAM (name information)Global Cache hitstimes (number of times)YesNo1300rts_nam_global_cache_hitYYY
Local Cache hitstimes (number of times)YesNo1301rts_nam_local_cache_hitYYY
Lookupevents (number of times)YesNo1302rts_nam_lookupYYY
OSL (shared memory management information)Common static memory (acquired)times (number of times)YesNo1400rts_osl_stamem_acqNNY
bytes (memory block size in bytes)NoYes
Common static memory (pool)times (number of times)YesNo1401rts_osl_stamem_polNNY
bytes (memory block size in bytes)NoYes
Common dynamic memory (acquired)times (number of times)YesNo1402rts_osl_dynmem_acqNNY
bytes (memory block size in bytes)NoYes
Common dynamic memory (pool)times (number of times)YesNo1403rts_osl_dynmem_polNNY
bytes (memory block size in bytes)NoYes
PRC (process information)Process generationtimes (number of times)YesNo1500rts_prc_prc_genertNYY
UAP abnormal terminationstimes (number of times)YesNo1501rts_prc_uap_abnmlNYY
System server abnormal terminationstimes (number of times)YesNo1502rts_prc_sys_abnmlNNY
Process terminationstimes (number of times)YesNo1503rts_prc_prc_termNYY
Number of processestimes (number of times)YesNo1504rts_prc_prc_numNNY
Process (number of processes)NoYes
QUE (message queue information)Read messagetimes (number of times)YesNo1601rts_que_readNYY
bytes (message length in bytes)NoYes
Write messagetimes (number of times)YesNo1602rts_que_writeNYY
bytes (message length in bytes)NoYes
Read errorsevents (number of items)YesNo1603rts_que_read_errNYY
Write errorsevents (number of items)YesNo1604rts_que_write_errNYY
Waits for an available bufferevents (number of items)YesNo1605rts_que_wait_bufNYY
Real readstimes (number of times)YesNo1606rts_que_real_readNYY
Real writestimes (number of times)YesNo1607rts_que_real_writeNYY
Number of delay writingstimes (number of times)YesNo1650rts_que_delay_wrtNNY
times (number of times)NoYes
Number of delay writing recordstimes (number of times)YesNo1651rts_que_delay_recNNY
records (number of records)NoYes
Delay writing record ratetimes (number of times)YesNo1652rts_que_delay_msgNNY
% (percentage of messages)NoYes
RPC (RPC information)RPC callstimes (number of times)YesNo1700rts_rpc_rpc_callYYY
microsec (length of time in microseconds)NoYes
RPC calls(chained)times (number of times)YesNo1701rts_rpc_rpc_call_chainedYYY
microsec (length of time in microseconds)NoYes
Execution of user servicetimes (number of times)YesNo1730rts_rpc_usr_srvcYYY
microsec (length of time in microseconds)NoYes
RPC overtimesevents (number of items)YesNo1731rts_rpc_rpc_ovrtimYYY
SCD (schedule information)Schedule Waitstimes (number of times)YesNo1800rts_scd_scd_waitY#YY
events (queue length)NoYes
Scheduletimes (number of times)YesNo1801rts_scd_scheduleYYY
bytes (message length in bytes)NoYes
Size of using buffertimes (number of times)YesNo1802rts_scd_using_bufY#YY
bytes (buffer pool size in bytes)NoYes
Message size in case of lack of buffertimes (number of times)YesNo1803rts_scd_lack_bufYYY
bytes (message length in bytes)NoYes
Schedule Staytimes (number of times)YesNo1804rts_scd_scd_stayYYY
microsec (length of time in microseconds)NoYes
Schedule Waits of servicetimes (number of times)YesNo1805rts_scd_svc_scd_waitYYY
events (queue length)NoYes
Size of using buffer of servicetimes (number of times)YesNo1806rts_scd_svc_using_bufYYY
bytes (buffer pool size in bytes)NoYes
Parallel Servicetimes (number of times)YesNo1807rts_scd_parallelYYY
counts (number of services)NoYes
TRN (transaction information)Commitsevents (number of items)YesNo1900rts_trn_commitYYY
Rollbacksevents (number of items)YesNo1901rts_trn_rollbackYYY
Commit settlement by commandevents (number of items)YesNo1902rts_trn_cmt_cmdNNY
Rollback settlement by commandevents (number of items)YesNo1903rts_trn_rbk_cmdNNY
Hazard settlement by commandevents (number of items)YesNo1904rts_trn_haz_cmdNNY
Mixed settlement by commandevents (number of items)YesNo1905rts_trn_mix_cmdNNY
Branch execution timetimes (number of times)YesNo1906rts_trn_branchYYY
microsec (length of time in microseconds)NoYes
Branch synchronous point processing timetimes (number of times)YesNo1907rts_trn_sync_pointYYY
microsec (length of time in microseconds)NoYes
RTS (real-time statistics)Arbitrary sectiontimes (number of times)YesNo1000000​-2147483647​-YYN
microsec (length of time in microseconds)NoYes
DAM (DAM information)Readtimes (number of times)YesNo2000rts_dam_readYYY
bytes (data length in bytes)NoYes
Read errorsevents (number of items)YesNo2001rts_dam_read_errYYY
Writetimes (number of times)YesNo2002rts_dam_writeYYY
bytes (data length in bytes)NoYes
Write errorsevents (number of items)YesNo2003rts_dam_write_errYYY
FJ output frequencytimes (number of times)YesNo2004rts_dam_fjYYY
bytes (journal size in bytes)NoYes
Number of DAM transaction branchestimes (number of times)YesNo2005rts_dam_trn_branchYYY
transaction (number of transactions)NoYes
DAM cache-block securing frequencytimes (number of times)YesNo2006rts_dam_cache_blockYYY
Common memory for DAM use ratetimes (number of times)YesNo2007rts_dam_shm_poolNNY
% (percentage of shared memory pool used)NoYes
TAM (TAM information)Table file real renewaltimes (number of times)YesNo2100rts_tam_real_renewNNY
bytes (number of data bytes)NoYes
Table file real renewal timetimes (number of times)YesNo2101rts_tam_real_renew_timeNNY
microsec (length of time in microseconds)NoYes
Number of tam record referencestimes (number of times)YesNo2102rts_tam_rec_referNYY
records (number of records)NoYes
Number of tam record renewaltimes (number of times)YesNo2103rts_tam_rec_renewNYY
records (number of records)NoYes
Readtimes (number of times)YesNo2104rts_tam_readYYY
bytes (data length in bytes)NoYes
Read errorsevents (number of items)YesNo2105rts_tam_read_errYYY
Writetimes (number of times)YesNo2106rts_tam_writeYYY
bytes (data length in bytes)NoYes
Write errorsevents (number of items)YesNo2107rts_tam_write_errYYY
XAR (XA resource service information)Start() requesttimes (number of times)YesNo2500rts_xar_startNYY
microsec (length of time in microseconds)NoYes
Start() request errorevents (number of items)YesNo2501rts_xar_start_errNYY
Call() requesttimes (number of times)YesNo2502rts_xar_callNYY
microsec (length of time in microseconds)NoYes
Call() request errorevents (number of items)YesNo2503rts_xar_call_errNYY
End() requesttimes (number of times)YesNo2504rts_xar_endNYY
microsec (length of time in microseconds)NoYes
End() request errorevents (number of items)YesNo2505rts_xar_end_errNYY
Prepare() requesttimes (number of times)YesNo2506rts_xar_prepareNYY
microsec (length of time in microseconds)NoYes
Prepare() request errorevents (number of items)YesNo2507rts_xar_prepare_errNYY
Commit() requesttimes (number of times)YesNo2508rts_xar_commitNYY
microsec (length of time in microseconds)NoYes
Commit() request errorevents (number of items)YesNo2509rts_xar_commit_errNYY
Rollback() requesttimes (number of times)YesNo2510rts_xar_rollbackNYY
microsec (length of time in microseconds)NoYes
Rollback() request errorevents (number of items)YesNo2511rts_xar_rollback_errNYY
Recover() requesttimes (number of times)YesNo2512rts_xar_recoverNYY
microsec (length of time in microseconds)NoYes
Recover() request errorevents (number of items)YesNo2513rts_xar_recover_errNYY
Forget() requesttimes (number of times)YesNo2514rts_xar_forgetNYY
microsec (length of time in microseconds)NoYes
Forget() request errorevents (number of items)YesNo2515rts_xar_forget_errNYY
MCF (MCF information)Schedule Staytimes (number of times)YesNo2300rts_mcf_ap_scd_stayYYY
microsec (length of time in microseconds)NoYes
Execution of user servicetimes (number of times)YesNo2301rts_mcf_ap_usr_srvcYYY
microsec (length of time in microseconds)NoYes
Legend:
Ttl: Total
Max: Maximum
Min: Minimum
Avg: Average
SVC: Acquired for each service.
SRV: Acquired for each server.
SYS: Acquired for the entire system.
Yes or Y: Applicable.
No or N: Not applicable.
#
For information acquired on a service basis, only times (number of times) is valid.

(2) Details about real-time statistics (when a target is specified)

The following table shows the details about real-time statistics when a target is specified.

Table E-9 Details about real-time statistics (when a target is specified)

Type (type of real-time statistics)Edited informationDetails
Event (real-time statistics item name)Acquired information
NAM (name information)Lookup to specified nodeNumber of itemsNumber of times search requests for service information are sent from each node to the specified reference node
When a UAP or a command executes an RPC, they may send search requests for service information to the node specified in the all_node operand in the system common definition to find the required information about the service group.
Response of Lookup from specified nodeNumber of itemsNumber of times each node receives the responses to the search requests for service information from the specified reference node. When a UAP or a command executes an RPC, they may send search requests for service information to the node specified in the all_node operand in the system common definition to find the required information about the service group.
MCF (MCF information)Residence time on input message#1Number of timesNumber of times the MHP retrieved messages from the input queue
TimeWait time until the MHP retrieves a message after it is placed in the input queue by the MCF communication process.
Residence time on output message of synchronous#1Number of timesNumber of times the MCF communication process processed synchronous send messages.
TimeLength of time until processing is performed by the MCF communication process after the UAP requests transmission of a synchronous send message.
Residence time on output message of response#1Number of timesNumber of times the MCF communication process processed inquiry response send messages.
TimeLength of time until processing is performed by the MCF communication process after a transaction is determined to have been committed following a UAP request for transmission of an inquiry response send message.
Residence time on output message of priority#1Number of timesNumber of times the MCF communication process processed priority branch send messages.
TimeLength of time until processing is performed by the MCF communication process after a transaction is determined to have been committed following a UAP request for transmission of a priority branch send message.
Residence time on output message of normal#1Number of timesNumber of times the MCF communication process processed normal branch send messages.
TimeLength of time until processing is performed by the MCF communication process after a transaction is determined to have been committed following a UAP request for transmission of a priority branch send message.
Number on input message queue#2Number of timesNumber of times the MCF communication process placed messages in the input queue, and the number of times MHP retrieved messages from the input queue
Number of itemsNumber of messages held in the input queue. If this value is large, increase the parallel_count operand value in the user service definition.
#1
Information acquired for each logical terminal.
#2
Information acquired for each service group.

The following table shows the format for specifying a target for acquiring real-time statistics.

Table E-10 Format for specifying a target for acquiring real-time statistics

Type (type of real-time statistics)Event (real-time statistics item name)Format for specifying target
Acquisition target name 1#1Acquisition target name 2#2
NAM (name information)Lookup to specified nodePort number#3IP address#3
Response of Lookup from specified node
MCF (MCF information)Residence time on input messageLogical terminalNone
Residence time on output message of synchronous
Residence time on output message of response
Residence time on output message of priority
Residence time on output message of normal
Number on input message queueNoneService group name
#1
When acquiring statistics:
Specify this in the -o option in the rtsput definition command with obj specified for the -u option or the rtsstats command.
When displaying or editing statistics:
Specify this in the -s option in the rtsls command with svc specified for the -u option or the rtsedit command.
#2
When acquiring statistics:
Specify this in the -b option in the rtsput definition command with obj specified for the -u option or the rtsstats command.
When displaying or editing statistics:
Specify this in the -v option in the rtsls command with svc specified for the -u option or the rtsedit command.
#3
Specify the IP address and port number of the node specified in the all_node operand in the system common definition or specified in the domain definition file.

The following table shows the information produced from real-time statistics when a target is specified.

Table E-11 Edited real-time statistics information (when a target is specified)

Type (type of real-time statistics)Edited informationItem ID
(Event ID)
Operand nameAcquisition unit#
Event (real-time statistics item name)Units (acquired information)Value to be outputSVCSRVSYS
TtlMax, Min, Avg
NAM (name information)Lookup to specified nodeevents (number of items)YesNo1303rts_nam_node_lookupNNN
Response of Lookup from specified nodeevents (number of items)YesNo1304rts_nam_node_lookup_responceNNN
MCF (MCF information)Residence time on input messagetimes (number of times)YesNo2350rts_mcf_in_msg_scd_waitNNN
microsec (length of time in microseconds)NoYes
Residence time on output message of synchronoustimes (number of times)YesNo2351rts_mcf_out_msg_sync_scd_waitNNN
microsec (length of time in microseconds)NoYes
Residence time on output message of responsetimes (number of times)YesNo2352rts_mcf_out_msg_resp_scd_waitNNN
microsec (length of time in microseconds)NoYes
Residence time on output message of prioritytimes (number of times)YesNo2353rts_mcf_out_msg_prio_scd_waitNNN
microsec (length of time in microseconds)NoYes
Residence time on output message of normaltimes (number of times)YesNo2354rts_mcf_out_msg_norm_scd_waitNNN
microsec (length of time in microseconds)NoYes
Number on input message queuetimes (number of times)YesNo2380rts_mcf_que_scd_wait_numNNN
num (count)NoYes
Legend:
Ttl: Total
Max: Maximum
Min: Minimum
Avg: Average
SVC: Acquired for each service.
SRV: Acquired for each server.
SYS: Acquired for the entire system.
Yes or Y: Applicable.
No or N: Not applicable.
#
When you specify a desired object as the target, real-time statistics are acquired from the object specified in acquisition target names 1 and 2.