|
PRODUCT NAME: DECscheduler for VMS, Version 1.0 SPD: 32.19.00
DESCRIPTION:
DECscheduler for VMS is a distributed scheduling product that automates the
execution of repetitive production jobs on VAX/VMS Systems. A "job" is a
DCL command file or a VMS command string. DECscheduler for VMS separates
information which specifies how jobs should be run from the jobs themselves.
It automatically takes care of the job re-scheduling calculation, completion
notification, etc. A scheduled job can run when constraints on its execution
are met. There are two types of constraints: The time must be LATER than the
job's scheduled time and all of the jobs that the job "depends on" must have
completed SUCCESSFULLY later than the last time the job completed. A job can
depend on up to 16 other jobs, which can be within a VAXcluster or on remote
nodes of a wide area DECnet network.
Job database information can be easily accessed through DCL commands. Most
commands can also work remotely over the network, allowing centralized
control of distributed applications.
DECscheduler for VMS has full VAXcluster failover capabilities. Jobs can be
divided into steps. Interrupted jobs can be automatically restarted at the
current step on another node in the VAXcluster or restricted to a single
node. An installation modifiable load-balancing procedure can be invoked at
execution time to select the VAXcluster node for job execution.
The product includes an event logging/reporting facility which can be used
to produce job reports.
FEATURES
o Executes repetitive jobs without the need for command files.
o Jobs can be synchronized with up to 16 other jobs within the network. The
user interface shows which job dependencies have been satisfied and which
which are still being waited for.
o Notifies the user of job termination via VAXmail or terminal messages.
o Provides date /time (calendar and fiscal) and node /cluster run specific-
ations for jobs. Jobs can be run automatically at regular intervals or
restricted to run on certain days of the week.
o Provides a job recovery/re-start mechanism. Interrupted jobs can be
automatically restarted at the current step on another node in the
VAXcluster (the user interface displays the step currently executing).
o Capability to schedule jobs remotely via the LAN or WAN. Most commands
work remotely over the network.
o Sets time limits for jobs. Notifies operator when a job has exceeded
the designated execution time. It can also notify the operator if a
job failed to start by a deadline after the scheduled time.
o Allows for cluster load-balancing.
o Commands can operate on multiple jobs. Jobs may be specified by "Group"
and "Type" as well as by name. Jobname, Group and Type are strings up
to 40 characters in length. The user interface supports the use of
wildcards. For example, the DCL command
$ SCHED RUN A*/GROUP=%O*/TYPE=*BACK/USER=*S*/CONFIRM
would prompt for the running of all jobs in the local VAXcluster with
names that begin with the letter "A", a type that ends in "BACK", a
group with "O" in the second character position, owned by users with an
"S" in their VMS username.
o "Prefunctions" and "postfunctions" can be automatically run before and
after the job.
o Ability to specify parameters or override job defaults (node, output file)
on the run command.
o Three levels of job status display - from a one line summary to full display
o Includes event logging and job reporting facility
Restrictions
A job can't have different sets of dependencies depending upon the day of week.
The work-around is to duplicate the job and its dependencies using the
$ SCHED COPY command.
Batch job procedures themselves may need to be modified slightly. Logic
relating to job re-scheduling and operator notification can be removed.
The mode of processes run by DECscheduler for VMS is "OTHER". DECscheduler
for VMS considers the completion status of the last DCL command in a
command file to be the completion status of the job. Sometimes jobs have
error handling logic which is invoked upon error and which may have to be
changed to exit the proper status. A job's exit status determines whether
jobs that "depend" on it will be run.
Day restrictions for cyclic jobs with dependencies sometimes don't
produce the desired behavior when production spans day boundaries. Usually
these problems can be gotten around by modifying the time calculation
algorithm for the specific jobs using the /USE_NEXT qualifier.
Documentation:
The DECscheduler Documentation Set consists of:
o Installation Guide
o Users Guide
HARDWARE REQUIREMENTS:
VAX, MicroVAX, VAXstation, or VAXserver configuration as specified in the
System Support Addendum (SSA 32.19.00-x).
SOFTWARE REQUIREMENTS:
Refer to the System Support Addendum for availability and required versions
of prerequisite/optional software (SSA 32.10.00-x).
DECnet-VAX (end-node)
ORDERING INFORMATION
DECscheduler for VMS
Software Licenses: QL-YLLA*-**
Software Media: QA-YLLA*-**
Software Documentation: QA-YLLAA-GZ
Software Product Services: QT-YLLA*-**
SOFTWARE LICENSING
Clusterwide License
This software is furnished under the licensing provisions of DIGITAL's
Standard Terms and Conditions. For more information about DIGITAL's
licensing terms and policies, contact your local DIGITAL office.
LICENSE MANAGEMENT FACILITY SUPPORT
The DECscheduler for VMS layered products support the VMS License Management
Facility.
License units for this product are allocated on a CPU-capacity basis.
For more information on the License Management Facility, refer to the VMS
Operating System Software Product Description (SPD 25.01.xx) or the VMS
Operating System documentation set.
For more information about DIGITAL's licensing terms and policies,
contact your local DIGITAL office.
SOFTWARE PRODUCT SERVICES
A variety of service options are available from DIGITAL. For more
information contact your local DIGITAL office.
SOFTWARE WARRANTY
Warranty for this software product is provided by DIGITAL with the
purchase of a license for the product as defined in the Software Warranty
Addendum of this SPD.
February 1989
AE-PBJ7A-TE
PRODUCT NAME: DECscheduler for VMS, Version 1.0 SSA: 32.19.00
HARDWARE REQUIREMENTS:
These are the current production processors supported by VMS Operating
System.
VAX :
VAX FT3000
VAX 6000 Model 200 Series, VAX 6000 Model 300 Series, VAX 6000 Model 400 Series
VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550, VAX 8600,
VAX 8650, VAX 8700, VAX 8800, VAX 8810, VAX 8820, VAX 8830, VAX 8840, VAX 8842,
VAX 8974, VAX 8978
VAX-11/730, VAX-11/750, VAX-11/780, VAX-11/785
MicroVAX :
MicroVAX II, MicroVAX 2000, MicroVAX 3100, MicroVAX 3300, MicroVAX 3400,
MicroVAX 3500, MicroVAX 3600, MicroVAX 3800, MicroVAX 3900
VAXstation :
VAXstation II, VAXstation 2000, VAXstation 3100 Series, VAXstation 3200,
VAXstation 3500, VAXstation 3520, VAXstation 3540
VAXserver :
VAXserver 3100, VAXserver 3300, VAXserver 3400, VAXserver 3500, VAXserver 3600,
VAXserver 3602, VAXserver 3800, VAXserver 3900, VAXserver 6000-210,
VAXserver 6000-310, VAXserver 6000-410, VAXserver 6000-420
"Processors Not Supported" :
MicroVAX I, VAXstation I, VAX-11/725, VAX-11/782, VAXstation 8000
"Processor Restriction":
A TK50 Tape Drive is required for Standalone MicroVAX 2000 and VAXstation
Systems.
Other Hardware Requirements
As required to support DECnet.
Block Space Requirements (Block Cluster Size = 1):
Disk space required for installation: 5,000 blocks
(2.56M bytes)
Disk space required for use of system disk
(permanent): 4,000 blocks*
(2.05M bytes)
*Note:Will grow depending on amount of audit trail information kept
CLUSTER ENVIRONMENT
This layered product is fully supported when installed on any valid and
licensed VAXcluster* configuration without restrictions. The HARDWARE
REQUIREMENTS sections of this product's Software Product Description and
System Support Addendum detail any special hardware required by this product.
* V5.n VAXcluster configurations are fully described in the VAXcluster
Software Product Description (29.78.xx) and include CI, Ethernet, and
Mixed Interconnect configurations.
SOFTWARE REQUIREMENTS
DECscheduler for VMS Software is supported on VMS Operating System V5.0 - V5.3
Layered Products
DECnet-VAX V5.0 - V5.4
VMS Tailoring
The following VMS classes are required for full functionality of this
layered product:
^ VMS Required Saveset
^ Network Support
^ Programming Support
^ System Programming Support
^ Utilities
For more information on VMS classes and tailoring, refer to the VMS
Operating System Software Product Description (SPD 25.01.xx).
GROWTH CONSIDERATIONS
The minimum hardware/software requirements for any future version of this
product may be different from the requirements for the current version.
DISTRIBUTION MEDIA
Tape: 9-track 1600 BPI Magtape (PE), TK50 Streaming Tape,
This product is also available as part of the VMS Consolidated Software
Distribution on CDROM in the near future.
The above information is valid at time of release. Please contact your
local DIGITAL office for the most up-to-date information.
February 1990
AE-PBJ8A-TE
|