Control-M is used to run Oracle scripts with scheduled jobs including monthly, weekly, and yearly schedules. Around 50 or more jobs are run every week. Control-M connects to the database, triggers all procedures, performs the operation, and generates the final report. The log is sent to mailboxes detailing how the process went, any issues, or any errors. If there are issues, the mailbox is checked; otherwise, a message indicating successful completion is received along with statistics such as how much time the process took and which processes were run. Jobs are scheduled once, Control-M jobs are created, timing is set up, and the jobs fire automatically at the particular time.

Control-M is used to connect to Oracle products, and through Control-M, a Tableau dashboard is maintained. Most of the scheduling jobs use Control-M to schedule. Control-M helps all products, making it a utility that can be used wherever scheduling features are needed. It is not just for DevOps, databases, or front-end applications; it can be used anywhere without manual intervention to perform particular activities. Wherever there is an opportunity for scheduling jobs, Control-M is the first option.

For migration, Control-M is considered very good. Once all the source and target details are configured in Control-M, it can automatically migrate data. It requires proper configuration and specifying the necessary changes for target technology along with the source system scripts. If properly configured, the complete migration can be triggered end to end. Data migrations and reporting, along with all scheduling activities, can be efficiently managed.

The best features in Control-M include sending emails to mailboxes after the process is completed and providing proper acknowledgement reports. The timing is impressive; it connects very fast and performs activities efficiently. The UI is very friendly, making it easy to configure jobs in Control-M. If core technology scripts are available, creating Control-M jobs is a five-minute task. The GUI is very friendly, which simplifies task assignment, scheduling, canceling, and all these operations, making it easily navigable.

Every week, 50 jobs are run using Control-M. If those 50 jobs were being run manually, it would take more than a week. Through Control-M, the jobs are able to be scheduled within two days, saving around five days of effort.

Before Control-M, jobs would be run on Friday evening so that the process would end by Sunday night, allowing the business to start on Monday. Without Control-M, everything would have to be run manually throughout the week. Thanks to Control-M, around five days are being saved. Otherwise, old data would be received for the current week's business, but now the latest data is received.

Control-M has room for improvement in displaying dashboard-like graphical reports once processes are completed. For example, after scheduling 50 jobs, if a dashboard showing the completed scripts, status, and time taken is displayed within Control-M itself, it would be very helpful. Currently, mailboxes are checked for reports; if it were in Control-M, anyone could check it. Only those configured with specific mail IDs receive emails, so if a few members are not set up, they will not see the reports. If it were available in Control-M, those users could directly check the dashboard.

Control-M has been used for the last two years from the beginning of the project level. Earlier, it was already there in Control-M that the client was using.

The same score for stability is a nine out of ten.

Control-M is capable of handling a large volume of processing if the necessary memory space is provided to the server.

Great support is received, with a rating of nine out of ten.

Control-M would definitely be recommended because it saves a lot of time. If everything were being done manually, it would take a lot of time to run and validate scripts. If everything is configured in Control-M, even non-experts like front-end staff can trigger jobs, making it simple. It is a one-time configuration, and anyone can trigger it. That is the best part; significant time is saved, and there is no waiting time; the next process starts immediately once the current one is completed. If dependencies are set in Control-M, it starts the next task automatically. That is why Control-M is highly recommended for scheduling.

The client is a big enterprise client.

Control-M requires occasional maintenance, maybe yearly or once every six months for upgrades. A Control-M team manages activities such as maintenance every six months or once a year, including cleaning up scripts or memory.

Around 15 members are using Control-M.

The overall review rating for Control-M is ten out of ten.

Control-M is used to orchestrate workloads across multiple environments including dev, UAT, and production. There are plans to consider moving towards either a hybrid or cloud-based model with the environments in the future.

