Modules Within Explain
|
|
SOURCE CODE ANALYSIS
EXPLAIN will accept imported COBOL source code identified by program ID's, DEC COBOL source code, DEC FORMS, FMS, and SMG screen code, and copy book information. Programs may be analyzed as individual entities or multiple programs (identified in the same sequence in which they are executed). Given information for a complete system, EXPLAIN can draw conclusions and report inconsistencies in file naming, file layouts, file sizes, data types, FD and data naming practices. From the Data Division and through recursive analysis of the Procedure Division code, EXPLAIN will build Data Dictionary entries for this and other programs with consistent naming conventions. Copy statements are resolved and that information is included in the analysis as well. Since the host computer, upon which this code runs, EXPLAIN incorporates logic procedures to perform "machine specific" filtration of the incoming code and procedures. These are routines that use LIB$.., SYS$.., and other DEC library routines. These functions are rewritten in COBOL as either in-line COBOL code or a callable subroutine depending on the routine being replaced. As a result, EXPLAIN will transform the program into modules and data information which it needs to build the screens and data dictionaries. The information that is gathered in this phase is also automatically incorporated into the Data Dictionary. It will be used for generation of new FD's, DCLGENS, and other supporting modules for the target machines.
SCREENS ANALYSIS
A variety of sources can supply the necessary screen information. If it is a screen data entry program that is being converted, the DEC FORMS, FMS, or SMG definitions are used as input into the Screens Analysis Programs. If the program uses some other method of screen processing, the screen analysis program is informed and looks to the source code for screen definition. Other systems can provide similar information that is used to describe screen requirements to the Screens Dictionary. By using these maps and forms, a duplicate data entry screen is provided to the user of the re-engineered code. This also provides the installation with the opportunity to make modifications and updates to the screen, or revise it to new installation standards. Text data can be changed, the layout of items changed and data sizes expanded. The changes will automatically be incorporated into the new code that is build during the EXPLAIN code building operation.
FILE ANALYSIS
EXPLAIN analysis the programs, VAX DBMS Data Base DDL, RDBMS, FMS information, and any other source of file information available. From this analysis a variety of reports are prepared to allow the user to have a total evaluation of file structures in the system being ported. From this information the user can apply standard naming convention, identify data inconstancies in size and type, and determine modifications to the data structure that will optimize performance on the new platform. The exchange feature of the EXPLAIN system can be used to apply the improvements as new code is build.
ANALYSIS REPORTS
The Source Code Analysis subsystem provides printed reports for each program analyzed. The converted system is accurate re-documentation to provide the user with complete new program and system documentation. In most cases the documentation is better than any previous documentation of the programs and the system. Reports are generated that provides related analysis information as viewed from all the programs in the system. A selection of reports are available that provide detailed analysis information in various useful groupings.
Some of the topics covered by the reports are:
DIRECT
CONVERSION It
is possible to convert a program from one machine with one operating system
to another machine with a different operating system. The new program will be
identical in structure to the original program as it was analyzed. The same
paragraph names and naming conventions will be used when they do not conflict
with installation standards or the target machine standards. Notes and comments
from the original program are incorporated in the new program. When changes
are made to the code a comment is inserted to explain the change. The new code
is generated with a standard format and layout with consistent form for indentation
and alignment to code. The
importance of this approach is to migrate programs to the new machine with as
few code changes as possible. When the programs are on the new machine, the
code will be ordered and function the same as in the original program on the
old host machine under the previous operating system.
| Home |
Why Convert Legacy Code? |
The Service Available |
How We Do It |
| Examples |
Hardware/Data Bases Supported |
COBOL to JAVA |
The Company Information |