What is your primary use case for Control-M?

We use Control-M for ACS and Azure services as it has inbuilt cloud integration. We have a product that works on government databases where we use data scraping and then integrate it with Azure and OpenAI. This integration allows us to process data and get insights. We also use AWS services to save the processed data in the AS.

We needed to automate our batch application workloads. We looked for a solution that perfectly matched our requirements. We use it as an orchestrator for our database, applications, data transfers, all data-related activities, and full automation of all processes.

Control-M is used to schedule jobs and run them regularly. It helps to automate processes and reduce manual effort, minimizing the risk of errors and enhancing efficiency. Our clients use Control-M for various use cases, especially when there is a need for regular, automated job executions.

We use Control-M for batch automation. Previously, all of our batch work was manual, but now Control-M has significantly reduced the need for manual intervention. As a result, our batch processes are now 99% automated.

We use the product as our primary application tool for workload automation. It helps monitor and manage client domains in terms of configuration daily.

We are using Control-M for task management, workload automation, and change management with our integrated framework for our existing application.

We have several SAP systems such as IBP, S4HANA, SolMan, etc. By implementing Helix Control-M, we wanted a tool that monitors different activities on these platforms and launches jobs. Each company has a different number of jobs. We have thousands of jobs, but we have selected the most critical jobs of the company that normally run in the early morning. We wanted a platform that allows us to launch the job, for example, from point A until it finishes, and then there is also the possibility of being able to launch another job from another tool, which could be a SaaS tool, such as IBP so that several jobs can be executed and finished in parallel. If there is a failure in the system, we send an email, and for much more important things, generate a ticket in a tool called SolMan so that the support team can attend to the case that has arisen due to the failure of a job.

Control-M is a job scheduler. You can schedule FTP jobs or use scripts within Control-M. You can also execute commands when necessary to schedule, or you can just run a script that is hosted on a server. Based on the schedule, you can orchestrate or automate jobs. You can set dependencies between jobs. You can correlate and create a sequence of your jobs and execute them in the order you wish. You can set the variables and options that you like. You can set the prerequisites and post-job activities after the completion, such as reports analysis, emails, etc.

We mainly use Control-M for integration in cloud environments like GCP and AWS. I'm an electrical engineer who mainly uses Control-M to access the files, documents, and data I need.

It is controlling our workflows, ingesting data, and then putting it up into our database platforms. In turn, those are consumed by our internal clients. We do integrate Control-M Python Client and cloud data service integrations with some of our cloud providers. We have pipelines going out to the public cloud and some pipelines that are internal. We have public and private cloud channels as well as on-prem. The expectation for most large financial institutions is that we will get 99.9% to the public cloud eventually. We want everything to be in OpEx as opposed to CapEx. We don't want data centers. We just want access to our data and to be able to turn it into information, which in turn, turns it into actionable items. Ideally, we would love to not support any on-prem or hybrid solutions, having everything be public.

We use the solution in Western Mutual Insurance Group's environment for the daily scheduling of around 11,000 jobs. Our number of end-users is in the hundreds, across 18 to 20 teams. We have three different physical locations as a company. Since COVID, we are a partially remote workforce as well, so we have multiple locations. It's essential that the solution orchestrates our workflows. Regarding processes like file transfers and data workflows, we want one source for that. We want one area where we can check and see how things are progressing, and Control-M is invaluable. Everyone has access in our environment to Control-M, and we all use it heavily. We utilize a ton of plugins in our environment. We started the transition into servers and are seeing what our license allows in that area. We try to take advantage of everything we can. We use Control-M to replace a lot of our manual logging of job data. It's been very valuable in terms of logs that can output alerts. I just did an audit earlier this year, and it was a swift process using the product. It took me less than a few hours, and without the solution, it would potentially take a couple of days to a week. We essentially have a nightly batch cycle. We process data overnight, so it's available for end-users during the day. Using manual execution, instead of Control-M, this nightly batch cycle would transition into a weekly or monthly batch cycle instead.

We use Control-M to monitor jobs on the endpoints. We monitor throughout the day to see which jobs fail. It helps resolve issues with the programmers. They know if they want to rerun, force complete, or hold a job. We work hand in hand with the programmers who have the final say on what they want to do with a particular job that requires action. Control-M is deployed across multiple locations, but I can't estimate the number of users.

