PreviousUsing Annotations Scripts, Editing and the ShellNext

Chapter 7: Exploring and Documenting

In this session, you look in more detail at the various Views, and at the Split Screen Editor and the Execution Simulator. You use them to find a JCL job and to make changes.

Please see the Tutorials Map to check that you have run all necessary previous sessions.

7.1 Overview

You can use Revolve to explore the structure of an existing system. Through the use of Views you can move step-by-step through an illustration of data movements in your source code.

Views provide graphical overviews of your system and different modules in your source code. They enable you to study your application to navigate the execution sequence. Views are good resources for system reference when you're not quite sure where to start or what information you need.

7.2 Preparation

This session uses the project you created in the chapter Using Revolve.

  1. If you have closed Revolve, open it as before.

  2. Open the Sample project by selecting it from the "recently used files" list at the bottom of the Project menu.

7.3 Exploring the Application

To explore your application through graphical views:

  1. Click Tools > Views > System.

    The System View illustrates the calls that link programs in the project together. It displays icons that depict the project's different programs as well as other system items. Between the icons are the links that connect them. The icons and links represent source code entities.

    This system contains a JCL job.

  2. To isolate the JCL job, click Find.

    The Find dialog enables you to isolate information in the System View.

  3. Uncheck everything except JCL jobs.

  4. Select job P00045R (REP1.JCL) from the list.

  5. Click OK.

    The JCL job card icon represents the JCL job. It is curently selected, as shown by an outline around it. (You may need to get rid of this outline temporarily, by selecting something else for a moment, to see this icon is shaped like a punched card.)

  6. Click Refocus.

  7. Click Expand Completely to expand the JCL.



    Figure 7-1: System View

  8. With the JCL selected, click View Source Code .

    This opens the Split Screen Editor where the source code for the JCL job is displayed.

  9. In the Split Screen Editor, click Inventory View.

    The Inventory view graphically depicts the steps, DDs, executables, and databases in the JCL job.



    Figure 7-2: Viewing Graphically in the Information Window and Editor

  10. To zoom in on the illustration, click Overview Panel. You might need to make the window slightly wider if you can't see this button on the toolbar.

  11. To zoom out on the illustration, click Overview Panel.

  12. Scroll down and right-click the BATCH1 icon .

  13. Click Select.

    BATCH1.CBL is the selected element. Notice it is selected in the System view in the top pane.

  14. Click Inventory View again.

    The Inventory view closes and is replaced by the Split Screen Editor displaying the source code for the program BATCH1.CBL.

You have isolated a program by using the graphical views. Do not close any windows or tools.

7.4 Exploring Source Code Logic

To explore the logical steps of BATCH1.CBL:

  1. In the Split Screen Editor, click Execution Simulator.

    The Execution Simulator tool bar appears. This shows that the Execution Simulator is invoked and ready.

  2. Click Run.

    The code executes slowly, while displaying the logical procedural flow. The walk through is displayed, item by item, in the Execution Path display. Wait until execution pauses when an IF statement in the code is encountered, and the Execution Simulator Branch Choices dialog box opens.



    Figure 7-3: Execution Simulator Condition Prompt

  3. Click Cancel to close the Execution Simulator Branch Choices dialog box.

  4. From the Windows menu, select the Close All Windows menu option.

7.5 Summary

In this session you:

7.6 Before Continuing

If you want to take a break before going on to the next session, you can close the project; or you can close Revolve, with or without closing the project.

Return to the Tutorials Map and choose which session to go on to next.

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.

PreviousUsing Annotations Scripts, Editing and the ShellNext