1 / 97

USING REVOLVE TO IMPROVE GDT PROGRAM MAINTENANCE

USING REVOLVE TO IMPROVE GDT PROGRAM MAINTENANCE. 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

helene
Download Presentation

USING REVOLVE TO IMPROVE GDT PROGRAM MAINTENANCE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. USING REVOLVE TO IMPROVE GDT PROGRAM MAINTENANCE

  2. The InfoSol GDT Environment

  3. 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)

  4. 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

  5. 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

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

  7. 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 .

  8. 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.

  9. Building the Repository 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.

  10. Building the Repository 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.

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

  12. Building the Repository

  13. Building the Repository 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.

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

  15. Building the Repository We will now add the Online (TPR’s) source components. 6 TPR’s were added to the Project Repository (COBOL files).

  16. Building the Repository 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).

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

  18. Building the Repository 18 online copybook components added.

  19. Building the Repository 16 GCOS7 form copybook components are added.

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

  21. Building the Repository • 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

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

  23. Building the Repository 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.

  24. Data Base Load Process Now, under the Utilities Dropdown menu, we will select Options.

  25. Data Base Load Process 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 Click Yes to include copybook files Click Yes to include text files (JCL and Standard GCOS7 FORMS).

  26. Data Base Load Process 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.

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

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

  29. Data Base Load Process 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.

  30. Data Base Load Process COMPLETE will list all the types of errors that REVOLVE could have found when parsing through the project.

  31. Data Base Load Process All copybooks were found, but there were some load modules (CALL’s) via the COBOL programs that were not found

  32. Data Base Load Process 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.

  33. Data Base Load Process 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.

  34. 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.

  35. Analyzing Data Impacts First, we will use the Text Browser to begin the manual impact trace.

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

  37. Analyzing Data Impacts 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.

  38. Analyzing Data Impacts 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.

  39. Analyzing Data Impacts Here are the results for the field INFOSOL-ZIP.

  40. 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.

  41. Analyzing Data Impacts and Split Screen Editor Here you see the definition of the field being highlighted.

  42. Analyzing Data Impacts and Split Screen Editor In the editor, you can also press the DEFINITION of USAGE button on the toolbar to get the field definition.

  43. 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.

  44. Execution Simulator via the Split Screen Editor Now the Run button is presented to launch the Execution.

  45. Execution Simulator via the Split Screen Editor 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.

  46. 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

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

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

  49. Use of the Annotations Now lets look at the annotation. Here is a list of all available annotations. We will now look at ADDRESS PROGRAM SIMULATION.

  50. Use of the Annotations Here you will see the exact flow the simulation followed. We will now open the source code.

More Related