| Feature |
Feature Description |
Benefit Description |
| ILOG JRules management and rule authoring features |
Full support of business rule authoring in ILOG Rule Studio or ILOG Rule Team Server. Decision tables and rule flows can be used to author rules for eventual generation of COBOL code on the mainframe. |
Manage and document business decisions executed in the mainframe applications |
| COBOL rule generator |
Once the rules are written, a developer uses a menu option in ILOG Rule Studio or ILOG Rule Team Server to generate the native COBOL code from the identified rule set. The COBOL code can then be uploaded and compiled with the main calling program on the mainframe. |
Generate native COBOL code from rules within ILOG JRules |
| COBOL copybook importing tool, to generate Business Object Model (BOM) and business vocabulary |
A developer can simply import a COBOL copybook that contains the necessary fields to write the rules.
Importing a COBOL copybook is a one-step process that will automatically create the necessary BOM. Developers can then provide the business terms so the rules can be written with the appropriate business terminology.
|
Author ILOG Rules for COBOL in business terminology |
| Java execution object model (XOM) mapping to the business object model (BOM) used by COBOL rules
|
A developer can map the BOM entries from the COBOL copybook to the necessary XOM entries needed for the rules that will be used in JAVA. |
Share rules and files in JAVA and on the mainframe |
| Support of existing mainframe technology |
ILOG Rules for COBOL supports IBM Enterprise COBOL 3.3 and the ability to generate COBOL code for the Customer Information Control system (CICS) and batch programs. |
Support COBOL on common IBM platforms |