JAMS Release Notes
Contents JAMS Home Support

JAMS V4.2 Release Notes
Previous Contents

Chapter 1
General User Release Notes

1.1 Contact Information

JAMS support questions should be directed to:

MVP Systems, Inc.
2700 E. Main St.
Suite 108
Columbus, OH 434209
Tel: (614) 238-0313
Fax: (614) 238-0850
E-Mail: Support@JAMSSupport.com

JAMS Support is available 24 hours a day, 7 days a week by calling (866) 259-JAMS (5267).

1.2 V4.0 Upgrade Notes

1.2.1 Backup your current JAMS Database

JAMS V4.0 introduced a new structure for many of the data files. If you are upgrading to JAMS V4.2 from V3.3 or older, the database will have to be converted. The installation procedure will automatically convert your existing data files to the new structure.

Caution
Make sure that you backup your existing JAMS data files before installing V4.2. If the installation or database conversion fails you may need to recover your current JAMS database from backup.

1.2.2 Make sure the JAMS_LOGIN command is executed

Your system-wide login command procedure should contain the line: 


    $ 'f$trnlnm("JAMS_LOGIN")'

This line notifies JAMS that a job is starting. Since JAMS can now run jobs as detached processes in addition to batch, you should make sure that this line is executed for all process modes.

1.3 OpenVMS V6.2 Limitations

JAMS V4.x requires OpenVMS V6.2 or higher however, there is a limitation when running OpenVMS V6.2. JAMS now supports running jobs as detached processes but, when running under OpenVMS V6.2 all detached processes will execute on the same node as the JAMS_SCHEDULE process. On OpenVMS V7.0 or higher JAMS can create detached processes on any node in a VMScluster.

1.4 Enhancements in V4.2

1.4.1 Support for new .NET based Client

JAMS V4.2 includes support for our new .NET based Windows client.

1.4.2 Record and play interactive sessions

JAMS V4.2 introduces a new execution method that can execute jobs that must run in an interactive environment. This includes the new RECORD command that can record an interactive session for later playback as a batch job.

1.5 After Installation

You may need to perform the following tasks after installing JAMS.

1.5.1 Defining the PLAY Execution Method

If you upgraded to V4.2 from an older version of JAMS, you must define the new "PLAY" Execution Method. Enter the following command do do this: 


    $ MCR JAMS_EXE:JAMS_MASTER @JAMS_DATA:JAMS_NEW_DEFS.JDF

1.5.2 Convert the SYS.DAT File

If you upgraded to V4.2 from JAMS V4.0 or higher, you must convert the SYS.DAT file if you want to use the new JAMS Windows Client. Enter the following commands do do this: 


    $ SET DEFAULT JAMS_DATA: 
    $ MCR JAMS_EXE:JAMS_MASTER STOP SCHEDULE 
    $ CONVERT/FDL=SYS.FDL SYS.DAT SYS.DAT 
    $ MCR JAMS_EXE:JAMS_MASTER START SCHEDULE

Converting the SYS.DAT file adds a secondary key to the file. This file can still be used by JAMS V4.0 and V4.1 in case you need to revert to an older version.

Previous Next Contents
JAMS Copyright © 2003, MVP Systems, Inc. All rights reserved.