Control-M Reviews

Control-M Virtual Terminal (CTMVT) for AS400: Because most of my customers are in banking, where their core banking processes run on AS400, Control-M Virtual Terminal helps us automate the interactive process on AS400.

This product helps my customers speed up the daily batch processes and also provides early warning if one or more processes are not running normally. For example, before we started using Control-M, one application took three hours to complete its end-of-day processes because many processes were waiting for human interaction. Control-M cut out the time waiting for human interaction.

Improve the capability to analyse the process output by making it more flexible. Actually its current capability is strong enough and I have no problem with Control-M implementation, but it would be great if the output analysis could accommodate functions such as arithmetic operations or regular expressions. Current capability only supports string matching.

Let me explain more technical details for this. For example, I have a job/task that has output:

Jobname : Test A
Result : Completed
Numbers of errors : 0

Currently Control-M has ability analyzing job / task output only with string / pattern matching operation, for example when output has text "Result : Completed" do something. What i mean good for improvement is Control-M has ability to analyze the output with arithmetic operation, for example i want when Numbers of errors greater than 0 do something.

To avoid misunderstanding, this is only for output analyzing, because Control-M itself has function to analyze return code number from the job/task.

I have used it for five years.

I did not encounter any stability issues.

I did not encounter any scalability issues.

The technical support is good. I've used them many times for technical issues. So far, their support has been good for resolving all the issues.

The initial setup is very straightforward.

The pricing is fair enough, considering its functionality.

I would recommend that others wanting to implement workload automation tools choose BMC Control-M as their solution.

We're not using it currently. We just did a PoC on it. We developed two or three use cases, and based on that, I had implemented the PoC.

For our use case, we wanted to schedule a job that will get data from the auditor and put it into Mongo. For that, we needed to do some calculations, and there was a whole workflow behind it.

The scheduling and management were really good. Monitoring was also better. It had a good visual presentation. It showed me charts and all such things. It was really good on that side.

It provided a unified view to easily define, orchestrate, and monitor all of our application workflows and data pipelines. We didn't have to go inside the box to find out what was happening behind the scenes. All that was easily showing up on the UI, which was a good part of it.

We used it for data transfer within our application workflows. It was very fast and secured.

Its cost should be improved. It is more expensive than other solutions.

Its architecture is old. AutoSys gives more flexibility.

I just started learning it. I saw the demo and started playing around with it.

It has old architecture, so it is sustainable.

Its scalability is fast.

I didn't use their technical support. 

Currently, we have a manual process. We don't have an automated process.

Its setup was straightforward. It was easy for us to host it up because it is a service, and we just hosted it up in the cloud, and it was there.

Its deployment was very fast. It took less than a day. I had to run some commands. I went through the documentation on BMC's website, and it was good.

Its cost is a little bit higher than other solutions such as AutoSys or DAC. For the demo, there were some plans, such as a start plan, scale plan, etc. Pricing was based on the plan.

We are also evaluating AutoSys and DAC. We have used Control-M only for PoC. We haven't decided whether we are going ahead with it or not. Its pricing is high, and its architecture is old. For our use cases, the architecture was a little bit older as compared to others. AutoSys gives more flexibility. 

Control-M's streamlining of our data and analytics projects didn't affect the rate at which we received actionable insights. The rate was okay, and I didn't see a drastic data speed change, but it was reliable.

I used its centralized connection profiles feature that enables you to store all connection profiles in a central database, but it was not really important for me. We already had a custom profile or custom configuration in our services for handling the connection. We were already doing that on our end. If we were not doing that on our end, the use of centralized connection profiles would be helpful for lowering the total cost of ownership.

I would rate Control-M a six out of 10. We only used it for PoC. We have not decided anything yet.

We are using Control-M for workload automation modules for day-to-day operations. We can click for visibility. After getting the information, we can minimize the workload, e.g., if I'm not available today, then I can automate the rescheduling for my operations. If some issues happen, like troubleshooting problems, Control-M identifies the exact error. So, it helps me quickly get into that area and troubleshoot the part.

With this version, we migrated from AFT to MFT jobs to help with SFTP connections. Before this version, AFT modeling was there. But, to utilize it, we would have to use a third-party system or software. When I moved to MFT modules, I didn't need third-party stuff so I could easily get clearance from the compliance team.

We are using the web-based version where we give individual users individual accounts.

We are using Control-M for day-to-day operations only. It is helpful for us in our day-to-day operations. It is a key in our financial sector. We are automating via Control-M in our treasury operations, including any evening updates. Control-M makes things easier and faster by helping our treasury operations go without any interruptions.

