A description of the fields in the Program Termination Statistics report follows:
Identifies the name of the program to which the information applies and the node name on which it executed. Transactions that terminate abnormally are flagged as ABORT.
Note: For non-SQL transactions, the subschema control supplies the name of the program. If the program name is blank, then the program issued a BIND RUN UNIT before moving its name to the name field in the subschema control.
For SQL transactions, the RCM for the program initiating the transaction supplies the name of the program.
Specifies the unique identifier (LID) assigned to each transaction.
Indicates the number of locks acquired by the transaction.
Indicates the number of shared locks held by the transaction at the time the transaction ended.
Indicates the number of exclusive locks held by the transaction at the time the transaction ended.
Indicates the number of CALC records stored/not stored on their target page.
Interpretation: The ratio of CALC records stored on target to the total number stored (that is, hits plus overflows) is the CALC cluster ratio. The ratio reflects the efficiency of the CALC algorithm. Ideally, the value should be 1, which indicates no overflow. Values less than 1 or less than the norm indicate space utilization is getting high and database tuning should be performed.
Identifies the number of VIA and/or DIRECT records stored/not stored on their target page.
Interpretation: The ratio of VIA records stored on target to the total number stored (that is, hits plus overflows) is the VIA cluster ratio. The ratio reflects how well VIA records cluster around their owner. Ideally, the value should be 1, which indicates no overflow. Values less than 1 or less than the norm indicate very large data clusters, high utilization of space, or small page size.
Indicates the number of database records requested by IDMSDBMS.
Indicates the number of times the current-of-transaction field in the subschema control block for the transaction was updated.
Interpretation: The ratio of records requested to records current-of-transaction is the effectiveness ratio. The ratio measures the amount of work CA IDMS/DB is doing for the programmer (that is, how many records the DBMS has to examine to find the one requested). The information in JREPORT 002 indicates whether the ratio is constant for all executions of the program or only for certain transactions.
The value should be as low as possible. If the value is high, examine set options (for example, sorted order) for appropriateness. If the options are correct, examine the program logic for accurate use of currency.
Indicates the number of calls to IDMSDBMS issued by the transaction. Execution of each navigational DML request involves one call; execution of each LRF and SQL request typically involves multiple calls.
Indicates the number of noncontiguous segments (fragments) stored for variable-length records.
Interpretation: If the number of stored fragments is large or increasing, increase the page size to accommodate larger records. The condition of the databases and areas involved with the program should be analyzed further with the Database Analysis Utility (IDMSDBAN), described in Other CA IDMS Reporting Facilities.
Indicates the number of records relocated from their home page.
|
Copyright © 2013 CA.
All rights reserved.
|
|