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 SoftwareMining: 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 SoftwareMining. 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:


For Java output (assuming that Java Package is set to com. yourcompany. test – see Target Language Settings page) the following output structure is applied:



DataGen and BRE Templates: Directory that contains COBOL templates for DataGen utility (see Projects Page) and sample code generation templates for Business Rule Extraction tool.

Report 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 'Reduce Array Size' is checked - the system will automatically reduce all the size of OCCURS on all the items which do not REDEFINE anything, are not subject to other redefinitions, or do not contain child items which contain REDEFINES, or are subject to other redefitions.

Unix to Dos Conversion.Introduces CR LF where only CR is available.

When Redefining Field more than ... If a memory position/variable is redefined a lot of times - then it is probably used to reduce the memory consumption. In such cases the system can automatically remove the redefinitions. The system can be set to
- do nothing (don't remove the REDEFINITIONS),
- Confirm with user if the excessive REDEFINES should be removed
- Automatically remove such REDEFINITIONS.

  

Target Language. Allow selection of the Target language for the migration process.

Java / C# Package. The base package when generating Java applications.

Additional Java / C# Import File. Using this option you can specify an additional imports to be inserted at top of every generated java program.

Filler Number Prefix. The prefix is used to differentiate between variables of the same name - within the same group.

Generate Separate Classes for WS/LK 01 Entries . By default the system will generate a single data-container class (iData) for the Working Storage section. If the Working storage section references COPYFILES which start at "01" level, then the system will also generate separate data-container classes for these.  However, if the Working Storage section only contains many 01 entires, and none-of the copy-files start at 01 level, then there will be only a single data-container (iData) class generated. 

Setting this check-box will create a single data-container file for each 01 entry.

Use Logger instead of Unformatted Screen Outputs. Redirects COBOL Display statements to a logger (e.g. Log4J) .

Use Sun Coding Standards. COBOL variable/Procedure names typically in  "ABC-DEF" format. The system can  translates these either to "abc_def" format, or use Sun coding Standards: "abcDef" .

 Add Logger Debug lines to generated Methods. COBOL variable/Procedure names typically in  "ABC-DEF" format. The system can  translates these either to "abc_def" format, or use Sun coding Standards: "abcDef" .

Target is  JSP / ASP . Check this box to generate JSP/ASP pages that correspond to original COBOL screens. Alternatively an XML Servlet version is generated If the check box is not ticked.  

 Generate Simple Beans. Generate data-containers (beans) which do not use SoftwareMining framework. These beans are written out to idata.beans or persistence.beans directory. They can be used for external communication via XML .

 Normalize FD's with Multiple 01 Entries. Break a File Definition with multiple 01 entries into multiple records/classes. Please note that generated code will require manual touch up.   

 Convert 88 Variables to methods. By default - the generated code will compare 88 varaibles either by using "equals" method - or by using methods on RangeItem class.  By ticking this check box - the system will generate additional wrapper methods such as 'is88Variable(variabele)', use them in the business logic code. Advantage is that the business logic code becomes more legible, disadvantage is that the generated data-wrapper classes become larger .   

Obfuscate Code. Obfuscate the Original cobol code - changing variable names, and string. The obfuscated code cannot be used for compilation and running. But it can help when a  sensitive code fails in  parsing / code generation. The obfuscated version of  can be  send to SoftwareMining.

Use this page to specify different initialization for java variables.


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.


Screen Directory. Screen Beans are placed into this folder.

 

Use this page to specify target database for translation of VSAM/ISAM files.