I would rate the stability of AutoSys Workload Automation nine out of ten. We occasionally encounter minor bugs, but critical issues that impact the core functionality of the product are rare. I sleep soundly knowing the system is reliable.

AutoSys Workload Automation is ninety-nine percent stable. In a year, it's rare for my team to see issues with it, and that's even mostly due to the infrastructure. As a product, AutoSys Workload Automation is very stable, and robustness is one of its strengths.

The stability has been good in my experience. I don't recall dealing with bugs or glitches and it doesn't crash or freeze. It's reliable and the performance is good. 

The solution is stable. there are no bugs or glitches. It does not crash or freeze. It's reliable. 

We had a few issues, however, the issues were more on the infrastructure rather than with the application itself.

Stability of the product is excellent, I'd give a very high score to that. 

It is stable. 

What I like about the product is, we've had issues at the infrastructure level, regarding components that stopped seeing each other, or they got out of sync regarding, say, the database communications. Once the system reestablishes itself, you don't have to worry about if something happens in your infrastructure regarding, “Oh my God, my jobs are going to get out of sync.” The system does a really good job of piecing current status together and giving you accurate results. That's a good stability piece.

I rate AutoSys Workload Automation ten out of ten for stability.

Stability is very good. Like I said before, very little remediation needed, close to zero. We probably have two or three tickets with CA in a year.

The stability of AutoSys Workload Automation is good.

It is quite mature. It is pretty good.

ESP is rock solid. It is as reliable as it gets.

It has issues and is not entirely stable. For example, the graphical interface is not 24/7 for us.

When we first installed ESP, we had a few issues with the ability of jobs to have their status reported across sysplexes.

It's very reliable. I haven't had a lot of problems with it; working through the schedule; making changes; simulating; making things work.

It is very stable.

It's extremely stable. We put in the Canadian systems about three years ago, and we have not had an incident in the three years that has kept us down for more than a couple of hours.

Support has been really good. If we need to call somebody, generally they're on the line in a few minutes, and we get right into the diagnostics and we're set to go again. Extremely stable; the agents are perfect. They never give us a problem at all. The servers are getting awfully close.

Stability has been good since we took release 11.36. Before that, we had release 11.35. That was somewhat stable. We had growing pains because we switched over from a different scheduling tool.

Stability is rock solid. We haven't had any major issues with it, not even minor issues. It's been good.

It's pretty stable. In the eight years I've been doing this, I've had three major outages. One of them was self-inflicted. One of them, I'm not really sure what happened. The other one was, the database ran out of resources.

We're expected be up all the time, 24/7/365. I'm always available. Really the only time I've had outages were some sort of hardware failure. The product itself has always been very, very stable, and extremely easy to upgrade. We've been able to keep it up-to-date and make sure that we're able to take care of it.

One specific thing is, we've all moved to Oracle Exadata. I am probably one of the few systems that handles all of the database node rolling really, really well. It freezes for a couple of seconds, and then it comes right back. Every time they're like, "We're doing maintenance. We have to shut down nodes." I'm like, "That's fine; we're good. You don't even have to tell me about it. It will take care of it."

The system is very, very stable and reliable.

In terms of stability, it’s pretty much always up. The solution stays running. We do have our company-wide scheduled outages, but that's the only time it comes down at this point. We are working towards a better solution for constantly being up and CA is working with us on that. We just converted to version 12, and that's a step in the direction of keeping the solution up.

Stability has been very good.

It is very reliable. There is always been a bump here there, but it really does well for us.

The stability is awesome. We have not had issues in twenty years. It is just that robust, with the exception of new product/new version releases.

I would rate it a nine out of 10.

It seems pretty stable. We have had issues in the past and we have worked through support to minimize any downtime. Again, with the failover solution, we are able to stay working 24/7. 

It's very stable. It's highly redundant. It's, like I said, very recoverable, within the batch work and it's easy to use.

No issues. Once we went from version 4.5 to 11.0 and now 11.36, we have experienced great stability as time goes on.

No issues with stability.

So far, the stability has been great. We do have a couple minor issues with some of the agents, as far as release is concerned, but other than that it's a very stable product.

Stability is actually why we selected this solution, for being able to support high availability. Otherwise, we wouldn't go to a single instance of it across the company.

It seems stable, as far as I know. It's been around for awhile, so it's a good product. From our testing, it's been fine. We have a failover situation as well that we've tested; so it's worked fine for us.

We've not had any stability issues.

It is very stable.

Now, it has become very stable. In the earlier releases, I have seen some issues but with the current release, it is very stable. We've been very happy with this.

It's pretty stable compared to the older versions I would say.

It's very stable. Just the usual database problems, but the application, normally, doesn't have any problems at all.

Never had any issues, which is the main reason we use it. We don’t use other products for scheduling on the mainframe.

We have not encountered any stability issues with the supported versions.

One of the biggest strengths is the stability of the product.

The problem has not been with workload, we do have some server outages. Also maintenance times of other products. Workload Automation is dynamic enough to put jobs in pending or put servers offline, until we get ready to bring them on. As soon as they go back online, the server's jobs start rescheduling themselves again. It's a dynamic product, it's been stable and we've never had a real outage with the product.

We have it right now operating in something called dual server mode. If we lose one end of it or one processor, the other side takes over and it picks up from where it left off. It's an always up situation. If we have to throw it back to the primary then we take it down, do an amendments window, do a quick switch over to the primary and let it keep operating.

We never really miss a beat.

It's been stable.

We've had stability problems with the tool.

We had some problems at first. I guess every new system has some problems. That was ten years ago. We had a very good consultant from CA. He basically became a resident expert for us for three months. He basically enhanced the whole workload, and improved all those workflows for us. After that, it has been running very smoothly for us.

The solution is stable. 

We are able to view reports at any point in time

Stability is a 10 out of 10.

No issues.

I have not encountered any stability issues.

CA 7 is stable all the time.

As far as I can tell, it is stable. We are just transferring to the AE version, but we were using Automation Manager for two years before that. 

I can't recall the actual product failing in any way. 

There have been a couple hiccups along the way, but then I call support and we always iron out any stability issues. It is a 24 x 7 operation product and it's highly stable.

Stability is great. We generally have no outages.

Stability is awesome.

No issues with stability.

We have had no issues.

It's stable. It’s so busy finding maintenance windows, and we are currently going through exercises.

No issues.

It is very stable. We haven't had it go down yet so that's very nice, that's always good. We've been using it about 10 years now and we've never had any crashes.

We've had no issues with the stability.

It's very, very stable. We've never had any problems with it.

It had downtime, but Sevis has been very supportive in that aspect.

We run about 100K jobs on a daily basis, so this adds up to having more critical customers in terms of reliability.

Maintenance to the database must be performed to prevent stability issues.

We've had stability issues, but CA's pretty prompt about fixing things for us. We've had commonly-known bugs that are fixed after an upgrade.

It is pretty stable from my understanding. I haven't heard any complaints about a run maintain.

It is a fairly stable solution. I have not had any issue with it.

The solution is stable.

I have not encountered any issues with stability.

It is very stable and we haven't had any problems.

AutoSys Workload Automation is a stable solution.