Control-M Alternatives and Competitors
Read reviews of Control-M alternatives and competitors
Sr System Engineer at a financial services firm with 5,001-10,000 employees
Real UserTop 5
Feb 5, 2020
Alerts when things are falling behind schedule, or something unexpectedly fails, enable us to jump in and address an issue
What is our primary use case?We use it to manage our batch processing. For us, it came in as a replacement for a lot of different systems running crontab. In our case it's primarily for Unix/Linux systems that don't have their own mechanism for kicking off all these batch processes. It's the coordinator of all of our background processes and batch jobs that are running overnight and during the day. We use it to kick off custom Unix/Linux scripts that will launch our application processes. It's almost entirely Windows and Linux shell scripts that it's kicking off.
Pros and Cons
- "The first, big thing that we got out of using Tidal Workload Automation was having a centralized view of the status of all of our batch processes across all these systems... We can look into the schedule at any given time and see if things are running on track or if they are falling behind. We can also see if something failed."
- "Their software installation and update process could use some improvements. I'm pretty sure they're working on that, but that's definitely an area where it could be streamlined a lot. There's still a lot of manual work that you have to do with the schedule when you deploy masters or do the agents."
What other advice do I have?The big thing I would say to someone who is deploying this new, aside from having a naming standard and the structure, would be to get their security groups right, up-front. That is a pretty big one. Set your owners and who your users are going to be. Think about how you are going to structure it from a user point of view. We have two core systems here. One is for our loan origination system and the other is for allocating leads and directing leads, and they both rely on Tidal heavily. If the scheduler were to shut down for some reason and we couldn't run it, it would have a huge impact on our…
Senior System Analyst at a insurance company with 5,001-10,000 employees
Real UserTop 20
Nov 30, 2020
Native API calls are very good and very easy, enabling us to tie in to a large range of solutions, including Tableau and ServiceNow
What is our primary use case?We have roughly 8,000 jobs that run every day and they manage anything from SaaS to Python to PowerShell to batch, Cognos, and Tableau. We run a lot of plans that involve a lot of constraints requiring them to look at other jobs that have to run before they do. Some of these plans are fairly complicated and others are reasonably simple. We also pull information from SharePoint and load that data into Greenplum, which is our main database. SharePoint provides the CSV file and we then move it across to Linux, which is where our main agent is that actually loads into the Greenplum environment… more »
Pros and Cons
- "The most valuable feature is its stability. We've only had very minor issues and generally they have happened because someone has applied a patch on a Windows operating system and it has caused some grief. We've actually been able to resolve those issues quite quickly with ActiveBatch. In all the time that I've had use of ActiveBatch, it hasn't failed completely once. Uptime is almost 100 percent."
- "A nice thing to have would be the ability to comfortably pass variables from one job to another. That was one of the things that I found difficult."
What other advice do I have?My advice would be to jump on it straight away. With the ease of installation, the expandability or scalability of the product across multiple servers with different agents, the ability to not only use Windows but Linux as well, and the fact that you can build complex plans that have multiple constraints, multiple types of scheduling, and multiple types of alert mechanisms, it's highly expandable. You're going to have a lot of fun with it. It's highly flexible and easy to use. In terms of what we can do, we still haven't gone to the Nth degree of what we can't do with ActiveBatch. It's…
Director of Production Control and Operations at NYSDOT
Dec 17, 2019
Gives us the ability to schedule dependent jobs across different mainframes
What is our primary use case?We chose OpCon to replace a scheduling package that was controlling approximately 10,000 batch jobs every day. So the main purpose of OpCon, for us, is to replace an aging homegrown solution with a more advanced scheduling product that has more bells and whistles. We use it for job control. We have Enterprise Manager on desktops communicating to agents that are on our mainframe computer. We haven't yet completed the conversion. We are about 30 percent converted right now. We still running 70 percent of the work through our old scheduling package. We have two main shops. One of them is an… more »
Pros and Cons
- "There are three features which are valuable: the automated calendar functions; the notification process for failed jobs or unscheduled events occurring, via email and text messaging; and the ability for the scheduling package to communicate across multiple platforms."
- "The calendar interface and the frequency interface is a very powerful, yet complex, section of OpCon in which all our staff have made mistakes. They have implemented what they believed was logically correct and then afterward discovered that their logic was flawed because OpCon did it a different way. That part, which is incredibly useful, is also incredibly dangerous. The interface or the ability to directly do more functions within the frequency definitely has room for expansion. As good as it is, it can be a lot better."
What other advice do I have?I would highly recommend an onsite evaluation of OpCon that has already been deployed and seeing it fully in action, so that you could be better prepared to ask the right questions prior to getting it. All we saw was a remote demo and that, to me, was a big mistake on my people's part and probably SMA's part. We never got to see it in action so we didn't know all the right questions to ask. My biggest lesson in using OpCon is that I wish I'd been more involved at the beginning of the project, when they were estimating the need for support. We should have budgeted for a different type of…
IT Manager at a manufacturing company with 10,001+ employees
Real UserTop 5
Feb 25, 2020
Workload automation that helps track productivity and progress across platforms
What is our primary use case?The tool is managed from offshore by another company. The primary use for it in our company providing support to our main client who is a large beverage company that needs the product to manage operations. I just act as the support interface between the client and the offshore team starting at the time I took this position as a global manager for workload scaling. I found out about this product someplace and how we could put it to use. We have been running it ourselves and with our client for a long time. It is also a part of our company's application or solution set. The use cases for my… more »
Pros and Cons
- "The technical support is great, the product is easy-to-use, and it is stable."
- "It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."
What other advice do I have?The advice I would give to others considering using Workload Automation depends on the necessity and the reality of their requirements. It depends on the complexity of the jobs. Depending on that it may be interesting to use Tivoli because it is a good tool. It is a good application to use to run workload tracking. On a scale from one to ten where one is the worst and ten is the best, I would rate this product between and eight and ten depending on who is using it and for what reason. I think it is quite good so I think it deserves a nine. Additional features I would like to see included in…
Workload Automation SME at a retailer with 10,001+ employees
Real UserTop 20
Nov 3, 2020
It is scalable and stable, but it is expensive and needs a better dashboard
Pros and Cons
- "The Zero Upgrade feature is the most valuable."
- "Its dashboard can be improved. In version 12, they have already moved to a web-based interface from a UI. We are looking into this feature now. We are also looking for available APIs that we can use to interface the engine into our other systems. There should be a subservice facility that we can use to interface with Microsoft Teams and send out authorization on job executions. We have seen a feature like this in other products that we are looking into."