Control-M handles complex workflows through a variety of job types and multiple job types being able to interact with each other. The complexity can either be in the job flow or the background to when the job runs. For example, using calendars, whether it's multiple types of calendars, a job would only run when jobs from another calendar either have run or haven't run, or a mix of several different options. Calendars is the part of Control-M that is almost a puzzle that you have to solve first. If you can solve those kinds of puzzles, the job builds themselves can do that, which is the easy part compared to the calendars.

Building, scheduling, managing, and monitoring workloads is what Control-M does. After seven years of using it, no limitations have been found. Whatever is asked of it, it can do, and if there's something that cannot be done, the BMC team will find a way of working around it and maybe improve the product to fit your particular situation.

Introducing the Batch Impact Manager job, or as it's known, the SLA management job, into batches has allowed alerting to be scaled up and refined so that intervention can occur when a batch is running late, if a job is running longer than expected, or if there is a failure upstream. This has certainly helped out the batches.

The creation of data pipelines across on-prem and cloud is quite complex. The integrations provided by BMC have made that really easy. Jobs fit together really well with no loss of visibility. Having one UI to see the source of data to the end product is really useful.

The interaction with Oracle Cloud Infrastructure through the Oracle EBS batch has been one of the biggest successes in recent years, with the EBS batch handling the general ledger for Virgin Money and Clydesdale. This is the strongest case.

The features that are most valued within Control-M are the division of the domains of planning, monitoring, forecast, and tools. There is a migration towards the web UI away from the main UI. Managed File Transfer is a favorite feature that has been worked on over the last couple of years, especially going up to either the AWS cloud or to the Azure cloud. Other features that are valued are the integrations coming through the Integrations Factory, such as through Azure Data Factory and Azure Databricks, which have been worked on recently.

These features are valued because they are so versatile. They can do so much within just one job type. For example, the Managed File Transfer job type combines lots of different little bits of technology. You can have a file watcher within the job type, but you could also have a file copy, and there are lots of advanced features beneath the surface, not just doing the file copy.

The best return on investment through Control-M is that single pane of glass, being able to see end-to-end batch from start to finish through one tool.

Control-M can be improved, especially from a financial industry background, with the Data Assurance module. If you put bad data in, you get bad data out. Having something such as the Data Assurance module in place will hopefully prevent any sort of downtime or batch interactions that are unnecessary and having to rerun jobs all the time.

Control-M has been used for seven years.

There have been a few issues in the UAT environment based purely on the infrastructure that it sits on. Anything that is improved in that space is attempted to be replicated in production to avoid any future issues. As far as with the tool itself, there are no issues to report.

Scalability is one of Control-M's best assets. Currently on a license-based model, when getting close to that limit, discussions with BMC about either contract extensions or increasing the license count within that current contract did not seem too difficult to do.

Whenever there is an issue that needs a ticket to be raised, the response time is always really good. There has never been an issue that could not be resolved by the support teams, whether that be a simple fix done by first-line support or whether team calls are needed to demonstrate the problem. There have even been issues where some of the team within the labs have jumped on the call as well and replicated the environment on their systems to understand the problem a lot more. The turnaround time for answers and solutions is really good.

Control-M is the only tool that is aimed to be used. There have been mergers over the last couple of years which have different tool sets, but there has been no competition as to which one is favored. People just want to use their respective tools, and the future will show what happens.

The best return on investment through Control-M is that single pane of glass, being able to see end-to-end batch from start to finish through one tool.

Advice for customers or potential customers of Control-M would be to just try it out. BMC can offer you a trial and then you can make use of it, put it through its paces, ask any questions you want of the support teams, and you will be pleasantly surprised. This review has a rating of ten out of ten.

My main business use cases supported by Control-M involve working with healthcare, insurance, telecoms, and banking, both retail and investment, primarily to ensure things are working. Much of this is in regulated industries, so we have established the necessary processes and tools to ensure that Control-M code is properly controlled, allowing us to satisfy SOX audits and other similar regulatory requirements.

