PXS
Production EXecution Scheduler
PXS is a market leader in the automation of
the running of VME batch work, used by a large number of ICL
customers.
- It is used by some of the world's largest users because
of its comprehensive facilities.
- It is used by some of the smallest because of its
simplicity.
- It is used by some of the most demanding because of its
support for advanced VME features.
What is PXS?
PXS is a VME software system which provides
facilities to define and describe batch work which can then be
executed automatically, in a precisely controlled manner.
The goal of PXS is that all planned and ad
hoc work can be designed by a suite designer, and run once or
many times without operator intervention.
PXS makes a Major Contribution to Quality
It improves the quality of service to the user and reduces the
development, implementation and running costs of applications.
In the Design and Definition Phase
- PXS enables the definition of work
schedules directly from system design documentation so
that the application requirements are fulfilled exactly.
- PXS makes it possible to reduce your
jobs to modules running a single application program so
that SCL is simple and error free.
- PXS provides a structure of suites,
jobs, parameters and conditions so that no SCL is
required to implement work dependencies or schedule the
work.
- PXS requires no change to existing
applications ; it also provides transition facilities.
In the Testing Phase
- PXS runs real work, test work or 'dummy'
work, in exactly the same way with no changes to the work
definitions or Job SCL. This enables thorough testing of
the application system design.
- PXS provides a screen based interface
for invoking work, setting parameters, monitoring and
controlling the running of work.
In the Job Control Phase
- PXS provides a screen based interface
for operations controllers or end users to invoke work
and set parameters.
- PXS enables parameters used by many jobs
to be specified once, thus reducing errors in job
submission.
In the Runtime Phase
- PXS provides a simple and natural
interface for operators to monitor and control work.
- PXS automatically schedules work exactly
according to the rules contained in the suite flow
charts.
- PXS optimises machine resources by
scheduling work as soon as all its dependencies have been
satisfied.
- PXS enables the control of concurrencies
and the use of resources to maximise throughput.
Other Features of PXS
- It enables the design and running of applications with
dependencies across a network of mainframes.
- It uses VME privacy facilities to ensure applications are
secure and the privacy/High Security strategy is not
compromised.
- It uses standard ICL interfaces in the ICL recommended
way to guarantee minimum risk, clear delineation of
responsibilities and long term protection of your
investment.
- It runs as a VME scheduler hook to ensure that it always
totally agrees with VME on the state of all work. This
also ensures that recovery from system or scheduler
failures is instant and automatic.
The Design Objectives of PXS
The architecture of PXS incorporates three
main goals:
- PXS should be simple and intuitive in
use. to this end it looks and feels like a simple
extension to VME, so that all its users (e.g.
applications designers, systems support, operations
support and operators) should find it easy and natural to
use.
- PXS complements rather than duplicates
VME's facilities and features, which are amongst the best
in the world.
- The production schedule must reflect the application
design. 95% of the decisions made in scheduling
production are made on the basis of dependency on other
work running, and on logical conditions defining when and
if work should be executed. It is because PXS
directly implements the design of the application that
people find it so natural and simple to use.