HCL Workload Automation for Z
Welcome to the HCL Workload Automation for Z documentation, where you can find information about how to install, maintain, and use the product.
- Program Directory
- Dynamic Workload Console Readmes
  For the latest information about a Dynamic Workload Console fix pack, see the appropriate Readme File.
- Planning and Installation
- Customization and Tuning
- Managing the Workload
  You can plan when and how your workload runs and manage it as part of a plan.
- Scheduling End-to-end with z-centric Capabilities
  - About this publication
  - Configuring
    - Overview
    - Configuring the agent
      - Configuring proxy properties [ITA_Env]
      - Configuring log message properties [JobManager.Logging.cclog]
      - Configuring trace properties when the agent is stopped [JobManager.Logging.cclog]
        How to configure the trace properties when the agent is stopped.
      - Trace configuration for the agent
        Use the twstrace command to set the trace on the agent when it is running.
      - Configuring common launchers properties [Launchers]
      - Configuring properties of the native job launcher [NativeJobLauncher]
      - Configuring properties of the Java™ job launcher [JavaJobLauncher]
      - Configuring properties of the Resource advisor agent [ResourceAdvisorAgent]
      - Configuring properties of the System scanner [SystemScanner]
      - Configuring properties of event-driven workload automation [EventDrivenWorkload]
      - Regular agent maintenance
        Regular maintenance refers to the mechanisms that are used on your dynamic workstation agents to free up storage space and improve performance.
    - Configuring Z controller
      This section describes the configuration steps required on the Z controller.
    - License computation model
  - Customizing the HTTP connections
    The communication between the HCL Workload Automation Agents and the HCL Workload Automation for Z controller is direct, through the HTTP or HTTPS protocol.
  - Defining user IDs and passwords with the USRREC statement
    Use the USRREC initialization statement to define the passwords for the users who need to schedule jobs to run on Windows™ workstations. You do not need to do this if you run native job types on non-Windows workstations.
  - Defining variables and passwords for local resolution
  - Defining and managing HCL Workload Automation Agent workstations in the database
    After defining the destinations of your HCL Workload Automation Agents, you need to define the HCL Workload Automation Agents as HCL Workload Automation for Z computer automatic workstations.
  - Defining and managing dynamic workstations
    When you add dynamic capabilities to your environment, you can schedule your workload dynamically.
  - Setting the security features
  - Defining and managing jobs
  - Administering IBM i dynamic environment
    On overview on how to administer the HCL Workload Automation IBM i dynamic environment.
  - Monitoring and recovering jobs
  - Running a script when a job completes
  - Viewing the job logs from the host
    An overview on how to view or retrieve the job logs issued in the z-centric environment and how to attach a header with job run information on top of each log.
  - Troubleshooting
    Troubleshooting agent problems
  - Configuring to schedule J2EE jobs
  - Security order of precedence used for the execution of J2EE tasks
  - Configure to schedule job types with advanced options
  - Managing return codes
  - Collecting job metrics
- Quick Reference
- Diagnosis Guide and Reference
- Workload Automation Programming Language for z/OS User's Guide and Reference
- Driving HCL Workload Automation for Z

Configuring properties of event-driven workload automation [EventDrivenWorkload]

About this task

In the JobManager.ini file, the section containing the properties of event-driven workload automation is named:

[EventDrivenWorkload]

Important: Do not modify the values of these properties, however, you can consult them for troubleshooting purposes.

The following properties are contained in this section:

EventProcessorHostname: The host name where the event processor is located.
ThisWorkstation: The name of the agent workstation where the JobManager.ini file, containing these properties, is located.
EventProcessorEifSslPort: The Event Integration Facility (EIF) port number where the event processing server receives events when it is SSL-protected.
EventProcessorEifPort: The EIF port number where the event processing server receives events.
EdwaDesiredStatusRunning: To enable event-driven workload automation set to true, otherwise, false. The default value is true.
CRC: The current cyclic redundancy check (CRC) of the event rules of this workstation as reported by the event processor.
DeployedCRC: The CRC of the event rules already deployed.
EventProcessorWorkstation: The name of the workstation on which the event processor is located.
EventProcessorPort: The port number used to contact the event processor.
EventProcessorContext: The context part of the unified resource identifier (URI) of the event processor.
EventProcessorProtocol: The protocol used to contact the event processor. Valid values: http, https. The default value is https.

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.