Host groups are one of the most valuable (and unrecognised) features in Control-M and allows you to make your code environment agnostic. They allow for load-balancing, simple scaling, and technology groupings. Control-M supports my DataOps and DevOps initiatives by providing a single pane of glass to orchestrate and manage workflows across numerous systems. With the integrations, I have access to all my on-prem and cloud-based applications, and I can write my own interfaces for systems that are no longer supported, such as managing Solaris machines which still run for some of my clients.

Control-M integrates with new or changing technologies within my DataOps or DevOps stack fairly easily. The BMC team consistently develops new integrations at a rate of two or three a month. If they have not already got an integration available, it is very straightforward for me to create one myself, even for older technology through agentless connections to unsupported systems.

Control-M enables new capabilities or business processes that were not previously possible. There is significant capability embedded in the tool, some of which is not immediately obvious. With some creative thinking, I can leverage these capabilities to improve performance and allow Control-M to handle much of the load balancing.

One key element where Control-M could be improved is in providing a better audit trail for converting from development through to test and then to production environments. The process can currently be done, but the XML version is difficult. JSON offers an easier approach and is going to be the standard moving forward, so some XML-related issues will resolve naturally. For those still on XML for source control, it is an ideal opportunity to review procedures within Control-M to ensure compliance.

I joined JP Morgan in 2007, which introduced me to Control-M, and I have essentially been working with Control-M ever since then, marking 18 years this year.

The stability and reliability of Control-M in my experience is commendable; it simply works if set up correctly. Proper analysis of infrastructure requirements, source code control, and growth expectations should be carried out before commencing the migration. Once those factors are right, the conversion should run very smoothly. It is important that the conversion is carried out by a collaboration between teams that understand the old and new systems.

Control-M orchestrates workloads across multiple environments quite easily. I find that the graphical interface is very user-friendly, and although I have traditionally used the desktop interface, the web interface in version 22 is now nearly as effective as the desktop.

My experience with pricing, setup costs, and licensing for Control-M raises interesting points. Pricing is often perceived as high, and the licensing model can be unclear. However, in the end, it is clear that I am paying for a top-end tool which rarely experiences issues, with most problems stemming from the applications being managed rather than the tooling itself.

Regarding other solutions considered before selecting Control-M, I have seen conversions from Redwood and witnessed attempts to convert out of Control-M into a cheaper product. These attempts often ended in failure, leading to a reversion back to Control-M. Currently, I am looking at conversions from TWS into Control-M SaaS, and Axway into Control-M SaaS, along with several other potential conversions.

With proper planning, setuo is straightforward.

The biggest return on investment I have experienced with Control-M is the reduction in support time. If I set things up correctly with appropriate alerting levels, my support team can proactively prevent incidents rather than waiting for something to go wrong. The most significant metric is the number of support tickets prevented, rather than the number of support tickets closed.

My experience with pricing, setup costs, and licensing for Control-M raises interesting points. Pricing is often perceived as high, and the licensing model can be unclear. However, in the end, it is clear that I am paying for a top-end tool which rarely experiences issues, with most problems stemming from the applications being managed rather than the tooling itself.

When considering the overall experience with the migration processes of my customers, I find that if they approach the process with proper planning and due diligence, it typically goes very smoothly. A common mistake is trying to lift and drop what they had in another tool into Control-M without considering process differences, as the tools do not function the same way.

My advice to other companies considering Control-M is to conduct due diligence, examining not just initial costs but also ongoing expenses. It is essential to consider anticipated usage duration and growth patterns, as a correct setup facilitates easy growth, whereas a faulty setup complicates matters.

I would rate Control-M overall as a 10 out of 10.

The main use case is to automate business processes from ERPs, SAP, databases, and file transfers. I also use it with DataOps and DevOps. It is very easy because Control-M has native integrations with many tools, and BMC develops more integrations every month, making integration straightforward.

Recently, BMC has focused on cutting-edge technologies, such as cloud, machine learning, and artificial intelligence. These are the latest connectors that BMC has released for these technologies.

