PreviousCustomizing the Analysis Environment Assembler ExtensionNext

Chapter 7: Administering Group Working

This chapter describes the features that enable programmers or analysts to work together in a group on the same project, with the work divided between them. These features are intended for the system administrator.

7.1 Introduction

Revolve provides the following features that help you, the system administrator, to facilitate and manage group working:

7.2 Shareable Projects

You have the ability to make projects available to more than one user at a time. When a project is made shareable a duplicate copy of the project is created, given an extension of .SHA, and stored in a different directory than the initial project. The copy is referred to as the Shadow Project.

Using a shareable project is not the same as using a network version of Revolve, where multiple users can use the same copy of Revolve at the same time. A shareable project can be accessed simultaneously by several users across a network. However, access to shareable projects is controlled. There are two levels assigned to shareable project operators:

USERS have analysis specific privileges in the shareable project. They perform analysis tasks and edit source code. But USERS cannot make changes to project loading and component options, like Search Directories or Component Parameters. They also cannot add or delete components. The modifications that a USER makes are implemented in the Shadow Project. It is the Administrator's responsibility to apply those modifications to the actual project.

The rights specific to an administrator include:

7.3 Automating Project Management

The Scripts tool provides project management scripts for you to use as templates for automating your administrative tasks. These scripts implement REQL functions and constructs for batch project management procedures and operations. Pronounced REE-QUAL, REQL is an acronym for Revolve Query Language. It is used to manage the Revolve database. REQL, used in conjunction with the provided scripts, facilitates batch, command line, project management, where an administrator maintains numerous projects at one time by running customized scripts.

When you use REQL in project management you should be familiar with some general functions and parameters. These correspond with features that are also available in the Graphical User Interface (GUI). For example, the projectOpen function corresponds to the Open option on the Project menu. Where the Open option displays a dialog box that you use to open a project, the projectOpen function requires that you enter the path to the project. For more specifics on REQL, see the chapter Introduction to the REQL Language.

7.3.1 General Project Functions

The following functions correspond to features accessible on Revolve's Project menu:

REQL Function
GUI Equivalent
projectClose Close on the Project menu.
projectMakeShareable Make Shareable on the Project menu.
projectNew New on the Project menu.
projectOpen Open on the Project menu.
deleteProject Delete Project on the Project menu.

7.3.2 Project Load Functions

Use the following functions when loading system components into a project The square brackets [ ] indicate optional parameters.

These functions correspond to those available on the Project Manager.

REQL Function
GUI Equivalent
addComponent(strPath, [type]); Add Components
projectAddDirectory(strPath, strFileSpec, indIncludeSubDirs [, type]); Add Components
addComponent(strPath, [type]); Add Components
projectAddDirectory(strPath, strFileSpec, indIncludeSubDirs [, type]); Add Components
projectRemoveComps(setUid, [, indDeleteDatabase [, indDeleteSearchPath]]); Delete Components
make(); Make
makeSelected(); Load Selected
parse(); Make
status(); Status
addPathSource(strPath, type, [, indScan [, parent]]); Search Directories (Project Level)
addExtSource(strExt, type); Extensions

7.3.3 Component Type Functions

REQL supports a wide variety of component types. Use the following type parameters when you add components to a project with REQL. These correspond to options available in Add Components.

File Types

Import Types

7.3.4 Component Parameters

This section describes functionality that corresponds to the Component Parameters feature that is accessed from the Utilities menu. All parameters are project level, in the sense that settings encompass components according to their type. The syntax for setting a component parameter is:

retCode :=addRel(sourceUid, relation="attribute-name", value);

A return code of 1 indicates success, 0 indicates failure. To set values for default project values with new components, use the project as the sourceUid parameter. To set values for existing components, use the component as the sourceUid parameter.

The following integer attributes are modified with the corresponding relationships.

The following string attributes are modified with the corresponding relationships.

The following flag attributes are modified with the corresponding relationships:

To set values for existing components, use the component as the sourceUid parameter:

The syntax for getting an existing setting is:

retVal :=sourceUid:>attribute-name;

For example:

retVal :=project:>attr_reql_comp-param-i_start-column;
uid :=system_component_cobol="BATCH1.CBL";
retVal :=uid:>attr_reql_comp-param-i_start-column;

The following project options are set and returned with the setOption() and getOption() functions.

7.3.4.1 Search Paths and Extensions

The following functions enable you to add search paths, and extension-type mappings. These correspond with functionality available in Search Directories.

For additional descriptions and examples of functions associated with REQL, refer to the Functions chapter.


Copyright © 2000 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.

PreviousCustomizing the Analysis Environment Assembler ExtensionNext