Show all | Hide all
Show all | Hide all
Prime function : Parsing source components & populate structured repository JCL Scripts: Reporting for consolidation of list of db tables/SAM/VSAM files. JCLs are converted to IBM 's JCL structure. Reverse engineering: Reporting on existing data model schema for re-modelling & customisation / optimisation. Forward engineering: DB2 schema is generated and components like DDL,Data access Layer Data download / Upload programs with revised model. DCCM3 Screens: Reporting & customisation,.components like BMS maps for CICS are generated. COBOL & Q Language: Analytical reports are generated and customised converted COBOL programs are generated with database I-O and Map Send/Receive.
• Technology Obsolescence - Lack of HW/SW support and upgrades - Lack of support for new technologies (Web, SOA) • High and Growing Costs - New initiatives are cheaper than legacy systems(around 40%) • Constrained IT Responsiveness - High backlog / slow response (competitive) • Graying skill base - Attrition - New resources hardly available • Rigid IT Infrastructure - Complex and very old software layers constrain choice
There are many Hitachi mainframe installations across the world, particularly in Japan, where Hitachi, with more than 15% market share in Japan, had been the third largest mainframe vendor till year 2000. Hitachi has stopped manufacturing mainframes and upgrades since year 2000. As a consequence, the existing Hitachi customers are finding it difficult to get adequate support and upgrades for the existing hardware and software. Skill availability for old Hitachi languages like COBOL or Q, databases like PDM II and OLTP like DCCM3 are absolutely scarce in the market place. With lack of upgrades, integration facilities with newer technology platforms are also not available. This scenario forces the Hitachi customers to look for migration options. In most cases, the Hitachi customers have heterogeneous mainframe environment and consolidation on a single platform like IBM is the immediate and best suited option. Merger and acquisitions of fairly big organizations also leads to migration and consolidation to a single platform, in most cases to IBM mainframes since the current market share of IBM in the mainframe market is more than 99%.
Return on investment
Reduce Migration Time: around 33% of manual approach Reduce Migration Cost: around 50% of manual approach Achieve Faster ROI: 12 months compared to 30 months in case of manual approach.
Major benefits and value additions to the customer - 1. Efficiency and coverage of the tools proven in customer projects and large code base. 2. Quick turn-around - Tool based approach reduces the migration timeline to around one-third compared to the manual approach. 3. Reduced effort and cost - the migration tools leads to great productivity gains reducing the migration effort and cost and thereby providing greater ROI to the customer. 4. The valuable business logic embedded in the application is retained 100% in a tool based migration. 5. The tool outputs are consistent in quality and the generation is repeatable, reducing the risk of migration. 6. Less testing and debugging effort required due to automated code generation. 7. User training is not required as the migrated application look and feel and functionalities remain exactly similar to the existing application.
Automotive OEMs (Manuf of Cars, Light Trucks, Motorbikes)
Business Process Management and Integration
Inventory/Warehouse and Shipping Mgmt
Production/Ops and Logistics
Dynamic Infrastructure/Smarter Planet
Midmarket Business (100 to 499 employees)
Midmarket Business (500 to 1000 employees)
Large Business (greater than 1000 employees)
Countries/regions available for distribution
Date last modified: Oct 2, 2012