Creating an application using the remote query and stored procedure adapter

The following example show you how to create a stored procedure, a subscription to the stored procedure, and a DB2 Everyplace application to use the stored procedure. The purpose of the example application is to allow a mobile user to check an account balance and transfer money between a savings and a checking account by using a DB2 Everyplace remote stored procedure call.

Prerequisites

The remote query and stored procedure adapter supports the Win32 (non-unicode), WinCE, Symbian, and Palm OS client platforms. The remote query and stored procedure adapter requires that the stored procedures are registered to DB2.

Restrictions

Multiple connections
DB2 Everyplace supports one connection to the local database and one connection to the remote database with some limitations. The application must connect to the local database first (if a local connection is needed), then connect to the remote database (if a remote connection is needed). The allocated connection handles should be freed together.
Statement handle
User should allocate only one statement handle for the remote connection.
On Palm OS, the application stack size may need to be increased.
On Win32 operating systems, at run time the IBM Sync Client DLL files must be included in the local directory or system path.
In a DB2 Universal Database stored procedure, if a binary large object (BLOB) is used as an input or output parameter, the first four bytes of the BLOB data are reserved to indicate length.

Procedure

To create a stored procedure, a subscription to the stored procedure, and a DB2 Everyplace application to use the stored procedure using the sample application:

Conceptos relacionados

The remote query and stored procedure adapter

Tareas relacionadas

Creating the Agent Adapter subscription for the sample application

Consulta relacionada