Glossary

A C D E I L M O P R S T U W

A

Administrator: A Revolve user who has been given the rights to configure projects as single user or shared and to authorize any additions or deletions of data that may be necessary. Refer to Chapter 4 "Using Revolve," section Modes of Operation for a list of Administrative rights.

C

Complete Project dialog box: The Complete Project dialog allows the user to fill in gaps in a project due to missing programs, copybooks, etc. This is a process which should precede any system wide analysis.
Component: A component is a single source file. When loaded into a project, it has a type which can include BMS, COBOL, DBD, MFS, PSB, or JCL. Copybooks, includes, procs, and control-cards are not considered components.

D

Data Management System (DMS): Database system for the Unisys OS 1100 system based on CODASYL specifications. The DMS 1100 manages mass storage device database files.
Dongle: See Usage counter.

E

Execution Simulator: The Execution Simulator provides a mechanism for analyzing the control flow in a system. Revolve traces the path through programs and screens.
Executive Control Language (ECL): A Unisys language used for constructing jobs that compile or run programs on 1100 series systems.
Extension: An extension is the DOS file type used for copybooks, includes, and proclibs. The default extensions include ".lib", ".cop", ".cpy", and ".cbl".

I

Impact: Impacts occur when source code elements are modified and that change effects other source code elements in the system.
Information Browsers: A group of dialog boxes used to present information about various types of elements and relationships in the system.
Integrated Editor: An editing tool that supplies the user with direct and unlimited access to source code. Changes to source code can be implemented singularly or across an entire application. Also appears in encapsulated form as the Split Screen Editor

M

Match: The Match button is located on the edit bars in most of Revolve's interfaces. Always preceded by an edit field and sometimes by a type drop-down listbox. Allows for search criteria to be specified.
Metering: In some Revolve-based products, someone needs to meter your application code before you can process that code using the Revolve-based product. Only one person needs to meter the code and it is then available for everyone to process. To meter code, you need write access to the metering control file and you need an enabled usage counter.
Metering control file: The metering control file keeps a record of the code that is metered. This file authorizes the users to process the metered code.; To access code that is metered, you need to point to the relevant metering control file to confirm that the code has been metered. The metering control file is called factory.bdb.; To meter code, you need write access to the metering control file. Ask the administrator to give you this access, as only the administrator can create the metering control file and set up the security protections on it. Then when you meter code, you point to the metering control file in which to meter the code.

O

Options: Options appear in some browsers and tools and allow the Revolve user to adjust the way information is displayed. Normally accessible from the Options button, located on the button bar. There are also Options available from the Utilities menu, specific to users and administrators.

P

Point of interest: A point in a program that is of interest and that you identify when analyzing an application. A point of interest can be a suspect line of code that might cause an error when the application runs dates. A point of interest might also be a data item or any other element in a program.
Project: A project contains the parsed representation of all the components that have been loaded. It is contained in a file with the extension ".prj".
Project Manager window: The Project Manager window is the control panel for the active project. It is used to view and manipulate the components of a project.
Project path: The project path specifies which directories contain the component databases. The default directory is \revolve\redb, but component databases can exist in other directories or on other machines.

R

Report: A text based document created by a script
REQL: Revolve Query Language: database language specifically designed to answer questions about source code.

S

Screen view: The Screen view provides an image of a BMS or MFS screen as it would appear on a terminal.
Script: Scripts are programs that automate activities in Revolve. There are many scripts provided with the product.
Search Directory: A Search Directory is a directory on the local system that is identified as containing files of a certain type. The Automatic Component Locator uses search directories to locate and load files.
Security key: See Usage counter.
Selected Element: A description of the selected element appears at the bottom of the desktop. An element is selected by right clicking on the element in any tool or browser and choosing Select.
Set: Hierarchical collection of record types in a database.
Source path: The source path specifies which directories contain copybooks, includes, and proclibs. It needs to be set so that these files can be found and included during parsing.
Source view: Provides a display of the source code. The Source view shows a logical view of the source files, including COBOL and JCL, with copybooks and include files interleaved.
Speed Menu: The pop-up menu for the selected item. This menu appears when you right-clicks the mouse button on the selected item.
Split Screen Editor: The encapsulated version of the Integrated Editor that appears when the View Source Code button is pressed. Allows access to source code for editing.
Status bar: The status bar is located at the bottom of the desktop window and at the bottom of some Revolve interfaces. It contains several objects which provide quick access to important information and functions. The right hand side of the status bar provides a display of the selected element.
Subproject: A subproject is a collection of individually specified items that are taken from a Revolve project to be analyzed and modified in specific ways.
System view: Depicts the calling relationships between all JCL jobs, programs, screens, and databases in the project.

T

Type: The class of an element. For example, cobol_state_move is the type for COBOL move statements, and cobol_label_para is the type for paragraphs.

U

Usage counter: A usage counter, also known as a dongle or security key, resembles the plug by which a printer is plugged into a computer.; You receive a usage counter with the Metering Administration pack. If you (or your systems administrator) have not already ordered one of these packs, and you need to meter code, please contact your MERANT sales representative.; In some Revolve-based products, the code is metered by means of the usage counter, which is credited with a number of lines of code. When someone meters code, the usage counter must be attached to the back of that person's PC and then the counter is debited by the appropriate number of lines.; See also metering.
Users: Individuals with access to analysis tasks and no administrative rights.

W

Wildcard: The Revolve wildcard character is an asterisk (*). It appears by default in most Match edit boxes. It establishes similar strings in Match searches.
Worksheet: Holds the points of interest that you identify when analyzing your application. The worksheet keeps track of what's of interest and the decisions made. You can record details on each point of interest, such as the reasons for it being of interest, what sort of problem it represents, and what further treatment it needs if any.