AWS Batch vs Control-M

• S3 amount of files
• Easy to share files to other sites
• Like that the files and folders can be open and public or completely private
• I like that you can have double or mirroring in different Data Centers for Data Recovery

Read full review

• Control-M provides a single, centralized interface for monitoring and managing all batch processes in the organization. Nothing is hidden or left unattended in a timely manner.
• The proper use of the BIM component has allowed the change of paradigm in the operation, adopting a proactive management instead of the typical reactive management in the event of production failures.
• The use of Forecast and production simulations allows you to identify bottlenecks and focus first on managing those failures that have the greatest impact on production SLAs.
• Control-M/Change Manager has arrived to shorten development cycles from requirements gathering to production testing. It has been a utility that monetizes the development of Jobs meshes.
• The GUI is capable of efficiently handling more than 80,000 jobs per day. This is certainly a challenge in designing a good user experience. I don't know if there is a reasonable limit to this. One of my clients runs more than 80,000 Jobs daily and the GUI remains smooth all the time.
• Job-As-Code is a DevOps accelerator that has just begun to be adopted. Its implementation will make workload management even more cost-effective.

Read full review

• Jobs monitoring dashboards are not matured
• Documentation and support is something which can be improved
• Sometime i faced the slow response or slow in performance i would say

Read full review

• As with most of the mainframe software products, documentation seems to be the weak link for the products - written by people and for people who already know what they need to do, not for people who are trying to figure how to use the product.
• We are a large JES3 mainframe shop. As with all vendors who still provide software for mainframe systems, software is generally designed and developed for JES2 and is frequently not fully tested in a JES3 environment before being shipped out.

Read full review

• Able to Schedule regular copy of S3 Instances regularly.
• Better security of data.
• Long waiting times resulted in hurdles while autoscaling.

Read full review

• I would expect this product to give a positive return on investment. Running jobs in cron for example would require a lot more scripting effort to ensure that the proper notifications are done on failures. With the built in functionality in Control-M the effort would be greatly reduced

Read full review