SQL-SUPPORT

This statement supports the SQL interface and specifies limit values.

Definition

A lower-level DBH option of SYSTEM-LIMITS

Function

You use the DBH option SQL-SUPPORT to specify whether the DBH is to support the SQL interface. If necessary, you can also specify limit values for important SQL-specific resources.

If the DBH supports the SQL interface, users can use both CALL DML statements and SQL and utility statements. However, this presupposes that transaction management is activated (see the DBH option TRANSACTION-SECURITY on "TRANSACTION-SECURITY").

SQL-SUPPORT

= *YES(...) / *NO
	*YES(...)
		|	INACTIVITY-TIME = 0 / <integer 0..999>
		|	,CURSORS = 70 / <integer 0..262143>
		|	,INTERNAL-SORT-LIMIT = 200 / <integer 1..2147483647>
		|	,PLANS = 70 / <integer 1..999999>

Operands

SQL-SUPPORT = *YES(...)

The DBH supports the SQL interface.

INACTIVITY-TIME = 0 / <integer 0..999>
Maximum permitted inactivity time in minutes at the DBH's inactivity check. The inactivity time is the time during which an SQL conversation does not have a transaction open. If the inactivity time exceeds the specified limit value, the resources of the SQL conversation are reset when there is a bottleneck.
The default value for INACTIVITY-TIME is 0; i.e. an inactivity check is not carried out, and inactive conversations are not eliminated.

You can adjust the value of the INACTIVITY-TIME operand by means of the SET-USER-INACTIVE-TIME administration statement (see "SET-USER-INACTIVE-TIME") to suit requirements.

CURSORS = 70 / <integer 0..262143>

Number of concurrent cursors that can be declared in the DBH session.

You can adjust the value of the CURSORS operand by means of the RECONFIGURE-DBH-SESSION administration statement (see "RECONFIGURE-DBH-SESSION").

INTERNAL-SORT-LIMIT = 200 / <integer 1..2147483647>
Maximum number of records that a cursor table can contain if the records are to be sorted in accordance with the cursor declaration.
If the number of records found during the sort exceeds this limit value, processing of the statement is aborted.

You can adjust the value of the INTERNAL-SORT-LIMIT operand by means of the MODIFY-SQL-SORT-LIMIT administration statement (see "MODIFY-SQL-SORT-LIMIT") to suit requirements.

PLANS = 70 / <integer 1..999999>
Minimum number of concurrently available SQL access plans.

You can adjust the value of the PLANS operand by means of the RECONFIGURE-DBH-SESSION administration statement (see "RECONFIGURE-DBH-SESSION").

SQL-SUPPORT = *NO
The DBH does not support the SQL interface. As a result, the DBH does not require so many Mbytes of virtual address space.
You cannot specify SQL-SUPPORT=*NO unless only CALL DML applications are to run in the DBH session. Utility statements are not permitted in this session either.

Size of the plan buffer

The plan buffer is an area of main memory reserved by the DBH exclusively for SQL access plans.

The size of the plan buffer depends essentially on the size of the area for retrieval statements. This is set by means of the DBH option COLUMNS.
In the case of the default values PLAN=70, COLUMNS=256 and USERS=24, the size of the plan buffer is approximately 1.1 Mbytes.

The “ Performance” manual describes when it makes sense to modify the size of the plan buffer the next time the DBH is started up.