Each project may require a different combination of:
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:
The PROJECT command has a corresponding new command to take
care of all compiling and linking. This new command is called
It replaces old commands such as PREPMORT, COMPILE, MAKESHR and ACTION.
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_COMcontains your current DUCS settings
project_name.PROJECTcontains 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.
PROJECT QUITThis 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 project_nameIf you leave off the name, you will be shown a list of projects currently defined for your account (it lists all of the
.PROJECTfiles found in your login directory).
When you restore a project,
PROJECT LISTThe system lists all of the
.PROJECTfiles found in your login directory.
PROJECT COMMENT comment_textThese comments will appear in subsequent PROJECT LIST or PROJECT QUERY commands.
PROJECT SAVEBut 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 old_project_name new_project_nameThe 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
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.