Presuming that you have the necessary resources, what you can guarantee in 5 to 10 days is a demonstration of the basic on-line functionality of your application.
. mainframe availability
. Windows server
. mainframe-to-Windows connectivity (for FTP and NDV)
. Windows versions of Adabas and Natural, with valid license keys
. Entire Net-Work - mainframe and Windows versions (for testing and verification)
. Natural Development Server - mainframe (for code conversion, enhancement, comparison, and testing)
A complete implementation likely will require much more time.
. Your application may be using mainframe features which are not available under Windows, forcing major application changes. For example, under Windows, you cannot select an output-only detail line using a PF key (ie drill-down).
. Batch JCL must be converted to scripts.
. Ending value ‘9’ must be changed to high-values.
. EBCDIC hex codes must be changed to ASCII.
. Screen-level help cannot be invoked as on the mainframe, forcing map changes.
A checksum routine can be used to verify your Adabas data, but some amount of testing will be necessary to validate the application. When comparing output from the two platforms, remember to look for equivalent results, not identical results. If you use keys that mix numeric and alpha values, EBCDIC and ASCII sequences will differ.
It would take a few days to analyze the application and provide an accurate estimate of the conversion effort.