Creating a task to Monitor Job Streams on Multiple Engines

About this task

If you need to combine queries about job streams running on multiple distributed and z/OS engines, you can use Monitor Jobs on Multiple Engines. For example, it might be useful to run a query to find all the job streams running in your environment by running a single task.

To create this task, perform the following steps.

Note: For all the details about options and fields displayed in the panels, see the online help by clicking the question mark located at the top-right corner of each panel.


  1. In the navigation bar, click System Status and Health > All Configured Tasks > New.
    Note: Alternatively, you can create a monitoring task query to be run on multiple engines. For details, see Creating a monitoring task query.
  2. In the Create Task panel, click Monitor Jobs on Multiple Engines > Monitor Job Streams and click Next.
  3. In the Enter Task Information panel, specify a name for the task you are creating (a default name is provided) and define the HCL Workload Automation engines where you want to run the task. The task is run following the specified engine sequence. In this panel, you can also specify whether to share the task with others, to allow them to see and run the task, but not to modify it.
  4. Click Next to proceed with task creation or click Finish to complete the creation using the default values and exit without proceeding to the following steps. If you are editing an existing task, properties are organized in tabs.
  5. In the General Filter section, specify some broad filtering criteria to limit the results retrieved by your query. Here you start refining the scope of your query by also considering the amount of information you want to retrieve. Optionally, in some of the results tables in the Periodic Refresh Options section, you can customize how often to refresh the information by specifying the refresh interval in seconds in hh:mm:ss format, with a minimum of 30 seconds and a maximum of 7200 seconds. For example, 00:01:10 means 70 seconds. If the value specified is not valid, the last valid value is automatically used. If the periodic refresh is enabled for a task, when the task runs, the refresh time control options are shown in the results table. You can also set or change the periodic refresh interval directly in the results table when the timer is in stop status. In this case, the value specified at task creation time is temporarily overwritten. You can search for job streams based on their identifier, status, scheduled time, and priority. For example, you can look for all the job streams that are currently running and were scheduled to run within a specific time period.
  6. In the Columns Definition panel, select the information you want to display in the table containing the query results. According to the columns you choose here, the corresponding information is displayed in the task results table. For example, for all the objects resulting from your query, you might want to see their statuses, when they were scheduled to run, and the engines on which they ran. You can then drill down into this information displayed in the table and navigate it.
  7. In the All Configured Tasks panel, you can see the main details about the task that you have just created. You can also choose to run the task immediately. The task is now in the list of your tasks where you can open and modify it. You can find it in the task lists displayed by clicking the following options: System Status and Health > All Configured Tasks or Workload Monitoring > Monitor Job Streams.


You have created your task that, when run, creates a list of job streams satisfying your filtering criteria and showing, for each job stream in the list, the information contained in the columns you selected to view.

To view connection status information and statistical information about the engines against which the task was run, click the statistics statistical icon on the table toolbar.

A pie chart showing the number of query results and job stream status is displayed for each engine on which the task ran successfully. Click the pie sections to see further details. If the task did not run successfully on one or more engines, you see a message containing details about the errors.