I've been with the same company for 22 years. The use case started out truly as a batch processing solution. That was what we originally got it for back in the day to help us automate what was being done manually or being done through homegrown tools or scripts, et cetera. The use cases evolved through the years. Now, we use it to orchestrate workflows that are touching traditional data centers and that are going out to the cloud and bringing it back. From one spot, we have a single pane of glass. Like many companies, our systems are getting more complex and more diverse, with cloud and edge computing, containerization, et cetera. However, we have one place where we can go and look and see what's going on. If something happens, we can check what happened and where it happened. Today, we're dependent upon a lot of services and cloud technology that sometimes we don't know the ins and outs of. A big challenge is to make sure that we have certain things run daily or on a periodic basis. That really was the driving use case. We had a lot of manual tasks going on and if someone, for example, left on vacation, something may not get done for two or three days, a week or two weeks. This solution takes all that away. The main use case was to get away from having to stare at a system or a screen, and just let things run, let the workflows flow, and only be notified if there's something wrong. That was really a big driving use case.

It is an enterprise tool, and it is a critical one. It is used for scheduling all of our enterprise jobs and monitoring them. We have both cloud and on-premise applications, but Control-M is installed only on-premises. We have high availability as well as load balancing servers in the cloud as well as on-premises.

We use Control-M for managed file transfer in the enterprise manager automating database workflows. We're using Oracle Business Intelligence with a generic database like Microsoft SQL Server. Next year, we plan to use Control-M for AWS Natural and upgrade Control-M to Helix Control-M. We need managed file transfers between our servers in Key West and Orlando. Vast amounts of data are routinely transferred between servers for backup and snapshots. We will deploy it on AWS and Azure next year. We will also integrate Control-M with other solutions like Salesforce and COS, which is challenging because COS is a complicated legacy IBM OS. Some of our customers require Control-M to do managed file transfer and also COS conversions between IBM jobs. Anything that involves COS or OS/400 is complicated but doable.

We use it for our workload automation. We use it as a single pane of automation for our enterprise. We are currently using three different environments for three different productions. We have production data tasks, and we have multiple different levels spread out. We are currently using its most recent version. In terms of deployment models, they have both models. They have an on-prem solution, and they also have a SaaS solution. It just depends on what your company needs. They can take care of you.

We primarily use the solution for automation, orchestrating and automating the workloads, and being able to schedule tasks. Prior to Control-M, we were manually running jobs or there was either a scheduled task on Windows, getting Task Scheduler, or we'd have a script laid out that someone would have to run through manually on a daily basis. We learned about Control-M and felt that it could take over that process and have it automated, while also providing some monitoring and notifications so that if something did fail, we could easily be notified and keep track of it.

We mostly use Control-M for the data flow and reporting. We also have the monitoring in place to make sure that the business meets the requirements, and there is on-time delivery of reporting and so on.

We use it for workload automation and it's the primary application tool that we use. We use the Monitoring domain and the Planning domain daily, as well as tools and Configuration Manager as needed. Our product support team installs it in our Citrix servers so that people can log in to Citrix, choose the application, and use it. But I, and the team that does the batch scheduling, also have our own local clients installed on our machines.

The major use cases we have are batch processing and MFT. We are heavy users of the MFT plugin.

Our primary use case for Control-M is to order the jobs we have, like database entries and processes that need to be run in Unix or any other environment. With Control-M, we can run a set of flows at a specific time, like maybe on the fourth of every month or every second Sunday of the month.

We use Control-M to automate scripts that we use in banking and automotive use cases. These are our two big applications. We have a total of 18 applications running in Control-M now, and we want to move over approximately 13 more. Control-M is running in a virtual machine.

We use Control-M to provide business services to our customers. The use cases involve Hadoop, a lot of file transfers, and SQL scripts. In our business, automation is used for many things and we use a lot of the Control-M modules. For example, we connect to SAP, with databases, Hadoop, MFT, Informatica, and other technologies. What we do relates to many different business services in a retail environment. We have hybrid deployment; over the past two years, we have had a mix of on-premises and cloud-based implementations. Ultimately, we are moving to the cloud. We are using AWS, GCP, and Azure.

Control-M is the primary tool used in our department as an interface between desk jobs and SAP. I create and monitor the jobs in Control-M and that ties into SAP. At this point, we are using it as a batch scheduler, which is primarily used for SAP. We use it for everything financial, like payroll, because SAP is our primary ERP. Our system administrator uses Control-M when he is scheduling batch jobs.

Our organization is a bank, and all batch processes are in Control-M. We have installed it on a mainframe. It is an on-premise distributed system.

I manage the team responsible for the tool itself, the administration of the system. We have a separate team internally that does all the operations and scheduling facets of the tool. Our primary use case includes supply chain, payroll, accounting, information technology, pricing validations, etc. Most of the areas of the business have some facet into Control-M.

I am working with a beauty products company and we are dealing with supply chain issues. Most of the jobs in Control-M are through SAP. Right now we have it deployed on-prem, but we are planning to move to the cloud very soon. We are using Control-M Workload Archiving, Control-M Enterprise Manager, Control-M servers, agents, APIs, REST APIs, and Control-M Forecast. We use all the services Control-M provides except Control-M Workload Change Manager.

