Workbook for SLD Offline Users - Project

Most SLD offline users find themselves managing a number of separate analysis projects at any given time.

Each project may require a different combination of:

DUCS settings
Setup_com files for user-created shareables
Directory from which to run IDA
Choice of host (Vax or Alpha) on which code has been compiled

A system has been created to keep track of these various settings for distinct projects. The system uses a command called PROJECT.

The syntax for the PROJECT command is as follows:

PROJECT NEW project_name
PROJECT QUIT
PROJECT RESTORE project_name
PROJECT QUERY
PROJECT LIST
PROJECT COMMENT
PROJECT SAVE
PROJECT COPY old_project_name new_project_name
Running a Job Managed by PROJECT

The PROJECT command has a corresponding new command to take care of all compiling and linking. This new command is called EXPEDITE. It replaces old commands such as PREPMORT, COMPILE, MAKESHR and ACTION.

PROJECT NEW

To begin using the system, type the command: PROJECT NEW project_name The project name can be any string. It is just a name you will use to refer to this project in the future.

If you leave off the name, you will be prompted for one.

The project system will then create two files in your login directory.

project_name.DUCS_SAVE_COM contains your current DUCS settings
project_name.PROJECT contains a pointer to the DUCS_SAVE_COM plus some other project related information.

The project system will also redefine a number of standard symbols such as DUCS and IDA such that these commands now pass through the PROJECT system.

Every time you issue a DUCS command that changes your DUCS settings, the PROJECT system will save the new DUCS settings.
Every time you issue the IDA command, the PROJECT system will first check whether you were in the directory you were in when you started this project. If you are not, you will be asked whether you really want to run from the current directory.
When you issue any of the old commands that do compilations and make shareables, such as PREPMORT, COMPILE, MAKESHR or ACTION, you will be told to instead use the new command EXPEDITE.

PROJECT QUIT

Though it should not be necessary in a typical session, you can turn off the PROJECT system by typing: PROJECT QUIT This restores all of the special symbols, such as DUCS and IDA, that were redefined by the PROJECT system. It restores the symbols to whatever values they had before you began the current project.

PROJECT RESTORE

To restore the settings saved for a given project, type the command: PROJECT RESTORE project_name If you leave off the name, you will be shown a list of projects currently defined for your account (it lists all of the .PROJECT files found in your login directory).

When you restore a project,

DUCS settings are restored to the values last used in that project
any .SETUP_COM files generated for that project are run (these files set up logical names for user-defined shareables)
your default directory is set to the directory currently noted as the "run Ida directory" for that project
you are warned if there is compiled code referred to in that project that was compiled or linked on an inappropriate kind of host. (Recall that code that is compiled on a Vax cannot be run on an Alpha and code that is compiled on an Alpha cannot be run on a Vax). This last check is not perfect but will catch most common mistakes. It notes what kind of host the user is on the first time they do any compile or link in this project. It then warns the user if they try to compile or link in the same project on a different kind of host. It resets to not care about the kind of host if it finds that there are no files of type OBJ, OLB or EXE in any of the project's test directories.

PROJECT QUERY

To get information about what project, if any, is currently active: PROJECT QUERY

PROJECT LIST

To get a list of all projects currently defined your account: PROJECT LIST The system lists all of the .PROJECT files found in your login directory.

PROJECT COMMENT

You can store comments in the currently active project file by typing: PROJECT COMMENT comment_text These comments will appear in subsequent PROJECT LIST or PROJECT QUERY commands.

PROJECT SAVE

If you really want to, you can type: PROJECT SAVE But it doesn't do anything. All saving is done automatically as you work. When you change your DUCS settings, the PROJECT system saves the new settings. When you create a new shareable, the name of its SETUP_COM file is saved. And so forth.

PROJECT COPY

If you want to create a new project and have that new project start off using the saved settings of a previous project, type: PROJECT COPY old_project_name new_project_name The old project file will be copied to a new project file. The corresponding file of saved DUCS settings will also be copied, and the new project file will point to the new file of saved DUCS settings.

You can then further develop either project without affecting the other project.

Running a Job Managed by PROJECT

When it comes time to run a job, whether from batch mode or interactive mode, there is no need to issue any DUCS settings, no need to set a default directory and no need to run any SETUP_COM files.

Just issue a single PROJECT RESTORE command.

Thus, a .COM file to submit as a batch job would just need:

   $ PROJECT RESTORE project_name
   $ IDA
   and some IDA code

Remember to include a CHAR=VAX or CHAR=ALPHA option in your SUBMIT command. This is necessary to make the job run on the same kind of machine that you compiled and linked your code on.

Back to Workbook Front Page

Joseph Perl
13 September 1995