Index Design

Control-V enables users to retrieve parts of reports based on any predefined index path. Define separate index paths for each meaningful way to retrieve a report page or section. It is recommended that each index name be unique. When possible, use page-level, rather than record-level, indexing. For example:

The following index paths may be specified for a life insurance policy file:

• Path 1 for computing reserves and cash values:
  1_pol_type, 1_policy_#, 1_face_amount, 1_riders, 1_rating, 1_issue_age, 1_issue_date
• Path 2 for premium billing:
  2_payment_mode, 2_state/country, 2_zipcode, 2_city, 2_bill_address, 2_pol_owner, 2_pol_#, 2_annual_prem
• Path 3 for commission payments
  3_payment_mode, 3_branch_ofc, 3_agent, 3_pol_type, 3_pol_#, 3_issue_date, 3_annual_prem, 3_comm_scale

In path 1 (above), 1_pol_type is a page-level index if only one policy type can occur on a page. Likewise, in paths 2 and 3, payment_mode is a page-level index if only one type of payment mode can occur on a page.

Index names should be as descriptive as possible. Use "acct-name" or "account#" rather than "account," use "part-num" or "part-name" rather than "part," and so on. Parameter MASK must be used to qualify a record-level index value. Whenever possible, also use parameter MASK to qualify a page-level index value. Mask values and index values must be on the same page of the report.

Index design requires an intimate knowledge of report layout and usage. When possible, the programmer responsible for maintaining the report program and a user who knows how the report is used should collaborate in designing indexes for the report.