| Contents | Index | JAMS Home | Support |
| ||||
|
| Previous | Contents | Index |
This chapter provides an overview of the Job Access and Management
System, also known as JAMS.
1.1 Introduction
The Job Access and Management System (JAMS) is designed to automate and enhance the batch processing capabilities provided by the OpenVMS, Windows NT/2000, and Unix/Linux operating systems. JAMS provides those in charge of operations as well as the general end-user, with the ability to request, monitor and control the processing of batch jobs.
JAMS provides the control mechanisms which allow you to give end-users the ability to request batch processing and yet, you can still retain control of how, and when, the requested jobs are executed. In addition to allowing end-users to submit their own jobs, JAMS allows you to schedule jobs for unattended execution.
JAMS is scalable, tightly integrated with the operating system, customizable, and yet is ready to provide benefits right-out-of-the-box. You can use JAMS as is, or customize it to your needs without worry that future JAMS upgrades will displace the work you have done. Properly implemented, JAMS will both enhance and simplify your batch scheduling which increases your system's reliability and lowers your total cost of operations.
Visit our web site at http://JAMS.mvpsi.com/ for the latest information
regarding JAMS.
1.2 Capabilities of the Job Access and Management System
The Job Access and Management System was designed to enhance and control the entire life cycle of a batch job, from the initial end-user request for processing, to the scheduling of the job (or jobs) which need to be run, to monitoring the jobs for successful completion, to the distribution of the information produced by the jobs.
JAMS provides the following key benefits:
JAMS is designed to enable end-users to take some responsibility for their batch processing. JAMS provides a simple interface to batch job submission as well as functions which allow a user to display and monitor their batch jobs. The end-user is best able to determine when, or if, a job should be executed and what the parameter values for the job should be.
While end-users can take responsibility for directly submitting most of their jobs, the Data Center management still controls the execution and definition of the jobs. Data Center personnel define the jobs and attributes such as execution method, scheduling windows, dependencies, required resources, default parameter values, job execution priority etc. The job can be required to be submitted on hold, meaning that a Data Center Professional must release the job before it will actually run.
In addition to time or trigger based automatic batch job submission, JAMS provides five additional means of requesting or submitting a batch job:
These interfaces are used to submit ad hoc jobs, jobs which are not
regularly scheduled via scheduled times or triggers.
1.2.1.1 Menu based job submission
The menu based system provides a simple means to locate and submit a
batch job. The end-user is provided with a menu of jobs which they may
submit. The menu hierarchy and content can be customized to your
specific needs. Once the end-user selects a job, they may be presented
with a "fill in the blanks" type of video form which is used
to obtain values for the parameters which the job needs. These
parameters can be edited and verified before the job is
submitted. With the built-in security model, users can only submit
those jobs which they have clearance to submit. Users will also have
the ability to modify job output characteristics, such as the number of
copies of a report, or the print queue it should print on.
1.2.1.2 DECwindows/Motif based job submission
The DECwindows/Motif based system is similar to the menu based system
except that it is designed to run under the DECwindows/Motif graphical
user interface.
1.2.1.3 Command line interface
The command line interface is similar to the OpenVMS SUBMIT command. By using the JAMS SUBMIT command, users have access to the enhancements provided by JAMS including:
Windows 9x/NT/2000 is similar to both the DECwindows/Motif based system
and the menu based system. This interface is designed to run under the
Windows graphical user interface standard.
1.2.1.5 Callable interface
The callable interface allows you to integrate the Job Access and
Management System into your custom OpenVMS software. All of the
capabilities of the JAMS Submit sub-system are available with
the callable interface. By calling the appropriate JAMS
routine, you can present the end-user with a menu of batch jobs to
submit or submit a specific job. The callable interface is explained in
more detail in the JAMS Reference Manual.
1.2.2 Managing Batch Jobs
JAMS provides a high performance dynamic job monitoring and management system. On OpenVMS systems, JAMS even monitors those jobs which were not submitted by JAMS. The information is constantly updated and always up to date. The Monitor never scans the OpenVMS batch queues so performance is not negatively affected, no matter how many people are running the Monitor.
A properly authorized user can use the JAMS Monitor to manage jobs. A job may be rescheduled, aborted, held, released or restarted all from within the JAMS Monitor.
The JAMS Monitor has three interfaces:
One of the most basic functions of JAMS is to monitor and track the status of batch jobs. JAMS maintains a history of batch jobs, tracks the history for those jobs which were submitted by JAMS as well as those jobs submitted by other means (OpenVMS SUBMIT command etc.) This history information is available on-line and is updated immediately after the status of a job has changed.
JAMS also monitors jobs in order to resolve job
dependencies. Job dependencies insure that all prerequisite
processing has been completed before a job is released for execution.
1.2.4 Remote Access
JAMS provides the ability to access JAMS Servers on remote nodes. Once a person has connected to a remote node, they can submit jobs, monitor batch processing and search the JAMS history information.
You can connect to an unlimited number of nodes and it is very easy to
toggle between nodes. This capability makes it very easy to manage the
batch processing of an entire distributed organization from a single
point.
1.2.5 Recurring Jobs
Virtually every site has batch jobs which must be submitted on a regular basis. These recurring jobs can be automatically submitted by JAMS. There is virtually no limit to the number of ways to specify the date and time at which a recurring job should be scheduled to execute. You can also define event based schedules.
The Resource functionality within JAMS is
designed to limit the number of jobs running simultaneously which
require the same resources. Once resource requirements are defined for
your jobs you can rest assured that the workload on your servers will
be controlled.
1.2.5.1 Time Based Schedules
The specification of a scheduled time includes an English language date selection, a time of day and whether or not to run the job on non-work days.
JAMS capability for understanding English language representations of dates is quite extensive. JAMS can understand simple dates such as "MONDAY" or "DAILY" and complex constructs such as "FIRST WORKDAY OF FISCAL QUARTER".
These English date specifications are used to define a job's scheduled day and for establishing the default value for date parameters to jobs. For more information on this capability, refer to Chapter 10, Entering Generic Date Specifications.
When you Setup a recurring Job you must specify the value of any parameters which the Job requires. If a parameter is a date, you can specify an absolute date or a date which is relative to the date on which the job is submitted.
You have the option of enabling any user to define recurring jobs. An
end-user who wants a specific report every Monday morning can Setup
their request as a recurring job and the report will be ready for their
review every Monday morning.
1.2.5.2 Event Based Schedules
JAMS allows you to define Triggers which consist of a list of events and a list of actions. When all of the specified events occur, the list of actions is automatically performed. An event can be the successful or unsuccessful completion of a specific Job. An event can also be a boolean expression based upon the value of a JAMS Variable.
A Trigger's list of actions is a list of Jobs to be submitted when the
Trigger is fired. For each action Job you can specify a schedule date
and time for the Job to start. For example, a Trigger could fire at
3:00 pm Tuesday which schedules a Job to run at 2:00 am Sunday.
1.2.6 Maintaining Schedules
One of the most important aspects of managing a data center is scheduling the workload of your computer systems. While the recurring job capabilities of the Job Access and Management System can help maintain your schedule, a recurring job is not always practical.
Batch processing which is run only on request can still be given a scheduled date and time for execution. When a user requests a job, JAMS will specify the scheduled time when it submits the job. A user can override this scheduled time when they request the job.
Keep in mind that if you elect to use JAMS Resources, jobs may not immediately run due to the defined Resource constraints.
Scheduled times are also used to produce reports which show the
expected workload for any given day.
1.2.7 Control of Printed Reports
When a batch job is defined in JAMS you can specify the
reports which the job produces along with the printer queue they should
be printed on and the number of copies and form to be printed on. This
lets the Operations group control the printing of reports without
changing any DCL command files. When a job is requested, a user is able
to override the default print specifications for each report.
This capability requires that you use the command file template expansion option when setting up jobs. Command file template expansion is explained in the JAMS Reference Manual. |
| Previous | Next | Contents | Index |
 | Copyright © 2000, MVP Systems, Inc. All rights reserved. |