Can you run jobs outside the scheduler?

Jobs fall into four categories:
  1. Jobs that are in the current plan and are submitted by HCL Workload Automation for Z.

    These are scheduled jobs, or jobs that you have added to the current plan using the MODIFY CURRENT PLAN (MCP) panel.

  2. Jobs that are in the current plan, but are not submitted by HCL Workload Automation for Z.

    These are usually jobs that are generated and submitted by some other subsystem, such as CICS®. The scheduler can track these jobs and take account of the resources that they use. It is also possible for other subsystems to submit held jobs and for HCL Workload Automation for Z to release them when all dependencies are met.

  3. Jobs that are not submitted by HCL Workload Automation for Z, but trigger events in HCL Workload Automation for Z.

    These jobs are specified with event-triggered tracking (ETT). Refer to Adding occurrences by event-triggered tracking for more details.

  4. Jobs that are completely ignored by HCL Workload Automation for Z controller.

One disadvantage of having jobs outside HCL Workload Automation for Z (categories 3 and 4) is that HCL Workload Automation for Z cannot take account of the resources that they use. The scheduler can schedule and control its jobs to avoid contention for resources (such as tapes, data sets, and JES initiators), but if other jobs use these resources, HCL Workload Automation for Z might submit its jobs when a resource is unavailable.