COBOL Translation and Documentation Toolkit requires the following information prior to commencement of the migration process.
Client Name: Enter Your Company Name - All the generated programs will include this at top of the program.
Licence Key: Key for unlocking the system. Provide after one-off licence payments.
Pay-for-use Username/Password: After registration at www.softwaremining.com, the system will allow you to pay only for the programs that you require translating/documenting. REQUIRES INTERNET CONNECTION.
Language: Working Language of COBOLTranslation and Documentation Toolkit - Currently only English is supported.
Default Editor: If the your selected editor is not in the operating system PATH directive, then you will need to enter the full path of the editor.
Show Hints Enables/Disables Windows Hints.
Report Bugs Automatically to COBOLMining: The system will use your Internet account to send the sequence of 20 words that was not understood by the parser. REQUIRES INTERNET CONNECTION.
View Generated programs before charging my account. Even after Pay-for-use registration, the system allows you to inspect the generated programs before sending charge information to COBOLMining. For performance improvements uncheck this box.
Repository Directory: All COBOL programs/sub-programs require certain amount of
preprocessing. This directory is where COBOL Translation and Documentation
Toolkit will place your prepared files. Essentially this directory will be the repository
of all the programs, which is needed to complete your
translation/documentation. The repository directory may be placed on a shared
drive, and multiple users setup to use the same repository directory. Then if
and when any files are modified - all users will see the changes.
COBOL Copy File Directory: Typically you would work on migration of one (or a few) program
at a time. COBOL Translation Toolkit will move the prepared files from the
Repository directory into the WORKING directory to start the actual migration.
When you start working on your next batch of programs, you are required to
remove the previous files from there.
Target Output Directory: The migrated programs will be placed here.
For Delphi output the following output structure is applied:
<Output Directory>\ -
Migrated Programs
<Output Directory>\sql-ddl\ - Migrated SQL Data Definition files - for
building the Database
<Output Directory>\FDinc\ - Object Wrappers for File Definitions
<Output Directory>\idata\ - Object Wrappers for WS/Printer/Screen
Definitions
<Output Directory>\templates\ - html templates for servlets
For Java output (assuming that Java Package is set to com. yourcompany. test –
see Target Language Settings page) the following output structure is applied:
<Output
Directory>\com\yourcompany\test\ - Migrated Programs
<Output Directory>\com\yourcompany\test\sql-ddl\ - Migrated SQL Data
Definition files - for building the Database
<Output Directory>\com\yourcompany\test\FDinc\ - Object Wrappers for File
Definitions
<Output Directory>\com\yourcompany\test\idata\ - Object Wrappers for
WS/Printer/Screen Definitions
<Output Directory>\com\yourcompany\test\templates\ - html templates for
servlets
COBOL Templates Directory: Directory that contains COBOL templates for DataGen utility
(see Projects Page)
HTML Templates: Directory that contains HTML templates to use for documentation of COBOL programs.
Help Directory: Directory that contains the help files.
Log Directory: Directory that contains translation log files.
COBOL Platform: COBOL Translation Toolkit can
detect most of the differences between the supported compilers automatically.
However, you should select the correct settings in this field.
Column Settings: If your COBOL compiler uses different setting
then you will need to readjust these parameters. Note that the columns are zero
based.
Keep Comments In Original Source: When
selected, this causes COBOL Translation Toolkit to transfer the original
comments into the translated code. Note that not all the comments will be
transferred.
Reduce Array Sizes. Programs with large array sizes can have an adverse
effect on memory requirement of the application. This is because the system have to map the entire array out
in order to be able to establish what happens when you move one variable onto
another (think of all different funny things you can do REDEFINing those array
sizes). Large arrays could crash the toolkit. If there is no redefinition on
the arrays within the programs, and if the MOVE statement only copies arrayed
variables onto another arrayed variable - then having this option may help.
Unix to Dos Conversion.Introduces CR LF where only CR is available.
Target Language. Allow selection of the Target language for the migration process.
Java Package. The base package when generating Java applications.
Non-persistent base class. The name of base class to be used for generated
wrappers for WS definitions.
Persistent base class. The name of base class to be used for generated
wrappers for FD definitions.
Generate HTML. Check this box to generate HTML templates for servlets.
Access level. Select a desired access level for data members of generated wrappers for WS and FD
definitions.
GUI Class Prefixes. Both Delphi and Java support Object Orientation, and Components Inheritance. COBOL Translation Toolkit can generate target screens using either the base
components, or components sub-classed from them. For example, a data entry
field can be translated to an instance of TextField in Java, or TEdit in Borland
Delphi, or alternatively, they could be translated to ACMTextField in Java and
TACMEdit in Borland Delphi types respectively. The advantage of using special
components is that you can control the overall behaviour of your application
from one place - the component. E.g. the ACMTextEdit field could be programmed
to trap function keys so for example "F2" can be used to quit out of the
application, "F3" can be used to print a form, turn a different color when the
cursor enters the field, etc. Hence you can mimic the look and feel of your
original COBOL application from one central place.
NOTE Software Mining distributes a set of predefined components with COBOL
Translation Toolkit, so you do not have to write your own.
Important Each COBOL program containing screens will be
translated into the following:
- JAVA - The screen is based on ACMForm. This allow simple migration route from APPLET
to SERVLETs. The source code for this component is distributed with the
application.
- Borland Delphi - The screen is based on ACMForm, which provides additional
facilities. The source code for this component is distributed with the
application.
- Borland Delphi - ACMLabel/ACMTextEdit components provide additional methods (e.g. setText() and
setLabel()). Therefore do not use the standard Delphi TLabel and TEdit
components. You may however provide your own components provided that the
components provide the said methods.
FD Wrapper Directory. Using this field you can change the default name for folder where generate FD
wrappers to. See Target Output Directory.
WS Wrapper Directory. Using this field you can change the default name for folder where generate WS
wrappers to. See Target Output Directory.
Additional Java Import File. Using this option you can specify an additional
imports to be inserted at top of every generated java program.
Target Database. COBOL Translation Toolkit can write the necessary SQL schemas for various databases.
The settings refer to the amount of space COBOL Translation Toolkit will
allocate for display of a character. This may be different to the amount of
space required by a character. For example, COBOL Translation Toolkit may be
setup to allocate '5' points for each character. But, using a proportional font
the character 'A' may actually require 8 points, and character 'i' may require
3 points.
Use this page to specify different initialization for java variables.
Reset Defaults. It resets the attributes in this page to their default values.
Top | Index | Glossary
|
