Subdivision of applications

If possible, divide large applications that might run over several days—or even months—into smaller applications that run daily. You can link these smaller applications with a network of external dependencies to provide a more meaningful picture of the overall run plan for an extended period. See Specifying dependencies.

Do not subdivide applications too finely. If you do, you will have to access many applications descriptions, instead of just a few, to make changes.

You can split large jobs consisting of many steps into smaller, interrelated jobs. This lets you use your installation resources more efficiently. For example, assume that job steps A, B, C, and D are all in the same job to ensure that B, C, and D run after A. HCL Workload Automation for Z can schedule the steps in the correct order and let B, C, and D run at the same time. This lets more work run in parallel and can give you more spare time in your batch window.

Also consider using dummy workstations to serialize operations. For more details, see Dummy workstations.