The Vantis Cobol Suite is a set of products aimed at large systems whose applications written in COBOL language run on the IBM zSeries and iSeries mainframe platforms, all products work in coordination in synergies, in a single architecture with the same operating principles, which minimizes the learning effort between the different Vantis Cobol Suite products.
At compile time, CleanCode analyzes the entire Cobol Program, identifies and effectively cleans all existing Dead or Inaccessible Code, including DB2/SQL and CICS statements.
Identifies Cobol Programs that do not use Good Programming Practices.
Identifies the instructions in the Cobol Program that cause low Performance, to obtain
a real reduction in the consumption of computational resources, including MIPS.
Identifies which instructions in the Cobol Program cause its security to be vulnerable.
Identifies instructions in the Cobol Program that need to be updated to avoid risks when migrating to newer versions of the Cobol compiler.
Enables rapid implementation
of new Rules with particularities of the
environment at the Customer's request.
Vantis Extractor collects “Near Real Time” the consumption of computational resources from all Cobol Programs, allowing the selection of the largest CPU consumers (MIPS), based on peak days and times, allowing a Performance analysis to be prioritized.
Ideal solution for performance and capacity planning disciplines in a DATA-CENTER with z/OS.
This allows the collection of performance data in near real-time, with direct extraction to the Azure Monitor platform, pre-configured Dashboards in Azure, creation of alerts for proactive actions, WEB application, pre-configured with layouts of SMF records among other features.
Integrated with IBM Workload Scheduler (IWS), it automates and fully or partially recovers an ABEND that occurred in Batch processing.
It analyzes the JCL and the conditions that caused the interruption in order to make the necessary changes to all file definitions, GDG or conventional. After this analysis, the necessary adjustments are made to the Restart process.
Depending on the analysis of the last processing, or other previous ones, an analysis of the 'Return codes' is made versus the composition of the COND parameter of the Steps to be restarted and the Steps already processed, which guarantees control of changes to the Steps to be executed .