Rational Developer for System z
Enterprise PL/I for z/OS, Version 3.8, Programming Guide

SQL preprocessor

Programming and compilation considerations
SQL preprocessor options
Coding SQL statements in PL/I applications
Defining the SQL communications area
Defining SQL descriptor areas
Embedding SQL statements
Using host variables
Determining equivalent SQL and PL/I data types
Additional Information on Large Object (LOB) support
General information on LOBs
PL/I variable declarations for LOB Support
Determining compatibility of SQL and PL/I data types
Using host structures
Using indicator variables
Host structure example
Using the SQL preprocessor with the compiler user exit (IBMUEXIT)
DECLARE STATEMENT statements

In general, the coding for your PL/I program will be the same whether or not you want it to access a DB2 database. However, to retrieve, update, insert, and delete DB2 data and use other DB2 services, you must use SQL statements. You can use dynamic and static EXEC SQL statements in PL/I applications.

To communicate with DB2, you need to do the following:

Before you can take advantage of EXEC SQL support, you must have authority to access a DB2 system. Contact your local DB2 Database Administrator for your authorization.

The PL/I SQL Preprocessor now supports DBCS in the same manner as the PL/I compiler does. When the GRAPHIC PL/I compiler option is in effect, some source language elements can be written using DBCS and SBCS characters. In particular, you can use DBCS characters in the source program in following places:


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)