AutoSys is the default non-mainframe scheduling tool used across the bank.

AutoSys Workload Automation was implemented to centralize the control of all our diverse business and infrastructure processes at the bank.

I use AutoSys Workload Automation for enterprise batch scheduling, so for banking and retail values, I have multiple modules of applications. AutoSys Workload Automation is used to schedule and process jobs or automated triggers 24/7. The tool is for cross-functional and cross-application dependency management purposes.

Currently, we're just giving support to the client environment. They already have the AutoSys setup there.

Our client uses the solution for insurance purposes. Most of the jobs are command jobs, FTP jobs. This is the current use case. In the systems, they use some of the task applications, so in some of the SAP applications, for example, they use AutoSys.

We use it to run different jobs across different servers.

In our organization we have more than 30,000 automations we are running in this product. From an admin perspective, we have around seven to eight people working with the solution, managing it and dealing with the volume. We are a customer of AutoSys and I'm a company manager. 

It is being used for all the ETL processing and batch processing that we have in the enterprise. It is being used for automated file processing. We get the file from the mainframe.

I work as an engineer in an enterprise company. We have used AutoSys Workload Automation for a long time for batch processing and other automation things.

CA 7 Edition supplies our mainframe scheduling workflow. Automation.

It's performed well over the years. Obviously we've had CA 7 Edition for decades. It just performs its job day in, day out. Very little of having to remediate any issues with 7. Obviously there are issues with jobs eventually, but those are always developer issues, with how they've coded their JCL. But, otherwise it performs well and executes as scheduled.

AutoSys Workload Automation can be deployed on the cloud and on-premise. We have some file storage in the cloud.

We use AutoSys to run our scheduled jobs. In terms of the version, I am probably using version 14.

We needed to replace Allen Systems Zeke/Zebb back in 2000, since the product was not being updated anymore. ESP met our needs.

We run millions of jobs through it every day using it for financial transactions, banking, credit cards, PeopleSoft, payroll, etc. We use it for everything.

We primarily use CA Workload Automation AE for batch management processing throughout the organization.

Primary use is job scheduling. It performs admirably. It really does what it is supposed to do. I have been doing this for 19 years with AutoSys.

I use the scheduling product to support the Home Depot stores here in the United States and Canada, as well as Mexico. It works wonderfully as it is very robust.

Enterprise job scheduling.

We run Automator processes and applications, so we use AutoSys for batch processes. This is pretty much it.

It works well. It has its issues, but we work with support to resolve our issues and get them taken care of in a timely manner.

We use CA Workload Automation ESP Edition to monitor our batch jobs and workload, to process data, and in that processing of data, we make sure that we complete the jobs in a timely manner so that we meet our service levels. 

We also use the alerts within ESP to detect if there's a failure, if there's a long running job or, if there's an issue with the job, within the scheduler, that didn't trigger correctly, and things like that. So that's primarily what we use ESP for.

It performs, it definitely does the job because it's an enterprise type of software, so it's used throughout our whole company. We really liked it, and we applied it throughout the whole company.

Workload automation and job scheduling.

We use it for SAP job submission in our total environment. 

So far, performance has been excellent. It's been 100 percent satisfactory. We had a couple glitches in the beginning, during initial setup, but we've worked out everything, it's 100 percent satisfactory.

It schedules application jobs throughout the night for different companies, various companies that AIG processes: American General Life, Life and Retirement Services, and several of their legacy partners. We monitor the input throughout the evening, make sure the cycles are complete, bring up the onlines in the morning, and run jobs per request.

It's our enterprise workload automation scheduler. 

It performs pretty well, it's a pretty stable product.

We are using AutoSys Workload Automation for parent jobs and can create scripts for automation.

We use it for batch processing. We're a service bureau, so a number of our customers contract with us to use it for mainframe batch processing.

The product does all of our enterprise scheduling. 

We schedule overnight and daily jobs, mainly on a Cc&B system. We do file transfers from outside agencies, things like financial pledges and meter readings.

It performs very well. As far as the product is concerned, all of our issues are really with the system that we call rather than with the AE product itself. 

Batch operations. Running our insurance systems.

It is wonderful. It's been everything we expected it to be.

It's a cross-platform scheduler. Any kind of automation that we actually do is over different platforms.

Scheduling, mainframe, workload.

It has performed great.

Enterprise job scheduling.

SME for Cross Platform Agent installation and configuration. We have taken over ownership from the Unix Ops Team for installing, configuring, and administering the Systems Agents. I have also installed and stood up the Web Client. Currently, rolling it out to the general population of our company.

We use it as an IT process automation solution.

We use CA Workload Automation AE r11.3.6 to automate enterprise-wide scheduling and file transfers using an FTP plugin.

Usually what we end up doing with Workload Automation is, we have a lot of different jobs: different batch scripts, PHP scripts, everything that we need to run at specific times in chains, with banner-related instances, which means different database connections. We need all the stuff to happen, we need to know that it's going to happen, and if it doesn't we need to make sure that we get logs as to why. That's usually the general work case that we have.

It's performed very well. I think right now the one issue that we're having is we have a lack of documentation on it and the different jobs that are inside of it. But the platform itself is working very well.

A strong aspect of our current use case is to provide integration with the Zeke mainframe scheduler and enable cross platform job dependencies between the two worlds.

We have used batch job scheduling and ad-hoc jobs in DEV, QA, UAT, PREPROD, and production for tier-one sensitive applications.

We use it for running jobs of workload automation, specifically bad jobs.

In our case, it's just managing the day and night jobs of banks because we are supporting several banks in Europe.

The company I'm working for is an outsourcing company who provides solutions for customers. We host their complete environment.

My clients mainly use this solution for server workloads — work process flows around the deployment of servers, etc

My primary use case for this solution is for production.

The solution can be used for scheduling workloads.

We are a system integrator and this is one of the products that we implement for our customers. AutoSys is primarily used for scheduling CP jobs, file transfer, and other miscellaneous jobs.