USING REVOLVE TO IMPROVE GDT PROGRAM MAINTENANCE

USING REVOLVE TO IMPROVE GDT PROGRAM MAINTENANCE

GDT 2004 International User Conference – Evolving the Legacy July 11 - 14 Tucson, Arizona

Using Revolve to Improve GDT Program MaintenanceDoug Evans

The InfoSol GDT Environment



The Revolve Project

Analyzing Data Impacts Project Inputs to project

JCL Forms Source (COBOL Programs) Copybooks

Trace Impacts Automatically Execution Simulator

Global Editing Document Your Findings (Annotations,

Program Inventories and Source Code Flows)



The Process

Create the Project Build the Repository

The DataBase Load process

Analyzing Data Impacts The Execution Simulator Tracing Impacts Automatically

Document your Findings Using Annotations



The Process

Project Documentation provided by Revolve Graphical view of Program Inventory Source Code Flow Charts

Modifying members of the Repository Global Editing / Split – Screen Editor



Creating the PROJECT

First, we need to create a new project. From the Project drop down menu we will select New.



Creating the PROJECT

Here we will create a project TRAINING. What we will plan to do is load this project with the source, copybooks and JCL .



Building the Repository

You are now presented with a prompt to see if you want to add components (COBOL source, copybooks, JCL) or not at this time. We will press the Yes button and continue.




The Add Components screen allows you to locate the component to add as well as gives you some options to allow Revolve to find the components quicker. In this case we have set the Filter to find all .CBL source and select the Component Type as COBOL.




We now can narrow down to the folder that the COBOL Source can be located. In this case I am selecting the INFOSOL folder on the Root of the C:\ drive.




Under the INFOSOL folder, we have broken up the different components into their own folder. Here we will select the PROD folder.







Right away, based on the Filters set, only the .CBL’s of the BATCH folder are shown. We will now select the .CBL’s and press the ADD button to add to the Project Repository.




Here you see that 2 components were added to the repository.Press OK to continue adding the other components.




We will now add the Online (TPR’s) source components.

6 TPR’s were added to the Project Repository (COBOL files).




Here we will add the copybook components. Note the Type is set to copybook and the Filter is set to wildcard since there are no specific identifier for the copybooks (.ie .CBL extension for COBOL source).




2 batch copybook components were added to the Project Repository (copybook files)




18 online copybook components added.




16 GCOS7 form copybook components are added.




Now we will add the JCL components using TEXT Filter.Please note: GCOS JCL cannot be analyzed under REVOLVE.




GCOS JCL What we will be able to do is allow REVOLVE to add

all text, pertaining to the JCL, to the repository. This will give us capabilities to do TEXT BROWSING searches which will be useful in IMPACT ANALYSIS PROCESSES to be discussed later in the document




GCOS7 Form components are added as text.Now we will press the DONE button.




Before we can start the Database Load Process, we need to set the COBOL Source Component settings necessary for Revolve to do the Database Load.



Data Base Load Process

Now, under the Utilities Dropdown menu, we will select Options.




Click Yes to include text files (JCL and Standard GCOS7 FORMS).

Click Yes to include copybook files

Here we need to press the Yes button to include all COBOL files

when setting the Source Component Options.Click Yes to

include COBOL files



Here we need to specify that the Comments (*) begin in the first column and that the source lines begin in Column 1. This takes into consideration the SOURCEFORMAT(FREE) COBOL directive being used.





Now we will select the copybook, text files and COBOL folders and press the Load Selected button. This will initiate the Database Parsing process.




This window will pop up on the screen showing the Parsing of all components selected being loaded into the repository database.




To verify that the Load Process went well you can double click on each folder within the Project Manager to see which components were loaded and which ones were not loaded.




COMPLETE will list all the types of errors that REVOLVE could have found when parsing through the project.




All copybooks were found, but there were some load modules (CALL’s) via the COBOL programs that were not found




Here we selected a missing load module and right click and select Browsers and Programs. This will show us what program(s) use this load module.




