|Working in a Group||Send Us Comments|
In this session, you take a look at the Investigator tool and how to incorporate it into your system analysis.
Please see the Tutorials Map to check that you have run all necessary previous sessions.
Effective system analysis requires knowledge of the system and an organized plan to implement modifications. The Investigator tool enables you to load project components of varied types into one interface for extended analysis and organization.
This session uses the project you created in the chapter Finding Points of Interest.
While working in Revolve's tools and browsers you can add items to the Investigator using the Revolve clipboard. For example:
Variables in your project that match the name selection criterion are displayed.
The folder expands to display the variables that were copied from the Variables browser. In the Investigator you can remove elements from the display without removing them from the tool. Let's assume that the variables CAT-END-VALUE, and CAT-START-VALUE are unneeded variables in this analysis. However, you're not sure that you want to remove them entirely from the Investigator. In this case, you can place these variables on the Filtered list.
Figure 10-1: Selecting unneeded variables in the Investigator
This excludes the variables from the displayed list. They are placed on the filtered list. You cannot see this immediately because the window has not been refreshed.
This toggles to the Filtered list. It displays all items that match filters specified in the Selection Criteria dialog or are directly excluded by the user.
The E flag indicates that you excluded these elements. User-specified filters like this are also displayed on the User tab when you click Options....
Items can be added to the Investigator in two ways. This functionality provides flexibility in the system analysis environment. In this section, you add items directly to the Investigator using the Selection Criteria dialog box.
To add items directly to the Investigator, you can set up Selection Criteria:
The Investigator tool and the Selection Criteria dialog are displayed.
The name-matching pattern *VALUE searches the project for all variables that include VALUE at the end of their names.
*VALUE is added to the list.
When this check box is checked, it indicates that all naming filters defined in the Name Filters dialog are applied to the Pattern Selection criteria.
The Name Filters dialog opens. Name patterns specified here are not included in the Investigator's results.
This means that variables matching the *VALUE pattern but containing CAT at the beginning of their names will not be listed by the Investigator.
The Investigator searches the project for matching variables.
The matching results are displayed. These items all correspond the name criteria *VALUE. Depending on the Display Format that is selected in the Utilities > Options... > User tab, detail may be abbreviated or extensive.
These are the variables in the project that matched the filter criteria CAT*. The N flag indicates they are filtered because of their names.
You can save selection criteria in a file so that you can reuse the same criteria later in your analysis. To do this:
The Selection Criteria for the *VALUE variables are displayed. Let's add some more criteria.
The Data File tab, like the Variable tab, adds items that correspond to the Pattern Selections and Filters. In this case, the items are references to external files.
The name pattern is displayed in the list.
The elements that match the criteria are loaded into the Investigator.
The filenames that matched the name patterns are displayed.
The Save Data Selection Criteria dialog is invoked. It enables you to save the existing criteria to a .sel file for use in other tasks and analysis.
The Selection Criteria specifications have been saved.
The results are displayed just as they were before.
In addition to loading and examining files, you can modify PIC clauses with the Investigator. To do this:
This tab enables you to define PIC translations that you apply to your project variables. In our project, there are some monetary data items defined as PIC 9(7)V99 that we're going to translate to PIC 9(9)V99.
The translation is listed in the translation list.
Figure 10-2: PIC Translations
Notice the PIC clauses are displayed for the various variables that match the name patterns and filters in sample.sel. To apply the PIC translations to these variables we'll use the Modification Driver.
The Modification Driver dialog box opens, referencing the first selected item. Use this dialog box to specify which code modifications you want to implement. The modification driver can insert blocks of text, tags, and other user-defined information into the source code of selected elements. In this case we want to implement the PIC translation for 9(7)V99 PIC clauses.
The first selected variable in the Investigator might not have a PIC clause. This is indicated if the PIC Translation check box is disabled (grayed). If this is the case, click Skip until the first variable with a PIC clause is encountered and the check box is enabled.
Figure 10-3: Modification Driver
This specifies that the Modification Driver's function is to perform the PIC translations defined in the Investigator's PIC Translations tab.
The PIC Translation tab is displayed listing defined translations.
The Modification Driver translates 9(7)V99 PIC clauses to 9(9)V99 in selected variables. When it encounters a PIC clause that is not 9(7)V99, it displays the PIC Translations tab for you to add further trnaslations if you want to. Notice the name of the variable is displayed along the top of the tab.
The non 9(7)V99 clauses are preserved while all 9(7)V99 clauses have been automatically translated.
Figure 10-4: Example of PIC Translation
The source code has been modified to include the new PIC translation. Changes must be saved and the project must be parsed for these modifications to take effect on the project. However, only the Administrator of a shared project can update the project by parsing and remaking it.
To update the project to incorporate the changes:
Revolve checks time stamps on COBOL files to see which files have been modified. ONLINE1.CBL contained the changed PIC clauses. It displays a status of Out of Date.
The project is parsed to incorporate all recent changes.
The files have a status of Loaded. The PIC translations have been successfully implemented.
In this session you:
This session completes the Revolve Enterprise Edition tutorials. For further information, please read the Revolve Enterprise Edition User's Guide, or see the online help system.
Comments on the books?
Click Send Us Comments.
Copyright © 2000 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.
|Working in a Group||Send Us Comments|