50% to 60% of our jobs are automated, like the scheduling part, and don't need manual intervention. The operator will monitor our jobs from that. This also minimizes manpower for updates, and we have already seen improvements in our manpower.

We have automated critical processes with Control-M, like SWIFT, which is a worldwide transfer application. We also use it for everyday backups. 

Control-M helps us achieve faster issue resolution. It lets us see the exact issue by providing error details. For example, one of our applications got stuck recently. We didn't know why it was stuck. When we went to Control-M, it said, "The Java memory is full." When the operator sees this issue, they can immediately call the system administrator to kill the process. This reduces time to resolution because it avoids escalation and contacting people unnecessarily.

If we make drastic changes to the environment, then we can see these changes end-to-end in Control-M. 

We use Control-M’s Role-Based Administration feature. it empowers decentralized product teams to manage their own application workflow orchestration environments with full autonomy. This feature is mostly under the compliance team. The feature is important, because without it, the day-to-day operations of the bank would not run. It is managing all our on-premises jobs, like application cleanups. We are doing everything via Control-M.

The use of Role-Based Administration definitely eliminates the need to submit tickets or requests to the Control-M administrator. The integration part of the Role-Based Administration has become very easy for us. We can integrate directly with Active Directory. This makes it easier for us to do things.

The MFT jobs are a valuable feature for us.

Control-M provides us with a unified view, where we can easily define, orchestrate, and monitor all our application workflows and data pipelines. It centralizes things and does automatic job scheduling.

We use Control-M to integrate file transfers within our application workflows. Nowadays, we depend on this feature for all our applications file transfers. This feature is helpful when you need to manage complicated documents or other files.

We have been using this product for more than seven years.

I haven't seen any issues as of now.

One or two guys are enough for each shift. Daily, there are three or four guys who maintain it.

Scalability depends on the cost. Expanding can be very costly.

Whenever new things come in, we request them to be moved to this solution.

We only use our partner's support.

The initial setup is straightforward. It is relatively easy to upgrade the tool.

We moved everything, including the database. Now, it is the heart of our operations.

We have a partner company. However, we are managing it 90% of the time. 

Our experience with the partner company has been very good. They are very experienced with the solution.

The cost of the hardware is high. Because you need to license each job, it is costly.

We use other tools to streamline our data and analytics projects.

For the past two year, we have blocked mobile access per our cybersecurity guidelines.

I would rate this solution as eight out of 10.

My client is one of the largest banks in Pakistan. They are using it for their international branches as well as for branches all over Pakistan. They have around 16 or 17 international branches in Gulf, North America, South Africa, Seychelles, and Singapore.

The operation window of our client is 24 hours. At different locations, they have to perform different activities. If you are working in a banking environment, the main activity is at the close of business, which is monitored by Control-M for all of their branches. Instead of having 20 people, now they have three to four people who are monitoring the tasks. Control-M is taking care of the close-of-business monitoring tasks, such as backups, etc.

It has multiple features. You can plan your execution in Control-M. It provides one single window where you can define workflows regardless of geographic boundaries and platforms. A batch process can be executed from this single window.

It provides insights into your processes. Your business people will know what process they are running and what is the state of the process. Instead of knowing that they're not going to meet the SLA the next morning, the business people immediately know the changes in their process.

Control-M is very easy. I can tell a non-technical person that this is how it works, and he would be able to easily understand it. Business people can understand the methodology of Control-M and the intuitive features that it has. It has a fantastic graphical user interface and is easy to understand. You just have to drag and drop but in a very intuitive way.

Monitoring features are also good. It has different color coding schemes, which can help you to understand the status of your workflow. An operator who is not that technical and is just monitoring the status of the application can see by color-coding the status of a process. If anything goes wrong or a process is stuck, it gives you a hint. You can just right-click and see the logs and the output. Even if the system is not right there in the data center and is located somewhere else, you can monitor it right from there and see the workflows.

A Control-M on-prem license is based on the number of jobs, which is the number of tasks a particular customer wants to have. These tasks have to be run within 24 hours window. For example, if you have a license for 100 jobs, you can run a maximum of 100 jobs in a 24-hour window. If your operations could not run 10 jobs, and they ran only 90 jobs, they just carry over to the next day, but the next day, they will have 110 jobs. Control-M asks you to buy those 10 more licenses because you were out of compliance in terms of the number of licenses. This is something that needs to be indicated in Control-M GUI so that customers know the number of licenses they're going to use in this time window. 

Their support and documentation should be improved. I am not that satisfied with their customer support. Sometimes, they don't have the answers. Their documentation is very poor. It is not well written, and it is not in a very logical manner.

