SCHEDULING
JMS/3000 is a sophisticated, yet easy-to-use software tool that lets you completely control the batch environment on the HP3000. It manages all batch jobs - both submitted and streamed.

You can modify schedules at any time and jobs will be automatically rescheduled according to your changes.

• No scheduling definition language to learn.

Scheduling repeat options: daily, select days of the week, select day of the month, every n day, monthly, end-of-month, +-offsets of select dates, fiscal calendars, holidays, workday of the month, workdays, daily time array[10], every n hours or every n minutes. For jobs that execute n minutes or hours, From and To times can be defined. Exception dates can also be assigned for when the job must cycle and not execute.

Retrieval of user's jcl each cycle to incorporate any new changes.

Holiday control for releasing or cycling of jobs. There is an option to force the jobs to execute prior to or after the holiday, but then return back to their normal schedule.

Schedule displayed in order of job execution. Numerous display options are available.

At any time, a job may be forced to execute without changing its schedule or a job may be released ahead of its normal scheduled time.

Straight line job dependency control can be assigned for jobs to enforce job sequencing. Jobs can also be added to completion lists to link between different job sequences.

Job descriptions may be assigned and displayed. Operator instructions may be assigned to each scheduled job and be displayed on request or on the optional pre-production run sheet.

Date parameters can be embedded within the user's jcl which will be replaced when the job is released from the schedule queue or added to the JMS job queue.

A recovery job may be assigned to execute if a scheduled job aborts.

Jobs can be automatically aborted if they exceed their assigned maximum elapsed time.

Scheduling information can be modified without deleting the job and re-adding.

The user's jcl (JMS's copy) can be displayed online with search capability.

Search capability to allow searching scheduled jobs for a jcl character string match.

JMS and MPE commands may be scheduled in the same manner as scheduling jobs.

The daily schedule may be moved up or back by changing the value of the JMS schedule clock.

Pre-production reports are available.

Do not need embedded MPE passwords within the job. JMS will insert or replace the passwords at execution time. Security is checked when the job is added to the JMS system.

The schedule cycle for a job can be suspended for up to 99 cycles. It may be resumed at any time.

Scheduled job can be moved to a background holding area so they will not execute but can be displayed. At any time they can be moved back to the foreground and their schedule will be automatically adjusted to the current date and time.

Average elapsed time history is maintained for the last 20 executions of the job and may be added to the show schedule display. This history can be used to delay jobs from being released if their average time added to the current clock time would allow the job to execute past the assigned system backup starting time.

A maintenance link can be assigned to a group of jobs to allow a single command to be executed for all jobs.

JOB INITIATING
Automatically runs multiple jobstreams concurrently with full job and schedule dependency control.

Total flexibility in altering the jobs status within the JMS job queue. The job may be moved within the queue by altering the JMS job priority, inpri, or subpri values.

Ad hoc jobs may be added to the JMS job queue with or without a scheduling date. Easy to use udc commands are available to add jobs.

Jobs that were streamed to MPE may be trapped and added to the JMS job queue to be controlled in the same manner as JMS submitted jobs. Their stdin spoolfile can be copied to an ascii file for scanning and recovery.

Restriction checking may be applied to control the releasing of jobs. Restriction types are file; program; udc; logon; queue; ldev; category; disc; jobname; and combinations. File checking can be enhanced to check for exclusive access, empty or not empty, or write access only. With logon restrictions activated, the system manager can control the number of jobs that a particular user can execute at the same time.

Independent restriction queues are available to group production queues thus controlling the overall number of jobs that can execute at the same time for a group of users.

Job aborts will be flagged and their stdlist spoolfile copied for display. If the job belongs to a production queue, the queue will be locked so dependent jobs can not execute. The aborted job can be rerun with the same jcl or with a revised temporary jcl file.

The MPE jobs that were trapped and released to execute can have their stdlist spoolfile checked for aborted conditions. If found to be aborted and assigned to a production queue, the queue can be locked.

Users can be notified if the job aborts or an optional notice when the job completes.

ONcondition file processing for JMS commands is available when the job is introduced, begins execution, completes, and or aborts. This allows flexibility in controlling what happens for each logical step.

Job card macro replacement is available for logon user , account, and group. The job card logon will be altered to match the user's logon.

The MPE executing priority level of the job may be altered.

The job's stdlist spoolfile options SPSAVE, PRIVATE, and DELETE may be altered.

Job history logging is recorded and available for online inquiry.

Executing jobs may be aborted, suspended and resumed.

A suspended job can automatically be resumed by another executing job when it completes.

The current executing job step may be displayed.

The stdlist spoolfile may be displayed while the job is executing.

MISCELLANEOUS
Define your own parameters and commands. Date parameters can have date files assigned which will automatically update the date when the old date expires. Defined commands can have replacement parameters for execution.

Maintain your own holiday tables. Up to 10 different holidays tables are allowed. The number of holidays within a table is only limited by the capacity of the data set.

JMS user security access levels and capabilities can be assigned to a logon. The level of capability controls which commands the user can execute.

Online inquiry into the history logfiles by date; jobname; MPE job number; JMS job number; JMS reference number; last x hours; account; weekend; user; etc.

Networking capability is available for peer-to-peer processing. JMS can submit a job from any cpu to any other cpu on the network with full inter-cpu job dependency. Individual cpu control is maintained for certain controls, such as job fence. MPE JMS can schedule jobs to be passed to JMS Unix.

The production queues can be locked by the JMS manager to suspend job processing.

Recover capability consists of many options to allow easy and complete recovery from down times. The updating of system date parameters can be delayed until all jobs for a previous day can be released or cycled.

Different override tables can be maintained. These tables are used to assign JMS defaults when a job is introduced to the JMS system.

Numerous system configuration and tuner options are available to tune the system to your specific needs.

Multiple copies of JMS can run on the same cpu. Designed for customers who were downsizing their cpus to one and wish to keep job scheduling separate.

Programmatic interface procedures are available to link into a user's program.

STREAMX compatible
A Program Dispatcher Subsystem is available with the JMS System. It is a batch job that will create and activate programs when needed. Some of features are:

•   Multiple dispatchers (batch jobs) that will create and activate programs.
•   Executes multiple standalone programs one at a time, or concurrently.
•   Allows up to 25 programs per dispatcher.
•   Requires a message to be sent to the dispatcher to execute a requested program.
•   Message may include parm value, info parameter, stdin filename, and stdlist filename.
•   Available programmatic message submission.
•   Dispatcher scheduling (day of week and time of day) plus holidays.

A Backup Manager System is available with the JMS System. This system will allow the MPE System Manager to abort sessions and jobs prior to the startup of the normal night's backup. Some options are:

•   Define jobs or sessions that can't be aborted.
•   Define logical devices that can't be aborted.
•   Optional Callback/3000 phone directory for notification in case of failure.
•   MPE commands (WARN, LIMIT, JOBFENCE, etc.)
•   Check for reply pending.
•   Check for tape mounted and ready.
•   Kill Networking ghost sessions
•   Logoff sessions and jobs.
•   Start backup.
•   Auto reply for tape mount.

CONVERSION FROM MAESTRO
A conversion package is available to convert the Tivoli IBM Maestro scheduling product to JMS, thus greatly reducing your annual maintenance costs and making the conversion process very easy.

Join ORBiTs mailing list today to be kept up to date with product news and technical issues.