Control-M is an orchestration tool that provides a broad and complete vision of your environment. You can integrate many different heterogeneous technologies. The main feature is its role as an orchestrator. It is easy to use and has numerous native integrations. If you need a specific integration for a homegrown application, you can develop a connector for that as well. Control-M can be used with a job as code approach, and it provides audit and governance capabilities on the platform.

I cannot identify areas for improvement at this time because Control-M is a state-of-the-art technology.

I have been using this solution for more than 15 years.

The deployment process is very straightforward. There are two distributions for Control-M: an on-premise offer, which is the classical offer, and Control-M as Software as a Service. While Control-M is easy to implement overall, the Software as a Service approach offers many advantages because customers don't need to worry about infrastructure since BMC handles it entirely. Additionally, customers don't need to perform upgrades and cumbersome initial setups.

The solution is very stable and secure.

The scalability is very good because Control-M implementation can be used in high availability. For on-premise implementation, you can distribute components of Control-M in different machines. The SaaS implementation is also very scalable.

The technical and customer support is excellent. BMC has great development in both areas. The support is accurate, and BMC is always ready to help with queries and complex incidents.

The benefits include achieving digital transformation, accelerating business processes, removing silos, and meeting SLAs at the exact time.

I am not comfortable discussing pricing details. I prefer to focus on technical issues.

I am a Control-M consultant working with utilities, banking, and government sectors. In Brazil, Control-M is used by a broad range of companies, including major financial companies, utilities, oil industry, telecom, and retail. Control-M is widely recognized in Brazil for orchestration. BMC continuously improves the tool. The reviewer has given Control-M a rating of 10 out of 10.

We use Control-M for batch automation. Previously, all of our batch work was manual, but now Control-M has significantly reduced the need for manual intervention. As a result, our batch processes are now 99% automated.

It's so easy to navigate, and especially for new hires, it's very straightforward to show them around the client because it is user-friendly. It's very easy to use. Compared to other softwares, Control-M has significantly simplified our monthly release process, making it easier to move things forward.

We're upgrading Control-M, and the process is very long. There are numerous boxes to tick and things to check to ensure everything is in order before the upgrade happens. We run three instances of Control-M, and making various changes for each is challenging.

I have been using Control-M for five years.

You might experience a brief connection issue, but it usually resolves within a few minutes. The problem is related to the web server.

Scalability is excellent. We utilize only about 20% of Control-M's capabilities.

Support is helpful, and the online community is very good. There's the community forum, which I use regularly to find answers to questions. BMC has been very helpful in that space. They were extremely fast and solved a difficult problem our in-house team couldn't solve in a matter of minutes.

The initial setup is straightforward. We used to use in-house software.

We have three different environments where people can work. People can use our development instance of Control-M to work on their batch processes before they go live, allowing them to experiment and refine until they get it right.

It's much simpler now. Everything was a manual batch job. Using the features of Control-M every day makes our batch processing so much easier.

It makes our lives so much easier. For our operations team, which runs our daily batch overnight, viewing everything as it happens has been an absolute lifesaver, especially if things go wrong overnight. It's great to have that visibility. It has also sped up our process, reducing overhead and weekend overtime. Batch processing is much quicker now, resulting in fewer manual errors.

Control-M has so much functionality that even if you initially purchase it to handle a specific part of your batch work, it can offer much more. We've progressed beyond traditional batch processing to include MFT, which has been incredibly useful. Our file watchers and other automation features have significantly simplified our workflows and made our lives much easier.

Overall, I rate the solution a ten out of ten.

Control-M is a job scheduler. You can schedule FTP jobs or use scripts within Control-M. You can also execute commands when necessary to schedule, or you can just run a script that is hosted on a server. Based on the schedule, you can orchestrate or automate jobs. You can set dependencies between jobs. You can correlate and create a sequence of your jobs and execute them in the order you wish. You can set the variables and options that you like. You can set the prerequisites and post-job activities after the completion, such as reports analysis, emails, etc.

