Recommended (but optional) first step

Two environment variables should be set: PRM_TOP and ARCH.

PRM_TOP is the "root" of the installation of PRM and it can be in principle any directory you want, but for now set it to: /nfs/gost/

ARCH is the architecture of your machine. If you are running SunOS 4.x or Solaris, set it to sun4; if you are running HP-UX, set it to hp700; other architectures are not yet supported.

Directory where the relevant binaries are

It is: $PRM_TOP/bin/$ARCH, i.e. /nfs/gost/bin/sun4

Starting a node manager

To start a node manager on your machine, first cd to the above directory, then run the start_node script.

The script takes the following switches:

The switches can be used in whatever combination is more appropriate for the needs of the user (i.e. -t and -b will cause the node manager to allow running of jobs only within the specified time window AND if the machine is idle; similarly, -t and -i will allow running of jobs only within the time window AND if there's no user logged in).

The script checks whether there is already a node manager running on your machine. If it doesn't find any, it starts a node manager; otherwise it does nothing.

To stop a node manager, use:

stop_node your_host_name

or kill it using the Unix kill(1) command.

Running an application under PRM

To run an application under PRM, the job manager must be invoked, specifying the name of a job configuration file:

jobmngr -j jcfile


jobmngr -D -j jcfile

The -D option activates the printing of some informational messages.

An example of an application which runs under PRM is crack_des, a program which cracks DES keys by brute force, i.e. trying all possible keys on a (plain text, cypher text) pair.

The job configuration file for crack_des is jcdes. It contains attribute-value pairs among which are the name of the application (t = crack_des_master) and the name of the machine which runs the system manager (s = in jcdes).

To check the status of the jobs running within PRM, the prm_jobs command can be used. Also, the system manager running on can be queried using the command:


Go to PRM home page.