Overview
What is Control-M?
Control-M from BMC is a platform for integrating, automating, and orchestrating application and data workflows in production across complex hybrid technology ecosystems. It provides deep operational capabilities, delivering speed, scale, security, and governance.
Control-M Workload and Task Management platform
Control-M Review
Control-M (z/OS onliy)
Control-M's experience in Banking and Telcos
Partner opinion
Control-M newbie, but impressed
Control-M at Navistar
My Control-M/WLA Review
First 2 years with Control-M
Control-M has served me well for 12 years
My Control-M review
Control-M is a critical enterprise jobstream manager
Control-M Review
CUNA Mutual Employees's Control-M Review
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Popular Features
- Central monitoring (49)10.0100%
- Multi-platform scheduling (51)8.787%
- Alerts and notifications (51)8.383%
- Logging (50)7.777%
Pricing
On-Premise
Contact Sales
SaaS
Contact Sales
Entry-level set up fee?
- Setup fee optional
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Product Demos
How to Integrate Apache Airflow and Control-M
Orchestrating Multi-Cloud Data Workflows with Control-M
MFT with Control M
Features
Workload Automation
Workload automation tools manage event-based scheduling and resource management across a wide variety of applications, databases and architectures
- 8.7Multi-platform scheduling(51) Ratings
Multi-platform scheduling is the ability to centrally manage a business process from end-to-end
- 10Central monitoring(49) Ratings
A central monitoring dashboard provides data on trends and forecasts
- 7.7Logging(50) Ratings
Logging and audit trails to ensure regulatory compliance
- 8.3Alerts and notifications(51) Ratings
Alerts and notifications enabling management by exception
- 8.7Analysis and visualization(48) Ratings
Analysis and visualization tools provide clear understanding of critical errors and helps prioritize errors
- 9.3Application integration(48) Ratings
Integration with a broad range of enterprise applications
Product Details
- About
- Integrations
- Competitors
- Tech Details
- Downloadables
- FAQs
What is Control-M?
Control-M Features
Workload Automation Features
- Supported: Multi-platform scheduling
- Supported: Central monitoring
- Supported: Logging
- Supported: Alerts and notifications
- Supported: Analysis and visualization
- Supported: Application integration
Additional Features
- Supported: SLA Management
- Supported: Data pipeline orchestration
- Supported: Hybrid and multi cloud workflow orchestration
- Supported: Jobs-as-Code and DevOps support
- Supported: Self-service interfaces
- Supported: Conversion tool
- Supported: Workload archiving
- Supported: Self-healing and remediation
- Supported: Standards in production
Control-M Videos
Control-M Integrations
- Apache Airflow
- Microsoft Azure
- Alteryx Designer Cloud
- Azure Backup
- Google BigQuery
- Google Cloud Functions
- Google Cloud Dataflow
- Azure Databricks
- Automation Anywhere
- Amazon Athena
- Azure Machine Learning
- Azure Synapse Analytics
- Apache Hadoop
- AWS Lambda
- Impala Open Distribution
- Amazon SageMaker
- Apache Hive
- Amazon S3 (Simple Storage Service)
- Docker
- MySQL
- MongoDB
- Apache Pig
- HashiCorp Terraform
- Apache Spark
- Snowflake
- UiPath Integration Service
- Talend Data Integration
- Oracle Linux
- Microsoft Power BI
- SQL Server Integration Services
- SAP S/4HANA Cloud
- PostgreSQL
- AWS Data Pipeline
- AWS Step Functions
- Google Cloud Dataplex
- Google Cloud Dataproc
- Google Cloud Deployment Manager
- Azure Resource Manager
- Azure Logic Apps
- Azure HDInsight
- Azure DevOps Services
- Azure Data Factory
- Databricks Lakehouse Platform
- AWS Glue
- AWS CloudFormation
- AWS Batch
- Amazon QuickSight
- Azure Batch
- CentOS Linux
- Db2
- SingleStore
- Amazon EMR (Elastic MapReduce)
Control-M Competitors
Control-M Technical Details
Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
---|---|
Operating Systems | Windows, Linux, UNIX, z/OS, i5/OS |
Mobile Application | Apple iOS, Android |
Supported Countries | Global support |
Supported Languages | English, French, German, Chinese, Japanese, Korean, Hebrew |
Control-M Downloadables
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(103)Attribute Ratings
Reviews
(1-25 of 32)- Implementing a Change Management Process across the Development Lifecycle.
- Orchestration of Batch-based workflows.
- Efficiency and streamlined administration of the platform.
- Records kept by agents might be indexed and kept in one convenient location.
- Improved graphical user interface for Tool would be fantastic.
- To implement the novel idea of "job as code," developers must acquire deeper technical expertise.
Control-M Workload and Task Management platform
- Change management for development cycle
- Orchestration for batch processes
- Platform performance and centralized management
- Platform support
- Agents logs could be indexed and stored on a centralized repository
- Job as code is a new concept that requires more technical skills for developers
Control-M Review
- Simplifies Application.
- Data workflow orchestration.
- Monitor batch jobs.
- It would be great if we get a better GUI of Tool.
- Its not supporting heavy database.
- More user friendly.
Control-M (z/OS onliy)
- Runs jobs when they should.
- Notify users when something goes wrong.
- Provide information on previous runs.
- The interface (On z/OS) is a bit clunky.
- Installation and upgrades are a pain.
- It is difficult to make mass changes.
Control-M's experience in Banking and Telcos
- Control-M is centralized and used transversally throughout the organization. Some cases have several Control-M/Server in production to serve the operation of different countries, however, the Control-M/EM component is usually only one for that environment.
- Different areas and IT management play different roles in the Control-M Jobs automation lifecycle.
- The use of Control-M is related to the massive processing of data across different applications and backend services running on different servers and operating systems that could be orchestrated in a complex way.
- File transfer jobs are common in banking.
- It is becoming more and more common to design REST API type Jobs in the industry.
- Control-M provides a single, centralized interface for monitoring and managing all batch processes in the organization. Nothing is hidden or left unattended in a timely manner.
- The proper use of the BIM component has allowed the change of paradigm in the operation, adopting a proactive management instead of the typical reactive management in the event of production failures.
- The use of Forecast and production simulations allows you to identify bottlenecks and focus first on managing those failures that have the greatest impact on production SLAs.
- Control-M/Change Manager has arrived to shorten development cycles from requirements gathering to production testing. It has been a utility that monetizes the development of Jobs meshes.
- The GUI is capable of efficiently handling more than 80,000 jobs per day. This is certainly a challenge in designing a good user experience. I don't know if there is a reasonable limit to this. One of my clients runs more than 80,000 Jobs daily and the GUI remains smooth all the time.
- Job-As-Code is a DevOps accelerator that has just begun to be adopted. Its implementation will make workload management even more cost-effective.
- Enabling secure mode on all Control-M is cumbersome and could be one reason why customers are reluctant to adopt it, despite the importance they place on the security of their IT assets.
- While it is true that connection profiles are useful for hiding secrets, there is no possibility to make use of secrets in system variables in the Jobs design. Furthermore, secrets that are escaped in the output output should be able to be managed individually.
- The use of translator tables for the promotion of Jobs between environments is limited and has not allowed their use in most of the clients I have worked with. The reason is that the rules of homologation between environments is more complex than usual.
- Workload and batch processing automation.
- Backend automation based processes
- Silent execution of processes and no human intervention
- Execution of workflows that are too complex for a human to handle
- Massive operations on massive amounts of data
- Invasive, with access to the data layer and business logic
- Processes with focus on security, efficiency and reliability
- When you want to predict the duration of each job and of the complete flow
- In critical path management
- For proactive alerting of deviations and possible job failures.
- For workload simulation
- Capability for resource automation
Control-M newbie, but impressed
- Using AFT, sending files to customers is automated and can be customized for success, failure, etc. allowing visibility into the process for all involved
- Self Service is a powerful addition as it allows jobs to be setup and available to users via the web. You can have granularity into the jobs then as access is assigned to users based on their roles, allowing the ability to order the job, or maybe even just monitor the progress.
- Workload Change Manager is going to give us the ability to allow our developers to implement Control-M into the design and coding stages instead of after the fact. This will save time as they will be able to see the end results right away and make adjustments if necessary without having to wait for a scheduler to make the changes. This also allows us to promote from lower environments with some oversight and control. This will be the biggest takeaway for us moving to v9.
- The ability to set default view settings would be a nice add as it would allow the admin to better control the environment for each user role/level of access. This would be especially helpful when it comes to differing environments (dev/test/etc.)
- The licensing structure could be better laid out. Typically when purchasing a licensing suite, you get the full offering for that product, but that is not currently the case for Control-M.
- The ability to setup multiple site customizations and associate them with the access level/role of the user would be something I would prefer to move to the top of the list of things to be done differently as this would allow better customization for web access by eliminating things that you don't want that particular role to have access to.
Control-M at Navistar
- Provides visibility and monitoring across all jobs/platforms.
- The UI is user-friendly and requires very little training to obtain the status of key business processes.
- Control-M for Hadoop enables Hadoop specific workflows to be developed, scheduled, managed and monitored along with other enterprise workloads, all in a single solution.
- Control-M AFT allows us to schedule and track FTP transfers any other batch job. Provides the ability to transfer files securely either via SFTP or FTP with SSL and manage encrypted FTP credentials in a single centralized location.
- The upgrade process could use some improvement as it is somewhat complex.
- The Reporting function can be improved.
- Control-M AFT could have better diagnostic tools or messages to aid in troubleshooting connection errors.
Control-M is a critical enterprise jobstream manager
- Control-M provides strong job auditing of who does what, when, where and how.
- Multiple jobstreams are managed for multiple environments simultaneously from one enterprise server.
- Since we have several OS and database platforms worldwide, this one scheduling application can handle all of it.
- Control-M is relatively easy to learn and engage with at user levels. Job loads and forecasting are relatively intuitive.
- Enhanced GUI functionality has been improving over the years, but screen design can lag behind depending on the version in use.
- Speed of operation is reasonably good but can always be better. Many new features have been added which require more server resources for efficiency.
Control-M Review
- Control-M provides the functionality required to run a lot of jobs in a short period of time. There are times when more than a thousand jobs are pushed through the system in a very short timeframe and Control-M is able to manage this workload with no problem.
- The GUI interface used for monitoring and interacting with Control-M also is a big advantage when processing so many events. This provides real-time viewing and allows for quick responses from our technicians to act and recover issues. This is very important to our business that requires very little down time without major impact to our customers.
- The history information Control-M captures and saves has been a big advantage when researching issues. This information is also used for quality control when making changes as well as satisfying audit requirements. This data is also used to manage capacity and performance of Control-M which has a long history of stability. This is important for many reasons but the number one reason for FIS would be the success it brings to our business and our customers' business.
- A key scheduling function that was omitted from Control-M is dataset triggering. BMC included this function as part of Control-O which requires a separate product to manage dataset triggering.
- Control-M product release upgrades are very complex and requires extensive knowledge for Control-M and the OS environment.
Control-M at OLG
- GUI presentation
- Operations can identify job flows and realize business impact visually
- Provides control within operations
- Processing streams can be halted immediately during a failure, without intervention and eliminates cascading issues and problems
- Self-Service access
- Providing browser access for all our users enables them to view their processes and realize interfaces and impact that their processes have on other systems. User access and viewing reduce delays during problem resolution as it enhances communication and expedites root cause determination.
- Direct product interfaces using modules
- DataStage job schedules are fast and are easily configured as well as Database maintenance functions which can now be linked to before and after DB activities
- Setting up Site Standards needs some enhancements
- More robust functionality for field validation is needed, such as only one Quantitative Resource rule can be applied on multiple QR's defined in a job. Therefore giving warnings on QR standards because each QR must match all QR rules
- Reporting structure is a bit cumbersome and needs a more effective interface. Jumping from panel to panel is not very effective.
- Connection profile password management is tough to maintain. Each entry must be manually updated every time there is a password update. Since our policy is that all system passwords must expire after 180 days and we must be included in all application related password updates. Unfortunately that also is an issue where the Control-M administrator is globally aware of those passwords, which should be held confidentially by each separate group
Control-M, the best WLA Tool
- The GUI is very good
- BIM is very helpful
- In the monitoring domain, please enable users to modify things like owner, set to dummy (options which are grayed out must be opened).
- Just like we have folders under home, please create some thing like jobs where-in we put in the job name then select it and run them. This make easy in an organization like us where we get a lot of requests to just run the jobs.
Control M review
- Control-M is very stable. It is rare to have any issues with the application.
- Dealing with dependencies is handled very well. Dependencies are easy to set up whether they are on the same server or across platforms.
- Alerting is also a strength in Control-M. It has a built in tie in to the Remedy system which allows ticket creation to be handled easily.
- I would like to see some improvement in handling conditions from previous days.
- I would like to see some improvement in being able to send out alert notifications on jobs that have not started past the new day.
Control-M - True enterprise scheduling
- Provides seamless cross-platform workload automation integration.
- Provides integrated SFTP capability. No scripting or custom error checking required!
- Control-M provides fully auditable, version controlled workload development and provides tools for users to collaborate on development.
- Control-M provides excellent exception management allowing us to use our resources where they are needed most instead of monitoring workloads.
- Control-M could provide improved dynamic workload management based on physical server resources.
- Control-M for File Transfer could provide better diagnostic tools for troubleshooting connection errors.
BMC - control M automation software
- Simplifies batch jobs
- Automates batch jobs
- Reduces failed batch jobs
- Helps maintain track of SLA commitments
- Provide more visibility into file transfer operations
- Can work better on big data workloads
- Control-M provides an easy-to-use and easy-to-interpret interface for users, with most of the screen options and field names being self-explanatory. The on-screen options provide for a full range of functionality for automating batch production requirements, with multiple options and flexibility.
- The vendor provides Control-M a wide range of utilities for extracting information from the dataset and providing with a minimal amount of training required for use.
- As the systems programmer for Control-M on the Mainframe, the ease of installation is one of the nicest features. The installation is panel driven and can be used by a relatively inexperienced technician to install successfully in a matter of several hours.
- Again, as the systems programmer, I appreciate the level of expertise of the technical support personnel. Over the past 20+ years, I have come to know them well and find them to be knowledgeable and willing to provide assistance for any and all queries.
- The developers have always been willing to listen to requests for new functionality and enhancements to existing functionality and are working to have the same type of functionality across all platforms.
- We have worked closely with BMC to participate in the beta testing program and have had the opportunity to have an impact on software development.
- As with most of the Mainframe software products, documentation seems to be the weak link for the products - written by people and for people who already know what they need to do, not for people who are trying to figure how to use the product.
Control-M is gromming year by year
Control-M is used across the organization, it helps the business to know of failures in a timely manner, and to investigate the issue immediately and figure out exactly where the impact is.
We sometimes find out from users that the trucks are stuck and not moving, due to pink slips not getting generated at the warehouse.
We immediately identify which is the job getting delayed, and we reach out to the right functional team to resolve the issue.
Control-M is easy to use, and reliable and we look forward to vast growth in the future if troubleshooting steps are made easier.
We feel bad having to tell our customers that an issue occurred due to the Control-M application, and we are still looking forward to a solution on retry submit for our JD Edwards Jobs.
- Map view and list view make it easy to filter jobs
- The planning domain for monitoring domains is a good idea on the application side
- The control-M modules are great
- Forecasting is another beneficial feature
- Bugs which I know cannot be entirely avoided are an issue
- It should be simpler and easier to install the control-m packages
- Troubleshooting steps should be be available: need to provide more videos on problem areas by checking the incident tickets raised by users on the BMC side
Not to sure if any JD Edwards module is coming up?
I'm also looking forward to a fix on retry submit: Although we have upgraded our agent to fix pack 5, we still see the issue occurring and the scary part is jobs turning into unknown status. We only get to know once the user informs us.
Looking forward to a nice feature to let us know if any such thing occurs.
Control-M Rocks
- Scheduling Flexibility. We have some very unique schedules. For example: we run a job on the 2nd Sunday after the 2nd Tuesday of the month.
- Cross platform interdependencies. Allows us to trigger jobs on the various different OS platforms.
- Notification from jobs. Failure alerts, job late and running long notification.
- One feature that I feel needs some improvement is the ability to create a graphical flow chart of jobs and be able to print it and look nice.
Best of breed and moving farther ahead
- Control-M Advanced File Transfer is a very useful add-on, allowing for a wide variety of file transfers to be configured "out of the box" and then used as part of the standard batch flow. This module is not included in the base price but is available at a relatively small additional cost.
- Using Control-M's GUI (the Enterprise Manager) allows for efficient management of the enterprise and can tie up a lot of "loose ends". Often the first point of tracking problems is to check with the Control-M guys!
- BMC is definitely moving the product forward, the new module "Application Integrator" is very helpful in building and deploying your own bespoke Control-M jobs and allows for closer and more secure integration.
- Although Control-M does open up the enterprise in an operational sense, the security settings (should you choose to implement them) are robust.
- The reporting provided with Control-M could have more functionality, Many users end up creating their own reporting based on the Control-M DB. I believe BMC are addressing this.
- Within the Advanced File Transfer (AFT) it would be useful to have an integrated FT server and not rely on the underlying SSH.
- All batch schedulers have issues with fully automating tasks in a Windows environment and Control-M is no exception. Userids and profiles are harder concepts to deal with in the Windows world but BMC are doing their best to address this and Control-M would be better at handling these scenarios than the alternative products.
- Control-M controls the flow of the execution of jobs and scripts, their actual status of execution, and how many jobs and scripts will be executed.
- Control-M triggers the start of jobs and scrips by the arrival of files.
- Control-M can control the execution of jobs and scripts simultaneously.
- Control-M allows a user or programer to start and follow the execution of jobs and scripts by internet.
Control-M for the enterprise
- Central monitoring of all jobs running in the environment.
- Easily tied into our ticketing system. This allows for auto-ticketing in the event of job abends.
- Uncomplicated job setup.
- It would be nice to be able to review agent logs from the central dashboard.
- Automated agent unavailable alerts that could tie into our ticketing system.
Control your jobs
- Easy to set up.
- Interfaces with third party applications.
- Friendly user interface that gives you a graphical view of your workload.
- Since it is such a robust product, users need extensive training.
- We have always run into issues with setting up security, which needs to be refined and made simpler.
- The reporting feature needs to be addressed. Its still a bit cumbersome to pull needed reports.
Control-M is well suited for mainframe and batch processing. If you are still using Windows scheduler, Control-M is definitely a replacement for that. It's perfect for workload automation. If you are looking to centralize administering, monitoring, and scheduling jobs...then Control-M is the product!
If you are a small business that does not have a large number of jobs to schedule, then perhaps Control-M might be an overkill for your environment.
Control M Practical uses and Functions
- Control-M has excellent calendar functionality that allows for detailed scheduling of jobs according to many specifics (day, month, year, time, preds, and several other conditions).
- The software is also easy to navigate and group related jobs together for easy viewing of job streams or flow.
- The alerts panel and its features make sure that if you encounter issues with any job it is brought to attention immediately for resolution.
- I would like to see an "on demand" refresh put back onto the GUI interface as well as the auto refresh it currently has.
- Although there are many different scheduling options, I think it would benefit the end users to have a better overall view of their jobs and job streams somehow.
The current best workload automation tool
- Ease of use
- Graphical view of your entire organization workload
- As it matures, the product gets better and more stable
- The WLA tools should be made as a web base rather than thick client.
- Built-in change manger should be part of the tool, not another add-on.
- Agent deployment should be all automatic, base install then fixpack, and so on.
My TrustRadius rating and review of Control-M
- Easy to set up basic batch schedule needs.
- Production Control has integrated x-Matters with Control-M so when a job fails x-Matters now sends out a notification, which is quite timely, versus Production Control manually calling on-call staff.
- From my usage Control-M is quite stable; that is, up and running.
- Control-M documentation needs to include examples with screen snapshots when describing a particular scenario. What is the saying? "A picture is worth a thousand words." Also these snapshots are very useful for users (like myself) that only have view authorization for production Control-M job definitions and that do not create job definitions in development environment. Thus, unable to see all possible setting options and BMC documentation may describe these options but may not have a screen snapshot. For example, ON-Do Conditions.
- For a Control-M Enterprise Manager need to provide a better way to Load Folders and Jobs. Currently click on 'Planning', 'Load Folders and Jobs', scroll down to find parent folder, click on parent folder, select which job definitions you want to see, and then (look all the way to the bottom right corner) to click on 'Open'. Now if I decide I want to see a job definition I did not include I have to open another tab by clicking on '+' and scroll down to find parent folder, etc. Of course, one can click on the check box to the left of parent folder to see "all" the job definitions, but what if I do not want to see "all" the job definitions?
- Need better search capabilities. For instance search for all 'cyclic' job definitions in this parent folder. Find job whose Order Id is xxxxx.
- Need a better way for scheduling a job instead of having a job definition for each scheduling occurrence. Why can there not be one job definition that shows for Mon.-Fri. The In-Conditions are this and for Sat. and Sun. The In-Conditions are this? Thus, the 'Prerequisites' and 'Actions' tabs may need to be subset of 'Scheduling' tab.
Control-M puts us firmly in control.
- Time - does a lot of the work for us when things go wrong and we can pinpoint where the problem was - Reduced cycle time!
- Confidence - Gives end users the confidence data is CORRECTLY processed.
- Easy to use - Great interface and reduces the errors common using other command line schedulers.
- Reduced ongoing costs - Allows us to concentrate on the actual job with out constantly writing our own monitoring tools.
- JAVA/Database API to allow tickets to be raised in to other in-house systems.
- Great processing to look inside the content of batches to correct some common/frequent problems and then allow processing to continue.