|
This page allows
you to control, which files are to be translated/documented. You only need to select
the primary COBOL files - i.e. those with Procedure division - not individual
copy files.
Analyse Button
The following operations will be performed on the selected files :
The selected files will be
analysed for dependencies on other files (e.g. COPY files).
A list of all the files
required for successful processing will be prepared.
When a Copy/Replacing
statement is encountered, a new file will be prepared and posted in the list.
All the necessary copy files
will be moved into your private Working Directory - ready to be
translated.
A warning will be issued if
one or more Copy files addressed by the program are not available. You will
need to make those files available to the system.
It is recommended that you process one program at a time - although when
some files are dependent on each other then you can process more than one file
in one go. For example, when the complete FD definition for a record structure
is present in more than one program - then all such programs will require to be
processed in one go. This is not a common situation as in most applications the
FD descriptions are kept in a separate file from the main programs. In general
the system is capable of processing more than one program at a time - but will
use huge system resources - in terms of memory and time of processing.
Edit Button
On Rare occasions you may require to view or
modify the prepared files. Double clicking on the file, or clicking on the edit
button will open the file using the default editor.
This page is also the main
Control section for the translation process. It works on the prepared files in
the Working Directory.
The processing is achieved in 3 main stages:
Parsing: Parsing of the programs & Data file. This process helps build
a model of the logic and data-structure of the COBOL application.
Analyses: Primarily this
is the analysis of the COBOL data files. It is here that the system converges
FD descriptions in multiple files, decide on data-types, organize array-sizes,
and process redefined fields.
Code Generation:
Analyses and modifies the model of the program logic, and
finally converts it into code written in a target language.
The three processes or Parsing, Analysing and Code Generation must be
activated in the correct sequence.
IMPORTANT
Note that for a given set of programs, if the system fails completing one
of the latter stages of translation (e.g. Analysis or Code Generation), the
process must be restarted at the Parser stage. If you continue without restart
the parser, the system cannot guarantee correct translation of the programs.
Clear Button. Deletes the files
from the Working
directory – Cobol Translation Toolkit will be
ready for processing of the next set of COBOL programs.
Flowchart Button. Processes the selected program to
a stage that flow chart documentation can be produced. To view the flowchart -
go to the 'Documentation' tab. On completion of the program analysis - the
system can automatically change to the 'Documentation' tab - if you have the
appropriate option selected from the check boxes menu (5 buttons along).
Translate Button. The selected
programs are translated to the desired target language (selected in the setup
page). If there are no errors encountered during the translation, then the
programs are presented within a syntax highlighted text viewer - before you
decide to purchase.
WS Entity Generation Button. On completion of the translation for a set of programs, all the
WS Copy files must be translated to class files in the target language. The
system automatically generates these. (See the check box menu - 3 buttons
along). Use this button to regenerate the classes. Pay-for-usage clients will
not be charged for generation of these classes.
SQL DDL Generation Button. On completion
of the translation for a set of programs, all the FD Schemas can be translated
to equivalent SQL tables. The system automatically generates these. (See the
check box menu - 2 buttons along). Use this button to regenerate the classes.
Pay-for-usage clients will not be charged for generation of these classes.
FD Entity Generation Button. On completion
of the translation for a set of programs, all the FD schemas must be translated
to class files in the target language. The system automatically generates
these. (See the check box menu - 1 buttons along). Use this button to
regenerate the classes. Pay-for-usage clients will not be charged for
generation of these classes.
Top | Index | Glossary
|
