2021. What an interesting year. With the world turned upside down by a pandemic that seemingly had its sights set on...
MultiBatch from Insider Technologies
“The Mainframe-Class NonStop Batch Scheduler”
Some of the benefits the UK Central Bank and OFI NonStop customers have realised:
- Exceed SLAs for site-swaps
- Fast batch recovery following a site-swap
- Run RTGS applications
- Reduce online-dealing batch by 6 hours per day (source available)
- Manage, process, service securities settlements
- Manage and monitor Atlas/GBS applications
- Run Guardian and OSS jobs within the same schedule
- Run OSS jobs, incorporating STDIN, STDOUT, STDERR (no TACL scripts)
For nearly 30 years, our customers have relied on MultiBatch to help improve their SLAs and batch scheduling run times.
All of our customers configure complex mainframe-class batch schedules, requiring reliability, flexibility and ease of use.
Some of the new features within MultiBatch version 9.5 include:
- CRONTAB scheduling
- Historical trend view of batch schedules
- A ridiculously easy approach to recover a batch schedule (e.g. during a site-swap):
- Recover the batch on new ‘live’ node, utilising the audited recovery file
- Dynamically change node names (if required, volume and subvolumes too).
- Batch schedule is now recovered
- During recovery, status of the original (failed) schedule is supplied
All batch and scheduling configurations are available via a single interface, easily navigable around the various screens and real-time status monitor facilities.
NO JCL MAINTANANCE
Having to maintain complex batch schedules via JCL scripts can be risky and prone to user error, e.g.:
MultiBatch does not require lengthy JCL (NBEXEC / TACL) maintenance.
All scheduling, dependencies, run time options are configured via the GUI and/or Pathway.
Inexperienced users can easily maintain the batch schedules.
MultiBatch arrives with an inbuilt security set, e.g. MBAT.OPS user for just viewing the configuration and status monitor screens, whereas an MBAT.CONFIG user is utilised to maintain one or more batch schedules.
If required, a user can run all of their MultiBatch jobs under the owner of the batch monitor process (BMON).
Alternatively, specific jobs can run under certain user ids, e.g. during a MultiBatch system coldload schedule, some Pathways may run as APPL.MANAGER, whereas TMF will start as 255,255.
Our customers utilise a control node in which to maintain their MultiBatch schedules ready for testing, trialling and if successful, migrating to production.
Alternative NonStop batch schedulers require some form of TACL maintenance to copy schedules between nodes.
MultiBatch simply extracts a batch schedule from one environment and inserts it into a target environment; no TACL changes, configuration changes needed.
Simple and effective migration, dynamically changing node name, volumes, subvolumes, parameters, defines, assigns, OSS file-descriptors and OSS environment variables.
REAL-TIME STATUS MONITORING
Within the GUI interface, a user can visually check where the batch schedule is up to. This is extremely important in large, complex batch schedules such as RTGS, Atlas/GBS, securities settlements.
A user can interrogate the cause of failure and with appropriate access rights, execute various command and control functions such as restart, hold, complete.
Provides an in-depth and real-time approach to batch status.
MultiBatch is supplied with an extensive list of fully tokenised EMS events that can be monitored via ViewPoint, EMSDIST, and our NonStop and Enterprise monitoring products, Reflex, Sentra.
+44 161 876 6606
Download the MultiBatch White Paper: