Home FAQ

The migration process can be confusing if not overwhelming, below are some frequently asked questions that have come up in the past to hopefully help get the conversation started. If you have further questions – please do not hesitate to Contact Us.

A native COBOL transaction monitor was created to handle pseudo-conversational

They are duplicated with equivalent subroutines or inline COBOL

The screens look exactly the same on the new platform, the keyboard is re-mapped, and the BMS is converted the appropriate platform screen presentation utility

The JCL is converted to the control or scripting language supported by that platform

VSAM is duplicated using the specific file access method as determined by the platform

A Select and File Description is added into the program when IO is found

Handled through platforms native sort utility

The appropriate print file is created and then routed to the customer decided printing location

The tool comments out the mainframe code and places the equivalent replacement code directly beneath as a form of source code documentation

Optionally, load programs are created for the test environment. Those programs are given to the customer to load their data into the new database

Time/Date subroutines have already been duplicated. A true program written in Assembler is rewritten into COBOL