User Modes: Initiating Output Retrieval › Cross-Report Indexing › Selecting by Index or Report

Selecting by Index or Report

You might have thousands of reports on your system, and tens of thousands of logical views and page indexes. Cross-report indexing offers great flexibility in report selection.

• A simple request might specify SELECT BY REPORT and include a SYSOUT ID. The appropriate SYSOUTs are displayed in a selection list.
• A more complex request could display every SYSOUT that has a page index called ZIPCODE, where the value 91356 was found.

  Depending on the size of your database, this kind of request could require the product to perform hundreds of thousands of cross reference checks.

Note: To maximize performance, always specify as much information as possible about SYSOUT ID and date (or generation).

To maximize the efficiency of the online system, your administrator has two ways to limit the number of page indexes that participate in cross-report indexing:

• With each logical view definition created, specify whether the page indexes for this view are to participate in cross-report indexing.

  The page index must reside on the primary disk database to participate in cross-report indexing. For information on defining logical views, page indexes, and sub-indexes, see the chapter "Creating Logical Views."

• Limit the amount of time the page index of a report stays on the CA View disk database.

  Do this with the ERO table statement IRETPD (index retention period).

  Note: For more information about defining the length of time a report and its page index stay on primary disk, see the chapter "Expanded Retention Option" in the Reference Guide.

You can also load only a report's page indexes to disk (SEL command LI or LX), or delete only its page indexes from disk (SEL command DI).