| Start Here for the Tutorials! | Assigning Scope with Subprojects | |
Revolve project's consist of defined source code components that you specify in your system. Once it is created, your project becomes the basis for your system analysis.
This is the first session of the tutorials in the Getting Started book. You need to work through this before you do any of the others. You need to have read the chapter Start Here for the Tutorials! before doing this one.
In the following sessions we assume that you are familiar with COBOL and other mainframe equivalents but we assume that you have never seen Revolve or any other Micro Focus software before, and that you have only a basic everyday knowledge of using Windows '95 or Windows NT V4.0 (these two operating systems are almost identical to use). While touring Revolve remember that window size and location will vary between machines and screen representations are only included for reference.
Revolve integrates the tools you need to compile system files into one entity for editing your source code and assessing your system maintenance needs. The easiest way to understand Revolve's features and apply them to your code is to perform the tasks that have been prepared for you here.
This session walks you through creating and loading a sample CICS application. It has a related batch stream, consisting of several reporting programs that are invoked by a JCL job stream.
Projects are the basis for Revolve's analysis. A project is comprised of multiple source code files or components that you load into Revolve. These files are parsed into multiple database files and a project file with a .prj extension. Once a project containing your source files is created, you are ready to start your system analysis.
It is required that you use system components to build a Revolve project. The Add Components feature enables you to navigate your system and identify the files to be included in the project.
In addition to specifying components to be added to the project, Add Components also enables you to use the the Automatic Component Locator or ACL and Search Directories to locate and load files that are referenced by project files. As described in this tutorial, the ACL steers Revolve to the search directories that contain referenced files, so that pertinent files are loaded automatically. This is useful because you don't have to go through and load individual files.
The Project Manager is a project specific interface, in that its perspective is the project itself and the files that comprise it. It is the interface used in performing administrative tasks like adding and deleting components, setting component level parameters, and maintaining the status of project files.
Once a project has been defined and all the components have been loaded, Revolve can provide information about the application. Revolve can only provide information about the source code that is loaded in the project. Sometimes projects are defined that require additional information to completely resolve all relationships defined in an application. For example, some of the copybooks may not have been included in the project, or some of the file accesses may be dependent on dynamic definitions stored in relational data tables. The Complete Project interface enables you to view all of the unresolved areas of your project and add additional information needed to resolve errant associations.
If the project sample.prj has already been created by another user, open it in Revolve and click the Project menu and select Delete. Check Delete out related database files and click Yes. This deletes all database files that were created when the project was created .
This tutorial walks you through creating the sample.prj. Once it is created, you will apply Revolve's scripting and Complete Project features to it to resolve a copybook association problem. Then you will create a subproject and apply the Metrics tool to it to measure its complexity.
The sample project you create here will be used in the Revolve tutorials that follow.
In this session you:
If you've entered Revolve by clicking the Run button at the end of
installation, the main screen of the installation utility may still be visible-
the one with the Install, Installation Notes, and Exit
buttons - though it may be hidden behind the Revolve desktop or main screen.
You can close it by clicking its 
button, now or at any time - it won't interfere with this session.
If not, then start Revolve as follows (this is how you will start Revolve in the future):
You may see a dialog box entitled Micro Focus Protection System, warning you that your license expires in a few days. In these sessions we will ignore this warning, but later you should load Revolve again and click Help on this screen for details of how to get a full license.
If you already have a full license, you see a screen telling you what options you have installed. This disappears after a few seconds and is replaced by the Revolve desktop. It is shown in Figure 5-1
Figure 5-1: Revolve Desktop
This is where all project windows, tools, views, browsers, and editing windows will be opened. You can change the size and shape of Revolve and it's windows by dragging the edges and corners.
To create a project:
All database files related to the project will be stored in this directory. It is a good practice to create a subdirectory for each new Revolve project.
If you are running Revolve on a network, create your project in a local directory to prevent sharing conflicts among users. For example, c:\projects\sample\sample.prj.
Create
New Folder.
The path to the sample project would look like this if you installed Revolve at C:\REVOLVE:
C:\REVOLVE\REDB\SAMPLE\SAMPLE.PRJ
If a sample.prj has already been created by another user in this directory, a New Project prompt is displayed. Click Yes.
Typically you would click Yes and then add your components but for the sake of understanding Revolve's functionality, we will separate this process.
Notice that the Project Manager is displayed. This is where you add and delete project components, create subprojects and set component level parameters. At the moment there are no components displayed. You will add them in the next section.
To add components to your project:
Add. If the Project Manager is not displayed, click
at the bottom of the Revolve
desktop or click the Project menu and choose Manager.
The Add Components dialog is displayed.
Be sure Filter is set to *.* and Type to automatic.
This directory contains all the source components that will be loaded into sample.prj. Notice that components are organized by type.
By doing this you specify the source files that are added to the project.
An Add Complete prompt displays the number of components that have been designated to be added to sample.prj.
You have added components to your project.
Figure 5-1: Files in the Project Manager
The files you added to the project are organized by type in the Project Manager.
Notice the cursor moved to select the fct files folder. If you are using the ALT and TAB keys to task switch between Revolve and the Getting Started, this will not work. In this case, select the fct files folder with the mouse.
Context key
on your keyboard.This displays a context menu. It enables you to perform actions available on the tool bar with your key board. This feature is available throughout the Revolve environment.
If your keyboard does not make use of a Context key, the functionality described below is available on the tool bar.
The Split Screen Editor displays the source
code for ONLINE.FCT. This corresponds to the
View Source
Code button.
In this exercise, you added starting points that the Automatic Component Locator will use to automatically create your project. The JCL and CICSTBL components reference COBOL and copybook files, which, in turn, have on line references to BMS and control-card files. The next step is to add search directories so Revolve can locate the referenced files. You will do that in the next section. Do not close the Project Manager.
When you added the JCL and CICSTBL components in the previous section, you provided a way into your code--an open door. Those files reference and call other files. If Revolve can't find referenced files, then sample.prj will be incomplete. To avoid this situation you should employ the Automatic Component Locator (ACL).
The ACL uses search paths to locate referenced files according to specified types. Search directories are mappings to files that are referenced by project components but are not explicitly added to the project through the Add Components dialog. For example, in sample.prj, if Revolve does not know where to find the files that are referenced by the JCL and the CICSTBL files, then the project will contain inconclusive information. When the search paths are defined, Revolve parses through the subset of added files and then iterates through to find referenced files in defined search directories. This ensures your project's source code is accurate and conclusive.
To define search paths for your project:
Add. If the
Project Manager is not displayed, click
at the bottom of the Revolve
desktop or select Manager from the Project menu.
The Add Components dialog is displayed.
File types must be defined for the type of files in the search directory.
The search path is defined for COBOL files. When the parser encounters references to COBOL files during the project build, it now knows where to find the appropriate files.
The search path is defined for copybooks.
The search path is defined for control-cards.
The search path is defined for BMS screen fields. The BMS screens that are referenced by on line COBOL files will now be pulled in from this directory.
The search directories that you just defined are listed.
The Project Manager still contains your original files. The search paths are defined and the project is ready to be built.
The components have been specified for inclusion in the project. However, the project database has not been created and parsed.
To build the project:
Make.
Make is also available from the Project menu.
The parser is invoked and parses through your source files to build sample.prj. It displays information about the loading process and the status of the source code that is being loaded. There are ten parsing phases. Notice how the Phase reading indicates that the code is passing from Phase 10 to Phase 6. This is the ACL connecting your components to the project through search paths. The Parser brings all loaded source code in the project up to date and displays a status of Loaded if everything is correct
This is all you need to do to build a project.
Close the project by selecting Close from the Project menu.
To open sample.prj:
Revolve loads sample.prj.
A good practice is to open the Project Manager and check the status of
project components. If you have components that are Out of date a
Make should update the
source files and give those components a status of Loaded.
To identify problems:
This brings up the Complete Project dialog box which displays a list of load modules and data files which are not resolved in the project.
The list of copybooks not found is displayed. All of Revolve's reporting capabilities can be used to find more information on the copybook that was not found.
The Imports browser is invoked.
Expand
Completely. This shows that the missing copybook is used in project components ONLINE2.CBL and ONLINE3.CBL. This is a link to the project source and the next step in identifying more information on EXTRADD.
Run. A Reports window and a Choose Components dialog are displayed.
These were identified by the Imports browser as reference points for the copybook.
The resulting report shows the errors or warnings in the two programs ONLINE2.CBL and ONLINE3.CBL. Scroll the Report window to view the entire output. Note Figure 5-3.
Figure 5-2: Unused Copybook EXTRADD
The problem is that the copybook EXTRADD was not found. Since there were no undefined variables it can be concluded that the information in the EXTRADD copybook is no longer being used by ONLINE2.CBL and ONLINE3.CBL. Clean up the desktop by closing down the information windows.
for the Report
window and the Imports browser. At this point the information that was discovered can be added to the Revolve database. Leave the Complete Project window open for the next exercise.
To do this:
Fix.... Fix enables you to resolve identified problems. In this case, the most appropriate action is to define the copybook as unavailable.
Once the copybook is defined as unavailable, the missing copybook entry will be removed from the Complete Project window. It is not deleted from the project. For the copybook EXTRADD to be removed you would have to explicitly delete it by using the Project Manager.
You can close Revolve, if you want to stop for now. The project that you have created and loaded is automatically saved.
You can continue with the next tutorial later, by simply reopening the project.
Copyright © 1999 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.
| Start Here for the Tutorials! | Assigning Scope with Subprojects | |