The following list is a broad set of information required while migrating from a mainframe. This is by no means exhaustive but is meant to provide adequate scope for anybody embarking on such projects. Do drop us a note if you feel there are additions that you would like to be included.

• 1.Application Meta DataObjectives and Critical Success factor for the project migration.Any known challenges, issues, limitations of applications?How many environments are they working with?Tools used in the current environment.Dependency with other applicationsHow big is the application? Number of lines of code.Upstream and Downstream interfaces of the applications.Any third-party products / tools / components libraries used in the application.
• 2.Users and SecurityHow many users? & How many are concurrent?How many user groups?Details of role mapping.
• 3.Application PerformanceApplication availability – 24/5 or 24/7 or otherData Recovery requirements.Back-up and Recovery requirements.What are the typical maintenance activities that will be done during the maintenance window of the application?MIPS details.What is the current Mean Time to Recovery?Transaction Growth Rate.
• 4.Legal and Regulatory CompliancesAre periodic audits/reviews required by regulatory/government agencies?
• 5.ResourcesExisting application team structure.Dependent Owners.Stake holders and their responsibilities.
• 6.StorageList down current types of storage and their rate of growth.
• 7.Data / DatabaseTypes of data.Complexity of data.Amount of data.Rate of growth of dataPartitioning and details of partitioning.Data Transformation requirements while migrating.Data Sharing.
• 8.Source CodeTypes of language.Number of components.Number of online screens.
• 9.Batch Process DetailsTotal number of batch jobs.Different schedulers and their details.Are there any SAR/SAS reports?Job flow details.Peak number of scheduling requests per day.
• 10.MonitoringComponents to monitor.Current process forApplication performance monitoringEnd to end transaction monitoring.Tools/products to be used.
• 11.PrintingCurrent Print Ecosystem.Current Print requirements.Current Reporting requirements.Frequency and type of reports.
• 12.TestingAvailability of test cases.Testing Process/ Tools used.Test scripts and their availability.
• 13.SystemsNumber of mainframe systems used and their models, configuration, and setup details.Available processors and their models.OS and their versions.Memory capacity and their management.
• 14.Program planning and executionChange management process currently in place.Information Security related process, procedures and documents.

Our aim at Kumaran Systems is to be a trusted partner for organizations embarking on mainframe modernization projects. Feel free to reach out to us in exploring our specialized range of services.