Scheduling and submitting jobs and job streams
You schedule HCL Workload Automation jobs by defining them in job streams.
For distributed environments, use the Dynamic Workload Console, Application Lab or
the conman command line.
After you define an HCL Workload Automation job, add it to a job stream with all the necessary scheduling arguments and submit it to run. After submission, when the job is running (EXEC status), you can kill the HCL Workload Automation job if necessary. For some job plug-ins, this action is converted into corresponding action in the plug-in application. Refer to the specific plug-in section for details about what effect the kill action has in the application.
For z/OS environments, use the Dynamic Workload Console or
the ISPF application.
- How to submit a job stream using the Dynamic Workload Console
- To submit a job or job stream to run according to the schedule defined, see Submitting Workload on Request in Production. For distributed environments only, see also Quick submit of jobs and job streams.
- How to submit a process (job stream) using Application Lab
- To submit a process to run according to the schedule defined for it, see Running a process.
- How to submit a job stream from the conman command line
- To submit a job stream for processing, see submit sched . To submit a job to be launched, see submit job. For more information about these commands see the HCL Workload Automation: User's Guide and Reference.
- How to submit your workload using the ISPF application
- The workload is defined by creating one or more calendars, defining applications, creating a long-term plan, and creating a current plan. The current plan is a detailed plan, typically for one day, that lists the applications that run and the operations in each application. See the section about creating plans for the first time in Managing the Workload (z/OS) for more information about creating plans.