Home
HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 9.5 Fix Pack 6.
User's Guide and Reference
Managing internetwork dependencies
Internetwork dependencies in a mixed environment

HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 9.5 Fix Pack 6.
- Fix Pack readmes
  For the latest information about a Fix Pack, see the appropriate Readme File.
- Planning and Installation
- User's Guide and Reference
  - HCL Workload Automation
  - Understanding basic processes and commands
  - Configuring the job environment
  - Managing the production cycle
  - Using workload service assurance
    Workload service assurance is an optional feature that provides the means to flag jobs as mission critical for your business and to ensure that they are processed in a timely manner. Using this function benefits your scheduling operations personnel by enhancing their ability to meet defined service levels.
  - Customizing your workload using variable tables
    This chapter introduces the concept of variable tables to group global parameters, from now on called variables, to customize your workload.
  - Condition-based workload automation
  - Running event-driven workload automation
  - Defining objects in the database
  - Managing objects in the database - composer
  - Managing workload applications
    Workload applications can be created and then exported so that they can be shared with other HCL Workload Automation environments. In the new environment, the workload application can be subsequently updated, replaced, or deleted.
  - Managing objects in the plan - conman
  - Monitoring with Prometheus
    Access metrics that provide insight into the state, health, and performance of your workload environment and infrastructure.
  - Predicting job duration
  - Extending HCL Workload Automation capabilities
    You can extend HCL Workload Automation capabilities by integrating with IBM and third-party products, such as IBM Sterling Connect:Direct or MS SQL. This integration allows you to easily start HCL Workload Automation jobs on external products, while using HCL Workload Automation scheduling capabilities. HCL Workload Automation also provides jobs that perform everyday operations, such as file transfer and web services, and utility jobs that automate and simplify operations such as the centralized agent update.
  - Managing dynamic scheduling
    This section explains how you can manage dynamic scheduling capabilities in your environment to schedule both existing HCL Workload Automation jobs and job types with advanced options, both those supplied with the product and the additional types implemented through the custom plug-ins.
  - Using utility commands
  - Using utility commands in the dynamic environment
  - Getting reports and statistics
  - Managing time zones
  - Defining access methods for agents
  - Managing internetwork dependencies
  - Applying conditional branching logic
    With HCL Workload Automation you can define jobs to run when and as often as necessary. Sometimes some jobs might have to wait for other jobs to finish successfully before they start. Add even more flexibility to your job flows by choosing which job to run depending on the result of the job status or output of a previous job. Whenever you have conditions that specify whether or not a segment of your job flow should run, then that is a conditional dependency.
  - Defining and managing cross dependencies
  - Managing an IBM i dynamic environment
  - Event-driven workload automation event and action definitions
  - Job Submission Description Language schema reference
    This reference section specifies the semantics and structure of the Job Submission Description Language (JSDL) that apply specifically for use with dynamic workload broker. The JSDL schema is used to describe the job requirements for submission to resources. dynamic workload broker analyzes the IT environment and assigns the best available resource to run the job, based on the requirements you specify.
  - Quick reference for commands
  - Accessibility
- Administration Guide
- Scheduling with the Agent for z/OS
- Database Views
- Integrating
- High Availability Cluster Environment
- Driving HCL Workload Automation
- Extending HCL Workload Automation

Internetwork dependencies in a mixed environment

Internetwork dependencies in a mixed environment shows the supported configuration for internetwork dependencies defined in a mixed version 8.3 environment. The key to the table is as follows:

Net_A: The network agent defined in the local network.
Wks_B: The workstation in the remote network that the network agent Net_A is connected to. Wks_B is the workstation that identifies and checks the state of the remote job or job stream specified in the internetwork dependency.
Sym_A: The Symphony file processed in the local network.
Sym_B: The Symphony file processed in the remote network.
back-level: Version 8.1, 8.2, or 8.2.1

Table 1. Internetwork dependencies in a mixed environment
	Net_A back-level Sym_A back-level	Net_A 8.3 Sym_A back-level	Net_A back-level Sym_A 8.3	Net_A 8.3 Sym_A 8.3
Wks_B back-level Sym_B back-level	This is not a mixed version 8.3 environment.	`Net_A` sends the information to `Wks_B` as if it had the same version as `Wks_B`.	`Net_A` sends the information to `Wks_B` in 8.1, 8.2, or 8.2.1 format. The use of the schedtime keyword in the job definition is not supported.	`Net_A` sends the information to `Wks_B` as if it had the same version as `Wks_B`. If defined, the schedtime keyword in the job definition is automatically removed by `Net_A`.
Wks_B 8.3 Sym_B back-level	`Wks_B` works as if it had the same version as `Net_A`.	`Net_A` sends the information to `Wks_B`. If defined, the schedtime keyword in the job definition is automatically removed by `Wks_B`.	`Net_A` sends the information to `Wks_B`. If defined, the schedtime keyword in the job definition is automatically removed by `Wks_B`.	`Net_A` sends the information to `Wks_B`. If defined, the schedtime keyword in the job definition is automatically removed by `Wks_B`.
Wks_B back-level Sym_B 8.3	Not supported.	Not supported.	Not supported.	Not supported.
Wks_B 8.3 Sym_B 8.3	Not supported.	Not supported.	`Net_A` sends the information to `Wks_B`. If defined, the schedtime keyword is parsed by `Wks_B`.	This is a version 8.3 environment.

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.