You can use it on Unix, Linux, Windows, and AIX, but it needs some improvement on iSeries. It needs a built-in mechanism inside the system to give you an option to restore from the last point of failure. If a process crashes, the Control-M needs to have a mechanism in iSeries where the process can be restored from the last point of failure.

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

It is stable.

It is scalable. Its licensing is not based on the number of users. Its licensing is based on the number of tasks that you're using. You can have as many as 100 users, but in the environments that I have seen, there were between 10 to 20 users. You have administrators who can design the workflows, and you have operators who just monitor the results.

I am not that satisfied with their customer support. I would give them a 4 or 3.8 out of 5. Sometimes, they don't have the answers. 

Their documentation is not that clear. It is not well written, and it is not in a very logical manner. They just put information in the documentation, and you have to find things. It is not easy. If you are new to this product, you have to spend some time to understand what is it, and when you go to the documentation, most of the pages have a few lines, and then they ask, "Did it help?" It actually doesn't help. There is not much documentation, and it is not that clear. IBM products have very clear-cut, systematic, and guided activity sort of things on the website, whereas BMC's documentation is very poor. It is not that eloquent and clear.

It has some complexities because it is a complex environment. It has a three-tier environment on-prem, and one has to establish a secure connection between these entities, which is not easy. The first one is the master server console. The second one is the main engine that determines the scheduling process, and the third one is the agent. Agents have to be deployed on different client machines.

I would highly recommend this product. Its setup is complex, but once the setup is done, it hides away all the complexity. The end-user will have a very clear and intuitive interface to define the workflows. It is very easy to use.

I would rate Control-M an eight out of ten.

We use it to handle most of our batch processing and all of the transactions that we do on a daily basis. It's a large financial institution which handles quite a bit of processing on an individual basis, and we both mainframe and distribute it.

We are receiving files from another system, then we use the File Watch Utility (because we have no view into the other system and how it works). However, when files arrive on certain servers, we're able to pick them up and trigger further downstream processes from them.

Control-M has improved application reliability and the SLAs in our company by quite a bit. You can see if problems are coming. If we have an SLA in a couple of hours, we know well before that couple hours if processing is behind, and it allows us to take some preventative action.

• The ability to go from one system to another.
• To be able to trigger something off of it, yet we are still on a mainframe for our batch processing. 
• To be able to trigger something from the batch, then distribute that back and forth.
• The solution has always been very streamlined. 
• Ease of use
• The BMC customer service behind the tool has been most valuable.

They have Workload Change Manager, and I would like to see a little more of that. Being in the business that we're in, there's a lot of hesitance. We are very hesitant to change things in the banking industry. It isn't bleeding edge by any means. Getting people to buy into things is sort of the hard part, because everybody wants their money to be handled properly.

The solution is very stable. We have our mainframe as well, which has not been bad at processing, and it's pretty stable. With the application of Control-M, we've seen minimal downtime. If there has been downtime, it hasn't been with the application. It has been with the hardware, and you can't get around that part of it.

It is a good application for scaling. We're able to scale pretty fast, whether we're building a small or large set of jobs. When we have new servers being built, agents are already put on them, and we can work pretty quickly without having to step back to handle it.

The technical support is extremely helpful. You can provide just a basic description of your case. If they need to, they can log onto your system. They can shoot you into the right direction, whether it's a knowledge article, community forums, etc. Overall, it is great technical support. Though, it has been a while since I've had a technical call with them.

Sometimes, with technical support, they will take feedback, but you don't know where that feedback goes or if it proceeds along in the thought process.

They did previously use CA-7 for the mainframe. They switched for the ability to use both distributed and mainframe from one central point.

We did recently migrated to version 9.0. Our organization did use a reseller. Our national IT group manages the application. We are just the user of it, so I wasn't involved in any of that.

It has absolutely saved us time. It has made us more efficient. As far as the processing between systems, we don't have as many people. They have been able to focus on other efforts, because we have been able to automate more stuff with Control-M.

Do the trial demo. Reach out to others via the BMC community forums. I don't believe a license is required. It's just a sign on. There are multiple vendors who are resellers or BMC partners who will provide you with input. All you have to do is ask. Feel free to ask others. The people who I have dealt with have always been forthcoming with information. They will tell you what they see as a plus or minus.

It has helped us streamline some things in IT operations, which is probably a slight improvement. We haven't seen any negative impacts.

I've used it in different forms and versions for about 20 years now. I'm pretty familiar with it from an operations standpoint. The tool itself is a ten, and the customer service behind it has made that even more so.

