| Contents | Support |
| ||
|
| Previous | Contents |
This chapter describes how to install JAMS on OpenVMS.
The installation procedures are described step by step and are, for the
most part, self-explanatory. The system prompts you to answer questions
and waits for you to respond before continuing.
2.1 Update Installation
If you are updating from an earlier version of JAMS, please
read the following sections before performing the upgrade. If this is a
new installation of JAMS, proceed directly to Section 2.2, Preparing to Install JAMS.
2.1.1 Shutdown JAMS
You should not attempt to install an upgrade to JAMS while it
is running. Before you perform the upgrade you should stop the
JAMS_MONITOR and JAMS_SCHEDULE processes on the
entire VAXcluster. Batch processing may continue during the
installation but, you will not have any history information on the jobs
which run while JAMS is stopped.
2.1.2 Backup JAMS
Before you start the upgrade, make sure that you have a valid backup of the JAMS data files and executables. Version 4.0 introduces a new format for some of the data files. If you are upgrading from Version 3.3 or earlier, the installation will convert your existing data files to the new format. If you need to revert to a previous version, you must recover the JAMS data files from a valid backup.
To backup all of the JAMS data files and executables, stop the JAMS_SCHEDULE process and use VMS BACKUP to backup the following files and directories:
2.1.3 Converting the JAMS Database
Version 4.0 introduced a new database structure. If you are upgrading
from a version of JAMS older than V4.0, the installation
procedure will try to convert your existing database to the V4.0
structure. When the conversion starts, the JAMS_MONITOR and
JAMS_SCHEDULE will be stopped on the entire VAXcluster. If someone is
using the JAMS_MASTER program when the installation attempts to convert
the database, the conversion will fail. If this happens, installation
will complete but the database will still have the old structure. If
anyone attempts to run the old software, they will receive the message:
%JAMS-F-OBSFILSTR, Obsolete file structures, please refer to... |
You can convert your JAMS database to the new format with the JAMS_CONVERT_DATABASE.COM command procedure which is in JAMS_COM. Issue the following command to update the JAMS database:
$ @JAMS_COM:JAMS_CONVERT_DATABASE.COM [Return] |
The command procedure will ask for the name of a disk drive which it
can use for scratch work space. The command procedure will issue
progress messages as it converts the database.
2.1.4 Template Libraries
The installation procedure will replace the JAMS_TEMPLATE.TLB
template text library. If you have made any customizations to this
library, you should save them before you install Version 4.0.
2.1.5 Execute JAMS_STARTUP after the upgrade
After you have successfully upgraded to V4.0 of JAMS, you must
execute the JAMS_STARTUP command procedure on all
nodes in the VMScluster.
2.2 Preparing to Install JAMS
JAMS is distributed on CD-ROM and via the Internet. There may
be more than one version of JAMS on a single CD-ROM, make sure
you are installing the correct version. The installation procedure is
identical for VAX and Alpha platforms.
2.2.1 Prerequisite Software
This version of JAMS requires OpenVMS/VAX version 6.2 or
higher or OpenVMS/AXP V6.2 or higher. If you want to use the
JAMS Motif interface, you must have DECwindows/Motif V1.2 or
higher installed.
2.2.2 Decompressing ZIP Files
If you downloaded JAMS over the Internet you downloaded a self-extracting zip archive. The file will be named either JAMSAXP040x.EXE or JAMSVAX040x.EXE where "x" is replaced by the patch level of the kit.
These self-extracting zip archives are OpenVMS executable images. You unpack them by simply running them. The archives contain the following files:
The
JAMS_DEMO_LICENSE.COM
is a command procedure used to register a demo license. If you have a
permanent license PAK you do not need to use this procedure.
2.2.3 Accessing the On-line Release Notes
JAMS provides on-line release notes. If you use OPTIONS N on the VMSINSTAL command line, the installation procedure will ask if you want to display or print these release notes. To obtain the release notes after installation, type or print the file SYS$HELP:JAMS040.RELEASE_NOTES.
The release notes are also located on the CD-ROM in text, Postscript,
Bookreader and HTML formats. The text and Postscript files are in the
[JAMS040.DOCUMENTATION] directory and the Bookreader version is in the
[DECW$BOOK] directory.
2.2.4 License Registration
Before you can install JAMS on a newly licensed node or cluster, you must first register and load a License Product Authorization Key (License PAK). The JAMS License PAK is registered and loaded using the standard VMS License Management Facility (LMF).
If you have a demonstration license PAK, you can register it with the JAMS_DEMO_LICENSE.COM command procedure. This command procedure is located on the CD-ROM in the [JAMS040] directory. Note that demonstration licenses have a product name of JAMS-DEMO and real licenses have a product name of JAMS. Example license management command shows a product name of JAMS which you must change to JAMS-DEMO if you are working with a demonstration license.
To register a license under VMS, first log into the system manager's account, SYSTEM. You then have a choice of two methods to register and load your License PAK:
$ LICENSE LOAD JAMS/PRODUCER=MVP |
The installation takes 10 to 20 minutes, depending on the type of media and your system configuration. Before installing JAMS, you must have the following privileges and resources:
The installation procedure will check for the required resources before it begins the installations. If you do not have enough of a given resource, the installation procedure will issue error messages which identify which resource you are short on and the installation will terminate.
To determine the number of free global pages on your system, type the following DCL command:
$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")[Return]
|
The number displayed is the total number of free global pages. If this number is less than 1,800 (3,600 for Alpha), you can increase the GBLPAGES system parameter by editing the file SYS$SYSTEM:MODPARAMS.DAT and invoking the SYS$UPDATE:AUTOGEN.COM command procedure. For more information on adjusting SYSGEN parameters and using AUTOGEN, please refer to the appropriate VMS documentation.
To determine the number of free global sections on your system, type the following DCL command:
$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")[Return]
|
The number displayed is the total number of free global sections. If
this number is less than 15, you can increase the GBLSECTIONS system
parameter by editing the file SYS$SYSTEM:MODPARAMS.DAT and invoking the
SYS$UPDATE:AUTOGEN.COM command procedure. For more information on
adjusting SYSGEN parameters and using AUTOGEN, please refer to the
appropriate VMS documentation.
2.2.6 Mounting the CD-ROM
If you are installing from the CD-ROM it should be mounted before you invoke VMSINSTAL. To mount the CD-ROM issue the command:
$ MOUNT dka400: JAMS |
In this example you must replace dka400: with the device name of your
CD-ROM drive.
2.2.7 Using VMSINSTAL
VMSINSTAL is a command procedure which is used to install software products onto the OpenVMS operating system. In step 2 of the installation procedure, described in the next section, you must invoke VMSINSTAL.
The format of the VMSINSTAL command is as follows:
$ @SYS$UPDATE:VMSINSTAL upivvv ddnn:[dir] [OPTIONS N][Return] |
Represents the unique product identifier, in this case either JAMSAXP or JAMSVAX.
Represents the version number of the product. Refer to the label on the JAMS distribution media to determine the version you will be installing. The complete product name for Alpha JAMS Version 4.0 would be JAMSAXP040.
Represents the device and directory where the distribution kits are located. If you are installing from CD-ROM, the distribution kits are located in the [JAMS040.KIT] directory. If you downloaded JAMS over the Internet, you should supply the device and directory were you unpacked the zip archives. DKA400:[JAMS040.KIT] is the device and directory used in the examples.
If this optional parameter is supplied, the installation procedure will ask if you want to display or print the release notes before performing the actual installation.
When you invoke VMSINSTAL, it checks the following:
If VMSINSTAL detects any user processes running on the system, you are asked whether you want to continue the installation. If you want to continue, type YES and press RETURN. If you want to stop the installation, press RETURN.
The JAMS installation does not update the DCL tables or the VMS help libraries. If this is a new installation of JAMS you can perform the installation while other users are logged on. |
This section contains excerpts from the installation procedure and provides explanatory text. Default answers appear in brackets throughout the installation procedure.
To abort the installation procedure at any time, press CTRL/Y. The installation procedure cleans up any files it has created and returns you to the DCL prompt.
Step 1: Log in to a privileged account and set your default device and directory to SYS$UPDATE.
$ @VMSINSTAL JAMSAXP040 DKA400:[JAMS040.KIT] [Return] |
Step 3: Answer standard VMSINSTAL questions.
VMSINSTAL will ask if you are satisfied with the backup of your system disk. If may also ask additional questions of you are not logged on as SYSTEM or it it detects other unusual circumstances.
Step 4: Provide device name for JAMS executables.
You will be asked which disk device should be used for the JAMS executables. You can install both VAX and AXP executables on the same device, JAMS will create different directories for them.
Step 5: Provide device name for JAMS data.
You will be asked which disk device should be used for the JAMS data files. You can store the data files on the same disk as the executables.
The JAMS data disk must be the same on all nodes in a VMScluster.
Step 6: Start JAMS when the installation is complete?
If you want to execute the JAMS startup procedure when the installation is complete, press Return; otherwise, enter NO and press Return.
You will be asked if you want to purge files which are replaced by this installation. If you want to purge replaced files, press Return; otherwise, enter NO and press Return.
You are asked if you want to run the installation verification procedure (IVP). If you want to run the JAMS IVP after the installation is complete, press Return; otherwise, enter NO and press Return.
Step 9: Read informational messages.
As the installation proceeds, you should read the informational messages and watch for problems.
JAMS puts all files in it's own directory tree with the exception of the following files:
SYS$STARTUP:JAMS_STARTUP.COM
VUE$LIBRARY:JAMS_PROFILE.VUE$DAT
VUE$LIBRARY:JAMS_VUE_STARTUP.COM
After successfully installing JAMS, you must perform the
following tasks.
2.4.1 Insert JAMS_STARTUP.COM into System start-up
You must execute the JAMS start-up procedure on every node which will be using JAMS. The JAMS start-up procedure should be executed before you start any batch queues.
To insure that the JAMS start-up procedure is executed every time the system re-boots, insert the following line into the system start-up procedure (SYS$MANAGER:SYSTARTUP_V5.COM):
$ @SYS$STARTUP:JAMS_STARTUP.COM |
Make sure you insert this line after the disk which contains the JAMS data files has been mounted and before you start any batch queues.
The JAMS start-up procedure could also be defined as a start
up file using the VMS SYSMAN utility.
2.4.2 Update the System wide LOGIN command file
Batch Jobs must register with the JAMS Monitor when they start execution. This is done by running JAMS_REGISTRAR.EXE. The JAMS Registrar will register batch jobs with the JAMS monitor. It does not do anything if the process which runs it is not a batch job.
The easiest way to make sure that all batch jobs are registered is to put the following line into your system-wide login command procedure.
$ 'f$trnlnm("JAMS_LOGIN")'
|
You should insert a line in your system shutdown procedure (SYSHUTDWN.COM) to stop the JAMS Monitor process. The line to be inserted is:
$ MCR JAMS_EXE:JAMS_MASTER.EXE STOP MONITOR |
This command will stop the JAMS Monitor process and, if the
Schedule process is also running on this node, it will also be stopped.
2.4.4 Initialize JAMS on all nodes
JAMS is fully initialized on the node on which the installation is performed. In order to initialize JAMS on other nodes in a VAXcluster, issue the following commands on every node on which JAMS is to execute:
$ LICENSE LOAD JAMS/PRODUCER=MVP $ @SYS$STARTUP:JAMS_STARTUP.COM |
JAMS has a batch job which is used to submit recurring Jobs. The first time you install JAMS, you must 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 re-installation of JAMS the JAMS_AUTOSUBMIT job
should already be pending in a batch queue.
2.4.6 Define JAMS DECnet Objects
If you plan 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.
2.5 Installing JAMS on a VAXcluster
If you installed JAMS on a VAXcluster, there may have been
other nodes in the cluster that were running during the installation.
If you do not want to re-boot these nodes after the installation, you
should execute the JAMS start-up procedure on each node which
will be using JAMS.
2.6 Customize your JAMS environment
JAMS has a number of options which need to be customized for
your sites environment. Take a few minutes to review these areas to be
sure that they meet your requirements.
2.6.1 Review JAMS Access Control
When you initially install JAMS, you need to be a member of
the System UIC Group to have the OpenVMS BYPASS privilege to select any
of the Maintenance menu options. This security is too restrictive for
most sites. You should use the Access Control menu option to relax
these security checks by specifying UIC and/or Rights Identifiers which
should be allowed to execute the various menu options.
2.7 Error Conditions
If the installation procedure fails for any reason, a message is displayed and the installation is not performed.
Try to determine what caused the installation to fail. If you can correct the problem, do so and then restart the installation.
If you cannot determine the cause of the problem, please contact technical support.
If you have questions about JAMS please feel free to call JAMS technical support at (866) 259-5267. Technical support is available around the clock, 24 hours a day, 7 days a week. The mailing address is:
| Previous | Next | Contents |
 | Copyright © 2000, MVP Systems, Inc. All rights reserved. |