Control-M Reviews

The user interface is very easy to navigate.

The batch team is now able to run an average of 1,500 jobs per day with incidents automatically created and routed to the correct team if a job fails or has an error.

The process to apply patches and upgrades is cumbersome. It feels like there could be a simpler or more streamlined way to apply patches.

We have been using Control-M for almost a year.

The deployment went smoothly.

We are having issues with failover working correctly but we are working with BMC Support.

No.

Customer service tries to be helpful. They tend to shy away from many tasks that BMC feels falls into "Customizations". Anything that differs from the OOB is hard to get help with.

Most of the technicians seem to be highly capable.

The previous solution was no longer supported.

We used BMC for the implementation.

ROI is unclear at this time as the software has been in use less than a year.

Product is intuitive, you can start working with it and figure out the basics pretty quickly. The built in modules (examples: File Transfer, Database, File Watcher etc.) help eliminate custom built scripts which accomplish the same thing.

One big example I can think of is the availability of the Self Service plug-in. The non scheduling IT users or business users will actually be able to have insight into their automated job flows which is a feature that we never had before.

Quicker adoption of the newest versions of the product by all would help work out the bugs sooner.

4 and a half years.

I have not encountered any stability issues.

Mostly on our end, as we grow learning how to properly increase resources of the distributed servers and spread out the workload.

I've been happy not only with the customer service overall but also the speed with which I am contacted after submitting a case.

The level of technical support for Control-M continues to meet my needs.

CA Workload Scheduler, archaic, not intuitive, lack of features.

In house.

Price is based on how many jobs come into the scheduler each day (not executions) across all your different environments.

This evaluation was done a year or two before I started working with the product.

• Job scheduling in general
• Self-service
• Workload archiving

We rely on Control-M in our production environment. The automated notification in a case of an error has helped us a lot in reducing downtime and erasing errors.

Support for Z/OS output.

The company has used Control-M since the late 90s.

I did not encounter any issues with deployment.

The GUI had some problems in the early stages, but those seemed to have been solved.

I did not encounter any issues with scalability.

I would give customer service a rating of 8/10. They are very good.

I would give technical support a rating of 8/10. They are very good.

We did not use a previous solution.

The setup was straightforward.

We implemented via a vendor team and in-house. The vendor teams we had were excellent.

Ask for packages and bundles, so you might get more plugins for one price.

We did not evaluate any other options.

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.

Promotions between environments, as well as local, mass update, versioning, and self-service.

It is much easier to move and copy schedules. Versioning allows for quick restoration when an error is found.

It can definitely expand promotions, so that a single job can be moved. Currently you can only promote a job by promoting the entire table. In our environment we have very similar jobs in a flow but some are different so if i want to move just one of those jobs to all the other Control-M servers i would not be able to because it would overlay the entire folder. I want to be able to copy/move just a single job to prevent the overlay.

I have been using Control-M for 18 years.

I have not had any issues with deployment in any of the versions.

I can honestly say, I only had a stability issue once. Other than that one time, Control-M has been a very stable application.

No scalability issues at all. When we grew, we upgraded the server and it was back to business as usual.

I would give customer service a rating of 8/10.

I would give technical support a rating of 8/10.

We used another solution. Our company was looking to standardize across the enterprise.

The setup was straightforward.

We had a single contractor and our in-house team. She was very knowledgeable of the product.

The GUI for operators.

Scheduling has changed from basic to more complex as our developers get acquainted with the ability and flexibility of the product.

Report builder is cumbersome. Not all interfaces work out-of-the-box and there are a lot of adjustments to the product and configurations after installation.

We have used this solution for three years.

Connectivity to agents is a constant challenge due to security and Firewalls.

There were no stability issues.

There were no scalability issues.

Customer support is good. The support site, searching, and accessing knowledge modules, and accessing product downloads is very slow.

Technical support is excellent.

We were a manual shop, where operators ran selected routines through menus.

We had do perform several install configurations until we finally achieved the stability we required.

We work with a vendor group and they were very good. The BMC support contributions for design were flawed and we had to make several adjustments.

I am not sure.

There are various methods available for licensing, and we use the task/day load process.

We evaluated Compugen, CA, and Cisco.

High availability through software, supported by an Oracle RAC with ASM, is a valuable feature. In operation, it is fantastic.

My clients are happy; the comment that gets repeated is, "Control-M is a very stable tool".

The web console consumes resources to my "high" point of view. Thinking about a totally web management environment is an opportunity for improvement.

• Operator = 2 years
• Scheduling = 3 years
• Administrator = 3 years

Implementation was easy and quick.

We have not encountered any stability issues. BMC Control-M is very stable in any version.

BMC Control-M is an easy-to-run, scalable, robust platform or architecture tool.

Customer service is the best.

Technical support is the best.

Previously, I had version 8, and I migrated to version 9 because of its high availability functionality.

You cannot be an airplane pilot without education; with the right education and training, the solution does what it has to do and makes it fantastic.

Providers implemented it; they were excellent.

I cannot mention ROI.

A good product always has a cost. I think the cost supports the efficiency of the product.

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

Is a very good option for the WLA tasks within a company. There is a lot of information on the internet for it. Analyze the costs vs the benefits and if you have the option to invest in a solution that gives you automation of almost everything in IT, acquire it. You will not regret it.

There are no specific features that I could say are more valuable than others. The whole product is valuable to us.

• Ninety percent or more of the batch processing is now centralized into a single scheduling platform. This helps the support teams so that they only need to go to one group for scheduling and monitoring the batch processing
• The operations support staff only has one platform where they can monitor almost all of our batch processing.

There aren’t any improvements that I’ve come across with the most recent release. If I had to note one improvement, it would be that jobs already in the system for a given day could be updated en masse. This could be the same on the database where the job definitions reside.

I have used the product for sixteen years.

I did not encounter any stability issues.

I did not encounter any scalability issues.

The level of support from BMC has been very good.

We already evaluated CA’s offering at the time because we were already using CA-7 on the mainframe.

Other than creating the jobs in Control-M once it was set up, I was not involved.

It is task based pricing. It is based on the number of jobs brought into the system daily and any that remain in the system from prior days.

For example, if you have 2000 new jobs that come in in for a new day, and you still have 500 left from previous days, you will need to have 2500 task licenses to cover them. This is the case, even if those 500 jobs are daily jobs that came in during the prior day and have not yet been completed.

We use BMC’s Control-M software for our open systems and SAP batch processing. We will be looking at converting the batch we are running via the solution to the same.

I’ve never used the mainframe version of Control-M before, so I don’t have any opinions about it.