Clustering ratio

Indicates the ratio of the number of records requested to the number of pages requested; ratios less than 4 indicate poor database design or space availability problems

• Redesign the database using clustering more effectively
• Increase the area's page size or page range andunload and reload the database
• Reassign files to buffers

Page space availability

Indicates how full database pages are

• Increase the database page size
• Increase the number of pages

Fragments stored

Indicates the number of fragments stored for a variable-length record.

• Increase the page size and read each record in an update mode
• Increase the page reserve size
• Change fragmentation specifications

Records relocated

Indicates the number of expanded records moved to a new page due to lack of space

• Unload/reload the database
• Increase the page size and read each record in an update mode

CALC cluster ratio

Indicates the ratio of CALC records stored on the target page to the total number (that is, hits plus overflow) stored; values less than 1 indicate space availability problems

Increase the area's page size or number of pages and unload and reload the database

VIA cluster ratio

Indicates the ratio of VIA (or clustered) records stored on the target page to the total number (that is, hits plus overflow) stored; values less than 1 indicate large clusters, space availability problems, or small page size

Increase the area's page size or number of pages and unload and reload the database

Effectiveness ratio

Indicates the ratio of number of records CA IDMS/DB requests to the number that are current-of-run-unit. Values much higher than 1 indicate poor program logic or set options

Review application/database design. Consider use of PRIOR or OWNER pointers and possible elimination of some sorted sets. (Note that linked constraints in SQL-defined databases always include PRIOR and OWNER pointers.)

Logically deleted records

Indicates the number of logically deleted records

Physically delete the logically deleted records using the CLEANUP utility statement