Valid SQL statements in an SQL package

 

Programs that are connected to another server can use any of the SQL statements except the SET TRANSACTION statement.

Programs compiled with DB2^® UDB for iSeries™ that refer to a remote database that is not DB2 UDB for iSeries can use executable SQL statements supported by the remote database. The precompiler will continue to issue diagnostic messages for statements that it does not understand. These statements are sent to the remote system during the creation of the SQL package. The runtime support will return an SQLCODE of -84 or -525 when the statement cannot be run on the current application server. For example, multiple-row FETCH, blocked INSERT, and scrollable cursor support are allowed only in distributed programs where both the application requester and the application server are running on the i5/OS^® V5R2, or later, with the following exception. An application requester that is not running on the i5/OS operating system can issue read-only, insensitive scrollable cursor operations on an i5/OS V5R3 application server. A further restriction on the use of multiple-row FETCH statements, blocked INSERT statements, and scrollable cursors is that the transmission of binary large object (BLOB), character large object (CLOB), and double-byte character large object (DBCLOB) data is not allowed when those functions are used.

 

Parent topic:

SQL package support

 

Related information

Characteristics of SQL statements