Book Image

BMC Control-M 7: A Journey from Traditional Batch Scheduling to Workload Automation

By : Qiang Ding
Book Image

BMC Control-M 7: A Journey from Traditional Batch Scheduling to Workload Automation

By: Qiang Ding

Overview of this book

Control-M is one of the most widely used enterprise class batch workload automation platform. With a strong knowledge of Control-M, you will be able to use the tool to meet ever growing batch needs. There has been no book that can guide you to implement and manage this powerful tool successfully... until now. With this book you will quickly master Control-M and be able to call yourself "a Control-M" specialist! "BMC Control-M 7: A Journey from Traditional Batch Scheduling to Workload Automation" will lead you into the world of Control-M and guide you to implement and maintain a Control-M environment successfully. By mastering this workload automation tool, you will see new opportunities opening up before you. With this book you will be able to take away and put into practice knowledge from every aspect of Control-M ñ implementation, administration, design and management of Control-M job flows, and more importantly how to move into workload automation and let batch processing utilize the cloud. You will start off with batch processing and workload automation, and then get an understanding of how Control-M meets these needs. Then we will look more in depth at the technical details of Control-M, and finally look at how to work with it to meet critical business needs. Throughout the book, you will learn important concepts and features, as well as learn from the Author's experience, accumulated over many years. By the end of the book you will be set up to work efficiently with this tool and also understand how to utilize the latest features of Control-M.
Table of Contents (16 chapters)
BMC Control-M 7: A Journey from Traditional Batch Scheduling to Workload Automation
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Managing batch jobs as workloads


The jobs we have been running so far are designed to be submitted onto a predefined host for execution; this is the so-called static scheduling. There is nothing wrong with it and, in fact, this is how batch processing happened originally, right back to the OS built-in scheduling tool (for example, CRON) days. It is absolutely fine if there is only a handful of non-critical jobs running on fixed dates at fixed times. However, as we progress into event triggering, the batch workload no longer stays the same and becomes subject to a number of external events, generated at a given time. Peak periods are hard to predict. Too many events generated around the same period can overload the job execution machine and thereby delay the delivery of processing outcome. On top of that, an outage may not be affordable for critical processing requests due to the business's real time expectation.

As famous American investor and author Robert Kiyosak, said, "Inside every...