COBOL Program Migration Support

You can use OpenESQL as an effective migration tool, particularly when you migrate from the mainframe. OpenESQL provides the BEHAVIOR directive to define the COBOL environment and make migration transparent, yet efficient:

• BEHAVIOR can be set to any of the following:

  ANSI	Enables OpenESQL to work like the ANSI standard, and enhances the access speed
  MAINFRAME	Enables OpenESQL to work as it does on the mainframe, and enhances the access speed
  UNOPTIMIZED	Provides backward compatibility with earlier Micro Focus products
  CICS	Sets all of the following: Enables OpenESQL to work as it does on the mainframe Enhances the access speed Automatically sets the TRANSACTION primitive directive to GLOBAL
  JCL	Sets all of the following: Enables OpenESQL to work as it does on the mainframe Enhances the access speed Checks for the following statements that are not compatible with JCL applications: CONNECT DISCONNECT SET CONNECT Reports an error for each incompatible statement found
  primitivedirective	Optional directives that enable the fine-tuning of BEHAVIOR

• With either the MAINFRAME or ANSI values, OpenESQL determines:
  • The optimal DBMS cursor for ambiguous COBOL cursors, i.e., cursors not defined as explicitly read only or updateable
  • The optimal DBMS cursor selection for both read-only and updateable COBOL cursors
  • The appropriate isolation level and lock concurrency settings

  You can set a default behavior of ANSI, MAINFRAME, or UNOPTIMIZED using the OpenESQL Configuration Utility. However, when the BEHAVIOR directive is specified in program code, project settings, or in a compiler directive file, the specified setting overrides the default setting.

• Capability to override the BEHAVIOR characteristics cited above without changing the program's associated EXEC SQL statement.

For more information, see the BEHAVIOR topic and the demo application behavior listed in the topic Demonstration Applications.