Control-M SaaS

I have been using Control-M  on a daily basis. My main use case for Control-M  is the scheduling of processing of jobs. A specific example of a job I schedule with Control-M is OS jobs that run a script for backup.

I use Control-M day-to-day mainly for database jobs, OS jobs, MFT  jobs, file transfer jobs, and many more.

In my opinion, the best features Control-M offers are advanced scheduling and the processing of various processes at a scheduled time.

Control-M has impacted my organization positively by automating many of our daily based tasks. The automation has helped us as taking backup has become really easy; earlier, we used to do it manually, but now with the help of Control-M, we do it through automation.

Control-M is deployed in my organization on-premises. It is easy to integrate Control-M with other technologies. We have added AWS  cloud as of now, and we are trying to move all of the infrastructure jobs to the cloud.

Control-M has improved the way my organization functions by mainly automating all the backups and database jobs that we used to do manually. The implementation of Control-M has had a great impact on business-critical applications as it provides clear monitoring and troubleshooting for business-critical jobs within the SLA.

Everything is good regarding improvements for Control-M. There is no need for additional improvements.

I have been working in my current field for seven months.

Control-M is stable.

Control-M's scalability is great.

The customer support is good. My experience with Control-M's customer support was good, and I would say it was helpful and responsive.

I previously used Autosys. Before using Control-M, my organization used Stonebranch  because it was what we relied on for job scheduling and automation. I switched from Stonebranch  to Control-M because it was hard to understand, the scheduling was difficult, and it had fewer integration options with technologies.

We directly chose Control-M without evaluating other options.

I have seen a return on investment with Control-M as we need fewer employees because it is really automated.

I think the forecast is a feature to consider. I assess Control-M for building, scheduling, managing, and monitoring production workflows primarily through the Control-M GUI. The accuracy and reliability of Control-M's AI output are ninety percent accurate and reliable. My advice to others looking into using Control-M is to have it in their organization. I find this interview good and do not think any changes are needed for the future. I would rate Control-M a ten out of ten.

I have used Control-M  mostly for batch monitoring across three projects with financial institutions. The primary focus was on batch monitoring and checking the health of the environment in production or pre-production settings. In almost every project, we implemented jobs that check network connection from the mainframe and database health. I monitored and controlled many different processes with Control-M . I mostly used the Windows version, but I have also used the version that operates inside the IBM mainframe.

I did not use Control-M for audit preparation. I knew that other people in my company used Control-M for audit purposes, but that was not my case.

In the mainframe part, Control-M works smoothly and perfectly with no lag or problems. However, in Windows, it certainly has some problems at times. I do not remember which version I was using, but it has a lot of lag when you try to click for rerun. You click it, the job starts working, but the display does not show the information that the job is already running. Sometimes it does not have the option for confirmation, so it was annoying to click run and not see the job working or doing anything because of the lag on the screen. Sometimes you click rerun or click the rerun button twice, so you get a second run that you did not want, but because of the lag, you get the second run. This was the most annoying thing in Control-M.

Regarding what I would want improved, the tool in the mainframe would be very helpful with a report that you can follow directly in the path of the jobs. In the Windows version, you have all the graphics, so you can follow your path and see when it is going to run and how it is scheduled, which allows you to work more easily to change, hold, or make any movement in the job. In the mainframe version, it is complicated sometimes to follow the same path. You need to consult a lot of documentation for the planning of how the jobs are done, but you cannot find this information directly in Control-M in the mainframe.

I think the biggest thing I would like Control-M to improve in the mainframe is some way to track or follow the jobs a little bit more graphically, similar to the Windows version. I know it is very complicated, but that is my feeling.

I would appreciate Control-M being more complex when it has more features, such as when you are making the planning for the batch. The more complex your tool is, the more you can do for certain parameters or to put a job exactly between two different processes. You can accomplish more with a more complex interface and tools. I think probably other job scheduling tools get a little bit easier or offer a more light version and a simplified version, but I think not. At least for me, when I was making the planning or checking the batch, the more complex and different tools for the different situations that you have in the batch is the better.

I have been working with Control-M for about five years.

There are a lot of stability issues, and it depends on the platform. In the mainframe part, Control-M works smoothly and perfectly with no lag or problems. However, in Windows, it certainly has some problems at times. I do not remember which version I was using, but it has a lot of lag when you try to click for rerun. You click it, the job starts working, but the display does not show the information that the job is already running. Sometimes it does not have the option for confirmation, so it was annoying to click run and not see the job working or doing anything because of the lag on the screen. Sometimes you click rerun or click the rerun button twice, so you get a second run that you did not want, but because of the lag, you get the second run. This was the most annoying thing in Control-M.

I do not have a certain response for how scalable Control-M is because every time I have needed to use it, it covers everything and I think that is great scalability. However, I have never been in a situation in which Control-M is insufficient and I need a more powerful tool for scaling or anything related to that. So, at least for my experience, it is great.