Here we see that program ADDRESS1 uses this load module. You can further drill down to get more details of where this load module is located specifically in the program.



Analyzing Data Impacts

First scenario: You want to expand all ZIP CODE fields by 4 bytes. You need to analyze the impact of this.First we will see how you can use REVOLVE to manually to follow logical connections defined in source code to analyze impacts and then see how REVOLVE can automatically determine the impact of changing the Variable.




First, we will use the Text Browser to begin the manual impact trace.




We will type in ZIP as the variable and press the Match button. REVOLVE will search the complete database for any use of ZIP.




You are now presented with the programs using the text ZIP. We will now expand each program to view where the TEXT ZIP is used.




Expanded view of source. From this information I can see two data file fields INFOSOL-ZIP and IADDR1-ZIP that I want to expand. INFOSOL-ZIP is contained in the file definition file ADDRESSFL. FD-IADDR1 is in the file definition FD-ADDR1.




Here are the results for the field INFOSOL-ZIP.



Analyzing Data Impacts and Split Screen Editor

Now we will open up the Split Screen Editor to see corresponding source code as it is selected in the top Text Browser Window. The Editor also allows you to make changes to the program.




Here you see the definition of the field being highlighted.




In the editor, you can also press the DEFINITION of USAGE button on the toolbar to get the field definition.



Execution Simulator via the Split Screen Editor

You can also launch the Execution Simulator via the button provided on the tool bar. With this you can simulate execution of the code either forward or backward so that the logical paths through the source code can be traced to determine impacts.




Now the Run button is presented to launch the Execution.




As execution proceeds, you will be prompt to assist REVOLVE in the decision making at conditional execution points. After completing the Execution Simulation, you can capture the results into a Annotation.



Use of the Annotations

Now lets capture your Execution Simulation into an Annotation that will document our findings.First we need to press the Capture Results Button.

We will select the Add to Annotation option




We will press the New Annotation button and enter the title for the Annotation. In this case we enter ADDRESS PROGRAM SIMULATION.




Here we see, after pressing the Add button, that 26 elements were captured and added to ADDRESS PROGRAM SIMULATION annotation.




Now lets look at the annotation.

Here is a list of all available annotations. We will now look at ADDRESS PROGRAM SIMULATION.




Here you will see the exact flow the simulation followed. We will now open the source code.




As you step down the lines in the Annotation browser, the lines in the Source code are highlighted giving you another view of the flow.This becomes great System Documentation, since you can have other users just open an annotation to step thru the flow and quickly understand the flow of a program.



Tracing Impacts Automatically

Here under the Variables Browser, we will right click on the variable INFOSOL-ZIP, select tools and then Impact Analysis.




Under the Impact Analysis screen, we will select INFOSOL-ZIP and press the Impact Tracing button on the tool bar.




First will chose the Options button for setting the properties of the Impact Analysis.

We will select Impact Group for this analysis.




And we will select Waterfall as the Tree format for display.




Here is the full break down of the impact analysis.




You can now open up the split screen editor to view the source code for each line shown in the Impact Analysis.



Using Annotations to Document the Automatic Impact Analysis

Here we want to capture the results of our Impact Analysis of variable INFOSOL-ZIP. Select the information on the screen and press the

Capture Results button on the toolbar.




We will create a New Annotation by pressing the New Annotation button.We will call the new annotation “INFOSOL ZIP FIELD EXPANSION IMPACT ANALYSIS”




Now we press the Add button to add the annotation. 10 elements were added. Press OK to continue.




You can use the split screen editor to view the source code from the entries in the Annotation. (Modify the code too!)

Just by pressing the Match button, a list of your Annotations will be displayed. Now we will select the INFOSO ZIP FIELD EXPANSION IMPACT ANALYSIS and expand completely.




Lets now edit the annotation giving the annotation a good descriptive name, submitted by name, submitted to name, status and element descriptions.

First, the Description is updated.