We use Control-M for file transfer and batch job scheduling.

We are using Control-M mainly to schedule our jobs and also for file transfers. We are now in the process of using Control-M to take some workload off our mainframe. We use it mainly for job automation and handling large chunks of data automatically. We have Informatica workflows, which make up about 50% of all our jobs. Then, we have all kinds of software on Windows and Linux servers. The file transfers are another big thing on Control-M. However, we are mainly using it to automate our in-house scripts, like monitoring and whatever needs to be done. We mainly use desktop clients. Some users are also on the web. Currently, we don't use the mobile interface at all.

In my organization, Control-M supports large services and data management. We are mostly using it to schedule jobs in applications, like Informatica PowerCenter, PeopleSoft, and SAP. We are using the desktop interface.

Most of my customer's jobs now run on Control-M, mainly on the finance side and for data management. Those are the core applications that we are running. We are using it as a scheduling tool. We have a few other applications that we are migrating to Control-M. Until about two weeks ago we were running on an older version of Control-M, so not many people were interested in migrating to it. But now we are running on an updated, supported version. So more applications should move to it. Control-M is deployed on-prem.

Because of security issues that we have, we are a private and public enterprise. Our main area is the lottery in Portugal. This is the most important business that we have. Also, because the money comes from the game, we need to invest it in social, health, and real estate areas.

A lot of the things we've done are just based on our needs, not so much because the product allows you to do it. Basically, I can do everything in Control-M. I mean, we've got plugins for Oracle, SQL, and Informatica, and I can go on and on and on. However, we don't use any of them as our developers prefer not to. A lot of what they do is they do the necessary connections through the batch files themselves. It's used for our daily batch. It handles all the batch processes and a lot of our maintenance processes. I would say most of it is file movement of some sort. A lot of it is daily processing, to get it in. Our data warehouse runs through Control-M. The big impetus behind it, when we purchased it, was due to the fact that the auditors wanted a more robust system and something that they could audit. Control-M gives you everything you need for that.

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.

We primarily use the solution for scheduling, including compiling for scheduling and financial scheduling across our countries. We use the schedule for 19 African countries and also in the UK, on the Isle of Man, where our corporate business is done.

Many companies are using Control-M in Mexico, two main companies from the retail sector have been using Control-M for around 15 years for all the administration of their processes.

We have a lot of projects with many companies, mostly in México. There are two main companies in the retail sector. The clients use this solution for their process orchestration.

We are a reseller. Our clients are from banks, retail, and pharmacy industries. We deploy versions 6, 7, 9, and 10 of this solution.

Our primary use case of this solution is to keep track of our help desk tickets.

We use this solution for automating workloads across traditional data centers, the cloud, SaaS offerings, and various other Enterprise software packages. It is allowing developers and product owners to create complex workflows that may encompass several different products or technologies and have it all visible, monitored, and managed from one place.

We use this solution for enterprise workload automation in the financial industry. We schedule and monitor hundreds of business-critical processes. We also leverage the Managed File Transfer capabilities of Control-M to handle our file transfers securely & efficiently. Most of our tasks also deal with databases, and Control-M's purpose-built module for the databases comes in very handy when handling database components. It adds value with its capability to execute tasks natively and bring more information to the output. The BIM feature is used to monitor the important set of jobs as a service and to proactively alert operations when it sees that some jobs in the critical path are failed or delayed. This helps a lot in maintaining our SLAs efficiently.

We use this solution to automate batch processing, create automated workflows to support various applications, and integrate various endpoints in the workflow to support business processes. File transfer between our company and partner is critical for us. MFT has provided this solution and we are now using MFT for internal and external file transfers.

We use it to control job submission.

We use it to schedule nightly batch jobs. We also have jobs that run during the day on a cyclic basis to provide up-to-date, real-time information for the company. I'm also pretty much focused on keeping things going. I'm the only scheduler at the company. We have about 4000 jobs in the daily schedule with around 42,000 iterations of jobs.

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.

It automates operations for all parts of the company. There isn't a part of the company that doesn't have jobs scheduled for Control-M.

We do scheduling of tasks and jobs in Control-M. The company has had the product for over 25 years.

We use it for our job automation, running jobs daily, monthly, and annually. So, it is all automation.

Our primary use cases for Control-M are scheduling, jobs, monitoring, and acting on job scheduling.

We have used Control-M mostly as a file transfer and in conjunction with Hadoop.

Relatively small setup for ETL jobs only. We do not use Control-M for enterprise-wide scheduling and automation.

It is primarily for batch job automation. It's working just fine.

Primary use case is automation, and it has performed fine.