Welcome to the MCTool Web Site.
In todays complex computing world, current trends are calling for handling a reduced product set in order to ensure more productive environments in development and management. Thus transfer to Cobol (and DB2) is an obvious option provided it can be done at reasonable cost and effort.
Product objectives.
Access full CICS standards.
Now you can have access to features like CICS MRO, ISC, CICS Sysplex, transaction distribution, VSAM Record Level Sharing, automatically, among others. And, at the cost of some extra coding, Journalling, Transient Data, Temporary Storage, Database access.
Access SQL standards.
Also update automatically your DB programming technology to present DB2/SQL standards. A SUPRA subset is supported. Requires preplanning and customer involvement and thorough checks.
Costs savings.
You simply write off a long term cost by paying onetime MCT. You will find MCT is in most cases a portion of one year bill. And you will find your extra manpower costs of migration reasonable as you are involved only in tests (with optional on site support) and, as a side advantage, your personnel will get reasonably familiar with replacing code.
"Universal" documentation.
Being Cobol a widely used programming language, most people will find it close to an universal code and somehow think of it as pseudocode.
Thus, in some way, Cobol executable code, is a documentation asset. And if you think of new languages like Java or C, Cobol is a more reasonable basis than others for migration.
See about MCTool.
Access full CICS standards.
Now you can have access to features like CICS MRO, ISC, CICS Sysplex, transaction distribution, VSAM Record Level Sharing, automatically, among others. And, at the cost of some extra coding, Journalling, Transient Data, Temporary Storage, Database access.
Access SQL standards.
Also update automatically your DB programming technology to present DB2/SQL standards. A SUPRA subset is supported. Requires preplanning and customer involvement and thorough checks.
Costs savings.
You simply write off a long term cost by paying onetime MCT. You will find MCT is in most cases a portion of one year bill. And you will find your extra manpower costs of migration reasonable as you are involved only in tests (with optional on site support) and, as a side advantage, your personnel will get reasonably familiar with replacing code.
"Universal" documentation.
Being Cobol a widely used programming language, most people will find it close to an universal code and somehow think of it as pseudocode.
Thus, in some way, Cobol executable code, is a documentation asset. And if you think of new languages like Java or C, Cobol is a more reasonable basis than others for migration.
See about MCTool.
Main issues.
Automatic conversion.
Every effort has been put into the product for no or minimum manual intervention for the conversion process. Simply feed in listings of Mantis objects and get BMS maps and Cobol code and supporting information. For Supra conversion you must also supply DB2 tables (declares).
Customizable algorithms.
As MCT System will generate program code and Job streams some installation defaults must be set like date and time standards, DSNs for Mantis files and compilation decks.
Another customizable item refers to program names because Mantis names may be longer than allowed by MVS host. You select which portions of source name to be used. You can add also fixed data. Once selected, this algorithm will be conversion wide used at program generation of own and called programs, thus almost eliminating manual intervention (the exception is when the called program is a variable not known at conversion time, a warning is recorded at log file).
For Supra conversion, parameters are available to specify current and new table names.
Cobol follow on uptades.
Enabled follow on Cobol maintenance is another plus you will get. When doing so may be you also you will find advantageous replacing some areas by a more efficient "native" Cobol code.
Execution pathlength savings.
Cobol execution of programs will be a simulation of converted program, but as long as complex "interpretation" is no longer needed, there will be important reductions in pathlength and storage requirements.
Automatic conversion.
Every effort has been put into the product for no or minimum manual intervention for the conversion process. Simply feed in listings of Mantis objects and get BMS maps and Cobol code and supporting information. For Supra conversion you must also supply DB2 tables (declares).
Customizable algorithms.
As MCT System will generate program code and Job streams some installation defaults must be set like date and time standards, DSNs for Mantis files and compilation decks.
Another customizable item refers to program names because Mantis names may be longer than allowed by MVS host. You select which portions of source name to be used. You can add also fixed data. Once selected, this algorithm will be conversion wide used at program generation of own and called programs, thus almost eliminating manual intervention (the exception is when the called program is a variable not known at conversion time, a warning is recorded at log file).
For Supra conversion, parameters are available to specify current and new table names.
Cobol follow on uptades.
Enabled follow on Cobol maintenance is another plus you will get. When doing so may be you also you will find advantageous replacing some areas by a more efficient "native" Cobol code.
Execution pathlength savings.
Cobol execution of programs will be a simulation of converted program, but as long as complex "interpretation" is no longer needed, there will be important reductions in pathlength and storage requirements.
8 Easy migration.
8 Simplified future maintenance.
8 Full fledged technology.
8 Convergent environments.
8 Simplified future maintenance.
8 Full fledged technology.
8 Convergent environments.
8 User supplies parameters and source objects.
8 We deliver BMS & source code.
8 No user conversion involvement,
except compile & test.
8 We deliver BMS & source code.
8 No user conversion involvement,
except compile & test.
