Editing Layout Definitions
Overview
The Layout Manager enables you to create or customize layouts for query result views. Each display layout can be used for these purposes:
- As the default view for queries. For more information about the default views that are specified in query definitions, see the topic Editing Query Definitions.
- For generating a new view for any type of graphic or XRef representation of query results.
- When exporting a cross-reference table to a CSV file, a custom layout enables you to specify the information to export (for example, object attributes or links between objects).
Defining the layout consists of choosing a display type (layout template) and specifying parameters to adjust result views to meet you specific needs.
This table lists all the available layout types:
Layout Type | Description |
---|---|
Specific to objects resulting from parsing based on the ADU model. Especially suited for the standard query JCL Flowchart Graph. |
|
Specific to objects resulting from parsing based on the ADU model. Especially suited for the standard query Program Flowchart Graph. |
|
All References Layout |
Defines the display layout for the All References function. This layout is only available when using the All References function.
|
Displays a mono- or multi-column histogram of numeric data or object counts retrieved from the repository by an appropriate query. |
|
Displays downward dependencies dynamically. Better suited for displaying the dependencies of a given object rather than the results of a query. When using this layout as the default view for queries, you retain the capability of exploring objects through any link, regardless of query definitions and results.
|
|
Displays a numeric value of an APM (for example, metrics value) in a dial chart. |
|
Displays, in a time table, the repository objects that have start, end, and duration attributes. |
|
Displays historical data either in a table or a chart. This layout is available only contextually to a single object of the type that has been defined as the impacted object type for the Snapshot feature. For more information about the Snapshot feature, see the topic Snapshots.
|
|
Displays graphically the hierarchical structure between objects, with horizontal links. |
|
Displays the result of a data lineage in a graph. |
|
Displays all the objects that result from a query in a flat list. When these objects are of various types, they are grouped by object class. |
|
Displays a graph type representation of query results. You can show/hide links and objects in the results graphic model. |
|
Displays a pie chart of query results. |
|
Displays a radar chart for comparing objects on the basis of multiple criteria. |
|
Displays an XY scatter plot layout of query results. |
|
Displays the MAP screen that is defined in the source file. |
|
Enables you to retrieve source code lines in addition to the source location of an object. The contents are displayed in a spreadsheet. |
|
Displays a spreadsheet-style report. The Tabular Layout Type is notably used to design an impact analysis report. For more information about the Impact Analysis feature, see the topic Reports and Files.
|
|
Represents the hierarchical structure between objects in a tree diagram. The initial view displays only the root objects from which users can easily expand the tree structure. This is the default layout. |
|
Displays a UML Class diagram by dynamically retrieving all required information and the dependencies. |
|
Displays graphically the hierarchical structure between objects, with vertical links. |
|
Displays objects and links in a table of cross-references. |
For examples of the use of layouts, see the topic Examples of Layout Types.