Jobs can be started using either the zos command line tool, scheduling through a .sched file, or manually through the PlateSpin Orchestrate Development Client. Internally, when a job is invoked, an XML file is created. It can be deployed immediately or it can be scheduled for later deployment, depending upon the requirements of the job.
Jobs also can be started within a job. For example, you might have a job that contains JDL code to run a secondary job. Jobs also can be started through the Web portal.
Rather than running jobs immediately, there are many benefits to using the Job Scheduling Manager:
Higher priority jobs can be run first and jump ahead in the scheduling priority band.
Jobs can be run on the least costly node resources when accelerated performance is not as critical.
Jobs can be run on specific types of hardware.
User classes can be defined to indicate different priority levels for running jobs.