(for building a basic project in Revolve as described in the tutorial

Susan Flynn

Informations

• Publié par: Ontau
• Nombre de lectures: 9
• Langue: English

Extrait

Revolve Tips, Hints and Suggestions

(for building a basic project in Revolve as described in the tutorial.)

Note

: Tutorial directions are in italics, Tips are in plain print.

1)

4.2 Preparation

- Decide which drive you will put your Revolve project folder for the Sample

demo on. It can go anywhere - it doesn't need to be related to the folder where the source of the

demo is.

The project folder is portable. It can be created and built on a local machine and then

moved to a network server or the other way around. However, the mappings for the source

must not change. If the source is on a network drive named M:\, the local machine must

map to that drive as M:\ as well. Also, the entire folder must be moved when changing the

location of the project, not just the .prj file.

2)

4.4 Creating a Project

- The folder where you keep the project for an application is called its

project folder. The application's other files can be anywhere, since the project contains pointers to

them.

Each project must reside in it's own folder. If you have 10 projects, you will have 10

separate project folders. Meanwhile, the source files may indeed reside anywhere, Revolve

will always look for them in the location from which they were loaded. If the source is

moved, you must inform Revolve of it's new location by either deleting and re-adding the

components, or using the DOS Translations function under Utilites/Options.

3)

4.5 Adding Components to your Project

- The Project Manager window is where all the

source files in your project are listed. You don't have to add every one explicitly. Once you've added

the top-level files, Revolve can find the rest by following links such as CALL and COPY statements,

provided you tell it which folders to look in.

These search paths will bring into the project only those components that are used (called)

by the components you have added explicitly. If your copybook directory has 10 copybooks,

but your Cobol program only calls 2 copybooks from that directory, only those 2 copybooks

will be loaded using a search path to that folder.

4)

4.7 Building the Project

- There are now seven entries in the Project Manager, showing the

types of file in the project. The number in parentheses by each shows how many of that type there

are.

These folders should each be expanded, and the status checked. Next to each component in

the project manager is it's type and it's status. All components should be checked at this

point to be sure they all have loaded successfully. The possible statuses are: Loaded, Not

Loaded, Parsed, Out of Date, Not Found, Error, Old Version, Invalid and Not Used. The

status for each component is displayed as follows in the Project Manager:

•

Loaded

: Component is fully loaded and all queries will be valid based on the source code.

•

Not Loaded

: Component has not been loaded into the project database.

•

Parsed

: Component has been partially loaded and should be reloaded so it is fully

integrated into the database. It will be fully integrated into the database with the next

project Make. An asterisk following this status indicates that the component encountered an

error while loading.

•

Out of Date

: Source code for this component or related copybooks/includes has been

changed since it was last loaded into the database. To resolve this error, perform a Make. If

this error remains, check to make sure that this file is not contained within a database used

by another project. If this is the case, you'll need to delete both projects and recreate them

in separate directories.

•

Not Found

: Source code for this component is not located on the file system where it was

initially specified or it could not be located with the Automatic Component Locator.

•

Old Version

: Indicates that database file(s) for the component were located, however,

they were created with an older version of Revolve. This component must be reloaded

before analysis can be performed on its contents.

•

Error

: An error in the code was encountered during loading and caused an incomplete load

of the database.

Page 1 of 2

Revolve Tips, Hints and Suggestions

•

Invalid

: Indicates that 1) a designated preprocessor .dll is not available or 2) the

designated preprocessor failed due to source code error.

•

Not Used

: This status will only occur if called components are added explicitly, but are not

needed for the project.

The project is now built and completed. At this point, we recommend backing up your project. Go to

Tools/Scripts and expand the Utilities folder. Select Generate a Script to build this project from

scratch. Running this script will create another script called C:\Builder.RQS (the default name and

location). Saving this script will create a C:\Builder.RQC file. When run, this script will create this

project again, exactly as it is at this point. This includes any changes or fixes that were applied. If

the project should ever get corrupted, this can be run to recreate it. Whenever major changes are

made to the project, you can run this again.

Page 2 of 2