The JAMS Scheduler for OpenVMS is the only required component that can run JAMS on OpenVMS. This installation kit includes the JAMS Scheduler, a command-line interface, and a character-cell interface.
JAMS for OpenVMS is delivered in three basic packages.
The JAMS Agent for OpenVMS is an optional component that allows JAMS Schedulers running on other machines (Windows or OpenVMS) to execute Jobs on an OpenVMS system.
The JAMS Windows components for OpenVMS package contains Windows-based components can that be used when running the JAMS Scheduler on OpenVMS. These components include:
The OpenVMS Connection Server is a Windows service that acts as a middle tier between an OpenVMS Scheduler and Windows Clients. This is an optional component and must be used with JAMS Windows-based Clients to access an OpenVMS-based JAMS Scheduler.
The JAMS Client and JAMS Agent in this kit are exactly the same as the Client and Agent in the Windows kits.
JAMS uses a temporary directory for storing temporary command procedures for parsed and jacketed jobs. If a VMS directory file becomes too large performance can degrade. If you expect to have more than 800 to 1,000 parsed or jacketed jobs scheduled simultaneously, it would be advisable to use more than one temporary directory.
To work with more than one temporary directory, create directories in the current JAMS temporary directory. The directories must be named TEMPn where n is the number of the directory. The numbers must begin at 1 and increase without any integer gaps. After creating the directories, you must define the logical name JAMS_TEMP_DIRECTORY_COUNT to be the number of temporary directories you created. This logical must be defined with /SYSTEM and /EXECUTIVE. The following example assumes that the JAMS temporary directory is JAMSDSK:[JAMS.TEMP].
$ CREATE/DIR JAMSDSK:[JAMS.TEMP.TEMP1] $ CREATE/DIR JAMSDSK:[JAMS.TEMP.TEMP2] $ CREATE/DIR JAMSDSK:[JAMS.TEMP.TEMP3] $ DEFINE/SYSTEM/EXEC JAMS_TEMP_DIRECTORY_COUNT 3