EXECSQL statement
The EXECSQL statement directs
Log Master
to execute a set of SQL statements against a Db2 database.
Log Master
uses the High-speed Apply Engine to execute SQL statements.
The following figure shows the EXECSQL statement syntax.
Option | Description | ||||||
|---|---|---|---|---|---|---|---|
SQLDataSetName | Specifies the name of a data set containing valid ANSI SQL statements. | ||||||
BINDOWNER (authid) | Specifies an authorization ID that has authority within Db2 security to bind programs and generate plans. Log Master uses this authorization ID to bind an application plan whenever Log Master executes generated SQL statements. The default value of this keyword depends on the value of the BINDOWN= installation option. If your environment does not specify a value for BINDOWN, Log Master uses the user ID of the user who submitted the job. | ||||||
DECIMAL POINT | Defines the character that was used to delineate fractional values in the SQL generated by the product. The default value for this keyword is the character specified in the DSNHDECP module of the target Db2 subsystem.
| ||||||
PLAN NAME (planName) | Specifies the name of an existing plan that Log Master uses to access data during execution of the generated SQL. Log Master creates or updates this plan during processing and uses it to access the required data. The default value for planName is the character constant ALP, followed by the job number (for example, 'ALP00302'). See also PLANESQL=ALP. | ||||||
FREE | NOFREE | The FREE and NOFREE keywords determine the persistence of information about the plan defined by planName.
| ||||||
SQLPRINT | Determines the content of the SQLPRINT data set. Log Master writes the results of SQL execution (including SQL codes and statement identifiers) into the SQLPRINT data set as it executes generated SQL statements.
For more information, see SQLPRINT in Specifying-the-DD-statements. |