After successfully installing the JAMS Scheduler, it is important to perform the following tasks.
You must execute the JAMS startup procedure on every node that will be using the JAMS Scheduler. The JAMS startup procedure should be executed before starting a batch queues
To ensure that the JAMS startup procedure is executed every time the system reboots, insert the following line into the system startup procedure: (SYS$MANAGER:SYSTARTUP_V5.COM)
$ @SYS$STARTUP:JAMS_STARTUP.COM
![]() |
Note: Make sure to insert this line after the disk that contains the JAMS data files has been mounted and before initiating any batch queues. |
The JAMS startup procedure can also be defined as a startup file using the VMS SYSMAN utility.
Batch Jobs must register with the JAMS Monitor when they start execution via the JAMS_REGISTRAR.EXE. The JAMS Registrar then records all batch jobs with the JAMS Monitor.
The easiest way to make sure that all batch jobs are registered is to insert the following line into your system-wide login command procedure.
$ 'f$trnlnm("JAMS_LOGIN")'
It is recommended that you insert a line (as shown below) in your system shutdown procedure (SYSHUTDWN.COM) to stop the JAMS Monitor process as well as the Scheduler process if that too is running.
$ MCR JAMS_EXE:JAMS_MASTER.EXE STOP MONITOR
JAMS is fully initialized on the node where the installation is performed. In order to initialize JAMS on other nodes in a VAXcluster, issue the following commands on each node on which JAMS executes:
$ LICENSE LOAD JAMS/PRODUCER=MVP
$ @SYS$STARTUP:JAMS_STARTUP.COM
JAMS includes a batch job that is used to submit recurring Jobs. The first time you install JAMS you will need to manually submit this Job. To submit the JAMS_AUTOSUBMIT Job, enter the following command:
$ MCR JAMS_EXE:JAMS_MASTER SUBMIT/NOPROMPT JAMS_AUTOSUBMIT
If this is a reinstall of JAMS, the JAMS_AUTOSUBMIT job should already be pending in a batch queue.
If planning to access JAMS on this node from a remote node, you must define the DECnet objects for the JAMS Server. Do this by executing the command procedure:
JAMS_COM:JAMS_DEFINE_DECNET_OBJECTS.COM.
If installing JAMS on a VAXcluster, there may be other nodes in the cluster running during the installation. To avoid rebooting these nodes after installation, execute the JAMS startup procedure on each node that will be using JAMS.