Home
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.
Scheduling End-to-end with z-centric Capabilities
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.

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
  - 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.
    - Customizing the job log header
      A sample job log header template is downloaded on HCL Workload Automation for Z at installation time. You can customize it to fit it to your preferences.
    - Collecting job logs with Output collector
      An overview on the mechanism that automatically retrieves the logs of jobs and dynamic jobs run on HCL Workload Automation Agents and copies them to the JES spool so that they can be processed by an external output management product.
  - 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

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.

There are two ways of retrieving the job logs:

You can manually request to browse the log of a specific job (on demand) or have automatically displayed the logs of jobs that ended in error. To browse the log you can use any of the available user interfaces (ISPF dialogs, Dynamic Workload Console, or programing interfaces).
To specify the job log retrieval policy (on demand, or automatic for ended-in-error), define the JOBLOGRETRIEVAL keyword in the HTTPOPTS initialization statement. See Customization and Tuning.
You can activate the Output collector started task to have the logs of all jobs, independently of their outcome, sent to the JES spool to be picked up by an external output management product.

On all the job logs originated from the z-centric environment you can customize HCL Workload Automation for Z so that a header is added automatically at the top of the job log with the information necessary to classify the output (occurrence name, occurrence IA, job name, workstation name, operation number, start time, end time) and information about the run (process ID, return code, duration, status, hostname).

Remember: to have the job log header mechanism functioning for workload run on dynamic agents, the dynamic agents must be running at least version 8.6.0.1 of HCL Workload Automation.