Assignment of project is given.




The status can be updated as well




Here, we add the element description.




Now, after editing the annotation, the view of the annotation via the Annotation browser is much more descriptive and great for project management tracking.



Graphical View of Program Inventory

We will select program INFADDR1.CBL from the Project manager and open up the Split Screen Editor. Now we will press the Inventory View button on the toolbar of the Editor.




Now you are shown the inventory view of the program (inputs and outputs).




The inventory view can be saved as an Enhanced Metafile.



Source Code Flows

Here we select the program that we want to produce the code flow chart for.Now under the Tools dropdown menu, you select Views and Code Flow.



Source Code Flows

Here is the code flow. You are able to scroll up/down left/right to view the complete chart. You can also save this as a metafile document.



Global Editing

What we want to do is change all variables named SYS-DATE to SYS-DATE-INFOSOL of the components within the Active Revolve Project.

First you need to open the Integrated Editor.



Global Editing

Now you press Search and Replace Button and fill in the necessary search parameters.



Global Editing

Also, under Origin, you select System to search and replace across the entire project.



Global Editing

Here is the replacement within ADDRESS.CBL



Global Editing

Another replacement in ADDRESS.CBL.



Global Editing

It then moves on to another program in your project (PROJECTS.CBL).



Modification Driver

Used to support the transition between source code and implementing modifications. Tag columns Insert Text Insert Comments Insert Blocks of text

GREAT FOR INCORPORATING INDENTICAL MODIFICATIONS TO GROUPS OF FILES!



Modification Driver

Scope: add a “Comment Block” in all locations where TD-FIELD2 is used throughout the Project. This Comment Block will contain a comment explaining what is needed to be done with the TD-FIELD2 field. Via the Variables Browser, we will find all instances of the TD-FIELD2 field. We will select the Modification Driver button on the toolbar.



Block Definition Setup

Tag Columns To insert text in the selected component’s

source columns




Insert Before To indicate that you want to insert a tag before

the selected component’s source




Insert After To indicate that you want to insert a tag at the

end of the component’s source code




Duplicate and comment out original Check this to duplicate and comment out

original source.




Execute Button To insert tags into

the selected component’s source code

Skip Button To skip the slected

component without inserting tags




Execute All Button To insert tags into all

selected components Done Button

To finish inserting tags into source code

Blocks…Button To open the Modification

Driver Code Blocks dialog box. To define or load existing blocks of code into the Modification Driver for insertion into your project’s source code



Modification Driver

First we need to create the Comment Block. To do this, press the Blocks… button and it opens the Modification Driver Code Blocks window. Here, you give the Block Name and the contents of the Block in the Block Definition Window. You then press Save As…



Modification Driver

Press save to save the Block just created



Modification Driver

We will now check the Insert Before box and select the Block Definition to be used. %% is mandatory before the name of the Block Definition. We will now press the Execute button.



Modification Driver

Here you see via the Split Screen Editor, that the Block Definition was placed just before the Line highlighted



Modification Driver

We will now highlight all locations of TD-FIELD2 so we can place the Block Definition before each line



Modification Driver

This time we will press the Execute All button to insert the Definition Block into all selected components.



Modification Driver

As we select each line in Variable window, you can see the corresponding addition of the Block Definition in the Split Screen Editor for that line of code



Modification Driver

Again we show the addition of the Block Definition



Using Predefined Revolve Scripts

Click Tools and Scripts

Double click the Unused Analysis Folder




Select Unused Procedural Logic and click the RUN button Select IPROJECT.CBL and click OK.




Click on the report line that reads:ERROR-IPROJECT. It will not be highlighted but the status bar at the bottom of the Report shows it as selected.




Highlighted in yellow has been identified by the script as unused code.

Date post:	11-Jan-2016
Category:	Documents
Upload:	helene
View:	25 times
Download:	1 times

USING REVOLVE TO IMPROVE GDT PROGRAM MAINTENANCE

Documents