The different types of workload scheduling you can implement in
your z-centric end-to-end environment:
Static scheduling
The HCL Workload Automation Agents are
installed on the distributed systems and are connected to the z/OS® system through the HCL Workload Automation for Z controller.
Static scheduling including job types with advanced options
Figure 1. Static end-to-end
environment with Java™ run time
installed in which you can run job types with advanced options The HCL Workload Automation Agents are
installed on the distributed systems with the Java™ run time, and are connected to the z/OS® system through the HCL Workload Automation for Z controller. Static end-to-end
environment with Java run time
installed in which you can run job types with advanced options shows a static end-to-end
environment in which HCL Workload Automation Agents:
Without the Java™ run time
installed, can run existing job types
With the Java™ run time installed,
can run both existing jobs and job types with advanced options
Dynamic scheduling
The HCL Workload Automation Agents are
installed on the distributed systems with dynamic capabilities, and
are connected to the dynamic domain manager.
The dynamic domain manager is
connected to the z/OS® system
through the HCL Workload Automation for Z controller.
Dynamic scheduling including job types with advanced options
Figure 2. Dynamic
end-to-end environment to run also job types with advanced options. The HCL Workload Automation Agents are
installed on the distributed systems with dynamic capabilities and
the Java™ run time, and are connected
to the dynamic domain manager.
The dynamic domain manager is
connected to the z/OS® system
through the HCL Workload Automation for Z controller. Dynamic
end-to-end environment to run also job types with advanced options. shows a dynamic end-to-end
environment in which HCL Workload Automation Agents:
Without the Java™ run time
installed, can run existing job types
With the Java™ run time installed,
can run both existing jobs and job types with advanced options
By using the z-centric end-to-end scheduling environment,
you schedule and control both static and dynamic workload from the
mainframe to distributed systems with a low cost of ownership. HCL Workload Automation for Z acts
as a single point of control, providing you with all the mainframe
capabilities to manage distributed workload.
HCL Workload Automation Agents can
be installed on the UNIX™, IBM® i, or Windows™ workstations where you run jobs scheduled
from HCL Workload Automation for Z.
After installation, you associate each agent to an HCL Workload Automation for Z workstation
definition, so that it can be used as a target for HCL Workload Automation for Z jobs.
The communication between the HCL Workload Automation Agent and HCL Workload Automation for Z controller
is direct, through the HTTP or HTTPS protocol. If the connection is
interrupted, the HTTP client retries to establish it until it is successful.
Process flow shows the process flow to
submit and track jobs on HCL Workload Automation Agent workstations.
Figure 3. Process flow
Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.