Currently Workload Automation customers are moving increasingly to dynamic agent scheduling managed by Dynamic Broker component (ITDWB enterprise application). Dynamic agent scheduling introduces additional processing to the traditional one.

There are multiple processing steps between job execute notification, via mailman server, to Broker component and the final job dispatch to the remote JobManager. All these steps correspond to an internal job status in the JOB_BROKER_JOBS table in the DWB schema that map to WAIT status in the plan (which could be check using conman or the Dynamic Console). The WAIT status means, as documented, that the job is waiting to fulfill its dependencies. In this blog, it is explained how to retrieve a meaningful detailed status of Jobs.

Workload Scheduler allows now to protect not only its resources like Applications, Special resources, Jobs or all the objects present in the Current Plan or in the Database, but also actions and commands.

For example, the Workload Scheduler execution information are stored in a VSAM file called  Current Plan. The execution workflows are defined through Applications including Operations (jobs), Dependencies and other resources. Currently an WSz user can either have READ or UPDATE access to the Current plan. A user with UPDATE access can add new workload, edit occurrences, restart jobs, hold, nop, un-nop, release jobs and many other actions and commands.

Are you curious about Workload Scheduler? Do you want to get to know it in an easy, immediate way? How about a detailed, comprehensive overview of its main features, both the latest ones and the ones which have decreed its success over the years?

​A great way to get started and understand what the fuss is all about is our exhaustive channel on YouTube, which features over one hundred very popular videos, describing the most exciting new features and tips and tricks on how to use the product for best performance and results.