Use the custom SQL operator to run one or more SQL statements
that will modify the database. The custom SQL operator contains the
following pages and properties.
General page
- Label
- Type a name for the highlighted operator on the control flow canvas.
The canvas displays only the first 26 characters.
- Description
- Type a description to record additional information about the
highlighted operator.
- Database connection
- Select the database connection to use
to run the custom SQL operator.
- Execution option
- Select one of the following execution
options for running the SQL statements.
- DB2® command
line
- Run SQL statements from the DB2 command line if the DB2 database server is installed locally on your
computer. The advantage of running SQL statements through the DB2 command line is that you can
run non-SQL commands, such as LOAD and EXPORT.
- JDBC connection
- Run SQL statements through a JDBC connection
when the database server is not necessarily on the local computer.
The advantage of using a JDBC connection is that you are not restricted
to the DB2 database server.
You can also use an Informix® Dynamic
Server, Oracle Server, Microsoft SQL
Server, or any other database server that supports JDBC connectivity.
However, with the JDBC connection, you cannot execute non-SQL DB2 commands, such as LOAD and EXPORT.
Diagnostics page
- Logging level
- Select the level of information detail to write to the log file:
- Info
- Writes informational messages, warnings, and errors to the log.
This value is the default.
- Warning
- Writes warnings and errors to the log.
- Error
- Writes errors to the log.
- Tracing level
- Select the type of trace output.
Tip: Because any tracing option requires additional system resources,
use tracing only when you need to debug a problem or when IBM support
representatives ask you to use it.
- None
- No output is generated. This value is the default.
- Methods
- Traces the processing flow through the methods. Use this option,
for example, when you want to determine which nodes were run in the
execution plan graph.
- Content
- Traces the SQL statements and commands that are run. This type
of trace is useful for debugging and for listing a de-parameterized
statement. You can determine the actual values that are used for a
variable in addition to the variable name.
- Both
- Traces methods and contents.
- Skip execution
- Use this property to skip the execution of individual operators
in a control flow. Select the check box or set a boolean variable
with a value of true to skip the operator when you run the
flow. The run status of the skipped operator is assumed to be successful,
and the flow continues with the next operator.
- If you use the check box to set the skip option, you can change
the @SKIPEXECUTION activity attribute in the Administration Console
after you deploy the application.
If you use a boolean
variable to define the skip option, you can change the variable value
for the application only when you start a process. This
option sets the same value for all operators using this variable.
You can use the variable assignment operator to change the variable
inside the control flow.
SQL Statements page
- SQL Statements
- Type one or more SQL statements. You can use variables in SQL
statements to specify schema and table names, which can be assigned
values later at run time.
For example, you can type an SQL statement that
deletes all the rows in a table. The table name can be specified as
a variable as follows:
DELETE FROM GOSALES.${GRP1/Table_name}
- Statement termination character
- Type a character that will be used as the statement termination
character for the SQL statements in the entry field. The default character
is a semicolon (;).