It's worked pretty well. I haven't been able to take a lot of advantage of some of the new features, so I haven't been able to expand on those. For what we do now, it chugs along pretty well.

Self Service for repeatable, low impact workload automation processes. BIM for SLA management. GUI client for visibility into the enterprise schedule. New to v9, the automatic Agent upgrade features have been quite helpful too. Relatively easy to perform upgrades and fix packs.

Offers a single pane of glass to our enterprise batch\workload automation environment. Allows us to empower business users to execute their own processes on demand through Self Service. We're able to proactively predict system availability thanks to BIM. Our 24/7 staff have all the right utilities to monitor and manage the schedule.

Advanced File Transfer (AFT) has limitations that cause us to use a bit more licensing than we feel is appropriate.

Almost 13 years.

No

Not usually.

No.

9/10 - Everything is typically great with customer service.

8/10 - After getting through the basics with lower level support, we tend to get problems resolved after proving our issue is "real" and we get put in contact with a technical SME.

We've used other stand-alone products that have their own scheduler while we've owned Control-M but have migrated away from that model to give ourselves the best visibility to the enterprise environment. We've broken down the silo and migrated all scheduling into Control-M.

We've been using the product for quite a long time, so reviewing initial setup wouldn't be applicable to current times. I feel the setup of v9 is quite straightforward.

In-house.

BMC does NOT have a great licensing model from my perspective.

We've evaluated many other products along the way... Just about every other major competitor in the market.

The entire suite of Control-M is valuable.

It is easy to use and most of the add-on features are available.

In a big environment, there is the need is to have easy access to the client.

I have been using Control-M for many years.

I have no particular issue to report.

I have no particular issue to report.

I have no particular issue to report.

Customer service is excellent.

Technical support is excellent.

We were using a different solution. We switched for less cost and for more benefits.

It is easy to set up and has clear information and support.

The implementation was done by an internal team.

It isn't related to my function and I do not have any specific details.

We evaluated other options, but now we are consolidating all environments to only use Control-M.

From my experience with the last version, you are able to manage everything. The conversion tool can offer an easy way to migrate jobs from another tool.

Control-M has a huge number of features and utilities that assist users in monitoring their schedules, and developers to build schedules that interface with many technologies. Here are some that stand out:

• Cross-platform support. A Linux job can be dependent on a Windows job, which can be dependent on many other flavours of hardware/software. Your batch is therefore managed by a single tool, allowing you to monitor your entire flow.
• Great GUI. Easy to navigate. Customisable. Status at a glance.
• BIM (Batch Impact Manager). Proactively monitors a batch flow, against a pre-defined OLA/SLA and alerts as soon as an exception occurs that might threaten the target.
• Automated error handling. Depending on the exit status of a process, automated actions can be defined that might circumvent the need to callout.
• Forecast utility. Particularly useful after making changes to a batch flow, to see what impact those changes will have.
• Reporting utility. Generate reports for the business to track batch performance, usage, and so on.
• Mobile App. Business users can track the progress of their own batch flow, on the go.
• Control Modules. These allow you to define jobs that interface with databases, SFTP, SAP, and so on, directly, via secure connection profiles.
• Too many great features to list!

Previous scheduling solutions were platform specific, so when the overnight batch processes crossed between technologies, manual intervention was required. This was time costly and meant that it was not possible to get an overall picture of the flow/progress.

The ability to work offline would be an improvement. It is sometimes inconvenient that you cannot load and work on a schedule – unless you are connected to a Control-M Server. For example, when you are away from the office or on a train…

When you launch the application, the first thing that you need to do is 'log in' to a valid Control-M server. It would be nice if there was an 'offline' mode that would enable you to launch the application and then work on a batch schedule that can be 'checked in' to the appropriate server when you are next connected. This would enable users to be productive in environments where there is not a reliable network connection.

I have been working with Control-M for 20 years, using many versions; three years with version 8.

No.

I have not encountered any stability issues.

I have not encountered any scalability issues.

Technical support is sufficient. BMC have a group of specialists in Tel Aviv who will advise on the best solution to any issue. It can be a little painful, trying to send huge log files to the vendor, but they are very helpful.

I have had limited experience with Windows Task Scheduler, Cron and Autosys. These are very basic scheduling tools that do not offer anywhere near the functionality of Control-M.

Out of the box, most clients will be fine installing Control-M with all default options. You have a choice of the packaged PostgreSQL database solution, or you can opt to use MS SQL It is therefore a relatively simple setup.

Control-M is expensive, but you get what you pay for. Talk to your account manager and discuss licensing options.

Before choosing this product, I did not evaluate other options.

Do it.