Helix Control-M is critical for us. If we do not have a job scheduler like this, we will have to have people running 366 different jobs on a daily basis and 24 hours a day. These are the jobs that we run from midnight to midnight every single day on a scheduled basis.

I do not use Helix Control-M's Python client or Airflow. I am using the web client. I do not create jobs. I give my users access to create their own jobs. I just maintain the agents and keep the administration going. When they have questions, they come up to me and ask. We just use the web interface to go into the planning mode and create our jobs, folders, dependencies, etc.

Control-M has helped to give business users visibility and control over their jobs. Both Control-M and Helix Control-M allow me to give users control over their own set of jobs. They can log in and orchestrate their jobs as they want. They can also troubleshoot them on their own. It makes that easy. I just have to be hands-off and stand by in case they need assistance, but once the tool is deployed and every agent is up and running, it is easy. The people who have the jobs running or the job scheduled know about their own jobs. They know their own demands. They have control over the decision of when they are going to run it and how they are going to run it. It makes it very simple, and it helps.

You can set up your users and define whether they have admin privileges or they can just affect a set of jobs.

The fact that it is all centralized in the web browser makes it easily accessible from everywhere. All my users are IT people. They do different things. They do databases. They do informatics. They do development and things of that nature. To business users, such as board members of the company, we can give them reports on, for example, how the business closed and how much profits were there, or if all the transactions were submitted to the bank on time. If not, what were they missing? We can provide all things of that nature. We can pull it all up in a report and then schedule it on a daily basis or weekly basis. It is simple.

There have been cost savings with Helix Control-M. The license that the company was paying for Control-M, including support, was three grand more expensive than Helix Control-M. With Control-M, we also had to have an administrator dedicated to maintaining Control-M on-premises. That cost of having a person dedicated to doing just Control-M jobs is gone after we moved to the cloud. We are not only getting more money in savings; we are also making a better distribution and use of our time. By not having a dedicated person, we are saving a couple of grand. We are saving on the license and, of course, resources. We do not have to have dedicated resources such as servers. We do it virtually. We do not need to have resources reserved for the server and database. I just have to deploy the agent, which can run multiple instances in my cluster. They can share resources, which is another saving there.

In Helix Control-M, we have the automation API that allows us to customize and do integrations easily in any script, such as Java or Python. It is all integrated within the integration API.

Every year, they add another set of automation or compatibility with different applications. They are capable of integrating with Informatica, AWS, etc. You can schedule queries directly from Control-M on databases without having a server or agent. You can do scan jobs or queries directly. Every other month, they are doing releases, and they have tons of new integrations, which makes it compatible with more and more applications around the cloud.

They have a department that handles requests for enhancements. I talked to Control-M guys back in October or November when they had a gathering here in Atlanta. We talked about not being able to go back in history in Helix Control-M for more than two weeks. We submitted a request for enhancement. They told us that they are working on it, and they are thinking of expanding that to 30 days. We would like to see it expand to 90 days, but they are working on it. In Control-M, we were able to go back 180 days, but that was on-prem. The storage of that data was on our own servers. We know that storage is money, and we do not expect them to store that much of the data, but at least 30 to 60 days seem proper.

Community Loans of America has been using Control-M since version 6. It has been at least 10 years.

I have not had any downtime with Helix Control-M. All the upgrades are scheduled, and they give us a time window when they think they are going to schedule them, and we adjust. I have not seen anybody notice it. The jobs get held before the update, and they start automatically after the update. If anybody noticed it, that was because I had to tell them that a maintenance window was coming up and to be aware of it.

I contacted their support a couple of times to ask them about an error that I did not understand. They have three guys who are pretty handy. When you ask questions, you, of course, have to wait at least 24 hours for someone to respond. They are pretty fast. Most of my queries were responded to within the same day, which is great. I would, for sure, rate their support a solid 10 out of 10.

