Reviews (1-25 of 47)
- Using AFT, sending files to customers is automated and can be customized for success, failure, etc. allowing visibility into the process for all involved
- Self Service is a powerful addition as it allows jobs to be setup and available to users via the web. You can have granularity into the jobs then as access is assigned to users based on their roles, allowing the ability to order the job, or maybe even just monitor the progress.
- Workload Change Manager is going to give us the ability to allow our developers to implement Control-M into the design and coding stages instead of after the fact. This will save time as they will be able to see the end results right away and make adjustments if necessary without having to wait for a scheduler to make the changes. This also allows us to promote from lower environments with some oversight and control. This will be the biggest takeaway for us moving to v9.
- The ability to set default view settings would be a nice add as it would allow the admin to better control the environment for each user role/level of access. This would be especially helpful when it comes to differing environments (dev/test/etc.)
- The licensing structure could be better laid out. Typically when purchasing a licensing suite, you get the full offering for that product, but that is not currently the case for Control-M.
- The ability to setup multiple site customizations and associate them with the access level/role of the user would be something I would prefer to move to the top of the list of things to be done differently as this would allow better customization for web access by eliminating things that you don't want that particular role to have access to.
- Provides visibility and monitoring across all jobs/platforms.
- The UI is user-friendly and requires very little training to obtain the status of key business processes.
- Control-M for Hadoop enables Hadoop specific workflows to be developed, scheduled, managed and monitored along with other enterprise workloads, all in a single solution.
- Control-M AFT allows us to schedule and track FTP transfers any other batch job. Provides the ability to transfer files securely either via SFTP or FTP with SSL and manage encrypted FTP credentials in a single centralized location.
- The upgrade process could use some improvement as it is somewhat complex.
- The Reporting function can be improved.
- Control-M AFT could have better diagnostic tools or messages to aid in troubleshooting connection errors.
- The UI is easy for the business to use to receive an instant status of the processes they care about.
- Control-M works well in connecting to and running processes on many servers in our network.
- The proactive notification of a process that may have issues is very nice to have.
- We have not defined a process to move processes across multiple environments. That would be nice to have.
- Dependencies between the jobs of various tools/technologies. We run Informatica, .Net, SAS, SQL - all kinds of jobs and Control-M works very well with each kind of job.
- Email alerting facility after completion, failure; ability to retry jobs.
- Ability to run a job multiple times a day.
- Cyclic jobs. Dependencies have issues if cyclic jobs fail and we rerun. Failed cyclic jobs do not show up in red color.
- Old jobs which did not run. Control-M should change the color of yesterday's ordered jobs vs. today's jobs.
- Control-M provides strong job auditing of who does what, when, where and how.
- Multiple jobstreams are managed for multiple environments simultaneously from one enterprise server.
- Since we have several OS and database platforms worldwide, this one scheduling application can handle all of it.
- Control-M is relatively easy to learn and engage with at user levels. Job loads and forecasting are relatively intuitive.
- Enhanced GUI functionality has been improving over the years, but screen design can lag behind depending on the version in use.
- Speed of operation is reasonably good but can always be better. Many new features have been added which require more server resources for efficiency.
- Control-M provides the functionality required to run a lot of jobs in a short period of time. There are times when more than a thousand jobs are pushed through the system in a very short timeframe and Control-M is able to manage this workload with no problem.
- The GUI interface used for monitoring and interacting with Control-M also is a big advantage when processing so many events. This provides real-time viewing and allows for quick responses from our technicians to act and recover issues. This is very important to our business that requires very little down time without major impact to our customers.
- The history information Control-M captures and saves has been a big advantage when researching issues. This information is also used for quality control when making changes as well as satisfying audit requirements. This data is also used to manage capacity and performance of Control-M which has a long history of stability. This is important for many reasons but the number one reason for FIS would be the success it brings to our business and our customers' business.
- A key scheduling function that was omitted from Control-M is dataset triggering. BMC included this function as part of Control-O which requires a separate product to manage dataset triggering.
- Control-M product release upgrades are very complex and requires extensive knowledge for Control-M and the OS environment.
- GUI presentation
- Operations can identify job flows and realize business impact visually
- Provides control within operations
- Processing streams can be halted immediately during a failure, without intervention and eliminates cascading issues and problems
- Self-Service access
- Providing browser access for all our users enables them to view their processes and realize interfaces and impact that their processes have on other systems. User access and viewing reduce delays during problem resolution as it enhances communication and expedites root cause determination.
- Direct product interfaces using modules
- DataStage job schedules are fast and are easily configured as well as Database maintenance functions which can now be linked to before and after DB activities
- Setting up Site Standards needs some enhancements
- More robust functionality for field validation is needed, such as only one Quantitative Resource rule can be applied on multiple QR's defined in a job. Therefore giving warnings on QR standards because each QR must match all QR rules
- Reporting structure is a bit cumbersome and needs a more effective interface. Jumping from panel to panel is not very effective.
- Connection profile password management is tough to maintain. Each entry must be manually updated every time there is a password update. Since our policy is that all system passwords must expire after 180 days and we must be included in all application related password updates. Unfortunately that also is an issue where the Control-M administrator is globally aware of those passwords, which should be held confidentially by each separate group
- The UI is easy for the business to use to receive an instant status of the processes they care about.
- Control-M works well in connecting to and running processes servers in our network.
- The proactive notification of a process that may have issues is very nice to have feature.
- Consolidates scheduling for multiple technologies in one place.
- Upgrade process is very difficult and time consuming - I think it needs improvement.
- Documentation is lacking -- would be nice to see some redbooks.
- Ability to handle interactions between mainframe and Open Systems jobs.
- Web interface for developers.
- Numerous options when scheduling jobs and tying them together in a workflow.
- Upgrade process is very difficult and time consuming.
- Web interface is still clunky and could use upgrading.
- Documentation is lacking -- would be nice to see some redbooks.
- Notifications of failures, very flexible and customizable
- Its GUI design
- Can be used easily for a variety of platforms in one single environment
- The GUI for version 9 is a bit slow and has few bugs
- SSL support needs a lot of improvement on the client side and also, managing certificates between the Control-M server and the agents
- I miss the option Playback on the Self Service
- Consolidates scheduling for multiple technologies in one place
- Provides visibility and monitoring across all jobs
- Basics needed to create typical process flow are easy to learn
- Company aggressively transforming and upgrading the tool
- Tool allowed to securely separate "tenant" applications and their development teams
- The peak use pricing model compares unfavorably to the typical use model (that averages across type). It penalizes organizations with an uneven workload.
- Control-M enables us to automate our workload with ease.
- Control-M helps us eliminates the needs for programmers to customize scripts to execute jobs according to sequence and dependencies accurately.
- Control-M enables us to perform RCA (Root Cause Analysis) in a timely manner through the logs, sysout and playback of events.
- Control-M provides us the flexibility to integrate our various used applications within the organization and connect other streams of jobs for continuity of processing.
- Flexible tasks or jobs pricing charges.
- Version upgrade should be made as simple as possible as it becomes overwhelming.
- RFE (Request for Enhancements) should be prioritized.
- Control-M is very stable. It is rare to have any issues with the application.
- Dealing with dependencies is handled very well. Dependencies are easy to set up whether they are on the same server or across platforms.
- Alerting is also a strength in Control-M. It has a built in tie in to the Remedy system which allows ticket creation to be handled easily.
- I would like to see some improvement in handling conditions from previous days.
- I would like to see some improvement in being able to send out alert notifications on jobs that have not started past the new day.
Application-wise we use it for Data Warehouse, PeopleSoft, file transfers, various banking apps, direct DB jobs (Control-M for Databases), Cadis, Tableau and managing various in-house apps.
- Control-M Advanced File Transfer is a very useful add-on, allowing for a wide variety of file transfers to be configured "out of the box" and then used as part of the standard batch flow. This module is not included in the base price but is available at a relatively small additional cost.
- Using Control-M's GUI (the Enterprise Manager) allows for efficient management of the enterprise and can tie up a lot of "loose ends". Often the first point of tracking problems is to check with the Control-M guys!
- BMC is definitely moving the product forward, the new module "Application Integrator" is very helpful in building and deploying your own bespoke Control-M jobs and allows for closer and more secure integration.
- Although Control-M does open up the enterprise in an operational sense, the security settings (should you choose to implement them) are robust.
- The reporting provided with Control-M could have more functionality, Many users end up creating their own reporting based on the Control-M DB. I believe BMC are addressing this.
- Within the Advanced File Transfer (AFT) it would be useful to have an integrated FT server and not rely on the underlying SSH.
- All batch schedulers have issues with fully automating tasks in a Windows environment and Control-M is no exception. Userids and profiles are harder concepts to deal with in the Windows world but BMC are doing their best to address this and Control-M would be better at handling these scenarios than the alternative products.
However, Control-M is a high-end solution and if your batch requirements are low (say below 200 tasks/jobs) and those tasks are not critical to your enterprise then maybe consider alternatives. Also, if your Agent platforms are not supported by Control-M (BMC can provide a list but very few OS are not included) then Control-M would be more difficult (but not impossible) to implement.
- Job Dependencies: Control-M can be used in sophisticated ways to link jobs - for example embedding logic that decides what return code to produce based on output from the job (e.g. look for an error message in the job log). It also allows force ordering a job (i.e. dynamically executing a job), or forcing a job status to OK or Failure. Of course it also has traditional job dependencies ( e.g. when job a finishes kick off job b, or kick off job c at a specific time). It also easily allows for combining various dependency types.
- Job Monitoring: Control-M has a sophisticated console for monitoring jobs. It allows easy access to job history and job output, and thru a GUI view of job dependencies.
- Job Setup: Control-M provides plugins for many different job templates including FTP, Cryptography, and web Services. It is highly configurable and provides a scripting language. Simple jobs can be set up in minutes using pre-built templates, and complex problems can also be solved by putting in the time and research.
- Single Major Action per job: this statement needs to be clarified. There are ways to do more than one action per job, and there are pre and post job commands available in most templates. Also some templates like FTP can have many instructions built in, like deleting source files after transfer (these are part of the positives). But basically you can only do one major action, like call one web service, or call one stored procedure per job. I believe this limitation is due to their licensing model, to ensure you will run as many jobs as possible.
- The only other negative is a necessary corollary of a having a powerful product. The learning curve is not simple due to the power of the product. I would recommend dedicate training for the primary operators and users of the product.
- Handling dependencies between platforms.
- Handling miscellaneous dependencies (dependencies other than Job dependencies).
- Learning curve is very steep. It takes way too long to get new employees up to speed.
- There isn't any educational material provided to train new employees.
- Our company had a long history of involving our business partners (non IT areas) in the scheduling process. Control-M did not have (and after 20 years) still does not have any sort of interface that our business partners could use. (So we created one ourselves.)
Control-M's documentation on how to use the product is very thin.
- The GUI is very good
- BIM is very helpful
- In the monitoring domain, please enable users to modify things like owner, set to dummy (options which are grayed out must be opened).
- Just like we have folders under home, please create some thing like jobs where-in we put in the job name then select it and run them. This make easy in an organization like us where we get a lot of requests to just run the jobs.
Control-M saves a lot of time and manpower, by running the production workload, letting people deal with development, maintenance and problem solving.
- Runs jobs when they should.
- Notify users when something goes wrong.
- Provide information on previous runs.
- The interface (On z/OS) is a bit clunky.
- Installation and upgrades are a pain.
- It is difficult to make mass changes.
- Provides seamless cross-platform workload automation integration.
- Provides integrated SFTP capability. No scripting or custom error checking required!
- Control-M provides fully auditable, version controlled workload development and provides tools for users to collaborate on development.
- Control-M provides excellent exception management allowing us to use our resources where they are needed most instead of monitoring workloads.
- Control-M could provide improved dynamic workload management based on physical server resources.
- Control-M for File Transfer could provide better diagnostic tools for troubleshooting connection errors.
- Once the job is scheduled in Control-M, it is all set to go on a regular basis. Very stable.
- Good GUI interface to drill down the failed jobs to further troubleshoot or to notify the owners of the jobs.
- Self Service options.
- It would be great if we can get some good customized reporting options to pull various reports.
- Central monitoring of all jobs running in the environment.
- Easily tied into our ticketing system. This allows for auto-ticketing in the event of job abends.
- Uncomplicated job setup.
- It would be nice to be able to review agent logs from the central dashboard.
- Automated agent unavailable alerts that could tie into our ticketing system.
- Is fast, reliable and scalable.
- The agent-less feature for Unix and Windows is really powerful and appreciated.
- It gives many option functionalities in a easy to use way. It allows you a very large customization use.
- Latest version (v9) allows you to upgrade management of the agent.
- Some workload automation tool to give you fast and easy access to the configuration (e.g. cli) instead of a Windows client.
- The web-interface is really nice (SelfService) but the service configuration (view) is a little bit tricky.
- The Smart Folder should have a cyclic parameter.
- Easy to set up.
- Interfaces with third party applications.
- Friendly user interface that gives you a graphical view of your workload.
- Since it is such a robust product, users need extensive training.
- We have always run into issues with setting up security, which needs to be refined and made simpler.
- The reporting feature needs to be addressed. Its still a bit cumbersome to pull needed reports.
Control-M is well suited for mainframe and batch processing. If you are still using Windows scheduler, Control-M is definitely a replacement for that. It's perfect for workload automation. If you are looking to centralize administering, monitoring, and scheduling jobs...then Control-M is the product!
If you are a small business that does not have a large number of jobs to schedule, then perhaps Control-M might be an overkill for your environment.
- Control-M is an excellent Workload Automation tool and has nearly unlimited options for scheduling tasks. This provides great flexibility in balancing workloads.
- Sometimes too many options make it difficult to find a simple way to get the task done. Often it takes longer to locate or decide on a function than it does to implement it.
Control-M Scorecard Summary
Feature Scorecard Summary
Control-M Technical Details
|Operating Systems:||Windows, UNIX|
|Mobile Application:||Apple iOS, Android|