Micro Focus Enterprise Developer 3.0 for Visual Studio 2013 > Programming > Data Access > Database Access > Reference > OpenESQL > SQL Compiler Directive Options > BEHAVIOR

BEHAVIOR

Instructs OpenESQL to properly match your COBOL cursors with the database you are using, thus maximizing database cursor performance. BEHAVIOR makes use of multiple primitive directives and associates a default value for each primitive directive depending on the target DBMS. You can also override the default setting of any primitive directive.

Note:

If you don't specify any BEHAVIOR primitive directives, and you also accept the default primitive directive values listed in the relevant table in the Default Primitive Directives section later in this topic, the TARGETDB directive is not required; however, you must specify TARGETDB if you want to use different default values for any primitive directive.
Setting the BEHAVIOR directive can also affect the SQL types returned when using Dynamic SQL. See the DESCRIBE Statement topic for more information.
Because the ADO.NET API does not support prefetching, very limited support is provided for BEHAVIOR primitive directives with DBMAN=ADO. See DBMAN Directive Settings for more information.

Syntax:

BEHAVIOR={OPTIMIZED | UNOPTIMIZED | ANSI | MAINFRAME | CICS | JCL} [primitivedirective [value]]...

Parameters:

OPTIMIZED	Enables OpenESQL to optimize ambiguous cursor declarations; enhances the access speed
UNOPTIMIZED	Provides backward compatibility with earlier Micro Focus products, where ambiguous cursors are both updateable and scrollable
ANSI	Enables OpenESQL to work like the ANSI standard; enhances the access speed
MAINFRAME	Synonym for OPTIMIZED
CICS	Sets all of the following: Enables OpenESQL to work as it does on the mainframe, optimizing ambiguous cursor declarations 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, optimizing ambiguous cursor declarations 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

Scope:

Used at compile time:	No
Behavior at run time:	Source file

See Scope - OpenESQL SQL Compiler Directive Options for more information.

Default:

BEHAVIOR=OPTIMIZED

Default Primitive Directives:

Table 1. Default Behavior Primitive Table for SQL Server:
BEHAVIOR = Primitive Default Values	OPTIMIZED, MAINFRAME, JCL	ANSI	CICS
AUTOFETCH	ON	OFF	ON
DEF_CURSOR	RO	UPD	RO
RO_CURSOR	FORWARD or IC_FH	FORWARD or IC_FH	FORWARD or IC_FH
PF_RO_CURSOR	1	1	1
IC_FH_ISOLATION	UR	UR	UR
UPD_CURSOR	DYNAMIC	DYNAMIC	DYNAMIC
PF_UPD_CURSOR	8	8	8
UPD_CONCURRENCY	LOCK	LOCK	LOCK
ISOLATION	CR	CR	CR
TRANSACTION	LOCAL	LOCAL	GLOBAL

Table 2. Default Behavior Primitive Table for Other DBMSs:
BEHAVIOR = Primitive Default Values	OPTIMIZED, MAINFRAME, JCL	ANSI	CICS
AUTOFETCH	ON	OFF	ON
DEF_CURSOR	RO	UPD	RO
RO_CURSOR	FORWARD	FORWARD	FORWARD
PF_RO_CURSOR	8	8	8
UPD_CURSOR	KEYSET	KEYSET	KEYSET
PF_UPD_CURSOR	8	8	8
UPD_CONCURRENCY	LOCK	LOCK	LOCK
ISOLATION	CR	CR	CR
TRANSACTION	LOCAL	LOCAL	GLOBAL

For more information on using BEHAVIOR to migrate your COBOL cursors, see the topic COBOL Program Migration Support.

You can fine tune the BEHAVIOR directive and override these default settings by providing alternate values for primitive directives. If you do this, you must set the TARGETDB directive.

Comments:

You can change the default setting to either ANSI 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 parameter overrides the default setting.
Setting this directive can also affect the SQL types returned when using Dynamic SQL. See the DESCRIBE Statement topic for more information.
OpenESQL sets default values for primitive directives depending on the value of BEHAVIOR and your target database. See the topic Primitive Directives for more information.