In the two projects I have been working on, the maintenance was from BMC directly. I actually did not know that other people can give maintenance or support directly to the tool because I have always used it through BMC, which actually provides great support. It is very useful and they respond very quickly, so I never figured out that we would probably need local support.

In the last project, we had a BMC group who was in charge of us or they responded directly to the last enterprise, in the last company where I was, so it was very helpful. If we had any problem regarding Control-M or BMC, they have a team in the company ready to support us.

I used another one, but I do not remember the name quite well. It was a bit more for DBA, but I do not remember. It was also a job scheduling tool, but I do not remember the name quite well. It was about six or seven years ago.

The initial deployment was pretty easy. Even the one in the mainframe was easy to follow. The one in Windows is super easy to start working with, and if you have minimum knowledge about COBOL and how the mainframe works, you will be very easily walked through the JCL. Also, the feature that you can see the JCL in the Windows version is fantastic.

I am probably not the correct one because I have never done a quotation for the team to integrate the tool for the team or for any specific project, so I do not have information about this.

As I said, I used another job scheduler in the past. I do not remember it quite well, but right now, it is very complicated to see another job scheduler that is not Control-M because I am very used to it. Also, since it is the principal tool in the mainframe for job scheduling, it is also complicated for me to try to figure out another tool for job scheduling because it has a lot of options. It is actually a pretty good tool for monitoring the jobs or for my experience and in the areas where I have been working. So, at this moment I cannot imagine another tool right now because Control-M is actually all that I need for my work.

In the two projects I have been working on, the maintenance was from BMC directly. I actually did not know that other people can give maintenance or support directly to the tool because I have always used it through BMC, which actually provides great support. It is very useful and they respond very quickly, so I never figured out that we would probably need local support.

For my last experience, I would give a rating of ten because we have this team specifically for us. However, in the past with another project when we had to call BMC directly for support, I think that overall I would give them an eight. I would give the support an eight overall.

I give this review a rating of nine.

I primarily use Control-M  for scheduling jobs for scripts, batch scripts, and Linux scripts. Most of the writing involves service restarts on servers.

For data ops and DevOps processes, the requirement involves integration processes that need to be scheduled in Control-M , allowing management of cyclic processes for integration and continuous execution.

For building, scheduling, and managing production workflows, access is available through the URL or from the client software, Control-M Configuration Manager.

Control-M has made it easier to create workflows for both cloud and on-premises environments with features such as drag and drop functionality. This makes it simpler for users to create jobs and integrate them with dependent jobs.

Control-M has helped consolidate job scheduler tools with features such as SMS and mail capabilities, which other scheduler tools do not provide.

The best features of Control-M are particularly effective for Windows scripts and Windows servers, mainly for service restarts.

What is most appreciated about Control-M is that it is easy and reliable. Jobs that have been created can be accessed through the front end URL, where operations such as hold, release, and execution can be managed entirely from the user GUI front end.

Workflow orchestration is important for data ops and DevOps tasks as it makes scheduling scripts and managing various aspects of operations much easier through a single screen.

There are areas for improvement in Control-M as it carries some vulnerability points that could be fixed in any version, or it could be made easier for organizations to repeatedly install or update new patches with more stable versions.

I have been using Control-M for four years.

On a scale from one to ten, with ten being the best, Control-M's stability is assessed as a solid product at approximately eight or nine. BMC support provides robust backing, with new patches arriving daily and being integrated with previous versions to replace outdated updates and fix bugs while unlocking more features. No stability issues have been noticed during the four years of use.

Regarding scalability, based on the features and how they help with day-to-day tasks, Control-M can be considered scalable.

In terms of technical support, the focus involves creating scripts for service restarts on particular servers with the main target of providing support for automation services, automation management, job failure management, and managing the agent package and Control-M package.

The deployment of Control-M is easier than other tools. There are no critical tasks or activities required to deploy on the server; it simply involves setup and installation on the server with the tool ready to use immediately.

Regarding pricing, Control-M is not the cheaper option. License renewal is based on active jobs in a year, but it is cost effective. More features are provided compared to other tools at the same price.

When comparing Control-M with other solutions such as ActiveBatch , JAMS , and IBM, Control-M offers easier manageable operations for hold, release, and execution, which can be managed directly from its front-end URL. In its configuration tools where jobs are created, there are no difficulties encountered. Unlike other tools where dependency tools and jobs must be mentioned separately, Control-M provides direct drag and drop functionality with arrows. This is much easier than other tools such as IBM Task Scheduler or Jenkins .

Approximately 2,000 to 3,000 people use Control-M, including users from Axis Bank where all employees are using Control-M.

Control-M is recommended to other users by providing them a demo and showing them the uses, which helps them understand the benefits and features that Control-M provides that cannot be obtained from other tools. This allows them to rely on Control-M for their day-to-day tasks.

One point is deducted from the overall rating because Control-M carries some vulnerability points. The overall rating for Control-M is nine out of ten.