We were just using Control-M. We did not have any other scheduler. We migrated from Control-M to Helix Control-M.

Control-M is on-premises, and it requires a dedicated administrator. Control-M has three major pieces. It has a Control-M server. It has a main agent, and it has a database. If you have HA, you will have the same things at a secondary location, so you will have to manage the cluster and make sure that all the pieces are working together. If, for some reason, one side fails, HA tries to recover in the second location. The management or the administration side of things is a challenge. It requires a dedicated person. Our main Control-M guy left us six years ago. Every time we had an issue with Control-M, it took us three or four hours to put it back where it should be. By migrating to Helix Control-M, our biggest success was getting away from the administration. Having Helix Control-M, which is a cloud product, allows us to use all the advantages of the job scheduler without handling the administration of our own servers.

If I compare Helix Control-M with what I had to do on Control-M on-prem, the process is very similar. The calendar has changed though. There was an advantage with Control-M that you could specify when was your new day load. Our new day load was every day at 9 AM in the morning. With Helix Control-M, we have to have only midnight as a new load because of the change of the date. It was a big challenge because we had to reorchestrate all the jobs to suit the new day load being moved from 9 AM to midnight.

Essentially, scheduling a job or creating a new job requires the same effort in both applications. The advantage of Helix Control-M is that I do not depend on a single agent to pull FTP profiles. All of them are centralized. It does not matter which agent I am using. I have access to the whole list. In Control-M, FTP profiles had to be added to the agents that were being used. Helix Control-M has made it easy to orchestrate data pipelines in production because now, I do not have to worry about the whole backend of Control-M. I am sure that it is up to date, and I can log in reliably, load jobs, and orchestrate them as I need.

I once tried to migrate Control-M to something else called RunMyJobs. Compared to RunMyJobs, I would definitely go for Helix Control-M.

In terms of our environment, we are a mixed shop. The majority of our products are on-prem. We have a Nutanix cluster in our data center, and that is where we host the majority of our things. We have maybe one or two devices on AWS. For Azure, I know that we have a license because it comes with our enterprise Microsoft 365 license, but I do not recall having any hosting there.

For migration, they have a migration tool that makes it very easy. You can run this migration tool, and it will export all your current jobs in a JSON file. It will try to import them on the tenant in the cloud on Helix Control-M. We faced a few challenges here and there because at the time we did it, some features were missing in Helix Control-M or were not supported, but they were supported in Control-M. We used to have dual endpoint profiles for the MSP file transfer or the ASP. FTP jobs have profiles where the server address, user password, or key gets stored. In Control-M, you could have a single profile with two endpoints. You could have Host A and Host B in a single profile. That was not supported with Helix Control-M at the time we decided to migrate, so we had the challenge of converting all those dual endpoint profiles into single endpoint profiles to be able to be imported. I know for a fact now that it is no longer an issue because they now allow you to create dual endpoint profiles in Helix Control-M, but it was a challenge at the time.

Fixing things here and there and making it compatible took about six months. Those six months were not just because of how hard it was to migrate. It was a combination of the challenges of migration and other tasks that we have not been doing because we could not afford to have a person dedicated entirely only to Control-M. Effectively, the time dedicated exclusively to the migration was two and a half months, but the migration was distributed in a six-month calendar because of other duties and tasks that I had to perform.

We got help from VPMA. VPMA is our reseller. We purchased a license of Control-M through VPMA, and they have support and all that. We get help from them. They helped us to run the Orchestrator or the migration tool from BMC. They told us where the odd points were, and then we went to do it on our own. We came back and reviewed them again and kept fixing them.

Overall, we had three people. We had one person from VPMA, and then there was me and one of my technicians to assist me.

It is not bad. The company can afford it, and it pays for itself. We have those jobs running automatically.

I would rate Helix Control-M a 10 out of 10. I like Helix Control-M.