CA View can create a multi level index of pages within a SYSOUT or report. For example, you can specify a field that appears on every page of a report and this could be the number or name of a division in your organization. This page indexing information becomes a part of the logical view definition. When you archive copies of this SYSOUT or report, CA View examines each page for these indexing criteria, and creates an additional selection list, showing each value that has appeared in this indexing field. You then have the option of selecting the entire report or SYSOUT for viewing, or selecting only the pages that contain any one of the given index fields.
To avoid overloading the system with individual user indexes, private logical views can only be used to create new page indexes if they match a public or global view index definition.
This section provides an overview of the panels used to specify the indexing criteria, and the panels through which you select SYSOUTs or reports that have page indexing as part of their view definitions.
Page indexing criteria for private views are not examined during the archival process. Page indexes are built using all view numbers for public and global view definitions only. Therefore, if you are defining page indexing criteria for a private view, it must match page indexing criteria for a public or global view. For example, if public view 1 exists for a given report ID, no global view 1s are used. If public view 1 does not exist, only the most specific global view 1 is used for building the page index for view number 1. This applies for all view numbers.
|
Copyright © 2013 CA.
All rights reserved.
|
|