Rbafy-Database SQL Programming 7.1

IBM
IBM i
Database
SQL programming
7.1
IBM
IBM i
Database
SQL programming
7.1
Note
Before using this information and the product it supports, read the information in Notices, on
page 493.
This edition applies to IBM i 7.1 (product number 5770-SS1) and to all subsequent releases and modifications until
otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC)
models nor does it run on CISC models.
Copyright IBM Corporation 1998, 2010.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
SQL programming . . . . . . . . ..
|
|
|
What's new for IBM i 7.1 . . . . . . . . ..

1
PDF file for SQL programming . . . . . . ..
4
Introduction to DB2 for i Structured Query Language 4
SQL concepts . . . . . . . . . . . ..
5
SQL relational database and system
terminology . . . . . . . . . . ..
6
SQL and system naming conventions . . ..
7
Types of SQL statements . . . . . . ..
7
SQL communication area . . . . . . ..
9
SQL diagnostics area. . . . . . . . ..
9
SQL objects . . . . . . . . . . . . ..
9
Schemas . . . . . . . . . . . . ..
9
Journals and journal receivers . . . . ..
9
Catalogs . . . . . . . . . . . ..
10
Tables, rows, and columns . . . . . ..
10
Aliases . . . . . . . . . . . . ..
10
Views . . . . . . . . . . . . ..
10
Indexes . . . . . . . . . . . . ..
11
Constraints . . . . . . . . . . ..
11
Triggers . . . . . . . . . . . ..
12
Stored procedures . . . . . . . . ..
12
Sequences . . . . . . . . . . . ..
12
Global variables . . . . . . . . . ..
12
User-defined functions. . . . . . . ..
12
User-defined types . . . . . . . . ..
13
XSR objects . . . . . . . . . . ..
13
SQL packages . . . . . . . . . ..
13
Application program objects . . . . . . ..
13
User source file . . . . . . . . . ..
15
Output source file member . . . . . ..
15
Program . . . . . . . . . . . ..
15
SQL package . . . . . . . . . . ..
15
Module . . . . . . . . . . . . ..
16
Service program . . . . . . . . . ..
16
Data definition language . . . . . . . . ..
16
Creating a schema . . . . . . . . . ..
16
Creating a table . . . . . . . . . . ..
17
Adding and removing constraints . . . ..
17
Referential integrity and tables . . . . ..
18
Adding and removing referential
constraints. . . . . . . . . . ..
18
Example: Adding referential constraints ..
19
Example: Removing constraints. . . . ..
20
Check pending . . . . . . . . . ..
20
Creating a table using LIKE . . . . . . ..
21
Creating a table using AS. . . . . . . ..
21
Creating and altering a materialized query table 22
Declaring a global temporary table . . . ..
23
Creating a table with remote server data . ..
23
Creating a row change timestamp column . ..
24
Creating and altering an identity column . ..
24
Using ROWID . . . . . . . . . . ..
25
Creating and using sequences . . . . . ..
26
Comparison of identity columns and
sequences . . . . . . . . . . . ..
27
Copyright IBM Corp. 1998, 2010
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Defining field procedures. . . . . . . ..

Field definition for field procedures . . ..
Specifying the field procedure . . . . ..
When field procedures are invoked . . ..
Parameter list for execution of field
procedures . . . . . . . . . . ..
The field procedure parameter value list
(FPPVL) . . . . . . . . . . ..
Parameter value descriptors for field
procedures . . . . . . . . . ..
Field-definition (function code 8) . . ..
Field-encoding (function code 0) . . ..
Field-decoding (function code 4) . . ..
Example field procedure program . . ..
General guidelines for writing field
procedures . . . . . . . . . . ..
Index considerations . . . . . . ..
Thread considerations . . . . . . ..
Debug considerations . . . . . . ..
Guidelines for writing field procedures that
mask data . . . . . . . . . . . ..
Example field procedure program that
masks data . . . . . . . . . ..
Creating descriptive labels using the LABEL ON
statement . . . . . . . . . . . . ..
Describing an SQL object using COMMENT ON
Changing a table definition . . . . . . ..
Adding a column . . . . . . . . ..
Changing a column. . . . . . . . ..
Allowable conversions of data types . . ..
Deleting a column . . . . . . . . ..
Order of operations for the ALTER TABLE
statement . . . . . . . . . . . ..
Using CREATE OR REPLACE TABLE . ..
Creating and using ALIAS names . . . . ..
Creating and using views. . . . . . . ..
WITH CHECK OPTION on a view . . ..
WITH CASCADED CHECK OPTION ..
WITH LOCAL CHECK OPTION . . ..
Example: Cascaded check option . . ..
Creating indexes. . . . . . . . . . ..
Creating and using global variables . . . ..
Replacing existing objects. . . . . . . ..
Catalogs in database design . . . . . . ..
Getting catalog information about a table ..
Getting catalog information about a column
Dropping a database object . . . . . . ..
Data manipulation language. . . . . . . ..
Retrieving data using the SELECT statement ..
Basic SELECT statement . . . . . . ..
Specifying a search condition using the
WHERE clause . . . . . . . . . ..
Expressions in the WHERE clause . . ..
Comparison operators . . . . . . ..
NOT keyword . . . . . . . . ..
GROUP BY clause . . . . . . . . ..
28
29
29
29
30
32
32
33
34
35
36
37
38
38
38
38
41
42
43
44
44
44
45
46
46
47
48
48
50
51
51
52
53
53
54
54
55
55
55
56
56
56
57
58
59
60
60
iii
HAVING clause . . . . . . . . . ..
ORDER BY clause . . . . . . . . ..
Static SELECT statements. . . . . . ..
Handling null values . . . . . . . ..
Special registers in SQL statements . . ..
Casting data types . . . . . . . . ..
Date, time, and timestamp data types . ..
Specifying current date and time values ..
Date/time arithmetic . . . . . . ..
Row change expressions . . . . . . ..
Handling duplicate rows . . . . . . ..
Defining complex search conditions . . ..
Special considerations for LIKE . . . ..
Multiple search conditions within a
WHERE clause . . . . . . . . ..
Using OLAP specifications . . . . . ..
Joining data from more than one table . ..
Inner join . . . . . . . . . . ..
Left outer join . . . . . . . . ..
Right outer join . . . . . . . . ..
Exception join . . . . . . . . ..
Cross join . . . . . . . . . . ..
Full outer join . . . . . . . . ..
Multiple join types in one statement . ..
Using table expressions . . . . . . ..
Using recursive queries . . . . . . ..
Using the UNION keyword to combine
subselects . . . . . . . . . . . ..
Specifying the UNION ALL keyword. ..
Using the EXCEPT keyword . . . . ..
Using the INTERSECT keyword . . . ..
Data retrieval errors . . . . . . . ..
Inserting rows using the INSERT statement ..
Inserting rows using the VALUES clause ..
Inserting rows using a select-statement . ..
Inserting multiple rows using the blocked
INSERT statement . . . . . . . . ..
Inserting data into tables with referential
constraints . . . . . . . . . . ..
Inserting values into an identity column ..
Selecting inserted values. . . . . . ..
Inserting data from a remote database . ..
Changing data in a table using the UPDATE
statement . . . . . . . . . . . . ..
Updating a table using a scalar-subselect ..
Updating a table with rows from another
table . . . . . . . . . . . . ..
Updating tables with referential constraints
Examples: UPDATE rules . . . . ..
Updating an identity column . . . . ..
Updating data as it is retrieved from a table
Removing rows from a table using the DELETE
statement . . . . . . . . . . . . ..
Removing rows from tables with referential
constraints . . . . . . . . . . ..
Example: DELETE rules . . . . . ..
Merging data . . . . . . . . . . ..
Using subqueries . . . . . . . . . ..
Subqueries in SELECT statements . . ..
Subqueries and search conditions. . ..
Usage notes on subqueries . . . . ..
iv
IBM i: Database SQL programming
62
63
65
65
66
68
68
68
69
69
69
70
71
72
73
76
76
77
78
78
79
80
81
81
83
95
98
100
102
104
105
106
107
108
108
109
110
110
111
112
112
113
114
114
114
116
117
118
119
120
121
122
122
|
|
Including subqueries in the WHERE or

HAVING clause . . . . . . . ..
Correlated subqueries . . . . . . ..
Correlated names and references . . ..
Example: Correlated subquery in a
WHERE clause . . . . . . . . ..
HAVING clause . . . . . . . ..
select-list . . . . . . . . . . ..
Example: Correlated subquery in an
UPDATE statement . . . . . . ..
DELETE statement . . . . . . ..
Sort sequences and normalization in SQL . . ..
Sort sequence used with ORDER BY and row
selection . . . . . . . . . . . . ..
Sort sequence and ORDER BY . . . . ..
Sort sequence and row selection . . . ..
Sort sequence and views . . . . . . ..
Sort sequence and the CREATE INDEX
statement. . . . . . . . . . . . ..
Sort sequence and constraints . . . . . ..
ICU sort sequence . . . . . . . . . ..
Normalization . . . . . . . . . . ..
Data protection . . . . . . . . . . . ..
Security for SQL objects . . . . . . . ..
Authorization ID . . . . . . . . ..
Views . . . . . . . . . . . . ..
Auditing . . . . . . . . . . . ..
Data integrity . . . . . . . . . . ..
Concurrency. . . . . . . . . . ..
Journaling . . . . . . . . . . ..
Commitment control . . . . . . . ..
Savepoints . . . . . . . . . . ..
Atomic operations . . . . . . . . ..
Constraints . . . . . . . . . . ..
Adding and using check constraints . ..
Save and restore functions . . . . . ..
Damage tolerance . . . . . . . . ..
Index recovery . . . . . . . . . ..
Catalog integrity . . . . . . . . ..
User auxiliary storage pool . . . . . ..
Independent auxiliary storage pool . . ..
Routines . . . . . . . . . . . . . ..
Stored procedures . . . . . . . . . ..
Defining an external procedure . . . ..
Defining an SQL procedure. . . . . ..
Defining a procedure with default
parameters . . . . . . . . . . ..
Calling a stored procedure . . . . . ..
Using the CALL statement where
procedure definition exists . . . . ..
Using the embedded CALL statement
where no procedure definition exists ..
Using the embedded CALL statement
with an SQLDA . . . . . . . ..
Using the dynamic CALL statement where
no CREATE PROCEDURE exists . . ..
Examples: CALL statements . . . ..
Returning result sets from stored procedures
123
124
124
125
126
127
127
128
128
129
129
131
131
132
132
132
133
134
134
135
135
135
136
136
138
138
142
144
145
146
146
147
148
148
149
149
149
149
150
151
156
158
158
159
160
161
161
167
|
|
|
|
|
|
|
|
|
|
|
|
Example 1: Calling a stored procedure

that returns a single result set . . . ..
Example 2: Calling a stored procedure
that returns a result set from a nested
procedure . . . . . . . . . ..
Writing a program or SQL procedure to
receive the result sets from a stored
procedure . . . . . . . . . . ..
Parameter passing conventions for stored
procedures and user-defined functions . ..
Indicator variables and stored procedures
Returning a completion status to the calling
program . . . . . . . . . . . ..
Passing parameters from DB2 to external
proceduress . . . . . . . . . . ..
Parameter style SQL . . . . . . ..
Parameter style GENERAL . . . . ..
Parameter style GENERAL WITH NULLS
Parameter style DB2GENERAL . . ..
Parameter style Java . . . . . . ..
Using user-defined functions . . . . . ..
UDF concepts . . . . . . . . . ..
Writing UDFs as SQL functions . . . ..
Example: SQL scalar UDFs . . . . ..
Example: SQL table UDFs . . . . ..
Writing UDFs as external functions . . ..
Registering UDFs . . . . . . . ..
Passing arguments from DB2 to external
functions . . . . . . . . . . ..
Table function considerations . . . ..
Error processing for UDFs . . . . ..
Threads considerations . . . . . ..
Parallel processing. . . . . . . ..
Fenced or unfenced considerations . ..
Save and restore considerations . . ..
Examples: UDF code . . . . . . . ..
Example: Square of a number UDF . ..
Example: Counter . . . . . . . ..
Example: Weather table function . . ..
Using UDFs in SQL statements . . . ..
Using parameter markers or the NULL
values as function arguments . . . ..
Using qualified function references . ..
Using unqualified function references ..
Summary of function references . . ..
Triggers . . . . . . . . . . . . ..
SQL triggers . . . . . . . . . . ..
BEFORE SQL triggers . . . . . ..
AFTER SQL triggers . . . . . . ..
Multiple event SQL triggers . . . ..
INSTEAD OF SQL triggers . . . . ..
Handlers in SQL triggers . . . . ..
SQL trigger transition tables . . . ..
External triggers . . . . . . . . ..
Array support in SQL procedures . . . ..
Debugging an SQL routine . . . . . . ..
Obfuscating an SQL routine . . . . . ..
Managing SQL and external routine objects ..
Improving performance of procedures and
functions . . . . . . . . . . . . ..
168
169
174
180
185
187
187
187
189
189
189
190
190
190
192
193
193
194
194
197
203
203
204
204
204
205
205
205
207
208
214
214
214
215
216
217
218
219
220
221
222
224
225
225
226
227
228
230
231
|
|
|
|
|
|
Improving implementation of procedures and

functions . . . . . . . . . . . ..
Redesigning routines for performance . ..
Processing special data types . . . . . . ..
Large objects . . . . . . . . . . ..
Large object data types . . . . . . ..
Large object locators . . . . . . . ..
Example: Using a locator to work with a
CLOB value . . . . . . . . . . ..
Example: LOBLOC in C . . . . . ..
Example: LOBLOC in COBOL . . . ..
Indicator variables and LOB locators . ..
LOB file reference variables . . . . ..
Example: Extracting CLOB data to a file ..
Example: LOBFILE in C . . . . . ..
Example: LOBFILE in COBOL . . . ..
Example: Inserting data into a CLOB column
Displaying the layout of LOB columns . ..
Journal entry layout of LOB columns . ..
User-defined distinct types . . . . . . ..
Defining a UDT . . . . . . . . ..
Example: Money . . . . . . . ..
Example: Resum . . . . . . . ..
Defining tables with UDTs . . . . . ..
Example: Sales . . . . . . . . ..
Example: Application forms . . . ..
Manipulating UDTs . . . . . . . ..
Examples: Using UDTs . . . . . . ..
Example: Comparisons between UDTs and
constants . . . . . . . . . . ..
Example: Casting between UDTs . . ..
Example: Comparisons involving UDTs
Example: Sourced UDFs involving UDTs
Example: Assignments involving UDTs
Example: Assignments in dynamic SQL
Example: Assignments involving different
UDTs . . . . . . . . . . . ..
Example: Using UDTs in UNION. . ..
Examples: Using UDTs, UDFs, and LOBs . ..
Example: Defining the UDT and UDFs . ..
Example: Using the LOB function to
populate the database . . . . . . ..
Example: Using UDFs to query instances of
UDTs . . . . . . . . . . . . ..
Example: Using LOB locators to manipulate
UDT instances . . . . . . . . . ..
Using DataLinks . . . . . . . . . ..
Linking control levels in DataLinks . . ..
NO LINK CONTROL . . . . . ..
FILE LINK CONTROL with FS
permissions . . . . . . . . . ..
FILE LINK CONTROL with DB
permissions . . . . . . . . . ..
Working with DataLinks . . . . . ..
SQL statements and SQL/XML functions . . ..
XML input and output overview . . . . ..
Comparison of XML and relational models ..
Tutorial for XML . . . . . . . . . ..
Exercise 1: Creating a table that can store
XML data . . . . . . . . . . ..
Contents
231
233
234
234
235
235
236
236
238
239
239
240
241
242
243
243
243
244
244
245
245
245
245
246
246
246
246
247
248
248
249
249
249
250
251
251
252
252
253
253
254
254
254
255
255
257
258
259
261
261
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Exercise 2: Inserting XML documents into

XML typed columns . . . . . . . ..
Exercise 3: Updating XML documents stored
in an XML column . . . . . . . ..
Exercise 4: Validating XML documents
against XML schemas . . . . . . ..
Exercise 5: Transforming with XSLT
stylesheets . . . . . . . . . . ..
Inserting XML data . . . . . . . . ..
Addition of XML columns to existing tables
Insertion into XML columns . . . . ..
XML parsing . . . . . . . . . ..
SQL/XML publishing functions for constructing
XML values . . . . . . . . . . . ..
Example: Construct an XML document with
values from a single table . . . . . ..
values from multiple tables. . . . . ..
values from table rows that contain null
elements . . . . . . . . . . . ..
Example: Transforming with XSLT stylesheets
Example: Using XSLT as a formatting engine
Example: Using XSLT for data exchange ..
Example: Using XSLT to remove namespaces
Important considerations for transforming
XML documents . . . . . . . . ..
Special character handling in SQL/XML
publishing functions . . . . . . . ..
XML serialization . . . . . . . . ..
Differences in an XML document after
storage and retrieval . . . . . . . ..
Data types for archiving XML documents
Using XMLTABLE to reference XML content as
a relational table . . . . . . . . . ..
Example: Use XMLTABLE to handle missing
elements . . . . . . . . . . . ..
Example: Use XMLTABLE to subset result
data . . . . . . . . . . . . ..
Example: Use XMLTABLE to handle multiple
values . . . . . . . . . . . . ..
Example: Use XMLTABLE with namespaces
Example: Number result rows for
XMLTABLE . . . . . . . . . . ..
Updating XML data . . . . . . . . ..
Deletion of XML data from tables . . ..
XML schema repository . . . . . . . ..
Application programming language support ..
XML column inserts and updates in CLI
applications . . . . . . . . . . ..
XML data retrieval in CLI applications . ..
Declaring XML host variables in embedded
SQL applications . . . . . . . . ..
Example: Referencing XML host variables
in embedded SQL applications . . ..
Recommendations for developing
embedded SQL applications with XML ..
Identifying XML values in an SQLDA ..
Java . . . . . . . . . . . . ..
XML data in JDBC applications . . ..
XML data in SQLJ applications . . ..
vi
261
262
263
265
267
267
268
269
270
271
272
273
273
275
277
278
281
281
282
284
284
284
286
286
287
289
291
292
293
293
294
294
295
296
297
298
298
298
298
304
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Routines . . . . . . . . . . . ..
XML support in SQL procedures . . ..
XML data type support in external
routines . . . . . . . . . . ..
XML data encoding . . . . . . . . ..
Encoding considerations when storing or
passing XML data . . . . . . . . ..
Encoding considerations for input of XML
data to a database . . . . . . . ..
Encoding considerations for retrieval of
XML data from a database . . . . ..
Encoding considerations for passing XML
data in routine parameters . . . . ..
Encoding considerations for XML data in
JDBC and SQLJ applications . . . ..
Effects of XML encoding and serialization on
data conversion . . . . . . . . ..
Encoding scenarios for input of internally
encoded XML data to a database . . ..
Encoding scenarios for input of externally
encoded XML data to a database . . ..
Encoding scenarios for retrieval of XML
data with implicit serialization . . ..
Encoding scenarios for retrieval of XML
data with explicit XMLSERIALIZE . ..
Mappings of encoding names to effective
CCSIDs for stored XML data . . . . ..
Mappings of CCSIDs to encoding names for
serialized XML output data. . . . . ..
Annotated XML schema decomposition . ..
Decomposing XML documents with
annotated XML schemas. . . . . . ..
Registering and enabling XML schemas for
decomposition . . . . . . . . . ..
Sources for annotated XML schema
decomposition . . . . . . . . . ..
XML decomposition annotations . . . ..
Specification and scope of XML
decomposition annotations . . . . ..
Annotations as attributes . . . . ..
Annotations as structured child elements
Global annotations . . . . . . ..
XML decomposition annotations Summary. . . . . . . . . . ..
db2-xdb:defaultSQLSchema decomposition
annotation . . . . . . . . . ..
db2-xdb:rowSet decomposition annotation
db2-xdb:table decomposition annotation
db2-xdb:column decomposition annotation
db2-xdb:locationPath decomposition
annotation . . . . . . . . . ..
db2-xdb:expression decomposition
annotation . . . . . . . . . ..
db2-xdb:condition decomposition
annotation . . . . . . . . . ..
db2-xdb:contentHandling decomposition
annotation . . . . . . . . . ..
db2-xdb:normalization decomposition
annotation . . . . . . . . . ..
db2-xdb:order decomposition annotation
306
307
307
311
312
312
312
312
312
313
313
315
316
319
321
321
321
321
322
322
322
323
323
323
324
324
326
327
331
333
335
338
341
344
348
350
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
db2-xdb:truncate decomposition
annotation . . . . . . . . . ..
db2-xdb:rowSetMapping decomposition
annotation . . . . . . . . . ..
db2-xdb:rowSetOperationOrder
decomposition annotation . . . . ..
Keywords for annotated XML schema
decomposition . . . . . . . . ..
Treatment of CDATA sections in annotated
XML schema decomposition . . . . ..
NULL values and empty strings in annotated
XML schema decomposition . . . . ..
Checklist for annotated XML schema
decomposition . . . . . . . . . ..
Examples of mappings in annotated XML
schema decomposition . . . . . . . ..
Annotations of derived complex types . ..
Decomposition annotation example: Mapping
to an XML column . . . . . . . ..
Decomposition annotation example: A value
mapped to a single table that yields a single
row . . . . . . . . . . . . ..
mapped to a single table that yields multiple
rows . . . . . . . . . . . . ..
mapped to multiple tables . . . . . ..
Decomposition annotation example:
Grouping multiple values mapped to a single
table . . . . . . . . . . . . ..
Decomposition annotation example: Multiple
values from different contexts mapped to a
single table . . . . . . . . . . ..
XML schema to SQL types compatibility for
annotated schema decomposition. . . ..
Limits and restrictions for annotated XML
schema decomposition . . . . . . ..
Schema for XML decomposition annotations
Using SQL in different environments . . . ..
Using a cursor . . . . . . . . . . ..
Types of cursors . . . . . . . . ..
Examples: Using a cursor . . . . . ..
Step 1: Defining the cursor . . . . ..
Step 2: Opening the cursor . . . . ..
Step 3: Specifying what to do when the
end of data is reached . . . . . ..
Step 4: Retrieving a row using a cursor
Step 5a: Updating the current row . ..
Step 5b: Deleting the current row. . ..
Step 6: Closing the cursor . . . . ..
Using the multiple-row FETCH statement
Multiple-row FETCH using a host
structure array . . . . . . . . ..
Multiple-row FETCH using a row storage
area . . . . . . . . . . . ..
Unit of work and open cursors . . . ..
Dynamic SQL applications . . . . . . ..
Designing and running a dynamic SQL
application . . . . . . . . . . ..
CCSID of dynamic SQL statements . . ..
Processing non-SELECT statements . . ..
352
354
356
357
358
358
359
360
360
366
367
368
370
371
373
375
381
382
383
383
383
384
386
387
387
388
389
389
389
390
390
392
394
395
395
396
396
Using the PREPARE and EXECUTE

statements . . . . . . . . . ..
Processing SELECT statements and using a
descriptor . . . . . . . . . . ..
Fixed-list SELECT statements . . . ..
Varying-list SELECT statements . . ..
SQL descriptor areas . . . . . . ..
SQLDA format . . . . . . . . ..
Example: A SELECT statement for
allocating storage for SQLDA . . . ..
Example: A SELECT statement using an
allocated SQL descriptor. . . . . ..
Parameter markers . . . . . . ..
Using interactive SQL . . . . . . . ..
Starting interactive SQL . . . . . . ..
Using the statement entry function . . ..
Prompting . . . . . . . . . . ..
Syntax checking . . . . . . . ..
Statement processing mode. . . . ..
Subqueries . . . . . . . . . ..
CREATE TABLE prompting . . . ..
Entering DBCS data . . . . . . ..
Using the list selection function . . . ..
Example: Using the list selection function
Session services description . . . . ..
Exiting interactive SQL . . . . . . ..
Using an existing SQL session . . . . ..
Recovering an SQL session . . . . . ..
Accessing remote databases with interactive
SQL . . . . . . . . . . . . ..
Using the SQL statement processor . . . ..
Execution of statements after errors occur
Commitment control in the SQL statement
processor . . . . . . . . . . . ..
Source listing for the SQL statement
processor . . . . . . . . . . . ..
Using the RUNSQL CL command . . . ..
Distributed relational database function and SQL
DB2 for i distributed relational database support
DB2 for i distributed relational database
example program . . . . . . . . . ..
SQL package support. . . . . . . . ..
Valid SQL statements in an SQL package ..
Considerations for creating an SQL package
CRTSQLPKG authorization . . . . ..
Creating a package on a database other
than DB2 for i . . . . . . . . ..
Target release (TGTRLS) parameter . ..
SQL statement size . . . . . . ..
Statements that do not require a package
Package object type . . . . . . ..
ILE programs and service programs . ..
Package creation connection . . . ..
Unit of work . . . . . . . . ..
Creating packages locally . . . . ..
Labels . . . . . . . . . . . ..
Consistency token . . . . . . . ..
SQL and recursion. . . . . . . ..
CCSID considerations for SQL. . . . . ..
Connection management and activation groups
Source code for PGM1 . . . . . . ..
Contents
396
397
397
398
399
399
402
406
408
410
411
412
412
414
414
414
414
414
415
415
417
418
419
419
419
421
423
423
423
425
427
427
428
429
430
430
430
430
431
431
431
432
432
432
432
432
432
432
433
433
433
434
vii
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

Multiple connections to the same relational
database . . . . . . . . . . . ..
Implicit connection management for the
default activation group . . . . . . ..
Implicit connection management for
nondefault activation groups . . . . ..
Distributed support . . . . . . . . ..
Determining the connection type . . . ..
Connect and commitment control restrictions
Determining the connection status . . ..
Distributed unit of work connection
considerations . . . . . . . . . ..
Ending connections . . . . . . . ..
Distributed unit of work. . . . . . . ..
Managing distributed unit of work
connections . . . . . . . . . . ..
Checking the connection status . . . ..
Cursors and prepared statements . . . ..
DRDA stored procedure considerations. . ..
WebSphere MQ with DB2 . . . . . . . ..
WebSphere MQ messages . . . . . . ..
WebSphere MQ message handling . . ..
DB2 MQ services . . . . . . . ..
DB2 MQ policies . . . . . . . ..
DB2 MQ functions. . . . . . . . . ..
DB2 MQ dependencies . . . . . . ..
DB2 MQ tables . . . . . . . . . . ..
DB2 MQ CCSID conversion . . . . . ..
Websphere MQ transactions . . . . . ..
Basic messaging with WebSphere MQ . . ..
Sending messages with WebSphere MQ . ..
Retrieving messages with WebSphere MQ . ..
Application to application connectivity with
WebSphere MQ. . . . . . . . . . ..
Reference. . . . . . . . . . . . . ..
DB2 for i sample tables . . . . . . . ..
Department table (DEPARTMENT) . . ..
DEPARTMENT . . . . . . . . ..
Employee table (EMPLOYEE) . . . . ..
EMPLOYEE . . . . . . . . . ..
Employee photo table (EMP_PHOTO) . ..
EMP_PHOTO . . . . . . . . ..
viii
434
435
437
438
439
439
440
442
442
444
444
445
445
447
447
448
448
449
449
450
450
451
452
453
458
459
460
461
462
463
463
463
464
465
465
466
467
468
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Employee resum table (EMP_RESUME) ..

EMP_RESUME . . . . . . . . ..
Employee to project activity table
(EMPPROJACT) . . . . . . . . ..
EMPPROJACT . . . . . . . . ..
Project table (PROJECT) . . . . . . ..
PROJECT. . . . . . . . . . ..
Project activity table (PROJACT) . . . ..
PROJACT . . . . . . . . . ..
Activity table (ACT) . . . . . . . ..
ACT . . . . . . . . . . . ..
Class schedule table (CL_SCHED) . . ..
CL_SCHED . . . . . . . . . ..
In-tray table (IN_TRAY) . . . . . . ..
IN_TRAY . . . . . . . . . . ..
Organization table (ORG) . . . . . ..
ORG . . . . . . . . . . . ..
Staff table (STAFF) . . . . . . . ..
STAFF . . . . . . . . . . . ..
Sales table (SALES) . . . . . . . ..
SALES. . . . . . . . . . . ..
Sample XML tables . . . . . . . ..
Product table (PRODUCT) . . . . . ..
PRODUCT . . . . . . . . . ..
Purchase order table (PURCHASEORDER)
PURCHASEORDER . . . . . . ..
Customer table (CUSTOMER) . . . . ..
CUSTOMER . . . . . . . . . ..
Catalog table (CATALOG) . . . . . ..
CATALOG . . . . . . . . . ..
Suppliers table (SUPPLIERS) . . . . ..
SUPPLIERS . . . . . . . . . ..
Inventory table (INVENTORY) . . . ..
INVENTORY . . . . . . . . ..
Product Supplier table
(PRODUCTSUPPLIER) . . . . . . ..
PRODUCTSUPPLIER. . . . . . ..
DB2 for i CL command descriptions . . . ..
Appendix. Notices . . . . . . . ..
Programming interface information .
Trademarks . . . . . . . . .
Terms and conditions. . . . . .
.
.
.
.
.
.
.
.
.
468
469
469
470
471
472
473
474
476
476
477
477
477
478
478
479
479
480
481
481
482
482
483
484
485
487
488
489
489
489
490
490
490
490
491
491
493
..
..
..
494
495
495
SQL programming
The DB2 for IBM i database provides a wide range of support for Structured Query Language (SQL).
The examples of SQL statements shown in this topic collection are based on the sample tables and
assume that the following statements are true:
v They are shown in the interactive SQL environment or they are written in ILE C or in COBOL. EXEC
SQL and END-EXEC are used to delimit an SQL statement in a COBOL program.
v Each SQL example is shown on several lines, with each clause of the statement on a separate line.
v SQL keywords are highlighted.
v Table names provided in the sample tables use the schema CORPDATA. Table names that are not
found in the Sample Tables should use schemas you create.
v Calculated columns are enclosed in parentheses, (), and brackets, [].
v The SQL naming convention is used.
v The APOST and APOSTSQL precompiler options are assumed although they are not the default
options in COBOL. Character string literals within SQL and host language statements are delimited by
single-quotation marks (').
v A sort sequence of *HEX is used, unless otherwise noted.
Whenever the examples vary from these assumptions, it is stated.
Because this topic collection is for the application programmer, most of the examples are shown as if they
were written in an application program. However, many examples can be slightly changed and run
interactively by using interactive SQL. The syntax of an SQL statement, when using interactive SQL,
differs slightly from the format of the same statement when it is embedded in a program.
Note: By using the code examples, you agree to the terms of the Code license and disclaimer
information on page 491.
Related concepts:
Embedded SQL programming
Related reference:
DB2 for i sample tables on page 463
These sample tables are referred to and used in the SQL programming and the SQL reference topic
collections.
DB2 for i5/OS SQL reference
|
What's new for IBM i 7.1
Read about new or significantly changed information for the SQL programming topic collection.
Result sets returned to programs
|
|
|
You can return a result set from a stored procedure to a program and have the program consume the
result set. For more information, see Writing a program or SQL procedure to receive the result sets from
a stored procedure on page 174.
XML
| The XML data type has been added to SQL. This includes internal handling of XML values and XML
| schema decomposition. For more information, see SQL statements and SQL/XML functions on page
| 257.
|
Field procedures
|
|
|
|
|
A field procedure is a user-written exit routine to transform values in a single column. When values in
the column are changed, or new values inserted, the field procedure is invoked for each value, and can
transform that value (encode it) in any way. The encoded value is then stored. When values are retrieved
from the column, the field procedure is invoked for each value, which is encoded, and must decode it
back to the original value. For more information, see Defining field procedures on page 28.
MERGE statement
| The MERGE statement can be used to either insert new rows or update existing rows in a table or view,
| depending on whether they already exists in the table or view. For more information, see Merging data
| on page 119.
|
Global variables
| Global variables can be created and used in SQL. For more information, see Creating and using global
| variables on page 53.
|
Arrays in SQL procedures
| An array data type has been added for use in SQL procedures. For more information, see Array support
| in SQL procedures on page 226 and Debugging an SQL routine on page 227.
|
WebSphere MQ with DB2
|
|
|
|
DB2 provides an application programming interface to the WebSphere MQ message handling system
through a set of external user-defined functions, which are called DB2 MQ functions. You can use these
functions in SQL statements to combine DB2 database access with WebSphere MQ message handling. For
more information, see WebSphere MQ with DB2 on page 448.
| Other functional changes to the SQL programming information

| v An option to replace an existing object has been added to many DDL CREATE statements. See
|
Replacing existing objects on page 54.
|
What's new as of April 2015
| The OR REPLACE option has been added to the CREATE TABLE statement. For more information, see
| Using CREATE OR REPLACE TABLE on page 47.
|
What's new as of October 2014
Pipelined table functions
| A pipelined SQL table function is a more flexible version of a table function. For more information, see
| Example: SQL table UDFs on page 193.
SQL variable debug for SQL routines
|
|
Debugging of SQL routines allows you to display values of SQL variables. For more information, see
Debugging an SQL routine on page 227.
What's new as of February 2013
Multiple event triggers
|
|
A trigger can be defined for more than one event. For more information, see Multiple event SQL
triggers on page 221.
System name for tables, views, and indexes
|
|
|
When creating a table, view, or index, the system name for the object can be specified on the create
statement. For more information, see Creating a table on page 17 and Creating and using views on
page 48.
What's new as of October 2012
Defaults for procedure parameters and using parameter names in CALL
|
|
|
|
You can define parameters for SQL and external procedures to have default values. Parameters with
default values can be omitted when calling the procedure. The CALL statement can specify parameter
names for any arguments. For more information, see Defining a procedure with default parameters on
page 156.
CREATE TABLE referencing a remote table
|
|
You can create a local table with the definition and data pulled from a non-local table. For more
information, see Creating a table with remote server data on page 23.
SQL and external routine management
|
|
Procedures and functions are tied to system objects that can be administered with CL commands. For
more information, see Managing SQL and external routine objects on page 230.
RUNSQLSTM OPTION parameter
|
|
The RUNSQLSTM command does not need to generate a listing. For more information, see Using the
SQL statement processor on page 421.
Obfuscation
|
|
The content of an SQL procedure or SQL function can be obfuscated. For more information, see
Obfuscating an SQL routine on page 228.
XMLTABLE
|
|
|
|
The XMLTABLE table function provides a way to work with XML content as a relational table. For more
information, see Using XMLTABLE to reference XML content as a relational table on page 284. In
addition, SQL XML Programming contains all the new and existing XML information that is related to
SQL.
SQL programming
Insert from a remote table
| You can insert into a local table with data pulled from a non-local table. For more information, see
| Inserting data from a remote database on page 110.
|
RUNSQL
| This new CL command runs a single SQL statement. For more information, see Using the RUNSQL CL
| command on page 425.
|
Connect by
| Hierarchical queries can be defined using the CONNECT BY syntax. For more information, see Using
| recursive queries on page 83.
|
How to see what's new or changed
| To help you see where technical changes have been made, the information center uses:
| v The
| v The
image to mark where new or changed information begins.

image to mark where new or changed information ends.
| In PDF files, you might see revision bars (|) in the left margin of new and changed information.
| To find other information about what's new or changed this release, see the Memo to users.
PDF file for SQL programming

You can view and print a PDF file of this information.
To view or download the PDF version of this document, select SQL programming (about 1,714 KB).
Saving PDF files

To save a PDF on your workstation for viewing or printing:
1. Right-click the PDF link in your browser.
2. Click the option that saves the PDF locally.
3. Navigate to the directory in which you want to save the PDF.
4. Click Save.
Downloading Adobe Reader

You need Adobe Reader installed on your system to view or print these PDFs. You can download a free
copy from the Adobe Web site (http://get.adobe.com/reader/)
Introduction to DB2 for i Structured Query Language

Structured Query Language (SQL) is a standardized language for defining and manipulating data in a
relational database. These topics describe the System i implementation of the SQL using the DB2 for i
database and the IBM DB2 Query Manager and SQL Development Kit for i licensed program.
SQL manages information based on the relational model of data. SQL statements can be embedded in
high-level languages, dynamically prepared and run, or run interactively. For information about
embedded SQL, see Embedded SQL programming.
SQL consists of statements and clauses that describe what you want to do with the data in a database
and under what conditions you want to do it.
SQL can access data in a remote relational database, using the IBM Distributed Relational Database
Architecture (DRDA).
Related concepts:
Distributed database programming
Related reference:
Distributed relational database function and SQL on page 427
A distributed relational database consists of a set of SQL objects that are spread across interconnected
computer systems.
SQL concepts
DB2 for i SQL consists of several main parts, such as SQL runtime support, precompilers, and interactive
SQL.
v SQL runtime support
SQL run time parses SQL statements and runs any SQL statements. This support is part of the IBM i
licensed program, which allows applications that contain SQL statements to be run on systems where
the IBM DB2 Query Manager and SQL Development Kit for i licensed program is not installed.
v SQL precompilers
SQL precompilers support precompiling embedded SQL statements in host languages. The following
languages are supported:
ILE C
ILE C++
ILE COBOL
COBOL
PL/I
RPG III (part of RPG)
ILE RPG
The SQL host language precompilers prepare an application program that contains SQL statements.
The host language compilers then compile the precompiled host source programs. For more
information about precompiling, see Preparing and running a program with SQL statements in the
Embedded SQL programming information. The precompiler support is part of the IBM DB2 Query
Manager and SQL Development Kit for i licensed program.
SQL interactive interface
The SQL interactive interface allows you to create and run SQL statements. For more information about
interactive SQL, see Using interactive SQL on page 410. Interactive SQL is part of the IBM DB2
Query Manager and SQL Development Kit for i licensed program.
Run SQL Scripts
The Run SQL Scripts window in System i Navigator allows you to create, edit, run, and troubleshoot
scripts of SQL statements.
Run SQL Statements (RUNSQLSTM) CL command
The RUNSQLSTM command can be used to run a series of SQL statements that are stored in a source
file or a source stream file. For more information about the RUNSQLSTM command, see Using the
SQL statement processor on page 421.
DB2 Query Manager
SQL programming
DB2 Query Manager provides a prompt-driven interactive interface that allows you to create data, add
data, maintain data, and run reports on the databases. Query Manager is part of the IBM DB2 Query
Manager and SQL Development Kit for i licensed program. For more information, see Query Manager
Use
.
v SQL REXX interface
The SQL REXX interface allows you to run SQL statements in a REXX procedure. For more information
about using SQL statements in REXX procedures, see Coding SQL statements in REXX applications in
the Embedded SQL programming information.
v SQL call level interface
The DB2 for i database supports the SQL call level interface. This allows users of any of the ILE
languages to access SQL functions directly through bound calls to a service program that is provided
by the system. Using the SQL call level interface, you can perform all the SQL functions without the
need to precompile. This is a standard set of procedure calls to prepare SQL statements, run SQL
statements, fetch rows of data, and even perform advanced functions, such as accessing the catalogs
and binding program variables to output columns.
For a complete description of all the available functions and their syntax, see SQL call level interface in
the Database section of the IBM i Information Center.
v Process Extended Dynamic SQL (QSQPRCED) API
This application programming interface (API) provides an extended dynamic SQL capability. You can
prepare SQL statements into an SQL package and run them by using this API. Statements that are
prepared into a package by this API persist until the package or statement is explicitly dropped. For
more information about the QSQPRCED API, see Process Extended Dynamic SQL (QSQPRCED) API.
For general information about APIs, see Application programming interfaces.
v Syntax Check SQL Statement (QSQCHKS) API
This API syntax checks SQL statements. For more information about the QSQCHKS API, see Syntax
Check SQL Statement (QSQCHKS) API. For general information about APIs, see Application
programming interfaces.
v DB2 Multisystem
This feature of the operating system allows your data to be distributed across multiple systems. For
more information, see DB2 Multisystem.
v DB2 Symmetric Multiprocessing
This feature of the operating system provides the query optimizer with additional methods for
retrieving data that include parallel processing. Symmetric multiprocessing (SMP) is a form of
parallelism achieved on a single system where multiple processors (CPU and I/O processors) that
share memory and disk resource work simultaneously toward achieving a single end result. This
parallel processing means that the database manager can have more than one (or all) of the system
processors working on a single query simultaneously. For more information, see Controlling parallel
processing for queries in the Database performance and query optimization topic collection.
SQL relational database and system terminology

In the relational model of data, all data is perceived as existing in tables. DB2 for i objects are created and
maintained as system objects.
The following table shows the relationship between system terms and SQL relational database terms.
Table 1. Relationship of system terms to SQL terms
System terms
SQL terms
Library. Groups related objects and allows you to find

the objects by name.
Schema. Consists of a library, a journal, a journal

receiver, an SQL catalog, and optionally a data
dictionary. A schema groups related objects and allows
you to find the objects by name.
Table. A set of columns and rows.
Physical file. A set of records.
Table 1. Relationship of system terms to SQL terms (continued)

System terms
SQL terms
Record. A set of fields.
Row. The horizontal part of a table containing a serial

set of columns.
Column. The vertical part of a table of one data type.
Field. One or more characters of related information of

one data type.
Logical file. A subset of fields and records of one or
more physical files.
SQL package. An object type that is used to run SQL
statements.
User Profile
View. A subset of columns and rows of one or more

tables.
Package. An object type that is used to run SQL
statements.
Authorization name or Authorization ID.
Related concepts:
SQL and system naming conventions

You can use either the system (*SYS) or the SQL (*SQL) naming convention in DB2 for i programming.
The naming convention used affects the method for qualifying file and table names and the terms used
on the interactive SQL displays. The naming convention used is selected by a parameter on the SQL
commands or by using the SET OPTION statement.
System naming (*SYS)

In the system naming convention, tables and other SQL objects in an SQL statement are qualified by
schema name in the form:
schema/table
SQL naming (*SQL)

In the SQL naming convention, tables and other SQL objects in an SQL statement are qualified by schema
name in the form:
schema.table
Related reference:
Qualification of unqualified object names
Types of SQL statements

There are several basic types of SQL statements. They are listed here according to their functions.
v SQL schema statements, also known as data definition language (DDL) statements
v SQL data and data change statements, also known as data manipulation language (DML) statements
v Dynamic SQL statements
v Embedded SQL host language statements
SQL programming
SQL schema statements
| ALTER FUNCTION
| ALTER PROCEDURE
|
|
ALTER SEQUENCE
ALTER TABLE
COMMENT ON
CREATE ALIAS
CREATE FUNCTION
CREATE INDEX
CREATE PROCEDURE
CREATE SCHEMA
CREATE SEQUENCE
CREATE TABLE
CREATE TRIGGER
CREATE TYPE
CREATE VARIABLE
CREATE VIEW
DROP
GRANT
LABEL ON
RENAME
REVOKE
SQL data statements

ALLOCATE CURSOR
ASSOCIATE LOCATORS
CLOSE
DECLARE CURSOR
DELETE
FETCH
FREE LOCATOR
HOLD LOCATOR
INSERT
LOCK TABLE
OPEN
REFRESH TABLE
SELECT INTO
SET variable
UPDATE
VALUES INTO
SQL data change statements

DELETE
INSERT
MERGE
UPDATE
SQL connection statements

CONNECT
DISCONNECT
RELEASE
SET CONNECTION
SQL transaction statements

COMMIT
RELEASE SAVEPOINT
ROLLBACK
SAVEPOINT
SET TRANSACTION
SQL session statements

DECLARE GLOBAL TEMPORARY TABLE
SET CURRENT DECFLOAT ROUNDING MODE
SET CURRENT DEGREE
SET CURRENT IMPLICIT XMLPARSE OPTION
SET ENCRYPTION PASSWORD
SET PATH
SET SCHEMA
SET SESSION AUTHORIZATION
Dynamic SQL statements

ALLOCATE DESCRIPTOR
DEALLOCATE DESCRIPTOR
DESCRIBE
DESCRIBE CURSOR
DESCRIBE INPUT
DESCRIBE PROCEDURE
DESCRIBE TABLE
EXECUTE
EXECUTE IMMEDIATE
GET DESCRIPTOR
PREPARE
SET DESCRIPTOR
Embedded SQL host language statements

BEGIN DECLARE SECTION
DECLARE PROCEDURE
DECLARE STATEMENT
DECLARE VARIABLE
END DECLARE SECTION
GET DIAGNOSTICS
INCLUDE
SET OPTION
SET RESULT SETS
SIGNAL
WHENEVER
SQL control statements

CALL
SQL statements can operate on objects that are created by SQL as well as externally described physical
files and single-format logical files. They do not refer to the interactive data definition utility (IDDU)
dictionary definition for program-described files. Program-described files appear as a table with only a
single column.
Related concepts:
Data definition language on page 16
Data definition language (DDL) describes the portion of SQL that creates, alters, and deletes database
objects. These database objects include schemas, tables, views, sequences, catalogs, indexes, and aliases.
Data manipulation language on page 56
Data manipulation language (DML) describes the portion of SQL that manipulates or controls data.
Related reference:
DB2 for i5/OS SQL reference
SQL communication area

The SQL communication area (SQLCA) is a set of variables that provides an application program with
information about its execution of SQL statements. The SQLCA is updated at the end of the execution of
every SQL statement.
Related concepts:
SQLCA (SQL communication area)
Handling SQL error return codes using the SQLCA
SQL diagnostics area

The SQL diagnostics area maintained by the database manager provides information about the SQL
statement that is most recently run. Your application program can access the SQL diagnostics area using
the GET DIAGNOSTICS statement.
Related concepts:
Using the SQL diagnostics area
Related reference:
GET DIAGNOSTICS statement
SQL objects
|
|
|
SQL objects are schemas, journals, catalogs, tables, aliases, views, indexes, constraints, triggers, sequences,
stored procedures, user-defined functions, user-defined types, global variables, and SQL packages. SQL
creates and maintains these objects as system objects.
Schemas
A schema provides a logical grouping of SQL objects. A schema consists of a library, a journal, a journal
receiver, a catalog, and, optionally, a data dictionary.
Tables, views, and system objects (such as programs) can be created, moved, or restored into any system
library. All system files can be created or moved into an SQL schema if the SQL schema does not contain
a data dictionary. If the SQL schema contains a data dictionary then:
v Source physical files or nonsource physical files with one member can be created, moved, or restored
into an SQL schema.
v Logical files cannot be placed in an SQL schema because they cannot be described in the data
dictionary.
You can create and own many schemas.
Journals and journal receivers

A journal and a journal receiver are used to record changes to tables and views in the database.
SQL programming
Journals and journal receivers are used in processing the SQL COMMIT, ROLLBACK, SAVEPOINT, and
RELEASE SAVEPOINT statements. Journals and journal receivers can also be used as audit trails or for
forward or backward recovery.
Related concepts:
Journal management
Commitment control
Catalogs
| An SQL catalog is a collection of tables and views that describe tables, views, indexes, procedures,
| functions, sequences, triggers, variables, constraints, programs, packages, and XSR objects.
This information is contained in a set of cross-reference tables in libraries QSYS and QSYS2. In each SQL
schema there is a set of views built over the catalog tables that contains information about the objects in
the schema.
A catalog is automatically created when you create a schema. You cannot drop or explicitly change the
catalog.
Related reference:
Catalog
Tables, rows, and columns

A table is a two-dimensional arrangement of data that consists of rows and columns.
The row is the horizontal part containing one or more columns. The column is the vertical part
containing one or more rows of data of one data type. All data for a column must be of the same type. A
table in SQL is a keyed or non-keyed physical file.
A materialized query table is a table that is used to contain materialized data that is derived from one or
more source tables specified by a select-statement.
A partitioned table is a table whose data is contained in one or more local partitions (members).
Related concepts:
DB2 Multisystem
Related reference:
Data types
Creating and altering a materialized query table on page 22
A materialized query table is a table whose definition is based on the result of a query, and whose data is in
the form of precomputed results that are taken from the table or tables on which the materialized query
table definition is based.
Aliases
An alias is an alternate name for a table or view.
You can use an alias to refer to a table or view in those cases where an existing table or view can be
referred to. Additionally, aliases can be used to join table members.
Related reference:
Aliases
Views
A view appears like a table to an application program. However, a view contains no data and only
logically represents one or more tables over which it is created.
10
A view can contain all the columns and rows of the given tables or a subset of them. The columns can be
arranged differently in a view than they are in the tables from which they are taken. A view in SQL is a
special form of a nonkeyed logical file.
Related reference:
Views
Indexes
An SQL index is a subset of the data in the columns of a table that are logically arranged in either
ascending or descending order.
Each index contains a separate arrangement. These arrangements are used for ordering (ORDER BY
clause), grouping (GROUP BY clause), and joining. An SQL index is a keyed logical file.
The index is used by the system for faster data retrieval. Creating an index is optional. You can create
any number of indexes. You can create or drop an index at any time. The index is automatically
maintained by the system. However, because the indexes are maintained by the system, a large number
of indexes can adversely affect the performance of the applications that change the table.
Related concepts:
Creating an index strategy
Constraints
A constraint is a rule enforced by the database manager to limit the values that can be inserted, deleted,
or updated in a table.
DB2 for i supports the following constraints:
v Unique constraints
A unique constraint is the rule that the values of the key are valid only if they are unique. You can
create a unique constraint using the CREATE TABLE or ALTER TABLE statement. Although the
CREATE INDEX statement can create a unique index that also guarantees uniqueness, such an index is
not a constraint.
Unique constraints are enforced during the execution of INSERT and UPDATE statements. A PRIMARY
KEY constraint is a form of the UNIQUE constraint. The difference is that a PRIMARY KEY cannot
contain any nullable columns.
v Referential constraints
A referential constraint is the rule that the values of the foreign key are valid only if one of the following
conditions is met:
They appear as values of a parent key.
Some component of the foreign key is null.
Referential constraints are enforced during the execution of INSERT, UPDATE, and DELETE
statements.
v Check constraints
A check constraint is the rule that limits the values allowed in a column or group of columns. You can
create a check constraint using the CREATE TABLE or ALTER TABLE statement. Check constraints are
enforced during the execution of INSERT and UPDATE statements. To satisfy the constraint, each row
of data inserted or updated in the table must make the specified condition either TRUE or unknown
(because of a null value).
Related reference:
Constraints on page 145
The DB2 for i database supports unique, referential, and check constraints.
SQL programming
11
Triggers
A trigger is a set of actions that runs automatically whenever a specified event occurs to a specified table
or view.
An event can be an insert, an update, a delete, or a read operation. A trigger can run either before or
after the event. DB2 for i supports SQL insert, update, and delete triggers and external triggers.
Related tasks:
Triggering automatic events in your database
Stored procedures
A stored procedure is a program that can be called with the SQL CALL statement.
DB2 for i supports external procedures and SQL procedures. An external procedure can be any system
program, service program, or REXX procedure. It cannot be a System/36 program or procedure. An SQL
procedure is defined entirely in SQL and can contain SQL statements, including SQL control statements.
Related concepts:
Stored procedures on page 149
A procedure (often called a stored procedure) is a program that can be called to perform operations. A
procedure can include both host language statements and SQL statements. Procedures in SQL provide the
same benefits as procedures in a host language.
Sequences
A sequence is a data area object that provides a quick and easy way of generating unique numbers.
You can use a sequence to replace an identity column or a user-generated numeric column. A sequence
has uses similar to these alternatives.
Related reference:
Creating and using sequences on page 26
Sequences are similar to identity columns in that they both generate unique values. However, sequences
are objects that are independent of any tables. You can use sequences to generate values quickly and
easily.
| Global variables
| A global variable is a named variable that can be created, accessed, and modified using SQL.
| A global variable can provide a unique value for a session. The variable can be used as part of any
| expression in places such as a query, a create view, or an insert statement.
User-defined functions
A user-defined function is a program that can be called like any built-in functions.
DB2 for i supports external functions, SQL functions, and sourced functions. An external function can be
any system ILE program or service program. An SQL function is defined entirely in SQL and can contain
SQL statements, including SQL control statements. A sourced function is built over any built-in or any
existing user-defined function. You can create a scalar function or a table function as either an SQL
function or an external function.
Related concepts:
Using user-defined functions on page 190
In writing SQL applications, you can implement some actions or operations as a user-defined function
(UDF) or as a subroutine in your application. Although it might appear easier to implement new
operations as subroutines, you might want to consider the advantages of using a UDF instead.
12
User-defined types
A user-defined type is a data type that you can define independently of the data types that are provided by
the database management system.
|
|
Distinct data types map to built-in types. Array data types are defined using a built-in type as the
element type and a maximum cardinality value.
Related concepts:
User-defined distinct types on page 244
A user-defined distinct type (UDT) is a mechanism to extend DB2 capabilities beyond the built-in data
types that are available.
|
|
|
XSR objects
|
|
You can use an XSR object during validation of an XML document or during annotated XML schema
decomposition.
An XSR object is one or more XML schema documents that have been registered in the XML schema
repository with the same name.
SQL packages
An SQL package is an object that contains the control structure produced when the SQL statements in an
application program are bound to a remote relational database management system (DBMS).
The DBMS uses the control structure to process SQL statements encountered while running the
application program.
SQL packages are created when a relational database name (RDB parameter) is specified on a Create SQL
(CRTSQLxxx) command and a program object is created. Packages can also be created with the Create
SQL Package (CRTSQLPKG) command.
Note: The xxx in this command refers to the host language indicators: CI for ILE C, CPPI for ILE C++,
CBL for COBOL, CBLI for ILE COBOL, PLI for PL/I, RPG for RPG/400, and RPGI for ILE RPG.
SQL packages can also be created with the Process Extended Dynamic SQL (QSQPRCED) API. The SQL
packages mentioned within this topic collection refer exclusively to distributed program SQL packages.
The QSQPRCED API uses SQL packages to provide extended dynamic SQL support.
Related reference:
Distributed relational database function and SQL on page 427
computer systems.
Process Extended Dynamic SQL (QSQPRCED) API
Application program objects

Several objects are created when a DB2 for i application program is being precompiled.
DB2 for i supports both non-ILE and ILE precompilers. Application programs can be either distributed or
nondistributed.
With the DB2 for i database, you might need to manage the following objects:
v The original source
v Optionally, the module object for ILE programs
v The program or service program
v The SQL package for distributed programs
SQL programming
13
With a nondistributed non-ILE DB2 for i program, you must manage only the original source and the
resulting program. The following figure shows the objects involved and the steps that happen during the
precompile and compile processes for a nondistributed non-ILE DB2 for i program. The user source file
precompiles the source to a temporary source file member. This member is then compiled into a program.
With a nondistributed ILE DB2 for i program, you might need to manage the original source, the
modules, and the resulting program or service program. The following figure shows the objects involved
and the steps that happen during the precompile and compile processes for a nondistributed ILE DB2 for
i program when OBJTYPE(*PGM) is specified on the precompile command. The user source file
precompiles the source to a temporary source file member. This member is then compiled into a module
that binds to a program.
With a distributed non-ILE DB2 for i program, you must manage the original source, the resulting
program, and the resulting package. The following figure shows the objects and the steps that occur
during the precompile and compile processes for a distributed non-ILE DB2 for i program. The user
source file precompiles the source to a temporary source file member. This member is then compiled into
a program. After the program is created, an SQL package is created to hold the program.
With a distributed ILE DB2 for i program, you must manage the original source, module objects, the
resulting program or service program, and the resulting packages. An SQL package can be created for
each distributed module in a distributed ILE program or service program. The following figure shows the
objects and the steps that occur during the precompile and compile processes for a distributed ILE DB2
for i program. The user source file precompiles the source to a temporary source file member. This
member is then compiled into a module that binds to a program. After the program is created, an SQL
package is created to hold the program.
14
Note: The access plans associated with the DB2 for i distributed program object are not created until the
program is run locally.
Related tasks:
Preparing and running a program with SQL statements
User source file

A source file member or a source stream file contains the application language and SQL statements. You
can create and maintain the source file member by using the source entry utility (SEU), a part of the IBM
Rational Development Studio for i licensed program.
Output source file member

By default, the precompile process creates a temporary source file QSQLTxxxxx in the QTEMP library.
However, you can specify the output source file as a permanent file on the precompile command.
If the precompile process uses the QTEMP library, the system automatically deletes the file when the job
is completed. A member with the same name as the program name is added to the output source file.
This member contains the following items:
v Calls to the SQL runtime support, which have replaced embedded SQL statements
v Parsed and syntax-checked SQL statements
By default, the precompiler calls the host language compiler.
Related tasks:
Program
A program is an object that is created as a result of the compilation process for non-ILE compilations or as
a result of the bind process for ILE compilations.
An access plan is a set of internal structures and information that tells SQL how to run an embedded SQL
statement most effectively. It is created only when the program has been successfully created. Access
plans are not created during program creation for SQL statements if the statements refer to an object,
such as a table or view, that cannot be found or to which you are not authorized.
The access plans for such statements are created when the program is run. If, at that time, the table or
view still cannot be found or you are still not authorized, a negative SQLCODE is returned. Access plans
are stored and maintained in the program object for non-distributed SQL programs and in the SQL
package for distributed SQL programs.
SQL package
An SQL package contains the access plans for a distributed SQL program.
An SQL package is an object that is created when:
v You successfully create a distributed SQL program by specifying the relational database (RDB)
parameter on the CREATE SQL (CRTSQLxxx) commands.
v You run the Create SQL Package (CRTSQLPKG) command.
SQL programming
15
When a distributed SQL program is created, the name of the SQL package and an internal consistency
token are saved in the program. They are used at run time to find the SQL package and to verify that the
SQL package is correct for this program. Because the name of the SQL package is critical for running
distributed SQL programs, an SQL package cannot be:
v Moved
v Renamed
v Duplicated
v Restored to a different library
Module
A module is an Integrated Language Environment (ILE) object that you create by compiling source code
using the Create Module (CRTxxxMOD) command (or any of the Create Bound Program (CRTBNDxxx)
commands, where xxx is C, CBL, CPP, or RPG).
You can run a module only if you use the Create Program (CRTPGM) command to bind it into a
program. You typically bind several modules together, but you can bind a module by itself. Modules
contain information about the SQL statements; however, the SQL access plans are not created until the
modules are bound into either a program or service program.
Related reference:
Create Program (CRTPGM) command
Service program
A service program is an Integrated Language Environment (ILE) object that provides a means of packaging
externally supported callable routines (functions or procedures) into a separate object.
Bound programs and other service programs can access these routines by resolving their imports to the
exports provided by a service program. The connections to these services are made when the calling
programs are created. This improves call performance to these routines without including the code in the
calling program.
Data definition language

Data definition language (DDL) describes the portion of SQL that creates, alters, and deletes database
objects. These database objects include schemas, tables, views, sequences, catalogs, indexes, and aliases.
Related concepts:
Types of SQL statements on page 7
Related tasks:
Getting started with SQL
Creating a schema
A schema provides a logical grouping of SQL objects. To create a schema, use the CREATE SCHEMA
statement.
A schema consists of a library, a journal, a journal receiver, a catalog, and optionally, a data dictionary.
Tables, views, and system objects (such as programs) can be created, moved, or restored into any system
libraries. All system files can be created or moved into an SQL schema if the SQL schema does not
contain a data dictionary. If the SQL schema contains a data dictionary then:
v Source physical files or nonsource physical files with one member can be created, moved, or restored
into an SQL schema.
v Logical files cannot be placed in an SQL schema because they cannot be described in the data
dictionary.
16
You can create and own many schemas.

You can create a schema using the CREATE SCHEMA statement. For example, create a schema called
DBTEMP:
CREATE SCHEMA DBTEMP
Related reference:
CREATE SCHEMA
Creating a table
A table can be visualized as a two-dimensional arrangement of data that consists of rows and columns.
To create a table, use the CREATE TABLE statement.
The row is the horizontal part containing one or more columns. The column is the vertical part
containing one or more rows of data of one data type. All data for a column must be of the same type. A
table in SQL is a keyed or non-keyed physical file.
|
|
|
You can create a table using the CREATE TABLE statement. You provide a name for the table. If the table
name is not a valid system object name, you can use the optional FOR SYSTEM NAME clause to specify
a system name.
The definition includes the names and attributes of its columns. The definition can include other
attributes of the table, such as the primary key.
Example: Given that you have administrative authority, create a table named 'INVENTORY' with the
following columns:
v Part number: Integer between 1 and 9999, and must not be null
v Description: Character of length 0 to 24
v Quantity on hand: Integer between 0 and 100000
The primary key is PARTNO.
CREATE TABLE INVENTORY
(PARTNO
SMALLINT
NOT NULL,
DESCR
VARCHAR(24 ),
QONHAND
INT,
PRIMARY KEY(PARTNO))
Related concepts:
Data types
Adding and removing constraints

Constraints can be added to a new table or to an existing table. To add a unique or primary key, a
referential constraint, or a check constraint, use the CREATE TABLE or the ALTER TABLE statement. To
remove a constraint, use the ALTER TABLE statement.
For example, add a primary key to an existing table using the ALTER TABLE statement:
ALTER TABLE CORPDATA.DEPARTMENT
ADD PRIMARY KEY (DEPTNO)
To make this key a unique key, replace the keyword PRIMARY with UNIQUE.
You can remove a constraint using the same ALTER TABLE statement:
DROP PRIMARY KEY (DEPTNO)
SQL programming
17
Referential integrity and tables

Referential integrity is the condition of a set of tables in a database in which all references from one table
to another are valid.
Consider the following example:
v CORPDATA.EMPLOYEE serves as a master list of employees.
v CORPDATA.DEPARTMENT acts as a master list of all valid department numbers.
v CORPDATA.EMP_ACT provides a master list of activities performed for projects.
Other tables refer to the same entities described in these tables. When a table contains data for which
there is a master list, that data should actually appear in the master list, or the reference is not valid. The
table that contains the master list is the parent table, and the table that refers to it is a dependent table.
When the references from the dependent table to the parent table are valid, the condition of the set of
tables is called referential integrity.
Stated another way, referential integrity is the state of a database in which all values of all foreign keys
are valid. Each value of the foreign key must also exist in the parent key or be null. This definition of
referential integrity requires an understanding of the following terms:
v A unique key is a column or set of columns in a table that uniquely identify a row. Although a table can
have several unique keys, no two rows in a table can have the same unique key value.
v A primary key is a unique key that does not allow nulls. A table cannot have more than one primary
key.
v A parent key is either a unique key or a primary key that is referenced in a referential constraint.
v A foreign key is a column or set of columns whose values must match those of a parent key. If any
column value used to build the foreign key is null, the rule does not apply.
v A parent table is a table that contains the parent key.
v A dependent table is the table that contains the foreign key.
v A descendent table is a table that is a dependent table or a descendent of a dependent table.
Enforcement of referential integrity prevents the violation of the rule that states that every non-null
foreign key must have a matching parent key.
SQL supports the referential integrity concept with the CREATE TABLE and ALTER TABLE statements.
Related reference:
collections.
CREATE TABLE
ALTER TABLE
Adding and removing referential constraints:
You can use the CREATE TABLE statement or the ALTER TABLE statement to add a referential
constraint. To remove a referential constraint, use the ALTER TABLE statement.
Constraints are rules that ensure that references from one table, a dependent table, to data in another
table, the parent table, are valid. You use referential constraints to ensure referential integrity.
With a referential constraint, non-null values of the foreign key are valid only if they also appear as
values of a parent key. When you define a referential constraint, you specify:
v A primary or unique key
v A foreign key
18
v Delete and update rules that specify the action taken with respect to dependent rows when the parent
row is deleted or updated.
Optionally, you can specify a name for the constraint. If a name is not specified, one is automatically
generated.
After a referential constraint is defined, the system enforces the constraint on every INSERT, DELETE,
and UPDATE operation performed through SQL or any other interface, including System i Navigator, CL
commands, utilities, or high-level language statements.
Related reference:
CREATE TABLE
ALTER TABLE
Example: Adding referential constraints:
You define a referential constraint that every department number in the sample employee table must
appear in the department table. The referential constraint ensures that every employee belongs to an
existing department.
The following SQL statements create the CORPDATA.DEPARTMENT and CORPDATA.EMPLOYEE tables
with those constraint relationships defined.
CREATE TABLE CORPDATA.DEPARTMENT
(DEPTNO
CHAR(3)
NOT NULL PRIMARY KEY,
DEPTNAME VARCHAR(29) NOT NULL,
MGRNO
CHAR(6),
ADMRDEPT CHAR(3)
NOT NULL
CONSTRAINT REPORTS_TO_EXISTS
REFERENCES CORPDATA.DEPARTMENT (DEPTNO)
ON DELETE CASCADE)
CREATE TABLE CORPDATA.EMPLOYEE
(EMPNO
CHAR(6)
NOT NULL PRIMARY KEY,
FIRSTNME VARCHAR(12) NOT NULL,
MIDINIT CHAR(1)
NOT NULL,
LASTNAME VARCHAR(15) NOT NULL,
WORKDEPT CHAR(3)
CONSTRAINT WORKDEPT_EXISTS
REFERENCES CORPDATA.DEPARTMENT (DEPTNO)
ON DELETE SET NULL ON UPDATE RESTRICT,
PHONENO CHAR(4),
HIREDATE DATE,
JOB
CHAR(8),
EDLEVEL SMALLINT
NOT NULL,
SEX
CHAR(1),
BIRTHDATE DATE,
SALARY
DECIMAL(9,2),
BONUS
DECIMAL(9,2),
COMM
DECIMAL(9,2),
CONSTRAINT UNIQUE_LNAME_IN_DEPT UNIQUE (WORKDEPT, LASTNAME))
In this case, the DEPARTMENT table has a column of unique department numbers (DEPTNO) which
functions as a primary key, and is a parent table in two constraint relationships:
REPORTS_TO_EXISTS
is a self-referencing constraint in which the DEPARTMENT table is both the parent and the
dependent in the same relationship. Every non-null value of ADMRDEPT must match a value of
DEPTNO. A department must report to an existing department in the database. The DELETE
CASCADE rule indicates that if a row with a DEPTNO value n is deleted, every row in the table
for which the ADMRDEPT is n is also deleted.
SQL programming
19
WORKDEPT_EXISTS
establishes the EMPLOYEE table as a dependent table, and the column of employee department
assignments (WORKDEPT) as a foreign key. Thus, every value of WORKDEPT must match a
value of DEPTNO. The DELETE SET NULL rule says that if a row is deleted from
DEPARTMENT in which the value of DEPTNO is n, then the value of WORKDEPT in
EMPLOYEE is set to null in every row in which the value was n. The UPDATE RESTRICT rule
says that a value of DEPTNO in DEPARTMENT cannot be updated if there are values of
WORKDEPT in EMPLOYEE that match the current DEPTNO value.
Constraint UNIQUE_LNAME_IN_DEPT in the EMPLOYEE table causes LASTNAME to be unique within
a department. While this constraint is unlikely, it illustrates how a constraint made up of several columns
can be defined at the table level.
Example: Removing constraints

When you remove the primary key over the DEPTNO column in the DEPARTMENT table, other tables
are affected.
You also remove the REPORTS_TO_EXISTS constraint that is defined on the DEPARTMENT table and the
WORKDEPT_EXISTS constraint that is defined on the EMPLOYEE table, because the primary key that
you remove is the parent key in those constraint relationships.
ALTER TABLE CORPDATA.EMPLOYEE DROP PRIMARY KEY
You can also remove a constraint by name, as in the following example:

DROP CONSTRAINT UNIQUE_LNAME_IN_DEPT
Check pending
Referential constraints and check constraints can be in a check pending state, where potential violations
of the constraints exist.
For referential constraints, a violation occurs when potential mismatches exist between parent and foreign
keys. For check constraints, a violation occurs when potential values exist in columns that are limited by
the check constraint. When the system determines that a constraint might have been violated (such as
after a restore operation), the constraint is marked as check pending. When this happens, restrictions are
placed on the use of tables involved in the constraint. For referential constraints, the following restrictions
apply:
v No input or output operations are allowed on the dependent file.
v Only read and insert operations are allowed on the parent file.
When a check constraint is in check pending, the following restrictions apply:
v Read operations are not allowed on the file.
v Insert and update operations are allowed and the constraint is enforced.
To get a constraint out of check pending, follow these steps:
1. Disable the relationship with the Change Physical File Constraint (CHGPFCST) CL command.
2. Correct the key (foreign, parent, or both) data for referential constraints or column data for check
constraints.
3. Enable the constraint again with the CHGPFCST CL command.
You can identify the rows that are in violation of the constraint with the Display Check Pending
Constraint (DSPCPCST) CL command.
Related concepts:
Check pending status in referential constraints
20
Related tasks:
Working with constraints that are in check pending status
Creating a table using LIKE

You can create a table that looks like another table. That is, you can create a table that includes all of the
column definitions from an existing table.
The following definitions are copied:
v Column names (and system column names)
v Data type, length, precision, and scale
v CCSID
| v FIELDPROC
If the LIKE clause immediately follows the table name and is not enclosed in parentheses, the following
attributes are also included:
v Column text (LABEL ON)
v Column heading (LABEL ON)
v Default value
v Hidden attribute
v Identity attribute
v Nullability
If the specified table or view contains an identity column, you must specify the option INCLUDING
IDENTITY on the CREATE TABLE statement if you want the identity column to exist in the new table.
The default behavior for CREATE TABLE is EXCLUDING IDENTITY. There are similar options to include
the default value, the hidden attribute, and the row change timestamp attribute. If the specified table or
view is a non-SQL-created physical file or logical file, any non-SQL attributes are removed.
Create a table EMPLOYEE2 that includes all of the columns in EMPLOYEE:
CREATE TABLE EMPLOYEE2 LIKE EMPLOYEE
Related reference:
CREATE TABLE
Creating a table using AS

You can create a table from the result of a SELECT statement. To create this type of table, use the
CREATE TABLE AS statement.
All of the expressions that can be used in a SELECT statement can be used in a CREATE TABLE AS
statement. You can also include all of the data from the table or tables that you are selecting from.
For example, create a table named EMPLOYEE3 that includes all of the column definitions from
EMPLOYEE where the DEPTNO = D11.
CREATE TABLE EMPLOYEE3 AS
(SELECT PROJNO, PROJNAME, DEPTNO
FROM EMPLOYEE
WHERE DEPTNO = D11) WITH NO DATA
If the specified table or view contains an identity column, you must specify the option INCLUDING
IDENTITY on the CREATE TABLE statement if you want the identity column to exist in the new table.
The default behavior for CREATE TABLE is EXCLUDING IDENTITY. There are similar options to include
the default value, the hidden attribute, and the row change timestamp attribute. The WITH NO DATA
clause indicates that the column definitions are to be copied without the data. If you want to include the
SQL programming
21
data in the new table EMPLOYEE3, include the WITH DATA clause. If the specified query includes a
non-SQL-created physical file or logical file, any non-SQL result attributes are removed.
Related concepts:
Retrieving data using the SELECT statement on page 56
The SELECT statement tailors your query to gather data. You can use the SELECT statement to retrieve a
specific row or retrieve data in a specific way.
Related reference:
CREATE TABLE
Creating and altering a materialized query table

A materialized query table is a table whose definition is based on the result of a query, and whose data is in
the form of precomputed results that are taken from the table or tables on which the materialized query
table definition is based.
If the optimizer determines that a query runs faster against a materialized query table than it does
against the base table or tables, the query will run against the materialized query table. You can directly
query a materialized query table. For more information about how the optimizer uses materialized query
tables, see the Database performance and query optimization topic.
Assume a very large transaction table named TRANS contains one row for each transaction processed by
a company. The table is defined with many columns. Create a materialized query table for the TRANS
table that contains daily summary data for the date and amount of a transaction by issuing the following:
CREATE TABLE STRANS
AS (SELECT YEAR AS SYEAR, MONTH AS SMONTH, DAY AS SDAY, SUM(AMOUNT) AS SSUM
FROM TRANS
GROUP BY YEAR, MONTH, DAY )
DATA INITIALLY DEFERRED
REFRESH DEFERRED
MAINTAINED BY USER
This materialized query table specifies that the table is not populated at the time that it is created by
using the DATA INITIALLY DEFERRED clause. REFRESH DEFERRED indicates that changes made to
TRANS are not reflected in STRANS. Additionally, this table is maintained by the user, enabling the user
to use ALTER, INSERT, DELETE, and UPDATE statements.
To populate the materialized query table or refresh the table after it has been populated, use the
REFRESH TABLE statement. This causes the query associated with the materialized query table to be run
and causes the table to be filled with the results of the query. To populate the STRANS table, run the
following statement:
REFRESH TABLE STRANS
You can create a materialized query table from an existing base table as long as the result of the
select-statement provides a set of columns that match the columns in the existing table (same number of
columns and compatible column definitions). For example, create a table TRANSCOUNT. Then, change
the base table TRANSCOUNT into a materialized query table:
To create the table:
CREATE TABLE TRANSCOUNT
(ACCTID SMALLINT NOT NULL,
LOCID SMALLINT,
YEAR DATE
CNT INTEGER)
You can alter this table to be a materialized query table:
22
ALTER TABLE TRANSCOUNT

ADD MATERIALIZED QUERY
(SELECT ACCTID, LOCID, YEAR, COUNT(*) AS CNT
FROM TRANS
GROUP BY ACCTID, LOCID, YEAR )
DATA INITIALLY DEFERRED
REFRESH DEFERRED
MAINTAINED BY USER
Finally, you can change a materialized query table back to a base table. For example:
ALTER TABLE TRANSCOUNT
DROP MATERIALIZED QUERY
In this example, the table TRANSCOUNT is not dropped, but it is no longer a materialized query table.
Related concepts:
Tables, rows, and columns on page 10
A table is a two-dimensional arrangement of data that consists of rows and columns.
Declaring a global temporary table

You can create a temporary table for use with your current session. To create a temporary table, use the
DECLARE GLOBAL TEMPORARY TABLE statement.
This temporary table does not appear in the system catalog and cannot be shared by other sessions.
When you end your session, the rows of the table are deleted and the table is dropped.
The syntax of this statement is similar to that of the CREATE TABLE statement and can include the LIKE
or AS clause.
For example, create a temporary table ORDERS:
DECLARE GLOBAL TEMPORARY TABLE ORDERS
(PARTNO
SMALLINT NOT NULL,
DESCR
VARCHAR(24),
QONHAND INT)
ON COMMIT DELETE ROWS
This table is created in QTEMP. To reference the table using a schema name, use either SESSION or
QTEMP. You can issue SELECT, INSERT, UPDATE, and DELETE statements against this table, the same
as any other table. You can drop this table by issuing the DROP TABLE statement:
DROP TABLE ORDERS
Related reference:
|
Creating a table with remote server data
You can create a table on the local server that references one or more tables on a remote server.
|
|
|
Along with the select-statement, you can specify copy options to get attributes such as the default values
or identity column information copied for the new table. The WITH DATA or WITH NO DATA clause
must be specified to indicate whether to populate the table from the remote system.
|
|
|
|
|
|
For example, create a table named EMPLOYEE4 that includes column definitions from the EMPLOYEE
table on remote server REMOTESYS. Include the data from the remote system as well.
CREATE TABLE EMPLOYEE4 AS
FROM REMOTESYS.TESTSCHEMA.EMPLOYEE
WHERE DEPTNO = D11) WITH DATA
SQL programming
23
|
|
|
|
|
|
|
You can also create this table as a global temporary table, which will create it in QTEMP. In this example,
different column names are provided for the new table. The table definition will pick up the default
values for its columns from the remote server.
|
|
|
|
|
The following restrictions apply to using a remote server as the source for the new table:
v The materialized query table clauses are not allowed.
v A column with a FIELDPROC cannot be listed in the select list.
v The copy options cannot be specified if the remote server is DB2 for LUW or DB2 for z/OS.
Related reference:
DECLARE GLOBAL TEMPORARY TABLE EMPLOYEE4 (Project_number, Project_name, Department_number) AS

FROM REMOTESYS.TESTSCHEMA.EMPLOYEE
WHERE DEPTNO = D11) WITH DATA INCLUDING DEFAULTS
| Inserting data from a remote database on page 110

| You can insert into a table on the local server using a select statement to get rows from a remote server.
Creating a row change timestamp column

Every time a row is added or changed in a table with a row change timestamp column, the row change
timestamp column value is set to the timestamp corresponding to the time of the insert or update
operation.
The data type of a row change timestamp column must be TIMESTAMP. You can define only one row
change timestamp column in a table.
When you create a table, you can define a column in the table to be a row change timestamp column. For
example, create a table ORDERS with columns called ORDERNO, SHIPPED_TO, ORDER_DATE,
STATUS, and CHANGE_TS. Define CHANGE_TS as a row change timestamp column.
CREATE TABLE ORDERS
(ORDERNO SMALLINT,
SHIPPED_TO VARCHAR(36),
ORDER_DATE DATE,
STATUS CHAR(1),
CHANGE_TS TIMESTAMP FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP NOT NULL)
When a row is inserted into the ORDERS table, the CHANGE_TS column for the row is set to the
timestamp of the insert operation. Any time a row in ORDERS is updated, the CHANGE_TS column for
the row is modified to reflect the timestamp of the update operation.
You can drop the row change timestamp attribute from a column:
ALTER TABLE ORDER
ALTER COLUMN CHANGE_TS
DROP ROW CHANGE TIMESTAMP
The column CHANGE_TS remains as a TIMESTAMP column in the table, but the system no longer
automatically updates timestamp values for this column.
Creating and altering an identity column

Every time a row is added to a table with an identity column, the identity column value for the new row
is generated by the system.
Only columns of type SMALLINT, INTEGER, BIGINT, DECIMAL, or NUMERIC can be created as
identity columns. You are allowed only one identity column per table. When you are changing a table
definition, only a column that you are adding can be specified as an identity column; existing columns
cannot.
24
When you create a table, you can define a column in the table to be an identity column. For example,
create a table ORDERS with three columns called ORDERNO, SHIPPED_TO, and ORDER_DATE. Define
ORDERNO as an identity column.
CREATE TABLE ORDERS
(ORDERNO SMALLINT NOT NULL
GENERATED ALWAYS AS IDENTITY
(START WITH 500
INCREMENT BY 1
CYCLE),
SHIPPED_TO VARCHAR (36) ,
ORDER_DATE DATE)
This column is defined with a starting value of 500, incremented by 1 for every new row inserted, and
will recycle when the maximum value is reached. In this example, the maximum value for the identity
column is the maximum value for the data type. Because the data type is defined as SMALLINT, the
range of values that can be assigned to ORDERNO is from 500 to 32 767. When this column value
reaches 32 767, it will restart at 500 again. If 500 is still assigned to a column, and a unique key is
specified on the identity column, a duplicate key error is returned. The next insert operation will attempt
to use 501. If you do not have a unique key specified for the identity column, 500 is used again,
regardless of how many times it appears in the table.
For a larger range of values, specify the column to be data type INTEGER or even BIGINT. If you want
the value of the identity column to decrease, specify a negative value for the INCREMENT option. It is
also possible to specify the exact range of numbers by using MINVALUE and MAXVALUE.
You can modify the attributes of an existing identity column using the ALTER TABLE statement. For
example, you want to restart the identity column with a new value:
ALTER TABLE ORDER
ALTER COLUMN ORDERNO
RESTART WITH 1
You can also drop the identity attribute from a column:

ALTER TABLE ORDER
ALTER COLUMN ORDERNO
DROP IDENTITY
The column ORDERNO remains as a SMALLINT column, but the identity attribute is dropped. The
system will no longer generate values for this column.
Related reference:
Comparison of identity columns and sequences on page 27
While identity columns and sequences are similar in many ways, there are also differences.
Inserting values into an identity column on page 109
You can insert a value into an identity column or allow the system to insert a value for you.
Updating an identity column on page 114
You can update the value in an identity column to a specified value or have the system generate a new
value.
Using ROWID
Using ROWID is another way to have the system assign a unique value to a column. ROWID is similar
to identity columns. But rather than being an attribute of a numeric column, it is a separate data type.
To create a table similar to the identity column example:
SQL programming
25
CREATE TABLE ORDERS

(ORDERNO ROWID
GENERATED ALWAYS,
SHIPPED_TO VARCHAR (36) ,
ORDER_DATE DATE)
Creating and using sequences

Sequences are similar to identity columns in that they both generate unique values. However, sequences
are objects that are independent of any tables. You can use sequences to generate values quickly and
easily.
Sequences are not tied to a column in a table and are accessed separately. Additionally, they are not
treated as any part of a transaction's unit of work.
You create a sequence using the CREATE SEQUENCE statement. For an example similar to the identity
column example, create a sequence ORDER_SEQ:
CREATE SEQUENCE ORDER_SEQ
START WITH 500
INCREMENT BY 1
MAXVALUE 1000
CYCLE
CACHE 24
This sequence is defined with a starting value of 500, incremented by 1 for every use, and recycles when
the maximum value is reached. In this example, the maximum value for the sequence is 1000. When this
value reaches 1000, it will restart at 500 again.
After this sequence is created, you can insert values into a column using the sequence. For example,
insert the next value of the sequence ORDER_SEQ into a table ORDERS with columns ORDERNO and
CUSTNO.
First, create the table ORDERS:
CREATE TABLE ORDERS
(ORDERNO SMALLINT NOT NULL,
CUSTNO SMALLINT);
Then, insert the sequence value:

INSERT INTO ORDERS (ORDERNO, CUSTNO)
VALUES (NEXT VALUE FOR ORDER_SEQ, 12)
Running the following statement returns the values in the columns:

SELECT *
FROM ORDERS
Table 2. Results for SELECT from table ORDERS
ORDERNO
CUSTNO
500
12
In this example, the next value for sequence ORDER is inserted into the ORDERNO column. Issue the
INSERT statement again. Then run the SELECT statement.
ORDERNO
CUSTNO
500
12
501
12
26
You can also insert the previous value for the sequence ORDER by using the PREVIOUS VALUE
expression. You can use NEXT VALUE and PREVIOUS VALUE in the following expressions:
v Within the select-clause of a SELECT statement or SELECT INTO statement as long as the statement
does not contain a DISTINCT keyword, a GROUP BY clause, an ORDER BY clause, a UNION
keyword, an INTERSECT keyword, or an EXCEPT keyword
v Within a VALUES clause of an INSERT statement
v Within the select-clause of the fullselect of an INSERT statement
v Within the SET clause of a searched or positioned UPDATE statement, though NEXT VALUE cannot be
specified in the select-clause of the subselect of an expression in the SET clause
You can alter a sequence by issuing the ALTER SEQUENCE statement. Sequences can be altered in the
following ways:
v Restarting the sequence
v Changing the increment between future sequence values
v Setting or eliminating the minimum or maximum values
v Changing the number of cached sequence numbers
v Changing the attribute that determines whether the sequence can cycle or not
v Changing whether sequence numbers must be generated in order of request
For example, change the increment of values of sequence ORDER from 1 to 5:
ALTER SEQUENCE ORDER_SEQ
INCREMENT BY 5
After this change is complete, run the INSERT statement again and then the SELECT statement. Now the
table contains the following columns.
ORDERNO
CUSTNO
500
12
501
12
528
12
Notice that the next value that the sequence uses is a 528. At first glance, this number appears to be
incorrect. However, look at the events that lead up to this assignment. First, when the sequence was
originally create, a cache value of 24 was assigned. The system assigns the first 24 values for this cache.
Next, the sequence was altered. When the ALTER SEQUENCE statement is issued, the system drops the
assigned values and starts up again with the next available value; in this case the original 24 that was
cached, plus the next increment, 5. If the original CREATE SEQUENCE statement did not have the
CACHE clause, the system automatically assigns a default cache value of 20. If that sequence was altered,
then the next available value is 25.
Related concepts:
Sequences on page 12
A sequence is a data area object that provides a quick and easy way of generating unique numbers.
Comparison of identity columns and sequences

While identity columns and sequences are similar in many ways, there are also differences.
Examine these differences before you decide which to use.
SQL programming
27
|
|
An identity column has the following characteristics:

v An identity column can be defined as part of a table when the table is created or it can be added to a
column using alter table. After a table is created, the identity column characteristics can be changed.
v An identity column automatically generates values for a single table.
v When an identity column is defined as GENERATED ALWAYS, the values used are always generated
by the database manager. Applications are not allowed to provide their own values when changing the
contents of the table.
v The IDENTITY_VAL_LOCAL function can be used to see the most recently assigned value for an
identity column.
A sequence has the following characteristics:
v A sequence is a system object of type *DTAARA that is not tied to a table.
v A sequence generates sequential values that can be used in any SQL statement.
v There are two expressions used to retrieve the next values in the sequence and to look at the previous
value assigned for the sequence. The PREVIOUS VALUE expression returns the most recently
generated value for the specified sequence for a previous statement within the current session. The
NEXT VALUE expression returns the next value for the specified sequence. The use of these
expressions allows the same value to be used across several SQL statements within several tables.
While these are not all of the characteristics of identity columns and sequences, these characteristics can
help you determine which to use depending on your database design and the applications that use the
database.
Related reference:
Creating and altering an identity column on page 24
Defining field procedures
| Field procedures are assigned to a table by the FIELDPROC clause of the CREATE TABLE and ALTER
| TABLE statements. A field procedure is a user-written exit routine that transforms values in a single
| column.
|
|
|
|
|
When values in the column are changed, or new values inserted, the field procedure is invoked for each
value, and can transform that value (encode it) in any way. The encoded value is then stored. When
values are retrieved from the column, the field procedure is invoked for each value, which is encoded,
and must decode it back to the original value. Any indexes defined on a non-derived column that uses a
field procedure are built with encoded values.
|
|
|
|
|
|
|
|
The transformation your field procedure performs on a value is called field-encoding. The same routine is
used to undo the transformation when values are retrieved; that operation is called field-decoding. Values
in columns with a field procedure are described to DB2 in two ways:
1. The description of the column as defined in CREATE TABLE or ALTER TABLE appears in the catalog
table QSYS2.SYSCOLUMNS. That is the description of the field-decoded value, and is called the
column description.
2. The description of the encoded value, as it is stored in the database, appears in the catalog table
QSYS2.SYSFIELDS. That is the description of the field-encoded value, and is called the field description.
| Important: The field-decoding function must be the exact inverse of the field-encoding function. For
| example, if a routine encodes 'ALABAMA' to '01', it must decode '01' to 'ALABAMA'. A violation of this
| rule can lead to unpredictable results. See General guidelines for writing field procedures on page 37.
28
|
|
|
|
Field procedures can also perform masking of data when decoded (retrieved). In this case, the field
procedure would decode '01' to 'ALABAMA for certain users or environments and for other users or
environments may return a masked value such as XXXXXXXX instead. See Guidelines for writing field
procedures that mask data on page 38.
|
|
|
Field definition for field procedures
|
|
|
The data type of the encoded value can be any valid SQL data type except ROWID or DATALINK. Also a
field procedure cannot be associated with any column having values generated by IDENTITY or ROW
CHANGE TIMESTAMP.
|
|
|
If a DDS-created physical file is altered to add a field procedure, the encoded attribute data type cannot
be a LOB type or DataLink. If an SQL table is altered to add a field procedure, the encoded attribute
precision field must be 0 if the encoded attribute data type is any of the integer types.
|
|
A field procedure may not be added to a column that has a default value of CURRENT DATE,
CURRENT TIME, CURRENT TIMESTAMP, or USER.
|
|
|
A column defined with a user-defined data type can have a field procedure if the source type of the
user-defined data type is any of the allowed SQL data types. DB2 casts the value of the column to the
source type before it passes it to the field procedure.
|
|
|
Specifying the field procedure
|
|
|
You cannot use a field procedure on a ROWID or DATALINK column of a table or on any column having
values generated by IDENTITY or ROW CHANGE TIMESTAMP. However, you can specify it for other
columns in the same table.
|
|
|
|
|
|
|
The optional parameter list that follows the procedure name is a list of constants, enclosed in parentheses,
called the literal list. The literal list is converted by DB2 into a data structure called the field procedure
parameter value list (FPPVL). The FPPVL is passed to the field procedure during the field-definition
operation. At that time, the procedure can modify it or return it unchanged. The output form of the
FPPVL is called the modified FPPVL. It is stored in the DB2 QSYS2.SYSFIELDS catalog table as part of the
column description. The modified FPPVL is passed again to the field procedure whenever that procedure
is invoked for field-encoding or field-decoding.
|
|
|
|
|
|
|
When field procedures are invoked
|
|
|
v For field-encoding, when a column value is to be encoded. Encoding occurs for any value that:
Is inserted in the column by an SQL INSERT statement, SQL MERGE statement, or native write
operation.
Is changed by an SQL UPDATE statement, SQL MERGE statement, or native update operation.
The field procedure is also invoked when the table is created or altered, to define the data type and
attributes of an encoded value to DB2. That operation is called field-definition.
To name a field procedure for a column, use the FIELDPROC clause of the CREATE TABLE or ALTER
TABLE statement, followed by the name of the procedure and, optionally, a list of parameters.
A field procedure that is specified for a column is invoked in three general situations.
v For field-definition, when the CREATE TABLE or ALTER TABLE statement that names the procedure is
executed. During this invocation, the procedure is expected to:
Determine whether the data type and attributes of the column are valid.
Verify the literal list, and change it if desired.
Provide the field description of the column.
SQL programming
29
|
If the data needs to be copied and the target column has a field procedure, it is possible that the
|
field procedure may be invoked to encode the copied data. Examples include the SQL statements
|
ALTER TABLE or CREATE TABLE (with a LIKE or as-result-table clause) and the CL commands
|
CPYF or RGZPFM.
|
Is compared to a column with a field procedure. The QAQQINI option
|
FIELDPROC_ENCODED_COMPARISON is used by the optimizer to decide if the column value is
|
decoded or if the variable, constant, or join column is encoded.
|
At CREATE or ALTER TABLE time for the DEFAULT value, if the column has a field procedure.
|
If there are any after or read triggers, the field procedure is invoked before any of these triggers. For
|
before triggers, there may be multiple invocations of the field procedure with encode and decode
|
operations. The number of calls to the field procedure depends on many factors including the type of
|
trigger and if the trigger changes the data in the trigger buffer. The database manager will ensure that
|
the field procedure is called to encode the data that will be inserted into the table.
| v For field-decoding, when a stored value is to be field-decoded back into its original value. This occurs
|
for any value that is:
|
Retrieved by an SQL SELECT or FETCH statement, or by a native read operation.
|
If the data needs to be copied and the source column has a field procedure, it is possible that the
|
field procedure may be invoked to decode the data prior to making the copy. Examples include the
|
SQL statements ALTER TABLE or CREATE TABLE (with a LIKE or as-result-table clause) and the CL
|
commands CPYF or RGZPFM.
|
|
|
|
|
|
Is compared to a column with a field procedure. The QAQQINI option

FIELDPROC_ENCODED_COMPARISON is used by the optimizer to decide if the column value is
decoded or if the variable or constant is encoded.
A field procedure is never invoked to process a null value. It is also not invoked for a DELETE
operation without a WHERE clause when the table has no DELETE triggers. The field procedure is
invoked for empty strings.
|
|
|
|
|
|
|
|
Recommendation: Avoid encoding blanks in a field procedure. When DB2 compares the values of two
strings with different lengths, it temporarily pads the shorter string with the appropriate blank characters
(for example, EBCDIC or double-byte blanks) up to the length of the longer string. If the shorter string is
the value of a column with a field procedure, padding is done to the encoded value, but the pad
character is not encoded. Therefore, if the procedure changes blanks to some other character, encoded
blanks at the end of the longer string are not equal to padded blanks at the end of the shorter string.
That situation can lead to errors; for example, some strings that ought to be equal might not be
recognized as such. Therefore, encoding blanks in a field procedure is not recommended.
| Parameter list for execution of field procedures

| The field procedure parameter list communicates general information to a field procedure.
| The parameter list tells what operation is to be done and allows the field procedure to signal errors. DB2
| provides storage for all parameters that are passed to the field procedure. Therefore, parameters are
| passed to the field procedure by address.
|
|
|
|
|
When defining and using the parameters in the field procedure, care should be taken to ensure that no
more storage is referenced for a given parameter than is defined for that parameter. The parameters are
all stored in the same space and exceeding a given parameter's storage space can overwrite another
parameter's value. This, in turn, can cause the field procedure to see invalid input data or cause the value
returned to the database to be invalid.
| Parameter 1
|
A small (2 byte) integer that describes the function to be performed. This parameter is input only.
|
Supported values are:
v 0 field-encoding
v 4 field-decoding
|
|
30
v 8 field-definition
|
|
|
|
|
Parameter 2
A structure that defines the field procedure parameter value list (FPPVL).
v For function code 8, this parameter is input/output.
v For function code 0 and 4, this parameter contains the output of the function code 8 call. This
parameter is input only
|
|
|
|
Parameter 3
The decoded data attribute that is defined by the Column Value Descriptor (CVD). This is the
column attributes that were specified at CREATE TABLE or ALTER TABLE time. This parameter
is input only.
|
|
|
|
Parameter 4
The decoded data. The exact structure is dependent on function code.
v If function code 8, then the NULL value. This parameter is input only.
v If function code 0, then the data to be encoded. This parameter is input only.
v If function code 4, then the location to place the decoded data. This parameter is output only.
|
|
|
|
|
|
Parameter 5
The encoded data attribute that is defined by the Field Value Descriptor (FVD).
v If function code 8, then the structure containing the encoded data attributes. This parameter is
output only.
v If function code 0 or 4 , then a structure containing the encoded data attributes that was
returned by the function 8 call. This parameter is input only.
|
|
|
|
|
Parameter 6
The encoded data that is defined by the Field Value Descriptor (FVD). The exact structure is
dependent on function code.
v If function code 8, then the NULL value. This parameter is input only.
v If function code 0, then the location to place the encoded data. This parameter is output only.
|
|
|
v If function code 4, then the encoded form of the data. This parameter is input only.
Parameter 7
The SQLSTATE (character(5)). This parameter is input/output.
|
|
|
|
|
This parameter is set by DB2 to '00000' before calling the field procedure. It can be set by the field
procedure. While normally the SQLSTATE is not set by a field procedure, it can be used to signal
an error to the database as follows:
v If the field procedure detects an error, it should set the SQLSTATE to '38xxx', where xxx may
be one of several possible strings. For more information, see DB2 Messages and Codes.
Warnings are not supported for field procedures
|
|
|
|
|
|
|
|
|
|
|
|
Parameter 8
The message text area (varchar(1000)). This parameter is input/output.
This argument is set by DB2 to the empty string before calling the field procedure. It is a
VARCHAR(1000) value that can be used by the field procedure to send message text back when
an SQLSTATE error is signaled by the field procedure. Message text is ignored by DB2 unless the
SQLSTATE parameter is set by the field procedure. The message text is assumed to be in the job
CCSID.
Parameter 9
A 128-byte structure containing additional information for the field procedure. This parameter is
input only.
This structure is set by DB2 before calling the field procedure. For field procedures that mask
data, it indicates that the caller is a system function that requires that the data be decoded
SQL programming
31
without masking. For example, in some cases, RGZPFM and ALTER TABLE may need to copy
data. If the field procedure ignores this parameter and masks data when these operations are
performed, the column data will be lost. Hence, it is critical that a field procedure that masks
data properly handle this parameter.
|
|
|
|
| Include SQLFP in QSYSINC/H describes these parameters.

| The field procedure parameter value list (FPPVL):
| The field procedure parameter value list communicates the literal list, supplied in the CREATE TABLE or
| ALTER TABLE statement, to the field procedure during field-definition.
| At that time, the field procedure can reformat the FPPVL; it is the reformatted FPPVL that is stored in
| QSYS2.SYSFIELDS and communicated to the field procedure during field-encoding and field-decoding as
| the modified FPPVL.
| The following tables describe the FPPVL:
|
|
|
|
|
|
|
|
|
|
|
|
Table 5. sqlfpFieldProcedureParameterList_T
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 6. sqlfpOptionalParameterValueDescriptor_T
Name
Offset
Data Type
Description
sqlfpOptParmValueListLength
4-byte integer
Length in bytes of this structure
sqlfpNumberOfOptionalParms
4-byte integer
Number of value descriptors that follow.

Equal to the number of parameters in the
FIELDPROC clause. Zero if no
parameters were listed.
sqlfpParmList
structure
A list containing
sqlfpOptionalParameterValueDescriptor_T sqlfpNumberOfOptionalParms count of
sqlfpOptionalParameterValueDescriptor_T
items.
Name
Offset
Data Type
Description
sqlfpOptDescLength
4-byte integer
Length in bytes of this structure
sqlfpParmDesc
structure sqlfpParameterDescription_T
Parameter description
reserved2
38
character(12)
Not used
sqlfpParmData
40
The optional parameter data value.

v If the value is a varying-length string,
the first 2 bytes contains its length.
v If the value is a LOB or XML string,
the first 4 bytes contains its length.
v If this value is numeric, the internal
numeric representation of the data.
v If a datetime value, the value is in *ISO
format.
| Parameter value descriptors for field procedures:

| A parameter value descriptor describes the data type and other attributes of a value.
| Parameter value descriptors are used with field procedures in these ways:
| v During field-definition, they describe each constant in the field procedure parameter value list
|
(FPPVL). The set of these optional parameter value descriptors are part of the FPPVL control block.
| v During field-encoding and field-decoding, the decoded (column) value and the encoded (field)
|
attributes are described by the column value descriptor (CVD) and the field value descriptor (FVD).
32
|
|
|
|
The column value descriptor (CVD) contains a description of a column value. During field-encoding, the
CVD describes the value to be encoded. During field-decoding, it describes the decoded value to be
supplied by the field procedure. During field-definition, it describes the column as defined in the
CREATE TABLE or ALTER TABLE statement.
|
|
|
|
The field value descriptor (FVD) contains a description of a field value. During field-encoding, the FVD
describes the encoded value to be returned from the field procedure. During field-decoding, it describes
the value to be decoded. During field-definition a description of the encoded value must put into the
FVD.
The following table describes a parameter value descriptor:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 7. sqlfpParameterDescription_T
Field-definition (function code 8):
The input provided to the field-definition operation, and the output required, are as follows:
|
|
v Parameter 1
Input - A small (2 byte) integer that describes the function to be performed (8 - field-definition).
|
|
|
|
v Parameter 2
Input/Output - A structure that defines the field procedure parameter value list (FPPVL). This is
an auto-extendable space. The minimum length of this structure is 8 bytes. The maximum
returned length of this structure is 32K.
|
|
v Parameter 3
Input - The structure sqlfpParameterDescription_T containing the decoded data attributes.
|
|
v Parameter 4
Not used.
Name
Offset
Data Type
Description
sqlfpSqlType
2-byte integer
SQL data type of this parameter. See

Appendix D of the SQL Reference for
supported values.
sqlfpByteLength
unsigned 4-byte integer
Length in bytes of this parameter. For

datetime parameters, the length of the
string representation of the parameter.
sqlfpLength
Length in characters of this parameter. If

this is a not a character or graphic type,
sqlfpLength and sqlfpByteLength are the
same value.
sqlfpPrecision
10
2-byte integer
Precision if this is a numeric parameter

that has precision (decimal, zoned, binary
with precision and scale).
sqlfpScale
12
2-byte integer
Scale if this is a numeric parameter that

has scale (decimal, zoned, binary with
precision and scale). Scale of 0 if this is a
date or time parameter. Scale of 6 if this
is a timestamp parameter.
sqlfpCcsid
14
CCSID of this parameter if character or

graphic or XML.
sqlfpAllocatedLength
16
The allocated length specified for the

column on the CREATE TABLE or ALTER
TABLE statement.
reserved1
18
character(14)
Reserved.
SQL programming
33
| v Parameter 5
|
Output - The structure sqlfpParameterDescription_T containing the encoded data attributes. The
|
output sqlfpParameterDescription_T must be valid with the appropriate CCSID, length, precision,
|
and scale fields set.
| v Parameter 6
|
Not used.
| v Parameter 7
|
Input/Output - The SQLSTATE (character(5)).
| v Parameter 8
|
Input/Output - The message text area (varchar(1000)).
| v Parameter 9
|
Input - Reserved.
|
|
|
|
|
Errors returned by a field procedure result in SQLCODE -681 (SQLSTATE '23507'), which is set in the SQL
communication area (SQLCA) and the DB2_RETURNED_SQLCODE and RETURNED_SQLSTATE
condition area item of the SQL diagnostics area. The contents of Parameter 7 and 8 are placed into the
tokens, in SQLCA, as field SQLERRMT and in the SQL Diagnostic area condition area item
MESSAGE_TEXT. The meaning of the error message is determined by the field procedure.
| Invalid data in Parameter 5, sqlfpParameterDescription_T, or an invalid length in Parameter 2 results in

| SQLCODE -685 (SQLSTATE '58002'). If the database manager is unable to invoke the field procedure then
| SQLCODE -682 (SQLSTATE '57010') is returned.
| The FPPVL can be redefined to suit the field procedure, and returned as the modified FPPVL, subject to
| the following restriction:
| v sqlfpOptParmValueListLength must contain the actual length of the modified FPPVL. If no parameter
|
list is returned, then sqlfpOptParmValueListLength must be set to 8.
|
|
|
|
The modified FPPVL is recorded in the catalog table QSYS2.SYSFIELDS, and is passed to the field
procedure during field-encoding and field-decoding. The modified FPPVL need not have the format of a
field procedure parameter list, and it need not describe constants by optional parameter value
descriptors.
| The nullability attribute of the column may not be changed.

| If the encoded data attribute is a character, graphic or XML type, the CCSID value must be set to a valid
| CCSID for the data type.
| If the column has a non-null default value, the encoded default value must not exceed the length allowed
| for the column's default value.
| Field-encoding (function code 0):
| The input provided to the field-encoding operation, and the output required, are as follows:
| v Parameter 1
|
Input - A small (2 byte) integer that describes the function to be performed (0 - field-encoding).
| v Parameter 2
|
Input - A structure that defines the modified field procedure parameter value list (FPPVL).
| v Parameter 3
|
Input - A structure described by sqlfpParameterDescription_T containing the decoded data
|
attributes.
34
|
|
|
|
|
v Parameter 4
Input Data to be encoded.
If the value is a varying-length string, the first 2 bytes contains its length. If the value is a LOB or
XML, then the first 4 bytes contains the length. If the value is numeric, the internal numeric
representation of the data. If a datetime value, the value is in *ISO format.
|
|
|
v Parameter 5
Input - A structure described by sqlfpParameterDescription_T containing the encoded data
attributes.
|
|
v Parameter 6
Output Location to place the encoded data.
|
|
|
|
If the encoded value is a varying-length string, the first 2 bytes must contain the length. If the
encoded value is a LOB or XML, then the first 4 bytes must contain the length. If the value is
numeric, the internal numeric representation of the data. If a datetime value, the value must be in
*ISO format.
|
|
v Parameter 7
|
|
v Parameter 8
|
|
v Parameter 9
Input - Reserved.
|
|
|
|
|
|
MESSAGE_TEXT. If the database manager is unable to invoke the field procedure then SQLCODE -682
(SQLSTATE '57010') is returned.
Field-decoding (function code 4):
The input provided to the field-decoding operation, and the output required, are as follows:
|
|
v Parameter 1
Input - A small (2 byte) integer that describes the function to be performed (4 - field-decoding).
|
|
v Parameter 2
Input - A structure that defines the modified field procedure parameter value list (FPPVL).
|
|
|
v Parameter 3
Input - A structure described by sqlfpParameterDescription_T containing the decoded data
attributes.
|
|
v Parameter 4
Output Location to place the decoded data.
|
|
|
|
If the decoded value is a varying-length string, the first 2 bytes must contain the length. If the
decoded value is a LOB or XML, then the first 4 bytes must contain the length. If the value is
numeric, the internal numeric representation of the data. If a datetime value, the value must be in
*ISO format.
|
|
|
v Parameter 5
Input - A structure described by sqlfpParameterDescription_T containing the encoded data
attributes.
|
|
v Parameter 6
Input - encoded data
SQL programming
35
If the value is a varying-length string, the first 2 bytes contains its length. If the value is a LOB or
XML, then the first 4 bytes contains the length. If the value is numeric, the internal numeric
representation of the data. If a datetime value, the value is in *ISO format.
|
|
|
| v Parameter 7
|
| v Parameter 8
|
| v Parameter 9
|
Input - Indicates that the caller is a system function that requires that the data be decoded
|
without masking.
|
|
|
|
|
|
MESSAGE_TEXT. If the database manager is unable to invoke the field procedure then SQLCODE -682
(SQLSTATE '57010') is returned.
| Example field procedure program:

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add field procedure FP1 to column C1. The Field Procedure FP1 takes one parameter which indicates the
number of bytes of the column the field procedure should operate on.
ALTER TABLE TESTTAB ALTER C1 SET FIELDPROC FP1(10)
#include "string.h"
#include <QSYSINC/H/SQLFP>
void reverse(char *in, char *out, long length);
main(int argc, void *argv[])
{
short *funccode = argv[1];
sqlfpFieldProcedureParameterList_T *optionalParms = argv[2];
char *sqlstate = argv[7];
sqlfpMessageText_T *msgtext = argv[8];
int bytesToProcess;
sqlfpOptionalParameterValueDescriptor_T *optionalParmPtr;
if (optionalParms->sqlfpNumberOfOptionalParms != 1)
{
memcpy(sqlstate,"38001",5);
return;
}
optionalParmPtr = (void *)&(optionalParms->sqlfpParmList);
bytesToProcess = *((int *)&optionalParmPtr->sqlfpParmData);
if (*funccode == 8)
/* create time */
{
sqlfpParameterDescription_T *inDataType = argv[3];
sqlfpParameterDescription_T *outDataType = argv[5];
if (inDataType->sqlfpSqlType !=452 &&
inDataType->sqlfpSqlType !=453 )
/* only support fixed length char */
{
return;
}
/* do something here to determine the result data type */
/* ..... */
/* in this example input and output types are exactly the same */
/* so just copy */
memcpy(outDataType, inDataType, sizeof(sqlfpParameterDescription_T));
}
else if (*funccode == 0)
/* encode */
{
36
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
char *decodedData = argv[4];

char *encodedData = argv[6];
reverse(decodedData, encodedData, bytesToProcess);
}
/* decode */
{
reverse(encodedData, decodedData, bytesToProcess);
}
else /* unsupported option -- error */
memcpy(sqlstate, "38003",5);
}
void reverse(char *in, char *out, long length)
{
int i;
for (i=0;i<length; ++i) {
out[length - (i+1)] = in[i];
}
}
|
|
|
|
|
|
|
|
|
|
|
|
General guidelines for writing field procedures
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
v The field procedure will not be called if the data to be encoded or decoded is the null value.
v On an encode operation, packed decimal and zoned decimal values will be converted to the preferred
sign prior to calling the user field procedure program.
v The field procedure must be deterministic. For SQE, caching of results will occur based on the
QAQQINI FIELDPROC_ENCODED_COMPARISON.
v The field procedure must be parallel capable and capable of running in a multi-threaded environment.
For RPG, this means the THREAD(*SERIALIZE) control specification must be specified.
v Must be capable of running in both a fenced and non-fenced environment.
v The program cannot be created with ACTGRP(*NEW). If the program is created with
ACTGRP(*CALLER), the program will run in the default activation group.
v Field procedure programs are expected to be short running. It is recommended that the field procedure
program avoid commitment control and native database operations.
v Create the program in the physical file's library.
v If an error occurs or is detected in the field procedure program, the field procedure program should set
the SQLSTATE and message text parameters. If the SQLSTATE parameter is not set to indicate an error,
database assumes that the field procedure ran successfully. This might cause the user data to end up in
an inconsistent state.
|
|
Warning: Field procedures are a productive way both to provide application functions and to manage
information. However, field procedure programs could provide the ability for someone with devious
The following considerations must be considered when writing field procedures:

v Must be an ILE *PGM object. *SRVPGMs, OPM *PGMs, and JAVA objects are not supported.
v Authority to the field procedure *PGM object is checked when the field procedure is added to the
table. Authority checking is not done when the field procedure is invoked.
Create the field procedure program so that it runs under the user profile of the user who created it.
In this way, users who do not have the same level of authority to the program will not encounter
errors.
Create the program with USRPRF(*OWNER) and *EXCLUDE public authority. Do not grant
authorities to the field procedure program to USER(*PUBLIC). Avoid having the field procedure
program altered or replaced by other users.
v No SQL is allowed in a field procedure.
SQL programming
37
| intentions to create a "Trojan horse"1 on your system. This is why it is important to restrict who has the
| authority to alter a table. If you are managing object authority carefully, the typical user will not have
| sufficient authority to add a field procedure program.
| Index considerations:
| Indexes may be recovered at IPL time based on the RECOVER parameter of CRTPF, CRTLF, CHGPF, or
| CHGLF commands. Indexes that are based on a column that has a field procedure have special
| considerations.
|
|
|
|
|
Use of PASE(QSH) and JAVA within field procedures must be avoided if the index keys are built over
expressions that contain columns with field procedures or the sparse index criteria references a column
with an associated field procedure. If use of PASE or JAVA is required, consider changing indexes to
RECOVER(*NO) so that they are not recovered during the IPL process and recovered during an open
operation instead.
| Thread considerations:
| A field procedure runs in the same job as the operation that initiated the field procedure. However, the
| field procedure may or may not run in a different system thread (fenced or not fenced) which are
| separate from the thread from the initiating request.
|
|
|
|
|
|
|
|
Because the field procedure runs in the same job, it shares much of the same environment as the
initiating request. However, because it may run under a separate thread, the following threads
considerations apply:
v Field procedures do not inherit any program adopted authority that may have been active at the time
the request was initiated. Field procedure authority comes from the authority associated with the field
procedure program or from the authority of the user running.
v The field procedure cannot perform any operation that is blocked from being run in a secondary
thread.
| v The field procedure program must be created such that it either runs under a named activation group
|
or in the activation group of its caller (ACTGRP parameter). Programs that specify *CALLER will run
|
in the default activation group.
| Debug considerations:
| There are some things to keep in mind when debugging field procedures.
| Since field procedures can run in a secondary thread, it is recommended that debugging should be done
| using STRSRVJOB or the graphical debugger.
|
|
|
|
For natively run field procedures, the database manager uses the job default wait time. If the field
procedure does not return within that specified time, an error is returned. This default wait time may
need to be increased when debugging field procedures. For example, to change the default wait time to 5
minutes: CHGJOB DFTWAIT(300)
| Guidelines for writing field procedures that mask data

| Field procedures can be used to mask data for certain users or environments when data is decoded. Field
| procedures that mask data must be coded to handle special situations to ensure data is not corrupted.
| The following special situations must be handled by a field procedure that masks data:
1. In history, the Trojan horse was a large hollow wooden horse that was filled with Greek soldiers. After the horse was introduced
within the walls of Troy, the soldiers climbed out of the horse and fought the Trojans. In the computer world, a program that
hides destructive functions is often called a Trojan horse.
38
|
|
|
|
|
|
|
|
|
|
|
|
|
|
v Field-decoding
Masking must only be performed for field-decoding. It must not be performed for field-encoding. If
masking was performed for field-encoding, the masked data would be stored in the table and the
actual value would be lost.
In some cases, system code needs to copy data internally (the data is not being returned to the user
in these cases). For example, in some cases, RGZPFM, ALTER TABLE, and CRTDUPOBJ must copy
data internally. Likewise, data passed internally to triggers must not be masked. During these
operations, when the data is read, field-decoding will occur and when the data is written,
field-encoding will occur. If masking is performed in these cases during field-decoding, the mask
data will then be written and the actual data will be lost.
To prevent corruption, the ninth parameter to the field procedure indicates whether this is a system
operation where masking must not be performed. It is critical that the field procedure be written to
check this parameter during field-decoding and if the parameter indicates that masking must not be
performed, the field procedure must not mask regardless of the user or environment.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
v Field-encoding
For native update and insert operations, the field procedure must be able to identify when masked
data is being passed to the field procedure and take special actions. For example, a field procedure
might be written to mask a credit card number column. That same user may be authorized to read
and update the table through an RPG application that performs READ and UPDATE operations.
When the READ is performed, the credit card number is masked to prevent the user from seeing it,
but when the user performs the UPDATE, the masked data will be passed back to database on the
UPDATE operation and the field procedure will be called to encode the data. If the field procedure
does not recognize that the value being passed is masked, the masked data would be encoded and
stored in the table and the original value in the row would be corrupted with an encoded masked
data.
To prevent corruption, the field procedure must recognize on field-encoding that the data is masked.
Instead of encoding the data, the field procedure must return a warning SQLSTATE value of 09501
in the seventh parameter.
- For an UPDATE operation, 09501 indicates to DB2 that the current value for the column should
be used.
- For an INSERT operation, 09501 indicates to DB2 that the default value should be used for the
associated column value.
|
|
|
|
|
|
|
|
|
|
|
Query Considerations: There are several considerations that apply to queries that reference a column of a
table that has a field procedure that masks data:
v Depending on how the optimizer implements a query, the same query may return different rows and
values for different users or environments. This will occur in cases where optimizer must decode the
data in order to perform comparisons or evaluate expressions in a query. If masking is performed for
one user but not for another user, the result of the decode operation will be very different, so the
resulting rows and values can also be quite different for the two users.
For example, assume that a field procedure returns (decodes) data for user profile MAIN without
masking and returns (decodes) data for user profile QUSER with masking. An application contains the
following query:
SELECT * FROM orders WHERE cardnum = 112233
|
|
By default, the optimizer will try to implement the search condition (logically) as follows:
|
|
|
|
|
This is the best performing implementation since it allows DB2 to compare the encoded version of the
constant 112233 with the encoded version of the CARDNUM values that are stored in the orders
table. Since the optimizer did not decode the data to perform the comparison, the query will return the
same rows for the MAIN and QUSER user profiles. The only difference will be that QUSER will see
masked values in the result rows for the CARDNUM column.
WHERE cardnum = FieldProc ENCODE(112233)
SQL programming
39
|
|
|
|
|
|
|
|
The implementation of queries that reference a field procedure column can be controlled by the
QAQQINI FIELDPROC_ENCODED_COMPARISON option. The default value for this option is
*ALLOW_EQUAL. This option enables the optimizer to implement the comparison using the encoded
values.
In the previous example, if the FIELDPROC_ENCODED_COMPARISON option was changed to
*NONE, the query would return different rows for the two users. When the value is *NONE, an equal
comparison will be implemented internally by DB2 as follows:
|
|
|
|
|
|
In this case, DB2 has to decode the CARDNUM values for every row in the table to compare against
the original constant '112233'. This means that the comparison for the MAIN user profile will compare
the decoded and unmasked card number values (112233, 332211, etc) to 112233. The MAIN user
profile will find the orders associated with the specified card number (112233). However, the query will
not return any rows for the QUSER user profile. That is because the comparison for QUSER will be
comparing the masked value of the card numbers (****33, ****11, etc) with the constant 112233.
|
|
|
For more information on how the QAQQINI FIELDPROC_ENCODED_COMPARISON option affects

field procedures see the Database Performance and Query Optimization topic in the Information
Center.
WHERE FieldProc DECODE(cardnum)=112233
| v REFRESH of a materialized query table is affected by the QAQQINI

|
FIELDPROC_ENCODED_COMPARISON option. If the materialized query table references a column
|
with a field procedure that masks, it is imperative that the REFRESH of the MQT be issued by a user
|
that is allowed to see unmasked data. Otherwise, the results in the MQT will be incorrect for all users.
| v CREATE TABLE LIKE, CREATE TABLE AS, DECLARE GLOBAL TEMPORARY TABLE LIKE, or
|
DECLARE GLOBAL TEMPORARY TABLE AS are affected by the QAQQINI
|
FIELDPROC_ENCODED_COMPARISON option. If the statements are issued by a user that is not
|
allowed to see unmasked data, the resulting table will contain masked data.
| v OPNQRYF and Query/400 are not affected by the QAQQINI FIELDPROC_ENCODED_COMPARISON
|
option. The optimizer always processes by decoding values (similar to a
|
FIELDPROC_ENCODED_COMPARISON option of *NONE).
| v Select/omit DDS-created logical files are also not affected by the QAQQINI
|
FIELDPROC_ENCODED_COMPARISON option. The logical file is processed by decoding values
|
(similar to a FIELDPROC_ENCODED_COMPARISON option of *NONE).
| Best Practices: There are two QAQQINI options that are strongly recommended for use if you have field
| procedures that mask data:
| FIELDPROC_ENCODED_COMPARISON
|
The default option for FIELDPROC_ENCODED_COMPARISON is *ALLOW_EQUAL which
|
works very well for field procedures that do not mask data. If field procedures are used that do
|
mask data, however, *NONE is the most secure and recommended option.
| CACHE_RESULTS
|
The default option for CACHE_RESULTS is *SYSTEM. In many cases, this option works well.
|
However, if field procedures that mask data are used, you should specify *JOB for
|
CACHE_RESULTS.
| Since these two options can affect the behavior of field procedures that mask data, it is also important to
| ensure that only authorized users be allowed to specify new or different QAQQINI options:
| v CHGQRYA command
|
|
|
| v
Verify that only authorized users can execute the CHGQRYA command. By default only users with job
control (*JOBCTL) special authority or have the QIBM_DB_SQLADM function usage are authorized to
the CHGQRYA command.
QUSRSYS/QAQQINI file
40
|
|
|
Verify that only authorized users can create the QUSRSYS/QAQQINI file or update it if it already
exists. By default *PUBLIC has *USE authority to QUSRSYS which is not be enough authority to create
a new QUSRSYS.QAQQINI file.
Example field procedure program that masks data:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add field procedure FP1 to column C1. The Field Procedure FP1 takes one additional parameter which
indicates the number of bytes of the column the field procedure should operate on.
ALTER TABLE TESTTAB ALTER C1 SET FIELDPROC FP1(10)
#include "string.h"
#include <QSYSINC/H/SQLFP>
void reverse(char *in, char *out, long length);
main(int argc, void *argv[])
{
short *funccode = argv[1];
sqlfpFieldProcedureParameterList_T *optionalParms = argv[2];
char *sqlstate = argv[7];
sqlfpMessageText_T *msgtext = argv[8];
int bytesToProcess;
sqlfpOptionalParameterValueDescriptor_T *optionalParmPtr;
sqlfpInformation_T *info = argv[9];
int masked;
if (optionalParms->sqlfpNumberOfOptionalParms != 1)
{
return;
}
optionalParmPtr = (void *)&(optionalParms->sqlfpParmList);
bytesToProcess = *((int *)&optionalParmPtr->sqlfpParmData);
/*******************************************************************/
/* CREATE CALL
*/
/*******************************************************************/
if (*funccode == 8)
/* create time */
{
sqlfpParameterDescription_T *inDataType = argv[3];
sqlfpParameterDescription_T *outDataType = argv[5];
if (inDataType->sqlfpSqlType !=452 &&
inDataType->sqlfpSqlType !=453 )
/* only support fixed length char */
{
return;
}
/* do something here to determine the result data type */
/* ..... */
/* in this example input and output types are exactly the same */
/* so just copy */
memcpy(outDataType, inDataType, sizeof(sqlfpParameterDescription_T));
}
/*******************************************************************/
/* ENCODE (WRITE) CALL
*/
/*******************************************************************/
/* encode */
{
/*
/*
/*
/*
if
Detect that the value passed on encode is masked.

*/
Return 09501 to tell DB that:
*/
- The field should not be updated for an update operation */
- The default value should be used for an insert operation*/
( memcmp(decodedData, "XXXXXXXXXXXX", 12) == 0 )
SQL programming
41
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{
}
else
{
reverse(decodedData, encodedData, bytesToProcess);
}
}
/*******************************************************************/
/* DECODE (READ) CALL
*/
/*******************************************************************/
/* decode */
{
/* The 9th paramter indicates that the column must not be
/* masked. For exmaple, during ALTER TABLE or RGZPFM.
if ( info->sqlfpNoMask == 1 )
{
return;
}
else
{
/* Mask the data when appropriate
/* Assume mask is set to 0 when it should not be masked
/* and 1 when it shoulbe be masked
if (masked == 1)
{
memcpy(decodedData, "XXXXXXXXXXXX", 12);
}
}
*/
*/
*/
*/
*/
return;
}
/*******************************************************************/
/* ERROR- UNSUPPORTED OPTION
*/
/*******************************************************************/
else /* unsupported option -- error */
memcpy(sqlstate, "38003",5);
}
/*******************************************************************/
/* REVERSE
*/
/*******************************************************************/
void reverse(char *in, char *out, long length)
{
int i;
for (i=0;i<length; ++i) {
out[length - (i+1)] = in[i];
}
}
Creating descriptive labels using the LABEL ON statement

Sometimes a text description is useful for an object (such as a table or an index) or useful as column text
or column headings. You can create a more descriptive label for these names by using the LABEL ON
statement.
42
These labels can be seen in the SQL catalog in the LABEL column.
The LABEL ON statement looks like this:
LABEL ON
TABLE CORPDATA.DEPARTMENT IS Department Structure Table
LABEL ON
COLUMN CORPDATA.DEPARTMENT.ADMRDEPT IS Reports to Dept.
After these statements are run, the table named DEPARTMENT displays the text description as
Department Structure Table and the column named ADMRDEPT displays the heading Reports to Dept. The
label for an object or a column cannot be more than 50 bytes and the label for a column heading cannot
be more than 60 bytes (blanks included). Here are the examples of LABEL ON statements for column
headings:
This LABEL ON statement provides column heading 1 and column heading 2:
*...+....1....+....2....+....3....+....4....+....5....+....6..*
LABEL ON COLUMN CORPDATA.EMPLOYEE.EMPNO IS
Employee
Number
This LABEL ON statement provides three levels of column headings for the SALARY column:
*...+....1....+....2....+....3....+....4....+....5....+....6..*
LABEL ON COLUMN CORPDATA.EMPLOYEE.SALARY IS
Yearly
Salary
(in dollars)
This LABEL ON statement removes the column heading for SALARY:

*...+....1....+....2....+....3....+....4....+....5....+....6..*
This LABEL ON statement provides a DBCS column heading with two levels specified:
*...+....1....+....2....+....3....+....4....+....5....+....6..*
<AABBCCDD>
<EEFFGG>
This LABEL ON statement provides the column text for the EDLEVEL column:
*...+....1....+....2....+....3....+....4....+....5....+....6..*
LABEL ON COLUMN CORPDATA.EMPLOYEE.EDLEVEL TEXT IS
Number of years of formal education
Related reference:
LABEL
Describing an SQL object using COMMENT ON

After you create an SQL object, such as a table or view, you can provide object information for future
reference using the COMMENT ON statement.
The information can be the purpose of the object, who uses it, and anything unusual or special about it.
You can also include similar information about each column of a table or view. A comment is especially
useful if your names do not clearly indicate the contents of the columns or objects. In that case, use a
comment to describe the specific contents of the column or objects. Usually, your comment must not be
more than 2000 characters, but for sequences the maximum length is 500 characters. If the object already
contains a comment, the old comment is replaced by the new one.
An example of using COMMENT ON follows:
COMMENT ON TABLE CORPDATA.EMPLOYEE IS
Employee table. Each row in this table represents
one employee of the company.
SQL programming
43
Getting comments after running a COMMENT ON statement

After you run a COMMENT ON statement for a table, your comments are stored in the
LONG_COMMENT column of SYSTABLES. Comments for the other objects are stored in the
LONG_COMMENT column of the appropriate catalog table. The following example gets the comments
that are added by the COMMENT ON statement in the previous example:
SELECT LONG_COMMENT
FROM CORPDATA.SYSTABLES
WHERE NAME = EMPLOYEE
Related reference:
COMMENT
Changing a table definition

You can change the definition of a table by adding a new column, changing an existing column definition
such as its length or default value, dropping an existing column, adding or removing constraints,
changing partitioning for the table, or altering one of many other options.
To change a table definition, you can use the ALTER TABLE statement. You can add, change, or drop
columns and add or remove constraints all with one ALTER TABLE statement. You can also include other
options to define or change partitioning, add a materialized query table definition, or change your media
preference for the table to use solid state disk storage media.
A second option for changing a table definition is to use the CREATE OR REPLACE TABLE statement.
With CREATE OR REPLACE TABLE, all the changes to the table definition are made with the standard
CREATE TABLE statement. If the table already exists, any changes between the new table definition and
the existing table definition are recognized and applied to the existing table. For example, based on the
content of the CREATE OR REPLACE TABLE statement, several new columns could be added, the data
type of a column could be changed, and a primary key could be defined.
Related reference:
ALTER TABLE
Adding a column
When you add a new column to a table, the column is initialized with its default value for all existing
rows. If NOT NULL is specified, a default value must also be specified.
You can add a column to a table using the ADD COLUMN clause of the SQL ALTER TABLE statement.
The altered table may consist of up to 8000 columns. The sum of the byte counts of the columns must not
be greater than 32766 or, if a VARCHAR or VARGRAPHIC column is specified, 32740. If a LOB column is
specified, the sum of record data byte counts of the columns must not be greater than 15 728 640.
Related reference:
ALTER TABLE
Changing a column
You can change a column definition in a table using the ALTER COLUMN clause of the ALTER TABLE
statement.
When you change the data type of an existing column, the old and new attributes must be compatible.
You can always change a character, graphic, or binary column from fixed length to varying length or
LOB; or from varying length or LOB to fixed length.
When you convert to a data type with a longer length, data is padded with the appropriate pad
character. When you convert to a data type with a shorter length, data might be lost because of
truncation. An inquiry message prompts you to confirm the request.
44
If you have a column that does not allow the null value and you want to change it to now allow the null
value, use the DROP NOT NULL clause. If you have a column that allows the null value and you want
to prevent the use of null values, use the SET NOT NULL clause. If any of the existing values in that
column are the null value, the ALTER TABLE will not be performed and an SQLCODE of -190 will result.
Related reference:
Allowable conversions of data types
Related information:
ALTER TABLE
Allowable conversions of data types

Table 8. Allowable conversions
From data type
To data type
Decimal
Numeric
Decimal
Bigint, Integer, Smallint
Decimal
Decfloat
Decimal
Float
Numeric
Decimal
Numeric
Numeric
Decfloat
Numeric
Float
Decimal
Numeric
Decfloat
Float
Float
Decimal
Float
Numeric
Float
Float
Decfloat
Character
DBCS-open
Character
UCS-2 or UTF-16 graphic
DBCS-open
Character
DBCS-open
DBCS-either
Character
DBCS-either
DBCS-open
DBCS-either
DBCS-only
DBCS-open
DBCS-only
DBCS graphic
DBCS-only
DBCS graphic
Character
DBCS-open
DBCS graphic
SQL programming
45
Table 8. Allowable conversions (continued)

From data type
To data type
distinct type
source type
source type
distinct type
When you change an existing column, only the attributes that you specify are changed. All other
attributes remain unchanged. For example, you have a table with the following table definition:
CREATE TABLE EX1 (COL1 CHAR(10) DEFAULT COL1,
COL2 VARCHAR(20) ALLOCATE(10) CCSID 937,
COL3 VARGRAPHIC(20) ALLOCATE(10)
NOT NULL WITH DEFAULT)
After you run the following ALTER TABLE statement, COL2 still has an allocated length of 10 and
CCSID 937, and COL3 still has an allocated length of 10.
ALTER TABLE EX1 ALTER COLUMN COL2 SET DATA TYPE VARCHAR(30)
ALTER COLUMN COL3 DROP NOT NULL
Related reference:
Changing a column on page 44
You can change a column definition in a table using the ALTER COLUMN clause of the ALTER TABLE
statement.
Deleting a column
You can delete a column using the DROP COLUMN clause of the ALTER TABLE statement.
Dropping a column deletes that column from the table definition. If CASCADE is specified, any views,
indexes, and constraints dependent on that column will also be dropped. If RESTRICT is specified, and
any views, indexes, or constraints are dependent on the column, the column will not be dropped and
SQLCODE of -196 will be issued.
ALTER TABLE DEPT
DROP COLUMN NUMDEPT
Related reference:
ALTER TABLE
Order of operations for the ALTER TABLE statement

Operations for the ALTER TABLE statement are performed in a defined order.
The ALTER TABLE statement is performed as this set of steps shows:
1. Drop constraints
2. Drop materialized query table
3. Drop partition information
4. Drop columns for which the RESTRICT option was specified
5. Alter column definitions (this includes adding columns and dropping columns for which the
CASCADE option was specified)
6. Add or alter materialized query table
7. Add partitioning to a table
8. Add constraints
Within each of these steps, the order in which you specify the clauses is the order in which they are
performed, with one exception. If any columns are being dropped, that operation is logically done before
any column definitions are added or altered, in case record length is increased as a result of the ALTER
TABLE statement.
46
|
|
|
Using CREATE OR REPLACE TABLE
|
|
|
|
|
Using CREATE OR REPLACE TABLE lets you consolidate the master definition of a table into one
statement. You do not need to maintain the source for the original CREATE TABLE statement plus a
complex list of ALTER TABLE statements needed to recreate the most current version of a table. This
CREATE TABLE statement can be executed to deploy the current definition of the table either as a new
table or to replace a prior version of the table.
|
|
|
|
There are options to either keep the existing data in the table or to clear the data from the table during
the replace. The default is to keep all data. If you elect to clear all the data, your new table definition
does not need to be compatible with the original version. In all cases, other objects that depend on the
table, such as referential constraints, triggers, and views, must remain satisfied or the replace will fail.
|
|
|
|
|
|
Suppose your original table was this basic INVENTORY table.
|
|
|
|
|
|
|
|
|
|
|
|
Perhaps over time, you have updated the column names to be more descriptive, changed the DESCR
column to be a longer Unicode column, and added a timestamp column for when the row was last
updated. The following statement reflects all of these changes and can be executed against any prior
version of the table, as long as the column names can be matched to the prior column names and the
data types are compatible.
|
|
Partitioned tables can be modified using CREATE OR REPLACE TABLE. The following example
demonstrates splitting a single partition into multiple partitions.
|
|
|
|
|
|
|
|
Suppose your original table was defined to have 3 partitions
|
|
|
|
|
|
|
|
|
|
|
To break the second partition into 3 pieces, modify the original CREATE TABLE statement to redefine the
partitions.
The OR REPLACE option on the CREATE TABLE statement can be used to change an existing table
definition.
CREATE TABLE INVENTORY

(PARTNO SMALLINT NOT NULL,
DESCR
VARCHAR(24),
QONHAND INT,
CREATE OR REPLACE TABLE INVENTORY

(PART_NUMBER FOR PARTNO
SMALLINT NOT NULL,
DESCRIPTION FOR DESCR
VARGRAPHIC(500) CCSID 1200,
QUANTITY_ON_HAND FOR QONHAND INT,
LAST_MODIFIED FOR MODIFIED
TIMESTAMP
NOT NULL GENERATED ALWAYS FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP,
CREATE TABLE PARTITIONED

(KEYFLD BIGINT,
DATAFLD VARCHAR(200))
PARTITION BY RANGE (KEYFLD)
(PARTITION FIRST STARTING 0 ENDING 100,
PARTITION SECOND STARTING 100 EXCLUSIVE ENDING 200,
PARTITION THIRD STARTING 200 EXCLUSIVE ENDING 300)
CREATE OR REPLACE TABLE PARTITIONED

(KEYFLD BIGINT,
DATAFLD VARCHAR(200))
PARTITION BY RANGE (KEYFLD)
(PARTITION FIRST STARTING 0 ENDING 100,
PARTITION SECOND STARTING 100 EXCLUSIVE ENDING 150,
PARTITION SPLIT1 STARTING 151 EXCLUSIVE ENDING 175,
PARTITION SPLIT2 STARTING 176 EXCLUSIVE ENDING 200,
PARTITION THIRD STARTING 200 EXCLUSIVE ENDING 300)
SQL programming
47
| Now the table will have 5 partitions with the data spread among them according to the new definition.
|
|
|
|
|
|
This example uses the default of ON REPLACE PRESERVE ALL ROWS. That means that all data for all
rows is guaranteed to be kept. If data from an existing partition doesn't fit in any new partition, the
statement fails. To remove a partition and the data from that partition, omit the partition definition from
the CREATE OR REPLACE TABLE statement and use ON REPLACE PRESERVE ROWS. This will
preserve all the data that can be assigned to the remaining partitions and discard any that no longer has
a defined partition.
Creating and using ALIAS names

When you refer to an existing table or view, or to a physical file that consists of multiple members, you
can avoid using file overrides by creating an alias. To create an alias, use the CREATE ALIAS statement.
You can create an alias for:
v A table or view
v A member of a table
A table alias defines a name for the file, including the specific member name. You can use this alias name
in an SQL statement in the same way that a table name is used. Unlike overrides, alias names are objects
that exist until they are dropped.
For example, if there is a multiple member file MYLIB.MYFILE with members MBR1 and MBR2, an alias
can be created for the second member so that SQL can easily refer to it.
CREATE ALIAS MYLIB.MYMBR2_ALIAS FOR MYLIB.MYFILE (MBR2)
When alias MYLIB.MYMBR2_ALIAS is specified on the following insert statement, the values are inserted
into member MBR2 in MYLIB.MYFILE:
INSERT INTO MYLIB.MYMBR2_ALIAS VALUES(ABC, 6)
Alias names can also be specified on DDL statements. Assume that MYLIB.MYALIAS is an alias for table
MYLIB.MYTABLE. The following DROP statement drops table MYLIB.MYTABLE:
DROP TABLE MYLIB.MYALIAS
If you really want to drop the alias name instead, specify the ALIAS keyword on the drop statement:
DROP ALIAS MYLIB.MYALIAS
Related reference:
CREATE ALIAS
Creating and using views

A view can be used to access data in one or more tables or views. You create a view by using a SELECT
statement.
For example, create a view that selects only the family name and the department of all the managers:
CREATE VIEW CORPDATA.EMP_MANAGERS FOR SYSTEM NAME EMPMANAGER AS
SELECT LASTNAME, WORKDEPT FROM CORPDATA.EMPLOYEE
WHERE JOB = MANAGER
| Since the view name, EMP_MANAGERS, is too long for a system object name, the FOR SYSTEM NAME
| clause can be used to provide the system name. Without adding this clause, a name like EMP_M00001
| will be generated for the system object.
48
After you create the view, you can use it in SQL statements just like a table. You can also change the data
in the base table through the view. The following SELECT statement displays the contents of
EMP_MANAGERS:
SELECT *
FROM CORPDATA.EMP_MANAGERS
The results follow.

LASTNAME
WORKDEPT
THOMPSON
B01
KWAN
C01
GEYER
E01
STERN
D11
PULASKI
D21
HENDERSON
E11
SPENSER
E21
If the select list contains elements other than columns such as expressions, functions, constants, or special
registers, and the AS clause was not used to name the columns, a column list must be specified for the
view. In the following example, the columns of the view are LASTNAME and YEARSOFSERVICE.
CREATE VIEW CORPDATA.EMP_YEARSOFSERVICE
(LASTNAME, YEARSOFSERVICE) AS
SELECT LASTNAME, YEAR (CURRENT DATE - HIREDATE)
FROM CORPDATA.EMPLOYEE
Because the results of querying this view change as the current year changes, they are not included here.
You can also define the previous view by using the AS clause in the select list to name the columns in the
view. For example:
CREATE VIEW CORPDATA.EMP_YEARSOFSERVICE AS
SELECT LASTNAME,
YEARS (CURRENT_DATE - HIREDATE) AS YEARSOFSERVICE
Using the UNION keyword, you can combine two or more subselects to form a single view. For example:
CREATE VIEW D11_EMPS_PROJECTS AS
(SELECT EMPNO
WHERE WORKDEPT = D11
UNION
SELECT EMPNO
FROM CORPDATA.EMPPROJACT
WHERE PROJNO = MA2112 OR
PROJNO = MA2113 OR
PROJNO = AD3111)
This view has the following data.

Table 9. Results of creating a view as UNION
EMPNO
000060
000150
000160
SQL programming
49
Table 9. Results of creating a view as UNION (continued)

EMPNO
000170
000180
000190
000200
000210
000220
000230
000240
200170
200220
Views are created with the sort sequence in effect at the time the CREATE VIEW statement is run. The
sort sequence applies to all character, or UCS-2 or UTF-16 graphic comparisons in the CREATE VIEW
statement subselect.
You can also create views using the WITH CHECK OPTION clause to specify the level of checking when
data is inserted or updated through the view.
Related concepts:
Retrieving data using the SELECT statement on page 56
Sort sequences and normalization in SQL on page 128
A sort sequence defines how characters in a character set relate to each other when they are compared or
ordered. Normalization allows you to compare strings that contain combining characters.
Related reference:
Using the UNION keyword to combine subselects on page 95
Using the UNION keyword, you can combine two or more subselects to form a fullselect.
CREATE VIEW
WITH CHECK OPTION on a view

WITH CHECK OPTION is an optional clause on the CREATE VIEW statement. It specifies the level of
checking when data is inserted or updated through a view.
If WITH CHECK OPTION is specified, every row that is inserted or updated through the view must
conform to the definition of the view. The option cannot be specified if the view is read-only. The
definition of the view must not include a subquery.
If the view is created without a WITH CHECK OPTION clause, insert and update operations that are
performed on the view are not checked for conformance to the view definition. Some checking might still
occur if the view is directly or indirectly dependent on another view that includes WITH CHECK
OPTION. Because the definition of the view is not used, rows that do not conform to the definition of the
view might be inserted or updated through the view. This means that the rows cannot be selected again
through the view.
Related reference:
CREATE VIEW
50
WITH CASCADED CHECK OPTION:

The WITH CASCADED CHECK OPTION clause specifies that every row that is inserted or updated
through a view must conform to the definition of the view.
In addition, the search conditions of all dependent views are checked when a row is inserted or updated.
If a row does not conform to the definition of the view, that row cannot be retrieved through the view.
For example, consider the following updatable view:
CREATE VIEW V1 AS SELECT COL1
FROM T1 WHERE COL1 > 10
Because no WITH CHECK OPTION is specified, the following INSERT statement is successful even
though the value being inserted does not meet the search condition of the view.
INSERT INTO V1 VALUES (5)
Create another view over V1, specifying the WITH CASCADED CHECK OPTION clause:
FROM V1 WITH CASCADED CHECK OPTION
The following INSERT statement fails because it produces a row that does not conform to the definition
of V2:
Consider one more view created over V2:

FROM V2 WHERE COL1 < 100
The following INSERT statement fails only because V3 is dependent on V2, and V2 has a WITH
CASCADED CHECK OPTION.
However, the following INSERT statement is successful because it conforms to the definition of V2.
Because V3 does not have a WITH CASCADED CHECK OPTION, it does not matter that the statement
does not conform to the definition of V3.
WITH LOCAL CHECK OPTION:

The WITH LOCAL CHECK OPTION clause is identical to the WITH CASCADED CHECK OPTION
clause except that you can update a row so that it can no longer be retrieved through the view. This can
happen only when the view is directly or indirectly dependent on a view that was defined with no WITH
CHECK OPTION clause.
For example, consider the same updatable view used in the previous example:
FROM T1 WHERE COL1 > 10
Create second view over V1, this time specifying WITH LOCAL CHECK OPTION:
FROM V1 WITH LOCAL CHECK OPTION
The same INSERT statement that failed in the previous CASCADED CHECK OPTION example succeeds
now because V2 does not have any search conditions, and the search conditions of V1 do not need to be
checked since V1 does not specify a check option.
SQL programming
51
Consider one more view created over V2:

FROM V2 WHERE COL1 < 100
The following INSERT is successful again because the search condition on V1 is not checked due to the
WITH LOCAL CHECK OPTION on V2, versus the WITH CASCADED CHECK OPTION in the previous
example.
The difference between LOCAL and CASCADED CHECK OPTION lies in how many of the dependent
views' search conditions are checked when a row is inserted or updated.
v WITH LOCAL CHECK OPTION specifies that the search conditions of only those dependent views
that have the WITH LOCAL CHECK OPTION or WITH CASCADED CHECK OPTION are checked
when a row is inserted or updated.
v WITH CASCADED CHECK OPTION specifies that the search conditions of all dependent views are
checked when a row is inserted or updated.
Example: Cascaded check option:
This example shows how the check option is enforced on a number of dependent views that are defined
with or without a check option.
Use the following table and views:
CREATE TABLE T1 (COL1 CHAR(10))
FROM T1 WHERE COL1 LIKE A%
FROM V1 WHERE COL1 LIKE %Z
WITH LOCAL CHECK OPTION
FROM V2 WHERE COL1 LIKE AB%
FROM V3 WHERE COL1 LIKE %YZ
WITH CASCADED CHECK OPTION
FROM V4 WHERE COL1 LIKE ABC%
Different search conditions are going to be checked depending on which view is being operated on with
an INSERT or UPDATE statement.
v If V1 is operated on, no conditions are checked because V1 does not have a WITH CHECK OPTION
specified.
v If V2 is operated on,
COL1 must end in the letter Z, but it doesn't need to start with the letter A. This is because the
check option is LOCAL, and view V1 does not have a check option specified.
COL1 must end in the letter Z, but it does not need to start with the letter A. V3 does not have a
check option specified, so its own search condition must not be met. However, the search condition
for V2 must be checked because V3 is defined on V2, and V2 has a check option.
52
COL1 must start with 'AB' and must end with 'YZ'. Because V4 has the WITH CASCADED CHECK
OPTION specified, every search condition for every view on which V4 is dependent must be
checked.
COL1 must start with 'AB', but not necessarily 'ABC'. This is because V5 does not specify a check
option, so its own search condition does not need to be checked. However, because V5 is defined on
V4, and V4 had a cascaded check option, every search condition for V4, V3, V2, and V1 must be
checked. That is, COL1 must start with 'AB' and end with 'YZ'.
If V5 were created WITH LOCAL CHECK OPTION, operating on V5 means that COL1 must start with
'ABC' and end with 'YZ'. The LOCAL CHECK OPTION adds the additional requirement that the third
character must be a 'C'.
Creating indexes
You can use indexes to sort and select data. In addition, indexes help the system retrieve data faster for
better query performance.
Use the CREATE INDEX statement to create indexes. The following example creates an index over the
column LASTNAME in the CORPDATA.EMPLOYEE table:
CREATE INDEX CORPDATA.INX1 ON CORPDATA.EMPLOYEE (LASTNAME)
You can also create an index that does not exactly match the data for a column in a table. For example,
you can create an index that uses the uppercase version of an employee name:
CREATE INDEX CORPDATA.INX2 ON CORPDATA.EMPLOYEE (UPPER(LASTNAME))
Most expressions allowed by SQL can be used in the definition of the key columns.
You can create any number of indexes. However, because the indexes are maintained by the system, a
large number of indexes can adversely affect performance. One type of index, the encoded vector index
(EVI), allows for faster scans that can be more easily processed in parallel.
If an index is created that has exactly the same attributes as an existing index, the new index shares the
existing indexes' binary tree. Otherwise, another binary tree is created. If the attributes of the new index
are exactly the same as another index, except that the new index has fewer columns, another binary tree
is still created. It is still created because the extra columns prevent the index from being used by cursors
or UPDATE statements that update those extra columns.
Indexes are created with the sort sequence in effect at the time the CREATE INDEX statement is run. The
sort sequence applies to all SBCS character fields, or UCS-2 or UTF-16 graphic fields of the index.
Related concepts:
Creating an index strategy
Related reference:
CREATE INDEX
|
Creating and using global variables
You can use global variables to assign specific variable values for a session.
|
|
|
Use the CREATE VARIABLE statement to create a global variable. The following example creates a global
variable that defines a user class.
CREATE VARIABLE USER_CLASS INT DEFAULT (CLASS_FUNC(USER))
SQL programming
53
| This variable will have its initial value set based on the result of invoking a function called
| CLASS_FUNC. This function is assumed to assign a class value such as administrator or clerk based on
| the USER special register value.
| A global variable is instantiated for a session the first time it is referenced. Once it is set, it will maintain
| its value unless explicitly changed within the session.
|
|
|
|
|
|
A global variable can be used in a query to determine what results will be returned. In the following
example, a list of all employees from department A00 are listed. Only a session that has a global variable
with a USER_CLASS value of 1 will see the salaries for these employees.
SELECT EMPNO, LASTNAME, CASE WHEN USER_CLASS = 1 THEN SALARY ELSE NULL END
FROM EMPLOYEE
WHERE WORKDEPT = A00
| Global variables can be used in any context where an expression is allowed. Unlike a host variable, a
| global variable can be used in a CREATE VIEW statement.
|
Replacing existing objects
| You can replace an existing object using a CREATE statement rather than always needing to drop the
| object first.
|
|
|
|
|
For many SQL objects, you can optionally replace an existing object when using the CREATE SQL
statement. The existing object is effectively dropped before the new object is created. The following SQL
statements have that option:
v CREATE ALIAS
v CREATE FUNCTION
| v CREATE PROCEDURE
| v CREATE SEQUENCE
| v CREATE TRIGGER
| v CREATE VARIABLE
| v CREATE VIEW
| When the replace option is used for any of these statements, the privileges for the existing object are
| kept. The object definition is replaced by the new definition.
|
Example: Create or replace sequence
| To create a sequence called MYSEQUENCE, or replace a sequence of that name if it exists, use the
| following SQL statement
| CREATE OR REPLACE SEQUENCE MYSEQUENCE AS BIGINT
| The sequence will be created if it does not already exist. If it does exist, the privileges from the existing
| sequence will be transferred to the new sequence.
Catalogs in database design

A catalog is automatically created when you create a schema. There is also a system-wide catalog that is
always in the QSYS2 library.
When an SQL object is created in a schema, information is added to both the system catalog tables and
the schema's catalog tables. When an SQL object is created in a library, only the QSYS2 catalog is
updated. A table created with DECLARE GLOBAL TEMPORARY TABLE is not added to a catalog.
54
As the following examples show, you can display catalog information. You cannot insert, delete, or
update catalog information. You must have SELECT privileges on the catalog views to run the following
examples.
Related reference:
DB2 for i5/OS catalog views
Getting catalog information about a table

The SYSTABLES view contains a row for each table and view in the SQL schema. The SYSTABLES view
provides information such as the object type (table or view), the object name, the owner of the object, and
the schema where the object exists.
The following example statement displays information for the CORPDATA.DEPARTMENT table:
SELECT *
FROM CORPDATA.SYSTABLES
WHERE TABLE_NAME = DEPARTMENT
Getting catalog information about a column

The SYSCOLUMNS view contains a row for each column of a table and view in the schema.
The following example statement displays all the column names in the CORPDATA.DEPARTMENT table:
SELECT *
FROM CORPDATA.SYSCOLUMNS
The result of the previous example statement is a row of information for each column in the table.
For specific information about each column, specify a select-statement like this:
SELECT COLUMN_NAME, TABLE_NAME, DATA_TYPE, LENGTH, HAS_DEFAULT
FROM CORPDATA.SYSCOLUMNS
In addition to the column name for each column, the select-statement shows:
v The name of the table that contains the column
v The data type of the column
v The length attribute of the column
v If the column allows default values
The result looks like this.
COLUMN_NAME
TABLE_NAME
DATA_TYPE
LENGTH
HAS_DEFAULT
DEPTNO
DEPARTMENT
CHAR
DEPTNAME
DEPARTMENT
VARCHAR
29
MGRNO
DEPARTMENT
CHAR
ADMRDEPT
DEPARTMENT
CHAR
Dropping a database object

The DROP statement deletes an object. Depending on the action requested, any objects that are directly or
indirectly dependent on that object might also be deleted or might prevent the drop from happening.
For example, if you drop a table, any aliases, constraints, triggers, views, or indexes associated with that
table are also dropped. Whenever an object is deleted, its description is deleted from the catalog.
For example, to drop table EMPLOYEE, issue the following statement:
SQL programming
55
DROP TABLE EMPLOYEE RESTRICT
Related reference:
DROP
Data manipulation language

Data manipulation language (DML) describes the portion of SQL that manipulates or controls data.
Related concepts:
Types of SQL statements on page 7
Retrieving data using the SELECT statement

If SQL is unable to find a row that satisfies the search condition, an SQLCODE of +100 is returned.
If SQL finds errors while running your select-statement, a negative SQLCODE is returned. If SQL finds
more host variables than results, +326 is returned.
Related reference:
Creating a table using AS on page 21
You can create a table from the result of a SELECT statement. To create this type of table, use the
CREATE TABLE AS statement.
Creating and using views on page 48
statement.
Basic SELECT statement

The basic format and syntax of the SELECT statement consists of several required and optional clauses.
You can write SQL statements on one line or on many lines. For SQL statements in precompiled
programs, the rules for the continuation of lines are the same as those of the host language (the language
the program is written in). A SELECT statement can also be used by a cursor in a program. Finally, a
SELECT statement can be prepared in a dynamic application.
Notes:
1. The SQL statements described in this section can be run on SQL tables and views, and
database physical and logical files.
2. Character strings specified in an SQL statement (such as those used with WHERE or VALUES
clauses) are case-sensitive; that is, uppercase characters must be entered in uppercase and
lowercase characters must be entered in lowercase.
WHERE ADMRDEPT=a00
(does not return a result)
WHERE ADMRDEPT=A00
(returns a valid department number)
Comparisons might not be case sensitive if a shared-weight sort sequence is used where
uppercase and lowercase characters are treated as the same characters.
A SELECT statement can include the following:
1. The name of each column you want to include in the result.
2. The name of the table or view that contains the data.
3. A search condition to identify the rows that contain the information you want.
4. The name of each column used to group your data.
56
5. A search condition that uniquely identifies a group that contains the information you want.
6. The order of the results so a specific row among duplicates can be returned.
A SELECT statement looks like this:
SELECT column names
FROM table or view name
WHERE search condition
GROUP BY column names
HAVING search condition
ORDER BY column-name
The SELECT and FROM clauses must be specified. The other clauses are optional.
With the SELECT clause, you specify the name of each column you want to retrieve. For example:
SELECT EMPNO, LASTNAME, WORKDEPT
You can specify that only one column be retrieved, or as many as 8000 columns. The value of each
column you name is retrieved in the order specified in the SELECT clause.
If you want to retrieve all columns (in the same order as they appear in the table's definition), use an
asterisk (*) instead of naming the columns:
SELECT *
The FROM clause specifies the table that you want to select data from. You can select columns from more
than one table. When issuing a SELECT, you must specify a FROM clause. Issue the following statement:
SELECT *
FROM EMPLOYEE
The result is all of the columns and rows from the table EMPLOYEE.
The SELECT list can also contain expressions, including constants, special registers, and scalar fullselects.
An AS clause can be used to give the resulting column a name. For example, issue the following
statement:
SELECT LASTNAME, SALARY * .05 AS RAISE
FROM EMPLOYEE
WHERE EMPNO = 200140
The result of this statement follows.

Table 10. Results for query
LASTNAME
RAISE
NATZ
1421
Specifying a search condition using the WHERE clause

The WHERE clause specifies a search condition that identifies the row or rows that you want to retrieve,
update, or delete.
The number of rows you process with an SQL statement then depends on the number of rows that satisfy
the WHERE clause search condition. A search condition consists of one or more predicates. A predicate
specifies a test that you want SQL to apply to a specified row or rows of a table.
In the following example, WORKDEPT = 'C01' is a predicate, WORKDEPT and 'C01' are expressions, and
the equal sign (=) is a comparison operator. Note that character values are enclosed in apostrophes ();
SQL programming
57
numeric values are not. This applies to all constant values wherever they are coded within an SQL
statement. For example, to specify that you are interested in the rows where the department number is
C01, issue the following statement:
... WHERE WORKDEPT = C01
In this case, the search condition consists of one predicate: WORKDEPT = 'C01'.
To further illustrate WHERE, put it into a SELECT statement. Assume that each department listed in the
CORPDATA.DEPARTMENT table has a unique department number. You want to retrieve the department
name and manager number from the CORPDATA.DEPARTMENT table for department C01. Issue the
SELECT DEPTNAME, MGRNO
FROM CORPDATA.DEPARTMENT
WHERE DEPTNO = C01
The result of this statement is one row.

Table 11. Result table
DEPTNAME
MGRNO
INFORMATION CENTER
000030
If the search condition contains character, or UCS-2 or UTF-16 graphic column predicates, the sort
sequence that is in effect when the query is run is applied to those predicates. If a sort sequence is not
being used, character constants must be specified in uppercase or lowercase to match the column or
expression they are being compared to.
Related concepts:
Related reference:
Defining complex search conditions on page 70
In addition to the basic comparison predicates, such as = and >, a search condition can contain any of
these predicates: BETWEEN, IN, EXISTS, IS NULL, and LIKE.
Multiple search conditions within a WHERE clause on page 72
You can qualify your request further by coding a search condition that includes several predicates.
Expressions in the WHERE clause:
An expression in a WHERE clause names or specifies something that you want to compare to something
else.
The expressions you specify can be:
v A column name names a column. For example:
... WHERE EMPNO = 000200
EMPNO names a column that is defined as a 6-byte character value.

v An expression identifies two values that are added (+), subtracted (-), multiplied (*), divided (/), have
exponentiation (**), or concatenated (CONCAT or ||) to result in a value. The most common operands
of an expression are:
A constant
A column
A host variable
A global variable
58
A function
A special register
A scalar fullselect
Another expression
For example:
... WHERE INTEGER(PRENDATE - PRSTDATE) > 100
When the order of evaluation is not specified by parentheses, the expression is evaluated in the
following order:
1. Prefix operators
2. Exponentiation
3. Multiplication, division, and concatenation
4. Addition and subtraction
Operators on the same precedence level are applied from left to right.
v A constant specifies a literal value for the expression. For example:
... WHERE 40000 < SALARY
SALARY names a column that is defined as a 9-digit packed decimal value (DECIMAL(9,2)). It is
compared to the numeric constant 40000.
v A host variable identifies a variable in an application program. For example:
... WHERE EMPNO = :EMP
v A special register identifies a special value defined by the database manager. For example:
... WHERE LASTNAME = USER
v The NULL value specifies the condition of having an unknown value.

... WHERE DUE_DATE IS NULL
A search condition can specify many predicates separated by AND and OR. No matter how complex the
search condition, it supplies a TRUE or FALSE value when evaluated against a row. There is also an
unknown truth value, which is effectively false. That is, if the value of a row is null, this null value is not
returned as a result of a search because it is not less than, equal to, or greater than the value specified in
the search condition.
To fully understand the WHERE clause, you need to know the order SQL evaluates search conditions and
predicates, and compares the values of expressions. This topic is discussed in the DB2 for i SQL reference
topic collection.
Related concepts:
Using subqueries on page 120
You can use subqueries in a search condition as another way to select data. Subqueries can be used
anywhere an expression can be used.
Related reference:
Expressions
Comparison operators:
SQL supports several comparison operators.
Comparison operator
Description
<> or = or !=
=
Not equal to
Equal to
SQL programming
59
Comparison operator
Description
<
>
<= or > or !>
> = or < or !<
Less than
Greater than
Less than or equal to (or not greater than)
Greater than or equal to (or not less than)
NOT keyword:
You can precede a predicate with the NOT keyword to specify that you want the opposite of the
predicate's value (that is, TRUE if the predicate is FALSE).
NOT applies only to the predicate it precedes, not to all predicates in the WHERE clause. For example, to
indicate that you are interested in all employees except those working in the department C01, you can
say:
... WHERE NOT WORKDEPT = C01
which is equivalent to:

... WHERE WORKDEPT <> C01
GROUP BY clause
The GROUP BY clause allows you to find the characteristics of groups of rows rather than individual
rows.
When you specify a GROUP BY clause, SQL divides the selected rows into groups such that the rows of
each group have matching values in one or more columns or expressions. Next, SQL processes each
group to produce a single-row result for the group. You can specify one or more columns or expressions
in the GROUP BY clause to group the rows. The items you specify in the SELECT statement are
properties of each group of rows, not properties of individual rows in a table or view.
Without a GROUP BY clause, the application of SQL aggregate functions returns one row. When GROUP
BY is used, the function is applied to each group, thereby returning as many rows as there are groups.
For example, the CORPDATA.EMPLOYEE table has several sets of rows, and each set consists of rows
describing members of a specific department. To find the average salary of people in each department,
you can issue:
SELECT WORKDEPT, DECIMAL (AVG(SALARY),5,0)
GROUP BY WORKDEPT
The result is several rows, one for each department.

WORKDEPT
AVG-SALARY
A00
40850
B01
41250
C01
29722
D11
25147
D21
25668
E01
40175
E11
21020
E21
24086
60
Notes:
1. Grouping the rows does not mean ordering them. Grouping puts each selected row in a
group, which SQL then processes to derive characteristics of the group. Ordering the rows
puts all the rows in the results table in ascending or descending collating sequence.
Depending on the implementation selected by the database manager, the resulting groups
might appear to be ordered.
2. If there are null values in the column you specify in the GROUP BY clause, a single-row result
is produced for the data in the rows with null values.
3. If the grouping occurs over character, or UCS-2 or UTF-16 graphic columns, the sort sequence
in effect when the query is run is applied to the grouping.
When you use GROUP BY, you list the columns or expressions you want SQL to use to group the rows.
For example, suppose that you want a list of the number of people working on each major project
described in the CORPDATA.PROJECT table. You can issue:
SELECT SUM(PRSTAFF), MAJPROJ
FROM CORPDATA.PROJECT
GROUP BY MAJPROJ
The result is a list of the company's current major projects and the number of people working on each
project.
SUM(PRSTAFF)
MAJPROJ
AD3100
AD3110
10
MA2100
MA2110
OP1000
OP2000
OP2010
32.5
You can also specify that you want the rows grouped by more than one column or expression. For
example, you can issue a select statement to find the average salary for men and women in each
department, using the CORPDATA.EMPLOYEE table. To do this, you can issue:
SELECT WORKDEPT, SEX, DECIMAL(AVG(SALARY),5,0) AS AVG_WAGES
GROUP BY WORKDEPT, SEX
The result follows.

WORKDEPT
SEX
AVG_WAGES
A00
49625
A00
35000
B01
41250
C01
29722
D11
25817
D11
24764
D21
26933
D21
24720
SQL programming
61
WORKDEPT
SEX
AVG_WAGES
E01
40175
E11
22810
E11
16545
E21
25370
E21
23830
Because you did not include a WHERE clause in this example, SQL examines and processes all rows in
the CORPDATA.EMPLOYEE table. The rows are grouped first by department number and next (within
each department) by sex before SQL derives the average SALARY value for each group.
Related concepts:
Related reference:
ORDER BY clause on page 63
The ORDER BY clause specifies the particular order in which you want selected rows returned. The order
is sorted by ascending or descending collating sequence of a column's or an expression's value.
HAVING clause
The HAVING clause specifies a search condition for the groups selected by the GROUP BY clause.
The HAVING clause says that you want only those groups that satisfy the condition in that clause.
Therefore, the search condition you specify in the HAVING clause must test properties of each group
rather than properties of individual rows in the group.
The HAVING clause follows the GROUP BY clause and can contain the same kind of search condition as
you can specify in a WHERE clause. In addition, you can specify aggregate functions in a HAVING
clause. For example, suppose that you want to retrieve the average salary of women in each department.
To do this, use the AVG aggregate function and group the resulting rows by WORKDEPT and specify a
WHERE clause of SEX = F.
To specify that you want this data only when all the female employees in the selected department have
an education level equal to or greater than 16 (a college graduate), use the HAVING clause. The HAVING
clause tests a property of the group. In this case, the test is on MIN(EDLEVEL), which is a group
property:
SELECT WORKDEPT, DECIMAL(AVG(SALARY),5,0) AS AVG_WAGES, MIN(EDLEVEL) AS MIN_EDUC
WHERE SEX=F
GROUP BY WORKDEPT
HAVING MIN(EDLEVEL)>=16
The result follows.

WORKDEPT
AVG_WAGES
MIN_EDUC
A00
49625
18
C01
29722
16
D11
25817
17
You can use multiple predicates in a HAVING clause by connecting them with AND and OR, and you
can use NOT for any predicate of a search condition.
62
Note: If you intend to update a column or delete a row, you cannot include a GROUP BY or HAVING
clause in the SELECT statement within a DECLARE CURSOR statement. These clauses make it a
read-only cursor.
Predicates with arguments that are not aggregate functions can be coded in either WHERE or HAVING
clauses. It is typically more efficient to code the selection criteria in the WHERE clause because it is
handled earlier in the query processing. The HAVING selection is performed in post processing of the
result table.
If the search condition contains predicates involving character, or UCS-2 or UTF-16 graphic columns, the
sort sequence in effect when the query is run is applied to those predicates.
Related concepts:
Related reference:
Using a cursor on page 383
When SQL runs a SELECT statement, the resulting rows comprise the result table. A cursor provides a
way to access a result table.
ORDER BY clause
For example, to retrieve the names and department numbers of female employees listed in the
alphanumeric order of their department numbers, you can use this select-statement:
SELECT LASTNAME,WORKDEPT
WHERE SEX=F
ORDER BY WORKDEPT
The result follows.

LASTNAME
WORKDEPT
HAAS
A00
HEMMINGER
A00
KWAN
C01
QUINTANA
C01
NICHOLLS
C01
NATZ
C01
PIANKA
D11
SCOUTTEN
D11
LUTZ
D11
JOHN
D11
PULASKI
D21
JOHNSON
D21
PEREZ
D21
HENDERSON
E11
SCHNEIDER
E11
SETRIGHT
D11
SQL programming
63
LASTNAME
WORKDEPT
SCHWARTZ
E11
SPRINGER
E11
WONG
E21
Note: Null values are ordered as the highest value.

The column specified in the ORDER BY clause does not need to be included in the SELECT clause. For
example, the following statement will return all female employees ordered with the largest salary first:
SELECT LASTNAME,FIRSTNME
WHERE SEX=F
ORDER BY SALARY DESC
If an AS clause is specified to name a result column in the select-list, this name can be specified in the
ORDER BY clause. The name specified in the AS clause must be unique in the select-list. For example, to
retrieve the full names of employees listed in alphabetic order, you can use this select-statement:
SELECT LASTNAME CONCAT FIRSTNME AS FULLNAME
ORDER BY FULLNAME
This select-statement can optionally be written as:

SELECT LASTNAME CONCAT FIRSTNME
ORDER BY LASTNAME CONCAT FIRSTNME
Instead of naming the columns to order the results, you can use a number. For example, ORDER BY 3
specifies that you want the results ordered by the third column of the results table, as specified by the
select-list. Use a number to order the rows of the results table when the sequencing value is not a named
column.
You can also specify whether you want SQL to collate the rows in ascending (ASC) or descending (DESC)
sequence. An ascending collating sequence is the default. In the previous select-statement, SQL first
returns the row with the lowest FULLNAME expression (alphabetically and numerically), followed by
rows with higher values. To order the rows in descending collating sequence based on this name, specify:
... ORDER BY FULLNAME DESC
You can specify a secondary ordering sequence (or several levels of ordering sequences) as well as a
primary one. In the previous example, you might want the rows ordered first by department number,
and within each department, ordered by employee name. To do this, specify:
... ORDER BY WORKDEPT, FULLNAME
If character columns, or UCS-2 or UTF-16 graphic columns are used in the ORDER BY clause, ordering
for these columns is based on the sort sequence in effect when the query is run.
Related concepts:
Related reference:
GROUP BY clause on page 60
rows.
64
Static SELECT statements

For a static SELECT statement (one embedded in an SQL program), an INTO clause must be specified
before the FROM clause.
The INTO clause names the host variables (variables in your program used to contain retrieved column
values). The value of the first result column specified in the SELECT clause is put into the first host
variable named in the INTO clause; the second value is put into the second host variable, and so on.
The result table for a SELECT INTO should contain just one row. For example, each row in the
CORPDATA.EMPLOYEE table has a unique EMPNO (employee number) column. The result of a SELECT
INTO statement for this table, if the WHERE clause contains an equal comparison on the EMPNO
column, will be exactly one row (or no rows). Finding more than one row is an error, but one row is still
returned. You can control which row will be returned in this error condition by specifying the ORDER BY
clause. If you use the ORDER BY clause, the first row in the result table is returned.
If you want more than one row to be the result of a SELECT INTO statement, use a DECLARE CURSOR
statement to select the rows, followed by a FETCH statement to move the column values into host
variables one or many rows at a time.
When using the select-statement in an application program, list the column names to give your program
more data independence. There are two reasons for this:
1. When you look at the source code statement, you can easily see the one-to-one correspondence
between the column names in the SELECT clause and the host variables named in the INTO clause.
2. If a column is added to a table or view you access and you use SELECT * ..., and you create the
program again from source, the INTO clause does not have a matching host variable named for the
new column. The extra column causes you to get a warning (not an error) in the SQLCA (SQLWARN3
will contain a W). When using the GET DIAGNOSTICS statement, the RETURNED_SQLSTATE item
will have a value of '01503'.
Related reference:
Handling null values

A null value indicates the absence of a column value in a row. A null value is an unknown value; it is not
the same as zero or all blanks.
Null values can be used as a condition in the WHERE and HAVING clauses. For example, a WHERE
clause can specify a column that, for some rows, contains a null value. A basic comparison predicate
using a column that contains null values does not select a row that has a null value for the column. This
is because a null value is not less than, equal to, or greater than the value specified in the condition. The
IS NULL predicate is used to check for null values. To select the values for all rows that contain a null
value for the manager number, you can specify:
SELECT DEPTNO, DEPTNAME, ADMRDEPT
FROM CORPDATA.DEPARTMENT
WHERE MGRNO IS NULL
The result follows.

DEPTNO
DEPTNAME
ADMRDEPT
D01
DEVELOPMENT CENTER
A00
F22
BRANCH OFFICE F2
E01
G22
BRANCH OFFICE G2
E01
H22
BRANCH OFFICE H2
E01
SQL programming
65
DEPTNO
DEPTNAME
ADMRDEPT
I22
BRANCH OFFICE I2
E01
J22
BRANCH OFFICE J2
E01
To get the rows that do not have a null value for the manager number, you can change the WHERE
clause like this:
WHERE MGRNO IS NOT NULL
Another predicate that is useful for comparing values that can contain the NULL value is the DISTINCT
predicate. Comparing two columns using a normal equal comparison (COL1 = COL2) will be true if both
columns contain an equal non-null value. If both columns are null, the result will be false because null is
never equal to any other value, not even another null value. Using the DISTINCT predicate, null values
are considered equal. So COL1 is NOT DISTINCT from COL2 will be true if both columns contain an
equal non-null value and also when both columns are the null value.
For example, suppose that you want to select information from two tables that contain null values. The
first table T1 has a column C1 with the following values.
C1
2
1
null
The second table T2 has a column C2 with the following values.

C2
2
null
Run the following SELECT statement:

SELECT *
FROM T1, T2
WHERE C1 IS DISTINCT FROM C2
The result follows.

C1
C2
For more information about the use of null values, see the DB2 for i SQL reference topic collection.
Special registers in SQL statements

You can specify certain special registers in SQL statements. A special register, for example, CURRENT
DATE, contains information that can be referenced in SQL statements.
For locally run SQL statements, the special registers and their contents are shown in the following table.
66
|
|
Special registers
Contents
CURRENT CLIENT_ACCTNG
CLIENT ACCTNG
The accounting string for the client connection.
CURRENT CLIENT_APPLNAME
CLIENT APPLNAME
The application name for the client connection.
CURRENT CLIENT_PROGRAMID
CLIENT PROGRAMID
The program ID for the client connection.
CURRENT CLIENT_USERID
CLIENT USERID
The client user ID for the client connection.
CURRENT CLIENT_WRKSTNNAME
CLIENT WRKSTNNAME
The workstation name for the client connection.
CURRENT DATE
CURRENT_DATE
The current date.
CURRENT DEBUG MODE
The debug mode to be used when creating or altering

routines.
CURRENT DECFLOAT ROUNDING MODE
The rounding mode to be used when working with

decimal floating point values.
CURRENT DEGREE
The number of tasks the database manager should run in

parallel.
CURRENT IMPLICIT XMLPARSE OPTION
The whitespace handling options to be used for XML

data when implicitly parsed without validation.
CURRENT PATH
CURRENT_PATH
CURRENT FUNCTION PATH
The SQL path used to resolve unqualified data type

names, procedure names, and function names in
dynamically prepared SQL statements.
CURRENT SCHEMA
The schema name used to qualify unqualified database

object references where applicable in dynamically
prepared SQL statements.
CURRENT SERVER
CURRENT_SERVER
The name of the relational database currently being used.
CURRENT TIME
CURRENT_TIME
The current time.
CURRENT TIMESTAMP
CURRENT_TIMESTAMP
The current date and time in timestamp format.
CURRENT TIMEZONE
CURRENT_TIMEZONE
A duration of time that links local time to Universal Time

Coordinated (UTC) using the formula:
local time CURRENT TIMEZONE = UTC
It is taken from the system value QUTCOFFSET.
SESSION_USER
USER
The runtime authorization identifier (user profile) of the

job.
SYSTEM_USER
The authorization identifier (user profile) of the user

connected to the database.
If a single statement contains more than one reference to any of CURRENT DATE, CURRENT TIME, or
CURRENT TIMESTAMP special registers, or the CURDATE, CURTIME, or NOW scalar functions, all
values are based on a single clock reading.
For remotely run SQL statements, the values for special registers are determined at the remote system.
SQL programming
67
When a query over a distributed table references a special register, the contents of the special register on
the system that requests the query are used. For more information about distributed tables, see the DB2
Multisystem topic collection.
Casting data types

Sometimes you need to cast or change the type of an expression to a different data type or to the same
data type with a different length, precision, or scale.
For example, if you want to compare two columns of different types, such as a user-defined type based
on a character and an integer, you can change the character to an integer or the integer to a character to
make the comparison possible. A data type that can be changed to another data type is castable from the
source data type to the target data type.
You can use cast functions or CAST specification to explicitly cast a data type to another data type. For
example, if you have a column of dates (BIRTHDATE) defined as DATE and want to cast the column
data type to CHARACTER with a fixed length of 10, enter the following:
SELECT CHAR (BIRTHDATE,USA)
You can also use the CAST specification to cast data types directly:
SELECT CAST(BIRTHDATE AS CHAR(10))
Related reference:
Casting between data types
Date, time, and timestamp data types

Date, time, and timestamp are data types that are represented in an internal form not seen by an SQL
user.
Date, time, and timestamp can be represented by character string values and assigned to character string
variables. The database manager recognizes the following as date, time, and timestamp values:
v A value returned by the DATE, TIME, or TIMESTAMP scalar function.
v A value returned by the CURRENT DATE, CURRENT TIME, or CURRENT TIMESTAMP special
register.
v A value of a character string in the ANSI/ISO standard date, time, or timestamp format, for example,
DATE '1950-01-01'.
v A character string when it is an operand of an arithmetic expression or a comparison and the other
operand is a date, time, or timestamp. For example, in the predicate:
... WHERE HIREDATE < 1950-01-01
if HIREDATE is a date column, the character string '1950-01-01' is interpreted as a date.

v A character string variable or constant used to set a date, time, or timestamp column in either the SET
clause of an UPDATE statement, or the VALUES clause of an INSERT statement.
Related reference:
Data types
Specifying current date and time values:
You can specify a current date, time, or timestamp in an expression by using one of these special
registers: CURRENT DATE, CURRENT TIME, and CURRENT TIMESTAMP.
The value of each is based on a time-of-day clock reading obtained during the running of the statement.
Multiple references to CURRENT DATE, CURRENT TIME, or CURRENT TIMESTAMP within the same
SQL statement use the same value. The following statement returns the age (in years) of each employee
in the EMPLOYEE table when the statement is run:
68
SELECT YEAR(CURRENT DATE - BIRTHDATE)

The CURRENT TIMEZONE special register allows a local time to be converted to Universal Time
Coordinated (UTC). For example, if you have a table named DATETIME that contains a time column type
with a name of STARTT, and you want to convert STARTT to UTC, you can use the following statement:
SELECT STARTT - CURRENT TIMEZONE
FROM DATETIME
Date/time arithmetic:
Addition and subtraction are the only arithmetic operators applicable to date, time, and timestamp
values.
You can increment and decrement a date, time, or timestamp by a duration; or subtract a date from a
date, a time from a time, or a timestamp from a timestamp.
Related reference:
Datetime arithmetic in SQL
Row change expressions

The ROW CHANGE TIMESTAMP and ROW CHANGE TOKEN expressions can be used to determine
when a row was last changed.
To use a ROW CHANGE TIMESTAMP expression for a table, the table must be defined to have a row
change timestamp column.
The following query can find all the orders that are at least four weeks old and can list when they were
last modified:
SELECT ORDERNO, ROW CHANGE TIMESTAMP FOR ORDERS
FROM ORDERS
WHERE ORDER_DATE < CURRENT DATE - 4 WEEKS
The ROW CHANGE TOKEN expression can be used for both tables that have a row change timestamp
and tables that do not. It represents a modification point for a row. If a table has a row change
timestamp, it is derived from the timestamp. If a table does not have a row change timestamp, it is based
on an internal modification time that is not row-based, so it is not as accurate as for a table that has a
row change timestamp.
Handling duplicate rows

When SQL evaluates a select-statement, several rows might qualify to be in the result table, depending on
the number of rows that satisfy the search condition of the select-statement. Some of the rows in the
result table might be duplicate.
You can specify that you do not want any duplicates by using the DISTINCT keyword, followed by the
list of expressions:
SELECT DISTINCT JOB, SEX
...
DISTINCT means that you want to select only the unique rows. If a selected row duplicates another row
in the result table, the duplicate row is ignored (it is not put into the result table). For example, suppose
you want a list of employee job codes. You do not need to know which employee has what job code.
Because it is probable that several people in a department have the same job code, you can use
DISTINCT to ensure that the result table has only unique values.
The following example shows how to do this:
SQL programming
69
SELECT DISTINCT JOB

The result is two rows.

JOB
DESIGNER
MANAGER
If you do not include DISTINCT in a SELECT clause, you might find duplicate rows in your result,
because SQL returns the JOB column's value for each row that satisfies the search condition. Null values
are treated as duplicate rows for DISTINCT.
If you include DISTINCT in a SELECT clause and you also include a shared-weight sort sequence, fewer
values might be returned. The sort sequence causes values that contain the same characters to be
weighted the same. If 'MGR', 'Mgr', and 'mgr' are all in the same table, only one of these values is
returned.
Related concepts:
Defining complex search conditions

A search condition can include a scalar fullselect.
For character, or UCS-2 or UTF-16 graphic column predicates, the sort sequence is applied to the
operands before evaluation of the predicates for BETWEEN, IN, EXISTS, and LIKE clauses.
You can also perform multiple search conditions.
v BETWEEN ... AND ... is used to specify a search condition that is satisfied by any value that falls on or
between two other values. For example, to find all employees who were hired in 1987, you can use
this:
... WHERE HIREDATE BETWEEN 1987-01-01 AND 1987-12-31
The BETWEEN keyword is inclusive. A more complex, but explicit, search condition that produces the
same result is:
... WHERE HIREDATE >= 1987-01-01 AND HIREDATE <= 1987-12-31
v IN says you are interested in rows in which the value of the specified expression is among the values
you listed. For example, to find the names of all employees in departments A00, C01, and E21, you can
specify:
... WHERE WORKDEPT IN (A00, C01, E21)
v EXISTS says you are interested in testing for the existence of certain rows. For example, to find out if
there are any employees that have a salary greater than 60000, you can specify:
EXISTS (SELECT * FROM EMPLOYEE WHERE SALARY > 60000)
v IS NULL says that you are interested in testing for null values. For example, to find out if there are
any employees without a phone listing, you can specify:
... WHERE EMPLOYEE.PHONE IS NULL
70
v LIKE says you are interested in rows in which an expression is similar to the value you supply. When
you use LIKE, SQL searches for a character string similar to the one you specify. The degree of
similarity is determined by two special characters used in the string that you include in the search
condition:
_
An underline character stands for any single character.
A percent sign stands for an unknown string of 0 or more characters. If the percent sign starts
the search string, then SQL allows 0 or more character(s) to precede the matching value in the
column. Otherwise, the search string must begin in the first position of the column.
Note: If you are operating on MIXED data, the following distinction applies: an SBCS underline
character refers to one SBCS character. No such restriction applies to the percent sign; that is, a
percent sign refers to any number of SBCS or DBCS characters. See the DB2 for i SQL reference
topic collection for more information about the LIKE predicate and MIXED data.
Use the underline character or percent sign either when you do not know or do not care about all the
characters of the column's value. For example, to find out which employees live in Minneapolis, you
can specify:
... WHERE ADDRESS LIKE %MINNEAPOLIS%
SQL returns any row with the string MINNEAPOLIS in the ADDRESS column, no matter where the
string occurs.
In another example, to list the towns whose names begin with 'SAN', you can specify:
... WHERE TOWN LIKE SAN%
If you want to find any addresses where the street name isn't in your master street name list, you can
use an expression in the LIKE expression. In this example, the STREET column in the table is assumed
to be upper case.
... WHERE UCASE (:address_variable) NOT LIKE %||STREET||%
If you want to search for a character string that contains either the underscore or percent character, use
the ESCAPE clause to specify an escape character. For example, to see all businesses that have a
percent in their name, you can specify:
... WHERE BUSINESS_NAME LIKE %@%% ESCAPE @
The first and last percent characters in the LIKE string are interpreted as the normal LIKE percent
characters. The combination '@%' is taken as the actual percent character.
Related concepts:
Using subqueries on page 120
Related reference:
Specifying a search condition using the WHERE clause on page 57
update, or delete.
Expressions in the WHERE clause on page 58
else.
Predicates
Special considerations for LIKE:
Here are some considerations for using the LIKE predicate.
SQL programming
71
v When host variables are used in place of string constants in a search pattern, you should consider
using varying length host variables. This allows you to:
Assign previously used string constants to host variables without any changes.
Obtain the same selection criteria and results as if a string constant were used.
v When fixed-length host variables are used in place of string constants in a search pattern, you should
ensure that the value specified in the host variable matches the pattern previously used by the string
constants. All characters in a host variable that are not assigned a value are initialized with a blank.
For example, if you do a search using the string pattern 'ABC%' in a varying length host variable, these
are some of the values that can be returned:
ABCD
ABCDE
ABCxxx
ABC
However, if you do a search using the search pattern 'ABC%' contained in a host variable with a fixed
length of 10, these values can be returned, assuming that the column has a length of 12:
ABCDE
ABCD
ABCxxx
ABC
Note: All returned values start with 'ABC' and end with at least 6 blanks. Blanks are used because the
last 6 characters in the host variable are not assigned a specific value.
If you want to do a search using a fixed-length host variable where the last 7 characters can be
anything, search for 'ABC%%%%%%%'. These are some of the values that can be returned:
ABCDEFGHIJ
ABCXXXXXXX
ABCDE
ABCDD
Multiple search conditions within a WHERE clause:

You can qualify your request further by coding a search condition that includes several predicates.
The search condition you specify can contain any of the comparison operators or the predicates
BETWEEN, DISTINCT, IN, LIKE, EXISTS, IS NULL, and IS NOT NULL.
You can combine any two predicates with AND and OR. In addition, you can use the NOT keyword to
specify that the search condition that you want is the negated value of the specified search condition. A
WHERE clause can have as many predicates as you want.
v AND says that, for a row to qualify, the row must satisfy both predicates of the search condition. For
example, to find out which employees in department D21 were hired after December 31, 1987, specify:
...
WHERE WORKDEPT = D21 AND HIREDATE > 1987-12-31
v OR says that, for a row to qualify, the row can satisfy the condition set by either or both predicates of
the search condition. For example, to find out which employees are in either department C01 or D11,
you can specify :
...
WHERE WORKDEPT = C01 OR WORKDEPT = D11
Note: You can also use IN to specify this request: WHERE WORKDEPT IN (C01, D11).
v NOT says that, to qualify, a row must not meet the criteria set by the search condition or predicate that
follows the NOT. For example, to find all employees in the department E11 except those with a job
code equal to analyst, you can specify:
...
WHERE WORKDEPT = E11 AND NOT JOB = ANALYST
When SQL evaluates search conditions that contain these connectors, it does so in a specific order. SQL
first evaluates the NOT clauses, next evaluates the AND clauses, and then the OR clauses.
You can change the order of evaluation by using parentheses. The search conditions enclosed in
parentheses are evaluated first. For example, to select all employees in departments E11 and E21 who
have education levels greater than 12, you can specify:
72
...
WHERE EDLEVEL > 12 AND
(WORKDEPT = E11 OR WORKDEPT = E21)
The parentheses determine the meaning of the search condition. In this example, you want all rows that
have a:
v WORKDEPT value of E11 or E21, and
v EDLEVEL value greater than 12
If you did not use parentheses:
...
WHERE EDLEVEL > 12 AND WORKDEPT = E11
OR WORKDEPT = E21
Your result is different. The selected rows are rows that have:
v WORKDEPT = E11 and EDLEVEL > 12, or
v WORKDEPT = E21, regardless of the EDLEVEL value
If you are combining multiple equal comparisons, you can write the predicate with the ANDs as shown
in the following example:
...
WHERE WORKDEPT = E11 AND EDLEVEL = 12 AND JOB = CLERK
You can also compare two lists, for example:

...
WHERE (WORKDEPT, EDLEVEL, JOB) = (E11, 12, CLERK)
When two lists are used, the first item in the first list is compared to the first item in the second list, and
so on through both lists. Thus, each list must contain the same number of entries. Using lists is identical
to writing the query with AND. Lists can only be used with the equal and not equal comparison
operators.
Related reference:
update, or delete.
Using OLAP specifications

Online analytical processing (OLAP) specifications are used to return ranking numbers and row numbers
for the result rows of a query. You can specify RANK, DENSE_RANK, and ROW_NUMBER.
Example: Ranking and row numbering

Suppose that you want a list of the top 10 salaries along with their ranking. The following query
generates the ranking number for you:
SELECT EMPNO, SALARY,
RANK() OVER(ORDER BY SALARY DESC),
DENSE_RANK() OVER(ORDER BY SALARY DESC),
ROW_NUMBER() OVER(ORDER BY SALARY DESC)
FROM EMPLOYEE
FETCH FIRST 10 ROWS ONLY
This query returns the following information.
SQL programming
73
Table 12. Results of the previous query

EMPNO
SALARY
RANK
DENSE_RANK
ROW_NUMBER
000010
52,750.00
000110
46,500.00
200010
46,500.00
000020
41,250.00
000050
40,175.00
000030
38,250.00
000070
36,170.00
000060
32,250.00
000220
29,840.00
200220
29,840.00
10
In this example, the SALARY descending order with the top 10 returned. The RANK column shows the
relative ranking of each salary. Notice that there are two rows with the same salary at position 2. Each of
those rows is assigned the same rank value. The following row is assigned the value of 4. RANK returns
a value for a row that is one more than the total number of rows that precede that row. There are gaps in
the numbering sequence whenever there are duplicates.
In contrast, the DENSE_RANK column shows a value of 3 for the row directly after the duplicate rows.
DENSE_RANK returns a value for a row that is one more than the number of distinct row values that
precede it. There will never be gaps in the numbering sequence.
ROW_NUMBER returns a unique number for each row. For rows that contain duplicate values according
to the specified ordering, the assignment of a row number is arbitrary; the row numbers could be
assigned in a different order for the duplicate rows when the query is run another time.
Example: Ranking groups

Suppose that you want to find out which department has the highest average salary. The following query
groups the data by department, determines the average salary for each department, and ranks the
resulting averages.
SELECT WORKDEPT, INT(AVG(SALARY)) AS AVERAGE,
RANK() OVER(ORDER BY AVG(SALARY) DESC) AS AVG_SALARY
FROM EMPLOYEE
GROUP BY WORKDEPT

Table 13. Results of previous query
WORKDEPT
AVERAGE
AVG_SALARY
B01
41,250
A00
40,850
E01
40,175
C01
29,722
D21
25,668
D11
25,147
E21
24,086
E11
21,020
74
Example: Ranking within a department

Suppose that you want a list of employees along with how their bonus ranks within their department.
Using the PARTITION BY clause, you can specify groups that are to be numbered separately.
SELECT LASTNAME, WORKDEPT, BONUS,
DENSE_RANK() OVER(PARTITION BY WORKDEPT ORDER BY BONUS DESC)
AS BONUS_RANK_IN_DEPT
FROM EMPLOYEE
WHERE WORKDEPT LIKE E%

LASTNAME
WORKDEPT
BONUS
BONUS_RANK_in_DEPT
GEYER
E01
800.00
HENDERSON
E11
600.00
SCHNEIDER
E11
500.00
SCHWARTZ
E11
500.00
SMITH
E11
400.00
PARKER
E11
300.00
SETRIGHT
E11
300.00
SPRINGER
E11
300.00
SPENSER
E21
500.00
LEE
E21
500.00
GOUNOT
E21
500.00
WONG
E21
500.00
ALONZO
E21
500.00
MENTA
E21
400.00
Example: Ranking and ordering by table expression results

Suppose that you want to find the top five employees whose salaries are the highest along with their
department names. The department name is in the department table, so a join operation is needed.
Because ordering is already being done in the nested table expression, that ordering can also be used for
determining the ROW_NUMBER value. The ORDER BY ORDER OF table clause is used to do this.
SELECT ROW_NUMBER() OVER(ORDER BY ORDER OF EMP),
EMPNO, SALARY, DEPTNO, DEPTNAME
FROM (SELECT EMPNO, WORKDEPT, SALARY
FROM EMPLOYEE
ORDER BY SALARY DESC
FETCH FIRST 5 ROWS ONLY) EMP,
DEPARTMENT
WHERE DEPTNO = WORKDEPT

ROW_NUMBER
EMPNO
SALARY
DEPTNO
DEPTNAME
000010
52,750.00
A00
SPIFFY COMPUTER
SERVICE DIV.
SQL programming
75
Table 15. Results of the previous query (continued)

ROW_NUMBER
EMPNO
SALARY
DEPTNO
DEPTNAME
000110
46,500.00
A00
SPIFFY COMPUTER
SERVICE DIV.
200010
46,500.00
A00
SPIFFY COMPUTER
SERVICE DIV.
000020
41,250.00
B01
PLANNING
000050
40,175.00
E01
SUPPORT SERVICES
Joining data from more than one table

Sometimes the information you want to see is not in a single table. To form a row of the result table, you
might want to retrieve some column values from one table and some column values from another table.
You can retrieve and join column values from two or more tables into a single row.
Several different types of joins are supported by DB2 for i: inner join, left outer join, right outer join, left
exception join, right exception join, and cross join.
Usage notes on join operations

When you join two or more tables, consider the following items:
v If there are common column names, you must qualify each common name with the name of the table
(or a correlation name). Column names that are unique do not need to be qualified. However, the
USING clause can be used in a join to allow you to identify columns that exist in both tables without
specifying table names.
v If you do not list the column names you want, but instead use SELECT *, SQL returns rows that
consist of all the columns of the first table, followed by all the columns of the second table, and so on.
v You must be authorized to select rows from each table or view specified in the FROM clause.
v The sort sequence is applied to all character, or UCS-2 or UTF-16 graphic columns being joined.
Inner join:
An inner join returns only the rows from each table that have matching values in the join columns. Any
rows that do not have a match between the tables do not appear in the result table.
With an inner join, column values from one row of a table are combined with column values from
another row of another (or the same) table to form a single row of data. SQL examines both tables
specified for the join to retrieve data from all the rows that meet the search condition for the join. There
are two ways of specifying an inner join: using the JOIN syntax, and using the WHERE clause.
Suppose you want to retrieve the employee numbers, names, and project numbers for all employees that
are responsible for a project. In other words, you want the EMPNO and LASTNAME columns from the
CORPDATA.EMPLOYEE table and the PROJNO column from the CORPDATA.PROJECT table. Only
employees with last names starting with 'S' or later should be considered. To find this information, you
need to join the two tables.
Inner join using the JOIN syntax:
To use the inner join syntax, both of the tables you are joining are listed in the FROM clause, along with
the join condition that applies to the tables.
The join condition is specified after the ON keyword and determines how the two tables are to be
compared to each other to produce the join result. The condition can be any comparison operator; it does
not need to be the equal operator. Multiple join conditions can be specified in the ON clause separated by
76
the AND keyword. Any additional conditions that do not relate to the actual join are specified in either
the WHERE clause or as part of the actual join in the ON clause.
SELECT EMPNO, LASTNAME, PROJNO
FROM CORPDATA.EMPLOYEE INNER JOIN CORPDATA.PROJECT
ON EMPNO = RESPEMP
WHERE LASTNAME > S
In this example, the join is done on the two tables using the EMPNO and RESPEMP columns from the
tables. Since only employees that have last names starting with at least 'S' are to be returned, this
additional condition is provided in the WHERE clause.
This query returns the following output.
EMPNO
LASTNAME
PROJNO
000250
SMITH
AD3112
000060
STERN
MA2110
000100
SPENSER
OP2010
000020
THOMPSON
PL2100
Inner join using the WHERE clause:

To use the WHERE clause to perform the same join as you perform using the INNER JOIN syntax, enter
both the join condition and the additional selection condition in the WHERE clause.
The tables to be joined are listed in the FROM clause, separated by commas.
FROM CORPDATA.EMPLOYEE, CORPDATA.PROJECT
WHERE EMPNO = RESPEMP
AND LASTNAME > S
This query returns the same output as the previous example.

Joining data with the USING clause:
You can use the USING clause for a shorthand way of defining join conditions. The USING clause is
equivalent to a join condition where each column from the left table is compared to a column with the
same name in the right table.
For example, look at the USING clause in this statement:
SELECT EMPNO, ACSTDATE
FROM CORPDATA.PROJACT INNER JOIN CORPDATA.EMPPROJACT
USING (PROJNO, ACTNO)
WHERE ACSDATE > 1982-12-31;
The syntax in this statement is valid and equivalent to the join condition in the following statement:
SELECT EMPNO, ACSTDATE
FROM CORPDATA.PROJACT INNER JOIN CORPDATA.EMPPROJACT
ON CORPDATA.PROJACT.PROJNO = CORPDATA.EMPPROJACT.PROJNO AND
CORPDATA.PROJACT.ACTNO = CORPDATA.EMPPROJACT.ACTNO
WHERE ACSTDATE > 1982-12-31;
Left outer join:

A left outer join returns all the rows that an inner join returns plus one row for each of the other rows in
the first table that do not have a match in the second table.
SQL programming
77
Suppose you want to find all employees and the projects they are currently responsible for. You want to
see those employees that are not currently in charge of a project as well. The following query will return
a list of all employees whose names are greater than 'S', along with their assigned project numbers.
FROM CORPDATA.EMPLOYEE LEFT OUTER JOIN CORPDATA.PROJECT
ON EMPNO = RESPEMP
WHERE LASTNAME > S
The result of this query contains some employees that do not have a project number. They are listed in
the query, but have the null value returned for their project number.
EMPNO
LASTNAME
PROJNO
000020
THOMPSON
PL2100
000060
STERN
MA2110
000100
SPENSER
OP2010
000170
YOSHIMURA
000180
SCOUTTEN
000190
WALKER
000250
SMITH
AD3112
000280
SCHNEIDER
000300
SMITH
000310
SETRIGHT
200170
YAMAMOTO
200280
SCHWARTZ
200310
SPRINGER
200330
WONG
Note: Using the RRN scalar function to return the relative record number for a column in the table on
the right in a left outer join or exception join will return a value of 0 for the unmatched rows.
Right outer join:
A right outer join returns all the rows that an inner join returns plus one row for each of the other rows
in the second table that do not have a match in the first table. It is the same as a left outer join with the
tables specified in the opposite order.
The query that was used as the left outer join example can be rewritten as a right outer join as follows:
FROM CORPDATA.PROJECT RIGHT OUTER JOIN CORPDATA.EMPLOYEE
ON EMPNO = RESPEMP
WHERE LASTNAME > S
The results of this query are identical to the results from the left outer join query.
Exception join:
A left exception join returns only the rows from the first table that do not have a match in the second
table.
Using the same tables as before, return those employees that are not responsible for any projects.
78

FROM CORPDATA.EMPLOYEE EXCEPTION JOIN CORPDATA.PROJECT
ON EMPNO = RESPEMP
WHERE LASTNAME > S
This join returns the following output.

EMPNO
LASTNAME
PROJNO
000170
YOSHIMURA
000180
SCOUTTEN
000190
WALKER
000280
SCHNEIDER
000300
SMITH
000310
SETRIGHT
200170
YAMAMOTO
200280
SCHWARTZ
200310
SPRINGER
200330
WONG
An exception join can also be written as a subquery using the NOT EXISTS predicate. The previous query
can be rewritten in the following way:
SELECT EMPNO, LASTNAME
WHERE LASTNAME > S
AND NOT EXISTS
(SELECT * FROM CORPDATA.PROJECT
WHERE EMPNO = RESPEMP)
The only difference in this query is that it cannot return values from the PROJECT table.
There is a right exception join, too, that works just like a left exception join but with the tables reversed.
Cross join:
A cross join, also known as a Cartesian Product join, returns a result table where each row from the first
table is combined with each row from the second table.
The number of rows in the result table is the product of the number of rows in each table. If the tables
involved are large, this join can take a very long time.
A cross join can be specified in two ways: using the JOIN syntax or by listing the tables in the FROM
clause separated by commas without using a WHERE clause to supply join criteria.
Suppose that the following tables exist.
Table 16. Table A
ACOL1
ACOL2
A1
AA1
A2
AA2
A3
AA3
SQL programming
79
Table 17. Table B

BCOL1
BCOL2
B1
BB1
B2
BB2
The following two select statements produce identical results.

SELECT * FROM A CROSS JOIN B
SELECT * FROM A, B
The result table for either of these SELECT statements looks like this.
ACOL1
ACOL2
BCOL1
BCOL2
A1
AA1
B1
BB1
A1
AA1
B2
BB2
A2
AA2
B1
BB1
A2
AA2
B2
BB2
A3
AA3
B1
BB1
A3
AA3
B2
BB2
Full outer join:

Like the left and right outer joins, a full outer join returns matching rows from both tables. However, a
full outer join also returns nonmatching rows from both tables.
Suppose that you want to find all employees and all of their projects. You want to see those employees
that are not currently in charge of a project as well as any projects that do not have an employee
assigned. The following query returns a list of all employees whose names are greater than 'S', along with
their assigned project numbers:
FROM CORPDATA.EMPLOYEE FULL OUTER JOIN CORPDATA.PROJECT
ON EMPNO = RESPEMP
WHERE LASTNAME > S
Because there are no projects without an assigned employee, the query returns the same rows as a left
outer join. Here are the results.
EMPNO
LASTNAME
PROJNO
000020
THOMPSON
PL2100
000060
STERN
MA2110
000100
SPENSER
OP2010
000170
YOSHIMURA
000180
SCOUTTEN
000190
WALKER
000250
SMITH
AD3112
000280
SCHNEIDER
000300
SMITH
000310
SETRIGHT
200170
YAMAMOTO
80
EMPNO
LASTNAME
PROJNO
200280
SCHWARTZ
200310
SPRINGER
200330
WONG
Multiple join types in one statement:

Sometimes you need to join more than two tables to produce the result that you want.
If you want to return all the employees, their department names, and the projects they are responsible
for, if any, you need to join the EMPLOYEE table, the DEPARTMENT table, and the PROJECT table to get
the information. The following example shows the query and the results:
SELECT EMPNO, LASTNAME, DEPTNAME, PROJNO
FROM CORPDATA.EMPLOYEE INNER JOIN CORPDATA.DEPARTMENT
ON WORKDEPT = DEPTNO
LEFT OUTER JOIN CORPDATA.PROJECT
ON EMPNO = RESPEMP
WHERE LASTNAME > S
EMPNO
LASTNAME
DEPTNAME
PROJNO
000020
THOMPSON
PLANNING
PL2100
000060
STERN
MANUFACTURING SYSTEMS
MA2110
000100
SPENSER
SOFTWARE SUPPORT
OP2010
000170
YOSHIMURA
000180
SCOUTTEN
000190
WALKER
000250
SMITH
ADMINISTRATION SYSTEMS
AD3112
000280
SCHNEIDER
OPERATIONS
000300
SMITH
OPERATIONS
000310
SETRIGHT
OPERATIONS
Using table expressions

You can use table expressions to specify an intermediate result table.
Table expressions can be used in place of a view to avoid creating the view when general use of the view
is not required. Table expressions consist of nested table expressions (also called derived tables) and
common table expressions.
Nested table expressions are specified within parentheses in the FROM clause. For example, suppose you
want a result table that shows the manager number, department number, and maximum salary for each
department. The manager number is in the DEPARTMENT table, the department number is in both the
DEPARTMENT and EMPLOYEE tables, and the salaries are in the EMPLOYEE table. You can use a table
expression in the FROM clause to select the maximum salary for each department. You can also add a
correlation name, T2, following the nested table expression to name the derived table. The outer select
then uses T2 to qualify columns that are selected from the derived table, in this case MAXSAL and
WORKDEPT. Note that the MAX(SALARY) column selected in the nested table expression must be
named in order to be referenced in the outer select. The AS clause is used to do that.
SELECT MGRNO, T1.DEPTNO, MAXSAL
FROM CORPDATA.DEPARTMENT T1,
(SELECT MAX(SALARY) AS MAXSAL, WORKDEPT
SQL programming
81
FROM CORPDATA.EMPLOYEE E1
GROUP BY WORKDEPT) T2
WHERE T1.DEPTNO = T2.WORKDEPT
ORDER BY DEPTNO
The result of the query follows.

MGRNO
DEPTNO
MAXSAL
000010
A00
52750.00
000020
B01
41250.00
000030
C01
38250.00
000060
D11
32250.00
000070
D21
36170.00
000050
E01
40175.00
000090
E11
29750.00
000100
E21
26150.00
Common table expressions can be specified before the full-select in a SELECT statement, an INSERT
statement, or a CREATE VIEW statement. They can be used when the same result table needs to be
shared in a full-select. Common table expressions are preceded with the keyword WITH.
For example, suppose you want a table that shows the minimum and maximum of the average salary of
a certain set of departments. The first character of the department number has some meaning and you
want to get the minimum and maximum for those departments that start with the letter 'D' and those
that start with the letter 'E'. You can use a common table expression to select the average salary for each
department. Again, you must name the derived table; in this case, the name is DT. You can then specify a
SELECT statement using a WHERE clause to restrict the selection to only the departments that begin with
a certain letter. Specify the minimum and maximum of column AVGSAL from the derived table DT.
Specify a UNION to get the results for the letter 'E' and the results for the letter 'D'.
WITH DT AS (SELECT E.WORKDEPT AS DEPTNO, AVG(SALARY) AS AVGSAL
FROM CORPDATA.DEPARTMENT D , CORPDATA.EMPLOYEE E
WHERE D.DEPTNO = E.WORKDEPT
GROUP BY E.WORKDEPT)
SELECT E, MAX(AVGSAL), MIN(AVGSAL) FROM DT
WHERE DEPTNO LIKE E%
UNION
SELECT D, MAX(AVGSAL), MIN(AVGSAL) FROM DT
WHERE DEPTNO LIKE D%
The result of the query follows.

MAX(AVGSAL)
MIN(AVGSAL)
40175.00
21020.00
25668.57
25147.27
Suppose that you want to write a query against your ordering database that will return the top 5 items
(in total quantity ordered) within the last 1000 orders from customers who also ordered item 'XXX'.
WITH X AS (SELECT ORDER_ID, CUST_ID
FROM ORDERS
ORDER BY ORD_DATE DESC
FETCH FIRST 1000 ROWS ONLY),
Y AS (SELECT CUST_ID, LINE_ID, ORDER_QTY
FROM X, ORDERLINE
WHERE X.ORDER_ID = ORDERLINE.ORDER_ID)
82
SELECT LINE_ID
FROM (SELECT LINE_ID
FROM Y
WHERE Y.CUST_ID IN (SELECT DISTINCT CUST_ID
FROM Y
WHERE LINE.ID = XXX )
GROUP BY LINE_ID
ORDER BY SUM(ORDER_QTY) DESC)
FETCH FIRST 5 ROWS ONLY
The first common table expression (X) returns the most recent 1000 order numbers. The result is ordered
by the date in descending order and then only the first 1000 of those ordered rows are returned as the
result table.
The second common table expression (Y) joins the most recent 1000 orders with the line item table and
returns (for each of the 1000 orders) the customer, line item, and quantity of the line item for that order.
The derived table in the main select statement returns the line items for the customers who are in the top
1000 orders who ordered item XXX. The results for all customers who ordered XXX are then grouped by
the line item and the groups are ordered by the total quantity of the line item.
Finally, the outer select selects only the first 5 rows from the ordered list that the derived table returned.
Using recursive queries

|
|
Some applications work with data that is recursive in nature. To query this type of data, you can use a
hierarchical query or a recursive common table expression.
One example of recursive data is a Bill of Materials (BOM) application that works with the expansion of
parts and its component subparts. For example, a chair might be made of a seat unit and a leg assembly.
The seat unit might consist of a seat and two arms. Each of these parts can be further broken down into
its subparts until there is a list of all the parts needed to build a chair.
|
|
|
|
DB2 for i provides two ways of defining a recursive query. The first one is called a hierarchical query
which uses the CONNECT BY clause to define how a parent row is to be associated with its child rows.
The second method is to use a recursive common table expression. This uses a common table expression
to define the first, or seed, rows and then uses a UNION to define how the child rows are determined.
|
|
|
|
Each of these methods of defining a recursive query has advantages and disadvantages. The CONNECT
BY syntax is much simpler to understand, but has fewer ways to derive the data in its query. CONNECT
BY can be specified in any subselect anywhere in a query. A recursive common table expression has more
options for how the union is defined to generate the child rows.
|
|
|
|
|
|
|
|
|
There are a couple of behavioral differences between a connect by recursive query and a recursive
common table expression query. First, they differ in how they handle cyclic data. This difference is
discussed in the examples. Second, connect by allows a sort among siblings. This is also shown in the
examples. Finally, the two implementations differ in how the data is put on a queue that is used to
implement the recursion. By default a recursive common table expression's data tends to come out in
breadth first order, first in first out. With connect by, the order is designed to come out depth first. This
means that rows in a recursive step immediately follow their parent row. The recursive common table
expression syntax gives you a choice of depth or breadth first hierarchical order by adding the SEARCH
clause. The connect by syntax is always depth first.
In the trip planner examples for these recursive methods, airline flights and train connections are used to
find transportation paths between cities. The following table definitions and data are used in the
examples.
SQL programming
83
CREATE TABLE FLIGHTS (DEPARTURE CHAR(20),

ARRIVAL CHAR(20),
CARRIER CHAR(15),
FLIGHT_NUMBER CHAR(5),
PRICE INT);
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
FLIGHTS
VALUES(New York, Paris, Atlantic, 234, 400);

VALUES(Chicago, Miami, NA Air, 2334, 300);
VALUES(New York, London, Atlantic, 5473, 350);
VALUES(London, Athens , Mediterranean, 247, 340);
VALUES(Athens, Nicosia , Mediterranean, 2356, 280);
VALUES(Paris, Madrid , Euro Air, 3256, 380);
VALUES(Paris, Cairo , Euro Air, 63, 480);
VALUES(Chicago, Frankfurt, Atlantic, 37, 480);
VALUES(Frankfurt, Moscow, Asia Air, 2337, 580);
VALUES(Frankfurt, Beijing, Asia Air, 77, 480);
VALUES(Moscow, Tokyo, Asia Air, 437, 680);
VALUES(Frankfurt, Vienna, Euro Air, 59, 200);
VALUES(Paris, Rome, Euro Air, 534, 340);
VALUES(Miami, Lima, SA Air, 5234, 530);
VALUES(New York, Los Angeles, NA Air, 84, 330);
VALUES(Los Angeles, Tokyo, Pacific Air, 824, 530);
VALUES(Tokyo, Hawaii, Asia Air, 94, 330);
VALUES(Washington, Toronto, NA Air, 104, 250);
CREATE TABLE TRAINS(DEPARTURE CHAR(20),

ARRIVAL CHAR(20),
RAILLINE CHAR(15),
TRAIN CHAR(5),
PRICE INT);
INSERT INTO TRAINS VALUES(Chicago, Washington, UsTrack, 323, 90;
INSERT INTO TRAINS VALUES(Madrid, Barcelona, EuroTrack, 5234, 60);
INSERT INTO TRAINS VALUES(Washington , Boston , UsTrack, 232, 50);
CREATE TABLE FLIGHTSTATS(FLIGHT# CHAR(5),
ON_TIME_PERCENT DECIMAL(5,2),
CANCEL_PERCENT DECIMAL(5,2));
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INSERT
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
INTO
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
FLIGHTSTATS
VALUES(234, 85.0, 0.20);

VALUES(2334, 92.0, 0.10);
VALUES(5473, 86.2, 0.10);
VALUES(247, 91.0, 0.10);
VALUES(2356, 91.0, 0.10);
VALUES(3256, 92.0 , 0.10);
VALUES(63, 90.5 , 0.10);
VALUES(37, 87.0 , 0.20);
VALUES(2337, 80.0, 0.20);
VALUES(77, 86.0, 0.10);
VALUES(437, 81.0, 0.10);
VALUES(59, 85.0, 01.0);
VALUES(534, 87.0 , 01.0);
VALUES(5234, 88.0, 0.20);
VALUES(84, 88.0, 0.1);
VALUES(824, 93.0, 0.10);
VALUES(94, 92.0, 0.10);
VALUES(104, 93.0, 0.10);
| Using connect by hierarchical queries

| Suppose you want to find out what cities you can fly to if you start in Chicago, and how many separate
| flights it will take to get there. The following query shows you that information.
84
|
|
|
|
SELECT CONNECT_BY_ROOT departure AS origin, departure, arrival, LEVEL AS flight_count

FROM flights
START WITH departure = Chicago
CONNECT BY PRIOR arrival = departure
ORIGIN
DEPARTURE
ARRIVAL
FLIGHT_COUNT
Chicago
Chicago
Miami
Chicago
Miami
Lima
Chicago
Chicago
Frankfurt
Chicago
Frankfurt
Vienna
Chicago
Frankfurt
Beijing
Chicago
Frankfurt
Moscow
Chicago
Moscow
Tokyo
|
|
Chicago
Tokyo
Hawaii
|
|
|
|
|
|
|
|
|
There are several parts to this hierarchical query. There is an initial selection which defines the initial seed
for the recursion. In this case, it is the rows from the flights table that START WITH a departure from
Chicago'. The CONNECT BY clause is used to define how the rows that have already been generated are
to be 'connected' to generate more rows for subsequent iterations of the query. The PRIOR unary operator
tells DB2 how to select a new row based on the results of the previous row. The recursive join column
(typically one column but could have several) selected by the result of the START WITH clause is
referenced by the PRIOR keyword. This means that the previous row's ARRIVAL city becomes the new
row's PRIOR value for the DEPARTURE city. This is encapsulated in the clause CONNECT BY PRIOR
arrival = departure.
|
|
|
|
|
|
There are two other connect by features illustrated in this example query. The unary operator
CONNECT_BY_ROOT is used to define a fixed expression value that is determined in the initialization
step and is the same for all the generated recursive result rows. Typically, it is your starting value for that
particular iteration as you might have multiple START WITH values. In this query, it defines in the result
set the ORIGIN of the different destination options from Chicago. If the START WITH clause selected
multiple cities, ORIGIN would indicate which city a row used as its start value.
|
|
|
LEVEL is one of three pseudo columns available when using connect by recursion. The value of LEVEL
reflects the recursion level of the current row. In this example, LEVEL also reflects the number of flights it
would take to get from the city of ORIGIN (Chicago) to the different ARRIVAL cities.
|
|
|
|
|
|
A hierarchical query is run just like its equivalent recursive common table expression query and generates
the same result set. See Using recursive common table expressions and recursive views on page 90. The
only difference is in the order of the returned rows. The connect by query returns the rows in depth first
order; every row of the result set immediately follows its parent row. The recursive common table
expression query returns the rows in breadth first order; all the rows for one level are returned, then all
the rows that were generated from the previous level are returned.
Example: Two tables used for recursion using CONNECT BY
|
|
Now, suppose you start in Chicago but want to add in transportation options by rail in addition to flights
and you want to know which cities you can get to and how many connections it would take.
|
|
The following connect by query returns that information. Note that in the corresponding recursive
common table expression example, Example: Two tables used for recursion using recursive common
SQL programming
85
|
|
|
|
|
|
|
|
|
|
|
table expressions on page 92, we can also distinguish between the number of rail vs number of airline
connections and sum the ongoing ticket cost of the connections to that destination. Those calculations are
examples of derivations allowed using the more complex but more flexible recursive common table
expression syntax. That capability is not available when using the connect by syntax.
SELECT CONNECT_BY_ROOT departure AS departure, arrival, LEVEL - 1 connections
FROM
( SELECT departure, arrival FROM flights
UNION
SELECT departure, arrival FROM trains) t
START WITH departure = Chicago
CONNECT BY PRIOR arrival = departure;
| This query returns the following information.

|
DEPARTURE
ARRIVAL
CONNECTIONS
Chicago
Miami
Chicago
Lima
Chicago
Frankfurt
Chicago
Vienna
Chicago
Beijing
Chicago
Moscow
Chicago
Tokyo
Chicago
Hawaii
Chicago
Washington
Chicago
Boston
|
|
Chicago
Toronto
| In this example, there are two data sources feeding the recursion, a list of flights and a list of trains. In
| the final results, you see how many connections are needed to travel between the cities.
| Example: Sibling ordering using CONNECT BY
|
|
|
|
|
|
|
|
|
|
|
One of the drawbacks of recursive common table expressions is that you cannot order the results among
siblings based on a particular column value. You can do this with connect by. For example, if you want to
output destinations from New York but you also want to order your hierarchical data among siblings by
a certain value, such as the cost of a ticket to that destination, you can do that by specifying the ORDER
SIBLINGS BY clause.
SELECT CONNECT_BY_ROOT departure AS origin, departure, arrival,
LEVEL level, price ticket_price
FROM flights
START WITH departure = New York
CONNECT BY PRIOR arrival = departure
ORDER SIBLINGS BY price ASC

|
ORIGIN
DEPARTURE
ARRIVAL
LEVEL
TICKET_PRICE
New York
New York
LA
330
New York
LA
Tokyo
530
New York
Tokyo
Hawaii
330
86
ORIGIN
DEPARTURE
ARRIVAL
LEVEL
TICKET_PRICE
New York
New York
London
350
New York
London
Athens
340
New York
Athens
Nicosia
280
New York
New York
Paris
400
New York
Paris
Rome
340
New York
Paris
Madrid
380
|
|
New York
Paris
Cairo
480
|
|
|
|
|
|
The result table shows all the destinations possible from the origin city of New York. All sibling
destinations (those destinations that originate from the same departure city) are output sorted by ticket
price. For example, the destinations from Paris are Rome, Madrid and Cairo; they are output ordered by
ascending ticket price. Note that the output shows New York to LA as the first destination directly from
New York because it has a less expensive ticket price (330) than did the direct connects to London or
Paris which are 350 and 400 respectively.
Example: Cyclic data checks using CONNECT BY
|
|
|
|
The key to any recursive process, whether is it a recursive program or a recursive query, is that the
recursion must be finite. If not, you will get into a never ending loop. CONNECT BY is unlike recursive
common table expressions in that it always checks for infinite recursion and terminates that cycle
automatically so you never have to worry about a runaway query.
|
|
By default, if connect by encounters cyclic data, it will issue an SQL error, SQ20451: Cycle detected in
hierarchical query. This error causes termination of the query so no results are returned.
|
|
If you want results back and just want the infinite cycle to stop, you can specify the NOCYCLE keyword
on the CONNECT BY clause. This means no error will be issued for cyclic data.
|
|
Using the NOCYCLE option along with the CONNECT_BY_ISCYCLE pseudo column is a way you can
find cyclic data and correct the data if desired.
|
|
|
Inserting the following row into the FLIGHTS table results in potentially infinite recursion since Paris
goes to Cairo and Cairo goes to Paris.
|
|
|
|
|
|
|
|
|
|
The following query illustrates the tolerance of the cyclic data by specifying NOCYCLE. In addition, the
CONNECT_BY_ISCYCLE pseudo column is used to identify cyclic rows and the function
SYS_CONNECT_BY_PATH is used to build an Itinerary string of all the connection cities leading up to
the destination. SYS_CONNECT_BY_PATH is implemented as a CLOB data type so you have a large
result column to reflect deep recursions.
INSERT INTO flights VALUES (Cairo, Paris, Atlantic, 1134, 440);
SELECT CONNECT_BY_ROOT departure AS origin, arrival,

SYS_CONNECT_BY_PATH(TRIM(arrival), : ) itinerary, CONNECT_BY_ISCYCLE cyclic
FROM flights
CONNECT BY NOCYCLE PRIOR arrival = departure;
SQL programming
87
ORIGIN
ARRIVAL
ITINERARY
CYCLIC
New York
Paris
: Paris
New York
Rome
: Paris : Rome
New York
Cairo
: Paris : Cairo
New York
Paris
: Paris : Cairo : Paris
New York
Madrid
: Paris : Madrid
New York
London
: London
New York
Athens
: London : Athens
New York
Nicosia
: London : Athens : Nicosia
New York
LA
: LA
New York
Tokyo
: LA : Tokyo
|
|
New York
Hawaii
: LA : Tokyo : Hawaii
| Note that the result set row that reflects cyclic data often depends on where you start in the cycle with
| the START WITH clause.
| Example: Pseudo column CONNECT_BY_ISLEAF in CONNECT BY
| There may be times when processing recursive data that you may want to know which rows result in no
| further recursion. In other words, which rows are leaf rows or have no children in the hierarchy.
|
|
|
|
|
|
|
|
|
In the following query, you can find out which destinations are final destinations; in other words, which
destinations have no outbound flights. The CONNECT_BY_ISLEAF pseudo column will be 0 if it is not a
leaf and 1 if it is. You can also specify CONNECT_BY_ISLEAF in a WHERE predicate to see only leaf
rows.
SELECT CONNECT_BY_ROOT departure AS origin, arrival,
SYS_CONNECT_BY_PATH(TRIM(arrival), : ) itinerary, CONNECT_BY_ISLEAF leaf
FROM flights

|
ORIGIN
ARRIVAL
ITINERARY
LEAF
New York
Paris
: Paris
New York
Rome
: Paris : Rome
New York
Cairo
: Paris : Cairo
New York
Madrid
: Paris : Madrid
New York
London
: London
New York
Athens
: London : Athens
New York
Nicosia
: London : Athens : Nicosia
New York
LA
: LA
New York
Tokyo
: LA : Tokyo
|
|
New York
Hawaii
: LA : Tokyo : Hawaii
88
Example: Join predicates and where clause selection with CONNECT BY
|
|
Often times the hierarchical nature of your data is reflected in one table but you need to join those results
to additional tables to fully determine the output of the row.
|
|
|
|
|
In a connect by query you can use any type of join supported by DB2 for i including INNER JOIN, LEFT
OUTER JOIN, and LEFT EXCEPTION JOIN. When you explicitly use a JOIN clause, the predicate
specified in the ON clause is applied first, before the connect by operation, and any WHERE clause in the
connect by query is applied after the recursion. The WHERE selection is applied after the connect by so
that the recursive process results don't end too soon.
|
|
|
|
|
|
|
|
In the following query, you are looking for all the flight connections starting in New York that have an
ON_TIME_PERCENT greater than 90%.
ORIGIN
DEPARTURE
ARRIVAL
FLIGHT#
ONTIME
New York
Paris
Cairo
63
90.50
New York
Paris
Madrid
3256
92.00
New York
London
Athens
247
91.00
New York
Athens
Nicosia
2356
91.00
New York
LA
Tokyo
824
93.00
|
|
New York
Tokyo
Hawaii
94
92.00
|
|
|
|
|
|
|
|
This query can also be expressed without using the JOIN syntax. The query optimizer will pull out of the
WHERE clause those predicates that are join predicates to be processed first and leave any remaining
WHERE predicates to be evaluated after the recursion.
|
|
|
In this second example, if the WHERE predicates are more complex, you may need to aid the optimizer
by explicitly pulling out the JOIN predicates between the flights and flightstats tables and using both an
ON clause and a WHERE clause.
|
|
|
|
|
|
|
|
|
If you want additional search conditions to be applied as part of the recursion process, for example you
never want to take a flight with an on time percentage of less than 90%, you can also control the join
results by putting the join in a derived table with a join predicate and a WHERE clause.
Another option is to put the selection predicates in the START WITH and CONNECT BY clauses.
SELECT CONNECT_BY_ROOT departure AS origin, departure, arrival,

flight_number, on_time_Percent AS onTime
FROM flights INNER JOIN flightstats ON flight_number = flight#
WHERE on_time_percent > 90
SELECT CONNECT_BY_ROOT departure AS origin, departure, arrival, flight_number, on_time_percent AS onTime

FROM flights, flightstats
WHERE flight_number = flight# AND on_time_percent > 90
SELECT CONNECT_BY_ROOT departure AS origin, departure, arrival, flight_number, on_time_percent AS onTime

FROM (SELECT departure, arrival, flight_number, on_time_percent
WHERE flight_number = flight# AND on_time_percent > 90) t1
START WITH departure=New York
SQL programming
89
| SELECT CONNECT_BY_ROOT departure AS origin, departure, arrival, flight_number, on_time_percent AS onTime

|
|
WHERE flight_number = flight#
|
START WITH departure = New York AND on_time_percent > 90
|
CONNECT BY PRIOR arrival = departure AND on_time_percent > 90
| In this case, you would be out of luck as there are no direct flights out of New York with a greater than
| 90% on time statistic. Since there is nothing to seed the recursion, no rows are returned from the query.
Using recursive common table expressions and recursive views

Suppose you want to find out what cities you can fly to if you start in Chicago, and how many separate
flights it will take to get there. The following query shows you that information.
WITH destinations (origin, departure, arrival, flight_count) AS
(SELECT a.departure, a.departure, a.arrival, 1
FROM flights a
WHERE a.departure = Chicago
UNION ALL
SELECT r.origin, b.departure, b.arrival, r.flight_count + 1
FROM destinations r, flights b
WHERE r.arrival = b.departure)
SELECT origin, departure, arrival, flight_count
FROM destinations

ORIGIN
DEPARTURE
ARRIVAL
FLIGHT_COUNT
Chicago
Chicago
Miami
Chicago
Chicago
Frankfurt
Chicago
Miami
Lima
Chicago
Frankfurt
Moscow
Chicago
Frankfurt
Beijing
Chicago
Frankfurt
Vienna
Chicago
Moscow
Tokyo
Chicago
Tokyo
Hawaii
This recursive query is written in two parts. The first part of the common table expression is called the
intialization fullselect. It selects the first rows for the result set of the common table expression. In this
example, it selects the two rows in the flights table that get you directly to another location from Chicago.
It also initializes the number of flight legs to one for each row it selects.
The second part of the recursive query joins the rows from the current result set of the common table
expression with other rows from the original table. It is called the iterative fullselect. This is where the
recursion is introduced. Notice that the rows that have already been selected for the result set are
referenced by using the name of the common table expression as the table name and the common table
expression result column names as the column names.
In this recursive part of the query, any rows from the original table that you can get to from each of the
previously selected arrival cities are selected. A previously selected row's arrival city becomes the new
departure city. Each row from this recursive select increments the flight count to the destination by one
more flight. As these new rows are added to the common table expression result set, they are also fed
into the iterative fullselect to generate more result set rows. In the data for the final result, you can see
that the total number of flights is actually the total number of recursive joins (plus 1) it took to get to that
arrival city.
90
A recursive view looks very similar to a recursive common table expression. You can write the previous
recursive common table expression as a recursive view like this:
CREATE VIEW destinations (origin, departure, arrival, flight_count) AS
SELECT departure, departure, arrival, 1
FROM flights
WHERE departure = Chicago
UNION ALL
SELECT r.origin, b.departure, b.arrival, r.flight_count + 1
|
|
|
The iterative fullselect part of this view definition refers to the view itself. Selection from this view
returns the same rows as you get from the previous recursive common table expression. For comparison,
note that connect by recursion is allowed anywhere a SELECT is allowed, so it can easily be included in a
view definition.
Example: Two starting cities using recursive common table expressions

Suppose you are willing to fly from either Chicago or New York, and you want to know where you
could go and how much it would cost.
WITH destinations (departure, arrival, connections, cost) AS
(SELECT a.departure, a.arrival, 0, price
FROM flights a
WHERE a.departure = Chicago OR
a.departure = New York
UNION ALL
SELECT r.departure, b.arrival, r.connections + 1,
r.cost + b.price
SELECT departure, arrival, connections, cost
FROM destinations

DEPARTURE
ARRIVAL
CONNECTIONS
COST
Chicago
Miami
300
Chicago
Frankfurt
480
New York
Paris
400
New York
London
350
New York
Los Angeles
330
Chicago
Lima
830
Chicago
Moscow
1,060
Chicago
Beijing
960
Chicago
Vienna
680
New York
Madrid
780
New York
Cairo
880
New York
Rome
740
New York
Athens
690
New York
Tokyo
860
Chicago
Tokyo
1,740
New York
Nicosia
970
SQL programming
91

DEPARTURE
ARRIVAL
CONNECTIONS
COST
New York
Hawaii
1,190
Chicago
Hawaii
2,070
For each returned row, the results show the starting departure city and the final destination city. It counts
the number of connections needed rather than the total number of flight and adds up the total cost for all
the flights.
Example: Two tables used for recursion using recursive common table expressions
Now, suppose you start in Chicago but add in transportation by railway in addition to the airline flights,
and you want to know which cities you can go to.
The following query returns that information:
WITH destinations (departure, arrival, connections, flights, trains, cost) AS
(SELECT f.departure, f.arrival, 0, 1, 0, price
FROM flights f
WHERE f.departure = Chicago
UNION ALL
SELECT t.departure, t.arrival, 0, 0, 1, price
FROM trains t
WHERE t.departure = Chicago
UNION ALL
SELECT r.departure, b.arrival, r.connections + 1 , r.flights + 1, r.trains,
r.cost + b.price
WHERE r.arrival = b.departure
UNION ALL
SELECT r.departure, c.arrival, r.connections + 1 ,
r.flights, r.trains + 1, r.cost + c.price
FROM destinations r, trains c
WHERE r.arrival = c.departure)
SELECT departure, arrival, connections, flights, trains, cost
FROM destinations

DEPARTURE
ARRIVAL
CONNECTIONS
FLIGHTS
TRAINS
COST
Chicago
Miami
300
Chicago
Frankfurt
480
Chicago
Washington
90
Chicago
Lima
830
Chicago
Moscow
1,060
Chicago
Beijing
960
Chicago
Vienna
680
Chicago
Toronto
340
Chicago
Boston
140
Chicago
Tokyo
1,740
Chicago
Hawaii
2,070
92
In this example, there are two parts of the common table expression that provide initialization values to
the query: one for flights and one for trains. For each of the result rows, there are two recursive
references to get from the previous arrival location to the next possible destination: one for continuing by
air, the other for continuing by train. In the final results, you would see how many connections are
needed and how many airline or train trips can be taken.
Example: DEPTH FIRST and BREADTH FIRST options for recursive common table
expressions
The two examples here show the difference in the result set row order based on whether the recursion is
processed depth first or breadth first.
Note: The search clause is not supported directly for recursive views. You can define a view that contains
a recursive common table expression to get this function.
The option to determine the result using breadth first or depth first is a recursive relationship sort based
on the recursive join column specified for the SEARCH BY clause. When the recursion is handled breadth
first, all children are processed first, then all grandchildren, then all great grandchildren. When the
recursion is handled depth first, the full recursive ancestry chain of one child is processed before going to
the next child.
In both of these cases, you specify an extra column name that is used by the recursive process to keep
track of the depth first or breadth first ordering. This column must be used in the ORDER BY clause of
the outer query to get the rows back in the specified order. If this column is not used in the ORDER BY,
the DEPTH FIRST or BREADTH FIRST processing option is ignored.
The selection of which column to use for the SEARCH BY column is important. To have any meaning in
the result, it must be the column that is used in the iterative fullselect to join from the initialization
fullselect. In this example, ARRIVAL is the column to use.
(SELECT f.departure, f.arrival, 0, price
FROM flights f
UNION ALL
r.cost + b.price
SEARCH DEPTH FIRST BY arrival SET ordcol
SELECT *
FROM destinations
ORDER BY ordcol

DEPARTURE
ARRIVAL
CONNECTIONS
COST
Chicago
Miami
300
Chicago
Lima
830
Chicago
Frankfurt
480
Chicago
Moscow
1,060
Chicago
Tokyo
1,740
Chicago
Hawaii
2,070
SQL programming
93

DEPARTURE
ARRIVAL
CONNECTIONS
COST
Chicago
Beijing
960
Chicago
Vienna
680
In this result data, you can see that all destinations that are generated from the Chicago-to-Miami row are
listed before the destinations from the Chicago-to-Frankfort row.
Next, you can run the same query but request the result to be ordered breadth first.
(SELECT f.departure, f.arrival, 0, price
FROM flights f
UNION ALL
r.cost + b.price
SEARCH BREADTH FIRST BY arrival SET ordcol
SELECT *
FROM destinations
ORDER BY ordcol

|
|
|
|
|
DEPARTURE
ARRIVAL
CONNECTIONS
COST
Chicago
Miami
300
Chicago
Frankfurt
480
Chicago
Lima
830
Chicago
Moscow
1,060
Chicago
Beijing
960
Chicago
Vienna
680
Chicago
Tokyo
1,740
Chicago
Hawaii
2,070
In this result data, you can see that all the direct connections from Chicago are listed before the
connecting flights. The data is identical to the results from the previous query, but in a breadth first order.
As you can see, there is no ordering done based on any values of the column used for depth or breadth
first processing. To get ordering, the ORDER SIBLINGS BY construct available with the CONNECT BY
form of recursion can be used.
Example: Cyclic data using recursive common table expressions

The key to any recursive process, whether it is a recursive programming algorithm or querying recursive
data, is that the recursion must be finite. If not, you will get into a never ending loop. The CYCLE option
allows you to safeguard against cyclic data. Not only will it terminate repeating cycles but it also allows
you to optionally output a cycle mark indicator that may lead you to find cyclic data.
Note: The cycle clause is not supported directly for recursive views. You can define a view that contains
a recursive common table expression to get this function.
94
For a final example, suppose we have a cycle in the data. By adding one more row to the table, there is
now a flight from Cairo to Paris and one from Paris to Cairo. Without accounting for possible cyclic data
like this, it is quite easy to generate a query that will go into an infinite loop processing the data.
INSERT INTO FLIGHTS VALUES(Cairo, Paris, Euro Air, 1134, 440)
WITH destinations (departure, arrival, connections, cost, itinerary) AS
(SELECT f.departure, f.arrival, 1, price,
CAST(f.departure CONCAT f.arrival AS VARCHAR(2000))
FROM flights f
WHERE f.departure = New York
UNION ALL
SELECT r.departure, b.arrival, r.connections + 1 ,
r.cost + b.price, CAST(r.itinerary CONCAT b.arrival AS VARCHAR(2000))
CYCLE arrival SET cyclic_data TO 1 DEFAULT 0
SELECT departure, arrival, itinerary, cyclic_data
FROM destinations

DEPARTURE
ARRIVAL
ITINERARY
CYCLIC_DATA
New York
Paris
New York
Paris
New York
London
New York
London
New York
Los Angeles
New York
Los Angeles
New York
Madrid
New York
Paris
Madrid
New York
Cairo
New York
Paris
Cairo
New York
Rome
New York
Paris
Rome
New York
Athens
New York
London
New York
Tokyo
New York
Los Angeles
New York
Paris
New York
Paris
New York
Nicosia
New York
London
New York
Hawaii
New York
Los Angeles
Athens
Tokyo
Cairo
Paris
Athens
Tokyo
Nicosia
Hawaii
In this example, the ARRIVAL column is defined in the CYCLE clause as the column to use for detecting
a cycle in the data. When a cycle is found, a special column, CYCLIC_DATA in this case, is set to the
character value of '1' for the cycling row in the result set. All other rows will contain the default value of
'0'. When a cycle on the ARRIVAL column is found, processing will not proceed any further in the data so
the infinite loop will not happen. To see if your data actually has a cyclic reference, the CYCLIC_DATA
| column can be referenced in the outer query. You can choose to exclude cyclic rows by adding a
| predicate: WHERE CYCLIC_DATA = 0.
Using the UNION keyword to combine subselects

When SQL encounters the UNION keyword, it processes each subselect to form an interim result table,
then it combines the interim result table of each subselect and deletes duplicate rows to form a combined
result table. You can use different clauses and techniques when coding select-statements.
You can use UNION to eliminate duplicates when merging lists of values obtained from several tables.
For example, you can obtain a combined list of employee numbers that includes:
SQL programming
95
v People in department D11

v People whose assignments include projects MA2112, MA2113, and AD3111
The combined list is derived from two tables and contains no duplicates. To do this, specify:
SELECT EMPNO
UNION
SELECT EMPNO
PROJNO = MA2113 OR
PROJNO = AD3111
ORDER BY EMPNO
To better understand the results from these SQL statements, imagine that SQL goes through the following
process:
Step 1. SQL processes the first SELECT statement:
SELECT EMPNO
The query returns the following interim result table.

EMPNO from CORPDATA.EMPLOYEE
000060
000150
000160
000170
000180
000190
000200
000210
000220
200170
200220
Step 2. SQL processes the second SELECT statement:

SELECT EMPNO
WHERE PROJNO=MA2112 OR
PROJNO= MA2113 OR
PROJNO= AD3111
The query returns another interim result table.

EMPNO from CORPDATA.EMPPROJACT
000230
000230
000240
000230
96

000230
000240
000230
000150
000170
000190
000170
000190
000150
000160
000180
000170
000210
000210
Step 3. SQL combines the two interim result tables, removes duplicate rows, and orders the result:
SELECT EMPNO
UNION
SELECT EMPNO
PROJNO= MA2113 OR
PROJNO= AD3111
ORDER BY EMPNO
The query returns a combined result table with values in ascending sequence.
EMPNO
000060
000150
000160
000170
000180
000190
000200
000210
000220
000230
000240
200170
200220
When you use UNION:

SQL programming
97
v Any ORDER BY clause must appear after the last subselect that is part of the union. In this example,
the results are sequenced on the basis of the first selected column, EMPNO. The ORDER BY clause
specifies that the combined result table is to be in collated sequence. ORDER BY is not allowed in a
view.
v A name may be specified on the ORDER BY clause if the result columns are named. A result column is
named if the corresponding columns in each of the unioned select-statements have the same name. An
AS clause can be used to assign a name to columns in the select list.
SELECT A + B AS X ...
UNION
SELECT X ... ORDER BY X
If the result columns are unnamed, use a positive integer to order the result. The number refers to the
position of the expression in the list of expressions you include in your subselects.
SELECT A + B ...
UNION
SELECT X ... ORDER BY 1
To identify which subselect each row is from, you can include a constant at the end of the select list of
each subselect in the union. When SQL returns your results, the last column contains the constant for the
subselect that is the source of that row. For example, you can specify:
SELECT A, B, A1 ...
UNION
SELECT X, Y, B2...
When a row is returned, it includes a value (either A1 or B2) to indicate the table that is the source of the
row's values. If the column names in the union are different, SQL uses the set of column names specified
in the first subselect when interactive SQL displays or prints the results, or in the SQLDA resulting from
processing an SQL DESCRIBE statement.
Note: Sort sequence is applied after the fields across the UNION pieces are made compatible. The sort
sequence is used for the distinct processing that implicitly occurs during UNION processing.
Related concepts:
Related reference:
statement.
Specifying the UNION ALL keyword:
If you want to keep duplicates in the result of a UNION operation, specify the UNION ALL keyword
instead of just UNION.
This topic uses the same steps and example as Using the UNION keyword to combine subselects on
page 95.
Step 3. SQL combines two interim result tables:
SELECT EMPNO
UNION ALL
SELECT EMPNO
98
PROJNO= MA2113 OR
PROJNO= AD3111
ORDER BY EMPNO
The query returns an ordered result table that includes duplicates.

EMPNO
000060
000150
000150
000150
000160
000160
000170
000170
000170
000170
000180
000180
000190
000190
000190
000200
000210
000210
000210
000220
000230
000230
000230
000230
000230
000240
000240
200170
200220
The UNION ALL operation is associative, for example:

(SELECT PROJNO FROM CORPDATA.PROJECT
UNION ALL
SELECT PROJNO FROM CORPDATA.PROJECT)
UNION ALL
SELECT PROJNO FROM CORPDATA.EMPPROJACT
This statement can also be written as:

SQL programming
99
SELECT PROJNO FROM CORPDATA.PROJECT

UNION ALL
(SELECT PROJNO FROM CORPDATA.PROJECT
UNION ALL
SELECT PROJNO FROM CORPDATA.EMPPROJACT)
When you include the UNION ALL in the same SQL statement as a UNION operator, however, the result
of the operation depends on the order of evaluation. Where there are no parentheses, evaluation is from
left to right. Where parentheses are included, the parenthesized subselect is evaluated first, followed,
from left to right, by the other parts of the statement.
Using the EXCEPT keyword

The EXCEPT keyword returns the result set of the first subselect minus any matching rows from the
second subselect.
Suppose that you want to find a list of employee numbers that includes people in department D11 minus
those people whose assignments include projects MA2112, MA2113, and AD3111.
This query returns all of the people in department D11 who are not working on projects MA2112,
MA2113, and AD3111:
SELECT EMPNO
EXCEPT
SELECT EMPNO
PROJNO = MA2113 OR
PROJNO = AD3111
ORDER BY EMPNO
process:
SELECT EMPNO
This query returns an interim result table.

000060
000150
000160
000170
000180
000190
000200
000210
000220
200170
200220
100

SELECT EMPNO
PROJNO= MA2113 OR
PROJNO= AD3111
This query returns another interim result table.

000230
000230
000240
000230
000230
000240
000230
000150
000170
000190
000170
000190
000150
000160
000180
000170
000210
000210
Step 3. SQL takes the first interim result table, removes all of the rows that also appear in the second
interim result table, removes duplicate rows, and orders the result:
SELECT EMPNO
EXCEPT
SELECT EMPNO
PROJNO= MA2113 OR
PROJNO= AD3111
ORDER BY EMPNO
This query returns a combined result table with values in ascending sequence.
EMPNO
000060
000200
000220
200170
SQL programming
101
EMPNO
200220
Using the INTERSECT keyword

The INTERSECT keyword returns a combined result set that consists of all of the rows existing in both
result sets.
Suppose that you want to find a list of employee numbers that includes people in department D11 and
people whose assignments include projects MA2112, MA2113, and AD3111.
The INTERSECT operation returns all of the employee numbers that exist in both result sets. In other
words, this query returns all of the people in department D11 who are also working on projects MA2112,
MA2113, and AD3111:
SELECT EMPNO
INTERSECT
SELECT EMPNO
PROJNO = MA2113 OR
PROJNO = AD3111
ORDER BY EMPNO
process:
SELECT EMPNO
This query returns an interim result table.

000060
000150
000160
000170
000180
000190
000200
000210
000220
200170
200220
102
SELECT EMPNO
PROJNO= MA2113 OR
PROJNO= AD3111
This query returns another interim result table.

000230
000230
000240
000230
000230
000240
000230
000150
000170
000190
000170
000190
000150
000160
000180
000170
000210
000210
Step 3. SQL takes the first interim result table, compares it to the second interim result table, and returns
the rows that exist in both tables minus any duplicate rows, and orders the results.
SELECT EMPNO
INTERSECT
SELECT EMPNO
PROJNO= MA2113 OR
PROJNO= AD3111
ORDER BY EMPNO
This query returns a combined result table with values in ascending sequence.
EMPNO
000150
000160
000170
000180
000190
SQL programming
103
EMPNO
000210
Data retrieval errors

Use this information to understand how SQL handles errors that occur when retrieving data.
If SQL finds that a retrieved character or graphic column is too long to be placed in a host variable, SQL
does the following:
v Truncates the data while assigning the value to the host variable.
v Sets SQLWARN0 and SQLWARN1 in the SQLCA to the value 'W' or sets RETURNED_SQLSTATE to
'01004' in the SQL diagnostics area.
v Sets the indicator variable, if provided, to the length of the value before truncation.
If SQL finds a data mapping error while running a statement, one of two things occurs:
v If the error occurs on an expression in the SELECT list and an indicator variable is provided for the
expression in error:
SQL returns a -2 for the indicator variable corresponding to the expression in error.
SQL returns all valid data for that row.
SQL returns a positive SQLCODE.
v If an indicator variable is not provided, SQL returns the corresponding negative SQLCODE.
Data mapping errors include:
v +138 - Argument of the substringing function is not valid.
v +180 - Syntax for a string representation of a date, time, or timestamp is not valid.
v +181 - String representation of a date, time, or timestamp is not a valid value.
v +183 - Invalid result from a date/time expression. The resulting date or timestamp is not within the
valid range of dates or timestamps.
v +191 - MIXED data is not properly formed.
v +304 - Numeric conversion error (for example, overflow, underflow, or division by zero).
v +331 - Characters cannot be converted.
v +364 - DECFLOAT arithmetic error.
v +420 - Character in the CAST argument is not valid.
v +802 - Data conversion or data mapping error.
For data mapping errors, the SQLCA reports only the last error detected. The indicator variable
corresponding to each result column having an error is set to -2.
For data mapping errors on a multi-row FETCH, each mapping error reported as a warning SQLSTATE
will have a separate condition area in the SQL diagnostics area. Note that SQL stops on the first error, so
only one mapping error that is reported as an error SQLSTATE will be returned in the SQL diagnostics
area.
For all other SQL statements, only the last warning SQLSTATE will be reported in the SQL diagnostics
area.
If the full-select contains DISTINCT in the select list and a column in the select list contains numeric data
that is not valid, the data is considered equal to a null value if the query is completed as a sort. If an
existing index is used, the data is not considered equal to a null.
The impact of data mapping errors on the ORDER BY clause depends on the situation:
104
v If the data mapping error occurs while data is being assigned to a host variable in a SELECT INTO or
FETCH statement, and that same expression is used in the ORDER BY clause, the result record is
ordered based on the value of the expression. It is not ordered as if it were a null (higher than all other
values). This is because the expression was evaluated before the assignment to the host variable is
attempted.
v If the data mapping error occurs while an expression in the select-list is being evaluated and the same
expression is used in the ORDER BY clause, the result column is normally ordered as if it were a null
value (higher than all other values). If the ORDER BY clause is implemented by using a sort, the result
column is ordered as if it were a null value. If the ORDER BY clause is implemented by using an
existing index, in the following cases, the result column is ordered based on the actual value of the
expression in the index:
The expression is a date column with a date format of *MDY, *DMY, *YMD, or *JUL, and a date
conversion error occurs because the date is not within the valid range for dates.
The expression is a character column and a character cannot be converted.
The expression is a decimal column and a numeric value that is not valid is detected.
Inserting rows using the INSERT statement

To add a single row or multiple rows to a table or view, use a form of the INSERT statement.
You can use the INSERT statement to add new rows to a table or view in one of the following ways:
v Specifying values in the INSERT statement for columns to be added.
v Including a select-statement in the INSERT statement to tell SQL what data for the new row is
contained in another table or view.
v Specifying the blocked form of the INSERT statement to add multiple rows.
For every row you insert, you must supply a value for each column defined with the NOT NULL
attribute if that column does not have a default value. The INSERT statement for adding a row to a table
or view may look like this:
INSERT INTO table-name
(column1, column2, ... )
VALUES (value-for-column1, value-for-column2, ... )
The INTO clause names the columns for which you specify values. The VALUES clause specifies a value
for each column named in the INTO clause. The value you specify can be:
v A constant. Inserts the value provided in the VALUES clause.
v A null value. Inserts the null value, using the keyword NULL. The column must be defined as capable
of containing a null value or an error occurs.
v A host variable. Inserts the contents of a host variable.
|
v A global variable. Inserts the contents of the global variable.

v A special register. Inserts a special register value; for example, USER.
v An expression. Inserts the value that results from an expression.
v A scalar fullselect. Inserts the value that is the result of running the select statement.
v The DEFAULT keyword. Inserts the default value of the column. The column must have a default
value defined for it or allow the NULL value, or an error occurs.
You must provide a value in the VALUES clause for each column named in an INSERT statement's
column list. The column name list can be omitted if all columns in the table have a value provided in the
VALUES clause. If a column has a default value, the keyword DEFAULT may be used as a value in the
VALUES clause. This causes the default value for the column to be placed in the column.
It is a good idea to name all columns into which you are inserting values because:
v Your INSERT statement is more descriptive.
SQL programming
105
v You can verify that you are providing the values in the proper order based on the column names.
v You have better data independence. The order in which the columns are defined in the table does not
affect your INSERT statement.
If the column is defined to allow null values or to have a default, you do not need to name it in the
column name list or specify a value for it. The default value is used. If the column is defined to have a
default value, the default value is placed in the column. If DEFAULT was specified for the column
definition without an explicit default value, SQL places the default value for that data type in the
column. If the column does not have a default value defined for it, but is defined to allow the null value
(NOT NULL was not specified in the column definition), SQL places the null value in the column.
v For numeric columns, the default value is 0.
v For fixed length character or graphic columns, the default is blanks.
v For fixed length binary columns, the default is hexadecimal zeros.
v For varying length character, graphic, or binary columns and for LOB columns, the default is a zero
length string.
v For date, time, and timestamp columns, the default value is the current date, time, or timestamp. When
inserting a block of records, the default date/time value is extracted from the system when the block is
written. This means that the column will be assigned the same default value for each row in the block.
v For DataLink columns, the default value corresponds to DLVALUE('','URL','').
v For distinct-type columns, the default value is the default value of the corresponding source type.
v For ROWID columns or columns that are defined AS IDENTITY, the database manager generates a
default value.
v For XML columns, there is no default allowed except the null value.
When your program attempts to insert a row that duplicates another row already in the table, an error
might occur. Multiple null values may or may not be considered duplicate values, depending on the
option used when the index was created.
v If the table has a primary key, unique key, or unique index, the row is not inserted. Instead, SQL
returns an SQLCODE of -803.
v If the table does not have a primary key, unique key, or unique index, the row can be inserted without
error.
If SQL finds an error while running the INSERT statement, it stops inserting data. If you specify
COMMIT(*ALL), COMMIT(*CS), COMMIT(*CHG), or COMMIT(*RR), no rows are inserted. Rows already
inserted by this statement, in the case of INSERT with a select-statement or blocked insert, are deleted. If
you specify COMMIT(*NONE), any rows already inserted are not deleted.
A table created by SQL is created with the Reuse Deleted Records parameter of *YES. This allows the
database manager to reuse any rows in the table that were marked as deleted. The CHGPF command can
be used to change the attribute to *NO. This causes INSERT to always add rows to the end of the table.
The order in which rows are inserted does not guarantee the order in which they will be retrieved.
If the row is inserted without error, the SQLERRD(3) field of the SQLCA has a value of 1.
Note: For blocked INSERT or for INSERT with select-statement, more than one row can be inserted. The
number of rows inserted is reflected in SQLERRD(3) in the SQLCA. It is also available from the
ROW_COUNT diagnostics item in the GET DIAGNOSTICS statement.
Related reference:
INSERT
Inserting rows using the VALUES clause

You use the VALUES clause in the INSERT statement to insert a single row or multiple rows into a table.
106
An example of this is to insert a new row into the DEPARTMENT table. The columns for the new row
are as follows:
v
v
v
v
Department number (DEPTNO) is 'E31'

Department name (DEPTNAME) is 'ARCHITECTURE'
Manager number (MGRNO) is '00390'
Reports to (ADMRDEPT) department 'E01'
The INSERT statement for this new row is as follows:

INSERT INTO DEPARTMENT (DEPTNO, DEPTNAME, MGRNO, ADMRDEPT)
VALUES(E31, ARCHITECTURE, 00390, E01)
You can also insert multiple rows into a table using the VALUES clause. The following example inserts
two rows into the PROJECT table. Values for the Project number (PROJNO) , Project name (PROJNAME),
Department number (DEPTNO), and Responsible employee (RESPEMP) are given in the values list. The
value for the Project start date (PRSTDATE) uses the current date. The rest of the columns in the table
that are not listed in the column list are assigned their default value.
INSERT INTO PROJECT (PROJNO, PROJNAME, DEPTNO, RESPEMP, PRSTDATE)
VALUES(HG0023, NEW NETWORK, E11, 200280, CURRENT DATE),
(HG0024, NETWORK PGM, E11", 200310, CURRENT DATE)
Inserting rows using a select-statement

You can use a select-statement within an INSERT statement to insert zero, one, or more rows into a table
from the result table of the select-statement.
One use for this kind of INSERT statement is to move data into a table you created for summary data.
For example, suppose you want a table that shows each employee's time commitments to projects. Create
a table called EMPTIME with the columns EMPNUMBER, PROJNUMBER, STARTDATE, and ENDDATE
and then use the following INSERT statement to fill the table:
INSERT INTO CORPDATA.EMPTIME
(EMPNUMBER, PROJNUMBER, STARTDATE, ENDDATE)
SELECT EMPNO, PROJNO, EMSTDATE, EMENDATE
The select-statement embedded in the INSERT statement is no different from the select-statement you use
to retrieve data. With the exception of FOR READ ONLY, FOR UPDATE, or the OPTIMIZE clause, you
can use all the keywords, functions, and techniques used to retrieve data. SQL inserts all the rows that
meet the search conditions into the table you specify. Inserting rows from one table into another table
does not affect any existing rows in either the source table or the target table.
You should consider the following when inserting multiple rows into a table:
Notes:
1. The number of columns implicitly or explicitly listed in the INSERT statement must equal the
number of columns listed in the select-statement.
2. The data in the columns you are selecting must be compatible with the columns you are
inserting into when using the INSERT with select-statement.
3. In the event the select-statement embedded in the INSERT returns no rows, an SQLCODE of
100 is returned to alert you that no rows were inserted. If you successfully insert rows, the
SQLERRD(3) field of the SQLCA has an integer representing the number of rows SQL actually
inserted. This value is also available from the ROW_COUNT diagnostics item in the GET
DIAGNOSTICS statement.
4. If SQL finds an error while running the INSERT statement, SQL stops the operation. If you
specify COMMIT (*CHG), COMMIT(*CS), COMMIT (*ALL), or COMMIT(*RR), nothing is
inserted into the table and a negative SQLCODE is returned. If you specify COMMIT(*NONE),
any rows inserted before the error remain in the table.
SQL programming
107
Inserting multiple rows using the blocked INSERT statement

Using a blocked INSERT statement, you can insert multiple rows into a table with a single INSERT
statement.
The blocked INSERT statement is supported in all of the languages except REXX. The data inserted into
the table must be in a host structure array. If indicator variables are used with a blocked INSERT, they
must also be in a host structure array.
For example, to add ten employees to the CORPDATA.EMPLOYEE table:
INSERT INTO CORPDATA.EMPLOYEE
(EMPNO,FIRSTNME,MIDINIT,LASTNAME,WORKDEPT)
10 ROWS VALUES(:DSTRUCT:ISTRUCT)
DSTRUCT is a host structure array with five elements that is declared in the program. The five elements
correspond to EMPNO, FIRSTNME, MIDINIT, LASTNAME, and WORKDEPT. DSTRUCT has a
dimension of at least ten to accommodate inserting ten rows. ISTRUCT is a host structure array that is
declared in the program. ISTRUCT has a dimension of at least ten small integer fields for the indicators.
Blocked INSERT statements are supported for non-distributed SQL applications and for distributed
applications where both the application server and the application requester are System i products.
Related concepts:
Inserting data into tables with referential constraints

When you insert data into tables with referential constraints, you need to consider these rules.
If you are inserting data into a parent table with a parent key, SQL does not allow:
v Duplicate values for the parent key
v If the parent key is a primary key, a null value for any column of the primary key
If you are inserting data into a dependent table with foreign keys:
v Each non-null value you insert into a foreign key column must be equal to some value in the
corresponding parent key of the parent table.
v If any column in the foreign key is null, the entire foreign key is considered null. If all foreign keys
that contain the column are null, the INSERT succeeds (as long as there are no unique index
violations).
Alter the sample application project table (PROJECT) to define two foreign keys:
v A foreign key on the department number (DEPTNO) which references the department table
v A foreign key on the employee number (RESPEMP) which references the employee table.
ALTER TABLE CORPDATA.PROJECT ADD CONSTRAINT RESP_DEPT_EXISTS
FOREIGN KEY (DEPTNO)
REFERENCES CORPDATA.DEPARTMENT
ON DELETE RESTRICT
ALTER TABLE CORPDATA.PROJECT ADD CONSTRAINT RESP_EMP_EXISTS
FOREIGN KEY (RESPEMP)
REFERENCES CORPDATA.EMPLOYEE
ON DELETE RESTRICT
Notice that the parent table columns are not specified in the REFERENCES clause. The columns are not
required to be specified as long as the referenced table has a primary key or eligible unique key which
can be used as the parent key.
108
Every row inserted into the PROJECT table must have a value of DEPTNO that is equal to some value of
DEPTNO in the department table. (The null value is not allowed because DEPTNO in the project table is
defined as NOT NULL.) The row must also have a value of RESPEMP that is either equal to some value
of EMPNO in the employee table or is null.
The following INSERT statement fails because there is no matching DEPTNO value ('A01') in the
DEPARTMENT table.
INSERT INTO CORPDATA.PROJECT (PROJNO, PROJNAME, DEPTNO, RESPEMP)
VALUES (AD3120, BENEFITS ADMIN, A01, 000010)
Likewise, the following INSERT statement is unsuccessful because there is no EMPNO value of '000011' in
the EMPLOYEE table.
VALUES (AD3130, BILLING, D21, 000011)
The following INSERT statement completes successfully because there is a matching DEPTNO value of
'E01' in the DEPARTMENT table and a matching EMPNO value of '000010' in the EMPLOYEE table.
VALUES (AD3120, BENEFITS ADMIN, E01, 000010)
Inserting values into an identity column

You can insert a value into an identity column or allow the system to insert a value for you.
For example, a table has columns called ORDERNO (identity column), SHIPPED_TO (varchar(36)), and
ORDER_DATE (date). You can insert a row into this table by issuing the following statement:
INSERT INTO ORDERS (SHIPPED_TO, ORDER_DATE)
VALUES (BME TOOL, 2002-02-04)
In this case, a value is generated by the system for the identity column automatically. You can also write
this statement using the DEFAULT keyword:
INSERT INTO ORDERS (SHIPPED_TO, ORDER_DATE, ORDERNO)
VALUES (BME TOOL, 2002-02-04, DEFAULT)
After the insert, you can use the IDENTITY_VAL_LOCAL function to determine the value that the system
assigned to the column.
Sometimes a value for an identity column is specified by the user, such as in this INSERT statement using
a SELECT:
INSERT INTO ORDERS OVERRIDING USER VALUE
(SELECT * FROM TODAYS_ORDER)
In this case, OVERRIDING USER VALUE tells the system to ignore the value provided for the identity
column from the SELECT and to generate a new value for the identity column. OVERRIDING USER
VALUE must be used if the identity column was created with the GENERATED ALWAYS clause; it is
optional for GENERATED BY DEFAULT. If OVERRIDING USER VALUE is not specified for a
GENERATED BY DEFAULT identity column, the value provided for the column in the SELECT is
inserted.
You can force the system to use the value from the select for a GENERATED ALWAYS identity column by
specifying OVERRIDING SYSTEM VALUE. For example, issue the following statement:
INSERT INTO ORDERS OVERRIDING SYSTEM VALUE
(SELECT * FROM TODAYS_ORDER)
This INSERT statement uses the value from SELECT; it does not generate a new value for the identity
column. You cannot provide a value for an identity column created using GENERATED ALWAYS without
using the OVERRIDING SYSTEM VALUE clause.
SQL programming
109
Related reference:
Scalar functions
Selecting inserted values

You can retrieve the values for rows that are being inserted by specifying the INSERT statement in the
FROM clause of a SELECT statement.
When you insert one or more rows into a table, you can select the result rows of the insert operation.
These rows include any of the following values:
v The value of any generated column, such as identity, ROWID, or row change timestamp columns
v Any default values used for columns
v All values for all rows inserted by a multiple-row insert operation
v Values that were changed by a before insert trigger
The following example uses a table defined as follows:
CREATE TABLE
(EMPNO
NAME
SALARY
DEPTNO
LEVEL
HIRETYPE
HIREDATE
EMPSAMP
INTEGER GENERATED ALWAYS AS IDENTITY,
CHAR(30),
DECIMAL(10,2),
SMALLINT,
CHAR(30),
VARCHAR(30) NOT NULL DEFAULT New Employee,
DATE NOT NULL WITH DEFAULT)
To insert a row for a new employee and see the values that were used for EMPNO, HIRETYPE, and
HIREDATE, use the following statement:
SELECT EMPNO, HIRETYPE, HIREDATE
FROM FINAL TABLE ( INSERT INTO EMPSAMP (NAME, SALARY, DEPTNO, LEVEL)
VALUES(Mary Smith, 35000.00, 11, Associate))
The returned values are the generated value for EMPNO, 'New Employee' for HIRETYPE, and the
current date for HIREDATE.
| Inserting data from a remote database
| You can insert into a table on the local server using a select statement to get rows from a remote server.
| To insert all the rows from the SALES table on REMOTESYS for sales made yesterday, use the following
| statement:
| INSERT INTO SALES
|
(SELECT * FROM REMOTESYS.TESTSCHEMA.SALES WHERE SALES_DATE = CURRENT DATE - 1 DAY)
| DB2 will connect to REMOTESYS to run the SELECT, return the selected rows to the local system, and
| insert them into the local SALES table.
|
|
|
|
|
Since a three-part object name or an alias that is defined to reference a three-part name of a table or view
creates an implicit connection to the application server, a server authentication entry must exist. Use the
Add Server Authentication Entry (ADDSVRAUTE) command on the application requestor specifying the
server name, user ID, and password. The server name and user ID must be entered in upper case.
ADDSVRAUTE USRPRF(yourprf) SERVER(DRDASERVERNAME) USRID(YOURUID) PASSWORD(yourpwd)
| See Distributed Database Programming for additional details on server authentication usage for DRDA.
| Related reference:
110
|
|
Creating a table with remote server data on page 23

You can create a table on the local server that references one or more tables on a remote server.
Changing data in a table using the UPDATE statement

To update data in a table or view, use the UPDATE statement.
With the UPDATE statement, you can change the value of one or more columns in each row that meets
the search condition of the WHERE clause. The result of the UPDATE statement is one or more changed
column values in zero or more rows of a table (depending on how many rows meet the search condition
specified in the WHERE clause). The UPDATE statement looks like this:
UPDATE table-name
SET column-1 = value-1,
column-2 = value-2, ...
WHERE search-condition ...
Suppose that an employee is relocated. To update the CORPDATA.EMPLOYEE table to reflect the move,
run the following statement:
UPDATE CORPDATA.EMPLOYEE
SET JOB = :PGM-CODE,
PHONENO = :PGM-PHONE
WHERE EMPNO = :PGM-SERIAL
Use the SET clause to specify a new value for each column that you want to update. The SET clause
names the columns that you want updated and provides the values that you want them changed to. You
can specify the following types of values:
v A column name. Replace the column's current value with the contents of another column in the same
row.
v A constant. Replace the column's current value with the value provided in the SET clause.
v A null value. Replace the column's current value with the null value, using the keyword NULL. The
column must be defined as capable of containing a null value when the table was created, or an error
occurs.
v A host variable. Replace the column's current value with the contents of a host variable.
| v A global variable. Replace the column's current value with the contents of a global variable.
v
v
v
v
A special register. Replace the column's current value with a special register value; for example, USER.
An expression. Replace the column's current value with the value that results from an expression.
A scalar fullselect. Replace the column's current value with the value that the subquery returns.
The DEFAULT keyword. Replace the column's current value with the default value of the column. The
column must have a default value defined for it or allow the NULL value, or an error occurs.
The following UPDATE statement uses many different values:

UPDATE WORKTABLE
SET COL1 = ASC,
COL2 = NULL,
COL3 = :FIELD3,
COL4 = CURRENT TIME,
COL5 = AMT - 6.00,
COL6 = COL7
WHERE EMPNO = :PGM-SERIAL
To identify the rows to be updated, use the WHERE clause:

v To update a single row, use a WHERE clause that selects only one row.
v To update several rows, use a WHERE clause that selects only the rows you want to update.
SQL programming
111
You can omit the WHERE clause. If you do, SQL updates each row in the table or view with the values
you supply.
If the database manager finds an error while running your UPDATE statement, it stops updating and
returns a negative SQLCODE. If you specify COMMIT(*ALL), COMMIT(*CS), COMMIT(*CHG), or
COMMIT(*RR), no rows in the table are changed (rows already changed by this statement, if any, are
restored to their previous values). If COMMIT(*NONE) is specified, any rows already changed are not
restored to previous values.
If the database manager cannot find any rows that meet the search condition, an SQLCODE of +100 is
returned.
Note: The UPDATE statement may have updated more than one row. The number of rows updated is
reflected in SQLERRD(3) of the SQLCA. This value is also available from the ROW_COUNT
diagnostics item in the GET DIAGNOSTICS statement.
The SET clause of an UPDATE statement can be used in many ways to determine the actual values to be
set in each row being updated. The following example lists each column with its corresponding value:
UPDATE EMPLOYEE
SET WORKDEPT = D11,
PHONENO = 7213,
JOB = DESIGNER
You can also write this UPDATE statement by specifying all of the columns and then all of the values:
UPDATE EMPLOYEE
SET (WORKDEPT, PHONENO, JOB)
= (D11, 7213, DESIGNER)
Related reference:
UPDATE
Updating a table using a scalar-subselect

Using a scalar-subselect, you can update one or more columns in a table with one or more values selected
from another table.
In the following example, an employee moves to a different department but continues working on the
same projects. The employee table has already been updated to contain the new department number.
Now the project table needs to be updated to reflect the new department number of this employee
(employee number is '000030').
UPDATE PROJECT
SET DEPTNO =
(SELECT WORKDEPT FROM EMPLOYEE
WHERE PROJECT.RESPEMP = EMPLOYEE.EMPNO)
WHERE RESPEMP=000030
This same technique can be used to update a list of columns with multiple values returned from a single
select.
Updating a table with rows from another table

You can update an entire row in one table with values from a row in another table.
Suppose that a master class schedule table needs to be updated with changes that have been made in a
copy of the table. The changes are made to the work copy and merged into the master table every night.
The two tables have exactly the same columns and one column, CLASS_CODE, is a unique key column.
112
UPDATE CL_SCHED
SET ROW =
(SELECT * FROM MYCOPY
WHERE CL_SCHED.CLASS_CODE = MYCOPY.CLASS_CODE)
This update will update all of the rows in CL_SCHED with the values from MYCOPY.
Updating tables with referential constraints

If you are updating a parent table, you cannot modify a primary key for which dependent rows exist.
Changing the key violates referential constraints for dependent tables and leaves some rows without a
parent. Furthermore, you cannot give any part of a primary key a null value.
Update rules
The action taken on dependent tables when an UPDATE is performed on a parent table depends on the
update rule specified for the referential constraint. If no update rule was defined for a referential
constraint, the UPDATE NO ACTION rule is used.
UPDATE NO ACTION
Specifies that the row in the parent table can be updated if no other row depends on it. If a
dependent row exists in the relationship, the UPDATE fails. The check for dependent rows is
performed at the end of the statement.
UPDATE RESTRICT
Specifies that the row in the parent table can be updated if no other row depends on it. If a
dependent row exists in the relationship, the UPDATE fails. The check for dependent rows is
performed immediately.
The subtle difference between the RESTRICT rule and the NO ACTION rule is easiest seen when looking
at the interaction of triggers and referential constraints. Triggers can be defined to fire either before or
after an operation (an UPDATE statement, in this case). A before trigger fires before the UPDATE is
performed and therefore before any checking of constraints. An after trigger is fired after the UPDATE is
performed, and after a constraint rule of RESTRICT (where checking is performed immediately), but
before a constraint rule of NO ACTION (where checking is performed at the end of the statement). The
triggers and rules occur in the following order:
1. A before trigger is fired before the UPDATE and before a constraint rule of RESTRICT or NO ACTION.
2. An after trigger is fired after a constraint rule of RESTRICT, but before a NO ACTION rule.
If you are updating a dependent table, any non-null foreign key values that you change must match the
primary key for each relationship in which the table is a dependent. For example, department numbers in
the employee table depend on the department numbers in the department table. You can assign an
employee to no department (the null value), but not to a department that does not exist.
If an UPDATE against a table with a referential constraint fails, all changes made during the update
operation are undone.
Related reference:
Journaling on page 138
The DB2 for i journal support provides an audit trail and forward and backward recovery.
Commitment control on page 138
The DB2 for i commitment control support provides a means for processing a group of database changes,
such as update, insert, or delete operations or data definition language (DDL) operations, as a single unit
of work (also referred to as a transaction).
SQL programming
113
Examples: UPDATE rules:

These examples illustrate the UPDATE rules for tables with referential constraints.
For example, you cannot update a department number from the DEPARTMENT table if the department is
still responsible for a project that is described by a dependent row in the PROJECT table.
The following UPDATE statement fails because the PROJECT table has rows that are dependent on
DEPARTMENT.DEPTNO that has a value of 'D01' (the row targeted by the WHERE statement). If this
UPDATE statement were to be allowed, the referential constraint between the PROJECT and
DEPARTMENT tables would be broken.
UPDATE CORPDATA.DEPARTMENT
SET DEPTNO = D99
WHERE DEPTNAME = DEVELOPMENT CENTER
The following statement fails because it violates the referential constraint that exists between the primary
key DEPTNO in DEPARTMENT and the foreign key DEPTNO in PROJECT:
UPDATE CORPDATA.PROJECT
SET DEPTNO = D00
WHERE DEPTNO = D01;
The statement attempts to change all department numbers of D01 to department number D00. Because
D00 is not a value of the primary key DEPTNO in DEPARTMENT, the statement fails.
Updating an identity column

You can update the value in an identity column to a specified value or have the system generate a new
value.
For example, using the table with columns called ORDERNO (identity column), SHIPPED_TO
(varchar(36)), and ORDER_DATE (date), you can update the value in an identity column by issuing the
UPDATE ORDERS
SET (ORDERNO, ORDER_DATE)=
(DEFAULT, 2002-02-05)
WHERE SHIPPED_TO = BME TOOL
A value is generated by the system for the identity column automatically. You can override having the
system generate a value by using the OVERRIDING SYSTEM VALUE clause:
UPDATE ORDERS OVERRIDING SYSTEM VALUE
SET (ORDERNO, ORDER_DATE)=
(553, 2002-02-05)
WHERE SHIPPED_TO = BME TOOL
Related reference:
Updating data as it is retrieved from a table

You can update rows of data as you retrieve them by using a cursor.
On the select-statement, use FOR UPDATE OF followed by a list of columns that may be updated. Then
use the cursor-controlled UPDATE statement. The WHERE CURRENT OF clause names the cursor that
points to the row you want to update. If a FOR UPDATE OF, an ORDER BY, a FOR READ ONLY, or a
SCROLL clause without the DYNAMIC clause is not specified, all columns can be updated.
If a multiple-row FETCH statement has been specified and run, the cursor is positioned on the last row
of the block. Therefore, if the WHERE CURRENT OF clause is specified on the UPDATE statement, the
114
last row in the block is updated. If a row within the block must be updated, the program must first
position the cursor on that row. Then the UPDATE WHERE CURRENT OF can be specified. Consider the
following example:
Table 30. Updating a table
Scrollable Cursor SQL Statement
Comments
EXEC SQL
DECLARE THISEMP DYNAMIC SCROLL CURSOR FOR
SELECT EMPNO, WORKDEPT, BONUS
WHERE WORKDEPT = 'D11'
FOR UPDATE OF BONUS
END-EXEC.
EXEC SQL
OPEN THISEMP
END-EXEC.
EXEC SQL
WHENEVER NOT FOUND
GO TO CLOSE-THISEMP
END-EXEC.
EXEC SQL
FETCH NEXT FROM THISEMP
FOR 5 ROWS
INTO :DEPTINFO :IND-ARRAY
END-EXEC.
DEPTINFO and IND-ARRAY are

declared in the program as a host
structure array and an indicator
array.
... determine if any employees in department D11 receive a bonus less than
$500.00. If so, update that record to the new minimum of $500.00.
EXEC SQL
FETCH RELATIVE :NUMBACK FROM THISEMP
END-EXEC.
EXEC SQL
SET BONUS = 500
WHERE CURRENT OF THISEMP
END-EXEC.
EXEC SQL
FETCH RELATIVE :NUMBACK FROM THISEMP
FOR 5 ROWS
INTO :DEPTINFO :IND-ARRAY
END-EXEC.
... positions to the record in the

block to update by fetching in the
reverse order.
... updates the bonus for the
employee in department D11 that
is under the new $500.00
minimum.
... positions to the beginning of

the same block that was already
fetched and fetches the block
again. (NUMBACK -(5 NUMBACK - 1))
... branch back to determine if any more employees in the block have a bonus
under $500.00.
... branch back to fetch and process the next block of rows.
SQL programming
115
Table 30. Updating a table (continued)

Scrollable Cursor SQL Statement
Comments
CLOSE-THISEMP.
EXEC SQL
CLOSE THISEMP
END-EXEC.
Related reference:
Removing rows from a table using the DELETE statement

To remove rows from a table, use the DELETE statement.
When you delete a row, you remove the entire row. The DELETE statement does not remove specific
columns from the row. The result of the DELETE statement is the removal of zero or more rows of a
table, depending on how many rows satisfy the search condition specified in the WHERE clause. If you
omit the WHERE clause from a DELETE statement, SQL removes all the rows from the table. The
DELETE statement looks like this:
DELETE FROM table-name
WHERE search-condition ...
For example, suppose that department D11 is moved to another site. You delete each row in the
CORPDATA.EMPLOYEE table with a WORKDEPT value of D11 as follows:
DELETE FROM CORPDATA.EMPLOYEE
The WHERE clause tells SQL which rows you want to delete from the table. SQL deletes all the rows that
satisfy the search condition from the base table. Deleting rows from a view deletes the rows from the
base table. You can omit the WHERE clause, but it is best to include one, because a DELETE statement
without a WHERE clause deletes all the rows from the table or view. To delete a table definition as well
as the table contents, issue the DROP statement.
If SQL finds an error while running your DELETE statement, it stops deleting data and returns a negative
SQLCODE. If you specify COMMIT(*ALL), COMMIT(*CS), COMMIT(*CHG), or COMMIT(*RR), no rows
in the table are deleted (rows already deleted by this statement, if any, are restored to their previous
values). If COMMIT(*NONE) is specified, any rows already deleted are not restored to their previous
values.
If SQL cannot find any rows that satisfy the search condition, an SQLCODE of +100 is returned.
Note: The DELETE statement may have deleted more than one row. The number of rows deleted is
reflected in SQLERRD(3) of the SQLCA. This value is also available from the ROW_COUNT
diagnostics item in the GET DIAGNOSTICS statement.
Related reference:
DROP
DELETE
116
Removing rows from tables with referential constraints

If a table has a primary key but no dependents, or if a table has only foreign keys but no primary key,
the DELETE statement operates the same way as it does for tables without referential constraints. If a
table has a primary key and dependent tables, the DELETE statement operates according to the delete
rules specified for the table.
All delete rules of all affected relationships must be satisfied in order for the delete operation to succeed.
If a referential constraint is violated, the DELETE operation fails.
The action to be taken on dependent tables when a DELETE is performed on a parent table depends on
the delete rule specified for the referential constraint. If no delete rule was defined, the DELETE NO
ACTION rule is used.
DELETE NO ACTION
Specifies that the row in the parent table can be deleted if no other row depends on it. If a
dependent row exists in the relationship, the DELETE fails. The check for dependent rows is
performed at the end of the statement.
DELETE RESTRICT
Specifies that the row in the parent table can be deleted if no other row depends on it. If a
dependent row exists in the relationship, the DELETE fails. The check for dependent rows is
performed immediately.
For example, you cannot delete a department from the department table if it is still responsible
for some project that is described by a dependent row in the project table.
DELETE CASCADE
Specifies that first the designated rows in the parent table are deleted. Then, the dependent rows
are deleted.
For example, you can delete a department by deleting its row in the department table. Deleting
the row from the department table also deletes:
v The rows for all departments that report to it
v All departments that report to those departments and so forth.
DELETE SET NULL
Specifies that each nullable column of the foreign key in each dependent row is set to its default
value. This means that the column is only set to its default value if it is a member of a foreign
key that references the row being deleted. Only the dependent rows that are immediate
descendents are affected.
DELETE SET DEFAULT
Specifies that each column of the foreign key in each dependent row is set to its default value.
This means that the column is only set to its default value if it is a member of a foreign key that
references the row being deleted. Only the dependent rows that are immediate descendants are
affected.
For example, you can delete an employee from the employee table (EMPLOYEE) even if the
employee manages some department. In that case, the value of MGRNO for each employee who
reported to the manager is set to blanks in the department table (DEPARTMENT). If some other
default value was specified on the create of the table, that value is used.
This is due to the REPORTS_TO_EXISTS constraint defined for the department table.
If a descendent table has a delete rule of RESTRICT or NO ACTION and a row is found such that a
descendant row cannot be deleted, the entire DELETE fails.
When running this statement with a program, the number of rows deleted is returned in SQLERRD(3) in
the SQLCA. This number includes only the number of rows deleted in the table specified in the DELETE
statement. It does not include those rows deleted according to the CASCADE rule. SQLERRD(5) in the
SQL programming
117
SQLCA contains the number of rows that were affected by referential constraints in all tables. The
SQLERRD(3) value is also available from the ROW_COUNT item in the GET DIAGNOSTICS statement.
The SQLERRD(5) value is available from the DB2_ROW_COUNT_SECONDARY item.
The subtle difference between RESTRICT and NO ACTION rules is easiest seen when looking at the
interaction of triggers and referential constraints. Triggers can be defined to fire either before or after an
operation (a DELETE statement, in this case). A before trigger fires before the DELETE is performed and
therefore before any checking of constraints. An after trigger is fired after the DELETE is performed, and
after a constraint rule of RESTRICT (where checking is performed immediately), but before a constraint
rule of NO ACTION (where checking is performed at the end of the statement). The triggers and rules
occur in the following order:
1. A before trigger is fired before the DELETE and before a constraint rule of RESTRICT or NO ACTION.
2. An after trigger is fired after a constraint rule of RESTRICT, but before a NO ACTION rule.
Example: DELETE rules:
Suppose that deleting a department from the DEPARTMENT table sets WORKDEPT in the EMPLOYEE
table to null for every employee assigned to that department.
Consider the following DELETE statement:
DELETE FROM CORPDATA.DEPARTMENT
WHERE DEPTNO = E11
Given the tables and the data in the DB2 for i sample tables on page 463, one row is deleted from table
DEPARTMENT, and table EMPLOYEE is updated to set the value of WORKDEPT to its default wherever
the value was 'E11'. A question mark ('?') in the following sample data reflects the null value. The results
appear as follows:
Table 31. DEPARTMENT table. Contents of the table after the DELETE statement is complete.
DEPTNO
DEPTNAME
MGRNO
ADMRDEPT
A00
SPIFFY COMPUTER SERVICE DIV.
000010
A00
B01
PLANNING
000020
A00
C01
INFORMATION CENTER
000030
A00
D01
DEVELOPMENT CENTER
A00
D11
000060
D01
D21
000070
D01
E01
SUPPORT SERVICES
000050
A00
E21
SOFTWARE SUPPORT
000100
E01
F22
BRANCH OFFICE F2
E01
G22
BRANCH OFFICE G2
E01
H22
BRANCH OFFICE H2
E01
I22
BRANCH OFFICE I2
E01
J22
BRANCH OFFICE J2
E01
Note that there were no cascaded delete operations in the DEPARTMENT table because no department
reported to department 'E11'.
Below are the snapshots of one affected portion of the EMPLOYEE table before and after the DELETE
statement is completed.
118
Table 32. Partial EMPLOYEE table. Partial contents before the DELETE statement.
EMPNO
FIRSTNME
MI
LASTNAME
WORKDEPT PHONENO
HIREDATE
000230
JAMES
JEFFERSON
D21
2094
1966-11-21
000240
SALVATORE
MARINO
D21
3780
1979-12-05
000250
DANIEL
SMITH
D21
0961
1960-10-30
000260
SYBIL
JOHNSON
D21
8953
1975-09-11
000270
MARIA
PEREZ
D21
9001
1980-09-30
000280
ETHEL
SCHNEIDER
E11
0997
1967-03-24
000290
JOHN
PARKER
E11
4502
1980-05-30
000300
PHILIP
SMITH
E11
2095
1972-06-19
000310
MAUDE
SETRIGHT
E11
3332
1964-09-12
000320
RAMLAL
MEHTA
E21
9990
1965-07-07
000330
WING
LEE
E21
2103
1976-02-23
000340
JASON
GOUNOT
E21
5696
1947-05-05
Table 33. Partial EMPLOYEE table. Partial contents after the DELETE statement.
EMPNO
FIRSTNME
MI
LASTNAME
WORKDEPT
PHONENO
HIREDATE
000230
JAMES
JEFFERSON
D21
2094
1966-11-21
000240
SALVATORE
MARINO
D21
3780
1979-12-05
000250
DANIEL
SMITH
D21
0961
1960-10-30
000260
SYBIL
JOHNSON
D21
8953
1975-09-11
000270
MARIA
PEREZ
D21
9001
1980-09-30
000280
ETHEL
SCHNEIDER
0997
1967-03-24
000290
JOHN
PARKER
4502
1980-05-30
000300
PHILIP
SMITH
2095
1972-06-19
000310
MAUDE
SETRIGHT
3332
1964-09-12
000320
RAMLAL
MEHTA
E21
9990
1965-07-07
000330
WING
LEE
E21
2103
1976-02-23
000340
JASON
GOUNOT
E21
5696
1947-05-05
Merging data
Use the MERGE statement to conditionally insert, update, or delete rows in a table or view.
|
|
|
You can use the MERGE statement to update a target table from another table, a derived table, or any
other table-reference. This other table is called the source table. The simplest form of a source table is a
list of values.
|
|
Based on whether or not a row from the source table exists in the target table, the MERGE statement can
insert a new row, or update or delete the matching row.
|
|
|
|
The most basic form of a MERGE statement is one where a new row is to be inserted if it doesn't already
exist, or updated if it does exist. Rather than attempting the insert or update and, based on the
SQLCODE or SQLSTATE, then trying the other option, by using the MERGE statement the appropriate
action will be performed.
SQL programming
119
|
|
|
|
|
|
|
|
|
|
In this example, you want to add or replace a row for a department. If the department does not already
exist, a row will be inserted. If the department does exist, information for the department will be
updated.
MERGE INTO DEPARTMENT USING
(VALUES (K22, BRANCH OFFICE K2, E01)) INSROW (DEPTNO, DEPTNAME, ADMRDEPT)
ON DEPARTMENT.DEPTNO = INSROW.DEPTNO
WHEN NOT MATCHED THEN
INSERT VALUES(INSROW.DEPTNO, INSROW.DEPTNAME, INSROW.ADMRDEPT)
WHEN MATCHED THEN
UPDATE SET DEPTNAME = INSROW.DEPTNAME, ADMRDEPT = INSROW.ASMRDEPT
| Suppose you have a temporary table that is a copy of the EMP_PHOTO table. In this table, you have
| added photo information for new employees and updated the photo for existing employees. The
| temporary table only contains changes, no rows for unchanged photo information.
|
|
|
|
|
|
|
|
|
To merge these updates into the master EMP_PHOTO table, you can use the following MERGE
statement.
|
|
|
|
|
|
|
|
When this statement is run, the rows in the target table are compared to the rows in the source table
using the EMPNO and PHOTO_FORMAT columns. These are the columns that make up the primary key
for the table, so they guarantee uniqueness. Any row that is in the source table that does not have a
matching EMPNO and PHOTO_FORMAT row in the target table (NOT MATCHED) will perform the
INSERT action. In this case, it will insert a new row into the target table containing the EMPNO,
PHOTO_FORMAT, and PICTURE values from the source table. Any row in the source table that already
has a corresponding row in the target table (MATCHED) will have the target table's row updated with
the PICTURE value from the source table.
MERGE INTO EMP_PHOTO target USING TEMP_EMP_PHOTO source

ON target.EMPNO = source.EMPNO
AND target.PHOTO_FORMAT = source.PHOTO_FORMAT
INSERT VALUES(EMPNO, PHOTO_FORMAT, PICTURE)
WHEN MATCHED THEN
UPDATE SET PICTURE = source.PICTURE
| To make the merge a little bit more complex, let's add a column to the EMP_PHOTO table.
| ALTER TABLE EMP_PHOTO ADD COLUMN LAST_CHANGED TIMESTAMP
|
GENERATED BY DEFAULT FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP
|
|
|
|
|
|
|
|
|
|
|
|
Now, let us assume that the person who maintains the TEMP_EMP_PHOTO table has some rows in the
temporary table that have already been merged into the master copy of the EMP_PHOTO table. When
doing the MERGE, you don't want to update the same rows again since the values have not changed. It
is also possible that someone else has updated the master EMP_PHOTO with a more recent picture.
MERGE INTO EMP_PHOTO target USING TEMP_EMP_PHOTO source
ON target.EMPNO = source.EMPNO
AND target.PHOTO_FORMAT = source.PHOTO_FORMAT
INSERT VALUES(EMPNO, PHOTO_FORMAT, PICTURE, LAST_CHANGED)
WHEN MATCHED AND target.LAST_CHANGED < source.LAST_CHANGED THEN
UPDATE SET PICTURE = source.PICTURE,
LAST_CHANGED = source.LAST_CHANGED
| This statement has an extra condition added to the MATCHED clause. Adding the comparison of the
| LAST_CHANGED column will prevent the master EMP_PHOTO table from being updated with a photo
| that has a timestamp older than the current master's timestamp.
Using subqueries
120
Conceptually, a subquery is evaluated whenever a new row or a group of rows must be processed. In
fact, if the subquery is the same for every row or group, it is evaluated only once. Subqueries like this are
said to be uncorrelated.
Some subqueries return different values from row to row or group to group. The mechanism that allows
this is called correlation, and the subqueries are said to be correlated.
Related reference:
Expressions in the WHERE clause on page 58
else.
Subqueries in SELECT statements

Subqueries further refine your search conditions in SELECT statements.
In simple WHERE and HAVING clauses, you can specify a search condition by using a literal value, a
column name, an expression, or a special register. In those search conditions, you know that you are
searching for a specific value. However, sometimes you cannot supply that value until you have retrieved
other data from a table. For example, suppose you want a list of the employee numbers, names, and job
codes of all employees working on a particular project, say project number MA2100. The first part of the
statement is easy to write:
SELECT EMPNO, LASTNAME, JOB
WHERE EMPNO ...
But you cannot go further because the CORPDATA.EMPLOYEE table does not include project number
data. You do not know which employees are working on project MA2100 without issuing another
SELECT statement against the CORPDATA.EMP_ACT table.
With SQL, you can nest one SELECT statement within another to solve this problem. The inner SELECT
statement is called a subquery. The SELECT statement surrounding the subquery is called the outer-level
SELECT. Using a subquery, you can issue just one SQL statement to retrieve the employee numbers,
names, and job codes for employees who work on the project MA2100:
WHERE EMPNO IN
(SELECT EMPNO
WHERE PROJNO = MA2100)
To better understand what will result from this SQL statement, imagine that SQL goes through the
following process:
Step 1: SQL evaluates the subquery to obtain a list of EMPNO values:
(SELECT EMPNO
WHERE PROJNO= MA2100)
The result in an interim result table follows.

000010
000110
SQL programming
121
Step 2: The interim result table then serves as a list in the search condition of the outer-level SELECT
statement. Essentially, this is the statement that is run:
WHERE EMPNO IN
(000010, 000110)
The final result table looks like this.

EMPNO
LASTNAME
JOB
000010
HAAS
PRES
000110
LUCCHESSI
SALESREP
Subqueries and search conditions:

A subquery can be part of a search condition. The search condition is in the form of operand operator
operand. Either operand can be a subquery.
In the following example, the first operand is EMPNO and operator is IN. The search condition can be
part of a WHERE or HAVING clause. The clause can include more than one search condition that
contains a subquery. A search condition that contains a subquery, like any other search condition, can be
enclosed in parentheses, can be preceded by the keyword NOT, and can be linked to other search
conditions through the keywords AND and OR. For example, the WHERE clause of a query can look
something like this:
WHERE
(subquery1) = X AND (Y > SOME (subquery2) OR Z = 100)
Subqueries can also appear in the search conditions of other subqueries. Such subqueries are said to be
nested at some level of nesting. For example, a subquery within a subquery within an outer-level
SELECT is nested at a nesting level of two. SQL allows nesting down to a nesting level of 32.
Usage notes on subqueries:
Here are some considerations for using subqueries to refine your search conditions.
1. When nesting SELECT statements, you can use as many as you need to satisfy your requirements (1
to 255 subqueries), although performance is slower for each additional subquery.
2. For predicates that use the keywords ALL, ANY, SOME, or EXISTS, the number of rows returned
from the subquery can vary from zero to many. For all other subqueries, the number of rows returned
must be zero or one.
3. For the following predicates, a row fullselect can be used for the subquery. This means that the
subquery can return more than one value for a row.
v Basic predicate with equal or not equal comparisons
v Quantified predicates using =ANY, =ALL, and =SOME
v IN and NOT IN predicates
If a row fullselect is used:
v The select list must not contain SELECT *. Explicit values must be specified.
v A row fullselect must be compared to a row expression. A row expression is a list of values
enclosed in parentheses. There must be the same number of values returned from the subquery as
there are in the row expression.
v The row expression for an IN or NOT IN predicate cannot contain an untyped parameter marker.
Use CAST to supply a result data type for these parameter markers.
v The subquery cannot contain UNION, EXCEPT, or INTERSECT or a correlated reference.
122
4. A subquery cannot include the ORDER BY, FOR READ ONLY, FETCH FIRST n ROWS, UPDATE, or
OPTIMIZE clause.
Including subqueries in the WHERE or HAVING clause:
You can include a subquery in a WHERE or HAVING clause by using a basic or quantified comparison,
the IN keyword, or the EXISTS keyword.
Basic comparisons
You can use a subquery before or after any of the comparison operators. The subquery can return only
one row. It can return multiple values for the row if the equal or not equal operators are used. SQL
compares each value from the subquery row with the corresponding value on the other side of the
comparison operator. For example, suppose that you want to find the employee numbers, names, and
salaries for employees whose education level is higher than the average education level throughout the
company.
SELECT EMPNO, LASTNAME, SALARY
WHERE EDLEVEL >
(SELECT AVG(EDLEVEL)
FROM CORPDATA.EMPLOYEE)
SQL first evaluates the subquery and then substitutes the result in the WHERE clause of the SELECT
statement. In this example, the result is the company-wide average educational level. Besides returning a
single row, a subquery can return no rows. If it does, the result of the compare is unknown.
Quantified comparisons (ALL, ANY, and SOME)
You can use a subquery after a comparison operator followed by the keyword ALL, ANY, or SOME.
When used in this way, the subquery can return zero, one, or many rows, including null values. You can
use ALL, ANY, and SOME in the following ways:
v Use ALL to indicate that the value you supplied must compare in the indicated way to ALL the rows
the subquery returns. For example, suppose you use the greater-than comparison operator with ALL:
... WHERE expression > ALL (subquery)
To satisfy this WHERE clause, the value of the expression must be greater than the result for each of
the rows (that is, greater than the highest value) returned by the subquery. If the subquery returns an
empty set (that is, no rows were selected), the condition is satisfied.
v Use ANY or SOME to indicate that the value you supplied must compare in the indicated way to at
least one of the rows the subquery returns. For example, suppose you use the greater-than comparison
operator with ANY:
... WHERE expression > ANY (subquery)
To satisfy this WHERE clause, the value in the expression must be greater than at least one of the rows
(that is, greater than the lowest value) returned by the subquery. If what the subquery returns is the
empty set, the condition is not satisfied.
Note: The results when a subquery returns one or more null values may surprise you, unless you are
familiar with formal logic.
IN keyword
You can use IN to say that the value in the expression must be among the rows returned by the
subquery. Using IN is equivalent to using =ANY or =SOME. Using ANY and SOME were previously
described. You can also use the IN keyword with the NOT keyword in order to select rows when the
value is not among the rows returned by the subquery. For example, you can use:
... WHERE WORKDEPT NOT IN (SELECT ...)
SQL programming
123
EXISTS keyword
In the subqueries presented so far, SQL evaluates the subquery and uses the result as part of the WHERE
clause of the outer-level SELECT. In contrast, when you use the keyword EXISTS, SQL checks whether
the subquery returns one or more rows. If it does, the condition is satisfied. If it returns no rows, the
condition is not satisfied. For example:
SELECT EMPNO,LASTNAME
WHERE EXISTS
(SELECT *
WHERE PRSTDATE > 1982-01-01);
In the example, the search condition is true if any project represented in the CORPDATA.PROJECT table
has an estimated start date that is later than January 1, 1982. This example does not show the full power
of EXISTS, because the result is always the same for every row examined for the outer-level SELECT. As
a consequence, either every row appears in the results, or none appear. In a more powerful example, the
subquery itself would be correlated, and change from row to row.
As shown in the example, you do not need to specify column names in the select-list of the subquery of
an EXISTS clause. Instead, you should code SELECT *.
You can also use the EXISTS keyword with the NOT keyword in order to select rows when the data or
condition you specify does not exist. You can use the following:
... WHERE NOT EXISTS (SELECT ...)
Correlated subqueries
A correlated subquery is a subquery that SQL might need to re-evaluate when it examines each new row
(the WHERE clause) or each group of rows (the HAVING clause) in the outer-level SELECT statement.
Correlated names and references:
A correlated reference can appear in a search condition in a subquery. The reference is always in the form
of X.C, where X is a correlation name and C is the name of a column in the table that X represents.
You can define a correlation name for any table appearing in a FROM clause. A correlation name
provides a unique name for a table in a query. The same table name can be used many times within a
query and its nested subselects. Specifying different correlation names for each table reference makes it
possible to uniquely designate which table a column refers to.
The correlation name is defined in the FROM clause of a query. This query can be the outer-level
SELECT, or any of the subqueries that contain the one with the reference. Suppose, for example, that a
query contains subqueries A, B, and C, and that A contains B and B contains C. Then a correlation name
used in C can be defined in B, A, or the outer-level SELECT. To define a correlation name, include the
correlation name after the table name. Leave one or more blanks between a table name and its correlation
name, and place a comma after the correlation name if it is followed by another table name. The
following FROM clause defines the correlation names TA and TB for the tables TABLEA and TABLEB,
and no correlation name for the table TABLEC.
FROM TABLEA TA, TABLEC, TABLEB TB
Any number of correlated references can appear in a subquery. For example, one correlated name in a
search condition can be defined in the outer-level SELECT, while another can be defined in a containing
subquery.
Before the subquery is executed, a value from the referenced column is always substituted for the
correlated reference.
124
Example: Correlated subquery in a WHERE clause:

Suppose that you want a list of all the employees whose education levels are higher than the average
education levels in their respective departments. To get this information, SQL must search the
CORPDATA.EMPLOYEE table.
For each employee in the table, SQL needs to compare the employee's education level to the average
education level for the employee's department. In the subquery, you tell SQL to calculate the average
education level for the department number in the current row. For example:
SELECT EMPNO, LASTNAME, WORKDEPT, EDLEVEL
FROM CORPDATA.EMPLOYEE X
WHERE EDLEVEL >
WHERE WORKDEPT = X.WORKDEPT)
A correlated subquery looks like an uncorrelated one, except for the presence of one or more correlated
references. In the example, the single correlated reference is the occurrence of X.WORKDEPT in the
subselect's FROM clause. Here, the qualifier X is the correlation name defined in the FROM clause of the
outer SELECT statement. In that clause, X is introduced as the correlation name of the table
CORPDATA.EMPLOYEE.
Now, consider what happens when the subquery is executed for a given row of CORPDATA.EMPLOYEE.
Before it is executed, the occurrence of X.WORKDEPT is replaced with the value of the WORKDEPT
column for that row. Suppose, for example, that the row is for CHRISTINE I HAAS. Her work
department is A00, which is the value of WORKDEPT for this row. The subquery executed for this row
is:
WHERE WORKDEPT = A00)
Thus, for the row considered, the subquery produces the average education level of Christine's
department. This is then compared in the outer statement to Christine's own education level. For some
other row for which WORKDEPT has a different value, that value appears in the subquery in place of
A00. For example, for the row for MICHAEL L THOMPSON, this value is B01, and the subquery for his
row delivers the average education level for department B01.
The result table produced by the query has the following values.
Table 34. Result set for previous query
EMPNO
LASTNAME
WORKDEPT
EDLEVEL
000010
HAAS
A00
18
000030
KWAN
C01
20
000070
PULASKI
D21
16
000090
HENDERSON
E11
16
000110
LUCCHESSI
A00
19
000160
PIANKA
D11
17
000180
SCOUTTEN
D11
17
000210
JONES
D11
17
000220
LUTZ
D11
18
000240
MARINO
D21
17
000260
JOHNSON
D21
16
SQL programming
125
Table 34. Result set for previous query (continued)

EMPNO
LASTNAME
WORKDEPT
EDLEVEL
000280
SCHNEIDER
E11
17
000320
MEHTA
E21
16
000340
GOUNOT
E21
16
200010
HEMMINGER
A00
18
200220
JOHN
D11
18
200240
MONTEVERDE
D21
17
200280
SCHWARTZ
E11
17
200340
ALONZO
E21
16
Example: Correlated subquery in a HAVING clause:

Suppose that you want a list of all the departments whose average salaries are higher than the average
salaries of their areas (all departments whose WORKDEPT begins with the same letter belong to the same
area). To get this information, SQL must search the CORPDATA.EMPLOYEE table.
For each department in the table, SQL compares the department's average salary to the average salary of
the area. In the subquery, SQL calculates the average salary for the area of the department in the current
group. For example:
SELECT WORKDEPT, DECIMAL(AVG(SALARY),8,2)
FROM CORPDATA.EMPLOYEE X
GROUP BY WORKDEPT
HAVING AVG(SALARY) >
(SELECT AVG(SALARY)
WHERE SUBSTR(X.WORKDEPT,1,1) = SUBSTR(WORKDEPT,1,1))
Consider what happens when the subquery is executed for a given department of
CORPDATA.EMPLOYEE. Before it is executed, the occurrence of X.WORKDEPT is replaced with the
value of the WORKDEPT column for that group. Suppose, for example, that the first group selected has
A00 for the value of WORKDEPT. The subquery executed for this group is:
(SELECT AVG(SALARY)
WHERE SUBSTR(A00,1,1) = SUBSTR(WORKDEPT,1,1))
Thus, for the group considered, the subquery produces the average salary for the area. This value is then
compared in the outer statement to the average salary for department 'A00'. For some other group for
which WORKDEPT is 'B01', the subquery results in the average salary for the area where department B01
belongs.
The result table produced by the query has the following values.
WORKDEPT
AVG SALARY
D21
25668.57
E01
40175.00
E21
24086.66
126
Example: Correlated subquery in a select-list:

Suppose that you want a list of all the departments, including the department name, number, and
manager's name.
Department names and numbers are found in the CORPDATA.DEPARTMENT table. However,
DEPARTMENT has only the manager's number, not the manager's name. To find the name of the
manager for each department, you need to find the employee number from the EMPLOYEE table that
matches the manager number in the DEPARTMENT table and return the name for the row that matches.
Only departments that currently have managers assigned are to be returned. Execute the following SQL
statement:
SELECT DEPTNO, DEPTNAME,
(SELECT FIRSTNME CONCAT CONCAT
MIDINIT CONCAT CONCAT LASTNAME
FROM EMPLOYEE X
WHERE X.EMPNO = Y.MGRNO) AS MANAGER_NAME
FROM DEPARTMENT Y
WHERE MGRNO IS NOT NULL
For each row returned for DEPTNO and DEPTNAME, the system finds where EMPNO = MGRNO and
returns the manager's name. The result table produced by the query has the following values.
Table 35. Result set for previous query
DEPTNO
DEPTNAME
MANAGER_NAME
A00
SPIFFY COMPUTER SERVICE DIV.
CHRISTINE I HAAS
B01
PLANNING
MICHAEL L THOMPSON
C01
INFORMATION CENTER
SALLY A KWAN
D11
IRVING F STERN
D21
EVA D PULASKI
E01
SUPPORT SERVICES
JOHN B GEYER
E11
OPERATIONS
EILEEN W HENDERSON
E21
SOFTWARE SUPPORT
THEODORE Q SPENSER
Example: Correlated subquery in an UPDATE statement:

When you use a correlated subquery in an UPDATE statement, the correlation name refers to the rows
that you want to update.
For example, when all activities of a project must be completed before September 1983, your department
considers that project to be a priority project. You can use the following SQL statement to evaluate the
projects in the CORPDATA.PROJECT table, and write a 1 (a flag to indicate PRIORITY) in the PRIORITY
column (a column you added to CORPDATA.PROJECT for this purpose) for each priority project.
UPDATE CORPDATA.PROJECT X
SET PRIORITY = 1
WHERE 1983-09-01 >
(SELECT MAX(EMENDATE)
WHERE PROJNO = X.PROJNO)
As SQL examines each row in the CORPDATA.EMPPROJACT table, it determines the maximum activity
end date (EMENDATE) for all activities of the project (from the CORPDATA.PROJECT table). If the end
date of each activity associated with the project is before September 1983, the current row in the
CORPDATA.PROJECT table qualifies and is updated.
SQL programming
127
Update the master order table with any changes to the quantity ordered. If the quantity in the orders
table is not set (the NULL value), keep the value that is in the master order table.
UPDATE MASTER_ORDERS X
SET QTY=(SELECT COALESCE (Y.QTY, X.QTY)
FROM ORDERS Y
WHERE X.ORDER_NUM = Y.ORDER_NUM)
WHERE X.ORDER_NUM IN (SELECT ORDER_NUM
FROM ORDERS)
In this example, each row of the MASTER_ORDERS table is checked to see if it has a corresponding row
in the ORDERS table. If it does have a matching row in the ORDERS table, the COALESCE function is
used to return a value for the QTY column. If QTY in the ORDERS table has a non-null value, that value
is used to update the QTY column in the MASTER_ORDERS table. If the QTY value in the ORDERS table
is NULL, the MASTER_ORDERS QTY column is updated with its own value.
Example: Correlated subquery in a DELETE statement:
When you use a correlated subquery in a DELETE statement, the correlation name represents the row
that you want to delete. SQL evaluates the correlated subquery once for each row in the table named in
the DELETE statement to decide whether to delete the row.
Suppose that a row in the CORPDATA.PROJECT table is deleted. Rows related to the deleted project in
the CORPDATA.EMPPROJACT table must also be deleted. To do this, run the following statement:
DELETE FROM CORPDATA.EMPPROJACT X
WHERE NOT EXISTS
(SELECT *
WHERE PROJNO = X.PROJNO)
SQL determines, for each row in the CORPDATA.EMP_ACT table, whether a row with the same project
number exists in the CORPDATA.PROJECT table. If not, the CORPDATA.EMP_ACT row is deleted.
Sort sequences and normalization in SQL

The sort sequence is used for all character, and UCS-2 and UTF-16 graphic comparisons performed in
SQL statements. There are sort sequence tables for both single byte and double byte character data. Each
single byte sort sequence table has an associated double-byte sort sequence table, and vice versa.
Conversion between the two tables is performed when necessary to implement a query. In addition, the
CREATE INDEX statement has the sort sequence (in effect at the time the statement was run) applied to
the character columns referred to in the index.
Related reference:
statement.
Creating indexes on page 53
You can use indexes to sort and select data. In addition, indexes help the system retrieve data faster for
better query performance.
update, or delete.
GROUP BY clause on page 60
rows.
128
HAVING clause on page 62

The HAVING clause specifies a search condition for the groups selected by the GROUP BY clause.
ORDER BY clause on page 63
Handling duplicate rows on page 69
When SQL evaluates a select-statement, several rows might qualify to be in the result table, depending on
the number of rows that satisfy the search condition of the select-statement. Some of the rows in the
result table might be duplicate.
Using the UNION keyword to combine subselects on page 95
Collating sequence
Sort sequence used with ORDER BY and row selection

The examples show how rows are ordered and selected for the sort sequence used.
The values in the JOB column are in mixed case. You can see the values 'Mgr', 'MGR', and 'mgr'.
Table 36. The STAFF table
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
10
Sanders
20
Mgr
18357.50
20
Pernal
20
Sales
18171.25
612.45
30
Merenghi
38
MGR
17506.75
40
OBrien
38
Sales
18006.00
846.55
50
Hanes
15
Mgr
10
20659.80
60
Quigley
38
SALES
16808.30
650.25
70
Rothman
15
Sales
16502.83
1152.00
80
James
20
Clerk
13504.60
128.20
90
Koonitz
42
sales
18001.75
1386.70
100
Plotz
42
mgr
18352.80
In the following examples, the results are shown for each statement using:
v *HEX sort sequence
v Shared-weight sort sequence using the language identifier ENU
v Unique-weight sort sequence using the language identifier ENU
Note: ENU is chosen as a language identifier by specifying either SRTSEQ(*LANGIDUNQ), or
SRTSEQ(*LANGIDSHR) and LANGID(ENU), on the CRTSQLxxx, STRSQL, or RUNSQLSTM
commands, or by using the SET OPTION statement.
Sort sequence and ORDER BY

Sort sequences affect ordering done by the ORDER BY clause.
The following SQL statement causes the result table to be sorted using the values in the JOB column:
SELECT * FROM STAFF ORDER BY JOB
SQL programming
129
The following table shows the result using a *HEX sort sequence. The rows are sorted based on the
EBCDIC value in the JOB column. In this case, all lowercase letters sort before the uppercase letters.
Table 37. Result of using the *HEX sort sequence
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
100
Plotz
42
mgr
18352.80
90
Koonitz
42
sales
18001.75
1386.70
80
James
20
Clerk
13504.60
128.20
10
Sanders
20
Mgr
18357.50
50
Hanes
15
Mgr
10
20659.80
30
Merenghi
38
MGR
17506.75
20
Pernal
20
Sales
18171.25
612.45
40
OBrien
38
Sales
18006.00
846.55
70
Rothman
15
Sales
16502.83
1152.00
60
Quigley
38
SALES
16808.30
650.25
The following table shows how sorting is done for a unique-weight sort sequence. After the sort sequence
is applied to the values in the JOB column, the rows are sorted. Notice that after the sort, lowercase
letters are before the same uppercase letters, and the values 'mgr', 'Mgr', and 'MGR' are adjacent to each
other.
Table 38. Result of using the unique-weight sort sequence for the ENU language identifier
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
80
James
20
Clerk
13504.60
128.20
100
Plotz
42
mgr
18352.80
10
Sanders
20
Mgr
18357.50
50
Hanes
15
Mgr
10
20659.80
30
Merenghi
38
MGR
17506.75
90
Koonitz
42
sales
18001.75
1386.70
20
Pernal
20
Sales
18171.25
612.45
40
OBrien
38
Sales
18006.00
846.55
70
Rothman
15
Sales
16502.83
1152.00
60
Quigley
38
SALES
16808.30
650.25
The following table shows how sorting is done for a shared-weight sort sequence. After the sort sequence
is applied to the values in the JOB column, the rows are sorted. For the sort comparison, each lowercase
letter is treated the same as the corresponding uppercase letter. In this table, notice that all the values
'MGR', 'mgr' and 'Mgr' are mixed together.
Table 39. Result of using the shared-weight sort sequence for the ENU language identifier
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
80
James
20
Clerk
13504.60
128.20
10
Sanders
20
Mgr
18357.50
30
Merenghi
38
MGR
17506.75
50
Hanes
15
Mgr
10
20659.80
100
Plotz
42
mgr
18352.80
130
Table 39. Result of using the shared-weight sort sequence for the ENU language identifier (continued)
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
20
Pernal
20
Sales
18171.25
612.45
40
OBrien
38
Sales
18006.00
846.55
60
Quigley
38
SALES
16808.30
650.25
70
Rothman
15
Sales
16502.83
1152.00
90
Koonitz
42
sales
18001.75
1386.70
Sort sequence and row selection

Sort sequences affect selection of data.
The following SQL statement selects rows with the value 'MGR' in the JOB column:
SELECT * FROM STAFF WHERE JOB=MGR
The first table shows how row selection is done with a *HEX sort sequence. The rows that match the row
selection criteria for the column JOB are selected exactly as specified in the select statement. Only the
uppercase 'MGR' is selected.
Table 40. Result of using the *HEX sort sequence
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
30
Merenghi
38
MGR
17506.75
Table 2 shows how row selection is done with a unique-weight sort sequence. The lowercase and
uppercase letters are treated as unique. The lowercase 'mgr' is not treated the same as uppercase 'MGR'.
Therefore, the lowercase 'mgr' is not selected.
Table 41. Result of using unique-weight sort sequence for the ENU language identifier
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
30
Merenghi
38
MGR
17506.75
The following table shows how row selection is done with a shared-weight sort sequence. The rows that
match the row selection criteria for the column 'JOB' are selected by treating uppercase letters the same as
lowercase letters. Notice that all the values 'mgr', 'Mgr' and 'MGR' are selected.
Table 42. Result of using the shared-weight sort sequence for the ENU language identifier
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
10
Sanders
20
Mgr
18357.50
30
Merenghi
38
MGR
17506.75
50
Hanes
15
Mgr
10
20659.80
100
Plotz
42
mgr
18352.80
Sort sequence and views

Views are created with the sort sequence that is in effect when the CREATE VIEW statement is run.
When the view is referred to in a FROM clause, that sort sequence is used for any character comparisons
in the subselect of the CREATE VIEW. At that time, an intermediate result table is produced from the
view subselect. The sort sequence in effect when the query is being run is then applied to all the
SQL programming
131
character and UCS-2 graphic comparisons (including those comparisons involving implicit conversions to
character, or UCS-2 or UTF-16 graphic) specified in the query.
The following SQL statements and tables show how views and sort sequences work. View V1, used in the
following examples, was created with a shared-weight sort sequence of SRTSEQ(*LANGIDSHR) and
LANGID(ENU). The CREATE VIEW statement is as follows:
CREATE VIEW V1 AS SELECT *
FROM STAFF
WHERE JOB = MGR AND ID < 100
Table 43. "SELECT * FROM V1"
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
10
Sanders
20
Mgr
18357.50
30
Merenghi
38
MGR
17506.75
50
Hanes
15
Mgr
10
20659.80
Any queries run against view V1 are run against the result table shown above. The query shown below is
run with a sort sequence of SRTSEQ(*LANGIDUNQ) and LANGID(ENU).
Table 44. "SELECT * FROM V1 WHERE JOB = 'MGR'" using the unique-weight sort sequence for ENU language
identifier
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
30
Merenghi
38
MGR
17506.75
Sort sequence and the CREATE INDEX statement

Indexes are created with the sort sequence that is in effect when the CREATE INDEX statement is run.
An entry is added to the index every time an insert is made into the table over which the index is
defined. Index entries contain the weighted value for character key, and UCS-2 and UTF-16 graphic key
columns. The system gets the weighted value by converting the key value based on the sort sequence of
the index.
When selection is made using that sort sequence and that index, the character, or UCS-2 or UTF-16
graphic keys do not need to be converted before comparison. This improves the performance of the
query.
Related concepts:
Using indexes with sort sequence
Sort sequence and constraints

Unique constraints are implemented with indexes. If the table on which a unique constraint is added is
defined with a sort sequence, the index is created with the same sort sequence.
If defining a referential constraint, the sort sequence between the parent and dependent table must match.
The sort sequence used at the time a check constraint is defined is the same sort sequence the system
uses to validate adherence to the constraint at the time of an INSERT or UPDATE.
ICU sort sequence

When an International Components for Unicode (ICU) sort sequence table is used, the database uses the
language-specific rules to determine the weight of the data based on the locale of the table.
132
An ICU sort sequence table named en_us (United States locale) can sort data differently than another ICU
table named fr_FR (French locale) for example.
The ICU support (IBM i option 39) properly handles data that is not normalized, producing the same
results as if the data were normalized. The ICU sort sequence table can sort all character, graphic, and
Unicode (UTF-8, UTF-16 and UCS-2) data.
For example, a UTF-8 character column named NAME contains the following names (the hex values of
the column are given as well).
NAME
HEX (NAME)
Gmez
47C3B36D657A
Gomer
476F6D6572
Gumby
47756D6279
A *HEX sort sequence orders the NAME values as follows.

NAME
Gomer
Gumby
Gmez
An ICU sort sequence table named en_us correctly orders the NAME values as follows.
NAME
Gomer
Gmez
Gumby
When an ICU sort sequence table is specified, the performance of SQL statements that use the table can
be much slower than the performance of SQL statements that use a non-ICU sort sequence table or use a
*HEX sort sequence. The slower performance results from calling the ICU support to get the weighted
value for each piece of data that needs to be sorted. An ICU sort sequence table can provide more sorting
function but at the cost of slower running SQL statements. However, indexes created with an ICU sort
sequence table can be created over columns to help reduce the need of calling the ICU support. In this
case, the index key already contains the ICU weighted value, so there is no need to call the ICU support.
Related concepts:
International Components for Unicode
Normalization
Normalization allows you to compare strings that contain combining characters.
Data tagged with a UTF-8 or UTF-16 CCSID can contain combining characters. Combining characters
allow a resulting character to be composed of more than one character. After the first character of the
compound character, one of many different non-spacing characters such as umlauts and accents can
follow in the data string. If the resulting character is one that is already defined in the character set,
normalization of the string results in multiple combining characters being replaced by the value of the
defined character. For example, if your string contained the letter 'a' followed by an '..', the string is
normalized to contain the single character ''.
SQL programming
133
Normalization makes it possible to accurately compare strings. If data is not normalized, two strings that
look identical on the display may not compare equal since the stored representation can be different.
When UTF-8 and UTF-16 string data is not normalized, it is possible that a column in a table can have
one row with the letter 'a' followed by the umlaut character and another row with the combined ''
character. These two values are not both compare equal in a comparison predicate: WHERE C1 = ''. For
this reason, it is recommended that all string columns in a table are stored in normalized form.
You can normalize the data yourself before inserting or updating it, or you can define a column in a table
to be automatically normalized by the database. To have the database perform the normalization, specify
NORMALIZED as part of the column definition. This option is only allowed for columns that are tagged
with a CCSID of 1208 (UTF-8) or 1200 (UTF-16). The database assumes all columns in a table have been
normalized.
The NORMALIZED clause can also be specified for function and procedure parameters. If it is specified
for an input parameter, the normalization will be done by the database for the parameter value before
invoking the function or procedure. If it is specified for an output parameter, the clause is not enforced; it
is assumed that the user's routine code will return a normalized value.
The NORMALIZE_DATA option in the QAQQINI file is used to indicate whether the system is to
perform normalization when working with UTF-8 and UTF-16 data. This option controls whether the
system will normalize literals, host variables, parameter markers, and expressions that combine strings
before using them in SQL. The option is initialized to not perform normalization. This is the correct value
for you if the data in your tables and any literal values in your applications is always normalized already
through some other mechanism or never contains characters which will need to be normalized. If this is
the case, you will want to avoid the overhead of system normalization in your query. If your data is not
already normalized, you will want to switch the value of this option to have the system perform
normalization for you.
Related tasks:
Controlling queries dynamically with the query options file QAQQINI
Data protection
The DB2 for i database provides various methods for protecting SQL data from unauthorized users and
for ensuring data integrity.
Security for SQL objects

All objects on the system, including SQL objects, are managed by the system security function.
Users can authorize SQL objects through either the SQL GRANT and REVOKE statements or the Edit
Object Authority (EDTOBJAUT), Grant Object Authority (GRTOBJAUT), and Revoke Object Authority
(RVKOBJAUT) CL commands.
|
|
|
|
|
The SQL GRANT and REVOKE statements operate on SQL functions, SQL packages, SQL procedures,
distinct types, array types, sequences, variables, tables, views, XSR objects, and the individual columns of
tables and views. Furthermore, SQL GRANT and REVOKE statements only grant private and public
authorities. In some cases, it is necessary to use EDTOBJAUT, GRTOBJAUT, and RVKOBJAUT to
authorize users to other objects, such as commands and programs.
The authority checked for SQL statements depends on whether the statement is static, dynamic, or being
run interactively.
For static SQL statements:
v If the USRPRF value is *USER, the authority to run the SQL statement locally is checked using the user
profile of the user running the program. The authority to run the SQL statement remotely is checked
using the user profile at the application server. *USER is the default for system (*SYS) naming.
134
v If the USRPRF value is *OWNER, the authority to run the SQL statement locally is checked using the
user profiles of the user running the program and of the owner of the program. The authority to run
the SQL statement remotely is checked using the user profiles of the application server job and the
owner of the SQL package. The higher authority is the authority that is used. *OWNER is the default
for SQL (*SQL) naming.
For dynamic SQL statements:
v If the USRPRF value is *USER, the authority to run the SQL statement locally is checked using the user
profile of the person running the program. The authority to run the SQL statement remotely is checked
using the user profile of the application server job.
v If the USRPRF value is *OWNER and DYNUSRPRF is *USER, the authority to run the SQL statement
locally is checked using the user profile of the person running the program. The authority to run the
SQL statement remotely is checked using the user profile of the application server job.
v If the USRPRF value is *OWNER and DYNUSRPRF is *OWNER, the authority to run the SQL
statement locally is checked using the user profiles of the user running the program and the owner of
the program. The authority to run the SQL statement remotely is checked using the user profiles of the
application server job and the owner of the SQL package. The highest authority is the authority that is
used. Because of security concerns, you should use the *OWNER parameter value for DYNUSRPRF
carefully. This option gives the access authority of the owner program or package to those who run the
program.
For interactive SQL statements, authority is checked against the authority of the person processing the
statement. Adopted authority is not used for interactive SQL statements.
Related reference:
Security reference
GRANT (Table or View Privileges)
REVOKE (Table or View Privileges)
Authorization ID
An authorization ID is a user profile object that identifies a unique user. You can use the Create User
Profile (CRTUSRPRF) command to create an authorization ID.
Views
Views can prevent unauthorized users from having access to sensitive data.
The application program can access the data it needs in a table, without having access to sensitive or
restricted data in the table. A view can restrict access to particular columns by not specifying those
columns in the SELECT list (for example, employee salaries). A view can also restrict access to particular
rows in a table by specifying a WHERE clause (for example, allowing access only to the rows associated
with a particular department number).
Auditing
The DB2 for i database is designed to comply with the U.S. government C2 security level. A key feature
of the C2 level is the ability to perform auditing on the system.
DB2 for i uses the audit facilities that are managed by the system security function. Auditing can be
performed at an object level, a user level, or a system level. The system value QAUDCTL controls
whether auditing is performed at the object or user level. The Change User Audit (CHGUSRAUD) and
Change Object Audit (CHGOBJAUD) commands specify which users and objects are audited. The system
value QAUDLVL controls what types of actions are audited (for example, authorization failures; and
create, delete, grant, or revoke operations).
DB2 for i can also audit row changes through the DB2 for i journal support.
SQL programming
135
In some cases, entries in the auditing journal will not be in the same order as they occured. For example,
a job that is running under commitment control deletes a table, creates a new table with the same name
as the one that was deleted, then does a commit. This will be recorded in the auditing journal as a create
followed by a delete. This is because objects that are created are journaled immediately. An object that is
deleted under commitment control is hidden and not actually deleted until a commit is done. Once the
commit is done, the action is journaled.
Related reference:
Security reference
Data integrity
Data integrity protects data from being destroyed or changed by unauthorized persons, system operation
or hardware failures (such as physical damage to a disk), programming errors, interruptions before a job
is completed (such as a power failure), or interference from running applications at the same time (such
as serialization problems).
Related reference:
XA APIs
Concurrency
Concurrency is the ability for multiple users to access and change data in the same table or view at the
same time without risk of losing data integrity.
This ability is automatically supplied by the DB2 for i database manager. Locks are implicitly acquired on
tables and rows to protect concurrent users from changing the same data at precisely the same time.
Typically, DB2 for i acquires locks on rows to ensure integrity. However, some situations require DB2 for i
to acquire a more exclusive table-level lock instead of row locks.
For example, an update (exclusive) lock on a row currently held by one cursor can be acquired by
another cursor in the same program (or in a DELETE or UPDATE statement not associated with the
cursor). This will prevent a positioned UPDATE or positioned DELETE statement that references the first
cursor until another FETCH is performed. A read (shared no-update) lock on a row currently held by one
cursor will not prevent another cursor in the same program (or DELETE or UPDATE statement) from
acquiring a lock on the same row.
Default and user-specifiable lock-wait timeout values are supported. DB2 for i creates tables, views, and
indexes with the default record wait time (60 seconds) and the default file wait time (*IMMED). This lock
wait time is used for data manipulation language (DML) statements. You can change these values by
using the CL commands Change Physical File (CHGPF), Change Logical File (CHGLF), and Override
Database File (OVRDBF).
The lock wait time used for all data definition language (DDL) statements and the LOCK TABLE
statement is the job default wait time (DFTWAIT). You can change this value by using the CL command
Change Job (CHGJOB) or Change Class (CHGCLS).
If a large record wait time is specified, deadlock detection is provided. For example, assume that one job
has an exclusive lock on row 1 and another job has an exclusive lock on row 2. If the first job attempts to
lock row 2, it waits because the second job is holding the lock. If the second job then attempts to lock
row 1, DB2 for i detects that the two jobs are in a deadlock and an error is returned to the second job.
You can explicitly prevent other users from using a table at the same time by using the SQL LOCK
TABLE statement. Using COMMIT(*RR) will also prevent other users from using a table during a unit of
work.
To improve performance, DB2 for i frequently leaves the open data path (ODP) open. This performance
feature also leaves a lock on tables referenced by the ODP, but does not leave any locks on rows. A lock
136
left on a table might prevent another job from performing an operation on that table. In most cases,
however, DB2 for i can detect that other jobs are holding locks and events can be signalled to those jobs.
The event causes DB2 for i to close any ODPs (and release the table locks) that are associated with that
table and are currently only open for performance reasons.
Note: The lock wait timeout must be large enough for the events to be signalled and the other jobs to
close the ODPs, or an error is returned.
Unless the LOCK TABLE statement is used to acquire table locks, or either COMMIT(*ALL) or
COMMIT(*RR) is used, data which has been read by one job can be immediately changed by another job.
Typically, the data that is read at the time the SQL statement is executed and therefore it is very current
(for example, during FETCH). In the following cases, however, data is read before the execution of the
SQL statement and therefore the data may not be current (for example, during OPEN).
v ALWCPYDTA(*OPTIMIZE) was specified and the optimizer determined that making a copy of the data
performs better than not making a copy.
v Some queries require the database manager to create a temporary result table. The data in the
temporary result table does not reflect changes that are made after the cursor was opened. For
information about when a temporary result table is created, see DECLARE CURSOR in the SQL
reference topic collection.
v A basic subquery is evaluated when the query is opened.
|
|
The concurrent access resolution option can be used to minimize transaction wait time. This option
directs the database manager on how to handle record lock conflicts under certain isolation levels.
The concurrent access resolution option can have one of the following values:
|
|
|
|
|
Wait for outcome

This is the default. This value directs the database manager to wait for the commit or rollback
when encountering locked data that is in the process of being updated or deleted. Locked rows
that are in the process of being inserted are not skipped. This option does not apply for read-only
queries running under COMMIT(*NONE) or COMMIT(*CHG).
|
|
|
|
|
Use currently committed

This value allows the database manager to use the currently committed version of the data for
read-only queries when encountering locked data in the process of being updated or deleted.
Locked rows in the process of being inserted can be skipped. This option applies where possible
when running under COMMIT(*CS) and is ignored otherwise.
|
|
|
Skip locked data

This value directs the database manager to skip rows in the case of record lock conflicts. This
option applies only when the query is running under COMMIT(*CS) or COMMIT(*ALL).
|
|
|
The concurrent access resolution values of USE CURRENTLY COMMITTED and SKIP LOCKED DATA
can be used to improve concurrency by avoiding lock waits. However, care must be used when using
these options because they might affect application functionality.
|
|
|
|
|
|
The concurrent access resolution value can be specified:

v With the concurrent-access-resolution clause at the statement level for a select-statement, SELECT INTO,
searched UPDATE, or searched DELETE.
v By using the CONACC keyword on the CRTSQLxxx or RUNSQLSTM commands.
v With the CONACC value in the SET OPTION statement.
v In the attribute-string of a PREPARE statement.
|
|
If the concurrent access resolution option is not directly set by the application, it takes on the value of the
SQL_CONCURRENT_ACCESS_RESOLUTION option in the QAQQINI query options file.
Related reference:
SQL programming
137
LOCK TABLE
Journaling
The DB2 for i journal support provides an audit trail and forward and backward recovery.
Forward recovery can be used to take an older version of a table and apply the changes logged on the
journal to the table. Backward recovery can be used to remove changes logged on the journal from the
table.
When an SQL schema is created, a journal and journal receiver are created in the schema. When SQL
creates the journal and journal receiver, they are only created on a user auxiliary storage pool (ASP) if the
ASP clause is specified on the CREATE SCHEMA statement. However, because placing journal receivers
on their own ASPs can improve performance, the person managing the journal might want to create all
future journal receivers on a separate ASP.
When a table is created into the schema, it is automatically journaled to the journal that DB2 for i created
in the schema (QSQJRN). A table created in a library also has journaling started if a journal named
QSQJRN exists in that library. After this point, it is your responsibility to use the journal functions to
manage the journal, the journal receivers, and the journaling of tables to the journal. For example, if a
table is moved into a schema, no automatic change to the journaling status occurs. If a table is restored,
the normal journal rules apply. That is, if the table was journaled at save time, it is journaled to the same
journal at restore time. If the table was not journaled at save time, it is not journaled at restore time.
The journal created in the SQL schema is normally the journal used for logging all changes to SQL tables.
You can, however, use the system journal functions to journal SQL tables to a different journal.
A user can stop journaling on any table using the journal functions, but doing so prevents an application
from running under commitment control. If journaling is stopped on a parent table of a referential
constraint with a delete rule of NO ACTION, CASCADE, SET NULL, or SET DEFAULT, all update and
delete operations will be prevented. Otherwise, an application is still able to function if you have
specified COMMIT(*NONE); however, this does not provide the same level of integrity that journaling
and commitment control provide.
Related concepts:
Journal management
Related reference:
Updating tables with referential constraints on page 113
If you are updating a parent table, you cannot modify a primary key for which dependent rows exist.
Commitment control
The DB2 for i commitment control support provides a means for processing a group of database changes,
such as update, insert, or delete operations or data definition language (DDL) operations, as a single unit
of work (also referred to as a transaction).
A commit operation guarantees that the group of operations is completed. A rollback operation
guarantees that the group of operations is backed out. A savepoint can be used to break a transaction into
smaller units that can be rolled back. A commit operation can be issued through several different
interfaces. For example,
v An SQL COMMIT statement
v A CL COMMIT command
v A language commit statement (such as an RPG COMMIT statement)
A rollback operation can be issued through several different interfaces. For example,
v An SQL ROLLBACK statement
v A CL ROLLBACK command
138
v A language rollback statement (such as an RPG ROLBK statement)

The only SQL statements that cannot be committed or rolled back are:
v DROP SCHEMA
v GRANT or REVOKE if an authority holder exists for the specified object
If commitment control was not already started when either an SQL statement is run with an isolation
level other than COMMIT(*NONE) or a RELEASE statement is run, then DB2 for i sets up the
commitment control environment by implicitly calling the CL command Start Commitment Control
(STRCMTCTL). DB2 for i specifies the NFYOBJ(*NONE) and CMTSCOPE(*ACTGRP) parameters, along
with the LCKLVL parameter, on the STRCMTCTL command. The LCKLVL parameter specified is the lock
level on the COMMIT parameter of the Create SQL (CRTSQLxxx), Start SQL Interactive Session
(STRSQL), or Run SQL Statements (RUNSQLSTM) command. In REXX, the LCKLVL parameter specified
is the lock level on the SET OPTION statement. You can use the STRCMTCTL command to specify a
different CMTSCOPE, NFYOBJ, or LCKLVL parameter. If you specify CMTSCOPE(*JOB) to start the
job-level commitment definition, DB2 for i uses the job-level commitment definition for programs in that
activation group.
Notes:
v When commitment control is used, the tables that are referred to in the application program by
data manipulation language (DML) statements must be journaled.
v The LCKLVL parameter specified is only the default lock level. After commitment control is
started, the SET TRANSACTION SQL statement and the lock level specified on the COMMIT
parameter of the CRTSQLxxx, STRSQL, or RUNSQLSTM command will override the default
lock level. Also, the LCKLVL parameter only applies to commitment control operations that are
requested through the IBM i traditional system interface (non-SQL). The lock level specified on
the LCKLVL parameter is not affected by any subsequent changes to the SQL isolation level
that are made by using, for example, the SET TRANSACTION statement.
For cursors that use aggregate functions, GROUP BY, or HAVING, and are running under commitment
control, a ROLLBACK HOLD has no effect on the cursor's position. In addition, the following occurs
under commitment control:
v If COMMIT(*CHG) and (ALWBLK(*NO) or (ALWBLK(*READ)) is specified for one of these cursors, a
message (CPI430B) is sent that says COMMIT(*CHG) requested but not allowed.
v If COMMIT(*ALL), COMMIT(*RR), or COMMIT(*CS) with the KEEP LOCKS clause is specified for one
of the cursors, DB2 for i locks all referenced tables in shared mode (*SHRNUP). The lock prevents
concurrent application processes from processing any but read-only operations on the named table. A
message (either SQL7902 or CPI430A) is sent that says COMMIT(*ALL), COMMIT(*RR), or
COMMIT(*CS) with the KEEP LOCKS clause is specified for one of the cursors requested but not
allowed. Message SQL0595 might also be sent.
For cursors where COMMIT(*ALL), COMMIT(*RR), or COMMIT(*CS) with the KEEP LOCKS clause is
specified and either catalog files are used or a temporary result table is required, DB2 for i locks all
referenced tables in shared mode (*SHRNUP). This prevents concurrent processes from processing
anything but read-only operations on the named table or tables. A message (either SQL7902 or CPI430A)
is sent that says COMMIT(*ALL) is requested but not allowed. Message SQL0595 might also be sent.
If ALWBLK(*ALLREAD) and COMMIT(*CHG) were specified, when the program was precompiled, all
read-only cursors will allow blocking of rows and a ROLLBACK HOLD will not roll the cursor position
back.
SQL programming
139
If COMMIT(*RR) is requested, the tables will be locked until the query is closed. If the cursor is
read-only, the table will be locked (*SHRNUP). If the cursor is in update mode, the table will be locked
(*EXCLRD). Since other users will be locked out of the table, running with repeatable read will prevent
concurrent access of the table.
In a highly contentious environment using COMMIT(*RR), an application might need to retry an
operation after getting an SQL0913 to allow the database unlocking mechanism time to work.
If an isolation level other then COMMIT(*NONE) was specified and the application issues a ROLLBACK
or the activation group ends abnormally (and the commitment definition is not *JOB), all updates, inserts,
deletes, and DDL operations made within the unit of work are backed out. If the application issues a
COMMIT or the activation group ends normally, all updates, inserts, deletes, and DDL operations made
within the unit of work are committed.
DB2 for i uses locks on rows to keep other jobs from accessing changed data before a unit of work is
completed. If COMMIT(*ALL) is specified, read locks on rows fetched are also used to prevent other jobs
from changing data that was read before a unit of work is completed. This does not prevent other jobs
from reading the unchanged rows. This ensures that, if the same unit of work rereads a row, it gets the
same result. Read locks do not prevent other jobs from fetching the same rows.
Commitment control handles up to 500 million distinct row changes in a unit of work. If COMMIT(*ALL)
or COMMIT(*RR) is specified, all rows read are also included in the limit. (If a row is changed or read
more than once in a unit of work, it is only counted once toward the limit.) Holding a large number of
locks adversely affects system performance and does not allow concurrent users to access rows locked in
the unit of work until the end of the unit of work. It is in your best interest to keep the number of rows
processed in a unit of work small.
COMMIT HOLD and ROLLBACK HOLD allow you to keep the cursor open and start another unit of
work without issuing an OPEN statement again. The HOLD value is not available when you are
connected to a remote database that is not on a System i platform. However, the WITH HOLD option on
DECLARE CURSOR can be used to keep the cursor open after a commit. This type of cursor is supported
when you are connected to a remote database that is not on a System i platform. Such a cursor is closed
on a rollback.
Table 45. Row lock duration
SQL statement
COMMIT parameter (see

note 5)
Duration of row locks
Lock type
SELECT INTO
SET variable
VALUES INTO
*NONE
*CHG
*CS (See note 6)
*ALL (See note 2 and 7)
No locks
No locks
Row locked when read and released
From read until ROLLBACK or COMMIT
READ
READ
FETCH (read-only cursor) *NONE

*CHG
*CS (See note 6)
*ALL (See note 2 and 7)
No locks
No locks
From read until the next FETCH
READ
READ
140
Table 45. Row lock duration (continued)

SQL statement

note 5)
Lock type
FETCH (update or delete

capable cursor) (See note
1)
*NONE
UPDATE
*ALL
When row is not updated or deleted

from read until next FETCH
When row is updated
When row is deleted
from read until next DELETE
When row is updated or deleted
from read until COMMIT or ROLLBACK
When row is updated or deleted
from read until COMMIT or ROLLBACK
INSERT (target table)

MERGE, INSERT
sub-statement
*NONE
*CHG
*CS
*ALL
No locks
From insert until ROLLBACK or COMMIT
UPDATE
UPDATE
UPDATE3
INSERT (tables in
subselect)
*NONE
*CHG
*CS
*ALL
No locks
No locks
Each row locked while being read
READ
READ
UPDATE (non-cursor)
*NONE
*CHG
*CS
*ALL
Each row locked while being updated

UPDATE
UPDATE
UPDATE
UPDATE
DELETE (non-cursor)
*NONE
*CHG
*CS
*ALL
Each row locked while being deleted

UPDATE
UPDATE
UPDATE
UPDATE
|
|
|
UPDATE (with cursor)

MERGE, UPDATE
sub-statement
*NONE
*CHG
*CS
*ALL
From
From
From
From
next FETCH
ROLLBACK or COMMIT
ROLLBACK or COMMIT
ROLLBACK or COMMIT
UPDATE
UPDATE
UPDATE
UPDATE
|
|
|
DELETE (with cursor)

MERGE, DELETE
sub-statement
*NONE
*CHG
*CS
*ALL
Lock released when row deleted

UPDATE
UPDATE
UPDATE
UPDATE
Subqueries (update or
delete capable cursor or
UPDATE or DELETE
non-cursor)
*NONE
*CHG
*CS
*ALL (see note 2)
From
From
From
From
next FETCH
next FETCH
next FETCH
ROLLBACK or COMMIT
READ
READ
READ
READ
Subqueries (read-only
cursor or SELECT INTO)
*NONE
*CHG
*CS
*ALL
No locks
No locks
Each row locked while being read
READ
READ
*CHG
*CS
|
|
|
read
read
read
read
read
read
read
read
until
until
until
until
until
until
until
until
UPDATE
UPDATE
UPDATE
SQL programming
141
Table 45. Row lock duration (continued)

SQL statement

note 5)
Lock type
Notes:
1. A cursor is open with UPDATE or DELETE capabilities if the result table is not read-only and if one of the following is true:
v The cursor is defined with a FOR UPDATE clause.
v The cursor is defined without a FOR UPDATE, FOR READ ONLY, or ORDER BY clause and the program contains at least
one of the following:
Cursor UPDATE referring to the same cursor-name
Cursor DELETE referring to the same cursor-name
An EXECUTE or EXECUTE IMMEDIATE statement and ALWBLK(*READ) or ALWBLK(*NONE) was specified on the
CRTSQLxxx command.
2. A table or view can be locked exclusively in order to satisfy COMMIT(*ALL). If a subselect is processed that includes a
UNION, or if the processing of the query requires the use of a temporary result, an exclusive lock is acquired to protect you
from seeing uncommitted changes.
3. An UPDATE lock on rows of the target table and a READ lock on the rows of the subselect table.
4. A table or view can be locked exclusively in order to satisfy repeatable read. Row locking is still done under repeatable read.
The locks acquired and their duration are identical to *ALL.
5. Repeatable read (*RR) row locks will be the same as the locks indicated for *ALL.
6. If the KEEP LOCKS clause is specified with *CS, any read locks are held until the cursor is closed or until a COMMIT or
ROLLBACK is done. If no cursors are associated with the isolation clause, then locks are held until the completion of the SQL
statement.
7. If the USE AND KEEP EXCLUSIVE LOCKS clause is specified with the *RS or *RR isolation level, an UPDATE lock on the row
will be obtained instead of a READ lock.
Related concepts:
Commitment control
Related reference:
DECLARE CURSOR
Isolation level
XA APIs
Savepoints
A savepoint is a named entity that represents the state of data and schemas at a particular point within a
unit of work. You can create savepoints within a transaction. If the transaction rolls back, changes are
undone to the specified savepoint, rather than to the beginning of the transaction.
You can set a savepoint using the SAVEPOINT SQL statement. For example, create a savepoint called
STOP_HERE:
SAVEPOINT STOP_HERE
ON ROLLBACK RETAIN CURSORS
Program logic in the application dictates whether the savepoint name is reused as the application
progresses, or if the savepoint name denotes a unique milestone in the application that should not be
reused.
If the savepoint represents a unique milestone that should not be moved with another SAVEPOINT
statement, specify the UNIQUE keyword. This prevents the accidental reuse of the name that can occur
by invoking a stored procedure that uses the identical savepoint name in a SAVEPOINT statement.
However, if the SAVEPOINT statement is used in a loop, then the UNIQUE keyword should not be used.
The following SQL statement sets a unique savepoint named START_OVER.
SAVEPOINT START_OVER UNIQUE
ON ROLLBACK RETAIN CURSORS
142
To rollback to a savepoint, use the ROLLBACK statement with the TO SAVEPOINT clause. The following
example illustrates using the SAVEPOINT and ROLLBACK TO SAVEPOINT statements:
This application logic books airline reservations on a preferred date, then books hotel reservations. If the
hotel is unavailable, it rolls back the airline reservations and then repeats the process for another date. Up
to 3 dates are tried.
got_reservations =0;
EXEC SQL SAVEPOINT START_OVER UNIQUE ON ROLLBACK RETAIN CURSORS;
if (SQLCODE != 0) return;
for (i=0; i<3 & got_reservations == 0; ++i)
{
Book_Air(dates(i), ok);
if (ok)
{
Book_Hotel(dates(i), ok);
if (ok) got_reservations = 1;
else
{
EXEC SQL ROLLBACK TO SAVEPOINT START_OVER;
if (SQLCODE != 0) return;
}
}
}
EXEC SQL RELEASE SAVEPOINT START_OVER;
Savepoints are released using the RELEASE SAVEPOINT statement. If a RELEASE SAVEPOINT statement
is not used to explicitly release a savepoint, it is released at the end of the current savepoint level or at
the end of the transaction. The following statement releases savepoint START_OVER.
RELEASE SAVEPOINT START_OVER
Savepoints are released when the transaction is committed or rolled back. Once the savepoint name is
released, a rollback to the savepoint name is no longer possible. The COMMIT or ROLLBACK statement
releases all savepoint names established within a transactions. Since all savepoint names are released
within the transaction, all savepoint names can be reused following a commit or rollback.
Savepoints are scoped to a single connection only. Once a savepoint is established, it is not distributed to
all remote databases that the application connects to. The savepoint only applies to the current database
that the application is connected to when the savepoint is established.
A single statement can implicitly or explicitly invoke a user-defined function, trigger, or stored procedure.
This is known as nesting. In some cases when a new nesting level is initiated, a new savepoint level is
also initiated. A new savepoint level isolates the invoking application from any savepoint activity by the
lower level routine or trigger.
Savepoints can only be referenced within the same savepoint level (or scope) in which they are defined.
A ROLLBACK TO SAVEPOINT statement cannot be used to rollback to a savepoint established outside
the current savepoint level. Likewise, a RELEASE SAVEPOINT statement cannot be used to release a
savepoint established outside the current savepoint level. The following table summarizes when
savepoint levels are initiated and terminated:
A new savepoint level is initiated when:
That savepoint level ends when:
A new unit of work is started
COMMIT or ROLLBACK is issued
A trigger is invoked
The trigger completes
A user-defined function is invoked
The user-defined function returns to the invoker
SQL programming
143
A new savepoint level is initiated when:
That savepoint level ends when:
A stored procedure is invoked, and that stored procedure The stored procedure returns to the caller
was created with the NEW SAVEPOINT LEVEL clause
There is a BEGIN for an ATOMIC compound SQL
statement
There is an END for an ATOMIC compound statement
A savepoint that is established in a savepoint level is implicitly released when that savepoint level is
terminated.
Atomic operations
When running under COMMIT(*CHG), COMMIT(*CS), or COMMIT(*ALL), all operations are guaranteed
to be atomic.
That is, they will complete or they will appear not to have started. This is true regardless of when or how
the function was ended or interrupted (such as power failure, abnormal job end, or job cancel).
If COMMIT (*NONE) is specified, however, some underlying database data definition functions are not
atomic. The following SQL data definition statements are guaranteed to be atomic:
v ALTER TABLE (See note 1)
v COMMENT (See note 2)
v
v
v
v
LABEL (See note 2)

GRANT (See note 3)
REVOKE (See note 3)
DROP TABLE (See note 4)
v DROP VIEW (See note 4)

v DROP INDEX
v DROP PACKAGE
v REFRESH TABLE
Notes:
1. If multiple alter table options are specified, the operations are processed one at a time so the
entire SQL statement is not atomic. The order of operations is:
v Remove constraints
v Remove materialized query table
v Remove partitions
v Remove partitioning
|
|
|
|
|
|
v Drop columns for which the RESTRICT option was specified

v All other column definition changes (DROP COLUMN CASCADE, ALTER COLUMN, ADD
COLUMN)
v Alter partition
v Add or alter materialized query table
|
|
|
|
|
v Add partition or partitioning

v Add constraints
2. If multiple columns are specified for a COMMENT or LABEL statement, the columns are
processed one at a time, so the entire SQL statement is not atomic, but the COMMENT or
LABEL to each individual column or object will be atomic.
3. If multiple tables, SQL packages, or users are specified for a GRANT or REVOKE statement,
the tables are processed one at a time, so the entire SQL statement is not atomic, but the
GRANT or REVOKE to each individual table will be atomic.
|
|
144
4. If dependent views need to be dropped during DROP TABLE or DROP VIEW, each dependent
view is processed one at a time, so the entire SQL statement is not atomic.
The following data definition statements are not atomic because they involve more than one database
operation:
v ALTER FUNCTION
v ALTER PROCEDURE
v ALTER SEQUENCE
v CREATE ALIAS
v CREATE TYPE
v
v
v
v
CREATE
CREATE
CREATE
CREATE
FUNCTION
INDEX
PROCEDURE
SCHEMA
v CREATE SEQUENCE
v CREATE TABLE
v CREATE TRIGGER
v CREATE VARIABLE
v CREATE VIEW
| v DECLARE GLOBAL TEMPORARY TABLE
|
v DROP ALIAS
v DROP FUNCTION
v DROP PROCEDURE
v
v
v
v
|
DROP
DROP
DROP
DROP
SCHEMA
SEQUENCE
TRIGGER
TYPE
v DROP VARIABLE
v RENAME (See note 1)
Note: RENAME is atomic only if the name or the system name is changed. When both are changed, the
RENAME is not atomic.
For example, a CREATE TABLE statement can be interrupted after the DB2 for i physical file has been
created, but before the member has been added. Therefore, in the case of create statements, if an
operation ends abnormally, you might need to drop the object and then create it again. In the case of a
DROP SCHEMA statement, you might need to drop the schema again or use the CL command Delete
Library (DLTLIB) to remove the remaining parts of the schema.
Constraints
The DB2 for i database supports unique, referential, and check constraints.
A unique constraint is a rule that guarantees that the values of a key are unique. A referential constraint
is a rule that all non-null values of foreign keys in a dependent table have a corresponding parent key in
a parent table. A check constraint is a rule that limits the values allowed in a column or group of
columns.
SQL programming
145
DB2 for i enforces the validity of the constraint during any data manipulation language (DML) statement.
Certain operations (such as restoring the dependent table), however, cause the validity of the constraint to
be unknown. In this case, DML statements might be prevented until DB2 for i has verified the validity of
the constraint.
v Unique constraints are implemented with indexes. If an index that implements a unique constraint is
not valid, the Edit Rebuild of Access Paths (EDTRBDAP) command can be used to display any indexes
that currently require being rebuilt.
v If DB2 for i does not currently know whether a referential constraint or check constraint is valid, the
constraint is considered to be in a check pending state. The Edit Check Pending Constraints
(EDTCPCST) command can be used to display any indexes that currently require being rebuilt.
Related concepts:
Constraints on page 11
A constraint is a rule enforced by the database manager to limit the values that can be inserted, deleted,
or updated in a table.
Adding and using check constraints:
A check constraint ensures the validity of data during insert and update operations by limiting the allowed
values in a column or group of columns.
Use the SQL CREATE TABLE and ALTER TABLE statements to add or drop check constraints.
In this example, the following statement creates a table with three columns and a check constraint over
COL2 that limits the values allowed in that column to positive integers:
CREATE TABLE T1 (COL1 INT, COL2 INT CHECK (COL2>0), COL3 INT)
Given this table, the following statement:

INSERT INTO T1 VALUES (-1, -1, -1)
fails because the value to be inserted into COL2 does not meet the check constraint; that is, -1 is not
greater than 0.
The following statement is successful:
INSERT INTO T1 VALUES (1, 1, 1)
Once that row is inserted, the following statement fails:

ALTER TABLE T1 ADD CONSTRAINT C1 CHECK (COL1=1 AND COL1<COL2)
This ALTER TABLE statement attempts to add a second check constraint that limits the value allowed in
COL1 to 1 and also effectively rules that values in COL2 be greater than 1. This constraint is not allowed
because the second part of the constraint is not met by the existing data (the value of '1' in COL2 is not
less than the value of '1' in COL1).
Related reference:
ALTER TABLE
CREATE TABLE
Save and restore functions

The IBM i save and restore functions are used to save SQL objects to disk (save file) or to external media.
The saved versions can be restored onto any IBM i operating system later. The save and restore functions
allow an entire schema, selected objects, or only objects that have been changed since a given date and
time to be saved. All information needed to restore an object to its previous state is saved. You can use
the functions to recover from damage to individual tables by restoring the data with a previous version
of the table or the entire schema.
146
When a program or service program that was created for an SQL procedure, an SQL function, or a
sourced function is restored, it is automatically added to the SYSROUTINES and SYSPARMS catalogs, as
long as a procedure or function does not already exist with the same signature and program name. SQL
programs created in QSYS will not be created as SQL procedures when restored. Additionally, external
programs or service programs that were referenced on a CREATE PROCEDURE or CREATE FUNCTION
statement may contain the information required to register the routine in SYSROUTINES. If the
information exists and the signature is unique, the functions or procedures will also be added to
SYSROUTINES and SYSPARMS when restored.
When an SQL table is restored, the definitions for the SQL triggers that are defined for the table are also
restored. The SQL trigger definitions are automatically added to the SYSTRIGGERS, SYSTRIGDEP,
SYSTRIGCOL, and SYSTRIGUPD catalogs. The program object that is created from the SQL CREATE
TRIGGER statement must also be saved and restored when the SQL table is saved and restored. The
saving and restoring of the program object is not automated by the database manager. The precautions
for self-referencing triggers should be reviewed when restoring SQL tables to a new library.
When an *SQLUDT object is restored for a user-defined type, the user-defined type is automatically
added to the SYSTYPES catalog. The appropriate functions needed to cast between the user-defined type
and the source type are also created, as long as the type and functions do not already exist.
When a *DTAARA for a sequence is restored, the sequence is automatically added to the
SYSSEQUENCES catalog. If the catalog is not successfully updated, the *DTAARA will be modified so it
cannot be used as a sequence and an SQL9020 informational message will be output in the job log.
|
|
|
|
When a *SRVPGM for a global variable is restored, the variable is automatically added to the
SYSVARIABLES catalog. If the catalog is not successfully updated, the object cannot be used as a global
variable. For a situation where it would have been a duplicate name in the schema, it might be possible
to have it recognized as a global variable by moving the object to a different schema.
Either a distributed SQL program or its associated SQL package can be saved and restored to any number
of systems. This allows any number of copies of the SQL programs on different systems to access the
same SQL package on the same application server. This also allows a single distributed SQL program to
connect to any number of application servers that have the SQL package restored (CRTSQLPKG can also
be used). SQL packages cannot be restored to a different library.
Note: Restoring a schema to an existing library or to a schema that has a different name does not restore
the journal, journal receivers, or IDDU dictionary (if one exists). If the schema is restored to a
schema with a different name, the catalog views in that schema will only reflect objects in the old
schema. The catalog views in QSYS2, however, will appropriately reflect all objects.
Damage tolerance
The DB2 for i database provides several mechanisms to reduce or eliminate damage caused by disk
errors.
For example, mirroring, checksums, and Redundant Array of Independent Disks (RAID) can all reduce
the possibility of disk problems. The DB2 for i functions also have a certain amount of tolerance to
damage caused by disk errors or system errors.
A DROP operation always succeeds, regardless of the damage. This ensures that should damage occur, at
least the table, view, SQL package, index, procedure, function, or distinct type can be deleted and
restored or created again.
If a disk error has damaged a small portion of the rows in a table, the DB2 for i database manager allows
you to read rows that are still accessible.
SQL programming
147
Index recovery
The DB2 for i database provides several functions to deal with index recovery.
v System managed index protection
The Edit Recovery for Access Paths (EDTRCYAP) CL command allows you to instruct DB2 for i to
guarantee that in the event of a system or power failure, the amount of time required to recover all
indexes on the system is kept below a specified time. The system automatically journals enough
information in a system journal to limit the recovery time to the specified amount.
v Journaling of indexes
DB2 for i provides an index journaling function that makes it unnecessary to rebuild an entire index in
the event of a power or system failure. If the index is journaled, the system database support
automatically makes sure that the index is in synchronization with the data in the tables without
having to rebuild it from scratch. SQL indexes are not journaled automatically. You can, however, use
the CL command Start Journal Access Path (STRJRNAP) to journal any index created by DB2 for i.
v Index rebuild
All indexes on the system have a maintenance option that specifies when an index is maintained. SQL
indexes are created with an attribute of *IMMED maintenance.
In the event of a power failure or an abnormal system failure, if indexes are not protected by one of
the previously described techniques, those indexes in the process of change might need to be rebuilt by
the database manager to make sure that they agree with the actual data. All indexes on the system
have a recovery option that specifies when an index should be rebuilt if necessary. All SQL indexes
with an attribute of UNIQUE are created with a recovery attribute of *IPL (this means that these
indexes are rebuilt before the IBM i operating system is started). All other SQL indexes are created with
the *AFTIPL recovery option (this means that after the operating system is started, indexes are
asynchronously rebuilt). During an IPL, the operator can see a display showing the indexes that need
to be rebuilt and their recovery options. The operator can override the recovery options.
v Save and restore of indexes
The save/restore function allows you to save indexes when a table is saved by using ACCPTH(*YES)
on the Save Object (SAVOBJ) or Save Library (SAVLIB) CL commands. In the event of a restore when
the indexes have also been saved, there is no need to rebuild the indexes. Any indexes not previously
saved and restored are automatically and asynchronously rebuilt by the database manager.
Catalog integrity
To ensure that the information in the catalog is always accurate, the DB2 for i database prevents users
from explicitly changing the information in the catalog and implicitly maintains the information when an
SQL object described in the catalog is changed.
The integrity of the catalog is maintained whether objects in the schema are changed by SQL statements,
IBM i CL commands, System/38 Environment CL commands, System/36 Environment functions, or any
other product or utility on a System i platform. For example, you can delete a table by running an SQL
DROP statement, issuing an IBM i Delete File (DLTF) CL command, issuing a System/38 Delete File
(DLTF) CL command, or entering option 4 on a WRKF or WRKOBJ display. Regardless of the interface
used to delete the table, the database manager removes the description of the table from the catalog when
the table is deleted. The following table lists various functions and their associated effects on the catalog.
Table 46. Effects of various functions on catalogs
Function
Effect on the catalog
Add constraint to table
Information added to catalog
Remove of constraint from table
Related information removed from catalog
Create object into schema
Delete of object from schema
Restore of object into schema
148
Table 46. Effects of various functions on catalogs (continued)

Function
Effect on the catalog
Change of object long comment
Comment updated in catalog
Change of object label (text)
Label updated in catalog
Change of object owner
Owner updated in catalog
Move of object from a schema
Move of object into schema
Rename of object
Name of object updated in catalog
User auxiliary storage pool

You can create a schema in a user auxiliary storage pool (ASP) using the ASP clause on the CREATE
SCHEMA statement.
The Create Library (CRTLIB) command can also be used to create a library in a user ASP. That library can
then be used to receive SQL tables, views, and indexes.
Related concepts:
Backup and recovery
Disk management
Independent auxiliary storage pool

Independent disk pools are used to set up user databases on the system.
There are three types of independent disk pools: primary, secondary, and user-defined file system (UDFS).
Primary independent disk pools are used to set up databases.
You can work with multiple databases. The system provides a system database (often referred to as
SYSBAS) and the ability to work with one or more user databases. User databases are implemented on
the system through the use of independent disk pools, which are set up in the disk management function
of System i Navigator. After an independent disk pool is set up, it appears as another database in the
Databases folder of System i Navigator.
Related concepts:
Disk management
Routines
Routines are pieces of code or programs that you can call to perform operations.
Stored procedures
DB2 stored procedure support provides a way for an SQL application to define and then call a procedure
through SQL statements. Stored procedures can be used in both distributed and nondistributed DB2
applications. One of the advantages of using stored procedures is that for distributed applications, the
processing of one CALL statement on the application requester, or client, can perform any amount of
work on the application server.
You may define a procedure as either an SQL procedure or an external procedure. An external procedure
can be any supported high level language program (except System/36 programs and procedures) or a
SQL programming
149
REXX procedure. The procedure does not need to contain SQL statements, but it may contain SQL
statements. An SQL procedure is defined entirely in SQL, and can contain SQL statements that include
SQL control statements.
Coding stored procedures requires that the user understand the following:
v Stored procedure definition through the CREATE PROCEDURE statement
v Stored procedure invocation through the CALL statement
v Parameter passing conventions
v Methods for returning a completion status to the program invoking the procedure.
You may define stored procedures by using the CREATE PROCEDURE statement. The CREATE
PROCEDURE statement adds procedure and parameter definitions to the catalog tables SYSROUTINES
and SYSPARMS. These definitions are then accessible by any SQL CALL statement on the system.
To create an external procedure or an SQL procedure, you can use the SQL CREATE PROCEDURE
statement.
The following sections describe the SQL statements used to define and call the stored procedure,
information about passing parameters to the stored procedure, and examples of stored procedure usage.
For more information about stored procedures, see Stored Procedures, Triggers, and User-Defined
Functions on DB2 Universal Database for iSeries
Related concepts:
A stored procedure is a program that can be called with the SQL CALL statement.
Java SQL routines
Related reference:
DRDA stored procedure considerations on page 448
The i5/OS Distributed Relational Database Architecture (DRDA) server supports the return of one or
more result sets in a stored procedure.
CREATE PROCEDURE
Defining an external procedure

The CREATE PROCEDURE statement for an external procedure names the procedure, defines the
parameters and their attributes, and provides other information about the procedure that the system uses
when it calls the procedure.
Consider the following example:
CREATE PROCEDURE P1
(INOUT PARM1 CHAR(10))
EXTERNAL NAME MYLIB.PROC1
LANGUAGE C
GENERAL WITH NULLS
This CREATE PROCEDURE statement:

v Names the procedure P1
v Defines one parameter which is used both as an input parameter and an output parameter. The
parameter is a character field of length ten. Parameters can be defined to be type IN, OUT, or INOUT.
The parameter type determines when the values for the parameters get passed to and from the
procedure.
v Defines the name of the program which corresponds to the procedure, which is PROC1 in MYLIB.
MYLIB.PROC1 is the program which is called when the procedure is called on a CALL statement.
150
v Indicates that the procedure P1 (program MYLIB.PROC1) is written in C. The language is important
since it impacts the types of parameters that can be passed. It also affects how the parameters are
passed to the procedure (for example, for ILE C procedures, a NUL-terminator is passed on character,
graphic, date, time, and timestamp parameters).
v Defines the CALL type to be GENERAL WITH NULLS. This indicates that the parameter for the
procedure can possibly contain the NULL value, and therefore will like an additional argument passed
to the procedure on the CALL statement. The additional argument is an array of N short integers,
where N is the number of parameters that are declared in the CREATE PROCEDURE statement. In this
example, the array contains only one element since there is only parameter.
It is important to note that it is not necessary to define a procedure in order to call it. However, if no
procedure definition is found, either from a prior CREATE PROCEDURE or from a DECLARE
PROCEDURE in this program, certain restrictions and assumptions are made when the procedure is
called on the CALL statement. For example, the NULL indicator argument cannot be passed.
Related reference:
Using the embedded CALL statement where no procedure definition exists on page 159
A static CALL statement without a corresponding CREATE PROCEDURE statement is processed with
these rules.
Defining an SQL procedure

The CREATE PROCEDURE statement for an SQL procedure names the procedure, defines the parameters
and their attributes, provides other information about the procedure that is used when the procedure is
called, and defines the procedure body.
The procedure body is the executable part of the procedure and is a single SQL statement.
Consider the following simple example that takes as input an employee number and a rate and updates
the employee's salary:
CREATE PROCEDURE UPDATE_SALARY_1
(IN EMPLOYEE_NUMBER CHAR(10),
IN RATE DECIMAL(6,2))
LANGUAGE SQL MODIFIES SQL DATA
SET SALARY = SALARY * RATE
WHERE EMPNO = EMPLOYEE_NUMBER

v Names the procedure UPDATE_SALARY_1.
v Defines parameter EMPLOYEE_NUMBER which is an input parameter and is a character data type of
length 6 and parameter RATE which is an input parameter and is a decimal data type.
v Indicates the procedure is an SQL procedure that modifies SQL data.
v Defines the procedure body as a single UPDATE statement. When the procedure is called, the UPDATE
statement is executed using the values passed for EMPLOYEE_NUMBER and RATE.
Instead of a single UPDATE statement, logic can be added to the SQL procedure by using SQL control
statements. SQL control statements consist of the following statements:
v
v
v
v
v
v
v
An assignment statement
A CALL statement
A CASE statement
A compound statement
A FOR statement
A GET DIAGNOSTICS statement
A GOTO statement
SQL programming
151
v
v
v
v
v
v
v
v
v
An IF statement
An ITERATE statement
A LEAVE statement
A LOOP statement
A REPEAT statement
A RESIGNAL statement
A RETURN statement
A SIGNAL statement
A WHILE statement
The following example takes as input the employee number and a rating that was received on the last
evaluation. The procedure uses a CASE statement to determine the appropriate increase and bonus for
the update.
CREATE PROCEDURE UPDATE_SALARY_2
IN RATING INT)
CASE RATING
WHEN 1 THEN
SET SALARY = SALARY * 1.10,
BONUS = 1000
WHERE EMPNO = EMPLOYEE_NUMBER;
WHEN 2 THEN
BONUS = 500
ELSE
BONUS = 0
END CASE

v Names the procedure UPDATE_SALARY_2.
v Defines parameter EMPLOYEE_NUMBER which is an input parameter and is a character data type of
length 6 and parameter RATING which is an input parameter and is an integer data type.
v Indicates the procedure is an SQL procedure that modifies SQL data.
v Defines the procedure body. When the procedure is called, input parameter RATING is checked and
the appropriate update statement is executed.
Multiple statements can be added to a procedure body by adding a compound statement. Within a
compound statement, any number of SQL statements can be specified. In addition, SQL variables, cursors,
and handlers can be declared.
The following example takes as input the department number. It returns the total salary of all the
employees in that department and the number of employees in that department who get a bonus.
CREATE PROCEDURE RETURN_DEPT_SALARY
(IN DEPT_NUMBER CHAR(3),
OUT DEPT_SALARY DECIMAL(15,2),
OUT DEPT_BONUS_CNT INT)
LANGUAGE SQL READS SQL DATA
P1: BEGIN
DECLARE EMPLOYEE_SALARY DECIMAL(9,2);
DECLARE EMPLOYEE_BONUS DECIMAL(9,2);
152
DECLARE TOTAL_SALARY DECIMAL(15,2)DEFAULT 0;

DECLARE BONUS_CNT INT DEFAULT 0;
DECLARE END_TABLE INT DEFAULT 0;
DECLARE C1 CURSOR FOR
SELECT SALARY, BONUS FROM CORPDATA.EMPLOYEE
WHERE WORKDEPT = DEPT_NUMBER;
DECLARE CONTINUE HANDLER FOR NOT FOUND
SET END_TABLE = 1;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
SET DEPT_SALARY = NULL;
OPEN C1;
FETCH C1 INTO EMPLOYEE_SALARY, EMPLOYEE_BONUS;
WHILE END_TABLE = 0 DO
SET TOTAL_SALARY = TOTAL_SALARY + EMPLOYEE_SALARY + EMPLOYEE_BONUS;
IF EMPLOYEE_BONUS > 0 THEN
SET BONUS_CNT = BONUS_CNT + 1;
END IF;
FETCH C1 INTO EMPLOYEE_SALARY, EMPLOYEE_BONUS;
END WHILE;
CLOSE C1;
SET DEPT_SALARY = TOTAL_SALARY;
SET DEPT_BONUS_CNT = BONUS_CNT;
END P1

v Names the procedure RETURN_DEPT_SALARY.
v Defines parameter DEPT_NUMBER which is an input parameter and is a character data type of length
3, parameter DEPT_SALARY which is an output parameter and is a decimal data type, and parameter
DEPT_BONUS_CNT which is an output parameter and is an integer data type.
v Indicates the procedure is an SQL procedure that reads SQL data
v Defines the procedure body.
Declares SQL variables EMPLOYEE_SALARY and TOTAL_SALARY as decimal fields.
Declares SQL variables BONUS_CNT and END_TABLE which are integers and are initialized to 0.
Declares cursor C1 that selects the columns from the employee table.
Declares a continue handler for NOT FOUND, which, when called sets variable END_TABLE to 1.
This handler is called when the FETCH has no more rows to return. When the handler is called,
SQLCODE and SQLSTATE are reinitialized to 0.
Declares an exit handler for SQLEXCEPTION. If called, DEPT_SALARY is set to NULL and the
processing of the compound statement is terminated. This handler is called if any errors occur, that
is, the SQLSTATE class is not '00', '01' or '02'. Since indicators are always passed to SQL procedures,
the indicator value for DEPT_SALARY is -1 when the procedure returns. If this handler is called,
SQLCODE and SQLSTATE are reinitialized to 0.
If the handler for SQLEXCEPTION is not specified and an error occurs that is not handled in
another handler, execution of the compound statement is terminated and the error is returned in the
SQLCA. Similar to indicators, the SQLCA is always returned from SQL procedures.
Includes an OPEN, FETCH, and CLOSE of cursor C1. If a CLOSE of the cursor is not specified, the
cursor is closed at the end of the compound statement since SET RESULT SETS is not specified in
the CREATE PROCEDURE statement.
Includes a WHILE statement which loops until the last record is fetched. For each row retrieved, the
TOTAL_SALARY is incremented and, if the employee's bonus is more than 0, the BONUS_CNT is
incremented.
Returns DEPT_SALARY and DEPT_BONUS_CNT as output parameters.
Compound statements can be made atomic so if an error occurs that is not expected, the statements
within the atomic statement are rolled back. The atomic compound statements are implemented using
SAVEPOINTS. If the compound statement is successful, the transaction is committed.
SQL programming
153
The following example takes as input the department number. It ensures the EMPLOYEE_BONUS table
exists, and inserts the name of all employees in the department who get a bonus. The procedure returns
the total count of all employees who get a bonus.
CREATE PROCEDURE CREATE_BONUS_TABLE
(IN DEPT_NUMBER CHAR(3),
INOUT CNT INT)
CS1: BEGIN ATOMIC
DECLARE NAME VARCHAR(30) DEFAULT NULL;
DECLARE CONTINUE HANDLER FOR SQLSTATE 42710
SELECT COUNT(*) INTO CNT
FROM DATALIB.EMPLOYEE_BONUS;
DECLARE CONTINUE HANDLER FOR SQLSTATE 23505
SET CNT = CNT - 1;
DECLARE UNDO HANDLER FOR SQLEXCEPTION
SET CNT = NULL;
IF DEPT_NUMBER IS NOT NULL THEN
CREATE TABLE DATALIB.EMPLOYEE_BONUS
(FULLNAME VARCHAR(30),
BONUS DECIMAL(10,2),
PRIMARY KEY (FULLNAME));
FOR_1:FOR V1 AS C1 CURSOR FOR
SELECT FIRSTNME, MIDINIT, LASTNAME, BONUS
WHERE WORKDEPT = CREATE_BONUS_TABLE.DEPT_NUMBER
DO
IF BONUS > 0 THEN
SET NAME = FIRSTNME CONCAT CONCAT
MIDINIT CONCAT CONCAT LASTNAME;
INSERT INTO DATALIB.EMPLOYEE_BONUS
VALUES(CS1.NAME, FOR_1.BONUS);
SET CNT = CNT + 1;
END IF;
END FOR FOR_1;
END IF;
END CS1

v Names the procedure CREATE_BONUS_TABLE.
v Defines parameter DEPT_NUMBER which is an input parameter and is a character data type of length
3 and parameter CNT which is an input/output parameter and is an integer data type.
v Indicates the procedure is an SQL procedure that modifies SQL data
v Defines the procedure body.
Declares SQL variable NAME as varying character.
Declares a continue handler for SQLSTATE 42710, table already exists. If the EMPLOYEE_BONUS
table already exists, the handler is called and retrieves the number of records in the table. The
SQLCODE and SQLSTATE are reset to 0 and processing continues with the FOR statement.
Declares a continue handler for SQLSTATE 23505, duplicate key. If the procedure attempts to insert
a name that already exists in the table, the handler is called and decrements CNT. Processing
continues on the SET statement following the INSERT statement.
Declares an UNDO handler for SQLEXCEPTION. If called, the previous statements are rolled back,
CNT is set to 0, and processing continues after the compound statement. In this case, since there is
no statement following the compound statement, the procedure returns.
Uses the FOR statement to declare cursor C1 to read the records from the EMPLOYEE table. Within
the FOR statement, the column names from the select list are used as SQL variables that contain the
data from the row fetched. For each row, data from columns FIRSTNME, MIDINIT, and
LASTNAME are concatenated together with a blank in between and the result is put in SQL variable
NAME. SQL variables NAME and BONUS are inserted into the EMPLOYEE_BONUS table. Because
154
the data type of the select list items must be known when the procedure is created, the table
specified in the FOR statement must exist when the procedure is created.
An SQL variable name can be qualified with the label name of the FOR statement or compound
statement in which it is defined. In the example, FOR_1.BONUS refers to the SQL variable that
contains the value of column BONUS for each row selected. CS1.NAME is the variable NAME
defined in the compound statement with the beginning label CS1. Parameter names can also be
qualified with the procedure name. CREATE_BONUS_TABLE.DEPT_NUMBER is the
DEPT_NUMBER parameter for the procedure CREATE_BONUS_TABLE. If unqualified SQL variable
names are used in SQL statements where column names are also allowed, and the variable name is
the same as a column name, the name will be used to refer to the column.
You can also use dynamic SQL in an SQL procedure. The following example creates a table that contains
all employees in a specific department. The department number is passed as input to the procedure and
is concatenated to the table name.
CREATE PROCEDURE CREATE_DEPT_TABLE (IN P_DEPT CHAR(3))
LANGUAGE SQL
BEGIN
DECLARE STMT CHAR(1000);
DECLARE MESSAGE CHAR(20);
DECLARE TABLE_NAME CHAR(30);
DECLARE CONTINUE HANDLER FOR SQLEXCEPTION
SET MESSAGE = ok;
SET TABLE_NAME = CORPDATA.DEPT_ CONCAT P_DEPT CONCAT _T;
SET STMT = DROP TABLE CONCAT TABLE_NAME;
PREPARE S1 FROM STMT;
EXECUTE S1;
SET STMT = CREATE TABLE CONCAT TABLE_NAME CONCAT
( EMPNO CHAR(6) NOT NULL,
MIDINIT CHAR(1) NOT NULL,
LASTNAME CHAR(15) NOT NULL,
SALARY DECIMAL(9,2));
EXECUTE S2;
SET STMT = INSERT INTO CONCAT TABLE_NAME CONCAT
SELECT EMPNO, FIRSTNME, MIDINIT, LASTNAME, SALARY
WHERE WORKDEPT = ?;
EXECUTE S3 USING P_DEPT;
END

v
v
v
v
Names the procedure CREATE_DEPT_TABLE

Defines parameter P_DEPT which is an input parameter and is a character data type of length 3.
Indicates the procedure is an SQL procedure.
Defines the procedure body.
Declares SQL variable STMT and an SQL variable TABLE_NAME as character.
Declares a CONTINUE handler. The procedure attempts to DROP the table in case it already exists.
If the table does not exist, the first EXECUTE fails. With the handler, processing will continue.
Sets variable TABLE_NAME to 'DEPT_' followed by the characters passed in parameter P_DEPT,
followed by '_T'.
Sets variable STMT to the DROP statement, and prepares and executes the statement.
Sets variable STMT to the CREATE statement, and prepares and executes the statement.
Sets variable STMT to the INSERT statement, and prepares and executes the statement. A parameter
marker is specified in the where clause. When the statement is executed, the variable P_DEPT is
passed on the USING clause.
SQL programming
155
If the procedure is called passing value 'D21' for the department, table DEPT_D21_T is created and the
table is initialized with all the employees that are in department 'D21'.
| Defining a procedure with default parameters
| External and SQL procedures can be created with optional parameters. Optional procedure parameters
| are defined to have a default value.
| Suppose you have a procedure that is defined with parameters as follows. Whether this is part of an SQL
| procedure or an external procedure statement doesnt matter; only the parameter definitions are being
| discussed here.
|
CREATE PROCEDURE UPDATE_EMPLOYEE_INFO
|
|
IN EMP_DEPT CHAR(3),
|
IN PHONE_NUMBER CHAR(4))
|
. . .
|
|
|
|
This procedure has been in use for a long time and is invoked from many places. Now, someone has
suggested that it would be useful to have this procedure update a few other columns in the same table,
JOB and EDLEVEL. Finding and changing all the calls to this procedure is a huge job, but if you add the
new parameters so they have default values it is very easy.
| The parameter definitions in the following CREATE PROCEDURE statement will allow all of the columns
| except the employee number to be passed in optionally.
|
CREATE OR REPLACE PROCEDURE UPDATE_EMPLOYEE_INFO
|
|
IN EMP_DEPT CHAR(3) DEFAULT NULL,
|
IN PHONE_NUMBER CHAR(4) DEFAULT NULL,
|
IN JOB CHAR(8) DEFAULT NULL,
|
IN EDLEVEL SMALLINT DEFAULT NULL)
|
. . .
|
|
|
|
|
The code for this procedure, either an SQL routine or an external program, needs to be modified to
handle the new parameters and to correctly process the two existing parameters when a NULL value is
passed. Since default parameters are optional, any existing call to this procedure will not need to change;
the two new parameters will pass a value of NULL to the procedure code. Any caller who needs the new
parameters can include them on the SQL CALL statement.
| Although this example uses NULL for all the default values, almost any expression can be used. It can be
| a simple constant or a complex query. It cannot reference any of the other parameters.
| There are several ways to have the defaults used for the CALL statement.
| v Omit the parameters at the end that you do not need to use.
|
CALL UPDATE_EMPLOYEE_INFO(123456, D11, 4424)
|
The defaults will be used for the JOB and EDLEVEL parameters.
| v Use the DEFAULT keyword for any parameters that are omitted.
|
CALL UPDATE_EMPLOYEE_INFO(123456, DEFAULT, 4424, DEFAULT, DEFAULT)
|
All the parameters are represented in this statement. The defaults will be used for the EMP_DEPT, JOB,
|
and EDLEVEL parameters.
| v Explicitly name some of the arguments with the corresponding parameter name and omit parameters
|
that are not used.
|
CALL UPDATE_EMPLOYEE_INFO(123456, EDLEVEL => 18)
|
|
By using the parameter name, the other three parameters do not need to be represented in this CALL
statement. The defaults will be used for the EMP_DEPT, PHONE_NUMBER, and JOB parameters.
156
|
|
|
|
|
Named arguments can be in any order in the CALL statement. Unnamed arguments must match the
order of the parameter definitions for the procedure and must be specified ahead of any named
arguments. Once a named argument is used in the statement, all arguments that follow it must also be
named. Any parameters that do not have an argument in the CALL statement must have a default
defined.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In the following example, the procedure creates a table containing all employees in a specified
department. The schema where it gets created has always been hard-coded for the environment where it
is used. For testing, however, it would be convenient to create the table in a test schema.
|
|
A second parameter is defined to pass a schema name. It has a default of CORPDATA. This is the value
that has been used by the procedure in the past.
|
|
When run in the production environment, the CALL statement might be:
This creates the table in the schema provided by the default, CORPDATA.
|
|
When run in the test environment, the CALL statement might be:
|
|
|
|
|
|
This creates the table in the specified schema, TESTSCHEMA.

Related concepts:
Procedure resolution
Related reference:
CALL
CREATE PROCEDURE (SQL)
CREATE PROCEDURE (External)
CREATE OR REPLACE PROCEDURE CREATE_DEPT_TABLE2

(IN P_DEPT CHAR(3),
IN SCHEMA_NAME VARCHAR(128) DEFAULT CORPDATA)
BEGIN
DECLARE DYNAMIC_STMT VARCHAR(1000);
DECLARE MESSAGE CHAR(20);
DECLARE TABLE_NAME VARCHAR(200);
DECLARE CONTINUE HANDLER FOR SQLEXCEPTION
SET MESSAGE = ok;
SET TABLE_NAME = " CONCAT SCHEMA_NAME CONCAT
".DEPT_ CONCAT P_DEPT CONCAT _T;
SET DYNAMIC_STMT = DROP TABLE CONCAT TABLE_NAME;
EXECUTE IMMEDIATE DYNAMIC_STMT;
SET DYNAMIC_STMT = CREATE TABLE CONCAT TABLE_NAME CONCAT
( EMPNO CHAR(6) NOT NULL,
MIDINIT CHAR(1) NOT NULL,
LASTNAME CHAR(15) NOT NULL,
SALARY DECIMAL(9,2));
EXECUTE IMMEDIATE DYNAMIC_STMT;
SET DYNAMIC_STMT = INSERT INTO CONCAT TABLE_NAME CONCAT
SELECT EMPNO, FIRSTNME, MIDINIT, LASTNAME, SALARY
WHERE WORKDEPT = ?;
PREPARE INSERT_INTO_DEPARTMENT_STMT FROM DYNAMIC_STMT;
EXECUTE INSERT_INTO_DEPARTMENT_STMT USING P_DEPT;
END;
CALL CREATE_DEPT_TABLE2(D21)
CALL CREATE_DEPT_TABLE2(D21, TESTSCHEMA)
SQL programming
157
Calling a stored procedure

The SQL CALL statement calls a stored procedure.
|
|
|
|
|
On the CALL statement, the name of the stored procedure and any arguments are specified. Arguments
may be constants, special registers, host variables, or expressions. The external stored procedure specified
in the CALL statement does not need to have a corresponding CREATE PROCEDURE statement.
Programs created by SQL procedures can only be called by invoking the procedure name specified on the
CREATE PROCEDURE statement.
Although procedures are system program objects, using the CALL CL command will not typically work
to call a procedure. The CALL CL command does not use the procedure definition to map the input and
output parameters, nor does it pass parameters to the program using the procedure's parameter style.
The following types of CALL statements need to be addressed because the DB2 for i database has
different rules for each type:
v Embedded or dynamic CALL statement where a procedure definition exists
v Embedded CALL statement where no procedure definition exists
v Dynamic CALL statement where no CREATE PROCEDURE exists
Notes:
Dynamic here refers to:
v A dynamically prepared and executed CALL statement.
v A CALL statement issued in an interactive environment (for example, through STRSQL or
Query Manager).
v A CALL statement executed in an EXECUTE IMMEDIATE statement.
Using the CALL statement where procedure definition exists:
This type of CALL statement reads all the information about the procedure and the argument attributes
from the CREATE PROCEDURE catalog definition.
The following PL/I example shows a CALL statement that corresponds to the CREATE PROCEDURE
statement shown.
DCL HV1 CHAR(10);
DCL IND1 FIXED BIN(15);
:
EXEC SQL CREATE P1 PROCEDURE
(INOUT PARM1 CHAR(10))
EXTERNAL NAME MYLIB.PROC1
LANGUAGE C
GENERAL WITH NULLS;
:
EXEC SQL CALL P1 (:HV1 :IND1);
:
When this CALL statement is issued, a call to program MYLIB/PROC1 is made and two arguments are
passed. Because the language of the program is ILE C, the first argument is a C NUL-terminated string,
11 characters long, which contains the contents of host variable HV1. On a call to an ILE C procedure,
SQL adds one character to the parameter declaration if the parameter is declared to be a character,
graphic, date, time, or timestamp variable. The second argument is the indicator array. In this case, it is
one short integer because there is only one parameter in the CREATE PROCEDURE statement. This
argument contains the contents of indicator variable IND1 on entry to the procedure.
Since the first parameter is declared as INOUT, SQL updates the host variable HV1 and the indicator
variable IND1 with the values returned from MYLIB.PROC1 before returning to the user program.
158
Notes:
1. The procedure names specified on the CREATE PROCEDURE and CALL statements must
match EXACTLY in order for the link between the two to be made during the SQL precompile
of the program.
2. For an embedded CALL statement where both a CREATE PROCEDURE and a DECLARE
PROCEDURE statement exist, the DECLARE PROCEDURE statement will be used.
Using the embedded CALL statement where no procedure definition exists:
A static CALL statement without a corresponding CREATE PROCEDURE statement is processed with
these rules.
v All host variable arguments are treated as INOUT type parameters.
v The CALL type is GENERAL (no indicator argument is passed).
v The program to call is determined based on the procedure name specified on the CALL, and, if
necessary, the naming convention.
v The language of the program to call is determined based on information retrieved from the system
about the program.
Example: Embedded CALL statement where no procedure definition exists
The following PL/I example shows an embedded CALL statement where no procedure definition exists:
DCL HV2 CHAR(10);
:
EXEC SQL CALL P2 (:HV2);
:
When the CALL statement is issued, SQL attempts to find the program based on standard SQL naming
conventions. For the preceding example, assume that the naming option of *SYS (system naming) is used
and that a DFTRDBCOL parameter is not specified on the Create SQL PL/I Program (CRTSQLPLI)
command. In this case, the library list is searched for a program named P2. Because the call type is
GENERAL, no additional argument is passed to the program for indicator variables.
Note: If an indicator variable is specified on the CALL statement and its value is less than zero when the
CALL statement is executed, an error results because there is no way to pass the indicator to the
procedure.
Assuming program P2 is found in the library list, the contents of host variable HV2 are passed in to the
program on the CALL and the argument returned from P2 is mapped back to the host variable after P2
has completed execution.
For numeric constants passed on a CALL statement, the following rules apply:
v All integer constants are passed as fullword binary integers.
v All decimal constants are passed as packed decimal values. Precision and scale are determined based
on the constant value. For instance, a value of 123.45 is passed as a packed decimal(5,2). Likewise, a
value of 001.01 is also passed with a precision of 5 and a scale of 2.
v All floating point constants are passed as double-precision floating point.
Special registers specified on a dynamic CALL statement are passed as their defined data type and length
with the following exceptions:
CURRENT DATE
Passed as a 10-byte character string in ISO format.
CURRENT TIME
Passed as an 8-byte character string in ISO format.
SQL programming
159
CURRENT TIMESTAMP
Passed as a 26-byte character string in IBM SQL format.
Using the embedded CALL statement with an SQLDA:
In either type of embedded CALL statement (where a procedure definition might or might not exist), an
SQLDA rather than a parameter list can be passed.
The following C examples illustrates this. Assume that the stored procedure is expecting 2 parameters,
the first of type SHORT INT and the second of type CHAR with a length of 4.
#define SQLDA_HV_ENTRIES 2
#define SHORTINT 500
#define NUL_TERM_CHAR 460
exec sql include sqlca;
exec sql include sqlda;
...
typedef struct sqlda Sqlda;
typedef struct sqlda* Sqldap;
...
main()
{
Sqldap dap;
short col1;
char col2[4];
int bc;
dap = (Sqldap) malloc(bc=SQLDASIZE(SQLDA_HV_ENTRIES));
/* SQLDASIZE is a macro defined in the sqlda include */
col1 = 431;
strcpy(col2,"abc");
strncpy(dap->sqldaid,"SQLDA ",8);
dap->sqldabc = bc;
/* bc set in the malloc statement above */
dap->sqln = SQLDA_HV_ENTRIES;
dap->sqld = SQLDA_HV_ENTRIES;
dap->sqlvar[0].sqltype = SHORTINT;
dap->sqlvar[0].sqllen = 2;
dap->sqlvar[0].sqldata = (char*) &col1;
dap->sqlvar[0].sqlname.length = 0;
dap->sqlvar[1].sqltype = NUL_TERM_CHAR;
dap->sqlvar[1].sqllen = 4;
dap->sqlvar[1].sqldata = col2;
...
EXEC SQL CALL P1 USING DESCRIPTOR :*dap;
...
}
The name of the called procedure may also be stored in a host variable and the host variable used in the
CALL statement, instead of the hard-coded procedure name. For example:
...
main()
{
char proc_name[15];
...
strcpy (proc_name, "MYLIB.P3");
...
EXEC SQL CALL :proc_name ...;
...
}
160
In the above example, if MYLIB.P3 is expecting parameters, either a parameter list or an SQLDA passed
with the USING DESCRIPTOR clause may be used, as shown in the previous example.
When a host variable containing the procedure name is used in the CALL statement and a CREATE
PROCEDURE catalog definition exists, it will be used. The procedure name cannot be specified as a
parameter marker.
Using the dynamic CALL statement where no CREATE PROCEDURE exists:
These rules pertain to the processing of a dynamic CALL statement when there is no CREATE
PROCEDURE definition.
v All arguments are treated as IN type parameters.
v The CALL type is GENERAL (no indicator argument is passed).
v The program to call is determined based on the procedure name specified on the CALL and the
naming convention.
v The language of the program to call is determined based on information retrieved from the system
about the program.
Example: Dynamic CALL statement where no CREATE PROCEDURE exists
The following C example shows a dynamic CALL statement:
char hv3[10],string[100];
:
strcpy(string,"CALL MYLIB.P3 (P3 TEST)");
EXEC SQL EXECUTE IMMEDIATE :string;
:
This example shows a dynamic CALL statement executed through an EXECUTE IMMEDIATE statement.
The call is made to program MYLIB.P3 with one parameter passed as a character variable containing 'P3
TEST'.
When executing a CALL statement and passing a constant, as in the previous example, the length of the
expected argument in the program must be kept in mind. If program MYLIB.P3 expected an argument of
only 5 characters, the last 2 characters of the constant specified in the example is lost to the program.
Note: For this reason, it is always safer to use host variables on the CALL statement so that the attributes
of the procedure can be matched exactly and so that characters are not lost. For dynamic SQL, host
variables can be specified for CALL statement arguments if the PREPARE and EXECUTE
statements are used to process it.
Examples: CALL statements:
These examples show how the arguments of a CALL statement are passed to a procedure for several
languages, and how the arguments are received into local variables in the procedure.
Example 1: ILE C and PL/I procedures called from an ILE C program:
This example shows an ILE C program that uses the CREATE PROCEDURE definitions to call the P1 and
P2 procedures. Procedure P1 is written in ILE C and has 10 parameters. Procedure P2 is written in PL/I
and also has 10 parameters.
Defining the P1 and P2 procedures
EXEC SQL CREATE PROCEDURE P1 (INOUT PARM1 CHAR(10),
INOUT PARM2 INTEGER,
INOUT PARM3 SMALLINT,
INOUT PARM4 FLOAT(22),
SQL programming
161

INOUT PARM6 DECIMAL(10,5),
INOUT PARM7 VARCHAR(10),
INOUT PARM8 DATE,
INOUT PARM9 TIME,
INOUT PARM10 TIMESTAMP)
EXTERNAL NAME TEST12.CALLPROC2
LANGUAGE C GENERAL WITH NULLS
EXEC SQL CREATE PROCEDURE P2 (INOUT PARM1 CHAR(10),
INOUT PARM2 INTEGER,
INOUT PARM3 SMALLINT,
INOUT PARM6 DECIMAL(10,5),
INOUT PARM7 VARCHAR(10),
INOUT PARM8 DATE,
INOUT PARM9 TIME,
INOUT PARM10 TIMESTAMP)
EXTERNAL NAME TEST12.CALLPROC
LANGUAGE PLI GENERAL WITH NULLS
Calling the P1 and P2 procedures
/**************************************************************/
/*********** START OF SQL C Application ***********************/
#include <stdio.h>
#include <string.h>
#include <decimal.h>
main()
{
EXEC SQL INCLUDE SQLCA;
char PARM1[10];
signed long int PARM2;
signed short int PARM3;
float PARM4;
double PARM5;
decimal(10,5) PARM6;
struct { signed short int parm7l;
char parm7c[10];
} PARM7;
char PARM8[10];
/* FOR DATE */
char PARM9[8];
/* FOR TIME */
char PARM10[26];
/* FOR TIMESTAMP */
/*******************************************************/
/* Initialize variables for the call to the procedures */
/*******************************************************/
strcpy(PARM1,"PARM1");
PARM2 = 7000;
PARM3 = -1;
PARM4 = 1.2;
PARM5 = 1.0;
PARM6 = 10.555;
PARM7.parm7l = 5;
strcpy(PARM7.parm7c,"PARM7");
strncpy(PARM8,"1994-12-31",10);
/* FOR DATE
*/
strncpy(PARM9,"12.00.00",8);
/* FOR TIME
*/
strncpy(PARM10,"1994-12-31-12.00.00.000000",26);
/* FOR TIMESTAMP */
/***********************************************/
/* Call the C procedure
*/
/*
*/
162
/*
*/
/***********************************************/
EXEC SQL CALL P1 (:PARM1, :PARM2, :PARM3,
:PARM4, :PARM5, :PARM6,
:PARM10 );
if (strncmp(SQLSTATE,"00000",5))
{
/* Handle error or warning returned on CALL statement */
}
/* Process return values from the CALL.
:
/***********************************************/
/* Call the PLI procedure
*/
/*
*/
/*
*/
/***********************************************/
/* Reset the host variables before making the CALL
/*
:
EXEC SQL CALL P2 (:PARM1, :PARM2, :PARM3,
:PARM10 );
if (strncmp(SQLSTATE,"00000",5))
{
/* Handle error or warning returned on CALL statement
}
/* Process return values from the CALL.
:
}
*/
*/
*/
*/
*/
/******** END OF C APPLICATION **********************************/

/****************************************************************/
Procedure P1
/******** START OF C PROCEDURE P1 *******************************/
/*
PROGRAM TEST12/CALLPROC2
*/
/****************************************************************/
#include <stdio.h>
#include <string.h>
main(argc,argv)
int argc;
char *argv[];
{
char parm1[11];
long int parm2;
short int parm3,i,j,*ind,ind1,ind2,ind3,ind4,ind5,ind6,ind7,
ind8,ind9,ind10;
float parm4;
double parm5;
decimal(10,5) parm6;
char parm7[11];
char parm8[10];
char parm9[8];
char parm10[26];
/* *********************************************************/
/* Receive the parameters into the local variables */
/* Character, date, time, and timestamp are passed as
*/
/* NUL terminated strings - cast the argument vector to
*/
/* the proper data type for each variable. Note that
*/
SQL programming
163
/*
/*
/*
/*
the argument vector can be used directly instead of

*/
copying the parameters into local variables - the copy */
is done here just to illustrate the method.
*/
*********************************************************/
/* Copy 10 byte character string into local variable

strcpy(parm1,argv[1]);
*/
/* Copy 4 byte integer into local variable

parm2 = *(int *) argv[2];
*/
/* Copy 2 byte integer into local variable

parm3 = *(short int *) argv[3];
*/
/* Copy floating point number into local variable

parm4 = *(float *) argv[4];
*/
/* Copy double precision number into local variable

parm5 = *(double *) argv[5];
*/
/* Copy decimal number into local variable

parm6 = *(decimal(10,5) *) argv[6];
*/
/**********************************************************/
/* Copy NUL terminated string into local variable.
*/
/* Note that the parameter in the CREATE PROCEDURE was
*/
/* declared as varying length character. For C, varying
*/
/* length are passed as NUL terminated strings unless
*/
/* FOR BIT DATA is specified in the CREATE PROCEDURE
*/
/**********************************************************/
strcpy(parm7,argv[7]);
/**********************************************************/
/* Copy date into local variable.
*/
/* Note that date and time variables are always passed in */
/* ISO format so that the lengths of the strings are
*/
/* known. strcpy works here just as well.
*/
/**********************************************************/
strncpy(parm8,argv[8],10);
/* Copy time into local variable
*/
/**********************************************************/
/* Copy timestamp into local variable.
*/
/* IBM SQL timestamp format is always passed so the length*/
/* of the string is known.
*/
/**********************************************************/
/**********************************************************/
/* The indicator array is passed as an array of short
*/
/* integers. There is one entry for each parameter passed */
/* on the CREATE PROCEDURE (10 for this example).
*/
/* Below is one way to set each indicator into separate
*/
/* variables.
*/
/**********************************************************/
ind = (short int *) argv[11];
ind1 = *(ind++);
ind2 = *(ind++);
ind3 = *(ind++);
ind4 = *(ind++);
ind5 = *(ind++);
ind6 = *(ind++);
ind7 = *(ind++);
ind8 = *(ind++);
ind9 = *(ind++);
ind10 = *(ind++);
164
:
/* Perform any additional processing here
*/
:
return;
}
/******** END OF C PROCEDURE P1 *******************************/
Procedure P2
/******** START OF PL/I PROCEDURE P2 **************************/
/******** PROGRAM TEST12/CALLPROC *****************************/
/**************************************************************/
CALLPROC :PROC( PARM1,PARM2,PARM3,PARM4,PARM5,PARM6,PARM7,
PARM8,PARM9,PARM10,PARM11);
DCL SYSPRINT FILE STREAM OUTPUT EXTERNAL;
OPEN FILE(SYSPRINT);
DCL PARM1 CHAR(10);
DCL PARM2 FIXED BIN(31);
DCL PARM3 FIXED BIN(15);
DCL PARM4 BIN FLOAT(22);
DCL PARM5 BIN FLOAT(53);
DCL PARM6 FIXED DEC(10,5);
DCL PARM7 CHARACTER(10) VARYING;
DCL PARM8 CHAR(10);
/* FOR DATE */
DCL PARM9 CHAR(8);
/* FOR TIME */
DCL PARM10 CHAR(26);
/* FOR TIMESTAMP */
DCL PARM11(10) FIXED BIN(15); /* Indicators */
/* PERFORM LOGIC - Variables can be set to other values for */
/* return to the calling program.
*/
:
END CALLPROC;
Example 2: A REXX procedure called from an ILE C program:

This example shows a REXX procedure called from an ILE C program.
Defining the REXX procedure
EXEC SQL CREATE PROCEDURE REXXPROC
(IN PARM1 CHARACTER(20),
IN PARM2 INTEGER,
IN PARM3 DECIMAL(10,5),
IN PARM4 DOUBLE PRECISION,
IN PARM5 VARCHAR(10),
IN PARM6 GRAPHIC(4),
IN PARM7 VARGRAPHIC(10),
IN PARM8 DATE,
IN PARM9 TIME,
IN PARM10 TIMESTAMP)
EXTERNAL NAME TEST.CALLSRC(CALLREXX)
LANGUAGE REXX GENERAL WITH NULLS
Calling the REXX procedure
/**************************************************************/
/*********** START OF SQL C Application ***********************/
#include <stdio.h>
SQL programming
165
#include <string.h>
#include <wcstr.h>
/*-----------------------------------------------------------*/
exec sql include sqlca;
exec sql include sqlda;
/* ***********************************************************/
/* Declare host variable for the CALL statement
*/
/* ***********************************************************/
char parm1[20];
signed long int parm2;
decimal(10,5) parm3;
double parm4;
struct { short dlen;
char dat[10];
} parm5;
wchar_t parm6[4] = { 0xC1C1, 0xC2C2, 0xC3C3, 0x0000 };
struct { short dlen;
wchar_t dat[10];
} parm7 = {0x0009, 0xE2E2,0xE3E3,0xE4E4, 0xE5E5, 0xE6E6,
0xE7E7, 0xE8E8, 0xE9E9, 0xC1C1, 0x0000 };
char parm8[10];
char parm9[8];
char parm10[26];
main()
{
/* *************************************************************/
/* Call the procedure - on return from the CALL statement the */
/* SQLCODE should be 0. If the SQLCODE is non-zero,
*/
/* the procedure detected an error.
*/
/* *************************************************************/
strcpy(parm1,"TestingREXX");
parm2 = 12345;
parm3 = 5.5;
parm4 = 3e3;
parm5.dlen = 5;
strcpy(parm5.dat,"parm6");
strcpy(parm8,"1994-01-01");
strcpy(parm9,"13.01.00");
strcpy(parm10,"1994-01-01-13.01.00.000000");
EXEC SQL CALL REXXPROC (:parm1, :parm2,
:parm3,:parm4,
:parm5, :parm6,
:parm7,
:parm8, :parm9,
:parm10);
if (strncpy(SQLSTATE,"00000",5))
{
/* handle error or warning returned on CALL
:
}
:
*/
}
/****** END OF SQL C APPLICATION ************************************/
/**********************************************************************/
/**********************************************************************/
/****** START OF REXX MEMBER TEST/CALLSRC CALLREXX ********************/
/**********************************************************************/
/* REXX source member TEST/CALLSRC CALLREXX
*/
/* Note the extra parameter being passed for the indicator*/
/* array.
*/
/*
*/
/* ACCEPT THE FOLLOWING INPUT VARIABLES SET TO THE
*/
166
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
SPECIFIED
AR1
AR2
AR3
AR4
AR5
AR6
AR7
AR8
AR9
AR10
AR11
VALUES :
CHAR(20)
= TestingREXX
INTEGER
= 12345
DECIMAL(10,5)
= 5.5
DOUBLE PRECISION = 3e3
VARCHAR(10)
= parm6
GRAPHIC
= GC1C1C2C2C3C3
VARGRAPHIC
=
GE2E2E3E3E4E4E5E5E6E6E7E7E8E8E9E9EAEA
DATE
= 1994-01-01
TIME
= 13.01.00
TIMESTAMP
=
1994-01-01-13.01.00.000000
INDICATOR ARRAY = +0+0+0+0+0+0+0+0+0+0
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
/**********************************************************/
/* Parse the arguments into individual parameters
*/
/**********************************************************/
parse arg ar1 ar2 ar3 ar4 ar5 ar6 ar7 ar8 ar9 ar10 ar11
/**********************************************************/
/* Verify that the values are as expected
*/
/**********************************************************/
if ar1<>"TestingREXX" then signal ar1tag
if ar2<>12345 then signal ar2tag
if ar3<>5.5 then signal ar3tag
if ar4<>3e3 then signal ar4tag
if ar5<>"parm6" then signal ar5tag
if ar6 <>"GAABBCC" then signal ar6tag
if ar7 <>"GSSTTUUVVWWXXYYZZAA" then ,
signal ar7tag
if ar8 <> "1994-01-01" then signal ar8tag
if ar9 <> "13.01.00" then signal ar9tag
if ar10 <> "1994-01-01-13.01.00.000000" then signal ar10tag
if ar11 <> "+0+0+0+0+0+0+0+0+0+0" then signal ar11tag
/************************************************************/
/* Perform other processing as necessary ..
*/
/************************************************************/
:
/************************************************************/
/* Indicate the call was successful by exiting with a
*/
/* return code of 0
*/
/************************************************************/
exit(0)
ar1tag:
say "ar1 did not match" ar1
exit(1)
ar2tag:
say "ar2 did not match" ar2
exit(1)
:
:
/************ END OF REXX MEMBER
**********************************/
Returning result sets from stored procedures

In addition to returning output parameters, a stored procedure can return a result set (that is, a result
table associated with a cursor opened in the stored procedure) to the application that issues the CALL
statement. The application can then issue fetch requests to read the rows of the result set cursor.
Whether a result set gets returned depends on the returnability attribute of the cursor. The cursor's
returnability attribute can be explicitly given in the DECLARE CURSOR statement or it can be defaulted.
The SET RESULT SETS statement also allows for an indication of where the result sets should be
returned. By default, cursors which are opened in a stored procedure are defined to have a returnability
SQL programming
167
attribute of RETURN TO CALLER. To return the result set associated with the cursor to the application
which called the outermost procedure in the call stack, the returnability attribute of RETURN TO CLIENT
is specified on the DECLARE CURSOR statement. This will allow inner procedures to return result sets
when the application calls nested procedures. For cursors whose result sets are never to be returned to
caller or client, the returnability attribute of WITHOUT RETURN is specified on the DECLARE CURSOR
statement.
Note: When you use COBOL, the result sets are automatically closed because of the setup of the COBOL
program. Change the EXIT PROGRAM statement to EXIT PROGRAM AND CONTINUE RUN
UNIT and the result sets should be returned.
There are many cases where opening the cursor in a stored procedure and returning its result set
provides advantages over opening the cursor directly in the application. For instance, security to the
tables referenced in the query can be adopted from the stored procedure so that users of the application
do not need to be granted direct authority to the tables. Instead, they are given authority to call the
stored procedure, which is compiled with adequate authority to access the tables. Another advantage to
opening the cursors in the stored procedure is that multiple result sets can be returned from a single call
to the stored procedure, which can be more efficient that opening the cursors separately from the calling
application. Additionally, each call to the same stored procedure may return a different number of result
sets, providing some application versatility.
The interfaces that can work with stored procedure result sets include JDBC, CLI, and ODBC. An
example of how to use these API interfaces for working with stored procedure result sets is included in
the following examples.
Example 1: Calling a stored procedure that returns a single result set:
This example shows the API calls that an Open Database Connectivity (ODBC) application can use to call
a stored procedure to return a result set.
Note that in this example the DECLARE CURSOR statement does not have an explicit returnability
specified. When there is only a single stored procedure on the call stack, the returnability attribute of
RETURN TO CALLER as well as that of RETURN TO CLIENT will make the result set available to the
caller of the application. Also note that the stored procedure is defined with a DYNAMIC RESULT SETS
clause. For SQL procedures, this clause is required if the stored procedure will be returning result sets.
Defining the stored procedure:
PROCEDURE prod.resset
CREATE PROCEDURE prod.resset () LANGUAGE SQL
DYNAMIC RESULT SETS 1
BEGIN
DECLARE C1 CURSOR FOR SELECT * FROM QIWS.QCUSTCDT;
OPEN C1;
RETURN;
END
ODBC application
Note: Some of the logic has been removed.
:
strcpy(stmt,"call prod.resset()");
rc = SQLExecDirect(hstmt,stmt,SQL_NTS);
if (rc == SQL_SUCCESS)
{
168
//
//
rc
if
CALL statement has executed successfully. Process the result set.

Get number of result columns for the result set.
= SQLNumResultCols(hstmt, &wNum);
(rc == SQL_SUCCESS)
// Get description of result columns in result set
{ rc = SQLDescribeCol(hstmt,);
if (rc == SQL_SUCCESS)
:
{
// Bind result columns based on attributes returned
//
rc = SQLBindCol(hstmt,);
:
// FETCH records until EOF is returned
rc = SQLFetch(hstmt);
while (rc == SQL_SUCCESS)
{ // process result returned on the SQLFetch
:
rc = SQLFetch(hstmt);
}
:
}
// Close the result set cursor when done with it.
rc = SQLFreeStmt(hstmt,SQL_CLOSE);
:
Example 2: Calling a stored procedure that returns a result set from a nested procedure:
This example shows how a nested stored procedure can open and return a result set to the outermost
procedure.
To return a result set to the outermost procedure in an environment where there are nested stored
procedures, the RETURN TO CLIENT returnability attribute should be used on the DECLARE CURSOR
statement or on the SET RESULT SETS statement to indicate that the cursors are to be returned to the
application which called the outermost procedure. Note that this nested procedure returns two result sets
to the client; the first, an array result set, and the second a cursor result set. Both an ODBC and a JDBC
client application are shown below along with the stored procedures.
Defining the stored procedures
CREATE PROCEDURE prod.rtnnested () LANGUAGE CL DYNAMIC RESULT SET 2
EXTERNAL NAME prod.rtnnested GENERAL
CREATE PROCEDURE prod.rtnclient () LANGUAGE RPGLE
EXTERNAL NAME prod.rtnclient GENERAL
CL source for stored procedure prod.rtnnested
PGM
CALL
PGM(PROD/RTNCLIENT)
ILE RPG source for stored procedure prod.rtnclient

DRESULT
DS
D COL1
1
C
1
DO
C
X
OCCUR
C
EVAL
C
ENDDO
C
EVAL
C/EXEC SQL DECLARE C2 CURSOR
OCCURS(20)
16A
10
X
RESULT
COL1=array result set
2 0
X=X-1
WITH RETURN TO CLIENT
SQL programming
169
C+ FOR SELECT LSTNAM FROM QIWS.QCUSTCDT FOR FETCH ONLY

C/END-EXEC
C/EXEC SQL
C+ OPEN C2
C/END-EXEC
C/EXEC SQL
C+ SET RESULT SETS FOR RETURN TO CLIENT ARRAY :RESULT FOR :X ROWS,
C+ CURSOR C2
C/END-EXEC
C
SETON
C
RETURN
LR
ODBC application
//*******************************************************************
//
// Module:
//
Examples.C
//
// Purpose:
//
Perform calls to stored procedures to get back result sets.
//
// *******************************************************************
#include "common.h"
#include "stdio.h"
// *******************************************************************
//
// Local function prototypes.
//
// *******************************************************************
SWORD
BOOL
BOOL
BOOL
FAR
FAR
FAR
FAR
PASCAL
PASCAL
PASCAL
PASCAL
RetClient(lpSERVERINFO lpSI);
Bind_Params(HSTMT);
Bind_First_RS(HSTMT);
Bind_Second_RS(HSTMT);
// *******************************************************************
//
// Constant strings definitions for SQL statements used in
// the auto test.
//
// *******************************************************************
//
// Declarations of variables global to the auto test.
//
// *******************************************************************
#define ARRAYCOL_LEN 16
#define LSTNAM_LEN 8
char stmt[2048];
char buf[2000];
UDWORD rowcnt;
char arraycol[ARRAYCOL_LEN+1];
char lstnam[LSTNAM_LEN+1];
SDWORD cbcol1,cbcol2;
lpSERVERINFO lpSI;
/* Pointer to a SERVERINFO structure. */
// ********************************************************************
//
// Define the auto test name and the number of test cases
170
//
for the current auto test. These informations will
//
be returned by AutoTestName().
//
// ********************************************************************
LPSTR szAutoTestName = CREATE_NAME("Result Sets Examples");
UINT iNumOfTestCases = 1;
// *******************************************************************
//
// Define the structure for test case names, descriptions,
//
and function names for the current auto test.
//
Test case names and descriptions will be returned by
//
AutoTestDesc(). Functions will be run by
//
AutoTestFunc() if the bits for the corresponding test cases
//
are set in the rglMask member of the SERVERINFO
//
structure.
//
// *******************************************************************
struct TestCase TestCasesInfo[] =
{
"Return to Client",
"2 result sets ",
RetClient
};
// *******************************************************************
//
// Sample return to Client:
//
Return to Client result sets. Call a CL program which in turn
//
calls an RPG program which returns 2 result sets. The first
//
result set is an array result set and the second is a cursor
//
result set.
//
//
// *******************************************************************
SWORD FAR PASCAL RetClient(lpSERVERINFO lpSI)
{
SWORD
sRC = SUCCESS;
RETCODE
returncode;
HENV
henv;
HDBC
hdbc;
HSTMT
hstmt;
if (FullConnect(lpSI, &henv, &hdbc, &hstmt) == FALSE)

{
sRC = FAIL;
goto ExitNoDisconnect;
}
// ********************************************************
// Call CL program PROD.RTNNESTED, which in turn calls RPG
// program RTNCLIENT.
// ********************************************************
strcpy(stmt,"CALL PROD.RTNNESTED()");
// **************************************************************
// Call the CL program prod.rtnnested. This program will in turn
// call the RPG program proc.rtnclient, which will open 2 result
// sets for return to this ODBC application.
// *************************************************************
returncode = SQLExecDirect(hstmt,stmt,SQL_NTS);
if (returncode != SQL_SUCCESS)
SQL programming
171
{
vWrite(lpSI, "CALL PROD.RTNNESTED is not Successful", TRUE);
}
else
{
vWrite(lpSI, "CALL PROC.RTNNESTED was Successful", TRUE);
}
// **************************************************************
// Bind the array result set output column. Note that the result
// sets are returned to the application in the order that they
// are specified on the SET RESULT SETS statement.
// *************************************************************
if (Bind_First_RS(hstmt) == FALSE)
{
myRETCHECK(lpSI, henv, hdbc, hstmt, SQL_SUCCESS,
returncode, "Bind_First_RS");
sRC = FAIL;
goto ErrorRet;
}
else
{
vWrite(lpSI, "Bind_First_RS Complete...", TRUE);
}
// **************************************************************
// Fetch the rows from the array result set. After the last row
// is read, a returncode of SQL_NO_DATA_FOUND will be returned to
// the application on the SQLFetch request.
// **************************************************************
returncode = SQLFetch(hstmt);
while(returncode == SQL_SUCCESS)
{
wsprintf(stmt,"array column = %s",arraycol);
vWrite(lpSI,stmt,TRUE);
}
if (returncode == SQL_NO_DATA_FOUND) ;
else {
myRETCHECK(lpSI, henv, hdbc, hstmt, SQL_SUCCESS_WITH_INFO,
returncode, "SQLFetch");
sRC = FAIL;
goto ErrorRet;
}
// ********************************************************
// Get any remaining result sets from the call. The next
// result set corresponds to cursor C2 opened in the RPG
// Program.
// ********************************************************
returncode = SQLMoreResults(hstmt);
{
myRETCHECK(lpSI, henv, hdbc, hstmt, SQL_SUCCESS, returncode, "SQLMoreResults");
sRC = FAIL;
goto ErrorRet;
}
// **************************************************************
// Bind the cursor result set output column. Note that the result
// sets are returned to the application in the order that they
// are specified on the SET RESULT SETS statement.
// *************************************************************
if (Bind_Second_RS(hstmt) == FALSE)
{
returncode, "Bind_Second_RS");
sRC = FAIL;
goto ErrorRet;
}
172
else
{
vWrite(lpSI, "Bind_Second_RS Complete...", TRUE);
}
// **************************************************************
// Fetch the rows from the cursor result set. After the last row
// is read, a returncode of SQL_NO_DATA_FOUND will be returned to
// the application on the SQLFetch request.
// **************************************************************
while(returncode == SQL_SUCCESS)
{
wsprintf(stmt,"lstnam = %s",lstnam);
vWrite(lpSI,stmt,TRUE);
}
if (returncode == SQL_NO_DATA_FOUND) ;
else {
myRETCHECK(lpSI, henv, hdbc, hstmt, SQL_SUCCESS_WITH_INFO,
returncode, "SQLFetch");
sRC = FAIL;
goto ErrorRet;
}
returncode = SQLFreeStmt(hstmt,SQL_CLOSE);
{
returncode, "Close statement");
sRC = FAIL;
goto ErrorRet;
}
else
{
vWrite(lpSI, "Close statement...", TRUE);
}
ErrorRet:
FullDisconnect(lpSI, henv, hdbc, hstmt);
if (sRC == FAIL)
{
// a failure in an ODBC function that prevents completion of the
// test - for example, connect to the server
vWrite(lpSI, "\t\t *** Unrecoverable RTNClient Test FAILURE ***",
} /* endif */
TRUE);
ExitNoDisconnect:
return(sRC);
} // RetClient
BOOL FAR PASCAL Bind_First_RS(HSTMT hstmt)

{
RETCODE rc = SQL_SUCCESS;
rc = SQLBindCol(hstmt,1,SQL_C_CHAR,arraycol,ARRAYCOL_LEN+1, &cbcol1);
if (rc != SQL_SUCCESS) return FALSE;
return TRUE;
}
BOOL FAR PASCAL Bind_Second_RS(HSTMT hstmt)
{
SQL programming
173
RETCODE rc = SQL_SUCCESS;
rc = SQLBindCol(hstmt,1,SQL_C_CHAR,lstnam,LSTNAM_LEN+1,&dbcol2);
if (rc != SQL_SUCCESS) return FALSE;
return TRUE;
}
JDBC application
//----------------------------------------------------------// Call Nested procedures which return result sets to the
// client, in this case a JDBC client.
//----------------------------------------------------------import java.sql.*;
public class callNested
{
public static void main (String argv[])
// Main entry point
{
try {
Class.forName("com.ibm.db2.jdbc.app.DB2Driver");
}
catch (ClassNotFoundException e) {
e.printStackTrace();
}
try {
Connection jdbcCon =
DriverManager.getConnection("jdbc:db2:lp066ab","Userid","xxxxxxx");
jdbcCon.setAutoCommit(false);
CallableStatement cs = jdbcCon.prepareCall("CALL PROD.RTNNESTED");
cs.execute();
ResultSet rs1 = cs.getResultSet();
int r = 0;
while (rs1.next())
{
r++;
String s1 = rs1.getString(1);
System.out.print("Result set 1 Row: " + r + ": ");
System.out.print(s1 + " " );
System.out.println();
}
cs.getMoreResults();
r = 0;
ResultSet rs2 = cs.getResultSet();
while (rs2.next())
{
r++;
String s2 = rs2.getString(1);
System.out.print("Result set 2 Row: " + r + ": ");
System.out.print(s2 + " ");
System.out.println();
}
}
catch ( SQLException e ) {
System.out.println( "SQLState: " + e.getSQLState() );
System.out.println( "Message : " + e.getMessage() );
e.printStackTrace();
}
} // main
}
| Writing a program or SQL procedure to receive the result sets from a stored
| procedure
| You can write a program to receive results sets from a stored procedure for either a fixed number of
| result sets, for which you know the contents, or a variable number of result sets, for which you do not
| know the contents.
174
|
|
|
Returning a known number of result sets is simpler to write, but if you write the code to handle a
varying number of result sets you do not need to make major modifications to your program if the stored
procedure changes.
|
|
|
|
|
|
|
|
|
|
|
|
The basic steps for receiving result sets are as follows:

1. Declare a locator variable for each result set that will be returned.
If you do not know how many result sets will be returned, declare enough result set locators for the
maximum number of result sets that might be returned.
2. Call the stored procedure and check the SQL return code.
If the SQLCODE from the CALL statement is +466, the stored procedure has returned result sets.
3. Determine how many result sets the stored procedure is returning.
If you already know how many result sets the stored procedure returns, you can skip this step.
Use the SQL statement DESCRIBE PROCEDURE to determine the number of result sets. DESCRIBE
PROCEDURE places information about the result sets in an SQLDA or SQL descriptor.
For an SQL descriptor, when the DESCRIBE PROCEDURE statement completes, the following values
can be retrieved:
|
|
|
|
|
|
|
|
v DB2_RESULT_SETS_COUNT contains the number of result sets returned by the stored procedure.
v One descriptor area item is returned for each result set:
DB2_CURSOR_NAME contains the name of the cursor used by the stored procedure to return
the result set.
The DB2_RESULT_SET_ROWS contains the estimated number of rows in the result set. A value
of -1 indicates that no estimate of the number of rows in the result set is available.
DB2_RESULT_SET_LOCATOR contains the value of the result set locator associated with the
result set.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For an SQLDA, make the SQLDA large enough to hold the maximum number of result sets that the
stored procedure might return. When the DESCRIBE PROCEDURE statement completes, the fields in
the SQLDA contain the following values:
v SQLD contains the number of result sets returned by the stored procedure.
v Each SQLVAR entry gives information about a result set. In an SQLVAR entry:
The SQLNAME field contains the name of the cursor used by the stored procedure to return the
result set.
The SQLIND field contains the estimated number of rows in the result set. A value of -1
indicates that no estimate of the number of rows in the result set is available.
The SQLDATA field contains the value of the result set locator, which is the address of the result
set.
4. Link result set locators to result sets.
You can use the SQL statement ASSOCIATE LOCATORS to link result set locators to result sets. The
ASSOCIATE LOCATORS statement assigns values to the result set locator variables. If you specify
more locators than the number of result sets returned, the extra locators will be ignored.
|
|
|
|
|
|
|
|
If you executed the DESCRIBE PROCEDURE statement previously, the result set locator values can be
retrieved from the DB2_RESULT_SET_LOCATOR in the SQL descriptor or from the SQLDATA fields
of the SQLDA. You can copy the values from these fields to the result set locator variables manually,
or you can execute the ASSOCIATE LOCATORS statement to do it for you.
The stored procedure name that you specify in an ASSOCIATE LOCATORS or DESCRIBE
PROCEDURE statement must be a procedure name that has already been used in the CALL statement
that returns the result sets.
5. Allocate cursors for fetching rows from the result sets.
|
|
|
Use the SQL statement ALLOCATE CURSOR to link each result set with a cursor. Execute one
ALLOCATE CURSOR statement for each result set. The cursor names can be different from the cursor
names in the stored procedure.
SQL programming
175
| 6. Determine the contents of the result sets.

|
If you already know the format of the result set, you can skip this step.
|
Use the SQL statement DESCRIBE CURSOR to determine the format of a result set and put this
|
information in an SQL descriptor or an SQLDA. For each result set, you need an SQLDA big enough
|
to hold descriptions of all columns in the result set.
|
You can use DESCRIBE CURSOR only for cursors for which you executed ALLOCATE CURSOR
|
previously.
|
After you execute DESCRIBE CURSOR, if the cursor for the result set is declared WITH HOLD, for an
|
SQL descriptor DB2_CURSOR_HOLD can be checked. For an SQLDA the high-order bit of the eighth
|
byte of field SQLDAID in the SQLDA is set to 1.
| 7. Fetch rows from the result sets into host variables by using the cursors that you allocated with the
|
ALLOCATE CURSOR statements.
|
If you executed the DESCRIBE CURSOR statement, perform these steps before you fetch the rows:
|
|
|
|
|
a. Allocate storage for host variables and indicator variables. Use the contents of the SQL descriptor
or SQLDA from the DESCRIBE CURSOR statement to determine how much storage you need for
each host variable.
b. Put the address of the storage for each host variable in the appropriate SQLDATA field of the
SQLDA.
|
|
c. Put the address of the storage for each indicator variable in the appropriate SQLIND field of the
SQLDA.
Fetching rows from a result set is the same as fetching rows from a table.
| The following examples show C language code that accomplishes each of these steps. Coding for other
| languages is similar.
|
|
|
|
|
|
|
|
|
|
||
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||
||
|
|
|
|
|
|
The following example demonstrates how you receive result sets when you know how many result sets
are returned and what is in each result set.
/*************************************************************/
/* Declare result set locators. For this example,
*/
/* assume you know that two result sets will be returned.
*/
/* Also, assume that you know the format of each result set. */
/*************************************************************/
EXEC SQL BEGIN DECLARE SECTION;
static volatile SQL TYPE IS RESULT_SET_LOCATOR loc1, loc2;
EXEC SQL END DECLARE SECTION;
.
.
.
/*************************************************************/
/* Call stored procedure P1.
*/
/* Check for SQLCODE +466, which indicates that result sets */
/* were returned.
*/
/*************************************************************/
EXEC SQL CALL P1(:parm1, :parm2, ...);
if(SQLCODE==+466)
{
/*************************************************************/
/* Establish a link between each result set and its
*/
/* locator using the ASSOCIATE LOCATORS.
*/
/*************************************************************/
EXEC SQL ASSOCIATE LOCATORS (:loc1, :loc2) WITH PROCEDURE P1;
.
.
.
/*************************************************************/
/* Associate a cursor with each result set.
*/
/*************************************************************/
EXEC SQL ALLOCATE C1 CURSOR FOR RESULT SET :loc1;
/*************************************************************/
176
|
|
|
|
|
||
||
|
|
|
|
||
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
||
|
|
|
|
|
|
|
||
||
|
|
|
|
|
|
|
|
|
|
/* Fetch the result set rows into host variables.

*/
/*************************************************************/
while(SQLCODE==0)
{
EXEC SQL FETCH C1 INTO :order_no, :cust_no;
..
.
}
while(SQLCODE==0)
{
EXEC SQL FETCH C2 :order_no, :item_no, :quantity;
..
.
}
}
The following example demonstrates how you receive result sets when you do not know how many
result sets are returned or what is in each result set.
/*************************************************************/
*/
/* assume that no more than three result sets will be
*/
/* returned, so declare three locators. Also, assume
*/
/* that you do not know the format of the result sets.
*/
/*************************************************************/
static volatile SQL TYPE IS RESULT_SET_LOCATOR loc1, loc2, loc3;
..
.
/*************************************************************/
/* Call stored procedure P2.
*/
/* Check for SQLCODE +466, which indicates that result sets */
/* were returned.
*/
/*************************************************************/
EXEC SQL CALL P2(:parm1, :parm2, ...);
if(SQLCODE==+466)
{
/*************************************************************/
/* Determine how many result sets P2 returned, using the
*/
/* statement DESCRIBE PROCEDURE. :proc_da is an SQLDA
*/
/* with enough storage to accommodate up to three SQLVAR
*/
/* entries.
*/
/*************************************************************/
EXEC SQL DESCRIBE PROCEDURE P2 INTO :proc_da;
..
.
/*************************************************************/
/* Now that you know how many result sets were returned,
*/
/* establish a link between each result set and its
*/
/* locator using the ASSOCIATE LOCATORS. For this example, */
/* we assume that three result sets are returned.
*/
/*************************************************************/
EXEC SQL ASSOCIATE LOCATORS (:loc1, :loc2, :loc3) WITH PROCEDURE P2;
..
.
/*************************************************************/
/* Associate a cursor with each result set.
*/
/*************************************************************/
/*************************************************************/
/* Use the statement DESCRIBE CURSOR to determine the
*/
/* format of each result set.
*/
SQL programming
177
|
|
|
|
||
||
|
|
|
|
|
|
|
||
||
|
|
|
|
|
|
|
||
||
|
|
|
|
||
||
|
|
|
|
||
||
|
|
/*************************************************************/
EXEC SQL DESCRIBE CURSOR C1 INTO :res_da1;
.
.
.
/*************************************************************/
/* Assign values to the SQLDATA and SQLIND fields of the
*/
/* SQLDAs that you used in the DESCRIBE CURSOR statements.
*/
/* These values are the addresses of the host variables and */
/* indicator variables into which DB2 will put result set
*/
/* rows.
*/
/*************************************************************/
.
.
.
/*************************************************************/
/* Fetch the result set rows into the storage areas
*/
/* that the SQLDAs point to.
*/
/*************************************************************/
while(SQLCODE==0)
{
EXEC SQL FETCH C1 USING :res_da1;
.
.
.
}
while(SQLCODE==0)
{
.
.
.
}
while(SQLCODE==0)
{
.
.
.
}
}
| The following example demonstrates how you receive result sets using an SQL descriptor.
| This is the SQL procedure that will be called:
| create procedure owntbl()
|
dynamic result sets 1
|
begin
|
declare c1 cursor for
|
select name, dbname from qsys2.systables
|
where creator = system_user ;
|
open c1 ;
|
return ;
|
end
|
|
|
|
|
|
|
|
|
|
|
|
This is the program that will process the result sets:

#include <string.h>
#include <stdio.h>
#include <stdlib.h>
/*************************************************************/
*/
/* you know that only one result set will be returned,
*/
/* so only one locator is declared.
*/
/*************************************************************/
178
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
||
|
|
|
|
static volatile SQL TYPE IS RESULT_SET_LOCATOR loc1;

struct {
short len;
char data[128];
} tblName;
/* table name */
struct {
short len;
char data[128];
} schName;
/* schema name */
void main(int argc, char* argv[])
{
/*************************************************************/
/* Call the procedure that might return a result set. Check */
/* the returned SQLCODE to see if result sets were returned. */
/*************************************************************/
int noMoreData = 0;
EXEC SQL WHENEVER SQLERROR GOTO error;
EXEC SQL CALL OWNTBL ;
if (SQLCODE != 466) {
goto error;
}
/*************************************************************/
/* Since you know only one result set can be returned from
*/
/* this procedure, associate a locator with the result set
*/
/* and define a cursor to be used with it.
*/
/*************************************************************/
EXEC SQL ASSOCIATE LOCATORS (:loc1) WITH PROCEDUREOWNTBL ;
EXEC SQL ALLOCATE C1 CURSOR FOR RESULT SET :loc1 ;
/*************************************************************/
/* Define the descriptor to use for fetching data from the
*/
/* cursor.
*/
/*************************************************************/
EXEC SQL ALLOCATE DESCRIPTOR desc WITH MAX 10 ;
EXEC SQL DESCRIBE CURSOR C1 USING SQL DESCRIPTOR desc ;
EXEC SQL WHENEVER NOT FOUND GOTO enddata;
while ( noMoreData == 0 ) {
EXEC SQL FETCH C1 INTO SQL DESCRIPTOR desc ;
memset(tblName.data,0x00,sizeof(tblName.data));
memset(schName.data,0x00,sizeof(schName.data));
EXEC SQL GET DESCRIPTOR desc VALUE 1 :tblName = DATA;
EXEC SQL GET DESCRIPTOR desc VALUE 2 :schName = DATA;
printf("Table: %s Schema: %s \n",
tblName.data,schName.data);
}
enddata:
printf("All rows fetched.\n");
return;
error:
printf("Unexpected error, SQLCODE = %d \n", SQLCODE);
return;
}
The following example demonstrates how you can use an SQL procedure to receive result sets. It is just a
fragment of a larger SQL procedure.
DECLARE RESULT1 RESULT_SET_LOCATOR VARYING;
DECLARE
RESULT2 RESULT_SET_LOCATOR VARYING;
..
.
CALL TARGETPROCEDURE();
ASSOCIATE RESULT SET LOCATORS(RESULT1,RESULT2)
WITH PROCEDURE TARGETPROCEDURE;
SQL programming
179
|
|
|
|
|
|
|
|
|
|
|
||
||
ALLOCATE RSCUR1 CURSOR FOR RESULT1;

ALLOCATE RSCUR2 CURSOR FOR RESULT2;
Parameter passing conventions for stored procedures and user-defined functions
WHILE AT_END = 0 DO
FETCH RSCUR1 INTO VAR1;
SET TOTAL1 = TOTAL1 + VAR1;
END WHILE;
WHILE AT_END = 0 DO
FETCH RSCUR2 INTO VAR2;
SET TOTAL2 = TOTAL2 + VAR2;
END
WHILE;
.
.
.
The CALL statement and a function call can pass arguments to programs written in all supported host
languages and REXX procedures.
Each language supports different data types that are tailored to it, as shown in the following tables. The
SQL data type is contained in the leftmost column of each table. Other columns in that row contain an
indication of whether that data type is supported as a parameter type for a particular language. If the
column is blank, the data type is not supported as a parameter type for that language. A host variable
declaration indicates that DB2 for i supports this data type as a parameter in this language. The
declaration indicates how host variables must be declared to be received and set properly by the
procedure or function. When an SQL procedure or function is called, all SQL data types are supported so
no column is provided in the table.
Table 47. Data types of parameters
SQL data type
C and C++
CL
COBOL and ILE COBOL
SMALLINT
short
PIC S9(4) BINARY
INTEGER
long
PIC S9(9) BINARY
BIGINT
long long
PIC S9(18) BINARY

Note: Only supported for
ILE COBOL.
DECIMAL(p,s)
decimal(p,s)
TYPE(*DEC) LEN(p s)
PIC S9(p-s)V9(s)
PACKED-DECIMAL
Note: Precision must not
be greater than 18.
NUMERIC(p,s)
PIC S9(p-s)V9(s) DISPLAY

SIGN LEADING
SEPARATE
Note: Precision must not
be greater than 18.
DECFLOAT
_Decimal32, _Decimal64,
_Decimal128
C.
REAL or FLOAT(p)
float
COMP-1
ILE COBOL.
180
Table 47. Data types of parameters (continued)

SQL data type
C and C++
CL
COBOL and ILE COBOL
DOUBLE PRECISION or
FLOAT or FLOAT(p)
double
CHARACTER(n)
char ... [n+1]
VARCHAR(n)
char ... [n+1]
Varying-Length Character
String
VARCHAR(n) FOR BIT

DATA
VARCHAR structured form
Varying-Length Character
String
CLOB
CLOB structured form
COMP-2
ILE COBOL.
TYPE(*CHAR) LEN(n)
PIC X(n)

ILE COBOL.
GRAPHIC(n)
wchar_t ... [n+1]
PIC G(n) DISPLAY-1 or PIC

N(n)
ILE COBOL.
VARGRAPHIC(n)
VARGRAPHIC structured
form
Varying-Length Graphic
String
ILE COBOL.
DBCLOB
DBCLOB structured form

ILE COBOL.
BINARY
BINARY structured form
VARBINARY
VARBINARY structured
form
form
BLOB
BLOB structured form

ILE COBOL.
DATE
char ... [11]
TYPE(*CHAR) LEN(10)
PIC X(10)
Note: For ILE COBOL only,
FORMAT DATE.
XML
XML structured form
TIME
char ... [9]
XML structured form

TYPE(*CHAR) LEN(8)
PIC X(8)
FORMAT TIME.
TIMESTAMP
char ... [27]
TYPE(*CHAR) LEN(26)
PIC X(26)
FORMAT TIMESTAMP.
ROWID
ROWID structured form
short
PIC S9(4) BINARY
DataLink
Array
Indicator variable
SQL programming
181

SQL data type
Java parameter style

JAVA
Java parameter style

DB2GENERAL
PL/I
SMALLINT
short
short
FIXED BIN(15)
INTEGER
int
int
FIXED BIN(31)
BIGINT
long
long
DECIMAL(p,s)
BigDecimal
BigDecimal
NUMERIC(p,s)
BigDecimal
BigDecimal
DECFLOAT
BigDecimal
BigDecimal
REAL or FLOAT(p)
float
float
FLOAT BIN(p)
DOUBLE PRECISION or
FLOAT or FLOAT(p)
double
double
FLOAT BIN(p)
CHARACTER(n)
String
String
CHAR(n)
VARCHAR(n)
String
String
CHAR(n) VAR
VARCHAR(n) FOR BIT

DATA
byte[ ]
com.ibm.db2.app.Blob
CHAR(n) VAR
CLOB
java.sql.Clob
com.ibm.db2.app.Clob
GRAPHIC(n)
String
String
VARGRAPHIC(n)
String
String
DBCLOB
java.sql.Clob
com.ibm.db2.app.Clob
BINARY
byte[ ]
VARBINARY
byte[ ]
form
BLOB
java.sql.Blob
XML AS CLOB
java.sql.CLOB
XML AS BLOB
java.sql.BLOB
DATE
Date
String
CHAR(10)
TIME
Time
String
CHAR(8)
TIMESTAMP
Timestamp
String
CHAR(26)
ROWID
byte[]
FIXED DEC(p,s)
DataLink
Array
java.sql.Array
Indicator variable
182
FIXED BIN(15)

SQL data type
REXX
SMALLINT
RPG
ILE RPG
Data structure that contains a

single sub-field. B in position 43,
length must be 2, and 0 in
position 52 of the sub-field
specification.
Data specification. B in position

40, length must be <= 4, and 00
in positions 41-42 of the sub-field
specification.
or
Data specification. I in position
40, length must be 5, and 00 in
positions 41-42 of the sub-field
specification.
INTEGER
Numeric string with

no decimal (and an
optional leading sign) length must be 4, and 0 in
specification.

40, length must be <=09 and
>=05, and 00 in positions 41-42
of the sub-field specification.
or
specification.
BIGINT

specification.
DECIMAL(p,s)
Numeric string with a Data structure that contains a

decimal (and an
single sub-field. P in position 43
optional leading sign) and 0 through 9 in position 52 of
the sub-field specification. or A
numeric input field or calculation
result field.
NUMERIC(p,s)

single sub-field. Blank in position
43 and 0 through 9 in position 52
Data specification. P in position

40 and 00 through 31 in positions
41-42 of the sub-field
specification.
Data specification. S in position

40, or Blank in position 40 and
00 through 31 in position 41-42
DECFLOAT
REAL or FLOAT(p)
String with digits,

then an E, (then an
optional sign), then
digits
Data specification. F in position

40, length must be 4.
DOUBLE PRECISION String with digits,

or FLOAT or
then an E, (then an
FLOAT(p)
optional sign), then
digits
Data specification. F in position

40, length must be 8.
CHARACTER(n)
String with n
characters within two
apostrophes
Data structure field without

sub-fields or data structure that
contains a single sub-field. Blank
in position 43 and 52 of the
sub-field specification. or A
character input field or
calculation result field.
Data specification. A in position

specification.
SQL programming
183

SQL data type
REXX
VARCHAR(n)
String with n
apostrophes

specification and the keyword
VARYING in positions 44-80.
VARCHAR(n) FOR
BIT DATA
String with n
apostrophes

specification and the keyword
VARYING in positions 44-80.
CLOB
ILE RPG
GRAPHIC(n)
String starting with

G', then n double-byte
characters, then '
Data specification. G in position

40 of the sub-field specification.
VARGRAPHIC(n)
String starting with

G', then n double-byte
characters, then '
Data specification. G in position

40 of the sub-field specification
and the keyword VARYING in
positions 44-80.
DBCLOB
BINARY
VARBINARY
VARBINARY structured form
BLOB
XML
XML structured form
DATE
String with 10
apostrophes

Data specification. D in position
contains a single sub-field. Blank DATFMT(*ISO) in position 44-80.
sub-field specification. Length is
10. or A character input field or
TIME
String with 8
apostrophes

Data specification. T in position
contains a single sub-field. Blank TIMFMT(*ISO) in position 44-80.
TIMESTAMP
String with 26
apostrophes

Data specification. Z in position
contains a single sub-field. Blank
ROWID
DataLink
RPG
Array
184

SQL data type
REXX
RPG
Indicator variable
Numeric string with

no decimal (and an
optional leading sign). length must be 2, and 0 in
specification.
ILE RPG
40, length must be <=4, and 00 in
specification.
Related concepts:
Java SQL routines
Indicator variables and stored procedures

Host variables with indicator variables can be used with the CALL statement to pass additional
information to and from a procedure.
To indicate that the associated host variable contains the null value, the indicator variable is set to a
negative value of -1, -2, -3, -4, or -6. A CALL statement with indicator variables is processed as follows:
v If the indicator variable is negative, a default value is passed for the associated host variable on the
CALL statement and the indicator variable is passed unchanged.
v If the indicator variable is not negative, the host variable and the indicator variable are passed
unchanged.
When an SQL procedure or an external procedure that was compiled without the *EXTIND option is
called, the extended indicator values of -5 and -7 cannot be passed. An error is then issued on the CALL
statement. When an external procedure that was compiled with the *EXTIND option is called, the
extended indicator values can be passed.
The processing rules are the same for input parameters to the procedure as well as output parameters
returned from the procedure. When indicator variables are used, the correct coding method is to check
the value of the indicator variable first before using the associated host variable.
The following example illustrates the handling of indicator variables in CALL statements. Notice that the
logic checks the value of the indicator variable before using the associated variable. Also note how the
indicator variables are passed into procedure PROC1 (as a third argument that consists of an array of
2-byte values).
Assume that a procedure is defined as follows. The ILE RPG program was compiled to not allow
extended indicators.
CREATE PROCEDURE PROC1
(INOUT DECIMALOUT DECIMAL(7,2), INOUT DECOUT2 DECIMAL(7,2))
EXTERNAL NAME LIB1.PROC1 LANGUAGE RPGLE
GENERAL WITH NULLS)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Program CRPG
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
D INOUT1
S
7P 2
D INOUT1IND
S
4B 0
D INOUT2
S
7P 2
D INOUT2IND
S
4B 0
C
EVAL
INOUT1 = 1
C
EVAL
INOUT1IND = 0
C
EVAL
INOUT2 = 1
SQL programming
185
C
EVAL
INOUT2IND = -2
C/EXEC SQL CALL PROC1 (:INOUT1 :INOUT1IND , :INOUT2
C+
:INOUT2IND)
C/END-EXEC
C
EVAL
INOUT1 = 1
C
EVAL
INOUT1IND = 0
C
EVAL
INOUT2 = 1
C
EVAL
INOUT2IND = -2
C/EXEC SQL CALL PROC1 (:INOUT1 :INOUT1IND , :INOUT2
C+
:INOUT2IND)
C/END-EXEC
C
INOUT1IND
IFLT
0
C*
:
C*
HANDLE NULL INDICATOR
C*
:
C
ELSE
C*
:
C*
INOUT1 CONTAINS VALID DATA
C*
:
C
ENDIF
C*
:
C*
HANDLE ALL OTHER PARAMETERS
C*
IN A SIMILAR FASHION
C*
:
C
RETURN
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
End of PROGRAM CRPG
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Program PROC1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
D INOUTP
S
7P 2
D INOUTP2
S
7P 2
D NULLARRAY
S
4B 0 DIM(2)
C
*ENTRY
PLIST
C
PARM
INOUTP
C
PARM
INOUTP2
C
PARM
NULLARRAY
C
NULLARRAY(1) IFLT
0
C*
:
C*
CODE FOR INOUTP DOES NOT CONTAIN MEANINGFUL DATA
C*
:
C
ELSE
C*
:
C*
CODE FOR INOUTP CONTAINS MEANINGFUL DATA
C*
:
C
ENDIF
C*
PROCESS ALL REMAINING VARIABLES
C*
C*
BEFORE RETURNING, SET OUTPUT VALUE FOR FIRST
C*
PARAMETER AND SET THE INDICATOR TO A NON-NEGATIVE
C*
VALUE SO THAT THE DATA IS RETURNED TO THE CALLING
C*
PROGRAM
C*
C
EVAL
INOUTP2 = 20.5
C
EVAL
NULLARRAY(2) = 0
C*
C*
INDICATE THAT THE SECOND PARAMETER IS TO CONTAIN
C*
THE NULL VALUE UPON RETURN. THERE IS NO POINT
C*
IN SETTING THE VALUE IN INOUTP SINCE IT WONT BE
C*
PASSED BACK TO THE CALLER.
C
EVAL
NULLARRAY(1) = -1
C
RETURN
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
End of PROGRAM PROC1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
186
Returning a completion status to the calling program

SQL and external procedures return status information to the calling program in different ways.
For SQL procedures, any errors that are not handled in the procedure are returned to the caller in the
SQLCA. The SIGNAL and RESIGNAL control statements can be used to send error information as well.
For external procedures, there are two ways to return status information. One method of returning a
status to the SQL program issuing the CALL statement is to code an extra INOUT type parameter and set
it before returning from the procedure. When the procedure being called is an existing program, this is
not always possible.
Another method of returning a status to the SQL program issuing the CALL statement is to send an
escape message to the calling program (operating system program QSQCALL) which calls the procedure.
The calling program that issues the procedure is QSQCALL. Each language has methods for signalling
conditions and sending messages. Refer to the respective language reference to determine the proper way
to signal a message. When the message is signalled, QSQCALL turns the error into SQLCODE/
SQLSTATE -443/38501.
Related reference:
|
|
|
Passing parameters from DB2 to external proceduress
|
|
This is the normal parameter passing method for programs. For service programs, ensure that the
parameters are defined correctly in the procedure code.
|
|
|
|
|
When defining and using the parameters in the external procedure, care should be taken to ensure that
no more storage is referenced for a given parameter than is defined for that parameter. The parameters
are all stored in the same space and exceeding a given parameter's storage space can overwrite another
parameter's value. This, in turn, can cause the procedure to see invalid input data or cause the value
returned to the database to be invalid.
|
|
There are several supported parameter styles available to external procedures. For the most part, the
styles differ in how many parameters are passed to the external program or service program.
Parameter style SQL:
The SQL parameter style conforms to the industry standard SQL.
|
|
|
|
With parameter style SQL, the parameters are passed into the external program as follows:
DB2 provides storage for all parameters that are passed to a procedure. Therefore, parameters are passed
to an external procedure by address.
SQL-state
SQL-parameter
|
|
|
|
|
|
|
|
procedure-name specific-name
SQL-parameter-ind
diagnostic-message
dbinfo
SQL-parameter
This argument is set by DB2 before calling the procedure. This value repeats n times, where n is
the number of parameters specified in the procedure definition. The value of each of these
parameters is taken from the expression specified in the CALL statement. It is expressed in the
SQL programming
187
data type of the defined parameter in the CREATE PROCEDURE statement. Note: Changes to
any parameters that are defined as INPUT will be ignored by DB2 upon return.
|
|
| SQL-parameter-ind
|
This argument is set by DB2 before calling the procedure. It can be used by the procedure to
|
determine if the corresponding SQL-parameter is null or not. The nth SQL-parameter-ind
|
corresponds to the nth SQL-parameter, described previously. Each indicator is defined as a
|
two-byte signed integer. It is set to one of the following values:
|
The parameter is present and not null.
-1
The parameter is null.
|
|
Note: Changes to any indicators that correspond to INPUT parameters are ignored by DB2 upon
return.
| SQL-state
|
This argument is a CHAR(5) value that represents the SQLSTATE.
|
|
|
This parameter is passed in from the database set to '00000' and can be set by the procedure as a
result state for the procedure. While normally the SQLSTATE is not set by the procedure, it can
be used to signal an error or warning to the database as follows:
|
|
01Hxx The procedure code detected a warning situation. This results in an SQL warning. Here
xx may be one of several possible strings.
|
|
38xxx
The procedure code detected an error situation. It results in a SQL error. Here xxx may be
one of several possible strings.
| procedure-name
|
This argument is set by DB2 before calling the procedure. It is a VARCHAR(139) value that
|
contains the name of the procedure on whose behalf the procedure code is being called.
|
|
The form of the procedure name that is passed is:
|
|
|
|
This parameter is useful when the procedure code is being used by multiple procedure
definitions so that the code can distinguish which definition is being called. Note: This parameter
is treated as input only; any changes to the parameter value made by the procedure are ignored
by DB2.
<schema-name>.<procedure-name>
| specific-name
|
This argument is set by DB2 before calling the procedure. It is a VARCHAR(128) value that
|
contains the specific name of the procedure on whose behalf the procedure code is being called.
Like procedure-name, this parameter is useful when the procedure code is being used by multiple
procedure definitions so that the code can distinguish which definition is being called. Note: This
parameter is treated as input only; any changes to the parameter value made by the procedure
are ignored by DB2.
|
|
|
|
| diagnostic-message
|
This argument is set by DB2 before calling the procedure. It is a VARCHAR(70) value that can be
|
used by the procedure to send message text back when an SQLSTATE warning or error is
|
signaled by the procedure.
|
|
|
It is initialized by the database on input to the procedure and may be set by the procedure with
descriptive information. Message text is ignored by DB2 unless the SQL-state parameter is set by
the procedure.
| dbinfo
|
|
This argument is set by DB2 before calling the procedure. It is only present if the CREATE
PROCEDURE statement for the procedure specifies the DBINFO keyword. The argument is a
structure whose definition is contained in the sqludf include.
188
Parameter style GENERAL:
|
|
With the GENERAL parameter style, the parameters are passed to an external program just as they are
specified in the CREATE PROCEDURE statement.
The format is:
SQL-parameter
|
|
|
|
|
|
|
SQL-parameter
the number of parameters specified in the procedure call. The value of each of these parameters
is taken from the expression specified in the CALL statement. It is expressed in the data type of
the defined parameter in the CREATE PROCEDURE statement. Note: Changes to any parameters
that are defined as INPUT will be ignored by DB2 upon return.
Parameter style GENERAL WITH NULLS:
|
|
The GENERAL WITH NULLS parameter style passes both parameter values and null indicator values to
an external program.
With this parameter style, the parameters are passed into the program as follows:
SQL-parameter-ind-array
SQL-parameter
|
|
|
|
|
|
|
SQL-parameter
the number of parameters specified in the procedure call. The value of each of these parameters
is taken from the expression specified in the CALL statement. It is expressed in the data type of
the defined parameter in the CREATE PROCEDURE statement. Note: Changes to any parameters
that are defined as INPUT will be ignored by DB2 upon return.
|
|
|
|
|
SQL-parameter-ind-array
This argument is set by DB2 before calling the procedure. It can be used by the procedure to
determine if one or more SQL-parameters are null or not. It is an array of two-byte signed integers
(indicators). The nth array argument corresponds to the nth SQL-parameter. Each array entry is set
to one of the following values:
The parameter is present and not null.
-1
The parameter is null.
|
|
The procedure should check for null input. Note: Changes to any indicator array entries that
correspond to parameters that are defined as INPUT will be ignored by DB2 upon return.
Parameter style DB2GENERAL:
|
|
|
The DB2GENERAL parameter style is used by Java procedures.

Related concepts:
Java SQL routines
SQL programming
189
| Parameter style Java:

| The Java parameter style is the style specified by the SQLJ Part 1: SQL Routines standard.
| Related concepts:
| Java SQL routines
Using user-defined functions

In writing SQL applications, you can implement some actions or operations as a user-defined function
(UDF) or as a subroutine in your application. Although it might appear easier to implement new
operations as subroutines, you might want to consider the advantages of using a UDF instead.
For example, if the new operation is something that other users or programs can take advantage of, a
UDF can help to reuse it. In addition, the function can be called directly in SQL wherever an expression
can be used. The database takes care of many data type promotions of the function arguments
automatically. For example, with DECIMAL to DOUBLE, the database allows your function to be applied
to different, but compatible data types.
In certain cases, calling the UDF directly from the database engine instead of from your application can
have a considerable performance advantage. You will notice this advantage in cases where the function
may be used in the qualification of data for further processing. These cases occur when the function is
used in row selection processing.
Consider a simple scenario where you want to process some data. You can meet some selection criteria
which can be expressed as a function SELECTION_CRITERIA(). Your application can issue the following
select statement:
SELECT A, B, C FROM T
When it receives each row, it runs the program's SELECTION_CRITERIA function against the data to decide
if it is interested in processing the data further. Here, every row of table T must be passed back to the
application. But, if SELECTION_CRITERIA() is implemented as a UDF, your application can issue the
SELECT C FROM T WHERE SELECTION_CRITERIA(A,B)=1
In this case, only the rows and one column of interest are passed across the interface between the
application and the database.
Another case where a UDF can offer a performance benefit is when you deal with large objects (LOBs).
Suppose that you have a function that extracts some information from a value of a LOB. You can perform
this extraction right on the database server and pass only the extracted value back to the application. This
is more efficient than passing the entire LOB value back to the application and then performing the
extraction. The performance value of packaging this function as a UDF can be enormous, depending on
the particular situation.
Related concepts:
User-defined functions on page 12
A user-defined function is a program that can be called like any built-in functions.
UDF concepts
A user-defined function (UDF) is a function that is defined to the DB2 database system through the
CREATE FUNCTION statement and that can be referenced in SQL statements. A UDF can be an external
function or an SQL function.
190
Types of function
There are several types of functions:
v Built-in. These are functions provided by and shipped with the database. SUBSTR() is an example.
v System-generated. These are functions implicitly generated by the database engine when a DISTINCT
TYPE is created. These functions provide casting operations between the DISTINCT TYPE and its base
type.
v User-defined. These are functions created by users and registered to the database.
In addition, each function can be further classified as a scalar function, an aggregate function, or a table
function.
A scalar function returns a single value answer each time it is called. For example, the built-in function
SUBSTR() is a scalar function, as are many built-in functions. System-generated functions are always scalar
functions. Scalar UDFs can either be external (coded in a programming language such as C), written in
SQL, or sourced (using the implementation of an existing function).
An aggregate function receives a set of like values (a column of data) and returns a single value answer
from this set of values. Some built-in functions are aggregate functions. An example of an aggregate
function is the built-in function AVG(). An external UDF cannot be defined as an aggregate function.
However, a sourced UDF is defined to be an aggregate function if it is sourced on one of the built-in
aggregate functions. The latter is useful for distinct types. For example, if a distinct type SHOESIZE exists
that is defined with base type INTEGER, you can define a UDF, AVG(SHOESIZE), as an aggregate function
sourced on the existing built-in aggregate function, AVG(INTEGER).
A table function returns a table to the SQL statement that references it. It must be referenced in the FROM
clause of a SELECT. A table function can be used to apply SQL language processing power to data that is
not DB2 data, or to convert such data into a DB2 table. It can, for example, take a file and convert it to a
table, sample data from the World Wide Web and tabularize it, or access a Lotus Notes database and
return information about mail messages, such as the date, sender, and the text of the message. This
information can be joined with other tables in the database. A table function can be defined as a external
function or an SQL function; it cannot be defined as a sourced function.
Full name of a function

The full name of a function using *SQL naming is <schema-name>.<function-name>.
|
|
|
The full name of a function in *SYS naming is <schema-name>/<function-name> or <schemaname>.<function-name>. Function names cannot be qualified using the slash in *SYS naming in DML
statements.
You can use this full name anywhere you refer to a function. For example:
QGPL.SNOWBLOWER_SIZE
SMITH.FOO
QSYS2.SUBSTR
QSYS2.FLOOR
However, you may also omit the <schema-name>., in which case, DB2 must determine the function to
which you are referring. For example:
SNOWBLOWER_SIZE
FOO
SUBSTR
FLOOR
Path
The concept of path is central to DB2's resolution of unqualified references that occur when schema-name is
not specified. The path is an ordered list of schema names that is used for resolving unqualified
references to UDFs and UDTs. In cases where a function reference matches a function in more than one
schema in the path, the order of the schemas in the path is used to resolve this match. The path is
established by means of the SQLPATH option on the precompile commands for static SQL. The path is
SQL programming
191
set by the SET PATH statement for dynamic SQL. When the first SQL statement that runs in an activation
group runs with SQL naming, the path has the following default value:
"QSYS","QSYS2","<ID>"
This applies to both static and dynamic SQL, where <ID> represents the current statement authorization
ID.
When the first SQL statement in an activation group runs with system naming, the default path is *LIBL.
Overloaded function names

Function names can be overloaded. Overloaded means that multiple functions, even in the same schema,
can have the same name. Two functions cannot, however, have the same signature. A function signature is
the qualified function name and the data types of all the function parameters in the order in that they are
defined.
Function resolution
It is the function resolution algorithm that takes into account the facts of overloading and function path to
choose the best fit for every function reference, whether it is a qualified or an unqualified reference. All
functions, even built-in functions, are processed through the function selection algorithm. The function
resolution algorithm does not take into account the type of a function. So a table function may be
resolved to as the best fit function, even though the usage of the reference requires an scalar function, or
vice versa.
Length of time that the UDF runs

UDFs are called from within an SQL statement execution, which is normally a query operation that
potentially runs against thousands of rows in a table. Because of this, the UDF needs to be called from a
low level of the database.
As a consequence of being called from such a low level, there are certain resources (locks and seizes)
being held at the time the UDF is called and for the duration of the UDF execution. These resources are
primarily locks on any tables and indexes involved in the SQL statement that is calling the UDF. Due to
these held resources, it is important that the UDF not perform operations that may take an extended
period of time (minutes or hours). Because of the critical nature of holding resources for long periods of
time, the database only waits for a certain period of time for the UDF to finish. If the UDF does not finish
in the time allocated, the SQL statement calling the UDF will fail.
The default UDF wait time used by the database should be more than sufficient to allow a normal UDF
to run to completion. However, if you have a long running UDF and want to increase the wait time, this
can be done using the UDF_TIME_OUT option in the query INI file. Note, however, that there is a
maximum time limit that the database will not exceed, regardless of the value specified for
UDF_TIME_OUT.
Since resources are held while the UDF is run, it is important that the UDF not operate on the same
tables or indexes allocated for the original SQL statement or, if it does, that it does not perform an
operation that conflicts with the one being performed in the SQL statement. Specifically, the UDF should
not try to perform any insert, update, or delete row operation on those tables.
Related tasks:
Controlling queries dynamically with the query options file QAQQINI
Writing UDFs as SQL functions

An SQL function is a user-defined function (UDF) that you define, write, and register using the CREATE
FUNCTION statement.
192
An SQL function is written only in the SQL language and its definition is completely contained within
one potentially large CREATE FUNCTION statement. The creation of an SQL function causes the
registration of the UDF, generates the executable code for the function, and defines to the database the
details of how parameters are passed.
Example: SQL scalar UDFs:
This example shows a scalar function that returns a priority based on a date.
CREATE FUNCTION PRIORITY(indate DATE) RETURNS CHAR(7)
LANGUAGE SQL
BEGIN
RETURN(
CASE WHEN indate>CURRENT DATE-3 DAYS THEN HIGH
WHEN indate>CURRENT DATE-7 DAYS THEN MEDIUM
ELSE LOW
END
);
END
The function can then be called as:

SELECT ORDERNBR, PRIORITY(ORDERDUEDATE) FROM ORDERS
Example: SQL table UDFs:

These examples show both a non-pipelined table function and a pipelined table function that return data
using the same underlying query.
|
|
This non-pipelined table function returns data based on a date. The RETURN statement must contain a
query.
CREATE FUNCTION PROJFUNC(indate DATE)
RETURNS TABLE (PROJNO CHAR(6), ACTNO SMALLINT, ACSTAFF DECIMAL(5,2),
ACSTDATE DATE, ACENDATE DATE)
BEGIN
RETURN SELECT * FROM PROJACT
WHERE ACSTDATE<=indate;
END
The function can be invoked as:

SELECT * FROM TABLE(PROJFUNC(:datehv)) X
Non-pipelined SQL table functions are required to have one and only one RETURN statement.
This pipelined table function returns data based on a date. In addition to the column values returned by
the query, it also returns an indication of whether the project has been carried over from a prior year.
CREATE FUNCTION PROJFUNC(indate DATE)
RETURNS TABLE (PROJNO CHAR(6), ACTNO SMALLINT, ACSTAFF DECIMAL(5,2),
ACSTDATE DATE, ACENDATE DATE, CARRYOVER CHAR(1))
BEGIN
FOR C1 CURSOR FOR SELECT * FROM PROJACT
WHERE ACSTDATE<=indate DO
IF YEAR(ACSTDATE) < YEAR(indate) THEN
PIPE (PROJNO, ACTNO, ACSTAFF, ACSTDATE, ACENDATE, Y);
ELSE
PIPE (PROJNO, ACTNO, ACSTAFF, ACSTDATE, ACENDATE, N);
END IF;
END FOR;
RETURN;
END
The function can be invoked the same way as a non-pipelined function:

SQL programming
193
SELECT * FROM TABLE(PROJFUNC(:datehv)) X
Pipelined SQL table functions can contain any number of PIPE statements. Each PIPE statement must
return a value for every result column. A RETURN statement must be executed at the end of processing.
The body of a pipelined function is not limited to querying tables. It could call another program, get
information from an API, query data from some other system, and then combine the results and use one
or more PIPE statements to determine what row values to return as the result table.
Writing UDFs as external functions

You can write the executable code of a user-defined function (UDF) in a language other than SQL.
While this method is slightly more cumbersome than an SQL function, it provides the flexibility for you
to use whatever language is most effective for you. The executable code can be contained in either a
program or service program.
External functions can also be written in Java.
Related concepts:
Java SQL routines
Registering UDFs:
A user-defined function (UDF) must be registered in the database before the function can be recognized
and used by SQL. You can register a UDF using the CREATE FUNCTION statement.
The statement allows you to specify the language and name of the program, along with options such as
DETERMINISTIC, ALLOW PARALLEL, and RETURNS NULL ON NULL INPUT. These options help to
more specifically identify to the database the intention of the function and how calls to the database can
be optimized.
You should register an external UDF after you have written and completely tested the actual code. It is
possible to define the UDF before actually writing it. However, to avoid any problems with running your
UDF, you are encouraged to write and test it extensively before registering it.
Related reference:
CREATE FUNCTION
Example: Exponentiation:
Suppose that you write an external function to perform exponentiation of floating point values, and you
want to register it in the MATH schema.
CREATE FUNCTION MATH.EXPON (DOUBLE, DOUBLE)
RETURNS DOUBLE
EXTERNAL NAME MYLIB/MYPGM(MYENTRY)
LANGUAGE C
PARAMETER STYLE DB2SQL
NO SQL
DETERMINISTIC
NO EXTERNAL ACTION
RETURNS NULL ON NULL INPUT
ALLOW PARALLEL
In this example, the RETURNS NULL ON NULL INPUT is specified since you want the result to be
NULL if either argument is NULL. As there is no reason why EXPON cannot be parallel, the ALLOW
PARALLEL value is specified.
194
Example: String search:

Suppose that you write a user-defined function (UDF) to look for a given string, passed as an argument,
within a given character large object (CLOB) value that is also passed as an argument. The UDF returns
the position of the string within the CLOB if it finds the string, or zero if it does not.
The C program was written to return a FLOAT result. Suppose you know that when it is used in SQL, it
should always return an INTEGER. You can create the following function:
CREATE FUNCTION FINDSTRING (CLOB(500K), VARCHAR(200))
RETURNS INTEGER
CAST FROM FLOAT
SPECIFIC FINDSTRING
EXTERNAL NAME MYLIB/MYPGM(FINDSTR)
LANGUAGE C
NO SQL
DETERMINISTIC
NO EXTERNAL ACTION
Note that a CAST FROM clause is used to specify that the UDF program really returns a FLOAT value,
but you want to cast this to INTEGER before returning the value to the SQL statement which used the
UDF. Also, you want to provide your own specific name for the function. Because the UDF was not
written to handle NULL values, you use the RETURNS NULL ON NULL INPUT.
Example: BLOB string search:
Suppose that you want the FINDSTRING function to work on binary large objects (BLOBs) as well as on
character large objects (CLOBs). To do this, you define another FINDSTRING function that takes BLOB as
the first parameter.
CREATE FUNCTION FINDSTRING (BLOB(500K), VARCHAR(200))
RETURNS INTEGER
CAST FROM FLOAT
SPECIFIC FINDSTRING_BLOB
EXTERNAL NAME MYLIB/MYPGM(FINDSTR)
LANGUAGE C
NO SQL
DETERMINISTIC
NO EXTERNAL ACTION
This example illustrates overloading of the UDF name and shows that multiple UDFs can share the same
program. Note that although a BLOB cannot be assigned to a CLOB, the same source code can be used.
There is no programming problem in the above example as the interface for BLOB and CLOB between
DB2 and the UDF program is the same: length followed by data.
Example: String search over a user-defined type (UDT):
Suppose that you are satisfied with the FINDSTRING function from the binary large object (BLOB) string
search, but now you want to define a distinct type BOAT with source type BLOB.
You also want FINDSTRING to operate on values having data type BOAT, so you create another
FINDSTRING function. This function is sourced on the FINDSTRING which operates on BLOB values.
Note the further overloading of FINDSTRING in this example:
CREATE FUNCTION FINDSTRING (BOAT, VARCHAR(200))
RETURNS INT
SPECIFIC "slick_fboat"
SOURCE SPECIFIC FINDSTRING_BLOB
SQL programming
195
Note that this FINDSTRING function has a different signature from the FINDSTRING functions in
Example: BLOB string search on page 195, so there is no problem overloading the name. Because you
are using the SOURCE clause, you cannot use the EXTERNAL NAME clause or any of the related
keywords specifying function attributes. These attributes are taken from the source function. Finally,
observe that in identifying the source function you are using the specific function name explicitly
provided in Example: BLOB string search on page 195. Because this is an unqualified reference, the
schema in which this source function resides must be in the function path, or the reference will not be
resolved.
Example: AVG over a user-defined type (UDT):
This example implements the AVG aggregate function over the CANADIAN_DOLLAR distinct type.
Strong typing prevents you from using the built-in AVG function on a distinct type. It turns out that the
source type for CANADIAN_DOLLAR was DECIMAL, and so you implement the AVG by sourcing it on
the AVG(DECIMAL) built-in function.
CREATE FUNCTION AVG (CANADIAN_DOLLAR)
RETURNS CANADIAN_DOLLAR
SOURCE "QSYS2".AVG(DECIMAL(9,2))
Note that in the SOURCE clause you have qualified the function name, just in case there might be some
other AVG function lurking in your SQL path.
Example: Counting:
Your simple counting function returns a 1 the first time and increments the result by one each time it is
called. This function takes no SQL arguments. By definition, it is a NOT DETERMINISTIC function
because its answer varies from call to call.
It uses the SCRATCHPAD to save the last value returned. Each time it is called, the function increments
this value and returns it.
CREATE FUNCTION COUNTER ()
RETURNS INT
EXTERNAL NAME MYLIB/MYFUNCS(CTR)
LANGUAGE C
NO SQL
NOT DETERMINISTIC
NOT FENCED
SCRATCHPAD 4
DISALLOW PARALLEL
Note that no parameter definitions are provided, just empty parentheses. The above function specifies
SCRATCHPAD and uses the default specification of NO FINAL CALL. In this case, the size of the
scratchpad is set to only 4 bytes, which is sufficient for a counter. Since the COUNTER function requires
that a single scratchpad be used to operate properly, DISALLOW PARALLEL is added to prevent DB2
from operating it in parallel.
Example: Table function returning document IDs:
Suppose that you write a table function that returns a row consisting of a single document identifier
column for each known document that matches a given subject area (the first parameter) and contains the
given string (second parameter).
This user-defined function (UDF) quickly identifies the documents:
CREATE FUNCTION DOCMATCH (VARCHAR(30), VARCHAR(255))
RETURNS TABLE (DOC_ID CHAR(16))
EXTERNAL NAME DOCFUNCS/UDFMATCH(udfmatch)
196
LANGUAGE C
NO SQL
DETERMINISTIC
NO EXTERNAL ACTION
NOT FENCED
SCRATCHPAD
NO FINAL CALL
DISALLOW PARALLEL
CARDINALITY 20
Within the context of a single session it will always return the same table, and therefore it is defined as
DETERMINISTIC. The RETURNS clause defines the output from DOCMATCH, including the column
name DOC_ID. FINAL CALL does not need to be specified for this table function. The DISALLOW
PARALLEL keyword is required since table functions cannot operate in parallel. Although the size of the
output from DOCMATCH can be a large table, CARDINALITY 20 is a representative value, and is
specified to help the optimizer make good decisions.
Typically, this table function is used in a join with the table containing the document text, as follows:
SELECT T.AUTHOR, T.DOCTEXT
FROM DOCS AS T, TABLE(DOCMATCH(MATHEMATICS, ZORNS LEMMA)) AS F
WHERE T.DOCID = F.DOC_ID
Note the special syntax (TABLE keyword) for specifying a table function in a FROM clause. In this
invocation, the DOCMATCH() table function returns a row containing the single column DOC_ID for
each MATHEMATICS document referencing ZORN'S LEMMA. These DOC_ID values are joined to the
master document table, retrieving the author's name and document text.
Passing arguments from DB2 to external functions:
DB2 provides storage for all parameters that are passed to a user-defined function (UDF). Therefore,
parameters are passed to an external function by address.
This is the normal parameter passing method for programs. For service programs, ensure that the
parameters are defined correctly in the function code.
When defining and using the parameters in the UDF, care should be taken to ensure that no more storage
is referenced for a given parameter than is defined for that parameter. The parameters are all stored in
the same space and exceeding a given parameter's storage space can overwrite another parameter's value.
This, in turn, can cause the function to see invalid input data or cause the value returned to the database
to be invalid.
There are several supported parameter styles available to external UDFs. For the most part, the styles
differ in how many parameters are passed to the external program or service program.
Parameter style SQL:
The SQL parameter style conforms to the industry standard SQL. This parameter style can be used only
with scalar user-defined functions (UDFs).
With parameter style SQL, the parameters are passed into the external program as follows (in the order
specified):
SQL programming
197
SQL-result
SQL-argument
function-name
SQL-result-ind
SQL-state
SQL-argument-ind
specific-name diagnostic-message
SQL-argument
This argument is set by DB2 before calling the UDF. This value repeats n times, where n is the
number of arguments specified in the function reference. The value of each of these arguments is
taken from the expression specified in the function invocation. It is expressed in the data type of
the defined parameter in the create function statement. Note: These parameters are treated as
input only; any changes to the parameter values made by the UDF are ignored by DB2.
SQL-result
This argument is set by the UDF before returning to DB2. The database provides the storage for
the return value. Since the parameter is passed by address, the address is of the storage where
the return value should be placed. The database provides as much storage as needed for the
return value as defined on the CREATE FUNCTION statement. If the CAST FROM clause is used
in the CREATE FUNCTION statement, DB2 assumes the UDF returns the value as defined in the
CAST FROM clause, otherwise DB2 assumes the UDF returns the value as defined in the
RETURNS clause.
SQL-argument-ind
This argument is set by DB2 before calling the UDF. It can be used by the UDF to determine if
the corresponding SQL-argument is null or not. The nth SQL-argument-ind corresponds to the nth
SQL-argument, described previously. Each indicator is defined as a two-byte signed integer. It is
set to one of the following values:
0
The argument is present and not null.
-1
The argument is null.
If the function is defined with RETURNS NULL ON NULL INPUT, the UDF does not need to
check for a null value. However, if it is defined with CALLS ON NULL INPUT, any argument
can be NULL and the UDF should check for null input. Note: these parameters are treated as
input only; any changes to the parameter values made by the UDF are ignored by DB2.
SQL-result-ind
the return value. The argument is defined as a two-byte signed integer. If set to a negative value,
the database interprets the result of the function as null. If set to zero or a positive value, the
database uses the value returned in SQL-result. The database provides the storage for the return
value indicator. Since the parameter is passed by address, the address is of the storage where the
indicator value should be placed.
SQL-state
This argument is a CHAR(5) value that represents the SQLSTATE.
This parameter is passed in from the database set to '00000' and can be set by the function as a
result state for the function. While normally the SQLSTATE is not set by the function, it can be
used to signal an error or warning to the database as follows:
01Hxx The function code detected a warning situation. This results in an SQL warning, Here xx
may be one of several possible strings.
38xxx
198
The function code detected an error situation. It results in a SQL error. Here xxx may be
one of several possible strings.
function-name
This argument is set by DB2 before calling the UDF. It is a VARCHAR(139) value that contains
the name of the function on whose behalf the function code is being called.
The form of the function name that is passed is:
<schema-name>.<function-name>
This parameter is useful when the function code is being used by multiple UDF definitions so
that the code can distinguish which definition is being called. Note: This parameter is treated as
input only; any changes to the parameter value made by the UDF are ignored by DB2.
specific-name
This argument is set by DB2 before calling the UDF. It is a VARCHAR(128) value that contains
the specific name of the function on whose behalf the function code is being called.
Like function-name, this parameter is useful when the function code is being used by multiple
UDF definitions so that the code can distinguish which definition is being called. Note: This
parameter is treated as input only; any changes to the parameter value made by the UDF are
ignored by DB2.
diagnostic-message
This argument is set by DB2 before calling the UDF. It is a VARCHAR(70) value that can be used
by the UDF to send message text back when an SQLSTATE warning or error is signaled by the
UDF.
It is initialized by the database on input to the UDF and may be set by the UDF with descriptive
information. Message text is ignored by DB2 unless the SQL-state parameter is set by the UDF.
Related reference:
SQL messages and codes
Parameter style DB2SQL:
With the DB2SQL parameter style, the same parameters and the same order of parameters are passed to
an external program or a service program as with the SQL parameter style. However, DB2SQL allows
additional optional parameters to be passed as well.
If more than one of the optional parameters below is specified in the UDF definition, they are passed to
the UDF in the order defined below. Refer to parameter style SQL for the common parameters. This
parameter style can be used for both scalar and table UDFs.
For scalar functions:
SQL-result
SQL-argument
SQL-result-ind
SQL-state
SQL-argument-ind
function-name specific-name
diagnostic-message
scratchpad
call-type
dbinfo
For table functions:
SQL-result
SQL-argument
SQL-result-ind
SQL-state
SQL-argument-ind
SQL programming
199
function-name
specific-name diagnostic-message
call-type
scratchpad
dbinfo
scratchpad
This argument is set by DB2 before calling the UDF. It is only present if the CREATE FUNCTION
statement for the UDF specified the SCRATCHPAD keyword. This argument is a structure with
the following elements:
v An INTEGER containing the length of the scratchpad.
v The actual scratchpad, initialized to all binary 0's by DB2 before the first call to the UDF.
The scratchpad can be used by the UDF either as working storage or as persistent storage, since it
is maintained across UDF invocations.
For table functions, the scratchpad is initialized as above before the FIRST call to the UDF if
FINAL CALL is specified on the CREATE FUNCTION. After this call, the scratchpad content is
totally under control of the table function. DB2 does not examine or change the content of the
scratchpad thereafter. The scratchpad is passed to the function on each invocation. The function
can be re-entrant, and DB2 preserves its state information in the scratchpad.
If NO FINAL CALL was specified or defaulted for a table function, then the scratchpad is
initialized as above for each OPEN call, and the scratchpad content is completely under control of
the table function between OPEN calls. This can be very important for a table function used in a
join or subquery. If it is necessary to maintain the content of the scratchpad across OPEN calls,
then FINAL CALL must be specified in your CREATE FUNCTION statement. With FINAL CALL
specified, in addition to the normal OPEN, FETCH, and CLOSE calls, the table function will also
receive FIRST and FINAL calls, for the purpose of scratchpad maintenance and resource release.
call-type
This argument is set by DB2 before calling the UDF. For scalar functions, it is only present if the
CREATE FUNCTION statement for the UDF specified the FINAL CALL keyword. However, for
table functions it is always present. It follows the scratchpad argument; or the diagnostic-message
argument if the scratchpad argument is not present. This argument takes the form of an
INTEGER value.
For scalar functions:
-1
This is the first call to the UDF for this statement. A first call is a normal call in that all
SQL argument values are passed.
This is a normal call. (All the normal input argument values are passed).
This is a final call. No SQL-argument or SQL-argument-ind values are passed. A UDF

should not return any answer using the SQL-result, SQL-result-ind arguments, SQL-state,
or diagnostic-message arguments. These arguments are ignored by the system when
returned from the UDF.
For table functions:
200
-2
This is the first call to the UDF for this statement. A first call is a normal call in that all
SQL argument values are passed.
-1
This is the open call to the UDF for this statement. The scratchpad is initialized if NO
FINAL CALL is specified, but not necessarily otherwise. All SQL argument values are
passed.
This is a fetch call. DB2 expects the table function to return either a row comprising the
set of return values, or an end-of-table condition indicated by SQLSTATE value '02000'.
This is a close call. This call balances the OPEN call, and can be used to perform any
external CLOSE processing and resource release.
dbinfo
This is a final call. No SQL-argument or SQL-argument-ind values are passed. A UDF

should not return any answer using the SQL-result, SQL-result-ind arguments, SQL-state,
or diagnostic-message arguments. These arguments are ignored by the system when
returned from the UDF.
This argument is set by DB2 before calling the UDF. It is only present if the CREATE FUNCTION
statement for the UDF specifies the DBINFO keyword. The argument is a structure whose
definition is contained in the sqludf include.
Parameter style GENERAL:

With the GENERAL parameter style, the parameters are passed to an external service program just as
they are specified in the CREATE FUNCTION statement. This parameter style can be used only with
scalar user-defined functions (UDFs).
The format is:
SQL-result = func
SQL-argument
SQL-argument
the defined parameter in the CREATE FUNCTION statement. Note: These parameters are treated
as input only; any changes to the parameter values made by the UDF are ignored by DB2.
SQL-result
This value is returned by the UDF. DB2 copies the value into database storage. In order to return
the value correctly, the function code must be a value-returning function. The database copies
only as much of the value as defined for the return value as specified on the CREATE
FUNCTION statement. If the CAST FROM clause is used in the CREATE FUNCTION statement,
DB2 assumes the UDF returns the value as defined in the CAST FROM clause, otherwise DB2
assumes the UDF returns the value as defined in the RETURNS clause.
Because of the requirement that the function code be a value-returning function, any function
code used for parameter style GENERAL must be created into a service program.
Parameter style GENERAL WITH NULLS:
The GENERAL WITH NULLS parameter style can be used only with scalar user-defined functions
(UDFs).
With this parameter style, the parameters are passed into the service program as follows (in the order
specified):
SQL-result = funcname
SQL-result-ind )
SQL-argument
SQL-argument-ind-array
SQL-argument
SQL programming
201
the defined parameter in the CREATE FUNCTION statement. Note: These parameters are treated
as input only; any changes to the parameter values made by the UDF are ignored by DB2.
SQL-argument-ind-array
This argument is set by DB2 before calling the UDF. It can be used by the UDF to determine if
one or more SQL-arguments are null or not. It is an array of two-byte signed integers (indicators).
The nth array argument corresponds corresponds to the nth SQL-argument. Each array entry is set
to one of the following values:
0
The argument is present and not null.
-1
The argument is null.
The UDF should check for null input. Note: This parameter is treated as input only; any changes
to the parameter value made by the UDF is ignored by DB2.
SQL-result-ind
the return value. The argument is defined as a two-byte signed integer. If set to a negative value,
the database interprets the result of the function as null. If set to zero or a positive value, the
database uses the value returned in SQL-result. The database provides the storage for the return
value indicator. Since the parameter is passed by address, the address is of the storage where the
indicator value should be placed.
SQL-result
This value is returned by the UDF. DB2 copies the value into database storage. In order to return
the value correctly, the function code must be a value-returning function. The database copies
only as much of the value as defined for the return value as specified on the CREATE
FUNCTION statement. If the CAST FROM clause is used in the CREATE FUNCTION statement,
DB2 assumes the UDF returns the value as defined in the CAST FROM clause, otherwise DB2
assumes the UDF returns the value as defined in the RETURNS clause.
Because of the requirement that the function code be a value-returning function, any function
code used for parameter style GENERAL WITH NULLS must be created into a service program.
Notes:
1. The external name specified on the CREATE FUNCTION statement can be specified
either with or without single quotation marks. If the name is not quoted, it is
uppercased before it is stored; if it is quoted, it is stored as specified. This becomes
important when naming the actual program, as the database searches for the program
that has a name that exactly matches the name stored with the function definition. For
example, if a function was created as:
CREATE FUNCTION X(INT) RETURNS INT
LANGUAGE C
EXTERNAL NAME MYLIB/MYPGM(MYENTRY)
and the source for the program was:

void myentry(
int*in
int*out,
.
.
. .
the database will not find the entry because it is in lowercase myentry and the
database was instructed to look for uppercase MYENTRY.
2. For service programs with C++ modules, make sure in the C++ source code to precede
the program function definition with extern "C". Otherwise, the C++ compiler will
perform 'name mangling' of the function's name and the database will not find it.
202
Parameter style DB2GENERAL:

The DB2GENERAL parameter style is used by Java user-defined functions (UDFs).
Related concepts:
Java SQL routines
Parameter style Java:
The Java parameter style is the style specified by the SQLJ Part 1: SQL Routines standard.
Related concepts:
Java SQL routines
Table function considerations:
An external table function is a user-defined function (UDF) that delivers a table to the SQL statement in
which it is referenced. A table function reference is valid only in a FROM clause of a SELECT statement.
When using table functions, observe the following:
v Even though a table function delivers a table, the physical interface between DB2 and the UDF is
one-row-at-a-time. There are five types of calls made to a table function: OPEN, FETCH, CLOSE,
FIRST, and FINAL. The existence of FIRST and FINAL calls depends on how you define the UDF. The
same call-type mechanism that can be used for scalar functions is used to distinguish these calls.
v The standard interface used between DB2 and user-defined scalar functions is extended to
accommodate table functions. The SQL-result argument repeats for table functions; each instance
corresponding to a column to be returned as defined in the RETURNS TABLE clause of the CREATE
FUNCTION statement. The SQL-result-ind argument likewise repeats, each instance related to the
corresponding SQL-result instance.
v Not every result column defined in the RETURNS clause of the CREATE FUNCTION statement for the
table function has to be returned. The DBINFO keyword of CREATE FUNCTION, and corresponding
dbinfo argument enable the optimization that only those columns needed for a particular table function
reference need be returned.
v The individual column values returned conform in format to the values returned by scalar functions.
v The CREATE FUNCTION statement for a table function has a CARDINALITY n specification. This
specification enables the definer to inform the DB2 optimizer of the approximate size of the result so
that the optimizer can make better decisions when the function is referenced. Regardless of what has
been specified as the CARDINALITY of a table function, exercise caution against writing a function
with infinite cardinality; that is, a function that always returns a row on a FETCH call. DB2 expects the
end-of-table condition, as a catalyst within its query processing. So a table function that never returns
the end-of-table condition (SQL-state value '02000') can cause an infinite processing loop.
Error processing for UDFs:
When an error occurs in processing a user-defined function (UDF), the system follows a specified model
to handle the error.
Table function error processing
The error processing model for table function calls is as follows:
1. If FIRST call fails, no further calls are made.
2. If FIRST call succeeds, the nested OPEN, FETCH, and CLOSE calls are made, and the FINAL call is
always made.
3. If OPEN call fails, no FETCH or CLOSE call is made.
4. If OPEN call succeeds, then FETCH and CLOSE calls are made.
SQL programming
203
5. If a FETCH call fails, no further FETCH calls are made, but the CLOSE call is made.
Note: This model describes the ordinary error processing for table UDFs. In the event of a system failure
or communication problem, a call indicated by the error processing model may not be made.
Scalar function error processing
The error processing model for scalar UDFs, which are defined with the FINAL CALL specification, is as
follows:
1. If FIRST call fails, no further calls are made.
2. If FIRST call succeeds, then further NORMAL calls are made as warranted by the processing of the
statement, and a FINAL call is always made.
3. If NORMAL call fails, no further NORMAL calls are made, but the FINAL call is made (if you have
specified FINAL CALL). This means that if an error is returned on a FIRST call, the UDF must clean
up before returning, because no FINAL call will be made.
Note: This model describes the ordinary error processing for scalar UDFs. In the event of a system failure
or communication problem, a call indicated by the error processing model may not be made.
Threads considerations:
A user-defined function (UDF) that is defined as FENCED runs in the same job as the SQL statement that
calls the function. However, the UDF runs in a system thread, separate from the thread that is running
the SQL statement.
Because the UDF runs in the same job as the SQL statement, it shares much of the same environment as
the SQL statement. However, because it runs under a separate thread, the following threads
considerations apply:
v The UDF will conflict with thread level resources held by the SQL statement's thread. Primarily, these
are the table resources discussed above.
v UDFs do not inherit any program adopted authority that may have been active at the time the SQL
statement was called. UDF authority comes from either the authority associated with the UDF program
itself or the authority of the user running the SQL statement.
v The UDF cannot perform any operation that is blocked from being run in a secondary thread.
Related reference:
Multithreaded applications
Fenced or unfenced considerations
When you create a user-defined function (UDF), consider whether to make the UDF an unfenced UDF.
Parallel processing:
A user-defined function (UDF) can be defined to allow parallel processing.
This means that the same UDF program can be running in multiple threads at the same time. Therefore,
if ALLOW PARALLEL is specified for the UDF, ensure that it is thread safe.
Related reference:
Multithreaded applications
Fenced or unfenced considerations:
When you create a user-defined function (UDF), consider whether to make the UDF an unfenced UDF.
204
By default, UDFs are created as fenced UDFs. Fenced indicates that the database should run the UDF in a
separate thread. For complex UDFs, this separation is meaningful as it will avoid potential problems such
as generating unique SQL cursor names. Not having to be concerned about resource conflicts is one
reason to stick with the default and create the UDF as a fenced UDF. A UDF created with the NOT
FENCED option indicates to the database that the user is requesting that the UDF can run within the
same thread that initiated the UDF. Unfenced is a suggestion to the database, which can still decide to
run the UDF in the same manner as a fenced UDF.
CREATE FUNCTION QGPL.FENCED (parameter1 INTEGER)
RETURNS INTEGER LANGUAGE SQL
BEGIN
RETURN parameter1 * 3;
END;
CREATE FUNCTION QGPL.UNFENCED1 (parameter1 INTEGER)
RETURNS INTEGER LANGUAGE SQL NOT FENCED
-- Build the UDF to request faster execution via the NOT FENCED option
BEGIN
RETURN parameter1 * 3;
END;
Related reference:
Threads considerations on page 204
A user-defined function (UDF) that is defined as FENCED runs in the same job as the SQL statement that
calls the function. However, the UDF runs in a system thread, separate from the thread that is running
the SQL statement.
Save and restore considerations:
When an external function associated with an ILE external program or service program is created, an
attempt is made to save the attributes of the function in the associated program or service program
object.
If the *PGM or *SRVPGM object is saved and then restored to this or another system, the catalogs are
automatically updated with those attributes. If the function's attribute cannot be saved, then the catalogs
will not be automatically updated and the user must create the external function on the new system. The
attributes can be saved for external functions subject to the following restrictions:
v The external program library must not be QSYS or QSYS2.
v The external program must exist when the CREATE FUNCTION statement is issued.
v The external program must be an ILE *PGM or *SRVPGM object.
v The external program or service program must contain at least one SQL statement.
If the program object cannot be updated, the function will still be created.
Examples: UDF code

These examples show how to implement user-defined function (UDF) code by using SQL functions and
external functions.
Example: Square of a number UDF:
Suppose that you want a function that returns the square of a number.
The query statement is:
SELECT SQUARE(myint) FROM mytable
SQL programming
205
The following examples show how to define the UDF in several different ways.
Using an SQL function
The CREATE FUNCTION statement:
CREATE FUNCTION SQUARE( inval INT) RETURNS INT
LANGUAGE SQL
SET OPTION DBGVIEW=*SOURCE
BEGIN
RETURN(inval*inval);
END
This creates an SQL function that you can debug.

Using an external function, parameter style SQL
CREATE FUNCTION SQUARE(INT) RETURNS INT CAST FROM FLOAT
LANGUAGE C
EXTERNAL NAME MYLIB/MATH(SQUARE)
DETERMINISTIC
NO SQL
NO EXTERNAL ACTION
PARAMETER STYLE SQL
ALLOW PARALLEL
The code:
void SQUARE(int *inval,
double *outval,
short *inind,
short *outind,
char *sqlstate,
char *funcname,
char *specname,
char *msgtext)
{
if (*inind<0)
*outind=-1;
else
{
*outval=*inval;
*outval=(*outval)*(*outval);
*outind=0;
}
return;
}
To create the external service program so it can be debugged:

CRTCMOD MODULE(mylib/square) DBGVIEW(*SOURCE)
CRTSRVPGM SRVPGM(mylib/math) MODULE(mylib/square)
EXPORT(*ALL) ACTGRP(*CALLER)
Using an external function, parameter style GENERAL

CREATE FUNCTION SQUARE(INT) RETURNS INT CAST FROM FLOAT
LANGUAGE C
EXTERNAL NAME MYLIB/MATH(SQUARE)
DETERMINISTIC
206
NO SQL
NO EXTERNAL ACTION
PARAMETER STYLE GENERAL
ALLOW PARALLEL
The code:
double SQUARE(int *inval)
{
double outval;
outval=*inval;
outval=outval*outval;
return(outval);
}
To create the external service program so it can be debugged:

CRTCMOD MODULE(mylib/square) DBGVIEW(*SOURCE)
CRTSRVPGM SRVPGM(mylib/math) MODULE(mylib/square)
EXPORT(*ALL) ACTGRP(*CALLER)
Example: Counter:
Suppose that you want to number the rows in a SELECT statement. So you write a user-defined function
(UDF) that increments and returns a counter.
This example uses an external function with DB2 SQL parameter style and a scratchpad.
CREATE FUNCTION COUNTER()
RETURNS INT
SCRATCHPAD
NOT DETERMINISTIC
NO SQL
NO EXTERNAL ACTION
LANGUAGE C
EXTERNAL NAME MYLIB/MATH(ctr)
DISALLOW PARALLEL
/* structure scr defines the passed scratchpad for the function "ctr" */
struct scr {
long len;
long countr;
char not_used[92];
};
void ctr (
long *out,
short *outnull,
char *sqlstate,
char *funcname,
char *specname,
char *mesgtext,
struct scr *scratchptr) {
*out = ++scratchptr->countr;
*outnull = 0;
return;
/*
/*
/*
/*
/*
/*
/*
output answer (counter) */

output NULL indicator */
SQL STATE */
function name */
specific function name */
message text insert */
scratch pad */
/* increment counter & copy out */
}
/* end of UDF : ctr */
For this UDF, observe that:

SQL programming
207
v It has no input SQL arguments defined, but returns a value.

v It appends the scratchpad input argument after the four standard trailing arguments, namely SQL-state,
function-name, specific-name, and message-text.
v It includes a structure definition to map the scratchpad which is passed.
v No input parameters are defined. This agrees with the code.
v SCRATCHPAD is coded, causing DB2 to allocate, properly initialize and pass the scratchpad argument.
v You have specified it to be NOT DETERMINISTIC, because it depends on more than the SQL input
arguments, (none in this case).
v You have correctly specified DISALLOW PARALLEL, because correct functioning of the UDF depends
on a single scratchpad.
Example: Weather table function:
Suppose that you write a table function that returns weather information for various cities in the United
States.
The weather date for these cities is read in from an external file, as indicated in the comments contained
in the example program. The data includes the name of a city followed by its weather information. This
pattern is repeated for the other cities.
#include
#include
#include
#include
<stdlib.h>
<string.h>
<stdio.h>
<sqludf.h> /* for use in compiling User Defined Function */
#define
#define
#define
#define
#define
SQL_NOTNULL 0 /* Nulls Allowed - Value is not Null */

SQL_ISNULL -1 /* Nulls Allowed - Value is Null */
SQL_TYP_VARCHAR 448
SQL_TYP_INTEGER 496
SQL_TYP_FLOAT 480
/* Short and long city name structure */

typedef struct {
char * city_short ;
char * city_long ;
} city_area ;
/* Scratchpad data */ (See note 1)
/* Preserve information from one function call to the next call */
typedef struct {
/* FILE * file_ptr; if you use weather data text file */
int file_pos ; /* if you use a weather data buffer */
} scratch_area ;
/* Field descriptor structure */
typedef struct {
char fld_field[31] ;
/* Field
int fld_ind ;
/* Field null indicator
int fld_type ;
/* Field
int fld_length ; /* Field length in the weather
int fld_offset ; /* Field offset in the weather
} fld_desc ;
/* Short and long city name data */
city_area cities[] = {
{ "alb", "Albany, NY"
{ "atl", "Atlanta, GA"
.
208
},
},
data
data
type
data
data
*/
*/
*/
*/
*/
.
.
{ "wbc", "Washington DC, DC"
},
/* You may want to add more cities here */
/* Do not forget a null termination */
{ ( char * ) 0, ( char * ) 0
}
} ;
/* Field descriptor data */
fld_desc fields[] = {
{ "", SQL_ISNULL, SQL_TYP_VARCHAR, 30, 0 }, /* city
*/
{ "", SQL_ISNULL, SQL_TYP_INTEGER, 3, 2 }, /* temp_in_f
*/
{ "", SQL_ISNULL, SQL_TYP_INTEGER, 3, 7 }, /* humidity
*/
{ "", SQL_ISNULL, SQL_TYP_VARCHAR, 5, 13 }, /* wind
*/
{ "", SQL_ISNULL, SQL_TYP_INTEGER, 3, 19 }, /* wind_velocity */
{ "", SQL_ISNULL, SQL_TYP_FLOAT,
5, 24 }, /* barometer
*/
{ "", SQL_ISNULL, SQL_TYP_VARCHAR, 25, 30 }, /* forecast
*/
/* You may want to add more fields here */
{ ( char ) 0, 0, 0, 0, 0 }
} ;
/* Following is the weather data buffer for this example. You
/* may want to keep the weather data in a separate text file.
/* Uncomment the following fopen() statement. Note that you
/* need to specify the full path name for this file.
char * weather_data[] = {
"alb.forecast",
"
34
28%
wnw
3 30.53 clear",
"atl.forecast",
"
46
89%
east 11 30.03 fog",
.
.
.
"wbc.forecast",
"
38
96%
ene 16 30.31 light rain",
/* You may want to add more weather data here */
*/
*/
*/
*/

( char * ) 0
} ;
#ifdef __cplusplus
extern "C"
#endif
/* This is a subroutine. */
/* Find a full city name using a short name */
int get_name( char * short_name, char * long_name ) {
int name_pos = 0 ;
while ( cities[name_pos].city_short != ( char * ) 0 ) {
if (strcmp(short_name, cities[name_pos].city_short) == 0) {
strcpy( long_name, cities[name_pos].city_long ) ;
/* A full city name found */
return( 0 ) ;
}
name_pos++ ;
}
/* can not find such city in the city data */
strcpy( long_name, "Unknown City" ) ;
return( -1 ) ;
}
SQL programming
209
#ifdef __cplusplus
extern "C"
#endif
/* Clean all field data and field null indicator data */
int clean_fields( int field_pos ) {
while (fields[field_pos].fld_length !=0 ) {
memset( fields[field_pos].fld_field, \0, 31 ) ;
fields[field_pos].fld_ind = SQL_ISNULL ;
field_pos++ ;
}
return( 0 ) ;
}
#ifdef __cplusplus
extern "C"
#endif
/* Fills all field data and field null indicator data ... */
/* ... from text weather data */
int get_value( char * value, int field_pos ) {
fld_desc * field ;
char field_buf[31] ;
double * double_ptr ;
int * int_ptr, buf_pos ;
while ( fields[field_pos].fld_length != 0 ) {
field = &fields[field_pos] ;
memset( field_buf, \0, 31 ) ;
memcpy( field_buf,
( value + field->fld_offset ),
field->fld_length ) ;
buf_pos = field->fld_length ;
while ( ( buf_pos > 0 ) &&
( field_buf[buf_pos] == ) )
field_buf[buf_pos--] = \0 ;
buf_pos = 0 ;
while ( ( buf_pos < field->fld_length ) &&
( field_buf[buf_pos] == ) )
buf_pos++ ;
if ( strlen( ( char * ) ( field_buf + buf_pos ) ) > 0 ||
strcmp( ( char * ) ( field_buf + buf_pos ), "n/a") != 0 ) {
field->fld_ind = SQL_NOTNULL ;
/* Text to SQL type conversion */
switch( field->fld_type ) {
case SQL_TYP_VARCHAR:
strcpy( field->fld_field,
( char * ) ( field_buf + buf_pos ) ) ;
break ;
case SQL_TYP_INTEGER:
int_ptr = ( int * ) field->fld_field ;
*int_ptr = atoi( ( char * ) ( field_buf + buf_pos ) ) ;
break ;
case SQL_TYP_FLOAT:
double_ptr = ( double * ) field->fld_field ;
*double_ptr = atof( ( char * ) ( field_buf + buf_pos ) ) ;
break ;
/* You may want to add more text to SQL type conversion here */
}
}
field_pos++ ;
}
210
return( 0 ) ;
}
#ifdef __cplusplus
extern "C"
#endif
void SQL_API_FN weather( /* Return row fields */
SQLUDF_VARCHAR * city,
SQLUDF_INTEGER * temp_in_f,
SQLUDF_INTEGER * humidity,
SQLUDF_VARCHAR * wind,
SQLUDF_INTEGER * wind_velocity,
SQLUDF_DOUBLE * barometer,
SQLUDF_VARCHAR * forecast,
/* You may want to add more fields here */
/* Return row field null indicators */
SQLUDF_NULLIND * city_ind,
SQLUDF_NULLIND * temp_in_f_ind,
SQLUDF_NULLIND * humidity_ind,
SQLUDF_NULLIND * wind_ind,
SQLUDF_NULLIND * wind_velocity_ind,
SQLUDF_NULLIND * barometer_ind,
SQLUDF_NULLIND * forecast_ind,
/* You may want to add more field indicators here */
/* UDF always-present (trailing) input arguments */
SQLUDF_TRAIL_ARGS_ALL
) {
scratch_area * save_area ;
char line_buf[81] ;
int line_buf_pos ;
/* SQLUDF_SCRAT is part of SQLUDF_TRAIL_ARGS_ALL */
/* Preserve information from one function call to the next call */
save_area = ( scratch_area * ) ( SQLUDF_SCRAT->data ) ;
/* SQLUDF_CALLT is part of SQLUDF_TRAIL_ARGS_ALL */
switch( SQLUDF_CALLT ) {
/* First call UDF: Open table and fetch first row */
case SQL_TF_OPEN:
/* If you use a weather data text file specify full path */
/* save_area->file_ptr = fopen("tblsrv.dat","r"); */
save_area->file_pos = 0 ;
break ;
/* Normal call UDF: Fetch next row */ (See note 2)
case SQL_TF_FETCH:
/* If you use a weather data text file */
/* memset(line_buf, \0, 81); */
/* if (fgets(line_buf, 80, save_area->file_ptr) == NULL) { */
if ( weather_data[save_area->file_pos] == ( char * ) 0 ) {
/* SQLUDF_STATE is part of SQLUDF_TRAIL_ARGS_ALL */
strcpy( SQLUDF_STATE, "02000" ) ;
break ;
}
memset( line_buf, \0, 81 ) ;
strcpy( line_buf, weather_data[save_area->file_pos] ) ;
line_buf[3] = \0 ;
/* Clean all field data and field null indicator data */
clean_fields( 0 ) ;
SQL programming
211
/* Fills city field null indicator data */

fields[0].fld_ind = SQL_NOTNULL ;
/* Find a full city name using a short name */
/* Fills city field data */
if ( get_name( line_buf, fields[0].fld_field ) == 0 ) {
save_area->file_pos++ ;
/* memset(line_buf, \0, 81); */
/* if (fgets(line_buf, 80, save_area->file_ptr) == NULL) { */
if ( weather_data[save_area->file_pos] == ( char * ) 0 ) {
/* SQLUDF_STATE is part of SQLUDF_TRAIL_ARGS_ALL */
strcpy( SQLUDF_STATE, "02000" ) ;
break ;
}
memset( line_buf, \0, 81 ) ;
strcpy( line_buf, weather_data[save_area->file_pos] ) ;
line_buf_pos = strlen( line_buf ) ;
while ( line_buf_pos > 0 ) {
if ( line_buf[line_buf_pos] >= )
line_buf_pos = 0 ;
else {
line_buf[line_buf_pos] = \0 ;
line_buf_pos-- ;
}
}
}
/* Fills field data and field null indicator data ... */
/* ... for selected city from text weather data */
get_value( line_buf, 1 ) ; /* Skips city field */
/* Builds return row fields */
strcpy( city, fields[0].fld_field ) ;
memcpy( (void *) temp_in_f,
fields[1].fld_field,
sizeof( SQLUDF_INTEGER ) ) ;
memcpy( (void *) humidity,
strcpy( wind, fields[3].fld_field ) ;
memcpy( (void *) wind_velocity,
memcpy( (void *) barometer,
sizeof( SQLUDF_DOUBLE ) ) ;
strcpy( forecast, fields[6].fld_field ) ;
/* Builds return row field null indicators */
memcpy( (void *) city_ind,
&(fields[0].fld_ind),
sizeof( SQLUDF_NULLIND ) ) ;
memcpy( (void *) temp_in_f_ind,
memcpy( (void *) humidity_ind,
memcpy( (void *) wind_ind,
memcpy( (void *) wind_velocity_ind,
memcpy( (void *) barometer_ind,
212
memcpy( (void *) forecast_ind,
/* Next city weather data */
save_area->file_pos++ ;
break ;
/* Special last call UDF for clean up (no real args!): Close table */ (See note 3)
case SQL_TF_CLOSE:
/* fclose(save_area->file_ptr); */
/* save_area->file_ptr = NULL; */
save_area->file_pos = 0 ;
break ;
}
}
Referring to the embedded notes in this UDF code, note the following points:
1. The scratchpad is defined. The row variable is initialized on the OPEN call, and the iptr array and
nbr_rows variable are filled in by the mystery function at open time.
2. FETCH traverses the iptr array, using row as an index, and moves the values of interest from the
current element of iptr to the location pointed to by out_c1, out_c2, and out_c3 result value
pointers.
3. CLOSE frees the storage acquired by OPEN and anchored in the scratchpad.
Following is the CREATE FUNCTION statement for this UDF:
CREATE FUNCTION tfweather_u()
RETURNS TABLE (CITY VARCHAR(25),
TEMP_IN_F INTEGER,
HUMIDITY INTEGER,
WIND VARCHAR(5),
WIND_VELOCITY INTEGER,
BAROMETER FLOAT,
FORECAST VARCHAR(25))
SPECIFIC tfweather_u
DISALLOW PARALLEL
NOT FENCED
DETERMINISTIC
NO SQL
NO EXTERNAL ACTION
SCRATCHPAD
NO FINAL CALL
LANGUAGE C
EXTERNAL NAME LIB1/WEATHER(weather);
For this table function definition, note the following points:

v It does not take any input, and it returns seven output columns.
v SCRATCHPAD is specified, so DB2 allocates, properly initializes, and passes the scratchpad argument.
v NO FINAL CALL is specified.
v The function is specified as NOT DETERMINISTIC, because it depends on more than the SQL input
arguments. That is, it depends on the mystery function and we assume that the content can vary from
execution to execution.
SQL programming
213
v CARDINALITY 100, the default, is an estimate of the expected number of rows returned, which is
provided to the DB2 optimizer.
v DBINFO is not used, and the optimization to only return the columns needed by the particular
statement referencing the function is not implemented.
To select all of the rows generated by this table function, use the following query:
SELECT *
FROM TABLE (tfweather_u())x
Using UDFs in SQL statements

Scalar and column user-defined functions (UDFs) can be called within an SQL statement almost
everywhere an expression is valid. Table UDFs can be called in the FROM clause of a SELECT statement.
Listed here are a few restrictions on the use of UDFs.
v UDFs and system generated functions cannot be specified in check constraints. Check constraints also
cannot contain references to some built-in functions that are implemented by the system as UDFs.
v External UDFs, SQL UDFS and the built-in functions DLVALUE, DLURLPATH, DLURLPATHONLY,
DLURLSCHEME, DLURLCOMPLETE, and DLURLSERVER cannot be referenced in an ORDER BY or
GROUP BY clause, unless the SQL statement is read-only and allows temporary processing
(ALWCPYDTA(*YES) or (*OPTIMIZE)).
Using parameter markers or the NULL values as function arguments:
You cannot use a parameter marker or a NULL value as a function argument. Because function resolution
does not know what data type this type of argument might turn out to be, it cannot resolve the reference.
You cannot code the following:
BLOOP(?)
or
BLOOP(NULL)
You can use the CAST specification to provide a data type for the parameter marker or NULL value that
function resolution can use:
BLOOP(CAST(? AS INTEGER))
or
BLOOP(CAST(NULL AS INTEGER))
Using qualified function references:

If you use a qualified function reference, you restrict the search for a matching function to the specified
schema.
For example, you have the following statement:
SELECT PABLO.BLOOP(COLUMN1) FROM T
Only the BLOOP functions in schema PABLO are considered. It does not matter that user SERGE has
defined a BLOOP function, or whether there is a built-in BLOOP function. Now suppose that user
PABLO has defined two BLOOP functions in his schema:
CREATE FUNCTION BLOOP (INTEGER) RETURNS ...
CREATE FUNCTION BLOOP (DOUBLE) RETURNS ...
BLOOP is thus overloaded within the PABLO schema, and the function selection algorithm chooses the
best BLOOP, depending on the data type of the argument, COLUMN1. In this case, both of the
PABLO.BLOOPs take numeric arguments, and if COLUMN1 is not one of the numeric types, the
214
statement will fail. On the other hand, if COLUMN1 is either SMALLINT or INTEGER, function selection
will resolve to the first BLOOP, while if COLUMN1 is DECIMAL or DOUBLE, the second BLOOP will be
chosen.
Several points about this example:
1. It illustrates argument promotion. The first BLOOP is defined with an INTEGER parameter, yet you
can pass it a SMALLINT argument. The function selection algorithm supports promotions among the
built-in data types and DB2 performs the appropriate data value conversions.
2. If for some reason you want to call the second BLOOP with a SMALLINT or INTEGER argument,
you need to take an explicit action in your statement as follows:
SELECT PABLO.BLOOP(DOUBLE(COLUMN1)) FROM T
3. If you want to call the first BLOOP with a DECIMAL or DOUBLE argument, you have your choice of
explicit actions, depending on your intent:
SELECT PABLO.BLOOP(INTEGER(COLUMN1)) FROM T
SELECT PABLO.BLOOP(FLOOR(COLUMN1)) FROM T
Related reference:
Using unqualified function references
You can use an unqualified function reference instead of a qualified function reference. When searching
for a matching function, DB2 normally uses the function path to qualify the reference.
Defining a UDT on page 244
You define a user-defined type (UDT) using the CREATE DISTINCT TYPE statement.
Using unqualified function references:
You can use an unqualified function reference instead of a qualified function reference. When searching
for a matching function, DB2 normally uses the function path to qualify the reference.
In the case of the DROP FUNCTION and COMMENT ON FUNCTION statements, the reference is
qualified using the current authorization ID, if they are unqualified for *SQL naming, or *LIBL for *SYS
naming. Thus, it is important that you know what your function path is, and what, if any, conflicting
functions exist in the schemas of your current function path. For example, suppose that you are PABLO
and your static SQL statement is as follows, where COLUMN1 is data type INTEGER:
SELECT BLOOP(COLUMN1) FROM T
You have created the two BLOOP functions in the section Using qualified function reference, and you
want and expect one of them to be chosen. If the following default function path is used, the first BLOOP
is chosen (since COLUMN1 is INTEGER), if there is no conflicting BLOOP in QSYS or QSYS2:
"QSYS","QSYS2","PABLO"
However, suppose you have forgotten that you are using a script for precompiling and binding which
you previously wrote for another purpose. In this script, you explicitly coded your SQLPATH parameter
to specify the following function path for another reason that does not apply to your current work:
"KATHY","QSYS","QSYS2","PABLO"
If there is a BLOOP function in schema KATHY, the function selection can very well resolve to that
function, and your statement executes without error. You are not notified because DB2 assumes that you
know what you are doing. It is your responsibility to identify the incorrect output from your statement
and make the required correction.
Related reference:
Using qualified function references on page 214
schema.
SQL programming
215
Summary of function references:

For both qualified and unqualified function references, the function selection algorithm looks at all the
applicable functions, both built-in and user-defined functions, that have the given name, the same
number of defined parameters as arguments, and each parameter identical to or promotable from the
type of the corresponding argument.
Applicable functions means functions in the named schema for a qualified reference, or functions in the
schemas of the function path for an unqualified reference. The algorithm looks for an exact match, or
failing that, a best match among these functions. The current function path is used, in the case of an
unqualified reference only, as the deciding factor if two identically good matches are found in different
schemas.
An interesting feature is that function references can be nested, even references to the same function. This
is generally true for built-in functions as well as UDFs. However, there are some limitations when
aggregate functions are involved.
Refining an earlier example:
CREATE FUNCTION BLOOP (INTEGER) RETURNS INTEGER ...
CREATE FUNCTION BLOOP (DOUBLE) RETURNS INTEGER ...
Now consider the following statement:

SELECT BLOOP( BLOOP(COLUMN1)) FROM T
If COLUMN1 is a DECIMAL or DOUBLE column, the inner BLOOP reference resolves to the second
BLOOP defined above. Because this BLOOP returns an INTEGER, the outer BLOOP resolves to the first
BLOOP.
Alternatively, if COLUMN1 is a SMALLINT or INTEGER column, the inner BLOOP reference resolves to
the first BLOOP defined above. Because this BLOOP returns an INTEGER, the outer BLOOP also resolves
to the first BLOOP. In this case, you are seeing nested references to the same function.
A few additional points important for function references are:
v You can define a function with the name of one of the SQL operators. For example, suppose you can
attach some meaning to the "+" operator for values which have distinct type BOAT. You can define the
following UDF:
CREATE FUNCTION "+" (BOAT, BOAT) RETURNS ...
Then you can write the following valid SQL statement:

SELECT "+"(BOAT_COL1, BOAT_COL2)
FROM BIG_BOATS
WHERE BOAT_OWNER = Nelson Mattos
You are not permitted to overload the built-in conditional operators such as >, =, LIKE, IN, and so on, in
this way.
v The function selection algorithm does not consider the context of the reference in resolving to a
particular function. Look at these BLOOP functions, modified a bit from before:
CREATE FUNCTION BLOOP (INTEGER) RETURNS INTEGER ...
CREATE FUNCTION BLOOP (DOUBLE) RETURNS CHAR(10)...
Now suppose you write the following SELECT statement:

SELECT ABCDEFG CONCAT BLOOP(SMALLINT_COL) FROM T
Because the best match, resolved using the SMALLINT argument, is the first BLOOP defined above,
the second operand of the CONCAT resolves to data type INTEGER. The statement might not return
the expected result since the returned integer will be cast as a VARCHAR before the CONCAT is
performed. If the first BLOOP was not present, the other BLOOP is chosen and the statement execution
is successful.
216
v UDFs can be defined with parameters or results having any of the LOB types: BLOB, CLOB, or
DBCLOB. The system will materialize the entire LOB value in storage before calling such a function,
even if the source of the value is a LOB locator host variable. For example, consider the following
fragment of a C language application:
SQL TYPE IS CLOB(150K) clob150K ;
SQL TYPE IS CLOB_LOCATOR clob_locator1;
char
string[40];
/* LOB host var */

/* LOB locator host var */
/* string host var */
Either host variable :clob150K or :clob_locator1 is valid as an argument for a function whose
corresponding parameter is defined as CLOB(500K). Referring to the FINDSTRING defined in Example:
String search on page 195 both of the following are valid in the program:
... SELECT FINDSTRING (:clob150K, :string) FROM ...
... SELECT FINDSTRING (:clob_locator1, :string) FROM ...
v External UDF parameters or results which have one of the LOB types can be created with the AS
LOCATOR modifier. In this case, the entire LOB value is not materialized before invocation. Instead, a
LOB LOCATOR is passed to the UDF.
You can also use this capability on UDF parameters or results which have a distinct type that is based
on a LOB. This capability is limited to external UDFs. Note that the argument to such a function can be
any LOB value of the defined type; it does not need to be a host variable defined as one of the
LOCATOR types. The use of host variable locators as arguments is completely unrelated to the use of
AS LOCATOR in UDF parameters and result definitions.
v UDFs can be defined with distinct types as parameters or as the result. DB2 will pass the value to the
UDF in the format of the source data type of the distinct type.
Distinct type values that originate in a host variable and which are used as arguments to a UDF which
has its corresponding parameter defined as a distinct type must be explicitly cast to the distinct type
by the user. There is no host language type for distinct types. DB2's strong typing necessitates this.
Otherwise your results may be ambiguous. So, consider the BOAT distinct type that is defined over a
BLOB that takes an object of type BOAT as its argument. In the following fragment of a C language
application, the host variable :ship holds the BLOB value that is to passed to the BOAT_COST
function:
SQL TYPE IS BLOB(150K) ship;
Both of the following statements correctly resolve to the BOAT_COST function, because both cast the
:ship host variable to type BOAT:
... SELECT BOAT_COST (BOAT(:ship)) FROM ...
... SELECT BOAT_COST (CAST(:ship AS BOAT)) FROM ...
If there are multiple BOAT distinct types in the database, or BOAT UDFs in other schema, you must be
careful with your function path. Otherwise your results may be unpredictable.
Triggers
A trigger is a set of actions that runs automatically when a specified change operation is performed on a
specified table or view.
The change operation can be an SQL INSERT, UPDATE, or DELETE statement, or an insert, an update, or
a delete high-level language statement in an application program. Triggers are useful for tasks such as
enforcing business rules, validating input data, and keeping an audit trail.
Triggers can be defined as SQL or external.
For an external trigger, the CRTPFTRG CL command is used. The program containing the set of trigger
actions can be defined in any supported high level language. External triggers can be insert, update,
delete, or read triggers.
SQL programming
217
For an SQL trigger, the CREATE TRIGGER statement is used. The trigger program is defined entirely
using SQL. SQL triggers can be insert, update, or delete triggers.
Once a trigger is associated with a table or view, the trigger support calls the trigger program whenever a
change operation is initiated against the table or view, or any logical file or view created over the table or
view. SQL triggers and external triggers can be defined for the same table. Only SQL triggers can be
defined for a view. Up to 200 triggers can be defined for a single table or view.
Each change operation for a table can call a trigger before or after the change operation occurs.
Additionally, you can add a read trigger that is called every time the table is accessed. Thus, a table can
be associated with many types of triggers.
v Before delete trigger
v Before insert trigger
v Before update trigger
v
v
v
v
After delete trigger

After insert trigger
After update trigger
Read-only trigger (external trigger only)
Each change operation for a view can call an instead of trigger which will perform some set of actions
instead of the insert, update, or delete. A view can be associated with an:
v Instead of delete trigger
v Instead of insert trigger
v Instead of update trigger
Related tasks:
SQL triggers
The SQL CREATE TRIGGER statement provides a way for the database management system to actively
control, monitor, and manage a group of tables and views whenever an insert, an update, or a delete
operation is performed.
The statements specified in the SQL trigger are executed each time an insert, update, or delete operation
is performed. An SQL trigger may call stored procedures or user-defined functions to perform additional
processing when the trigger is executed.
Unlike stored procedures, an SQL trigger cannot be directly called from an application. Instead, an SQL
trigger is invoked by the database management system on the execution of a triggering insert, update, or
delete operation. The definition of the SQL trigger is stored in the database management system and is
invoked by the database management system when the SQL table or view that the trigger is defined on,
is modified.
An SQL trigger can be created by specifying the CREATE TRIGGER SQL statement. All objects referred to
in the CREATE TRIGGER statement (such as tables and functions) must exist; otherwise, the trigger will
not be created. The statements in the routine-body of the SQL trigger are transformed by SQL into a
program (*PGM) object. The program is created in the schema specified by the trigger name qualifier. The
specified trigger is registered in the SYSTRIGGERS, SYSTRIGDEP, SYSTRIGCOL, and SYSTRIGUPD SQL
catalogs.
Related concepts:
Debugging an SQL routine on page 227
By specifying SET OPTION DBGVIEW = *SOURCE in the CREATE PROCEDURE, CREATE FUNCTION,
or CREATE TRIGGER statement, you can debug the generated program or service program at the SQL
statement level.
218
Related reference:
CREATE TRIGGER
BEFORE SQL triggers:
BEFORE triggers cannot change tables, but they can be used to verify input column values and to change
column values that are inserted or updated in a table.
In the following example, the trigger is used to set the fiscal quarter for the corporation before inserting
the row into the target table.
CREATE TABLE TransactionTable (DateOfTransaction DATE, FiscalQuarter SMALLINT)
CREATE TRIGGER TransactionBeforeTrigger BEFORE INSERT ON TransactionTable
REFERENCING NEW AS new_row
FOR EACH ROW MODE DB2ROW
BEGIN
DECLARE newmonth SMALLINT;
SET newmonth = MONTH(new_row.DateOfTransaction);
IF newmonth < 4 THEN
SET new_row.FiscalQuarter=3;
ELSEIF newmonth < 7 THEN
ELSEIF newmonth < 10 THEN
ELSE
END IF;
END
For the SQL insert statement below, the "FiscalQuarter" column is set to 2, if the current date is
November 14, 2000.
INSERT INTO TransactionTable(DateOfTransaction)
VALUES(CURRENT DATE)
SQL triggers have access to and can use user-defined types (UDTs) and stored procedures. In the
following example, the SQL trigger calls a stored procedure to execute some predefined business logic, in
this case, to set a column to a predefined value for the business.
CREATE DISTINCT TYPE enginesize AS DECIMAL(5,2) WITH COMPARISONS
CREATE DISTINCT TYPE engineclass AS VARCHAR(25) WITH COMPARISONS
CREATE PROCEDURE SetEngineClass(IN SizeInLiters enginesize,
OUT CLASS engineclass)
LANGUAGE SQL CONTAINS SQL
BEGIN
IF SizeInLiters<2.0 THEN
SET CLASS = Mouse;
ELSEIF SizeInLiters<3.1 THEN
SET CLASS =Economy Class;
SET CLASS =Most Common Class;
SET CLASS = Getting Expensive;
ELSE
SET CLASS =Stop Often for Fillups;
END IF;
END
CREATE TABLE EngineRatings (VariousSizes enginesize, ClassRating engineclass)
CREATE TRIGGER SetEngineClassTrigger BEFORE INSERT ON EngineRatings
SQL programming
219

CALL SetEngineClass(new_row.VariousSizes, new_row.ClassRating)
For the SQL insert statement below, the "ClassRating" column is set to "Economy Class", if the
"VariousSizes" column has the value of 3.0.
INSERT INTO EngineRatings(VariousSizes) VALUES(3.0)
SQL requires all tables, user-defined functions, procedures and user-defined types to exist before creating
an SQL trigger. In the examples above, all of the tables, stored procedures, and user-defined types are
defined before the trigger is created.
AFTER SQL triggers:
An after trigger runs after the corresponding insert, update, or delete changes are applied to the table.
The WHEN condition can be used in an SQL trigger to specify a condition. If the condition evaluates to
true, the SQL statements in the SQL trigger routine body are run. If the condition evaluates to false, the
SQL statements in the SQL trigger routine body are not run, and control is returned to the database
system.
In the following example, a query is evaluated to determine if the statements in the trigger routine body
should be run when the trigger is activated.
CREATE TABLE TodaysRecords(TodaysMaxBarometricPressure FLOAT,
TodaysMinBarometricPressure FLOAT)
CREATE TABLE OurCitysRecords(RecordMaxBarometricPressure FLOAT,
RecordMinBarometricPressure FLOAT)
CREATE TRIGGER UpdateMaxPressureTrigger
AFTER UPDATE OF TodaysMaxBarometricPressure ON TodaysRecords
WHEN (new_row.TodaysMaxBarometricPressure>
(SELECT MAX(RecordMaxBarometricPressure) FROM
OurCitysRecords))
UPDATE OurCitysRecords
SET RecordMaxBarometricPressure =
new_row.TodaysMaxBarometricPressure
CREATE TRIGGER UpdateMinPressureTrigger
AFTER UPDATE OF TodaysMinBarometricPressure
ON TodaysRecords
WHEN(new_row.TodaysMinBarometricPressure<
(SELECT MIN(RecordMinBarometricPressure) FROM
OurCitysRecords))
UPDATE OurCitysRecords
SET RecordMinBarometricPressure =
new_row.TodaysMinBarometricPressure
First the current values are initialized for the tables.

INSERT INTO TodaysRecords VALUES(0.0,0.0)
INSERT INTO OurCitysRecords VALUES(0.0,0.0)
For the SQL update statement below, the RecordMaxBarometricPressure in OurCitysRecords is updated
by the UpdateMaxPressureTrigger.
UPDATE TodaysRecords SET TodaysMaxBarometricPressure = 29.95
220
But tomorrow, if the TodaysMaxBarometricPressure is only 29.91, then the RecordMaxBarometricPressure

is not updated.
UPDATE TodaysRecords SET TodaysMaxBarometricPressure = 29.91
SQL allows the definition of multiple triggers for a single triggering action. In the previous example,
there are two AFTER UPDATE triggers: UpdateMaxPressureTrigger and UpdateMinPressureTrigger. These
triggers are activated only when specific columns of the table TodaysRecords are updated.
AFTER triggers may modify tables. In the example above, an UPDATE operation is applied to a second
table. Note that recursive insert and update operations should be avoided. The database management
system terminates the operation if the maximum trigger nesting level is reached. You can avoid recursion
by adding conditional logic so that the insert or update operation is exited before the maximum nesting
level is reached. The same situation needs to be avoided in a network of triggers that recursively cascade
| through the network of triggers.
|
Multiple event SQL triggers:
A single trigger can be defined for more than one insert, update, or delete event.
|
|
|
|
A trigger can be defined to handle one, two, or all three of the insert, update, and delete events. The only
restriction is that the events must share a common BEFORE, AFTER, or INSTEAD OF triggering time.
Trigger event predicates can be used within the trigger body to distinguish which event caused the
trigger to be activated.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In the following example, several warnings are grouped into a single trigger definition.
|
|
|
In the trigger body the INSERTING, UPDATING, and DELETING predicates are used to determine which
event caused the trigger to activate. A distinct piece of code is executed for each of the defined events.
For each event, a warning condition is handled.
CREATE TABLE PARTS (INV_NUM INT, PART_NAME CHAR(20), ON_HAND INT, MAX_INV INT,
PRIMARY KEY (INV_NUM))
CREATE OR REPLACE TRIGGER INVENTORY_WARNINGS
AFTER DELETE OR INSERT OR UPDATE OF ON_HAND ON PARTS
REFERENCING NEW AS N_INV
OLD AS O_INV
FOR EACH ROW MODE DB2SQL
BEGIN
IF INSERTING THEN
IF (N_INV.ON_HAND > N_INV.MAX_INV) THEN
BEGIN
SIGNAL SQLSTATE 75001 (Inventory on hand exceeds maximum allowed.);
END;
END IF;
ELSEIF UPDATING THEN
IF (N_INV.ON_HAND < 5) THEN
BEGIN
SIGNAL SQLSTATE 75002 (Inventory low - Re-order soon.);
END;
END IF;
ELSEIF DELETING THEN
IF (O_INV.ON_HAND > 0) THEN
BEGIN
SIGNAL SQLSTATE 75004 (Deleting a part while inventory still in stock.);
END;
END IF;
END IF;
END
SQL programming
221
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In the next example, the trigger event predicates are used in an INSERT statement to generate a row for a
transaction history table.
CREATE TABLE TRANSACTION_HISTORY(INV_NUM INT, POSTTIME TIMESTAMP,
TRANSACTION_TYPE CHAR(1))
CREATE TRIGGER SET_TRANS_HIST
AFTER INSERT OR UPDATE OR DELETE ON PARTS
REFERENCING NEW AS N
OLD AS O
BEGIN
INSERT INTO TRANSACTION_HISTORY VALUES (
CASE
WHEN INSERTING OR UPDATING
THEN N.INV_NUM
WHEN DELETING
THEN O.INV_NUM
END,
CURRENT TIMESTAMP,
CASE
WHEN INSERTING
THEN I
WHEN UPDATING
THEN U
WHEN DELETING
THEN D
END
);
END
| For this trigger, the same routine logic is used by all three trigger events. The trigger event predicates are
| used to determine whether the inventory number needs to be read from the before or after row value and
| a second time to set the type of transaction.
INSTEAD OF SQL triggers:
An INSTEAD OF trigger is an SQL trigger that is processed instead of an SQL UPDATE, DELETE or
INSERT statement. Unlike SQL BEFORE and AFTER triggers, an INSTEAD OF trigger can be defined
only on a view, not a table.
An INSTEAD OF trigger allows a view, which is not inherently insertable, updatable, or deletable, to be
inserted into, updated, or deleted from. See CREATE VIEW for more information about deleteable,
updatable, and insertable views.
After an SQL INSTEAD OF trigger is added to a view, the view which previously could only be read
from can be used as the target of an insert, update, or delete operation. The INSTEAD OF trigger defines
the operations which need to be performed to maintain the view.
A view can be used to control access to tables. INSTEAD OF triggers can simplify the maintenance of
access control to tables.
Using an INSTEAD OF trigger
The definition of the following view V1 is updatable, deletable, and insertable:
CREATE TABLE T1 (C1 VARCHAR(10), C2 INT)
CREATE VIEW V1(X1) AS SELECT C1 FROM T1 WHERE C2 > 10
For the following insert statement, C1 in table T1 will be assigned a value of 'A'. C2 will be assigned the
NULL value. The NULL value would cause the new row to not match the selection criteria C2 > 10 for
the view V1.
222
INSERT INTO V1 VALUES(A)
Adding the INSTEAD OF trigger IOT1 can provide a different value for the row that will be selected by
the view:
CREATE TRIGGER IOT1 INSTEAD OF INSERT ON V1
REFERENCING NEW AS NEW_ROW
INSERT INTO T1 VALUES(NEW_ROW.X1, 15)
Making a view deletable

The definition of the following join view V3 is not updatable, deletable, or insertable:
CREATE TABLE A (A1 VARCHAR(10), A2 INT)
CREATE VIEW V1(X1) AS SELECT A1 FROM A
CREATE TABLE B (B1 VARCHAR(10), B2 INT)
CREATE VIEW V2(Y1) AS SELECT B1 FROM B
CREATE VIEW V3(Z1, Z2) AS SELECT V1.X1, V2.Y1 FROM V1, V2 WHERE V1.X1 = A AND V2.Y1 > B
Adding the INSTEAD OF trigger IOT2 makes the view V3 deletable:

CREATE TRIGGER IOT2 INSTEAD OF DELETE ON V3
REFERENCING OLD AS OLD_ROW
BEGIN
DELETE FROM A WHERE A1 = OLD_ROW.Z1;
DELETE FROM B WHERE B1 = OLD_ROW.Z2;
END
With this trigger, the following DELETE statement is allowed. It deletes all rows from table A having an
A1 value of 'A', and all rows from table B having a B1 value of 'X'.
DELETE FROM V3 WHERE Z1 = A AND Z2 = X
INSTEAD OF triggers with views defined on views

The following definition of view V2 defined on V1 is not inherently insertable, updatable, or deletable:
CREATE TABLE T1 (C1 VARCHAR(10), C2 INT)
CREATE TABLE T2 (D1 VARCHAR(10), D2 INT)
CREATE VIEW V1(X1, X2) AS SELECT C1, C2 FROM T1
UNION SELECT D1, D2 FROM T2
CREATE VIEW V2(Y1, Y2) AS SELECT X1, X2 FROM V1
Adding the INSTEAD OF trigger IOT1 to V1 does not make V2 updatable:

CREATE TRIGGER IOT1 INSTEAD OF UPDATE ON V1
REFERENCING OLD AS OLD_ROW NEW AS NEW_ROW
BEGIN
UPDATE T1 SET C1 = NEW_ROW.X1, C2 = NEW_ROW.X2 WHERE
C1 = OLD_ROW.X1 AND C2 = OLD_ROW.X2;
UPDATE T2 SET D1 = NEW_ROW.X1, D2 = NEW_ROW.D2 WHERE
D1 = OLD_ROW.X1 AND D2 = OLD_ROW.X2;
END
View V2 remains not updatable since the original definition of view V2 remains not updatable.
Using INSTEAD OF triggers with BEFORE and AFTER triggers
The addition of an INSTEAD OF trigger to a view does not cause any conflicts with BEFORE and AFTER
triggers defined on the base tables:
SQL programming
223
CREATE TABLE T1 (C1 VARCHAR(10), C2 DATE)

CREATE TABLE T2 (D1 VARCHAR(10))
CREATE TRIGGER AFTER1 AFTER DELETE ON T1
DELETE FROM T2 WHERE D1 = OLD_ROW.C1
CREATE VIEW V1(X1, X2) AS SELECT SUBSTR(T1.C1, 1, 1), DAYOFWEEK_ISO(T1.C2) FROM T1
CREATE TRIGGER IOT1 INSTEAD OF DELETE ON V1
DELETE FROM T1 WHERE C1 LIKE (OLD_ROW.X1 CONCAT %)
Any delete operations for view V1 result in the AFTER DELETE trigger AFTER1 being activated also
because trigger IOT1 performs a delete on table T1. The delete for table T1 causes the AFTER1 trigger to
be activated.
Dependent views and INSTEAD OF triggers
When adding an INSTEAD OF trigger to a view, if the view definition references views that also have
INSTEAD OF triggers defined, you should define INSTEAD OF triggers for all three operations,
UPDATE, DELETE, and INSERT, to avoid confusion on what capabilities the view being defined contains
versus what the capabilities of any dependent views have.
Handlers in SQL triggers:
A handler in an SQL trigger gives the SQL trigger the ability to recover from an error or log information
about an error that has occurred while processing the SQL statements in the trigger routine body.
In the following example, there are two handlers defined: one to handle the overflow condition and a
second handler to handle SQL exceptions.
CREATE TABLE ExcessInventory(Description VARCHAR(50), ItemWeight SMALLINT)
CREATE TABLE YearToDateTotals(TotalWeight SMALLINT)
CREATE TABLE FailureLog(Item VARCHAR(50), ErrorMessage VARCHAR(50), ErrorCode INT)
CREATE TRIGGER InventoryDeleteTrigger
AFTER DELETE ON ExcessInventory
REFERENCING OLD AS old_row
BEGIN
DECLARE sqlcode INT;
DECLARE invalid_number condition FOR 22003;
DECLARE exit handler FOR invalid_number
INSERT INTO FailureLog VALUES(old_row.Description,
Overflow occurred in YearToDateTotals, sqlcode);
DECLARE exit handler FOR sqlexception
INSERT INTO FailureLog VALUES(old_row.Description,
SQL Error occurred in InventoryDeleteTrigger, sqlcode);
UPDATE YearToDateTotals SET TotalWeight=TotalWeight +
old_row.itemWeight;
END
First, the current values for the tables are initialized.

INSERT INTO ExcessInventory VALUES(Desks,32500)
INSERT INTO ExcessInventory VALUES(Chairs,500)
INSERT INTO YearToDateTotals VALUES(0)
224
When the first SQL delete statement below is executed, the ItemWeight for the item "Desks" is added to
the column total for TotalWeight in the table YearToDateTotals. When the second SQL delete statement is
executed, an overflow occurs when the ItemWeight for the item "Chairs" is added to the column total for
TotalWeight, as the column only handles values up to 32767. When the overflow occurs, the
invalid_number exit handler is executed and a row is written to the FailureLog table. The sqlexception
exit handler runs, for example, if the YearToDateTotals table was deleted by accident. In this example, the
handlers are used to write a log so that the problem can be diagnosed at a later time.
DELETE FROM ExcessInventory WHERE Description=Desks
DELETE FROM ExcessInventory WHERE Description=Chairs
SQL trigger transition tables:

An SQL trigger might need to refer to all of the affected rows for an SQL insert, update, or delete
operation. For example, a trigger needs to apply aggregate functions, such as MIN or MAX, to a specific
column of the affected rows. The OLD_TABLE and NEW_TABLE transition tables can be used for this
purpose.
In the following example, the trigger applies the aggregate function MAX to all of the affected rows of
the table StudentProfiles.
CREATE TABLE StudentProfiles(StudentsName VARCHAR(125),
StudentsYearInSchool SMALLINT, StudentsGPA DECIMAL(5,2))
CREATE TABLE CollegeBoundStudentsProfile
(YearInSchoolMin SMALLINT, YearInSchoolMax SMALLINT, StudentGPAMin
DECIMAL(5,2), StudentGPAMax DECIMAL(5,2))
CREATE TRIGGER UpdateCollegeBoundStudentsProfileTrigger
AFTER UPDATE ON StudentProfiles
REFERENCING NEW_TABLE AS ntable
FOR EACH STATEMENT MODE DB2SQL
BEGIN
DECLARE maxStudentYearInSchool SMALLINT;
SET maxStudentYearInSchool =
(SELECT MAX(StudentsYearInSchool) FROM ntable);
IF maxStudentYearInSchool >
(SELECT MAX (YearInSchoolMax) FROM
CollegeBoundStudentsProfile) THEN
UPDATE CollegeBoundStudentsProfile SET YearInSchoolMax =
maxStudentYearInSchool;
END IF;
END
In the preceding example, the trigger is processed a single time following the processing of a triggering
update statement because it is defined as a FOR EACH STATEMENT trigger. You will need to consider
the processing overhead required by the database management system for populating the transition tables
when you define a trigger that references transition tables.
External triggers
For an external trigger, the program that contains the set of trigger actions can be defined in any
supported high-level language that creates a *PGM object.
The trigger program can have SQL embedded in it. To define an external trigger, you must create a
trigger program and add it to a table using the Add Physical File Trigger (ADDPFTRG) CL command or
you can add it using System i Navigator. To add a trigger to a table, you must do the following things:
v Identify the table.
v Identify the kind of operation.
v Identify the program that performs the actions that you want.
Related tasks:
SQL programming
225

|
Array support in SQL procedures
| SQL procedures support parameters and variables of array types. Arrays are a convenient way of passing
| transient collections of data between an application and a stored procedure or between two stored
| procedures.
|
|
|
|
Within SQL stored procedures, arrays can be manipulated as arrays in conventional programming
languages. Furthermore, arrays are integrated within the relational model in such a way that data
represented as an array can be easily converted into a table and data in a table column can be aggregated
into an array. The examples below illustrate several operations on arrays.
Example 1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This example shows two procedures, sub and main. Procedure main creates an array of 6 integers using an
array constructor. It then passes the array to procedure sum, which computes the sum of all the elements
in the input array and returns the result to main. Procedure sum illustrates the use of array subindexing
and of the CARDINALITY function, which returns the number of elements in an array.
Example 2
|
|
|
|
|
|
|
|
|
|
|
|
In this example, we use two array data types (intArray and stringArray), and a persons table with two
columns (id and name). Procedure processPersons adds three additional persons to the table, and returns
an array with the person names that contain the letter 'a', ordered by id. The ids and names of the three
persons to be added are represented as two arrays (ids and names). These arrays are used as arguments
to the UNNEST function, which turns the arrays into a two-column table, whose elements are then
inserted into the persons table. Finally, the last set statement in the procedure uses the ARRAY_AGG
aggregate function to compute the value of the output parameter.
CREATE TYPE intArray AS INTEGER ARRAY[100]

CREATE PROCEDURE sum(IN inList intArray, OUT total INTEGER)
BEGIN
DECLARE i, n INTEGER;
SET n = CARDINALITY(inList);
SET i = 1;
SET total = 0;
WHILE (i <= n) DO
SET total = total + inList[i];
SET i = i + 1;
END WHILE;
END
CREATE PROCEDURE main(OUT arrayTotal INTEGER)
BEGIN
DECLARE numList intArray;
SET numList = ARRAY[1,2,3,4,5,6];
CALL sum(numList,arrayTotal);
END
CREATE TYPE intArray AS INTEGER ARRAY[100]

CREATE TYPE stringArray AS VARCHAR(10) ARRAY[100]
CREATE TABLE persons (id INTEGER, name VARCHAR(10))
226
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
INSERT INTO persons VALUES(2,

(4,
(1,
(3,
Tom),
Gina),
Kathy),
John)
CREATE PROCEDURE processPersons(OUT witha stringArray)

BEGIN
DECLARE ids intArray;
DECLARE names stringArray;
SET ids = ARRAY[5,6,7];
SET names = ARRAY[Denise, Randy, Sue];
INSERT INTO persons(id, name)
(SELECT t.i, t.n FROM UNNEST(ids, names) AS t(i, n));
SET witha = (SELECT ARRAY_AGG(name ORDER BY id)
FROM persons
WHERE name LIKE %a%);
END
Debugging an SQL routine

By specifying SET OPTION DBGVIEW = *SOURCE in the CREATE PROCEDURE, CREATE FUNCTION,
or CREATE TRIGGER statement, you can debug the generated program or service program at the SQL
statement level.
You can also specify DBGVIEW(*SOURCE) as a parameter on a RUNSQLSTM command and it will apply
to all routines within the RUNSQLSTM.
The source view will be created by the system from your original routine body into source file QSQDSRC
in the routine library. If the library cannot be determined, QSQDSRC is created in QTEMP. The source
view is not saved with the program or service program. It will be broken into lines that correspond to
places you can stop in debug. The text, including parameter and variable names, will be folded to
| uppercase. Delimited names and character literals are not folded to uppercase.
|
|
|
|
SQL routines can be debugged using either the SQL Object Processor Root view or the ILE C view. The
debugger can be used to evaluate both SQL variables and C variables in the generated program or
service program. The preferred approach is to debug using the SQL Object Processor Root view, but the
ILE C view can be used as necessary to obtain additional execution information.
SQL Object Processor Root View
|
|
|
|
|
|
|
This view uses the routine source in QSQDSRC. To evaluate an SQL variable, add the prefix '%%' to the
variable name to indicate the name represents an SQL variable. Any SQL variable must be prefixed with
'%%' when it is referenced in a debugger command. SQL variable names are not case sensitive. Both
undelimited and delimited identifiers can be referenced. When an SQL variable name is specified, the
debugger will determine which C variable represents the SQL variable and then display the name and
contents of the corresponding C variable. When an SQL parameter or variable which has an indicator is
referenced, the debugger will return 'NULL' if the indicator is set to indicate the null value.
|
|
|
|
There is no need to qualify a variable name unless there is ambiguity. In that case, the variable should be
qualified by the label of its containing compound SQL block to avoid the ambiguity. C variables can be
referenced while debugging in the SQL Object Processor view. A variable name without the prefix '%%' is
considered to be a C variable.
ILE C listing view
This view uses the generated C source for the SQL routine.
SQL programming
227
All variables and parameters are generated as part of a structure. The structure name must be used when
evaluating a variable in debug. Variables are qualified by the current label name. Parameters are qualified
by the procedure or function name. Transition variables in a trigger are qualified by the appropriate
correlation name. It is highly recommended that you specify a label name for each compound statement
or FOR statement. If you don't specify one, the system will generate one for you. This will make it nearly
impossible to evaluate variables. Remember that all variables and parameters must be evaluated as an
uppercase name. You can also evaluate the name of the structure. This will show you all the variables
within the structure. If a variable or parameter is nullable, the indicator for that variable or parameter
immediately follows it in the structure.
Because SQL routines are generated in C, there are some rules for C that affect SQL source debug.
Delimited names that are specified in the SQL routine body cannot be specified in C. Names are
generated for these names, which again makes it difficult to debug or evaluate them. In order to evaluate
the contents of any character variable, specify an * prior to the name of the variable.
Since the system generates indicators for most variable and parameter names, there is no way to check
directly to see if a variable has the SQL null value. Evaluating a variable will always show a value, even
if the indicator is set to indicate the null value.
| SQL variables cannot be directly referenced (using the '%%' prefix) while debugging in the ILE C view.
In order to determine if a handler is getting called, set a breakpoint on the first statement within the
handler. Variables that are declared in a compound statement or FOR statement within the handler can be
evaluated.
| SQL array debug
|
|
|
|
|
|
|
|
|
|
The SQL array data type, which is only supported in SQL procedures, has special debugging rules since
the array variables do not have permanent storage in the generated C program. Unlike C arrays, SQL
arrays are 1 based. To display the fifth element of the array, specify array index 5 on the EVAL command
(EVAL TSTARR.ABC[5]). Specifying an array variable name without specifying an array index is not
supported; this will result in a variable not found error. To see a range of values in the array, an EVAL
command with array index ranges can be used. For example, to see the first 25 elements in an array,
EVAL TSTARR.ABC[1..25]. The EVAL command will indicate when an array variable has the NULL
value. An expression containing a reference to an array variable that is NULL evaluates to NULL. The
numeric array types can be used in expressions; the other types cannot. The non-prefixed string types
will be displayed as a string, not a pointer.
|
|
|
|
|
Not all debug commands support the SQL array type. They cannot be used on the left side of an
assignment (EVAL TSTARR.ABC[5] = 3). They cannot be used as the target of the '&' address operator
(EVAL &TSTARR.ABC[3]). Arrays cannot be used with the WATCH debug command, either. Array
variables will not be displayed by the EVAL %LOCALVARS command because they are not in the debug
symbol table.
Obfuscating an SQL routine

SQL functions and procedures can be obfuscated so that their routine body logic and statements are not
visible on a system.
Once testing of an SQL procedure or function is complete, you can obfuscate the text so it is not readable
to anyone on the system. To do this, use the WRAP SQL function or the CREATE_WRAPPED SQL
procedure. Both are system provided routines in schema SYSIBMADM.
The WRAP scalar function returns an obfuscated form of the SQL statement that was provided as an
input argument. The CREATE_WRAPPED procedure will obfuscate the SQL statement and then execute
it.
228
When an obfuscated routine is created, the routine body will not be visible in the catalog tables or in the
program object. No listing will be generated and any temporary files used during creation of the routine
will be deleted. The routine will always be created as not debuggable so no debug view containing the
routine content will exist.
The Generate SQL feature of System i Navigator has an option to make it easy to obfuscate many
procedures and functions at one time.
Once a routine is obfuscated, the program or service program object for the SQL routine can be saved
and restored to other systems. It can be used as an object for the Generate SQL feature of System i
Navigator. DB2 will understand how to process the statement correctly and it will remain obfuscated.
For example, suppose your procedure is:
CREATE PROCEDURE UPDATE_STAFF (
IN P_EmpNo CHAR(6),
IN P_NewJob CHAR(5),
IN P_Dept INTEGER)
BEGIN
UPDATE STAFF
SET JOB = P_NewJob
WHERE DEPT = P_Dept and ID = P_EmpNo;
END;
After testing the procedure to make sure it works, you can generate an obfuscated form of the statement
by using the WRAP function.
VALUES(SYSIBMADM.WRAP(
IN P_EmpNo CHAR(6),
IN P_Dept INTEGER)
BEGIN
UPDATE STAFF
SET JOB = P_NewJob
END
));
The result from this statement is a CLOB value that contains a value that looks something like the
following statement. Since the timestamp is used during the obfuscation process, your result can be
different every time. The value is shown here on several lines for convenience. New line characters are
not allowed in the wrapped part of the statement text.
CREATE PROCEDURE UPDATE_STAFF ( IN P_EMPNO CHAR ( 6 ) , IN P_NEWJOB CHAR ( 5 )
, IN P_DEPT INTEGER ) WRAPPED QSQ07010 aacxW8plW8FjG8pnG8VzG8FD68Fj68:Hl8:dY_p
B2qpdW8pdW8pdW_praqebaqebaGEMj_vsPBs5bOJUUqnHVayEl_ogAlGWqz2jJCIE1dQEjt33hd5Sps
5cYGViD1urv7vGKeOcC4CwpCibbmeMfsW3XzXWnlplyX9wunOCqqFiDqaBl
This is an executable SQL statement. It can be run just like the original SQL statement. Altering any of
the characters that follow the WRAPPED keyword will cause the statement to fail.
To deploy this statement, the obfuscated form can be embedded in a RUNSQLSTM source member or
source stream file. You need to be very careful to include exactly the characters in the obfuscated version.
A second way of obfuscating an SQL procedure or function is to use the CREATE_WRAPPED SQL
procedure:
CALL SYSIBMADM.CREATE_WRAPPED(
IN P_EmpNo CHAR(6),
IN P_Dept INTEGER)
BEGIN
SQL programming
229
UPDATE STAFF
SET JOB = P_NewJob
END
);
This will create the procedure and the entire SQL routine body will be obfuscated. Looking at the
ROUTINE_DEFINITION column in SYSROUTINES will show the obfuscated form of the routine body,
starting with the WRAPPED keyword. You must save the original routine source if you might need it for
future reference since there is no way to generate the original source from the obfuscated text.
|
Managing SQL and external routine objects
| SQL and external functions and procedures are implemented using system programs and service
| programs. When managed correctly, these objects can regenerate the routine registration in the
| QSYS2/SYSROUTINES, QSYS2/SYSPARMS, and QSYS2/SYSROUTINEDEP system catalogs.
| When an SQL procedure or function is created, an ILE C program or service program is generated. In
| addition to containing executable statements, this object contains all the information used to define it as
| an SQL routine.
|
|
|
|
When an external procedure or function is created and is associated with an ILE program or service
program object, information about the routine definition is saved in the *PGM or *SRVPGM object. By
successfully adding the routine information to the object, maintaining the object requires less manual
effort.
| The external procedure or function definition can only be saved when:

|
|
|
|
|
|
v The external program is an ILE *PGM or *SRVPGM object.

v The program or service program is not in QSYS, QSYS2, SYSIBM, SYSPROC, or SYSIBMADM.
v The program exists when the CREATE PROCEDURE or CREATE FUNCTION statement is issued and
the program can be found.
v The CREATE or ALTER statement can get an exclusive lock on the program.
v The program does not already contain attributes for 32 routines.
| Message SQL7909 will be issued when an external routine is created, changed, or dropped and the *PGM
| or *SRVPGM could not be modified. This message includes a reason code.
|
|
|
|
When these procedure and function *PGM and *SRVPGM objects are administered like other system
objects, the information saved in the object is used to maintain the SYSROUTINES and SYSPARMS
catalog information. The following CL commands (and their API counterparts) will keep the catalogs in
sync with the executable object for procedures and functions:
| Save/Restore (SAVOBJ/RSTOBJ and SAVLIB/RSTLIB)

|
A row is inserted into the SYSROUTINES catalog for each routine. The EXTERNAL_NAME
|
column contains the name of the newly restored executable object.
| Create Duplicate Object (CRTDUPOBJ)
|
A new row is inserted into the SYSROUTINES catalog. The EXTERNAL_NAME column contains
|
the name of the newly duplicated executable object.
| Copy Library (CPYLIB)
|
A new row is inserted into the SYSROUTINES catalog. The EXTERNAL_NAME column contains
|
the name of the newly duplicated executable object.
| Rename Object (RNMOBJ)
|
The existing row in SYSROUTINES is modified. The EXTERNAL_NAME column contains the
|
name of the renamed executable object.
230
|
|
|
Move Object (MOVOBJ)

The existing row in SYSROUTINES is modified. The EXTERNAL_NAME column contains the
name of the moved executable object.
|
|
|
Clear Library (CLRLIB)

All rows in SYSROUTINES are deleted where the SPECIFIC_SCHEMA column matches the name
of the library being cleared.
|
|
|
Delete Program (DLTPGM) and Delete Service Program (DLTSRVPGM)

For an SQL routine, the corresponding rows in SYSROUTINES are deleted using the
SPECIFIC_NAME and SPECIFIC_SCHEMA columns. No updates are made for external routines.
|
|
Message SQL9015 will be issued when a *PGM or *SRVPGM is operated upon using a system command
and the catalog entries for the associated routine(s) could not be updated.
Improving performance of procedures and functions

When creating a stored procedure or a user-defined function (UDF), the SQL procedural language
processor does not always generate the most efficient code. However, you can reduce the number of
database engine calls and improve performance.
Some changes are in the design of a routine and some are in the implementation. For example,
differences between how the C language compiler handles host variables and the way the SQL
procedural processor requires the host variables to be handled can cause many calls to the database
engine. These calls are very expensive and, when done many times, can significantly degrade
performance.
|
|
|
|
The IBM i 6.1 release contained significant improvements to the performance of the code generated
within SQL routines. If you have SQL procedures or functions that have not been rebuilt since before IBM
i 6.1, it is recommended that you drop and recreate them to guarantee that your procedure or function is
running with the improved code generation.
|
|
|
|
|
|
|
|
|
Another simple action which will improve the performance of SQL procedures is to use the PROGRAM
TYPE SUB clause. When omitted or PROGRAM TYPE MAIN is used on the CREATE PROCEDURE
(SQL) statement, an ILE C program (*PGM) is built for the procedure. PROGRAM TYPE SUB results in
an ILE C service program (*SRVPGM) being built for the procedure. The use of PROGRAM TYPE SUB is
most relevant for procedures that are frequently called within a performance critical application.
PROGRAM TYPE SUB procedures perform better due to the fact that ILE service programs are activated
a single time per activation group, while ILE programs are activated on every call. The cost of an ILE
activation is related to the procedure size, complexity, number of parameters, number of variables, and
the size of the parameters and variables.
|
|
|
The only functional difference to be noted when using PROGRAM TYPE SUB is that the
QSYS2.SYSROUTINES catalog entry for the EXTERNAL_NAME column is formatted to show an export
name along with the service program name.
Improving implementation of procedures and functions

These coding techniques help reduce the processing time of a function or procedure.
The following tips are especially important for functions because a function tends to be called multiple
times from many different procedures:
v Use the NOT FENCED option so UDFs run in the same thread as the caller.
v Use the DETERMINISTIC option on procedures and UDFs that return the same results for identical
inputs. This allows the optimizer to cache the results of a function call or order where the function is
called in the execution stream to reduce the run time.
SQL programming
231
v Use the NO EXTERNAL ACTION option on UDFs that do not take an action outside the scope of the
function. An example of an external action is a function that initiates a different process to fulfill a
transaction request.
| The use of pipelined table functions can improve performance in some situations.
| v Avoid the overhead of creating and populating a temporary table by returning the results directly.
| v Return only a subset of the data, rather than all the rows from a query, with the flexibility of
|
combining SQL routine logic with the PIPE statement.
Coding techniques used for the SQL routine body can have a major impact on the runtime performance
of the generated C program. By writing your routine to allow greater use of C code for assignments and
comparisons, the overhead of an equivalent SQL statement is avoided. The following tips should help
your routine generate more C code and fewer SQL statements.
v Declare host variables as NOT NULL when possible. This saves the generated code from having to
check and set the null value flags. Do not automatically set all variables to NOT NULL. When you
specify NOT NULL, you need to also give a default value. If a variable is always used in the routine, a
default value might help. However, if a variable is not always used, having a default value set may
cause additional initialization overhead that is not needed. A default value is best for numeric values,
where an additional database call to process the assignment of the default value is not needed.
v Avoid character and date data types when possible. An example of this is a variable used as a flag
with a value of 0, 1, 2, or 3. If this value is declared as a single character variable instead of an integer,
it causes calls to the database engine that can be avoided.
v Use integer instead of decimal with zero scale, especially when the variable is used as a counter.
v Do not use temporary variables. Look at the following example:
IF M_days<=30 THEN
SET I = M_days-7;
SET J = 23
RETURN decimal(M_week_1 + ((M_month_1 - M_week_1)*I)/J,16,7);
END IF
This example can be rewritten without the temporary variables:

IF M_days<=30 THEN
Return decimal(M-week_1 + ((M_month_1 - M_week_1)* (M_days-7))/23,16,7);
END IF
v Combine sequences of complex SET statements into one statement. This applies to statements where C
code only cannot be generated because of CCSIDS or data types.
SET var1 = function1(var2);
SET var2 = function2();
Can be rewritten into one statement:

SET var1 = function1(var2), var2 = function2();
| v Simple array element assignments can be implemented in C code when only one assignment is
|
performed in a SET statement.
|
SET array_var[1] = 10, array_var[2] = 20;
|
|
|
Should be rewritten as:

SET array_var[1] = 10;
SET array_var[2] = 20;
v Use IF () ELSE IF () ... ELSE ... constructs instead of IF (x AND y) to avoid unnecessary comparisons.
v Do as much in SELECT statements as possible:
SELECT A INTO Y FROM B;
SET Y=Y||X;
Rewrite this example:
232
SELECT A || X INTO Y FROM B
v Avoid doing character or date comparisons inside of loops when not necessary. In some cases the loop
can be rewritten to move a comparison to precede the loop and have the comparison set an integer
variable that is used within the loop. This causes the complex expression to be evaluated only one
time. An integer comparison within the loop is more efficient since it can be done with generated C
code.
v Avoid setting variables that might not be used. For example, if a variable is set outside of the an IF
statement, be sure that the variable will actually be used in all instances of the IF statement. If not,
then set the variable only in the portion of the IF statement that is it actually used.
v Replace sections of code with a single SELECT statement when possible. Look at the following code
snippet:
SET vnb_decimal = 4;
cdecimal:
FOR vdec AS cdec CURSOR FOR
SELECT nb_decimal
FROM K$FX_RULES
WHERE first_currency=Pi_curl AND second_currency=P1_cur2
DO
SET vnb_decimal=SMALLINT(cdecimal.nb_decimal);
END FOR cdecimal;
IF vnb_decimal IS NULL THEN
SET vnb_decimal=4;
END IF;
SET vrate=ROUND(vrate1/vrate2,vnb_decimal);
RETURN vrate;
This code snippet can be more efficient if rewritten in the following way:
RETURN( SELECT
CASE
WHEN MIN(nb_decimal) IS NULL THEN ROUND(Vrate1/Vrate2,4)
ELSE ROUND(Vrate1/Vrate2,SMALLINT(MIN(nb_decimal)))
END
FROM K$FX_RULES
WHERE first_currency=Pi_curl AND second_currency=Pi_cur2);
v C code can only be used for assignments and comparisons of character data if the CCSIDs of both
operands are the same, if one of the CCSIDs is 65535, if the CCSID is not UTF8, and if truncation of
character data is not possible. If the CCSID of the variable is not specified, the CCSID is not
determined until the procedure is called. In this case, code must be generated to determine and
compare the CCSID at runtime. If an alternate collating sequence is specified or if *JOBRUN is
specified, C code cannot be generated for character comparisons.
v Use the same data type, length and scale for numeric variables that are used together in assignments.
C code can only be generated if truncation is not possible.
DECLARE v1, v2 INT;
SET v1 = 100;
SET v1 = v2;
|
|
|
|
|
|
v Using identical attributes to set or retrieve array elements may result in the generation of C code for
integer, character, varchar, decimal, and numeric types. Character variables that require CCSID
processing can require an SQL SET statement to be generated.
v Comparisons using array elements are never generated in C. Some comparisons could result in better
performance if the element value is assigned to a local variable first that can be used in the
comparison.
Redesigning routines for performance

Even if you follow all of the implementation tips, a procedure or function still might not perform well. In
this case, you need to look at the design of the procedure or user-defined function (UDF) and see
whether there are any changes that can be made to improve the performance.
SQL programming
233
Here are the different types of design changes that you can look at.
The first change is to reduce the number of database calls or function calls that a procedure makes, a
process similar to looking for blocks of code that can be converted to SQL statements. Many times you
can reduce the number of calls by adding additional logic to your code.
A more difficult design change is to restructure a whole function to get the same result a different way.
For example, your function uses a SELECT statement to find a route that meets a particular set of criteria
and then executes that statement dynamically. By looking at the work that the function is performing,
you might be able to change the logic so that the function can use a static SELECT query to find the
answer, thereby improving your performance.
You should also use nested compound statements to localize exception handling and cursors. If several
specific handlers are specified, code is generated to check to see if the error occurred after each statement.
Code is also generated to close cursors and process savepoints if an error occurs in a compound
statement. In routines with a single compound statement with multiple handlers and multiple cursors,
code is generated to process each handler and cursor after every SQL statement. If you scope the
handlers and cursors to a nested compound statement, the handlers and cursors are only checked within
the nested compound statement.
In the following routine, code to check the SQLSTATE '22H11' error will only be generated for the
statements within the lab2 compound statement. Specific checking for this error will not be done for any
statements in the routine outside of the lab2 block. Code to check the SQLEXCEPTION error will be
generated for all statements in both the lab1 and lab2 blocks. Likewise, error handling for closing cursor
c1 will be limited to the statements in the lab2 block.
Lab1: BEGIN
DECLARE var1 INT;
DECLARE EXIT HANDLER FOR SQLEXCEPTION
RETURN -3;
lab2: BEGIN
DECLARE EXIT HANDLER FOR SQLSTATE 22H11
RETURN -1;
DECLARE c1 CURSOR FOR SELECT col1 FROM table1;
OPEN c1;
CLOSE c1;
END lab2;
END Lab1
Because redesigning a whole routine takes a lot of effort, examine routines that are showing up as key
performance bottlenecks rather than looking at the application as a whole. More important than
redesigning existing performance bottlenecks is to spend time during the design of the application
thinking about the performance impacts of the design. Focusing on areas of the application that are
expected to be high use areas and making sure that they are designed with performance in mind saves
you from having to do a redesign of those areas later.
Processing special data types

Most data types, such as INTEGER and CHARACTER, do not have any special processing characteristics.
However, a few data types require special functions or locators to use them effectively.
Large objects
A large object (LOB) is a string data type with a size ranging from 0 bytes to 2 GB (GB equals 1 073 741
824 bytes).
The VARCHAR, VARGRAPHIC, and VARBINARY data types have a limit of 32 KB (where KB equals
1024 bytes) of storage. While this might be sufficient for small to medium-sized text data, applications
234
often need to store large text documents. They might also need to store a wide variety of additional data
types, such as audio, video, drawings, mixed text and graphics, and images. Some data types can store
these data objects as strings of up to 2 GB.
These data types are binary large objects (BLOBs), single-byte character large objects (CLOBs), and
double-byte character large objects (DBCLOBs). Each table can have a large amount of associated LOB
data. Although a single row that contains one or more LOB values cannot exceed 3.5 GB, a table can
contain nearly 256 GB of LOB data.
You can refer to and manipulate LOBs using host variables as you do any other data type. However, host
variables use the program's storage that might not be large enough to hold LOB values, so you might
need to manipulate large values in other ways. Locators are useful for identifying and manipulating a
large object value at the database server and for extracting pieces of the LOB value. File reference variables
are useful for physically moving a large object value (or a large part of it) to and from the client.
Large object data types

Here are the definitions of binary large objects (BLOBs), character large objects (CLOBs), and double-byte
character large objects (DBCLOBs).
v Binary large objects (BLOBs) A binary string made up of bytes with no associated code page. This
data type can store binary data larger than VARBINARY (32K limit). This data type is good for storing
image, voice, graphical, and other types of business or application-specific data.
v Character large objects (CLOBs) A character string made up of single-byte characters with an
associated code page. This data type is appropriate for storing text-oriented information where the
amount of information can grow beyond the limits of a regular VARCHAR data type (upper limit of
32K bytes). Code page conversion of the information is supported.
v Double-byte character large objects (DBCLOBs) A character string made up of double-byte
characters with an associated code page. This data type is appropriate for storing text-oriented
information where double-byte character sets are used. Again, code page conversion of the information
is supported.
Large object locators

A large object (LOB) locator is a small, easily managed value that is used to refer to a much larger value.
Specifically, a LOB locator is a 4-byte value stored in a host variable that a program uses to refer to a
LOB value held in the database server. Using a LOB locator, a program can manipulate the LOB value as
if it were stored in a regular host variable. When you use the LOB locator, there is no need to transport
the LOB value from the server to the application (and possibly back again).
The LOB locator is associated with a LOB value, not a row or physical storage location in the database.
Therefore, after selecting a LOB value into a locator, you cannot perform an operation on the original
row(s) or table(s) that have any effect on the value referenced by the locator. The value associated with
the locator is valid until the unit of work ends, or the locator is explicitly freed, whichever comes first.
The FREE LOCATOR statement releases a locator from its associated value. In a similar way, a commit or
rollback operation frees all LOB locators associated with the transaction.
LOB locators can also be passed to and returned from UDFs. Within the UDF, those functions that work
on LOB data can be used to manipulate the LOB values using LOB locators.
When selecting a LOB value, you have three options.
v Select the entire LOB value into a host variable. The entire LOB value is copied into the host variable.
v Select the LOB value into a LOB locator. The LOB value remains on the server; it is not copied to the
host variable.
v Select the entire LOB value into a file reference variable. The LOB value is moved to an integrated file
system file.
SQL programming
235
How a LOB value is used within the program can help the programmer to determine which method is
best. If the LOB value is very large and is needed only as an input value for one or more subsequent SQL
statements, keep the value in a locator.
If the program needs the entire LOB value regardless of the size, then there is no choice but to transfer
the LOB. Even in this case, there are still options available to you. You can select the entire value into a
regular or file reference host variable. You may also select the LOB value into a locator and read it
piecemeal from the locator into a regular host variable.
Related reference:
LOB file reference variables on page 239
File reference variables are similar to host variables except that they are used to transfer data to and from
integrated file system files (not to and from memory buffers).
Example: Using a locator to work with a CLOB value
Suppose that you want your application program to retrieve a locator for a character large object (CLOB)
value and then use the locator to extract data from the CLOB value.
Example: Using a locator to work with a CLOB value

Suppose that you want your application program to retrieve a locator for a character large object (CLOB)
value and then use the locator to extract data from the CLOB value.
Using this method, the program allocates only enough storage for one piece of CLOB data (the size is
determined by the program). In addition, the program needs to issue only one fetch call using the cursor.
How the example LOBLOC program works

The example program has three sections that work with the CLOB locator variables:
1. Declare host variables. CLOB locator host variables are declared.
2. Fetch the CLOB value into the locator host variable. A CURSOR and FETCH routine is used to
obtain the location of a CLOB field in the database to a locator host variable.
3. Free the CLOB locators. The CLOB locators used in this example are freed, releasing the locators
from their previously associated values.
Related concepts:
Large object locators on page 235
Example: LOBLOC in C:
This example program, written in C, uses a locator to retrieve a CLOB value.
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
int main(int argc, char *argv[]) {
char number[7];
long deptInfoBeginLoc;
long deptInfoEndLoc;
SQL TYPE IS CLOB_LOCATOR resume;
[1]
SQL TYPE IS CLOB_LOCATOR deptBuffer;
short lobind;
236
char buffer[1000]="";
char userid[9];
char passwd[19];
printf( "Sample C program: LOBLOC\n" );
if (argc == 1) {
EXEC SQL CONNECT TO sample;
}
else if (argc == 3) {
strcpy (userid, argv[1]);
strcpy (passwd, argv[2]);
EXEC SQL CONNECT TO sample USER :userid USING :passwd;
}
else {
printf ("\nUSAGE: lobloc [userid passwd]\n\n");
return 1;
} /* endif */
/* Employee A10030 is not included in the following select, because
the lobeval program manipulates the record for A10030 so that it is
not compatible with lobloc */
EXEC SQL DECLARE c1 CURSOR FOR
SELECT empno, resume FROM emp_resume WHERE resume_format=ascii
AND empno <> A00130;
EXEC SQL OPEN c1;
do {
EXEC SQL FETCH c1 INTO :number, :resume :lobind; [2]
if (SQLCODE != 0) break;
if (lobind < 0) {
printf ("NULL LOB indicated\n");
} else {
/* EVALUATE the LOB LOCATOR */
/* Locate the beginning of "Department Information" section */
EXEC SQL VALUES (POSSTR(:resume, Department Information))
INTO :deptInfoBeginLoc;
/* Locate the beginning of "Education" section (end of "Dept.Info" */
EXEC SQL VALUES (POSSTR(:resume, Education))
INTO :deptInfoEndLoc;
/* Obtain ONLY the "Department Information" section by using SUBSTR */
EXEC SQL VALUES(SUBSTR(:resume, :deptInfoBeginLoc,
:deptInfoEndLoc - :deptInfoBeginLoc)) INTO :deptBuffer;
/* Append the "Department Information" section to the :buffer var. */
EXEC SQL VALUES(:buffer || :deptBuffer) INTO :buffer;
} /* endif */
} while ( 1 );
printf ("%s\n",buffer);
EXEC SQL FREE LOCATOR :resume, :deptBuffer; [3]
EXEC SQL CLOSE c1;
EXEC SQL CONNECT RESET;
return 0;
}
/* end of program : LOBLOC */
SQL programming
237
Example: LOBLOC in COBOL:

This example program, written in COBOL, uses a locator to retrieve a CLOB value.
Identification Division.
Program-ID. "lobloc".
Data Division.
Working-Storage Section.
EXEC SQL INCLUDE SQLCA END-EXEC.
EXEC SQL BEGIN DECLARE SECTION END-EXEC.
01 userid
pic x(8).
01 passwd.
49 passwd-length
pic s9(4) comp-5 value 0.
49 passwd-name
pic x(18).
01 empnum
pic x(6).
01 di-begin-loc
pic s9(9) comp-5.
01 di-end-loc
pic s9(9) comp-5.
01 resume
USAGE IS SQL TYPE IS CLOB-LOCATOR.
01 di-buffer
USAGE IS SQL TYPE IS CLOB-LOCATOR.
01 lobind
pic s9(4) comp-5.
01 buffer
USAGE IS SQL TYPE IS CLOB(1K).
EXEC SQL END DECLARE SECTION END-EXEC.
[1]
Procedure Division.
Main Section.
display "Sample COBOL program: LOBLOC".
* Get database connection information.
display "Enter your user id (default none): "
with no advancing.
accept userid.
if userid = spaces
EXEC SQL CONNECT TO sample END-EXEC
else
display "Enter your password : " with no advancing
accept passwd-name.
* Passwords in a CONNECT
* format with the length
inspect passwd-name
before initial "
statement must be entered in a VARCHAR

of the input string.
tallying passwd-length for characters
".
EXEC SQL CONNECT TO sample USER :userid USING :passwd

END-EXEC.
* Employee A10030 is not included in the following select, because
* the lobeval program manipulates the record for A10030 so that it is
* not compatible with lobloc
EXEC SQL DECLARE c1 CURSOR FOR
SELECT empno, resume FROM emp_resume
WHERE resume_format = ascii
AND empno <> A00130 END-EXEC.
EXEC SQL OPEN c1 END-EXEC.
Move 0 to buffer-length.
perform Fetch-Loop thru End-Fetch-Loop
until SQLCODE not equal 0.
238
* display contents of the buffer.

display buffer-data(1:buffer-length).
EXEC SQL FREE LOCATOR :resume, :di-buffer END-EXEC.
[3]
EXEC SQL CLOSE c1 END-EXEC.

EXEC SQL CONNECT RESET END-EXEC.
End-Main.
go to End-Prog.
Fetch-Loop Section.
EXEC SQL FETCH c1 INTO :empnum, :resume :lobind
END-EXEC.
[2]
if SQLCODE not equal 0

go to End-Fetch-Loop.
* check to see if the host variable indicator returns NULL.
if lobind less than 0 go to NULL-lob-indicated.
* Value exists. Evaluate the LOB locator.
* Locate the beginning of "Department Information" section.
EXEC SQL VALUES (POSSTR(:resume, Department Information))
INTO :di-begin-loc END-EXEC.
* Locate the beginning of "Education" section (end of Dept.Info)
EXEC SQL VALUES (POSSTR(:resume, Education))
INTO :di-end-loc END-EXEC.
subtract di-begin-loc from di-end-loc.
* Obtain ONLY the "Department Information" section by using SUBSTR
EXEC SQL VALUES (SUBSTR(:resume, :di-begin-loc,
:di-end-loc))
INTO :di-buffer END-EXEC.
* Append the "Department Information" section to the :buffer var
EXEC SQL VALUES (:buffer || :di-buffer) INTO :buffer
END-EXEC.
go to End-Fetch-Loop.
NULL-lob-indicated.
display "NULL LOB indicated".
End-Fetch-Loop. exit.
End-Prog.
stop run.
Indicator variables and LOB locators

For normal host variables in an application program, when selecting a NULL value into a host variable, a
negative value is assigned to the indicator variable signifying that the value is NULL. In the case of LOB
locators, however, the meaning of indicator variables is slightly different.
Since a locator host variable itself can never be NULL, a negative indicator variable value indicates that
the LOB value represented by the LOB locator is NULL. The NULL information is kept local to the client
using the indicator variable value. The server does not track NULL values with valid locators.
LOB file reference variables

File reference variables are similar to host variables except that they are used to transfer data to and from
integrated file system files (not to and from memory buffers).
SQL programming
239
A file reference variable represents (rather than contains) the file, just as a LOB locator represents (rather
than contains) the LOB value. Database queries, updates, and inserts may use file reference variables to
store, or to retrieve, single LOB values.
For very large objects, files are natural containers. It is likely that most LOBs begin as data stored in files
on the client before they are moved to the database on the server. The use of file reference variables helps
move LOB data. Programs use file reference variables to transfer LOB data from the integrated file
system file directly to the database engine. To carry out the movement of LOB data, the application does
not need to write utility routines to read and write files using host variables.
Note: The file referenced by the file reference variable must be accessible from (but not necessarily
resident on) the system on which the program runs. For a stored procedure, this is the server.
A file reference variable has a data type of BLOB, CLOB, or DBCLOB. It is used either as the source of
data (input) or as the target of data (output). The file reference variable may have a relative file name or
a complete path name of the file (the latter is advised). The file name length is specified within the
application program. The data length portion of the file reference variable is unused during input. During
output, the data length is set by the application requester code to the length of the new data that is
written to the file.
When using file reference variables there are different options on both input and output. You must choose
an action for the file by setting the file_options field in the file reference variable structure. Choices for
assignment to the field covering both input and output values are shown below.
Values (shown for C) and options when using input file reference variables are as follows:
v SQL_FILE_READ (Regular file) This option has a value of 2. This is a file that can be open, read,
and closed. DB2 determines the length of the data in the file (in bytes) when opening the file. DB2 then
returns the length through the data_length field of the file reference variable structure. The value for
COBOL is SQL-FILE-READ.
Values and options when using output file reference variables are as follows:
v SQL_FILE_CREATE (New file) This option has a value of 8. This option creates a new file. Should
the file already exist, an error message is returned. The value for COBOL is SQL-FILE-CREATE.
v SQL_FILE_OVERWRITE (Overwrite file) This option has a value of 16. This option creates a new
file if none already exists. If the file already exists, the new data overwrites the data in the file. The
value for COBOL is SQL-FILE-OVERWRITE.
v SQL_FILE_APPEND (Append file) This option has a value of 32. This option has the output
appended to the file, if it exists. Otherwise, it creates a new file. The value for COBOL is
SQL-FILE-APPEND.
Note: If a LOB file reference variable is used in an OPEN statement, do not delete the file associated with
the LOB file reference variable until the cursor is closed.
Related concepts:
Large object locators on page 235
Integrated file system
Example: Extracting CLOB data to a file

Suppose that you need to retrieve character large object (CLOB) elements from a table into an external
file.
How the example LOBFILE program works

The example program has three sections that work with the CLOB file reference variable:
240
1. Declare host variables. A CLOB file reference host variable is declared. The declaration is expanded
as a structure that includes declarations for a file name, file name length, and file options.
2. CLOB file reference host variable is set up. The attributes of the file reference are set up. A file name
without a fully declared path is, by default, placed in the user's current directory. If the path name
does not begin with the forward slash (/) character, it is not qualified.
3. Select into the CLOB file reference host variable. The data from the resume field is selected into the
file name that is referenced by the host variable.
Example: LOBFILE in C:
This example program, written in C, extracts CLOB data from a table to an external file.
#include
#include
#include
#include
<stdio.h>
<stdlib.h>
<string.h>
<sql.h>

int main(int argc, char *argv[]) {
SQL TYPE IS CLOB_FILE resume;
short lobind;
char userid[9];
char passwd[19];
[1]
printf( "Sample C program: LOBFILE\n" );

if (argc == 1) {
EXEC SQL CONNECT TO sample;
else if (argc == 3) {
strcpy (userid, argv[1]);
strcpy (passwd, argv[2]);
EXEC SQL CONNECT TO sample USER :userid USING :passwd;
else {
printf ("\nUSAGE: lobfile [userid passwd]\n\n");
return 1;
} /* endif */
strcpy (resume.name, "RESUME.TXT");
resume.name_length = strlen("RESUME.TXT");
resume.file_options = SQL_FILE_OVERWRITE;
[2]
EXEC SQL SELECT resume INTO :resume :lobind FROM emp_resume [3]
WHERE resume_format=ascii AND empno=000130;
if (lobind < 0) {
printf ("NULL LOB indicated \n");
} else {
printf ("Resume for EMPNO 000130 is in file : RESUME.TXT\n");
} /* endif */
EXEC SQL CONNECT RESET;
return 0;
}
/* end of program : LOBFILE */
SQL programming
241
Example: LOBFILE in COBOL:

This example program, written in COBOL, extracts CLOB data from a table to an external file.
Identification Division.
Program-ID. "lobfile".
Data Division.
Working-Storage Section.
EXEC SQL INCLUDE SQLCA END-EXEC.
EXEC SQL BEGIN DECLARE SECTION END-EXEC.
01 userid
pic x(8).
01 passwd.
49 passwd-length
pic s9(4) comp-5 value 0.
49 passwd-name
pic x(18).
01 resume
USAGE IS SQL TYPE IS CLOB-FILE.
01 lobind
pic s9(4) comp-5.
EXEC SQL END DECLARE SECTION END-EXEC.
[1]
Procedure Division.
Main Section.
display "Sample COBOL program: LOBFILE".
* Get database connection information.
display "Enter your user id (default none): "
with no advancing.
accept userid.
if userid = spaces
EXEC SQL CONNECT TO sample END-EXEC
else
display "Enter your password : " with no advancing
accept passwd-name.
* Passwords in a CONNECT
* format with the length
inspect passwd-name
before initial "
statement must be entered in a VARCHAR

of the input string.
tallying passwd-length for characters
".
EXEC SQL CONNECT TO sample USER :userid USING :passwd

END-EXEC.
move "RESUME.TXT" to resume-NAME.
move 10 to resume-NAME-LENGTH.
move SQL-FILE-OVERWRITE to resume-FILE-OPTIONS.
[2]
EXEC SQL SELECT resume INTO :resume :lobind

[3]
FROM emp_resume
WHERE resume_format = ascii
AND empno = 000130 END-EXEC.
if lobind less than 0 go to NULL-LOB-indicated.
display "Resume for EMPNO 000130 is in file : RESUME.TXT".
go to End-Main.
NULL-LOB-indicated.
display "NULL LOB indicated".
End-Main.
EXEC SQL CONNECT RESET END-EXEC.
End-Prog.
stop run.
242
Example: Inserting data into a CLOB column

This example shows how to insert data from a regular file referenced by :hv_text_file into a character
large object (CLOB) column.
In the path description of the following C program segment:
v userid represents the directory for one of your users.
v dirname represents a subdirectory name of userid.
v filnam.1 can become the name of one of your documents that you want to insert into the table.
v clobtab is the name of the table with the CLOB data type.
strcpy(hv_text_file.name, "/home/userid/dirname/filnam.1");
hv_text_file.name_length = strlen("/home/userid/dirname/filnam.1");
hv_text_file.file_options = SQL_FILE_READ; /* this is a regular file */
EXEC SQL INSERT INTO CLOBTAB
VALUES(:hv_text_file);
Displaying the layout of LOB columns

When you use CL commands, such as Display Physical File Member (DSPPFM), to display a row of data
from a table that holds large object (LOB) columns, the LOB data stored in the row is not displayed.
Instead, the database shows a special value for the LOB columns.
The layout of this special value is as follows:
v 13 to 28 bytes of hexadecimal zeros.
v 16 bytes beginning with *POINTER and followed by blanks.
The number of bytes in the first portion of the value is set to the number needed to 16 byte boundary
align the second part of the value.
For example, say you have a table that holds three columns: ColumnOne Char(10), ColumnTwo
CLOB(40K), and ColumnThree BLOB(10M). If you were to issue a DSPPFM of this table, each row of data
looks as follows.
v For ColumnOne: 10 bytes filled with character data.
v For ColumnTwo: 22 bytes filled with hexadecimal zeros and 16 bytes filled with '*POINTER '.
v For ColumnThree: 16 bytes filled with hexadecimal zeros and 16 bytes filled with '*POINTER '.
The full set of commands that display LOB columns in this way is:
v Display Physical File Member (DSPPFM)
v Copy File (CPYF) when the value *PRINT is specified for the TOFILE keyword
v Display Journal (DSPJRN)
v Retrieve Journal Entry (RTVJRNE)
v Receive Journal Entry (RCVJRNE) when the values *TYPE1, *TYPE2, *TYPE3 and *TYPE4 are specified
for the ENTFMT keyword.
Journal entry layout of LOB columns

These commands return a buffer that gives the user addressability to the large object (LOB) data that has
been journaled.
v Receive Journal Entry (RCVJRNE) CL command, when the value *TYPEPTR is specified for the
ENTFMT keyword
v Retrieve Journal Entries (QjoRetrieveJournalEntries) API
The layout of the LOB columns in these entries is as follows:
v 0 to 15 bytes of hex zeros
SQL programming
243
v
v
v
v
1 byte of system information set to '00'x

4 bytes holding the length of the LOB data addressed by the pointer, below
8 bytes of hex zeros
16 bytes holding a pointer to the LOB data stored in the Journal Entry.
The first part of this layout is intended to 16 byte boundary align the pointer to the LOB data. The
number of bytes in this area depends on the length of the columns that proceed the LOB column. Refer
to the section above on the Display Layout of LOB Columns for an example of how the length of this
first part is calculated.
User-defined distinct types

A user-defined distinct type (UDT) is a mechanism to extend DB2 capabilities beyond the built-in data
types that are available.
User-defined distinct types enable you to define new data types to DB2, which gives you considerable
power because you are no longer restricted to using the system-supplied built-in data types to model
your business and capture the semantics of your data. Distinct data types allow you to map on a
one-to-one basis to existing database types.
These benefits are associated with UDTs:
v Extensibility.
By defining new types, you can indefinitely increase the set of types provided by DB2 to support your
applications.
v Flexibility.
You can specify any semantics and behavior for your new type by using user-defined functions (UDFs)
to augment the diversity of the types available in the system.
v Consistent behavior.
Strong typing ensures that your UDTs will behave appropriately. It guarantees that only functions
defined on your UDT can be applied to instances of the UDT.
v Encapsulation.
The behavior of your UDTs is restricted by the functions and operators that can be applied on them.
This provides flexibility in the implementation since running applications do not depend on the
internal representation that you chose for your type.
v Extensible behavior.
The definition of user-defined functions on types can augment the functionality provided to
manipulate your UDT at any time.
v Foundation for object-oriented extensions.
UDTs are the foundation for most object-oriented features. They represent the most important step
toward object-oriented extensions.
Related concepts:
User-defined types on page 13
A user-defined type is a data type that you can define independently of the data types that are provided by
the database management system.
Defining a UDT
You define a user-defined type (UDT) using the CREATE DISTINCT TYPE statement.
For the CREATE DISTINCT TYPE statement, note that:
1. The name of the new UDT can be a qualified or an unqualified name.
244
2. The source type of the UDT is the type used by the system to internally represent the UDT. For this
reason, it must be a built-in data type. Previously defined UDTs cannot be used as source types of
other UDTs.
As part of a UDT definition, the system always generates cast functions to:
v Cast from the UDT to the source type, using the standard name of the source type. For example, if you
create a distinct type based on FLOAT, the cast function called DOUBLE is created.
v Cast from the source type to the UDT.
These functions are important for the manipulation of UDTs in queries.
The function path is used to resolve any references to an unqualified type name or function, except if the
type name or function is the main object of a CREATE, DROP, or COMMENT ON statement.
Related reference:
Using qualified function references on page 214
schema.
CREATE TYPE
Example: Money:
Suppose that you are writing applications that handle different currencies and want to ensure that DB2
does not allow these currencies to be compared or manipulated directly with one another in queries.
Remember that conversions are necessary whenever you want to compare values of different currencies.
So you define as many UDTs as you need; one for each currency that you may need to represent:
CREATE DISTINCT TYPE US_DOLLAR AS DECIMAL (9,2)
CREATE DISTINCT TYPE CANADIAN_DOLLAR AS DECIMAL (9,2)
CREATE DISTINCT TYPE EURO AS DECIMAL (9,2)
Example: Resum:
Suppose that you want to keep the application forms that are filled out by applicants to your company in
a table, and that you are going to use functions to extract information from these forms.
Because these functions cannot be applied to regular character strings (because they are certainly not able
to find the information they are supposed to return), you define a UDT to represent the filled forms:
CREATE DISTINCT TYPE PERSONAL.APPLICATION_FORM AS CLOB(32K)
Defining tables with UDTs

After you have defined several user-defined types (UDTs), you can start defining tables with columns
whose types are UDTs.
Example: Sales:
Suppose that you want to define tables to keep your company's sales in different countries.
You create the tables as follows:
CREATE TABLE US_SALES
(PRODUCT_ITEM INTEGER,
MONTH
INTEGER CHECK (MONTH BETWEEN 1 AND 12),
YEAR
INTEGER CHECK (YEAR > 1985),
TOTAL
US_DOLLAR)
CREATE TABLE CANADIAN_SALES
SQL programming
245
MONTH
YEAR
TOTAL

CANADIAN_DOLLAR)
CREATE TABLE GERMAN_SALES

MONTH
YEAR
TOTAL
EURO)
The UDTs in the preceding examples are created with the same CREATE DISTINCT TYPE statements in
Example: Money on page 245. Note that the preceding examples use check constraints.
Example: Application forms:
Suppose that you need to define a table to keep the forms that are filled out by applicants.
Create the table as follows:
CREATE TABLE APPLICATIONS
(ID
INTEGER,
NAME
VARCHAR (30),
APPLICATION_DATE DATE,
FORM
PERSONAL.APPLICATION_FORM)
You have fully qualified the UDT name because its qualifier is not the same as your authorization ID and
you have not changed the default function path. Remember that whenever type and function names are
not fully qualified, DB2 searches through the schemas listed in the current function path and looks for a
type or function name matching the given unqualified name.
Manipulating UDTs
Strong typing is an important concept associated with user-defined types (UDTs). Strong typing
guarantees that only functions and operators defined on a UDT can be applied to its instances.
Strong typing is important to ensure that the instances of your UDTs are correct. For example, if you
have defined a function to convert US dollars to Canadian dollars according to the current exchange rate,
you do not want this same function to be used to convert Euros to Canadian dollars because it will
certainly return the wrong amount.
As a consequence of strong typing, DB2 does not allow you to write queries that compare, for example,
UDT instances with instances of the UDT source type. For the same reason, DB2 will not let you apply
functions defined on other types to UDTs. If you want to compare instances of UDTs with instances of
another type, you need to cast the instances of one or the other type. In the same sense, you need to cast
the UDT instance to the type of the parameter of a function that is not defined on a UDT if you want to
apply this function to a UDT instance.
Examples: Using UDTs

These examples show the use of user-defined types (UDTs) in various situations.
Example: Comparisons between UDTs and constants:
Suppose that you want to know which products had total sales of over US $100 000.00 in the U.S. in the
month of July 1998.
SELECT PRODUCT_ITEM
FROM
US_SALES
WHERE TOTAL > US_DOLLAR (100000)
AND
month = 7
AND
year = 1998
246
Because you cannot compare U.S. dollars with instances of the source type of U.S. dollars (that is,
DECIMAL) directly, you have used the cast function provided by DB2 to cast from DECIMAL to U.S.
dollars. You can also use the other cast function provided by DB2 (that is, the one to cast from U.S.
dollars to DECIMAL) and cast the column total to DECIMAL. Either way you decide to cast, from or to
the UDT, you can use the cast specification notation to perform the casting, or the functional notation.
You might have written the above query as:
SELECT PRODUCT_ITEM
FROM
US_SALES
WHERE TOTAL > CAST (100000 AS us_dollar)
AND
MONTH = 7
AND
YEAR = 1998
Example: Casting between UDTs:

Suppose that you want to define a user-defined function (UDF) that converts Canadian dollars to U.S.
dollars.
You can obtain the current exchange rate from a file managed outside of DB2. Then define a UDF that
obtains a value in Canadian dollars, accesses the exchange rate file, and returns the corresponding
amount in U.S. dollars.
At first glance, such a UDF may appear easy to write. However, not all C compilers support DECIMAL
values. The UDTs representing different currencies have been defined as DECIMAL. Your UDF will need
to receive and return DOUBLE values, since this is the only data type provided by C that allows the
representation of a DECIMAL value without losing the decimal precision. Your UDF should be defined as
follows:
CREATE FUNCTION CDN_TO_US_DOUBLE(DOUBLE) RETURNS DOUBLE
EXTERNAL NAME MYLIB/CURRENCIES(C_CDN_US)
LANGUAGE C
NO SQL
NOT DETERMINISTIC
The exchange rate between Canadian and U.S. dollars may change between two invocations of the UDF,
so you declare it as NOT DETERMINISTIC.
The question now is, how do you pass Canadian dollars to this UDF and get U.S. dollars from it? The
Canadian dollars must be cast to DECIMAL values. The DECIMAL values must be cast to DOUBLE. You
also need to have the returned DOUBLE value cast to DECIMAL and the DECIMAL value cast to U.S.
dollars.
Such casts are performed automatically by DB2 anytime you define sourced UDFs, whose parameter and
return type do not exactly match the parameter and return type of the source function. Therefore, you
need to define two sourced UDFs. The first brings the DOUBLE values to a DECIMAL representation.
The second brings the DECIMAL values to the UDT. Define the following:
CREATE FUNCTION CDN_TO_US_DEC (DECIMAL(9,2)) RETURNS DECIMAL(9,2)
SOURCE CDN_TO_US_DOUBLE (DOUBLE)
CREATE FUNCTION US_DOLLAR (CANADIAN_DOLLAR) RETURNS US_DOLLAR
SOURCE CDN_TO_US_DEC (DECIMAL())
Note that an invocation of the US_DOLLAR function as in US_DOLLAR(C1), where C1 is a column whose type
is Canadian dollars, has the same effect as invoking:
US_DOLLAR (DECIMAL(CDN_TO_US_DOUBLE (DOUBLE (DECIMAL (C1)))))
That is, C1 (in Canadian dollars) is cast to decimal which in turn is cast to a double value that is passed
to the CDN_TO_US_DOUBLE function. This function accesses the exchange rate file and returns a double value
(representing the amount in U.S. dollars) that is cast to decimal, and then to U.S. dollars.
SQL programming
247
A function to convert Euros to U.S. dollars is similar to the example above:

CREATE FUNCTION EURO_TO_US_DOUBLE(DOUBLE)
RETURNS DOUBLE
EXTERNAL NAME MYLIB/CURRENCIES(C_EURO_US)
LANGUAGE C
NO SQL
NOT DETERMINISTIC
CREATE FUNCTION EURO_TO_US_DEC (DECIMAL(9,2))
RETURNS DECIMAL(9,2)
SOURCE EURO_TO_US_DOUBLE(DOUBLE)
CREATE FUNCTION US_DOLLAR(EURO) RETURNS US_DOLLAR
SOURCE EURO_TO_US_DEC (DECIMAL())
Example: Comparisons involving UDTs:

Suppose that you want to know which products had higher sales in the U.S. than in Canada and
Germany for the month of March 2003.
Issue the following SELECT statement:
SELECT US.PRODUCT_ITEM, US.TOTAL
FROM US_SALES AS US, CANADIAN_SALES AS CDN, GERMAN_SALES AS GERMAN
WHERE US.PRODUCT_ITEM = CDN.PRODUCT_ITEM
AND US.PRODUCT_ITEM = GERMAN.PRODUCT_ITEM
AND US.TOTAL > US_DOLLAR (CDN.TOTAL)
AND US.TOTAL > US_DOLLAR (GERMAN.TOTAL)
AND US.MONTH = 3
AND US.YEAR = 2003
AND CDN.MONTH = 3
AND CDN.YEAR = 2003
AND GERMAN.MONTH = 3
AND GERMAN.YEAR = 2003
Because you cannot directly compare U.S. dollars with Canadian dollars or Euros, you use the UDF to
cast the amount in Canadian dollars to U.S. dollars, and the UDF to cast the amount in Euros to U.S.
dollars. You cannot cast them all to DECIMAL and compare the converted DECIMAL values because the
amounts are not monetarily comparable as they are not in the same currency.
Example: Sourced UDFs involving UDTs:
Suppose that you have defined a sourced user-defined function (UDF) on the built-in SUM function to
support SUM on Euros.
The function statement is as follows:
CREATE FUNCTION SUM (EURO)
RETURNS EURO
SOURCE SYSIBM.SUM (DECIMAL())
You want to know the total of sales in Germany for each product in the year of 2004. You want to obtain
the total sales in U.S. dollars:
SELECT PRODUCT_ITEM, US_DOLLAR (SUM (TOTAL))
FROM GERMAN_SALES
WHERE YEAR = 2004
GROUP BY PRODUCT_ITEM
You cannot write SUM (US_DOLLAR (TOTAL)), unless you had defined a SUM function on U.S. dollar in a
manner similar to the above.
Related reference:
248
Example: Assignments involving different UDTs

Suppose that you have defined these sourced user-defined functions (UDFs) on the built-in SUM function
to support SUM on U.S. and Canadian dollars.
Example: Assignments involving UDTs:
Suppose that you want to store the form that is filled out by a new applicant into the database.
You have defined a host variable containing the character string value used to represent the filled form:
SQL TYPE IS CLOB(32K) hv_form;
/* Code to fill hv_form */
INSERT INTO APPLICATIONS
VALUES (134523, Peter Holland, CURRENT DATE, :hv_form)
You do not explicitly invoke the cast function to convert the character string to the UDT
personal.application_form. This is because DB2 allows you to assign instances of the source type of a
UDT to targets having that UDT.
Related reference:
Example: Assignments in dynamic SQL
If you want to store the application form using dynamic SQL, you can use parameter markers.
Example: Assignments in dynamic SQL:
If you want to store the application form using dynamic SQL, you can use parameter markers.
The statement is as follows:
long id;
char name[30];
SQL TYPE IS CLOB(32K) form;
char command[80];
/* Code to fill host variables */
strcpy(command,"INSERT INTO APPLICATIONS VALUES");
strcat(command,"(?, ?, CURRENT DATE, ?)");
EXEC SQL PREPARE APP_INSERT FROM :command;
EXEC SQL EXECUTE APP_INSERT USING :id, :name, :form;
You made use of DB2's cast specification to tell DB2 that the type of the parameter marker is CLOB(32K),
a type that is assignable to the UDT column. Remember that you cannot declare a host variable of a UDT
type, since host languages do not support UDTs. Therefore, you cannot specify that the type of a
parameter marker is a UDT.
Related reference:
Example: Assignments involving UDTs
Suppose that you want to store the form that is filled out by a new applicant into the database.
Example: Assignments involving different UDTs:
Suppose that you have defined these sourced user-defined functions (UDFs) on the built-in SUM function
to support SUM on U.S. and Canadian dollars.
SQL programming
249
CREATE FUNCTION SUM (CANADIAN_DOLLAR)

RETURNS CANADIAN_DOLLAR
CREATE FUNCTION SUM (US_DOLLAR)
RETURNS US_DOLLAR
Now suppose your supervisor requests that you maintain the annual total sales in U.S. dollars of each
product and in each country, in separate tables:
CREATE TABLE US_SALES_04
TOTAL
US_DOLLAR)
CREATE TABLE GERMAN_SALES_04
TOTAL
US_DOLLAR)
CREATE TABLE CANADIAN_SALES_04
TOTAL
US_DOLLAR)
INSERT INTO US_SALES_04
SELECT PRODUCT_ITEM, SUM (TOTAL)
FROM US_SALES
WHERE YEAR = 2004
INSERT INTO GERMAN_SALES_04
FROM GERMAN_SALES
WHERE YEAR = 2004
INSERT INTO CANADIAN_SALES_04
FROM CANADIAN_SALES
WHERE YEAR = 2004
You explicitly cast the amounts in Canadian dollars and Euros to U.S. dollars since different UDTs are not
directly assignable to each other. You cannot use the cast specification syntax because UDTs can only be
cast to their own source type.
Related reference:
Example: Sourced UDFs involving UDTs on page 248
Suppose that you have defined a sourced user-defined function (UDF) on the built-in SUM function to
support SUM on Euros.
Example: Using UDTs in UNION:
Suppose that you want to provide your U.S. users with a query to show the sales of every product of
your company.
The SELECT statement is as follows:
SELECT PRODUCT_ITEM, MONTH, YEAR, TOTAL
FROM US_SALES
UNION
SELECT PRODUCT_ITEM, MONTH, YEAR, US_DOLLAR (TOTAL)
250
FROM CANADIAN_SALES
UNION
SELECT PRODUCT_ITEM, MONTH, YEAR, US_DOLLAR (TOTAL)
FROM GERMAN_SALES
You cast Canadian dollars to U.S. dollars and Euros to U.S. dollars because UDTs are union compatible
only with the same UDT. You must use the functional notation to cast between UDTs since the cast
specification only allows you to cast between UDTs and their source types.
Examples: Using UDTs, UDFs, and LOBs

These examples show how to use user-defined types (UDTs), user-defined functions (UDFs), and large
objects (LOBs) together in complex applications.
Example: Defining the UDT and UDFs

Suppose that you want to keep the electronic mail (e-mail) that is sent to your company in a table.
Ignoring any issues of privacy, you plan to write queries over such e-mail to find out their subject, how
often your e-mail service is used to receive customer orders, and so on. E-mail can be quite large, and it
has a complex internal structure (a sender, a receiver, the subject, date, and the e-mail content). Therefore,
you decide to represent the e-mail by means of a UDT whose source type is a large object. You define a
set of UDFs on your e-mail type, such as functions to extract the subject of the e-mail, the sender, the
date, and so on. You also define functions that can perform searches on the content of the e-mail. You do
the above using the following CREATE statements:
CREATE DISTINCT TYPE E_MAIL AS BLOB (1M)
CREATE FUNCTION SUBJECT (E_MAIL)
RETURNS VARCHAR (200)
EXTERNAL NAME LIB/PGM(SUBJECT)
LANGUAGE C
NO SQL
DETERMINISTIC
NO EXTERNAL ACTION
CREATE FUNCTION SENDER (E_MAIL)
EXTERNAL NAME LIB/PGM(SENDER)
LANGUAGE C
NO SQL
DETERMINISTIC
NO EXTERNAL ACTION
CREATE FUNCTION RECEIVER (E_MAIL)
EXTERNAL NAME LIB/PGM(RECEIVER)
LANGUAGE C
NO SQL
DETERMINISTIC
NO EXTERNAL ACTION
CREATE FUNCTION SENDING_DATE (E_MAIL)
RETURNS DATE CAST FROM VARCHAR(10)
EXTERNAL NAME LIB/PGM(SENDING_DATE)
LANGUAGE C
NO SQL
DETERMINISTIC
NO EXTERNAL ACTION
CREATE FUNCTION CONTENTS (E_MAIL)
SQL programming
251
RETURNS BLOB (1M)

EXTERNAL NAME LIB/PGM(CONTENTS)
LANGUAGE C
NO SQL
DETERMINISTIC
NO EXTERNAL ACTION
CREATE FUNCTION CONTAINS (E_MAIL, VARCHAR (200))
RETURNS INTEGER
EXTERNAL NAME LIB/PGM(CONTAINS)
LANGUAGE C
NO SQL
DETERMINISTIC
NO EXTERNAL ACTION
CREATE TABLE ELECTRONIC_MAIL
(ARRIVAL_TIMESTAMP TIMESTAMP,
MESSAGE E_MAIL)
Example: Using the LOB function to populate the database

Suppose that you populate your table by transferring your e-mail that is maintained in files into the DB2
for i database.
Run the following INSERT statement multiple times with different values of the HV_EMAIL_FILE until
you have stored all your e-mail:
EXEC SQL BEGIN DECLARE SECTION
SQL TYPE IS BLOB_FILE HV_EMAIL_FILE;
EXEC SQL END DECLARE SECTION
strcpy (HV_EMAIL_FILE.NAME, "/u/mail/email/mbox");
HV_EMAIL_FILE.NAME_LENGTH = strlen(HV_EMAIL_FILE.NAME);
HV_EMAIL_FILE.FILE_OPTIONS = 2;
EXEC SQL INSERT INTO ELECTRONIC_MAIL
VALUES (CURRENT TIMESTAMP, :hv_email_file);
All the function provided by DB2 LOB support is applicable to UDTs whose source type are LOBs.
Therefore, you have used LOB file reference variables to assign the contents of the file into the UDT
column. You have not used the cast function to convert values of BLOB type into your e-mail type. This
is because DB2 allows you to assign values of the source type of a distinct type to targets of the distinct
type.
Example: Using UDFs to query instances of UDTs

Suppose that you need to know how much e-mail was sent by a specific customer regarding customer
orders and you have the e-mail addresses of your customers in the customers table.
The statement is as follows:
SELECT COUNT (*)
FROM ELECTRONIC_MAIL AS EMAIL, CUSTOMERS
WHERE SUBJECT (EMAIL.MESSAGE) = customer order
AND CUSTOMERS.EMAIL_ADDRESS = SENDER (EMAIL.MESSAGE)
AND CUSTOMERS.NAME = Customer X
You have used the UDFs defined on the UDT in this SQL query since they are the only means to
manipulate the UDT. In this sense, your UDT e-mail is completely encapsulated. Its internal
representation and structure are hidden and can only be manipulated by the defined UDFs. These UDFs
know how to interpret the data without the need to expose its representation.
252
Suppose you need to know the details of all the e-mail your company received in 1994 that had to do
with the performance of your products in the marketplace.
SELECT SENDER (MESSAGE), SENDING_DATE (MESSAGE), SUBJECT (MESSAGE)
FROM ELECTRONIC_MAIL
WHERE CONTAINS (MESSAGE,
"performance" AND "products" AND "marketplace") = 1
You have used the contains UDF that is capable of analyzing the contents of the message searching for
relevant keywords or synonyms.
Example: Using LOB locators to manipulate UDT instances

Suppose that you want to obtain information about specific e-mail without having to transfer the entire
e-mail into a host variable in your application program.
Remember that e-mail can be quite large. Because your user-defined type (UDT) is defined as a large
object (LOB), you can use LOB locators for that purpose:
EXEC SQL BEGIN DECLARE SECTION
long hv_len;
char hv_subject[200];
char hv_sender[200];
char hv_buf[4096];
char hv_current_time[26];
SQL TYPE IS BLOB_LOCATOR hv_email_locator;
EXEC SQL END DECLARE SECTION
EXEC SQL SELECT MESSAGE
INTO :hv_email_locator
FROM ELECTRONIC MAIL
WHERE ARRIVAL_TIMESTAMP = :hv_current_time;
EXEC SQL VALUES (SUBJECT (E_MAIL(:hv_email_locator))
INTO :hv_subject;
.... code that checks if the subject of the e_mail is relevant ....
.... if the e_mail is relevant, then...............................
EXEC SQL VALUES (SENDER (CAST (:hv_email_locator AS E_MAIL)))
INTO :hv_sender;
Because your host variable is of type BLOB locator (the source type of the UDT), you have explicitly
converted the BLOB locator to your UDT, whenever it was used as an argument of a UDF defined on the
UDT.
Using DataLinks
The DataLink data type is one of the basic building blocks for extending the types of data that can be
stored in database files. The idea of a DataLink is that the actual data stored in the column is only a
pointer to the object.
This object can be anything, an image file, a voice recording, a text file, and so on. The method used for
resolving to the object is to store a Uniform Resource Locator (URL). This means that a row in a table can
be used to contain information about the object in traditional data types, and the object itself can be
referenced using the DataLink data type. The user can use SQL scalar functions to get back the path to
the object and the server on which the object is stored (see Built-in functions in the SQL Reference). With
the DataLink data type, there is a fairly loose relationship between the row and the object. For instance,
deleting a row will sever the relationship to the object referenced by the DataLink, but the object itself
might not be deleted.
A table created with a DataLink column can be used to hold information about an object, without
actually containing the object itself. This concept gives the user much more flexibility in the types of data
that can be managed using a table. If, for instance, the user has thousands of video clips stored in the
SQL programming
253
integrated file system of their server, they may want to use an SQL table to contain information about
these video clips. But since the user already has the objects stored in a directory, they only want the SQL
table to contain references to the objects, not the actual bytes of storage. A good solution is to use
DataLinks. The SQL table uses traditional SQL data types to contain information about each clip, such as
title, length, date, and so on. But the clip itself is referenced using a DataLink column. Each row in the
table stores a URL for the object and an optional comment. Then an application that is working with the
clips can retrieve the URL using SQL interfaces, and then use a browser or other playback software to
work with the URL and display the video clip.
There are several advantages of using this technique:
v The integrated file system can store any type of stream file.
v The integrated file system can store extremely large objects, that does not fit into a character column,
or perhaps even a LOB column.
v The hierarchical nature of the integrated file system is well-suited to organizing and working with the
stream file objects.
v By leaving the bytes of the object outside the database and in the integrated file system, applications
can achieve better performance by allowing the SQL runtime engine to handle queries and reports, and
allowing the file system to handle streaming of video, displaying images, text, and so on.
Using DataLinks also gives control over the objects while they are in "linked" status. A DataLink column
can be created such that the referenced object cannot be deleted, moved, or renamed while there is a row
in the SQL table that references that object. This object is considered linked. Once the row containing that
reference is deleted, the object is unlinked. To understand this concept fully, one should know the levels
of control that can be specified when creating a DataLink column.
Related reference:
Data types
Linking control levels in DataLinks

You can create a DataLink column with different link controls.
NO LINK CONTROL:
If a DataLink column is created with NO LINK CONTROL, no linking takes place when rows are added
to the SQL table.
The URL is verified to be syntactically correct, but there is no check to make sure that the server is
accessible, or that the file even exists.
FILE LINK CONTROL with FS permissions:
If a DataLink column is created with FILE LINK CONTROL with file system (FS) permissions, the system
verifies that each DataLink value is a valid URL, with a valid server name and file name.
The file must exist when the row is being inserted into the SQL table. When the object is found, it is
marked as linked. This means that the object cannot be moved, deleted, or renamed during the time it is
linked. Also, an object cannot be linked more than once. If the server name portion of the URL specifies a
remote system, that system must be accessible. If a row that contains a DataLink value is deleted, the
object is unlinked. If a DataLink value is updated to a different value, the old object is unlinked and the
new object is linked.
The integrated file system is still responsible for managing permissions for the linked object. The
permissions are not modified during the link or unlink processes. This option provides control of the
object's existence for the duration of time that it is linked.
254
FILE LINK CONTROL with DB permissions:

If a DataLink column is created with FILE LINK CONTROL with database (DB) permissions, the URL is
verified, and all existing permissions to the object are removed.
The ownership of the object is changed to a special system-supplied user profile. During the time that the
object is linked, the only access to the object is by obtaining the URL from the SQL table that has the
object linked. This is handled by using a special access token that is appended to the URL returned by
SQL. Without the access token, all attempts to access the object will fail with an authority violation. If the
URL with the access token is retrieved from the SQL table by normal means (FETCH, SELECT INTO, and
so on.) the file system filter will validate the access token and allow the access to the object.
This option provides the control of preventing updates to the linked object for users trying to access the
object by direct means. Since the only access to the object is by obtaining the access token from an SQL
operation, an administrator can effectively control access to the linked objects by using the database
permissions to the SQL table that contains the DataLink column.
Working with DataLinks

To work with DataLinks, you need to understand the DataLink processing environment.
Support for the DataLink data type can be broken down into the following different components:
1. The DB2 database support has a data type called DATALINK. This can be specified on SQL
statements such as CREATE TABLE and ALTER TABLE. The column cannot have any default other
than NULL. Access to the data must be using SQL interfaces. This is because the DataLink itself is not
compatible with any host variable type. SQL scalar functions can be used to retrieve the DataLink
value in character form. There is a DLVALUE scalar function that must be used in SQL to INSERT
and UPDATE the values in the column.
2. The DataLink File Manager (DLFM) is the component that maintains the link status for the files on a
server and keeps track of metadata for each file. This code handles linking, unlinking, and
commitment control issues. An important aspect of DataLinks is that the DLFM does not need to be
on the same physical system as the SQL table that contains the DataLink column. So an SQL table can
link an object that resides in either the same system's integrated file system or a remote server's
integrated file system.
3. The DataLink filter must be run when the file system tries operations against files that are in
directories designated as containing linked objects. This component determines if the file is linked,
and optionally, if the user is authorized to access the file. If the file name includes an access token, the
token will be verified. Because there is extra overhead in this filter process, it is only run when the
accessed object exists in one of the directories within a DataLink prefix. See the following discussion
on prefixes.
When working with DataLinks, there are several steps that must be taken to properly configure the
system:
v TCP/IP must be configured on any systems that are going to be used when working with DataLinks.
This includes the systems on which the SQL tables with DataLink columns are going to be created, as
well as the systems that will contain the objects to be linked. In most cases, this will be the same
system. Since the URL that is used to reference the object contains a TCP/IP server name, this name
must be recognized by the system that is going to contain the DataLink. The command CFGTCP can be
used to configure the TCP/IP names, or to register a TCP/IP name server.
v The system that contains the SQL tables must have the Relational Database Directory updated to reflect
the local database system, and any optional remote systems. The command WRKRDBDIRE can be used
to add or modify information in this directory. For consistency, it is recommended that the same names
be used as the TCP/IP server name and the Relational Database name.
v The DLFM server must be started on any systems that will contain objects to be linked. The command
STRTCPSVR *DLFM can be used to start the DLFM server. The DLFM server can be ended by using
the CL command ENDTCPSVR *DLFM.
SQL programming
255
Once the DLFM has been started, there are some steps needed to configure the DLFM. These DLFM
functions are available via an executable script that can be entered from the QShell interface. To get to the
interactive shell interface, use the CL command QSH. This will open a command entry screen from which
you can enter the DLFM script commands. The script command dfmadmin -help can be used to display
help text and syntax diagrams. For the most commonly used functions, CL commands have also been
provided. Using the CL commands, most or all of the DLFM configuration can be accomplished without
using the script interface. Depending on your preferences, you can choose to use either the script
commands from the QSH command entry screen or the CL commands from the CL command entry
screen.
Since these functions are meant for a system administrator or a database administrator, they all require
the *IOSYSCFG special authority.
Adding a prefix
A prefix is a path or directory that will contain objects to be linked. When setting up the Data Links File
Manager (DLFM) on a system, the administrator must add any prefixes that will be used for DataLinks.
The script command dfmadmin -add_prefix is used to add prefixes. The CL command to add prefixes is
Add Prefix to DataLink File Manager (ADDPFXDLFM) command.
For instance, on server TESTSYS1, there is a directory called /mydir/datalinks/ that contains the objects
that will be linked. The administrator uses the command ADDPFXDLFM PREFIX('/mydir/datalinks/') to
add the prefix. The following links for URLs are valid because their paths have valid prefixes:
http://TESTSYS1/mydir/datalinks/videos/file1.mpg
or
file://TESTSYS1/mydir/datalinks/text/story1.txt
It is also possible to remove a prefix using the script command dfmadmin -del_prefix. This is not a
commonly used function since it can only be run if there are no linked objects anywhere in the directory
structure contained within the prefix name.
Notes:
1. The following directories, or any of their subdirectories, should not be used as prefixes for
DataLinks:
v /QIBM
v /QReclaim
v /QSR
v /QFPNWSSTG
2. Additionally, common base directories such as the following should not be used unless the
prefix is a subdirectory within one of the base directories:
v /home
v
v
v
v
v
v
256
/dev
/bin
/etc
/tmp
/usr
/lib
Adding a host database

A host database is a relational database system from which a link request originates. If the DLFM is on
the same system as the SQL tables that will contain the DataLinks, then only the local database name
needs to be added. If the DLFM will have link requests coming from remote systems, then all of their
names must be registered with the DLFM. The script command to add a host database is dfmadmin
-add_db and the CL command is Add Host Database to DataLink File Manager (ADDHDBDLFM)
command. This function also requires that the libraries containing the SQL tables also be registered.
For instance, on server TESTSYS1 where you have already added the /mydir/datalinks/ prefix, you want
SQL tables on the local system in either TESTDB or PRODDB library to be allowed to link objects on this
server. Use the following:
ADDHDBDLFM HOSTDBLIB((TESTDB) (PRODDB)) HOSTDB(TESTSYS1)
Once the DLFM has been started, and the prefixes and host database names have been registered, you
can begin linking objects in the file system.
|
SQL statements and SQL/XML functions
|
|
|
|
|
Many SQL statements support the XML data type. This enables you to perform many common database
operations with XML data, such as creating tables with XML columns, adding XML columns to existing
tables, creating triggers on tables with XML columns, and inserting, updating, or deleting XML
documents. A set of SQL/XML functions, expressions, and specifications supported by DB2 database
server takes full advantage of the XML data type.
XML data type
|
|
|
|
The XML data type can store an XML value up to 2 GB. A CCSID can be specified for the XML data type.
If a CCSID is not specified, the value of the SQL_XML_DATA_CCSID QAQQINI option will be used. The
default for this option is 1208 (UTF-8). The XML data type can store single byte and Unicode double byte
characters.
|
|
A single row in a table that contains one or more XML or LOB values cannot exceed 3.5 GB. The XML
data type can be specified in a partitioned table.
XML host variables and XML locators can be declared in application programs.
|
|
|
XML locators can be used to refer to XML values. An XML value can be fetched into an XML locator. An
XML locator can be passed to a procedure or function. The locator can be specified as a value on an
INSERT or UPDATE statement.
|
|
Journal entries for XML columns are the same as for LOBs. See "Journal entry layout of LOB columns" in
the SQL programming topic collection.
Application development
|
|
Support for application development is provided by several programming languages, and through SQL
and external functions and procedures:
|
|
|
|
|
|
Programming language support

Application development support of XML enables applications to combine XML and relational
data access and storage. The following programming languages support the XML data type for
SQL:
v ILE RPG
v ILE COBOL
SQL programming
257
v C or C++ (embedded SQL or DB2 CLI)

v Java (JDBC or SQLJ)
|
|
| SQL and external functions and procedures

|
XML data can be passed to SQL procedures and external procedures by including parameters of
|
data type XML in CREATE PROCEDURE parameter signatures. XML data can also be passed to
|
SQL functions and external functions by including parameters of data type XML in CREATE
|
FUNCTION parameter signatures. Existing SQL routine features support the implementation of
|
procedural logic flow around SQL statements that produce or make use of XML values as well as
|
the temporary storage of XML data values in variables.
|
Administration
| The XML features provide a repository for managing the URI dependencies of XML documents:
| XML schema repository (XSR)
|
The XML schema repository (XSR) is a repository for all XML artifacts required to process XML
|
instance documents stored in XML columns. It stores XML schemas, referenced in XML
|
documents. It can be used to validate or decompose XML instance documents.
|
Tooling
| Support for the XML data type is available with the IBM i Navigator.
|
Annotated XML schema decomposition
|
|
|
|
|
|
|
|
|
The XML features enable you to store and access XML data as XML documents. There can be cases where
accessing XML data as relational data is required. Annotated XML schema decomposition decomposes
documents based on annotations specified in an XML schema.
Related concepts:
Annotated XML schema decomposition on page 321
Annotated XML schema decomposition, also referred to as "decomposition" or "shredding," is the process
of storing content from an XML document in columns of relational tables. Annotated XML schema
decomposition operates based on annotations specified in an XML schema. After an XML document is
decomposed, the inserted data has the SQL data type of the column that it is inserted into.
XML input and output overview
| The DB2 database server, which manages both relational and XML data, offers various methods for the
| input and output of XML documents.
| XML documents are stored in columns defined with the XML data type. Each row of an XML column
| stores a single well-formed XML document. The stored document is kept in its XML document form.
| XML columns can be defined in tables that contain columns of other types, which hold relational data,
| and multiple XML columns can be defined for a single table.
|
Input
| The method that you use to put XML data into the database system depends on the task you want to
| accomplish:
| Insert or update
|
Well-formed documents are inserted into XML columns using the SQL INSERT statement. A
|
document is well-formed when it can be parsed successfully. Validation of the XML documents
258
|
|
|
|
|
|
|
|
during an insert or update operation is optional. If validation is performed, the XML schema
must first be registered with the XML schema repository (XSR). Documents are updated using the
SQL UPDATE statement.
Data from XML documents can be decomposed or stored into relational and XML columns using
annotated XML schema decomposition. Decomposition stores data in columns according to
annotations that are added to XML schema documents. These annotations map the data in XML
documents to columns of tables.
|
|
XML schema documents referenced by the decomposition feature are stored in the XML schema
repository (XSR).
|
|
|
|
|
XML schema repository (XSR) registration

The XML schema repository (XSR) stores XML schemas that are used for the validation or
decomposition of XML documents. Registration of XML schemas is usually a prerequisite for
other tasks that are performed on XML documents which have a dependency on these schemas.
XML schemas are registered with the XSR using stored procedures provided by DB2.
Output
SQL is used to retrieve the XML data from the database system.
|
|
|
When querying XML data using an SQL fullselect, the query occurs at the column level. For this reason,
only entire XML documents can be returned from the query. The XMLTABLE built in table function can
be used to retrieve fragments of an XML document in an SQL query.
|
|
|
A number of publishing functions are also available to construct XML values from relational data stored
in DB2 database server. XML values constructed with these publishing functions do not have to be
well-formed XML documents.
Comparison of XML and relational models
|
|
|
When you design your databases, you need to decide whether your data is better suited to the XML
model or the relational model. Your design can also take advantage of the nature of a DB2 database - the
ability to support both relational and XML data in a single database.
|
|
|
|
While this discussion explains some of the main differences between the models and the factors that
apply to each, there are numerous factors that can determine the most suitable choice for your
implementation. Use this discussion as a guideline to assess the factors that can impact your specific
implementation.
Major differences between XML data and relational data
|
|
|
|
XML data is hierarchical; relational data is represented in a model of logical relationships

An XML document contains information about the relationship of data items to each other in the
form of the hierarchy. With the relational model, the only types of relationships that can be
defined are parent table and dependent table relationships.
|
|
|
|
|
XML data is self-describing; relational data is not

An XML document contains not only the data, but also tagging for the data that explains what it
is. A single document can have different types of data. With the relational model, the content of
the data is defined by its column definition. All data in a column must have the same type of
data.
|
|
XML data has inherent ordering; relational data does not

For an XML document, the order in which data items are specified is assumed to be the order of
SQL programming
259
the data in the document. There is often no other way to specify order within the document. For
relational data, the order of the rows is not guaranteed unless you specify an ORDER BY clause
for one or more columns in a fullselect.
|
|
|
|
Factors influencing data model choice
| What kind of data you store can help you determine how you store it. For example, if the data is
| naturally hierarchical and self-describing, you might store it as XML data. However, there are other
| factors that might influence your decision about which model to use:
| When you need maximum flexibility
|
Relational tables follow a fairly rigid model. For example, normalizing one table into many or
|
denormalizing many tables into one can be very difficult. If the data design changes often,
|
representing it as XML data is a better choice. XML schemas can be evolved over time, for
|
example.
| When you need maximum performance for data retrieval
|
Some expense is associated with serializing and interpreting XML data. If performance is more of
|
an issue than flexibility, relational data might be the better choice.
| When data is processed later as relational data
|
If subsequent processing of the data depends on the data being stored in a relational database, it
|
might be appropriate to store parts of the data as relational, using decomposition. An example of
|
this situation is when online analytical processing (OLAP) is applied to the data in a data
|
warehouse. Also, if other processing is required on the XML document as a whole, then storing
|
some of the data as relational as well as storing the entire XML document might be a suitable
|
approach in this case.
| When data components have meaning outside a hierarchy
|
Data might be inherently hierarchical in nature, but the child components do not need the
|
parents to provide value. For example, a purchase order might contain part numbers. The
|
purchase orders with the part numbers might be best represented as XML documents. However,
|
each part number has a part description associated with it. It might be better to include the part
|
descriptions in a relational table, because the relationship between the part numbers and the part
|
descriptions is logically independent of the purchase orders in which the part numbers are used.
| When data attributes apply to all data, or to only a small subset of the data
|
Some sets of data have a large number of possible attributes, but only a small number of those
|
attributes apply to any particular data value. For example, in a retail catalog, there are many
|
possible data attributes, such as size, color, weight, material, style, weave, power requirements, or
|
fuel requirements. For any given item in the catalog, only a subset of those attributes is relevant:
|
power requirements are meaningful for a table saw, but not for a coat. This type of data is
|
difficult to represent and search with a relational model, but relatively easy to represent and
|
search with an XML model.
| When referential integrity is required
|
XML columns cannot be defined as part of referential constraints. Therefore, if values in XML
|
documents need to participate in referential constraints, you should store the data as relational
|
data.
| When the data needs to be updated often
|
You update XML data in an XML column only by replacing full documents. If you need to
|
frequently update small fragments of very large documents for a large number of rows, it can be
|
more efficient to store the data in non-XML columns. If, however, you are updating small
|
documents and only a few documents at a time, storing as XML can be efficient as well.
260
Tutorial for XML
|
|
|
The XML data type enables you to define table columns that store in each row a single well-formed XML
document. This tutorial demonstrates how to set up a DB2 database to store XML data and to perform
basic operations with the XML features.
|
|
|
|
|
|
After completing this tutorial, you will be able to do the following tasks:
v Creating a table that can store XML data
v Inserting XML documents into XML typed columns
v Updating XML documents stored in an XML column
v Validating XML documents against XML schemas
v Transforming with XSLT stylesheets
Preparation
|
|
The examples in the exercises should be entered at or copied and pasted into the IBM i Navigator Run
SQL Scripts tool. Using Interactive SQL will not show the XML result data as serialized data.
|
|
Exercise 1: Creating a table that can store XML data
|
|
|
|
|
|
Create a table named Customer that contains an XML column:
Note that specifying a primary key is optional and not required in order to store XML.
You can also add one or more XML columns to existing tables with the ALTER TABLE SQL statement.
Return to the tutorial
|
|
|
Exercise 2: Inserting XML documents into XML typed columns
|
|
|
Typically, XML documents are inserted using application programs. While XML data can be inserted
through applications using XML, binary, or character types, it is recommended that you use XML or
binary types if XML documents from many sources are processed with different encodings.
|
|
|
|
|
|
This exercise shows how to insert XML documents into XML typed columns manually in Run SQL
Scripts, where the XML document is always a character literal. In most cases, string data cannot be
directly assigned to a target with an XML data type; the data must first be parsed explicitly using the
XMLPARSE function. In INSERT or UPDATE operations, however, string data can be directly assigned to
XML columns without an explicit call to the XMLPARSE function. In these two cases, the string data is
implicitly parsed. Refer to the XML parsing documentation for more information.
|
|
|
|
|
|
|
|
Insert three XML documents into the Customer table that you created in Exercise 1:
This exercise shows how to create a table that contains an XML column.
CREATE SCHEMA POSAMPLE;

SET CURRENT SCHEMA POSAMPLE;
CREATE TABLE Customer (Cid BIGINT NOT NULL PRIMARY KEY, Info XML);
Well-formed XML documents are inserted into XML typed columns using the SQL INSERT statement.
This exercise shows you how to insert XML documents into XML columns.
INSERT INTO Customer (Cid, Info) VALUES (1000,

<customerinfo xmlns="http://posample.org" Cid="1000">
<name>Kathy Smith</name>
<addr country="Canada">
<street>5 Rosewood</street>
<city>Toronto</city>
<prov-state>Ontario</prov-state>
SQL programming
261
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<pcode-zip>M6W 1E6</pcode-zip>
</addr>
<phone type="work">416-555-1358</phone>
</customerinfo>);
<name>Jim Noodle</name>
<street>25 EastCreek</street>
<city>Markham</city>
<pcode-zip>N9C 3T6</pcode-zip>
</addr>
</customerinfo>);
<name>Robert Shoemaker</name>
<street>1596 Baseline</street>
<city>Aurora</city>
<pcode-zip>N8X 7F8</pcode-zip>
</addr>
</customerinfo>);
| You can confirm that the records were successfully inserted as follows:
| SELECT * from Customer;
| If you are running this exercise in Interactive SQL, the XML values will not be serialized for you. You
| must explicitly use the XMLSERIALIZE function to see the inserted data.
| Return to the tutorial
| Exercise 3: Updating XML documents stored in an XML column
| This exercise shows you how to update XML documents with SQL statements.
| Updating with SQL
| To update an XML document stored in an XML column using SQL, you must perform a full-document
| update using the SQL UPDATE statement.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Update one of the documents inserted in Exercise 2 as follows (where the values of the <street>, <city>,
and <pcode-zip> elements have changed):
UPDATE customer SET info =
<street>1150 Maple Drive</street>
<city>Newtown</city>
<pcode-zip>Z9Z 2P2</pcode-zip>
</addr>
</customerinfo>
WHERE Cid = 1002;
| You can confirm that the XML document was updated as follows:
| SELECT * from Customer;
262
|
|
If you are running this exercise in Interactive SQL, the XML values will not be serialized for you. You
must explicitly use the XMLSERIALIZE function to see the updated data.
The row where Cid="1002" contains the changed <street>, <city>, and <pcode-zip> values.
XML documents can be identified by values in the non-XML columns of the same table.
|
|
|
|
Exercise 4: Validating XML documents against XML schemas
|
|
There are tools available, such as those in IBM Rational Application Developer, that help you generate
XML schemas from various sources, including DTDs, existing tables, or XML documents.
|
|
|
Before you can validate, you must register your XML schema with the built-in XML schema repository
(XSR). This process involves registering each XML schema document that makes up the XML schema.
Once all XML schema documents have been successfully registered, you must complete the registration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Register and complete registration of the posample.customer XML schema as follows:
This exercise shows you how to validate XML documents. You can validate your XML documents against
XML schemas only; DTD validation is not supported. (Although you cannot validate against DTDs, you
can still insert documents that contain a DOCTYPE or that refer to DTDs.)
CREATE PROCEDURE SAMPLE_REGISTER

LANGUAGE SQL
BEGIN
DECLARE CONTENT BLOB(1M);
VALUES BLOB(<?xml version="1.0"?>
<xs:schema targetNamespace="http://posample.org"
xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:element name="customerinfo">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string" minOccurs="1" />
<xs:element name="addr" minOccurs="1" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="street" type="xs:string" minOccurs="1" />
<xs:element name="city" type="xs:string" minOccurs="1" />
<xs:element name="prov-state" type="xs:string" minOccurs="1" />
<xs:element name="pcode-zip" type="xs:string" minOccurs="1" />
</xs:sequence>
<xs:attribute name="country" type="xs:string" />
</xs:complexType>
</xs:element>
<xs:element name="phone" nillable="true" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" form="unqualified" type="xs:string" />
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="assistant" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string" minOccurs="0" />
<xs:element name="phone" nillable="true" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:simpleContent >
<xs:attribute name="type" type="xs:string" />
</xs:extension>
SQL programming
263
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="Cid" type="xs:integer" />
</xs:complexType>
</xs:element>
</xs:schema>) INTO CONTENT;
|
|
|
|
|
|
|
|
|
You can verify that the XML schema was successfully registered by querying the QSYS2.XSROBJECTS
catalog view, which contains information about objects stored in the XSR. This query and its result
(formatted for clarity) are as follows:
CALL SYSPROC.XSR_REGISTER(POSAMPLE, CUSTOMER, http://posample.org, CONTENT, null);

END;
SET PATH POSAMPLE;
CALL SAMPLE_REGISTER;
CALL SYSPROC.XSR_COMPLETE(POSAMPLE, CUSTOMER, null, 0);
SELECT XSROBJECTSCHEMA, XSROBJECTNAME FROM QSYS2.XSROBJECTS

WHERE XSROBJECTSCHEMA = POSAMPLE;
XSROBJECTSCHEMA
-------------------POSAMPLE
XSROBJECTNAME
-------------------CUSTOMER
| This XML schema is now available to be used for validation. Validation is typically performed during an
| INSERT or UPDATE operation. Perform validation using the XMLVALIDATE function. The INSERT or
| UPDATE operation on which XMLVALIDATE was specified, will occur only if the validation succeeds.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following INSERT statement inserts a new XML document into the Info column of the Customer
table, only if the document is valid according to the posample.customer XML schema previously
registered.
|
|
|
|
|
XMLVALIDATE operates on XML data. Because the XML document in this example is passed as character
data, XMLVALIDATE must be used in conjunction with the XMLPARSE function. Note that character
data can be assigned directly to XML only in INSERT, UPDATE, or MERGE statements. Here, an INSERT
statement is used. The XMLPARSE function parses its argument as an XML document and returns an
XML value.
INSERT INTO Customer(Cid, Info) VALUES (1004, XMLVALIDATE (XMLPARSE (DOCUMENT

<city>Aurora</city>
</addr>
<phone type="home">416-555-2937</phone>
<phone type="cell">905-555-8743</phone>
<phone type="cottage">613-555-3278</phone>
</customerinfo> PRESERVE WHITESPACE )
ACCORDING TO XMLSCHEMA ID posample.customer ));
| To verify that the validation and insert were successful, query the Info column:
| SELECT Info FROM Customer;
264
This query should return three XML documents, one of which is the document just inserted.
|
|
Exercise 5: Transforming with XSLT stylesheets
|
|
|
|
|
|
|
|
|
This example illustrates how to use the XSLTRANSFORM built-in function to transform XML documents
that are stored in the database. In this case the XML document contains an arbitrary number of university
student records. Each student element contains a student's ID, first name, last name, age, and the
university he is attending, as follows:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The intent of the XSLT transformation is to extract the information in the XML records and create an
HTML web page that can be viewed in a browser. For that purpose we will use the following XSLT
stylesheet, which is also stored in the database.
You can use the XSLTRANSFORM function to convert XML data within the database into other formats.
<?xml version="1.0"?>
<students xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<student studentID="1" firstName="Steffen" lastName="Siegmund"
age="23" university="Rostock"/>
</students>
<?xml version="1.0" ?>

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:param name="headline"/>
<xsl:param name="showUniversity"/>
<xsl:template match="students">
<html>
<head/>
<body>
<h1><xsl:value-of select="$headline"/></h1>
<table border="1">
<th>
<tr>
<td width="80">StudentID</td>
<td width="200">First Name</td>
<td width="200">Last Name</td>
<td width="50">Age</td>
<xsl:choose>
<xsl:when test="$showUniversity =true">
<td width="200">University</td>
</xsl:when>
</xsl:choose>
</tr>
</th>
<xsl:apply-templates/>
</table>
</body>
</html>
</xsl:template>
<xsl:template match="student">
<tr>
<td><xsl:value-of select="@studentID"/></td>
<td><xsl:value-of select="@firstName"/></td>
<td><xsl:value-of select="@lastName"/></td>
<td><xsl:value-of select="@age"/></td>
<xsl:choose>
<xsl:when test="$showUniversity = true ">
<td><xsl:value-of select="@university"/></td>
</xsl:when>
</xsl:choose>
</tr>
</xsl:template>
</xsl:stylesheet>
SQL programming
265
| This stylesheet will work both with a standard XSLT transform, and using a supplied parameter file to
| control its behavior at runtime.
| 1. Create the table into which you can store your XML document and stylesheet document.
|
SET CURRENT SCHEMA USER;
|
CREATE TABLE XML_TAB (DOCID INTEGER, XML_DOC XML, XSL_DOC CLOB(1M));
| 2. Insert your documents into the tables. In this example the XML document and XSLT stylesheet can be
|
loaded into the same table as separate column values. The INSERT statement uses a truncated version
|
of the XSLT stylesheet as the third value. To use the following INSERT statement, replace the
|
truncated stylesheet value with the XSLT stylesheet listed previously in this exercise.
|
INSERT INTO XML_TAB VALUES
|
(1,
|
|
<students xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
|
|
|
</students>,
|
|
<?xml version="1.0" encoding="UTF-8"?>
|
|
...
|
</xsl:stylesheet>
|
);
| 3. Call the XSLTRANSFORM built-in function to transform the XML document.
|
SELECT XSLTRANSFORM (XML_DOC USING XSL_DOC AS CLOB(1M)) FROM XML_TAB;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The output of this process will be the following HTML file:
|
|
|
|
|
While this is straightforward, there may be occasions when you want to alter the behavior of the XSLT
stylesheet at runtime, either to add information not contained in the XML records or to change the nature
of the output itself (to XHTML instead of standard HTML, for instance). You can pass parameters to the
XSLT process at runtime by using a separate parameter file. The parameter file is itself an XML document
and contains param statements that correspond to similar statements in the XSLT stylesheet file.
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<h1></h1>
<table border="1">
<th>
<tr>
</tr>
</th>
<tr>
<td>1</td>
<td>Steffen</td><td>Siegmund</td>
<td>23</td>
</tr>
</table>
</body>
</html>
| For instance, two parameters are defined in the stylesheet above as follows:
| <xsl:param name="showUniversity"/>
| <xsl:param name="headline"/>
266
|
|
|
|
|
|
|
|
|
|
|
|
These parameters were not used in the first transform as described above. To see how parameter-passing
works, create a parameter file as follows:
|
|
|
|
Examine this query:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The above query generates the following HTML:
Inserting XML data
|
|
Before you can insert XML documents, you must create a table that contains an XML column, or add an
XML column to an existing table.
|
|
|
Addition of XML columns to existing tables
|
|
|
|
|
Example The sample database contains a table for customer data that contains two XML columns. The
definition looks like this:
CREATE TABLE PARAM_TAB (DOCID INTEGER, PARAM VARCHAR(1000));

INSERT INTO PARAM_TAB VALUES
(1,
<params xmlns="http://www.ibm.com/XSLTransformParameters">
<param name="showUniversity" value="true"/>
<param name="headline">The student list ...</param>
</params>
);
SELECT XSLTRANSFORM (
XML_DOC USING XSL_DOC WITH PARAM AS CLOB(1M)) FROM XML_TAB X, PARAM_TAB P
WHERE X.DOCID=P.DOCID;
<html>
<head>
</head>
<body>
<h1>The students list ...</h1>
<table border="1">
<th>
<tr>
</tr>
</th>
<tr>
<td>1</td>
<td>Steffen</td>
<td>Siegmund</td><td>23</td><td>Rostock</td>
</tr>
</table>
</body>
</html>
To add XML columns to existing tables, you specify columns with the XML data type in the ALTER
TABLE statement with the ADD clause. A table can have one or more XML columns.
CREATE TABLE Customer (Cid BIGINT NOT NULL PRIMARY KEY,

Info XML,
History XML);
SQL programming
267
|
|
|
|
|
Create a table named MyCustomer that is a copy of Customer, and add an XML column to describe
customer preferences:
SET CURRENT SCHEMA USER;
CREATE TABLE MyCustomer LIKE Customer;
ALTER TABLE MyCustomer ADD COLUMN Preferences XML;
| Insertion into XML columns

| To insert data into an XML column, use the SQL INSERT statement. The input to the XML column must
| be a well-formed XML document, as defined in the XML 1.0 specification. The application data type can
| be an XML, character, or binary type.
| You should insert XML data from host variables, rather than literals, so that the DB2 database server can
| use the host variable data type to determine some of the encoding information.
|
|
|
|
|
XML data in an application is in its serialized string format. When you insert the data into an XML
column, it must be converted to the stored XML document format. If the application data type is an XML
data type, the DB2 database server performs this operation implicitly. If the application data type is not
an XML type, you can invoke the XMLPARSE function explicitly when you perform the insert operation,
to convert the data from its serialized string format to the XML document format.
| During document insertion, you might also want to validate the XML document against a registered XML
| schema. You can do that with the XMLVALIDATE function.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following examples demonstrate how XML data can be inserted into XML columns. The examples
use table MyCustomer, which is a copy of the sample Customer table. The XML data that is to be
inserted is in file c6.xml, and looks like this:
|
|
|
|
|
|
|
|
|
|
|
Example: In a JDBC application, read XML data from file c6.xml as binary data, and insert the data into
an XML column:
|
|
|
|
|
|
|
|
Example: In a static embedded C application, insert data from a binary XML host variable into an XML
column:

<name>Christine Haas</name>
<street>12 Topgrove</street>
<pcode-zip>N8X-7F8</pcode-zip>
</addr>
</customerinfo>
PreparedStatement insertStmt = null;

String sqls = null;
int cid = 1015;
sqls = "INSERT INTO MyCustomer (Cid, Info) VALUES (?, ?)";
insertStmt = conn.prepareStatement(sqls);
insertStmt.setInt(1, cid);
File file = new File("c6.xml");
insertStmt.setBinaryStream(2, new FileInputStream(file), (int)file.length());
insertStmt.executeUpdate();

sqlint64 cid;
SQL TYPE IS XML AS BLOB (10K) xml_hostvar;
...
cid=1015;
268
|
|
|
/* Read data from file c6.xml into xml_hostvar */

...
EXEC SQL INSERT INTO MyCustomer (Cid,Info) VALUES (:cid, :xml_hostvar);
|
|
|
XML parsing
|
|
You can let the DB2 database server perform parsing implicitly, or you can perform XML parsing
explicitly.
|
|
|
|
|
|
|
|
|
Implicit XML parsing occurs in the following cases:

v When you pass data to the database server using a host variable of type XML, or use a parameter
marker of type XML
The database server does the parsing when it binds the value for the host variable or parameter
marker for use in statement processing.
You must use implicit parsing in this case.
v When you assign a host variable, parameter marker, or SQL expression with a string data type
(character, graphic, or binary) to an XML column in an INSERT, UPDATE, or MERGE statement. The
implicit parsing occurs when the statement is executed.
|
|
|
You perform explicit XML parsing when you invoke the XMLPARSE function on the input XML data. You
can use the result of XMLPARSE in any context that accepts an XML data type. For example, you can
assign the result to an XML column or use it as a stored procedure parameter of type XML.
|
|
|
|
|
The XMLPARSE function takes a non-XML character, binary, or Unicode graphic data type as input. For
embedded dynamic SQL applications, you need to cast the parameter marker that represents the input
document for XMLPARSE to the appropriate data type. For example:
|
|
For static embedded SQL applications, a host variable argument of the XMLPARSE function cannot be
declared as an XML type (XML AS BLOB, XML AS CLOB, or XML AS DBCLOB type).
XML parsing and whitespace handling
|
|
During implicit or explicit XML parsing, you can control the preservation or stripping of boundary
whitespace characters when you store the data in the database.
|
|
|
According to the XML standard, whitespace is space characters (U+0020), carriage returns (U+000D), line
feeds (U+000A), or tabs (U+0009) that are in the document to improve readability. When any of these
characters appear as part of a text string, they are not considered to be whitespace.
|
|
|
Boundary whitespace is whitespace characters that appear between elements. For example, in the following
document, the spaces between <a> and <b> and between </b> and </a> are boundary whitespace.
|
|
With explicit invocation of XMLPARSE, you use the STRIP WHITESPACE or PRESERVE WHITESPACE
option to control preservation of boundary whitespace. The default is stripping of boundary whitespace.
With implicit XML parsing:
|
|
v If the input data type is not an XML type or is not cast to an XML data type, the DB2 database server
always strips whitespace.
XML parsing is the process of converting XML data from its serialized string format to its XML document
format.
INSERT INTO MyCustomer (Cid, Info)

VALUES (?, XMLPARSE(DOCUMENT CAST(? AS CLOB(1K)) PRESERVE WHITESPACE))
<a> <b> and between </b> </a>
SQL programming
269
| v If the input data type is an XML data type, you can use the CURRENT IMPLICIT XMLPARSE OPTION
|
special register to control preservation of boundary whitespace. You can set this special register to
|
STRIP WHITESPACE or PRESERVE WHITESPACE. The default is stripping of boundary whitespace.
|
|
|
|
|
|
|
|
|
If you use XML validation, the DB2 database server ignores the CURRENT IMPLICIT XMLPARSE
OPTION special register and uses only the validation rules to determine stripping or preservation of
whitespace in the following cases:
xmlvalidate(? ACCORDING TO XMLSCHEMA ID schemaname)
xmlvalidate(?)
xmlvalidate(:hvxml ACCORDING TO XMLSCHEMA ID schemaname)
xmlvalidate(:hvxml)
xmlvalidate(cast(? as xml) ACCORDING TO XMLSCHEMA ID schemaname)
xmlvalidate(cast(? as xml))
| In these cases, ? represents XML data, and :hvxml is an XML host variable.
| The XML standard specifies an xml:space attribute that controls the stripping or preservation of
| whitespace within XML data. xml:space attributes override any whitespace settings for implicit or explicit
| XML parsing.
|
|
|
|
For example, in the following document, the spaces immediately before and after <b> are always
preserved, regardless of any XML parsing options, because the spaces are contained within an element
which is defined with the attribute xml:space="preserve":
|
|
|
|
However, in the following document, the spaces immediately before and after <b> can be controlled by
the XML parsing options, because the spaces are contained within an element which is defined with the
attribute xml:space="default":
SQL/XML publishing functions for constructing XML values
<a xml:space="preserve"> <b> <c>c</c>b </b></a>
<a xml:space="default"> <b> <c>c</c>b </b></a>
| You can construct XML values, which do not necessarily have to be well-formed XML documents, by
| combining those publishing functions that correspond to the components you want in the resulting XML
| value. The functions must be specified in the order that you want the results to appear.
| Values constructed using the SQL/XML publishing functions are returned as XML. Depending on what
| you want to do with the XML value, you might need to explicitly serialize the value to convert it to
| another SQL data type. Refer to the documentation on XML serialization for details.
| The following SQL/XML publishing functions can be used to construct XML values.
| XMLAGG aggregate function
|
Returns an XML sequence containing an item for each non-null value in a set of XML values.
| XMLATTRIBUTES scalar function
|
Constructs XML attributes from the arguments. This function can be used only as an argument of
|
the XMLELEMENT function.
| XMLCOMMENT scalar function
|
Returns an XML value with the input argument as the content.
| XMLCONCAT scalar function
|
Returns a sequence containing the concatenation of a variable number of XML input arguments.
| XMLDOCUMENT scalar function
|
Returns an XML value that is a well-formed XML document. Every XML value that is stored in a
|
DB2 table must be a document. This function forms an XML document from the XML value.
270
|
|
|
|
XMLELEMENT scalar function

Returns an XML value that is an XML element. Every XML value that is stored in a DB2 table
must be a document. The XMLELEMENT function does not create a document, only an element.
The stored XML value must be a document formed by the XMLDOCUMENT function.
|
|
XMLFOREST scalar function

Returns an XML value that is a sequence of XML elements.
|
|
|
|
|
XMLGROUP aggregate function

Returns a single top-level element to represent a table or the result of a query. By default each
row in the result set is mapped to a row subelement and each input expression is mapped to a
subelement of the row subelement. Optionally, each row in the result can be mapped to a row
subelement and each input expression to be mapped to an attribute of the row subelement.
|
|
|
XMLNAMESPACES declaration
Constructs namespace declarations from the arguments. This declaration can be used only as an
argument of the XMLELEMENT and XMLFOREST functions.
|
|
XMLPI scalar function

Returns an XML value with a single processing instruction.
|
|
|
|
XMLROW scalar function

Returns a sequence of row elements to represent a table or the result of a query. By default each
input expression is transformed into a subelement of a row element. Optionally, each input
expression can be transformed into an attribute of a row element.
|
|
XMLTEXT scalar function

Returns an XML value that contains the value of the input argument.
|
|
XSLTRANSFORM scalar function

Converts XML data into other formats, including other XML schemas.
|
|
|
|
Related concepts:
XML serialization on page 282
XML serialization is the process of converting XML data from the format that it has in a DB2 database, to
the serialized string format that it has in an application.
|
|
|
Example: Construct an XML document with values from a single table
|
|
|
|
|
|
|
|
|
|
|
This example shows how an XML document can be constructed from values stored in a single table. In
the following query:
v Each <item> element is constructed with values from the NAME column of the PRODUCT table, using
the XMLELEMENT function.
v All <item> elements are then aggregated, using XMLAGG, within the constructed <allProducts>
element.
v A namespace is added to the <allProducts> element, with the XMLNAMESPACES function.
|
|
|
|
|
|
|
This query returns the following XML value. It is formatted here to improve readability.
This example shows how you can construct XML values suitable for publishing from a single table with
SQL/XML publishing functions.
SELECT XMLELEMENT (NAME "allProducts",

XMLNAMESPACES (DEFAULT http://posample.org),
XMLAGG(XMLELEMENT (NAME "item", p.name)))
FROM Product p
<allProducts xmlns="http://posample.org">
<item>Snow Shovel, Basic 22 inch</item>
<item>Snow Shovel, Deluxe 24 inch</item>
<item>Snow Shovel, Super Deluxe 26 inch</item>
<item>Ice Scraper, Windshield 4 inch</item>
</allProducts>
SQL programming
271
|
|
|
|
|
|
|
You can construct a similar XML document that contains a sequence of row elements by using the
XMLROW function instead of aggregating the elements with XMLAGG. Item elements are also given a
namespace prefix:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The resulting output is as follows:
SELECT XMLELEMENT (NAME "products",

XMLNAMESPACES (http://posample.org AS "po"),
XMLROW(NAME AS "po:item"))
FROM Product
<products xmlns:po="http://posample.org">
<row>
<po:item>Snow Shovel, Basic 22 inch</po:item>
</row>
</products>
<row>
<po:item>Snow Shovel, Deluxe 24 inch</po:item>
</row>
</products>
<row><po:item>Snow Shovel, Super Deluxe 26 inch</po:item>
</row>
</products>
<row><po:item>Ice Scraper, Windshield 4 inch</po:item>
</row>
</products>
| Example: Construct an XML document with values from multiple tables

| This example shows how you can construct XML values suitable for publishing from multiple tables with
| SQL/XML publishing functions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This example shows how an XML document can be constructed from values stored in multiple tables. In
the following query:
v <prod> elements are constructed from a forest of elements, which are called name and numInStock,
using the XMLFOREST function. This forest is built with values from the NAME column in the
PRODUCT table and the QUANTITY column in the INVENTORY table.
v All <prod> elements are then aggregated within the constructed <saleProducts> element.
SELECT XMLELEMENT (NAME "saleProducts",
XMLNAMESPACES (DEFAULT http://posample.org),
XMLAGG (XMLELEMENT (NAME "prod",
XMLATTRIBUTES (p.Pid AS "id"),
XMLFOREST (p.name AS "name",
i.quantity AS "numInStock"))))
FROM PRODUCT p, INVENTORY i
WHERE p.Pid = i.Pid
| The previous query yields the following XML document:

| <saleProducts xmlns="http://posample.org">
|
<prod id="100-100-01">
|
<name>Snow Shovel, Basic 22 inch</name>
|
<numInStock>5</numInStock>
|
</prod>
|
<prod id="100-101-01">
|
<name>Snow Shovel, Deluxe 24 inch</name>
|
|
</prod>
|
<prod id="100-103-01">
|
<name>Snow Shovel, Super Deluxe 26 inch</name>
|
|
</prod>
|
<prod id="100-201-01">
272
|
|
|
|
<name>Ice Scraper, Windshield 4 inch</name>

</prod>
</saleProducts>
|
|
|
|
Example: Construct an XML document with values from table rows that contain
null elements
|
|
|
|
|
When an XML value is constructed using XMLELEMENT or XMLFOREST, it is possible that a null value
is encountered when determining the element's content. The EMPTY ON NULL and NULL ON NULL
options of XMLELEMENT and XMLFOREST allow you to specify whether an empty element or no
element is generated when an element's content is null. The default null handling for XMLELEMENT is
EMPTY ON NULL. The default null handling for XMLFOREST is NULL ON NULL.
|
|
|
|
|
|
|
|
This example assumes that the LOCATION column of the INVENTORY table contains a null value in one
row. The following query therefore does not return the <loc> element, because XMLFOREST treats nulls
as null by default:
|
|
|
|
In the result value, there is no <loc> element for the row that contains the null value.
|
|
|
|
|
|
The same query, with the EMPTY ON NULL option specified, returns an empty <loc> element:
|
|
|
|
|
In the result value, there is an empty <loc> element.
|
|
|
|
Example: Transforming with XSLT stylesheets
|
|
|
|
|
|
|
XSLT uses stylesheets to convert XML into other data formats. You can convert part or all of an XML
document and select or rearrange the data using the XPath query language and the built-in functions of
XSLT. XSLT is commonly used to convert XML to HTML, but can also be used to transform XML
documents that comply with one XML schema into documents that comply with another schema. XSLT
can also be used to convert XML data into unrelated formats, like comma-delimited text or formatting
languages such as troff. XSLT has two main areas of applicability:
v Formatting (conversion of XML into HTML)
|
|
v Data exchange (querying, reorganizing and converting data from one XML schema to another, or into a
data exchange format such as SOAP)
This example shows how you can construct XML values suitable for publishing from table rows that
contain null elements with SQL/XML publishing functions.
SELECT XMLELEMENT (NAME "newElem",

XMLATTRIBUTES (PID AS "prodID"),
XMLFOREST (QUANTITY AS "quantity",
LOCATION AS "loc"))
FROM INVENTORY
<newElem prodID="100-100-01">
<quantity>5</quantity>
</newElem>
SELECT XMLELEMENT (NAME "newElem",

XMLATTRIBUTES (PID AS "prodID"),
XMLFOREST (QUANTITY AS "quantity",
LOCATION AS "loc" OPTION EMPTY ON NULL))
FROM INVENTORY
<newElem prodID="100-100-01">
<loc/>
</newElem>
The standard way to transform XML data into other formats is by Extensible Stylesheet Language
Transformations (XSLT). You can use the built-in XSLTRANSFORM function to convert XML documents
into HTML, plain text, or different XML schemas.
SQL programming
273
|
|
|
|
Both cases may require that an entire XML document or only selected parts of it be transformed. XSLT
incorporates the XPath specification, permitting query and retrieval of arbitrary data from the source
XML document. An XSLT template may also contain or create additional information such as file headers
and instruction blocks that will be added to the output file.
| How XSLT Works

|
|
|
|
|
|
XSLT stylesheets are written in Extensible Stylesheet Language (XSL), an XML schema. XSL is a template
language rather than an algorithmic language such as C or Perl, a feature that limits XSL's power but
makes it uniquely suited to its purpose. XSL stylesheets contain one or more template elements, which
describe what action to take when a given XML element or query is encountered in the target file. A
typical XSLT template element will start by specifying which element it applies to. For instance,
<xsl:template match="product">
| declares that the contents of this template will be used to replace the content of any <product> tag
| encountered in the target XML file. An XSLT file consists of a list of such templates, in no necessary
| order.
|
|
|
|
|
|
|
|
|
|
The following example shows typical elements of an XSLT template. In this case the target will be XML
documents containing inventory information, such as this record describing an ice scraper:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This record includes such information as the part number, description, and price of a windshield ice
scraper. Some of this information is contained within elements, such as <name>. Some, like the part
number, are contained in attributes (in this case the pid attribute of the <product> element). To display
this information as a web page, you could apply the following XSLT template:
<product pid="100-201-01">
<description>
<name>Ice Scraper, Windshield 4 inch</name>
<details>Basic Ice Scraper 4 inches wide, foam handle</details>
<price>3.99</price>
</description>
</product>

<xsl:output method="html"/>
<xsl:template match="/">
<html>
<body>
<h1><xsl:value-of select="/product/description/name"/></h1>
<table border="1">
<th>
<xsl:apply-templates select="product"/>
</th>
</table>
</body>
</html>
</xsl:template>
<tr>
<td width="80">product ID</td>
<td><xsl:value-of select="@pid"/></td>
</tr>
<tr>
<td width="200">product name</td>
<td><xsl:value-of select="/product/description/name"/></td>
</tr>
<tr>
<td width="200">price</td>
<td>$<xsl:value-of select="/product/description/price"/></td>
274
|
|
|
|
|
|
|
</tr>
<tr>
<td width="50">details</td>
<td><xsl:value-of select="/product/description/details"/></td>
</tr>
</xsl:template>
</xsl:stylesheet>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When an XSLT processor receives as input both the template and target documents above, it will output
the following HTML document:
|
|
|
|
The XSLT processor tests the incoming XML document for given conditions (typically one condition per
template). If a condition is true the template contents are inserted into the output, and if they are false
the template is passed over by the processor. The stylesheet may add its own data to the output, for
example in the HTML table tagging and strings such as "product ID."
|
|
|
XPath can be used both to define template conditions, as in <xsl:template match="product"> and to
select and insert data from anywhere in the XML stream, as in <h1><xsl:value-of select="/product/
description/name"/></h1>.
Using XSLTRANSFORM
|
|
|
You can use the XSLTRANSFORM function to apply XSLT stylesheets to XML data. If you supply the
function with the name of an XML document and an XSLT stylesheet, the function will apply the
stylesheet to the document and return the result.
|
|
|
Example: Using XSLT as a formatting engine
|
|
|
|
|
|
|
|
|
|
|
To get set up, first insert the two example documents below into the database.
<html>
<body>
<h1>Ice Scraper, Windshield 4 inch</h1>
<table border="1">
<th>
<tr>
<td width="80">product ID</td><td>100-201-01</td>
</tr>
<tr>
<td width="200">product name</td><td>Ice Scraper, Windshield 4 inch</td>
</tr>
<tr>
<td width="200">price</td><td>$3.99</td>
</tr>
<tr>
<td width="50">details</td><td>Basic Ice Scraper 4 inches wide, foam handle</td>
</tr>
</th>
</table>
</body>
</html>
The following example illustrates how to use the built-in XSLTRANSFORM function as a formatting
engine.
INSERT INTO XML_TAB VALUES

(1,
<students xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation = "/home/steffen/xsd/xslt.xsd">
</students>,
SQL programming
275
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<xsl:param name="showUniversity"/>
<xsl:template match="students">
<html>
<head/>
<body>
<table border="1">
<th>
<tr>
<xsl:choose>
<xsl:when test="$showUniversity =true">
</xsl:when>
</xsl:choose>
</tr>
</th>
</table>
</body>
</html>
</xsl:template>
<xsl:template match="student">
<tr>
<td><xsl:value-of select="@studentID"/></td>
<td><xsl:value-of select="@firstName"/></td>
<td><xsl:value-of select="@lastName"/></td>
<td><xsl:value-of select="@age"/></td>
<xsl:choose>
<xsl:when test="$showUniversity = true ">
<td><xsl:value-of select="@university"/></td>
</xsl:when>
</xsl:choose>
</tr>
</xsl:template>
</xsl:stylesheet>
);
| Next, call the XSLTRANSFORM function to convert the XML data into HTML and display it.
| SELECT XSLTRANSFORM (XML_DOC USING XSL_DOC AS CLOB(1M)) FROM XML_TAB;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The result is this document:

<html>
<head>
</head>
<body>
<h1></h1>
<table border="1">
<th>
<tr>
</tr>
</th>
<tr>
<td>1</td>
<td>Steffen</td><td>Siegmund</td>
276
|
|
|
|
|
<td>23</td>
</tr>
</table>
</body>
</html>
|
|
|
In this example, the output is HTML and the parameters influence only what HTML is produced and
what data is brought over to it. As such it illustrates the use of XSLT as a formatting engine for end-user
output.
|
|
|
Example: Using XSLT for data exchange
This example uses parameters with the stylesheet to produce different data exchange formats at runtime.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We use a stylesheet that incorporates xsl:param elements to capture data from a parameter file.
|
|
|
|
|
|
|
The parameter file contains parameters corresponding to the ones in the XSLT template, with content:
This example illustrates how to use the built-in XSLTRANSFORM function to convert XML documents
for data exchange.
INSERT INTO Display_productdetails values(1, <?xml version="1.0" encoding="UTF-8"?>

<xsl:param name="supermarketname"/>
<html>
<head/>
<body>
<table border="1">
<th>
<tr>
<td width="200">product name</td>
<td width="50">details</td>
<xsl:choose>
<xsl:when test="$supermarket =true ">
<td width="200">BIG BAZAAR super market</td>
</xsl:when>
</xsl:choose>
</tr>
</th>
</table>
</body>
</html>
</xsl:template>
<tr>
<td><xsl:value-of select="@pid"/></td>
<td><xsl:value-of select="/product/description/name"/></td>
<td><xsl:value-of select="/product/description/price"/></td>
<td><xsl:value-of select="/product/description/details"/></td>
</tr>
</xsl:template>
</xsl:stylesheet>
);
CREATE TABLE PARAM_TAB (DOCID INTEGER, PARAM VARCHAR (10K));

INSERT INTO PARAM_TAB VALUES
(1,
<params xmlns="http://www.ibm.com/XSLTransformParameters">
SQL programming
277
|
<param name="supermarketname" value="true"/>
|
<param name="headline">BIG BAZAAR super market</param>
| </params>
| );
| You can then apply the parameter file at runtime using the following command:
| SELECT XSLTRANSFORM (XML_DOC USING XSL_DOC WITH PARAM AS CLOB (1M))
|
FROM product_details X, PARM_TAB P WHERE X.DOCID=P.DOCID;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The result is HTML, but with content determined by the parameter file and tests done against the content
of the XML document:
<html>
<head>
</head>
<body>
<h1></h1>
<table border="1">
<th>
<tr>
<td width="200">product Name</td>
<td width="50">Details</td>
</tr>
</th>
</table>
</body>
</html>
| In other applications, the output of XSLTRANSFORM might not be HTML but rather another XML
| document or a file using a different data format, such as an EDI file.
|
|
|
|
For data exchange applications, the parameter file could contain EDI or SOAP file header information
such as e-mail or port addresses, or other critical data unique to a particular transaction. Since the XML
used in the above examples is an inventory record, it is easy to imagine using XSLT to repackage this
record for exchange with a client's purchasing system.
| Example: Using XSLT to remove namespaces

| XML documents you receive might contain unneeded or incorrect namespace information. You can use
| XSLT style sheets to remove or manipulate the namespace information in the documents.
| The following examples show how to use XSLT to remove namespace information from an XML
| document. The examples store the XML document and the XSLT stylesheets in XML columns and use the
| XSLTRANSFORM function to convert the XML document using one of the XSLT stylesheets.
|
|
|
|
The following CREATE statements create the tables XMLDATA and XMLTRANS. XMLDATA contains a
sample XML document, and XMLTRANS contains XSLT stylesheets.
|
|
|
|
|
|
|
|
|
Add the sample XML document to the XMLDATA table using the following INSERT statement.
CREATE TABLE XMLDATA (ID BIGINT NOT NULL PRIMARY KEY, XMLDOC XML );
CREATE TABLE XMLTRANS (XSLID BIGINT NOT NULL PRIMARY KEY, XSLT XML );
insert into XMLDATA (ID, XMLDOC) values ( 1,

<newinfo xmlns="http://mycompany.com">

<customerinfo xmlns="http://oldcompany.com" xmlns:d="http://test" Cid="1004">
<name>Matt Foreman</name>
278
|
|
|
|
|
|
|
|
|
|
|
|
<pcode-zip>M3Z 5H9</pcode-zip>
</addr >
<phone type="work" >905-555-4789</phone>
<h:phone xmlns:h="http://test1" type="home">416-555-3376</h:phone>
<d:assistant>
<name>Gopher Runner</name>
<h:phone xmlns:h="http://test1" type="home">416-555-3426</h:phone>
</d:assistant>
</customerinfo>
</newinfo>
);
Example XSLT stylesheet that removes all namespaces
|
|
|
The following example uses an XSLT stylesheet to remove all namespace information from the XML
document stored in the table XMLDATA. The examples stores the stylesheet in the table XMLTRANS and
uses a SELECT statement to apply the stylesheet to the XML document.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add the stylesheet to the XMLTRANS table using the INSERT statement.
|
|
|
|
The following SELECT statement converts the sample XML document using the XSLT stylesheet.
|
|
|
|
|
|
|
|
|
|
|
The XSLTRANSFORM command converts the XML document using the first XSLT stylesheet and returns
the following XML with all the namespace information removed.
insert into XMLTRANS (XSLID, XSLT) values ( 1,

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>

<xsl:template match="comment()">
<xsl:copy>
</xsl:copy>
</xsl:template>
<xsl:template match="*">

<xsl:element name="{local-name()}">

<xsl:for-each select="@*">

<xsl:attribute name="{local-name()}">
<xsl:value-of select="."/>
</xsl:attribute>
</xsl:for-each>
</xsl:element>
</xsl:template>
</xsl:stylesheet>
) ;
SELECT XSLTRANSFORM (XMLDOC USING XSLT )

FROM XMLDATA, XMLTRANS
where ID = 1 and XSLID = 1

<newinfo>
<customerinfo Cid="1004">
SQL programming
279
|
|
</addr>
|
|
|
<assistant>
|
|
|
</assistant>
| </customerinfo>
| </newinfo>
| Example XSLT stylesheet that keeps the namespace binding for an element
|
|
|
|
The following example uses an XSLT stylesheet keeps the namespace binding for only the phone
elements. The name of the element is specified in the XSLT variable mynode. The example stores the
stylesheet in the table XMLTRANS and uses a SELECT statement to apply the stylesheet to the XML
document.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add the stylesheet to the XMLTRANS table using the following INSERT statement.
insert into XMLTRANS (XSLID, XSLT) values ( 2,
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:variable name ="mynode">phone</xsl:variable>

<xsl:template match="comment()">
<xsl:copy>
</xsl:copy>
</xsl:template>
<xsl:template xmlns:d="http://test" xmlns:h="http://test1" match="*">
<xsl:choose>

<xsl:when test="local-name() = $mynode " >
<xsl:element name="{name()}">

</xsl:attribute>
</xsl:for-each>
</xsl:element>
</xsl:when>

<xsl:otherwise>
<xsl:element name="{local-name()}">

</xsl:attribute>
</xsl:for-each>
</xsl:element>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:stylesheet>
);
280
|
|
|
|
|
The following SELECT statement converts the sample XML document using the second XSLT stylesheet
since XSLID = 2 is specified.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The XSLTRANSFORM command converts the XML document using the second XSLT stylesheet and
returns the following XML with the namespaces for only the phone elements.
|
|
|
Important considerations for transforming XML documents
|
|
Note the following when transforming XML documents:

v Source XML documents must be single-rooted and well-formed.
|
|
v Because XSLT transformation by default produces UTF-8 characters, the output stream might lose
characters if inserted into a character column that is not Unicode.
|
|
|
Restrictions
|
|
v Transformation with more than one stylesheet document (using an xsl:include declaration) is not
supported.
|
|
Special character handling in SQL/XML publishing functions
SQL values to XML values
|
|
Certain characters are considered special characters within XML documents, and must appear in their
escaped format, using their entity representation. These special characters are as follows:
Table 50. Special characters and their entity representations
Special character
Entity representation
<
<
SELECT XSLTRANSFORM (XMLDOC USING XSLT)

FROM XMLDATA, XMLTRANS
where ID = 1 and XSLID = 2 ;

<newinfo>
</addr>
<h:phone xmlns:h="http://test1" type="home">
416-555-3376
</h:phone>
<assistant>
<h:phone xmlns:h="http://test1" type="home">
416-555-3426
</h:phone>
</assistant>
</customerinfo>
</newinfo>
When using the built-in XSLTRANSFORM function to convert XML documents some important
considerations and restrictions apply.
v Only the W3C XSLT Version 1.10 Recommendation is supported.

v All parameters and the result type must be SQL types; they cannot be file names.
SQL/XML publishing functions have a default behavior for handling special characters.
SQL programming
281
| Table 50. Special characters and their entity representations (continued)

| Special character
| >
>
| &
&
| "
|
"
| When publishing SQL values as XML values using the SQL/XML publishing functions, these special
| characters are escaped and replaced with their predefined entities.
| SQL identifiers and QNames
|
|
|
|
|
When publishing or constructing XML values from SQL values, it can be necessary to map an SQL
identifier to an XML qualified name, or QName. The set of characters that are allowed in delimited SQL
identifiers differs, however, from those permitted in a QName. This difference means that some
characters used in SQL identifiers will not be valid in QNames. These characters are therefore substituted
with their entity representation in the QName.
| For example, consider the delimited SQL identifier "phone@work". Because the @ character is not a valid
| character in a QName, the character is escaped, and the QName becomes: phone@work.
|
|
|
|
Note that this default escape behavior applies only to column names. For SQL identifiers that are
provided as the element name in XMLELEMENT, or as a name in the AS clause of XMLFOREST and
XMLATTRIBUTES, there are no escape defaults. You must provide valid QNames in these cases. Refer to
the W3C XML namespace specifications for more details on valid names.
| XML serialization
| XML serialization is the process of converting XML data from the format that it has in a DB2 database, to
| the serialized string format that it has in an application.
| You can let the DB2 database manager perform serialization implicitly, or you can invoke the
| XMLSERIALIZE function to explicitly request XML serialization. The most common usage of XML
| serialization is when XML data is sent from the database server to the client.
|
|
|
|
Implicit serialization is the preferred method in most cases because it is simpler to code, and sending
XML data to the client allows the DB2 client to handle the XML data properly. Explicit serialization
requires additional handling, as described below, which is automatically handled by the client during
implicit serialization.
| In general, implicit serialization is preferable because it is more efficient to send data to the client as XML
| data. However, under certain circumstances (described later), it is better to do an explicit
| XMLSERIALIZE.
| The best data type to which to convert XML data is the BLOB data type, because retrieval of binary data
| results in fewer encoding issues.
| Implicit XML serialization
|
|
|
|
|
With implicit serialization for DB2 CLI and embedded SQL applications, the DB2 database server adds an
XML declaration with the appropriate encoding specified to the data. For .NET applications, the DB2
database server also adds an XML declaration. For Java applications, depending on the SQLXML object
methods that are called to retrieve the data from the SQLXML object, the data with an XML declaration
added by the DB2 database server will be returned.
282
|
|
|
|
|
|
|
|
|
|
Example: In a C program, implicitly serialize the customerinfo document for customer ID '1000' and
retrieve the serialized document into a binary XML host variable. The retrieved data is in the UTF-8
encoding scheme, and it contains an XML declaration.
Explicit XML serialization
|
|
After an explicit XMLSERIALIZE invocation, the data has a non-XML data type in the database server,
and is sent to the client as that data type.
|
|
|
The XMLSERIALIZE scalar function lets you specify:

v The SQL data type to which the data is converted when it is serialized
The data type is a character, graphic, or binary data type.
|
|
v Whether the output data should include the explicit encoding specification (EXCLUDING
XMLDECLARATION or INCLUDING XMLDECLARATION).
The output from XMLSERIALIZE is Unicode, character, or graphic data.
|
|
|
|
If you retrieve the serialized data into an non-binary data type, the data is converted to the application
encoding, but the encoding specification is not modified. Therefore, the encoding of the data most likely
will not agree with the encoding specification. This situation results in XML data that cannot be parsed
by application processes that rely on the encoding name.
|
|
In general, implicit serialization is preferable because it is more efficient to send data to the client as XML
data. However, when the client does not support XML data, it is better to do an explicit XMLSERIALIZE:
|
|
|
If the client is an earlier version that does not support the XML data type, and you use implicit XML
serialization, the DB2 database server converts the data to a CLOB or DBCLOB before sending the data to
the client.
If you want the retrieved data to be some other data type, you can use XMLSERIALIZE.
|
|
|
|
|
|
|
|
|
|
|
|
Example: XML column Info in sample table Customer contains a document that contains the hierarchical
equivalent of the following data:
|
|
|
|
Invoke XMLSERIALIZE to serialize the data and convert it to a BLOB type before retrieving it into a host
variable.

SQL TYPE IS XML AS BLOB (1M) xmlCustInfo;
...
EXEC SQL SELECT INFO INTO :xmlCustInfo
FROM Customer
WHERE Cid=1000;
<customerinfo xml:space="default" xmlns="http://posample.org" Cid=1000>

<addr country=Canada>
</addr>
<phone type=work>416-555-1358</phone>
</customerinfo>
SELECT XMLSERIALIZE(Info as BLOB(1M)) into :hostvar from Customer

WHERE CID=1000
SQL programming
283
| Differences in an XML document after storage and retrieval

| When you store an XML document in a DB2 database and then retrieve that copy from the database, the
| retrieved document might not be exactly the same as the original document. This behavior is defined by
| the XML and SQL/XML standard.
| Some of the changes to the document occur when the document is stored. Those changes are:
| v If you execute XMLVALIDATE, the database server:
|
Strips ignorable whitespace from the input document
| v If you do not request XML validation, the database server:
|
Strips boundary whitespace, if you do not request preservation
|
Replaces all carriage return and line feed pairs (U+000D and U+000A), or carriage returns (U+000D),
|
within the document with line feeds (U+000A)
|
|
|
Performs attribute-value normalization, as specified in the XML 1.0 specification

This process causes line feed (U+000A) characters in attributes to be replaced with space characters
(U+0020).
| Additional changes occur when you retrieve the data from an XML column. Those changes are:
| v If the data has an XML declaration before it is sent to the database server, the XML declaration is not
|
preserved.
|
|
|
|
|
With implicit serialization for DB2 CLI and embedded SQL applications, the DB2 database server adds
an XML declaration with the appropriate encoding specified to the data. For .NET applications, the
DB2 database server also adds an XML declaration. For Java applications, depending on the SQLXML
object methods that are called to retrieve the data from the SQLXML object, the data with an XML
declaration added by the DB2 database server will be returned.
|
If you execute the XMLSERIALIZE function, the DB2 database server adds an XML declaration with an
|
encoding specification if you specify the INCLUDING XMLDECLARATION option.
| v Within the content of a document or in attribute values, certain characters are replaced with their
|
predefined XML entities. Those characters and their predefined entities are:
|| Character
Unicode value
| AMPERSAND
U+0026
&
| LESS-THAN SIGN
U+003C
<
|
|
|
|
|
|
|
GREATER-THAN SIGN
U+003E
>
|
|
|
|
|
Data types for archiving XML documents
Using XMLTABLE to reference XML content as a relational table
v Within attribute values, the QUOTATION MARK (U+0022) character is replaced with its predefined
XML entity ".
v If the input document has a DTD declaration, the declaration is not preserved, and no markup based
on the DTD is generated.
v If the input document contains CDATA sections, those sections are not preserved in the output.
Although you can store XML serialized string data in a column of any binary or character type, non-XML
columns should be used only for archiving XML data. The best column data type for archiving XML data
is a binary data type, such as BLOB. Use of a character column for archiving introduces CCSID
conversions, which can make a document inconsistent with its original form.
| The XMLTABLE built-in table function can be used to retrieve the content of an XML document as a
| result set that can be referenced in SQL.
| Assume you have a table called EMP with an XML column defined like this:
284
CREATE TABLE EMP (DOC XML)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The table contains 2 rows, which look like this:
|
|
|
|
|
|
|
|
|
|
|
In the XMLTABLE function invocation, you specify a row-generating XPath expression and, in the
columns clause, one or more column-generating expressions. In this example, the row-generating
expression is the XPath expression $d/dept/employee. The passing clause indicates that the variable $d
refers to the XML column doc of the table emp.
|
|
|
|
The row-generating expression is applied to each XML document in the XML column and produces one
or multiple employee elements (sub-trees) per document. The output of the XMLTABLE function contains
one row for each employee element. Hence, the output produced by the row-generating XPath expression
determines the cardinality of the result set of the SELECT statement.
|
|
|
|
|
|
|
|
|
The COLUMNS clause is used to transform XML data into relational data. Each of the entries in this
clause defines a column with a column name and an SQL data type. In the example above, the returned
rows have 3 columns named empID, firstname, and lastname of data types Integer, Varchar(20), and
Varchar(25), respectively. The values for each column are extracted from the employee elements, which
are produced by the row-generating XPath expression, and cast to the SQL data types. For example, the
path name/first is applied to each employee element to obtain the value for the column firstname. The
row-generating expression provides the context for the column-generating expressions. In other words,
you can typically append a column-generating expression to the row-generating expression to get an idea
of what a given XMLTABLE function returns for a column.
<dept bldg="101">
<employee id="901">
<name>
<first>John</first>
<last>Doe</last>
</name>
<office>344</office>
<salary currency="USD">55000</salary>
</employee>
<employee id="902">
<name>
<first>Peter</first>
<last>Pan</last>
</name>
<phone>905-416-5004</phone>
</employee>
</dept>
<dept bldg="114">
<employee id="903">
<name>
<first>Mary</first>
<last>Jones</last>
</name>
<phone>905-403-6112</phone>
<phone>647-504-4546</phone>
</employee>
</dept>
SELECT X.*
FROM emp,
XMLTABLE ($d/dept/employee PASSING
COLUMNS
empID
INTEGER
firstname VARCHAR(20)
lastname VARCHAR(25)
emp.doc AS "d"
PATH @id,
PATH name/first,
PATH name/last) AS X
SQL programming
285
| The result of the previous query is:

| EMPID
FIRSTNAME
LASTNAME
| ----------- -------------------- ------------------------|
901 John
Doe
|
902 Peter
Pan
|
903 Mary
Jones
| Be aware that the path expressions in the COLUMNS clause must not return more than one item per row.
| If a path expression returns a sequence of two or more items, the XMLTABLE execution will typically fail,
| as it is not possible to convert a sequence of XML values into an atomic SQL value.
| Example: Use XMLTABLE to handle missing elements
| XML data can contain optional elements that are not present in all of your documents
|
|
|
|
|
|
|
|
|
|
|
For example, employee Peter Pan does not have a salary element since it is not a required data field. It's
easy to deal with that because the XMLTABLE function produces NULL values for missing elements. You
can write XMLTABLE queries as if the salary element is always present.
|
|
|
|
|
|
|
This query returns the following result. Note that the salary column for Peter Pan has the NULL value
since the XML document contains no salary value.
|
|
|
|
|
|
|
|
|
|
|
If you want a value other than NULL to appear for a missing element, you can define a default value to
use when the expected element is missing. Here, we define the salary result column to return 0 instead of
NULL.
SELECT X.*
FROM emp,
XMLTABLE ($d/dept/employee PASSING
COLUMNS
empID
INTEGER
salary
INTEGER
EMPID
----------901
902
903
FIRSTNAME
-------------------John
Peter
Mary
doc AS "d"
PATH
PATH
PATH
PATH
@id,
name/first,
name/last,
salary) AS X
LASTNAME
------------------------Doe
Pan
Jones
SALARY
---------55000
64000
SELECT X.*
FROM emp,
XMLTABLE ($d/dept/employee PASSING doc AS "d"
COLUMNS
empID
INTEGER
PATH @id,
PATH name/first,
PATH name/last,
salary
INTEGER DEFAULT 0 PATH salary) AS X
| Example: Use XMLTABLE to subset result data

| Often you want to produce a result containing a subset of the possible rows based on some filtering
| predicate.
|
|
|
|
There are several ways to produce a subset of rows. One solution is to add a WHERE clause to the query
to filter using an output column. This requires all the rows to be generated only to be immediately
discarded. Another solution is to use filtering predicates in the row-generating expression of the
XMLTABLE function.
| Suppose you need to produce rows only for employees in building 114. You can add a corresponding
| condition to the XMLTABLE like this:
286
|
|
|
|
|
|
|
|
SELECT X.*
FROM emp,
XMLTABLE ($d/dept[@bldg="114"]/employee PASSING doc AS "d"
COLUMNS
empID
INTEGER
PATH @id,
PATH name/first,
PATH name/last,
salary
INTEGER DEFAULT 0 PATH salary) AS X
This query returns a single row for Mary Jones, who is the only employee in building 114.
|
|
Example: Use XMLTABLE to handle multiple values
|
|
|
|
|
|
|
|
|
|
|
The path expressions in the COLUMNS clause must not produce more than one item per row. In the
sample documents, notice that the employee Mary Jones has two phone numbers. If you need to query
this data and return a relational table with each employee's name and phone number, the query you
would write might look like this:
|
|
When run against the sample documents, this query fails since there are two values for phone. A different
solution is needed.
Return only first value
|
|
|
|
One way to deal with this issue is to return only one of the multiple phone numbers. If you need
summarized information for each employee, having just one phone number might be enough. Returning
only one occurrence of the phone element can be done with a positional predicate in the XPath
expression for the column phone.
|
|
|
|
|
|
|
|
|
|
Square brackets in XPath are used to specify predicates. To obtain the first phone element for an
employee, use a positional predicate, written either as [1] or [fn:position()=1]. The first notation of [1]
is an abbreviated version of the second.
Return multiple values as XML
|
|
|
|
|
|
|
|
|
|
Another option to return multiple phone numbers for a single employee is to return an XML sequence of
phone elements. To achieve this, the generated phone column needs to be of type XML, which allows you
to return an XML value as the result of the XPath expression.
Sometimes a path expression refers to an item that has multiple values.
SELECT X.*
FROM emp,
COLUMNS
firstname VARCHAR(20) PATH name/first,
lastname VARCHAR(25) PATH name/last,
phone
VARCHAR(12) PATH phone) AS X
SELECT X.*
FROM emp,
COLUMNS
phone
VARCHAR(12) PATH phone[1]) AS X
SELECT X.*
FROM emp,
COLUMNS
phone
XML
PATH phone) AS X
SQL programming
287
|
|
|
|
|
|
The result of this query is:
|
|
|
|
The XML value returned in the phone column for Mary Jones is not a well-formed XML document since
there is no single root element. This value can still be processed by DB2, but you won't be able to insert it
into an XML column or parse it with an XML parser. Combining multiple phone numbers into a single
VARCHAR or XML value may require additional code in your application to use the individual numbers.
FIRSTNAME
----------John
Peter
Mary
LASTNAME
---------Doe
Pan
Jones
PHONE
-----------------<phone>905-416-5004</phone>
<phone>905-403-6112</phone><phone>647-504-4546</phone>
| Return multiple columns

|
|
|
|
|
|
|
|
|
|
|
Another solution is to return each phone number as a separate VARCHAR value by producing a fixed
number of result phone columns. This example uses positional predicates to return phone numbers in
two columns.
|
|
|
|
An obvious drawback to this approach is that a variable number of items is being mapped to a fixed
number of columns. One employee may have more phone numbers than anticipated. Others may have
fewer which results in null values. If every employee has exactly one office phone and one cell phone,
then producing two columns with corresponding names might be very useful.
SELECT X.*
FROM emp,
COLUMNS
phone
VARCHAR(12) PATH phone[1],
phone2
VARCHAR(12) PATH phone[2]) AS X
| Return one row for each value

|
|
|
|
|
|
|
|
|
|
|
Instead of returning the phone numbers in separate columns, you can also use XMLTABLE to return
them in separate rows. In this case, you need to return one row for each phone number instead of one
row for each employee. This may result in repeated information in the columns for the first and last
names.
|
|
|
|
|
|
The result of this query is:
SELECT X.*
FROM emp,
XMLTABLE ($d/dept/employee/phone PASSING
COLUMNS
firstname VARCHAR(20) PATH
lastname VARCHAR(25) PATH
phone
VARCHAR(12) PATH
FIRSTNAME
----------Peter
Mary
Mary
LASTNAME
---------Pan
Jones
Jones
doc AS "d"
../name/first,
../name/last,
.) AS X
PHONE
-----------------905-416-5004
905-403-6112
647-504-4546
| In this result, there is no row for John Doe since he has no phone number.
| Handling non-existent path values
| The previous example did not return a row for employee John Doe because the row-xquery expression
| iterates over all the phone elements and there is no phone element for the employee John Doe. As a
| result, the employee element for John Doe is never processed.
288
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To resolve this issue, you need to use an SQL UNION of two XMLTABLE functions.
|
|
The $d/dept/employee[fn:not(phone)] row expression in the second XMLTABLE returns all employees
with no phone numbers, adding the employee rows that were omitted in the first XMLTABLE.
|
|
|
|
|
Example: Use XMLTABLE with namespaces
|
|
|
|
|
|
|
In XML documents, you declare XML namespaces with the reserved attribute xmlns, whose value must
contain an Universal Resource Identifier (URI). URIs are used as identifiers; they typically look like a
URL but they don't have to point to an existing web page. A namespace declaration can also contain a
prefix, used to identify elements and attributes. Below is an example of a namespace declaration with
and without prefix:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To demonstrate the use of namespaces with XMLTABLE, a sample document is added to the previous
example, so we are working with the following three rows:
SELECT X.*
FROM emp,
XMLTABLE ($d/dept/employee/phone PASSING doc AS "d"
COLUMNS
firstname VARCHAR(20) PATH ../name/first,
lastname VARCHAR(25) PATH ../name/last,
phone
VARCHAR(12) PATH .) AS X
UNION
SELECT Y.*, CAST(NULL AS VARCHAR(12))
FROM emp,
XMLTABLE ($d/dept/employee[fn:not(phone)] PASSING doc AS "d"
COLUMNS
lastname VARCHAR(25) PATH name/last) AS Y
XML namespaces are a W3C XML standard for providing uniquely named elements and attributes in an
XML document. XML documents may contain elements and attributes from different vocabularies but
have the same name. By giving a namespace to each vocabulary, the ambiguity is resolved between
identical element or attribute names.
xmlns:ibm = "http://www.ibm.com/xmltable/"
xmlns = "http://www.ibm.com/xmltable/"
<dept bldg="101">
<employee id="901">
<name>
<first>John</first>
<last>Doe</last>
</name>
</employee>
<employee id="902">
<name>
<first>Peter</first>
<last>Pan</last>
</name>
<phone>905-416-5004</phone>
</employee>
</dept>
<dept bldg="114">
<employee id="903">
<name>
<first>Mary</first>
<last>Jones</last>
</name>
<phone>905-403-6112</phone>
SQL programming
289
|
<phone>647-504-4546</phone>
|
|
</employee>
| </dept>
| <ibm:dept bldg="123" xmlns:ibm="http://www.ibm.com/xmltable">
|
<ibm:employee id="144">
|
<ibm:name>
|
<ibm:first>James</ibm:first>
|
<ibm:last>Bond</ibm:last>
|
</ibm:name>
|
<ibm:office>007</ibm:office>
|
<ibm:phone>905-007-1007</ibm:phone>
|
<ibm:salary currency="USD">77007</ibm:salary>
|
</ibm:employee>
| </ibm:dept>
|
|
|
|
|
|
|
|
|
|
In order to return all the employees in the database, you can use the * wildcard for the namespace prefix
in the path expressions. This causes all elements to be considered, regardless of namespaces, because this
wildcard (*) matches any namespace including no namespace.
SELECT X.*
FROM emp,
XMLTABLE ($d/*:dept/*:employee PASSING doc AS "d"
COLUMNS
empID
INTEGER
PATH @*:id,
firstname VARCHAR(20) PATH *:name/*:first,
lastname VARCHAR(25) PATH *:name/*:last) AS X
| The result of the query is:

| EMPID
FIRSTNAME
| ----------- -------------------|
901 John
|
902 Peter
|
903 Mary
|
144 James
|
|
|
|
LASTNAME
------------------------Doe
Pan
Jones
Bond
For this specific data, the namespace wildcard for the attribute @id was not strictly necessary. The reason
is that the @id attribute employee James Bond has no namespace. Attributes never inherit namespaces
from their element and also never assume the default namespace. So, unless the attribute name has a
prefix, it doesn't belong to any namespace.
| The use of the wildcard expression is the simplest way to return all employees, regardless of namespace.
| Declaring a default element namespace
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When all the elements you want to query belong to the same namespace, declaring a default element
namespace can be the simplest way to write your queries. You just need to declare the default namespace
in the beginning of your XPath expression and, after that, all unqualified elements you reference are tied
to that namespace.
SELECT X.*
FROM emp,
XMLTABLE (declare default element namespace "http://www.ibm.com/xmltable";
$d/dept/employee PASSING doc AS "d"
COLUMNS
empID
INTEGER
PATH @id,
firstname VARCHAR(20) PATH
declare default element namespace "http://www.ibm.com/xmltable"; name/first,
lastname VARCHAR(25) PATH
declare default element namespace "http://www.ibm.com/xmltable"; name/last) AS X
| The result is:
290
|
|
|
EMPID
FIRSTNAME
LASTNAME
----------- -------------------- ------------------------144 James
Bond
|
|
|
|
The column-generating expressions do not inherit the namespace declaration from the row-generating
expression. Each column-generating expression is a separate XPath query and needs its own namespace
declaration. These namespace declarations may differ from each other, for example, if your document
contains multiple namespaces.
|
|
|
|
|
|
|
Often there is only one namespace, in which case it would be convenient to declare a single namespace
for all expressions in the XMLTABLE function. This can be achieved by using the function
XMLNAMESPACES(). This function allows you to declare a default element namespace and/or several
namespace prefixes to be used within the XMLTABLE function. The advantage of using the
XMLNAMESPACES function is that the declared namespaces are global for all expressions in the
XMLTABLE context, so all the XPath expressions will be aware of these namespaces declarations and
repeated namespace declarations are not required.
|
|
|
|
|
|
|
|
|
|
|
|
The default namespace declared by the XMLNAMESPACES function applies to both the row-generating
expression and all the column-generating expressions. This way only one namespace declaration is
needed for all XPath expressions in an XMLTABLE function. The result of the following query is exactly
the same as the previous example.
Declaring a namespace prefix with XMLNAMESPACES
|
|
|
|
|
|
|
|
|
|
|
|
If you want to select elements and attributes from multiple specific namespaces, then using namespace
prefixes can be your best option. Unless you use the XMLNAMESPACES function, the namespaces
prefixes need to be declared for every expression. But, just like for default element namespaces, you can
use the XMLNAMESPACES function to avoid repeated namespace declarations.
|
|
|
|
Example: Number result rows for XMLTABLE
|
|
|
|
|
|
|
To number the result rows, use the FOR ORDINALITY clause. Note that the numbering starts with 1 for
each document that is input to the XMLTABLE function.
SELECT X.*
FROM emp,
XMLTABLE (XMLNAMESPACES(DEFAULT http://www.ibm.com/xmltable),
$d/dept/employee PASSING doc AS "d"
COLUMNS
empID
INTEGER
PATH @id,
lastname VARCHAR(25) PATH name/last) AS X
SELECT X.*
FROM emp,
XMLTABLE (XMLNAMESPACES(http://www.ibm.com/xmltable AS "ibm"),
$d/ibm:dept/ibm:employee PASSING doc AS "d"
COLUMNS
empID
INTEGER
PATH @id,
firstname VARCHAR(20) PATH ibm:name/ibm:first,
lastname VARCHAR(25) PATH ibm:name/ibm:last) AS X
In some cases, you may want to generate a column that numbers the rows that XMLTABLE produces for
any given document. This can help your application to remember the order in which the values appeared
in each document.
SELECT X.*
FROM emp,
COLUMNS
seqno
FOR ORDINALITY,
SQL programming
291
|
|
|
empID
INTEGER
PATH @id,
lastname VARCHAR(25) PATH name/last) AS X
| The result of the query is:

| SEQNO
EMPID
FIRSTNAME
| -------- ----------- -------------------|
1
901 John
|
2
902 Peter
|
1
903 Mary
LASTNAME
------------------------Doe
Pan
Jones
Updating XML data
|
|
|
|
To update data in an XML column, use the SQL UPDATE statement. Include a WHERE clause when you
want to update specific rows. The entire column value will be replaced. The input to the XML column
must be a well-formed XML document. The application data type can be an XML, character, or binary
type.
| When you update an XML column, you might also want to validate the input XML document against a
| registered XML schema. You can do that with the XMLVALIDATE function.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following examples demonstrate how XML data can be updated in XML columns. The examples use
table MyCustomer, which is a copy of the sample Customer table. The examples assume that MyCustomer
already contains a row with a customer ID value of 1004. The XML data that updates existing column
data is assumed to be stored in a file c7.xml, whose contents look like this:
|
|
|
|
|
|
|
|
|
|
|
Example: In a JDBC application, read XML data from file c7.xml as binary data, and use it to update the
data in an XML column:
|
|
|
|
|
|
|
|
|
|
|
Example: In an embedded C application, update data in an XML column from a binary XML host
variable:

<name>Christine Haas</name>
<street>12 Topgrove</street>
<pcode-zip>N9Y-8G9</pcode-zip>
</addr>
</customerinfo>
PreparedStatement updateStmt = null;

String sqls = null;
int cid = 1004;
sqls = "UPDATE MyCustomer SET Info=? WHERE Cid=?";
updateStmt = conn.prepareStatement(sqls);
updateStmt.setInt(1, cid);
File file = new File("c7.xml");
updateStmt.setBinaryStream(2, new FileInputStream(file), (int)file.length());
updateStmt.executeUpdate();

sqlint64 cid;
SQL TYPE IS XML AS BLOB (10K) xml_hostvar;
...
cid=1004;
/* Read data from file c7.xml into xml_hostvar */
...
EXEC SQL UPDATE MyCustomer SET Info=:xml_hostvar WHERE Cid=:cid;
292
|
|
|
In these examples, the value of the Cid attribute within the <customerinfo> element happens to be stored
in the Cid relational column as well. The WHERE clause in the UPDATE statements uses the relational
column Cid to specify the rows to update.
|
|
|
Deletion of XML data from tables
|
|
|
An XML column must either be NULL or contain a well-formed XML document. To delete an XML
document from an XML column without deleting the row, use the UPDATE statement with SET NULL,
to set the column to NULL, if the column is defined as nullable.
|
|
|
The following example demonstrates how XML data can be deleted from XML columns. The example
uses table MyCustomer, which is a copy of the sample Customer table, and assume that MyCustomer has
been populated with all of the Customer data.
|
|
Example: Delete the rows from table MyCustomer for which the Cid column value is 1002.
XML schema repository
The XML schema repository (XSR) is a set of tables containing information about XML schemas.
|
|
|
|
XML instance documents might contain a reference to a Uniform Resource Identifier (URI) that points to
an associated XML schema. This URI is required to process the instance documents. The DB2 database
system manages dependencies on such externally referenced XML artifacts with the XSR without
requiring changes to the URI location reference.
|
|
|
Without this mechanism to store associated XML schemas, an external resource may not be accessible
when needed by the database. The XSR also removes the additional overhead required to locate external
documents, along with the possible performance impact.
|
|
An XML schema consists of a set of XML schema documents. To add an XML schema to the DB2 XSR,
you register XML schema documents to DB2, by calling the following DB2-supplied stored procedures:
|
|
|
|
|
|
SYSPROC.XSR_REGISTER
Begins registration of an XML schema. You call this stored procedure when you add the first
XML schema document to an XML schema.
|
|
|
|
|
|
|
SYSPROC.XSR_ADDSCHEMADOC
Adds additional XML schema documents to an XML schema that you are in the process of
registering. You can call SYSPROC.XSR_ADDSCHEMADOC only for an existing XML schema
that is not yet complete.
|
|
|
SYSPROC.XSR_COMPLETE
Completes the registration of an XML schema.
|
|
|
|
To delete rows that contain XML documents, use the SQL DELETE statement. Include a WHERE clause
when you want to delete specific rows.
DELETE FROM MyCustomer WHERE Cid=1002
CALL SYSPROC.XSR_REGISTER (user1, POschema,

http://myPOschema/PO,
:content_host_var, NULL)
CALL SYSPROC.XSR_ADDSCHEMADOC (user1, POschema,

http://myPOschema/address,
:content_host_var, NULL)
CALL SYSPROC.XSR_COMPLETE (user1, POschema, :schemaproperty_host_var, 0)
During XML schema completion, DB2 resolves references inside XML schema documents to other
XML schema documents. An XML schema document is not checked for correctness when
registering or adding documents. Document checks are performed only when you complete the
XML schema registration.
SQL programming
293
| To remove an XML schema from the DB2 XML schema repository, you can:
| v call the SYSPROC.XSR_REMOVE stored procedure or
| v use the DROP XSROBJECT SQL statement.
|
Independent ASP considerations for the XML Schema Repository (XSR)
| Because an independent auxiliary storage pool (ASP) can be switched between multiple systems, there
| are some additional considerations for administering XML schemas on an ASP.
| Use of an XML schema must be contained on the independent ASP where it was registered. You cannot
| reference an XML schema that is defined in a different independent ASP group or in the system ASP
| when the job is connected to the independent ASP.
|
Application programming language support
| You can write applications to store XML data in DB2 databases tables, retrieve data from tables, or call
| stored procedures or user-defined functions with XML parameters.
|
|
|
|
|
You can use any of the following languages to write your applications:
v ILE RPG
v ILE COBOL
v C and C++ (embedded SQL or DB2 CLI)
v Java (JDBC or SQLJ)
| An application program can retrieve an entire document that is stored in an XML column.
| When an application provides an XML value to a DB2 database server, the database server converts the
| data from the XML serialized string format to an XML value with the specified CCSID.
| When an application retrieves data from XML columns, the DB2 database server converts the data from
| the XML value, with the specified CCSID, to the XML serialized string format. In addition, the database
| server might need to convert the output data from the XML CCSID to the string CCSID.
| When you retrieve XML data, you need to be aware of the effect of CCSID conversion on data loss. Data
| loss can occur when characters in the source XML CCSID cannot be represented in the target string's
| CCSID.
| When you fetch an XML document, you retrieve the serialized form of a document into an application
| variable.
| XML column inserts and updates in CLI applications
| When you update or insert data into XML columns of a table, the input data must be in the serialized
| string format.
| For XML data, you use SQLBindParameter() to bind parameter markers to input data buffers.
| The SQL XML data type can be bound to the following application C character and graphic data types:
| v SQL_C_CHAR
| v SQL_VARCHAR
| v SQL_C_WCHAR
| v SQL_VARGRAPHIC
| The following character LOB data types:
| v SQL_C_CLOB
| v SQL_C_CLOB_LOCATOR
294
|
|
|
|
|
and the following binary data types:

v SQL_C_BINARY
v SQL_C_BLOB
v SQL_C_BLOB_LOCATOR
v SQL_C_BINARY
|
|
|
When you bind a data buffer that contains XML data as a binary data type, DB2 CLI processes the XML
data as internally encoded data. This is the preferred method because it avoids the overhead and
potential data loss of character conversion when character types are used.
|
|
Note: The XML data should be bound to a binary data type when the XML is received from many
sources with different encoding schemes.
|
|
|
|
When you bind a data buffer that contains XML data as SQL_C_CHAR or SQL_C_WCHAR, DB2 CLI
processes the XML data as externally encoded data. DB2 CLI determines the encoding of the data as
follows:
v If the C type is SQL_C_WCHAR, DB2 CLI assumes that the data is encoded as UTF-16.
|
|
v If the C type is SQL_C_CHAR, DB2 CLI assumes that the data is encoded in the application's
single-byte default CCSID.
|
|
If you want the database server to implicitly parse the data before storing it in an XML column, the
parameter marker data type in SQLBindParameter() should be specified as SQL_XML.
|
|
|
|
|
|
|
|
|
|
|
|
|
The following example shows how to update XML data in an XML column using the SQL_C_BINARY
type.
|
|
XML data retrieval in CLI applications
|
|
|
|
|
|
|
For XML data, when you use SQLBindCol() to bind columns in a query result set to application variables,
you can specify the application C character and graphic data types, the character and graphic LOB data
types, and the binary data types. When retrieving a result set from an XML column, you should consider
binding your application variable to the binary types. Binding to character types can result in possible
data loss resulting from the CCSID conversion. Data loss can occur when characters in the source XML
CCSID cannot be represented in the target string CCSID. Binding your variable to the binary types avoids
these issues.
|
|
XML data is returned to the application as internally encoded data. DB2 CLI determines the encoding of
the data as follows:
|
|
|
v If the C type is SQL_C_BINARY, DB2 CLI returns the data in the XML value encoding scheme.
v If the C type is SQL_C_CHAR, DB2 CLI returns the data in the application character encoding scheme.
v If the C type is SQL_C_WCHAR, DB2 CLI returns the data in the UTF-16 encoding scheme.
char xmlBuffer[10240];
integer length;
// Assume a table named dept has been created with the following statement:
// CREATE TABLE dept (id CHAR(8), deptdoc XML)
// xmlBuffer contains an internally encoded XML document that is to replace
// the existing XML document
length = strlen (xmlBuffer);
SQLPrepare (hStmt, "UPDATE dept SET deptdoc = ? WHERE id = '001'", SQL_NTS);
SQLBindParameter (hStmt, 1, SQL_PARAM_INPUT, SQL_C_BINARY, SQL_XML, 0, 0,
xmlBuffer, 10240, &length);
SQLExecute (hStmt);
When you select data from XML columns in a table, the output data is in the serialized string format.
SQL programming
295
|
|
|
|
The database server performs an implicit serialization of the data before returning it to the application.
You can explicitly serialize the XML data to a specific data type by calling the XMLSERIALIZE function.
Implicit serialization is recommended, however, because explicitly serializing to character types with
XMLSERIALIZE can introduce encoding issues.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following example shows how to retrieve XML data from an XML column into a binary application
variable.
char xmlBuffer[10240];
// xmlBuffer is used to hold the retrieved XML document
integer length;
// Assume a table named dept has been created with the following statement:
// CREATE TABLE dept (id CHAR(8), deptdoc XML)
length = sizeof (xmlBuffer);
SQLExecute (hStmt, "SELECT deptdoc FROM dept WHERE id='001'", SQL_NTS);
SQLBindCol (hStmt, 1, SQL_C_BINARY, xmlBuffer, &length, NULL);
SQLFetch (hStmt);
SQLCloseCursor (hStmt);
// xmlBuffer now contains a valid XML document encoded in UTF-8
| Declaring XML host variables in embedded SQL applications

| To exchange XML data between the database server and an embedded SQL application, you need to
| declare host variables in your application source code.
|
|
|
|
|
|
XML data is stored in an XML data type column in a table. Columns with the XML data type are
described as an SQL_TYP_XML column SQLTYPE, and applications can bind various language-specific
data types for input to and output from these columns or parameters. XML columns can be accessed
directly using SQL or the SQL/XML extensions. The XML data type applies to more than just columns.
Functions can have XML value arguments and produce XML values as well. Similarly, stored procedures
can take XML values as both input and output parameters.
|
|
|
|
|
|
XML data is character in nature and has an encoding that specifies the character set used. The encoding
of XML data can be determined externally, derived from the base application type containing the
serialized string representation of the XML document. It can also be determined internally, which requires
interpretation of the data. For Unicode encoded documents, a byte order mark (BOM), consisting of a
Unicode character code at the beginning of a data stream is recommended. The BOM is used as a
signature that defines the byte order and Unicode encoding form.
|
|
|
|
Existing character. graphic, and binary types, which include CHAR, VARCHAR, CLOB, DBCLOB, and
BLOB may be used in addition to XML host variables for fetching and inserting data. However, they will
not be subject to implicit XML parsing, as XML host variables would. Instead, an explicit XMLPARSE
function with default whitespace stripping is applied.
| To declare XML host variables in embedded SQL applications, in the declaration section of the application
| declare the XML host variables AS LOB data types. The examples shown here are for C, but similar
| syntax exists for the other supported languages.
|
|
|
|
|
|
|
|
|
|
v SQL TYPE IS XML AS CLOB(n) <hostvar_name> to define a CLOB host variable that contains XML data
encoded in the CCSID specified by the SQL_XML_DATA_CCSID QAQQINI file option.
v SQL TYPE IS XML AS DBCLOB(n) <hostvar_name> to define a DBCLOB host variable that contains XML
data. It is encoded in the CCSID specified by the SQL_XML_DATA_CCSID QAQQINI file option if the
option is UCS-2 or UTF-16, otherwise the default CCSID is UTF-16.
v SQL TYPE IS XML AS BLOB(n) <hostvar_name> to define a BLOB host variable that contains XML data
internally encoded.
v SQL TYPE IS XML AS LOCATOR <hostvar_name> to define a locator that contains XML data.
v SQL TYPE IS XML AS CLOB_FILE <hostvar_name> to define a CLOB file that contains XML data encoded
in the file CCSID.
296
|
|
v SQL TYPE IS XML AS DBCLOB_FILE <hostvar_name> to define a DBCLOB file that contains XML data
encoded in the application double-byte default CCSID.
|
|
v SQL TYPE IS XML AS BLOB_FILE <hostvar_name> to define a BLOB file that contains XML data internally
encoded.
Example: Referencing XML host variables in embedded SQL applications:
The following sample applications demonstrate how to reference XML host variables in C and COBOL.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Embedded SQL C application:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Embedded SQL COBOL application:
EXEC SQL BEGIN DECLARE;

SQL TYPE IS XML AS CLOB( 10K ) xmlBuf;
SQL TYPE IS XML AS BLOB( 10K ) xmlblob;
SQL TYPE IS CLOB( 10K ) clobBuf;
// using XML AS CLOB host variable
// The XML value written to xmlBuf will be prefixed by an XML declaration
// similar to: <?xml version = "1.0" encoding = "UTF-8"?>
// Note: The encoding name will depend upon the SQL_XML_DATA_CCSID QAQQINI setting
EXEC SQL SELECT xmlCol INTO :xmlBuf
FROM myTable
WHERE id = 001;
EXEC SQL UPDATE myTable
SET xmlCol = :xmlBuf
WHERE id = 001;
// using XML AS BLOB host variable
// The XML value written to xmlblob will be prefixed by an XML declaration
// similar to: <?xml version = "1.0" encoding = "UTF-8"?>
EXEC SQL SELECT xmlCol INTO :xmlblob
FROM myTable
WHERE id = 001;
SET xmlCol = :xmlblob
WHERE id = 001;
// using CLOB host variable
// The output will be encoded in the application single byte default CCSID,
// but will not contain an XML declaration
EXEC SQL SELECT XMLSERIALIZE (xmlCol AS CLOB(10K)) INTO :clobBuf
FROM myTable
WHERE id = 001;
SET xmlCol = XMLPARSE (:clobBuf PRESERVE WHITESPACE)
WHERE id = 001;
EXEC
01
01
01
EXEC
SQL BEGIN DECLARE SECTION END-EXEC.

xmlBuf USAGE IS SQL TYPE IS XML as CLOB(5K).
clobBuf USAGE IS SQL TYPE IS CLOB(5K).
xmlblob USAGE IS SQL TYPE IS XML AS BLOB(5K).
SQL END DECLARE SECTION END-EXEC.
* using XML AS CLOB host variable

EXEC SQL SELECT xmlCol INTO :xmlBuf
FROM myTable
WHERE id = 001.
SET xmlCol = :xmlBuf
WHERE id = 001.
* using XML AS BLOB host variable
EXEC SQL SELECT xmlCol INTO :xmlblob
FROM myTable
SQL programming
297
|
|
|
|
|
|
|
|
|
|
|
|
WHERE id = 001.
SET xmlCol = :xmlblob
WHERE id = 001.
* using CLOB host variable
EXEC SQL SELECT XMLSERIALIZE(xmlCol AS CLOB(10K)) INTO :clobBuf
FROM myTable
WHERE id= 001.
SET xmlCol = XMLPARSE(:clobBuf) PRESERVE WHITESPACE
WHERE id = 001.
| Recommendations for developing embedded SQL applications with XML:

| The following recommendations and restrictions apply to using XML within embedded SQL applications.
| v Applications must access all XML data in the serialized string format.
|
You must represent all data, including numeric and date time data, in its serialized string format.
| v Externalized XML data is limited to 2 GB.
| v All cursors containing XML data are non-blocking (each fetch operation produces a database server
|
request).
| v Whenever character host variables contain serialized XML data, the host variable CCSID is assumed to
|
be used as the encoding of the data and must match any internal encoding that exists in the data.
| v You must specify a LOB data type as the base type for an XML host variable.
| v When using static SQL, where an XML data type is expected for input, the use of CHAR, VARCHAR,
|
CLOB, DBCLOB, and BLOB host variables will be subject to an XMLPARSE operation with default
|
whitespace handling characteristics ('STRIP WHITESPACE'). Any other non-XML host variable type
|
will be rejected.
| Identifying XML values in an SQLDA:
| To indicate that a base type holds XML data, the sqlname field of the SQLVAR must be updated.
|
|
|
|
|
|
sqlname.length must be 8
The first two bytes of sqlname.data must be X'0000'
The third and fourth bytes of sqlname.data should be X'0000'
The fifth byte of sqlname.data must be X'01' (referred to as the XML subtype indicator only when the
first two conditions are met)
v The remaining bytes should be X'000000'
v
v
v
v
| If the XML subtype indicator is set in an SQLVAR whose SQLTYPE is non-LOB, an SQL0804 error will be
| returned at runtime.
| Note: SQL_TYP_XML can only be returned from the DESCRIBE statement. This type cannot be used for
|
any other requests. The application must modify the SQLDA to contain a valid character or binary
|
type, and set the sqlname field appropriately to indicate that the data is XML.
| Java
| Java and XML
| XML data in JDBC applications:
| In JDBC applications, you can store data in XML columns and retrieve data from XML columns.
| In database tables, the XML built-in data type is used to store XML data in a column.
298
In applications, XML data is in the serialized string format.
In JDBC applications, you can:
|
|
v Store an entire XML document in an XML column using setXXX methods.

v Retrieve an entire XML document from an XML column using getXXX methods.
|
|
|
JDBC 4.0 java.sql.SQLXML objects can be used to retrieve and update data in XML columns. Invocations
of metadata methods, such as ResultSetMetaData.getColumnTypeName return the integer value
java.sql.Types.SQLXML for an XML column type.
XML column updates in JDBC applications:
|
|
When you update or insert data into XML columns of a database table, the input data in your JDBC
applications must be in the serialized string format.
|
|
The following table lists the methods and corresponding input data types that you can use to put data in
XML columns.
Table 51. Methods and data types for updating XML columns
Method
Input data type
PreparedStatement.setAsciiStream
InputStream
PreparedStatement.setBinaryStream
InputStream
PreparedStatement.setBlob
Blob
PreparedStatement.setBytes
byte[]
PreparedStatement.setCharacterStream
Reader
PreparedStatement.setClob
Clob
PreparedStatement.setObject
byte[], Blob, Clob, SQLXML, InputStream, Reader, String
|
|
PreparedStatement.setString
String
|
|
|
|
The encoding of XML data can be derived from the data itself, which is known as internally encoded data,
or from external sources, which is known as externally encoded data. XML data that is sent to the database
server as binary data is treated as internally encoded data. XML data that is sent to the data source as
character data is treated as externally encoded data.
External encoding for Java applications is always Unicode encoding.
|
|
|
|
Externally encoded data can have internal encoding. That is, the data might be sent to the data source as
character data, but the data contains encoding information. The data source handles incompatibilities
between internal and external encoding by generating an error if the external and internal encoding are
incompatible.
|
|
Data in XML columns is stored in the XML column CCSID. The database source handles conversion of
the data from its internal or external encoding to the XML column CCSID.
|
|
|
|
|
|
|
|
|
The following example demonstrates inserting data from an SQLXML object into an XML column. The
data is String data, so the database source treats the data as externally encoded.
public void insertSQLXML()
{
Connection con = DriverManager.getConnection(url);
SQLXML info = con.createSQLXML;
// Create an SQLXML object
String infoData =
SQL programming
299
|
"<customerinfo xmlns=""http://posample.org"" " +
|
"Cid=""1000"" xmlns=""http://posample.org"">...</customerinfo>";
|
cid.setString(cidData);
|
// Populate the SQLXML object
|
int cid = 1000;
|
try {
|
sqls = "INSERT INTO CUSTOMER (CID, INFO) VALUES (?, ?)";
|
insertStmt = con.prepareStatement(sqls);
|
|
insertStmt.setSQLXML(2, info);
|
// Assign the SQLXML object value
|
// to an input parameter
|
if (insertStmt.executeUpdate() != 1) {
|
System.out.println("insertSQLXML: No record inserted.");
|
}
| }
|
catch (IOException ioe) {
|
ioe.printStackTrace();
| }
|
catch (SQLException sqle) {
|
System.out.println("insertSQLXML: SQL Exception: " +
|
sqle.getMessage());
|
System.out.println("insertSQLXML: SQL State: " +
|
sqle.getSQLState());
|
System.out.println("insertSQLXML: SQL Error Code: " +
|
sqle.getErrorCode());
|
}
| }
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following example demonstrates inserting data from a file into an XML column. The data is inserted
as binary data, so the database server honors the internal encoding.
public void insertBinStream()
{
String sqls = null;
int cid = 0;
ResultSet rs=null;
Statement stmt=null;
try {
sqls = "INSERT INTO CUSTOMER (CID, INFO) VALUES (?, ?)";
insertStmt = conn.prepareStatement(sqls);
File file = new File(fn);
insertStmt.setBinaryStream(2,
new FileInputStream(file), (int)file.length());
if (insertStmt.executeUpdate() != 1) {
System.out.println("insertBinStream: No record inserted.");
}
}
catch (IOException ioe) {
ioe.printStackTrace();
}
System.out.println("insertBinStream: SQL Exception: " +
sqle.getMessage());
System.out.println("insertBinStream: SQL State: " +
System.out.println("insertBinStream: SQL Error Code: " +
}
}
300
XML data retrieval in JDBC applications:
|
|
In JDBC applications, you use ResultSet.getXXX or ResultSet.getObject methods to retrieve data from
XML columns.
|
|
When you retrieve data from XML columns of a DB2 table, the output data is in the serialized string
format.
|
|
|
|
|
|
|
You can use one of the following techniques to retrieve XML data:
v Use the ResultSet.getSQLXML method to retrieve the data. Then use a SQLXML.getXXX method to
retrieve the data into a compatible output data type. The SQLXML.getBinaryStream method adds an
XML declaration with encoding specification to the output data. The SQLXML.getString and
SQLXML.getCharacterStream methods do not add the XML declaration.
v Use a ResultSet.getXXX method other than ResultSet.getObject to retrieve the data into a compatible
data type.
|
|
The following table lists the ResultSet methods and corresponding output data types for retrieving XML
data.
Table 52. ResultSet methods and data types for retrieving XML data
Method
Output data type
ResultSet.getAsciiStream
InputStream
ResultSet.getBinaryStream
InputStream
ResultSet.getBytes
byte[]
ResultSet.getCharacterStream
Reader
ResultSet.getSQLXML
SQLXML
|
|
ResultSet.getString
String
|
|
The following table lists the methods that you can call to retrieve data from a java.sql.SQLXML object,
and the corresponding output data types and type of encoding in the XML declarations.
Table 53. SQLXML and DB2Xml methods, data types, and added encoding specifications
|
|
Method
Output data type
Type of XML internal

encoding declaration added
SQLXML.getBinaryStream
InputStream
XML column CCSID encoding
SQLXML.getCharacterStream
Reader
None
SQLXML.getSource
Source
None
|
|
SQLXML.getString
String
None
|
|
|
|
If the application executes the XMLSERIALIZE function on the data that is to be returned, after execution
of the function, the data has the data type that is specified in the XMLSERIALIZE function, not the XML
data type. Therefore, the driver handles the data as the specified type and ignores any internal encoding
declarations.
|
|
|
|
|
|
|
The following example demonstrates retrieving data from an XML column into an SQLXML object, and
then using the SQLXML.getString method to retrieve the data into a string.
public void fetchToSQLXML()
{
System.out.println(">> fetchToSQLXML: Get XML data as an SQLXML object " +
"using getSQLXML");
PreparedStatement selectStmt = null;
SQL programming
301
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| }
String sqls = null, stringDoc = null;

ResultSet rs = null;
try{
sqls = "SELECT info FROM customer WHERE cid = " + cid;
selectStmt = conn.prepareStatement(sqls);
rs = selectStmt.executeQuery();
// Get metadata
// Column type for XML column is the integer java.sql.Types.OTHER
ResultSetMetaData meta = rs.getMetaData();
String colType = meta.getColumnType(1);
System.out.println("fetchToSQLXML: Column type = " + colType);
while (rs.next()) {
// Retrieve the XML data with getSQLXML.
// Then write it to a string with
// explicit internal ISO-10646-UCS-2 encoding.
java.sql.SQLXML xml = rs.getSQLXML(1);
System.out.println (xml.getString());
}
rs.close();
}
System.out.println("fetchToSQLXML: SQL Exception: " +
sqle.getMessage());
System.out.println("fetchToSQLXML: SQL State: " +
System.out.println("fetchToSQLXML: SQL Error Code: " +
}
| The following example demonstrates retrieving data from an XML column into a String variable.
| public void fetchToString()
|
{
|
System.out.println(">> fetchToString: Get XML data " +
|
"using getString");
|
PreparedStatement selectStmt = null;
|
String sqls = null, stringDoc = null;
|
ResultSet rs = null;
|
|
try{
|
sqls = "SELECT info FROM customer WHERE cid = " + cid;
|
selectStmt = conn.prepareStatement(sqls);
|
rs = selectStmt.executeQuery();
|
|
// Get metadata
|
// Column type for XML column is the integer java.sql.Types.OTHER
|
ResultSetMetaData meta = rs.getMetaData();
|
String colType = meta.getColumnType(1);
|
System.out.println("fetchToString: Column type = " + colType);
|
|
while (rs.next()) {
|
stringDoc = rs.getString(1);
|
System.out.println("Document contents:");
|
System.out.println(stringDoc);
|
}
|
|
System.out.println("fetchToString: SQL Exception: " +
|
sqle.getMessage());
|
System.out.println("fetchToString: SQL State: " +
|
|
System.out.println("fetchToString: SQL Error Code: " +
|
|
}
| }
302
Invocation of routines with XML parameters in Java applications:
SQL or external stored procedures and external user-defined functions can include XML parameters.
|
|
|
|
For SQL procedures, those parameters in the stored procedure definition have the XML type. For external
stored procedures and user-defined functions, XML parameters in the routine definition have the XML AS
type. When you call a stored procedure or user-defined function that has XML parameters, you need to
use a compatible data type in the invoking statement.
|
|
|
To call a routine with XML input parameters from a JDBC program, use parameters of the
java.sql.SQLXML type. To register XML output parameters, register the parameters as the
java.sql.Types.SQLXML type.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example: JDBC program that calls a stored procedure that takes three XML parameters: an IN parameter,
an OUT parameter, and an INOUT parameter. This example requires JDBC 4.0.
|
|
|
|
|
|
|
|
|
|
|
Example: SQLJ program that calls a stored procedure that takes three XML parameters: an IN parameter,
an OUT parameter, and an INOUT parameter. This example requires JDBC 4.0.
java.sql.SQLXML in_xml = xmlvar;

java.sql.SQLXML out_xml = null;
java.sql.SQLXML inout_xml = xmlvar;
// Declare an input, output, and
// input/output XML parameter
Connection con;
CallableStatement cstmt;
ResultSet rs;
...
stmt = con.prepareCall("CALL SP_xml(?,?,?)");
// Create a CallableStatement object
cstmt.setObject (1, in_xml);
// Set input parameter
cstmt.setObject (3, inout_xml); // Set inout parameter
cstmt.registerOutParameter (2, java.sql.Types.SQLXML);
// Register out and input parameters
cstmt.registerOutParameter (3, java.sql.Types.SQLXML);
cstmt.executeUpdate();
// Call the stored procedure
out_xml = cstmt.getSQLXML(2); // Get the OUT parameter value
inout_xml = cstmt.getSQLXML(3); // Get the INOUT parameter value
System.out.println("Parameter values from SP_xml call: ");
System.out.println("Output parameter value ");
MyUtilities.printString(out_xml.getString());
// Use the SQLXML.getString
// method to convert the out_xml
// value to a string for printing.
// Call a user-defined method called
// printString (not shown) to print
// the value.
System.out.println("INOUT parameter value "); MyUtilities.printString(inout_xml.getString());
// method to convert the inout_xml
// the value.
java.sql.SQLXML in_xml = xmlvar;

java.sql.SQLXML out_xml = null;
java.sql.SQLXML inout_xml = xmlvar;
// Declare an input, output, and
// input/output XML parameter
...
#sql [myConnCtx] {CALL SP_xml(:IN in_xml,
:OUT out_xml,
:INOUT inout_xml)};
SQL programming
303
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
// Call the stored procedure

System.out.println("Parameter values from SP_xml call: ");
System.out.println("Output parameter value ");
MyUtilities.printString(out_xml.getString());
// method toconvert the out_xml value
// to a string for printing.
// the value.
System.out.println("INOUT parameter value "); MyUtilities.printString(inout_xml.getString());
// method to convert the inout_xml
// the value.
| XML data in SQLJ applications:

| In SQLJ applications, you can store data in XML columns and retrieve data from XML columns.
| In DB2 tables, the XML built-in data type is used to store XML data in a column.
| In applications, XML data is in the serialized string format.
| In SQLJ applications, you can:
| v Store an entire XML document in an XML column using INSERT or UPDATE statements.
| v Retrieve an entire XML document from an XML column using single-row SELECT statements or
|
iterators.
| JDBC 4.0 java.sql.SQLXML objects can be used to retrieve and update data in XML columns. Invocations
| of metadata methods, such as ResultSetMetaData.getColumnTypeName return the integer value
| java.sql.Types.SQLXML for an XML column type.
| XML column updates in SQLJ applications:
| When you update or insert data into XML columns of a table in an SQLJ application, the input data must
| be in the serialized string format.
|
|
|
|
|
|
|
|
|
The host expression data types that you can use to update XML columns are:
v java.sql.SQLXML (requires SQLJ Version 4.0 or later)
v String
v byte
v Blob
v Clob
v sqlj.runtime.AsciiStream
v sqlj.runtime.BinaryStream
v sqlj.runtime.CharacterStream
| For stream types, you need to use an sqlj.runtime.typeStream host expression, rather than a
| java.io.typeInputStream host expression so that you can pass the length of the stream to the JDBC driver.
| The encoding of XML data can be derived from the data itself, which is known as internally encoded data,
| or from external sources, which is known as externally encoded data. XML data that is sent to the database
304
|
|
|
server as binary data is treated as internally encoded data. XML data that is sent to the data source as
character data is treated as externally encoded data. The external encoding is the default encoding for the
JVM.
External encoding for Java applications is always Unicode encoding.
|
|
|
|
Externally encoded data can have internal encoding. That is, the data might be sent to the data source as
character data, but the data contains encoding information. The data source handles incompatibilities
between internal and external encoding by generating an error if the external and internal encoding are
incompatible.
Data in XML columns is stored in the XML column CCSID.
|
|
|
Suppose that you use the following statement to insert data from String host expression xmlString into an
XML column in a table. xmlString is a character type, so its external encoding is used.
|
|
|
|
|
|
|
|
sqlj.runtime.CharacterStream host expression: Suppose that you construct an

sqlj.runtime.CharacterStream host expression, and insert data from the sqlj.runtime.CharacterStream host
expression into an XML column in a table.
sqljXmlCharacterStream is a character type, so its external encoding is used.
|
|
|
|
|
|
Suppose that you retrieve a document from an XML column into a java.sql.SQLXML host expression, and
insert the data into an XML column in a table.
|
|
After you retrieve the data it is still in UTF-8 encoding, so when you insert the data into another XML
column, no conversion occurs.
XML data retrieval in SQLJ applications:
|
|
When you retrieve data from XML columns of a database table in an SQLJ application, the output data
must be explicitly or implicitly serialized.
|
|
|
|
|
|
The host expression or iterator data types that you can use to retrieve data from XML columns are:
v java.sql.SQLXML (SQLJ Version 4.0)
v String
v byte[]
v sqlj.runtime.AsciiStream
v sqlj.runtime.BinaryStream
v sqlj.runtime.CharacterStream
|
|
|
|
If the application does not call the XMLSERIALIZE function before data retrieval, the data is converted
from UTF-8 to the external application encoding for the character data types, or the internal encoding for
the binary data types. No XML declaration is added. If the host expression is an object of the
java.sql.SQLXML or com.ibm.db2.jcc.DB2Xml type, you need to call an additional method to retrieve the
#sql [ctx] {INSERT INTO CUSTACC VALUES (1, :xmlString)};
java.io.StringReader xmlReader =
new java.io.StringReader(xmlString);
sqlj.runtime.CharacterStream sqljXmlCharacterStream =
new sqlj.runtime.CharacterStream(xmlReader, xmlString.length());
#sql [ctx] {INSERT INTO CUSTACC VALUES (4, :sqljXmlCharacterStream)};
java.sql.ResultSet rs = s.executeQuery ("SELECT * FROM CUSTACC");

rs.next();
java.sql.SQLXML xmlObject = (java.sql.SQLXML)rs.getObject(2);
#sql [ctx] {INSERT INTO CUSTACC VALUES (6, :xmlObject)};
SQL programming
305
| data from this object. The method that you call determines the encoding of the output data and whether
| an XML declaration with an encoding specification is added.
| The following table lists the methods that you can call to retrieve data from a java.sql.SQLXML or a
| com.ibm.db2.jcc.DB2Xml object, and the corresponding output data types and type of encoding in the
| XML declarations.
|
Table 54. SQLXML and DB2Xml methods, data types, and added encoding specifications
|
|
Method
Output data type
Type of XML internal encoding

declaration added
SQLXML.getBinaryStream
InputStream
XML column CCSID encoding
SQLXML.getCharacterStream
Reader
None
SQLXML.getSource
Source
None
|
|
SQLXML.getString
String
None
|
|
|
|
If the application executes the XMLSERIALIZE function on the data that is to be returned, after execution
of the function, the data has the data type that is specified in the XMLSERIALIZE function, not the XML
data type. Therefore, the driver handles the data as the specified type and ignores any internal encoding
declarations.
|
|
|
|
Suppose that you retrieve data from an XML column into a String host expression.
#sql iterator XmlStringIter (int, String);
#sql [ctx] siter = {SELECT C1, CADOC from CUSTACC};
#sql {FETCH :siter INTO :row, :outString};
| The String type is a character type, so the data is converted from UTF-8 to the external encoding and
| returned without any XML declaration.
|
|
|
|
|
Suppose that you retrieve data from an XML column into a byte[] host expression.
#sql iterator XmlByteArrayIter (int, byte[]);
XmlByteArrayIter biter = null;
#sql [ctx] biter = {SELECT c1, CADOC from CUSTACC};
#sql {FETCH :biter INTO :row, :outBytes};
| The byte[] type is a binary type, so no data conversion from UTF-8 encoding occurs, and the data is
| returned without any XML declaration.
|
|
|
|
|
|
|
|
Suppose that you retrieve a document from an XML column into a java.sql.SQLXML host expression, but
you need the data in a binary stream.
#sql iterator SqlXmlIter (int, java.sql.SQLXML);
SqlXmlIter SQLXMLiter = null;
java.sql.SQLXML outSqlXml = null;
#sql [ctx] SqlXmlIter = {SELECT c1, CADOC from CUSTACC};
#sql {FETCH :SqlXmlIter INTO :row, :outSqlXml};
java.io.InputStream XmlStream = outSqlXml.getBinaryStream();
| The FETCH statement retrieves the data into the SQLXML object in UTF-8 encoding. The
| SQLXML.getBinaryStream stores the data in a binary stream.
| Routines
| Routines and XML
306
XML support in SQL procedures:
|
|
SQL procedures support parameters and variables of data type XML. They can be used in SQL statements
in the same way as variables of any other data type.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following example shows the declaration, use, and assignment of XML parameters and variables in
an SQL procedure:
|
|
|
In the example above there is a table T1 with an XML column. The SQL procedure accepts two
parameters, parm1 and parm2. parm1 is of the XML data type. Within the SQL procedure an XML variable
is declared named var1.
|
|
The value of parameter parm2 is parsed using the XMLPARSE function and assigned to XML variable
var1. The XML variable value is then also inserted into column C1 in table T1.
Effect of commits and rollbacks on XML parameter and variable values in SQL procedures:
|
|
|
Commits and rollbacks within SQL procedures affect the values of parameters and variables of data type
XML. During the execution of SQL procedures, upon a commit or rollback operation, the values assigned
to XML parameters and XML variables will no longer be available.
|
|
Attempts to reference an SQL variable or SQL parameter of data type XML after a commit or rollback
operation will cause an error to be raised.
|
|
To successfully reference XML parameters and variables after a commit or rollback operation occurs, new
values must first be assigned to them.
|
|
Consider the availability of XML parameter and variable values when adding ROLLBACK and COMMIT
statements to SQL procedures.
XML data type support in external routines:
|
|
External procedures and functions written in programming languages that support parameters and
variables of data type XML:
|
|
|
|
|
These programming languages include:

v ILE RPG
v ILE COBOL
v C
v C++
CREATE TABLE T1(C1 XML) ;

CREATE PROCEDURE proc1(IN parm1 XML, IN parm2 VARCHAR(32000))
LANGUAGE SQL
BEGIN
DECLARE var1 XML;
/* insert the value of parm1 into table T1 */
INSERT INTO T1 VALUES(parm1);
/* parse parameter parm2s value and assign it to a variable */
SET var1 = XMLPARSE(document parm2 preserve whitespace);
/* insert variable var1 into table T1
INSERT INTO T1 VALUES(var1);
END ;
SQL programming
307
| v Java
| XML data type values are represented in external routine code in the same way as character, graphic, and
| binary data types.
|
|
|
|
When declaring external routine parameters of data type XML, the CREATE PROCEDURE and CREATE
FUNCTION statements that will be used to create the routines in the database must specify that the XML
data type is to be stored as a character, graphic, or binary data type. The size of the character, graphic, or
binary value should be close to the size of the XML document represented by the XML parameter.
|
|
|
|
|
|
|
The CREATE PROCEDURE statement below shows a CREATE PROCEDURE statement for an external
procedure implemented in the C programming language with an XML parameter named parm1:
|
|
|
|
|
|
|
|
|
|
|
Similar considerations apply when creating external UDFs, as shown in the example below:
CREATE PROCEDURE myproc(IN parm1 XML AS CLOB(2M), IN parm2 VARCHAR(32000))

LANGUAGE C
FENCED
PARAMETER STYLE SQL
EXTERNAL NAME mylib.myproc;
CREATE FUNCTION myfunc (IN parm1 XML AS CLOB(2M))

RETURNS SMALLINT
LANGUAGE C
PARAMETER STYLE SQL
DETERMINISTIC
NOT FENCED
NULL CALL
NO SQL
NO EXTERNAL ACTION
EXTERNAL NAME mylib1.myfunc
| Within external routine code, XML parameter and variable values are accessed, set, and modified in the
| same way as in database applications.
| Example: XML support in Java (JDBC) procedure:
| Once the basics of Java procedures, programming in Java using the JDBC application programming
| interface (API) are understood, you can start creating and using Java procedures that query XML data.
|
|
|
|
This example of a Java procedure illustrates:

v CREATE PROCEDURE statement for a parameter style JAVA procedure
v Source code for a parameter style JAVA procedure
v Input and output parameters of data type XML
| The Java external code file

| The example shows a Java procedure implementation. The example consists of two parts: the CREATE
| PROCEDURE statement and the external Java code implementation of the procedure from which the
| associated Java class can be built.
| The Java source file that contains the procedure implementations of the following examples is named
| stpclass.java included in a JAR file named myJAR. The file has the following format:
|
|
|
|
|
|
Java external code file format

using System;
import java.lang.*;
import java.io.*;
import java.sql.*;
import java.util.*;
308
|
|
|
|
|
|
public class stpclass

{
...
// Java procedure implementations
...
}
|
|
|
|
It is important to note the name of the class file and JAR name that contains a given procedure
implementation. These names are important, because the EXTERNAL clause of the CREATE
PROCEDURE statement for each procedure must specify this information so that DB2 can locate the class
at run time.
Example: Parameter style JAVA procedure with XML parameters
This example shows the following:
|
|
v CREATE PROCEDURE statement for a parameter style JAVA procedure

v Java code for a parameter style JAVA procedure with XML parameters
|
|
|
This procedure takes an input parameter, inXML, inserts a row including that value into a table,
queriesXML data using both an SQL statement and an XQuery expression, and sets two output
parameters, outXML1, and outXML2.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Code to create a parameter style JAVA procedure with XML parameters

CREATE PROCEDURE xmlProc1 ( IN inNUM INTEGER,
IN inXML XML as CLOB (1K),
OUT out1XML XML as CLOB (1K),
OUT out2XML XML as CLOB (1K) )
DETERMINISTIC
LANGUAGE JAVA
PARAMETER STYLE JAVA
MODIFIES SQL DATA
FENCED
THREADSAFE
PROGRAM TYPE SUB
NO DBINFO
EXTERNAL NAME stpclass.xmlProc1;
public void xmlProc1(int inNum,
CLOB inXML ,
CLOB [] out1XML,
)
throws Exception
{
Connection con = DriverManager.getConnection("jdbc:default:connection");
// Insert data including the XML parameter value into a table
String query = "INSERT INTO xmlDataTable (num, inXML ) VALUES ( ?, ? )" ;
String xmlString = inXML.getCharacterStream() ;
stmt = con.prepareStatement(query);
stmt.setInt(1, inNum);
stmt.setString (2, xmlString );
stmt.executeUpdate();
stmt.close();
// Query and retrieve a single XML value from a table using SQL
query = "SELECT xdata from xmlDataTable WHERE num = ? " ;
stmt = con.prepareStatement(query);
stmt.setInt(1, inNum);
ResultSet rs = stmt.executeQuery();
SQL programming
309
|
|
|
|
|
|
|
|
| }
if ( rs.next() )
{ out1Xml[0] = (CLOB) rs.getObject(1); }
rs.close() ;
stmt.close();
return ;
| Example: XML support in C procedure:

| Once the basics of procedures, the essentials of C routines and XML are understood, you can start
| creating and using C procedures with XML features.
| The example below demonstrates a C procedure with parameters of type XML as well as how to update
| and query XML data.
| C parameter style SQL procedure with XML features
| This example shows the following:
| v CREATE PROCEDURE statement for a parameter style SQL procedure
| v C code for a parameter style SQL procedure with XML parameters
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This procedure receives two input parameters. The first input parameter is named inNum and is of type
INTEGER. The second input parameters is named inXML and is of type XML. The values of the input
parameters are used to insert a row into the table xmlDataTable. Then an XML value is retrieved using an
SQL statement. The retrieved XML value is assigned to the out1XML parameter. No result sets are
returned.
CREATE PROCEDURE xmlProc1 ( IN inNUM INTEGER,
IN inXML XML as CLOB (1K),
OUT out1XML XML as CLOB (1K)
)
LANGUAGE C
PARAMETER STYLE SQL
DETERMINISTIC
MODIFIES SQL DATA
PROGRAM TYPE SUB
EXTERNAL NAME xmlProc1 ;
//*************************************************************************
// Stored Procedure: xmlProc1
//
// Purpose: insert XML data into XML column
//
// Parameters:
//
// IN:
inNum -- the sequence of XML data to be insert in xmldata table
//
inXML -- XML data to be inserted
// OUT: out1XML -- XML data returned - value retrieved using SQL
//*************************************************************************
#include <stdio.h>
#include <string.h>
#include <stdlib.h>
#include <sqlda.h>
#include <sqlca.h>
#include <sqludf.h>
#include <sql.h>
#include <memory.h>
#ifdef __cplusplus
extern "C"
310
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#endif
SQL_API_RC SQL_API_FN testSecA1(sqlint32* inNum,
SQLUDF_CLOB* inXML,
SQLUDF_CLOB* out1XML,
SQLUDF_NULLIND *inNum_ind,
SQLUDF_NULLIND *inXML_ind,
SQLUDF_NULLIND *out1XML_ind,
SQLUDF_TRAIL_ARGS)
{
char *str;
FILE *file;
XML data encoding
|
|
The encoding of XML data can be derived from the data itself, which is known as internally encoded data,
or from external sources, which is known as externally encoded data.
|
|
|
|
|
|
|
The application data type that you use to exchange the XML data between the application and the XML
column determines how the encoding is derived.
v XML data that is in character or graphic application data types is considered to be externally encoded.
Like character and graphic data, XML data that is in these data types is considered to be encoded in
the host variable declared CCSID.
v XML data that is in a binary application data type or binary data that is in a character data type is
considered to be internally encoded.

sqlint32 hvNum1;
SQL TYPE IS XML AS CLOB(200) hvXML1;
SQL TYPE IS XML AS CLOB(200) hvXML2;
/* Check null indicators for input parameters */
if ((*inNum_ind < 0) || (*inXML_ind < 0)) {
strcpy(sqludf_sqlstate, "38100");
strcpy(sqludf_msgtext, "Received null input");
return 0;
}
/* Copy input parameters to host variables */
hvNum1 = *inNum;
hvXML1.length = inXML->length;
strncpy(hvXML1.data, inXML->data, inXML->length);
/* Execute SQL statement */
EXEC SQL
INSERT INTO xmlDataTable (num, xdata) VALUES (:hvNum1, :hvXML1);
/* Execute SQL statement */
EXEC SQL
SELECT xdata INTO :hvXML2
FROM xmlDataTable
WHERE num = :hvNum1;
exit:
/* Set output return code */
*outReturnCode = sqlca.sqlcode;
*outReturnCode_ind = 0;
return 0;
}
SQL programming
311
| Externally coded XML data might contain internal encoding, such as when an XML document in a
| character data type contains an encoding declaration. Externally encoded data sent to a DB2 database is
| checked by the database manager for internal encoding.
| The effective CCSID that is associated with the internal encoding must match the external encoding;
| otherwise, an error occurs.
| Encoding considerations when storing or passing XML data
| XML data must be encoded properly to be stored in a DB2 table. Encoding must be considered when the
| data is retrieved from the table and used with DB2 stored procedures or user-defined functions, or when
| used with external Java applications.
| Encoding considerations for input of XML data to a database:
| The internal and external encoding must be considered when storing XML data in a DB2 table.
| The following rules need to be observed:
| v For externally encoded XML data (data that is sent to the database server using character data types),
|
any internally encoded declaration must match the external encoding, otherwise an error occurs, and
|
the database manager rejects the document.
| v For internally encoded XML data (data that is sent to the database server using binary data types), the
|
application must ensure that the data contains accurate encoding information.
| Encoding considerations for retrieval of XML data from a database:
| When you retrieve XML data from a DB2 table, you need to avoid data loss and truncation. Data loss can
| occur when characters in the source data cannot be represented in the encoding of the target data.
| Truncation can occur when conversion to the target data type results in expansion of the data.
| Encoding considerations for passing XML data in routine parameters:
| In a DB2 database system, several XML data types are available for parameters in a stored procedure or
| user-defined function definition.
| The following XML data types are available:
| XML
For SQL procedures and functions.
| XML AS
|
For external procedures and external user-defined functions.
|
|
|
|
Data in XML AS parameters is subject to character conversion. Any application character or graphic data
type can be used for the parameters in the calling application, but the source data should not contain an
encoding declaration. Additional CCSID conversions may occur, which can make the encoding
information inaccurate. If the data is further parsed in the application, data corruption can result.
| Encoding considerations for XML data in JDBC and SQLJ applications:

|
|
|
|
Typically, there are fewer XML encoding considerations for Java applications than for CLI or embedded
SQL applications. Although the encoding considerations for internally encoded XML data are the same
for all applications, the situation is simplified for externally encoded data in Java applications because the
application CCSID is always Unicode.
| General recommendations for input of XML data in Java applications

| v If the input data is in a file, read the data in as a binary stream (setBinaryStream) so that the database
|
manager processes it as internally encoded data.
312
|
|
|
|
v If the input data is in a Java application variable, your choice of application variable type determines
whether the DB2 database manager uses any internal encoding. If you input the data as a character
type (for example, setString), the database manager converts the data from UTF-16 (the application
CCSID) to the XML column CCSID before storing it.
|
|
|
|
|
|
|
General recommendations for output of XML data in Java applications

v If you output XML data to a file as non-binary data, you should add XML internal encoding to the
output data.
The encoding for the file system might not be Unicode, so string data can undergo conversion when it
is stored in the file.
For an explicit XMLSERIALIZE function with INCLUDING XMLDECLARATION, the database server
adds encoding, and the JDBC driver does not modify it.
|
|
v If the application sends the output data to an XML parser, you should retrieve the data in a binary
application variable, with UTF-8, UCS-2, or UTF-16 encoding.
|
|
|
|
Effects of XML encoding and serialization on data conversion
Encoding scenarios for input of internally encoded XML data to a database:
|
|
The following examples demonstrate how internal encoding affects data conversion and truncation
during input of XML data to an XML column.
|
|
In general, use of a binary application data type minimizes code page conversion problems during input
to a database.
Scenario 1
||
Encoding source
Value
Data encoding
UTF-8 Unicode input data, with or without a UTF-8 BOM or XML encoding declaration
|
|
Host variable data

type
Binary
|
|
|
Host variable
declared CCSID
Not applicable
|
|
|
|
Example input statements:
Character conversion: None.
Data loss: None.
Truncation: None.
Scenario 2
||
Encoding source
Value
Data encoding
UTF-16 Unicode input data containing a UTF-16 BOM or XML encoding declaration
The method of specifying the encoding of XML data, either internally or externally, and the method of
XML serialization affect the conversion of XML data when passing the data between a database and an
application.
INSERT INTO T1 (XMLCOL) VALUES (?)

INSERT INTO T1 (XMLCOL) VALUES
(XMLPARSE(DOCUMENT CAST(? AS BLOB) PRESERVE WHITESPACE))
SQL programming
313
| Encoding source
Value
| Host variable data

| type
Binary
| Host variable
| declared CCSID
|
Not applicable
| Example input statements:

| INSERT INTO T1 (XMLCOL) VALUES (?)
| INSERT INTO T1 (XMLCOL) VALUES
|
| Character conversion: the DB2 database server converts the data from UTF-16 to UTF-8 when it performs
| the XML parse for storage in a UTF-8 XML column.
| Data loss: None.
| Truncation: None.
| Scenario 3
|| Encoding source
Value
| Data encoding
ISO-8859-1 input data containing an XML encoding declaration

| type
Binary
| Host variable
| declared CCSID
|
Not applicable

|
| Character conversion: The DB2 database system converts the data from CCSID 819 to UTF-8 when it
| performs the XML parse for storage in a UTF-8 XML column.
| Data loss: None.
| Truncation: None.
| Scenario 4
|| Encoding source
Value
| Data encoding
Shift_JIS input data containing an XML encoding declaration

| type
Binary
| Host variable
| declared CCSID
|
Not applicable

|
314
|
|
Character conversion: The DB2 database system converts the data from CCSID 943 to UTF-8 when it
performs the XML parse for storage in a UTF-8 XML column.
Data loss: None.
Truncation: None.
Encoding scenarios for input of externally encoded XML data to a database:
|
|
The following examples demonstrate how external encoding affects data conversion and truncation
during input of XML data to an XML column.
|
|
In general, when you use a character application data type, there is not a problem with CCSID
conversion during input to a database.
|
|
Only scenario 1 and scenario 2 apply to Java because the application code page for Java is always
Unicode because character strings in Java are always Unicode.
Scenario 1
||
Encoding source
Value
Data encoding
UTF-8 Unicode input data, with or without an appropriate encoding declaration or BOM
|
|
Host variable data

type
Character
|
|
|
Host variable
declared CCSID
1208 (UTF-8)
|
|
|
|
Data loss: None.
Truncation: None.
Scenario 2
||
Encoding source
Value
Data encoding
UTF-16 Unicode input data, with or without an appropriate encoding declaration or BOM
|
|
Host variable data

type
Graphic
|
|
|
Host variable
declared CCSID
1200 or 13488
|
|
|
|

(XMLPARSE(DOCUMENT CAST(? AS CLOB) PRESERVE WHITESPACE))

(XMLPARSE(DOCUMENT CAST(? AS DBCLOB) PRESERVE WHITESPACE))
SQL programming
315
| Character conversion: The DB2 database system converts the data from UTF-16 to UTF-8 when it performs
| the XML parse for storage in a UTF-8 XML column.
| Data loss: None.
| Truncation: Truncation can occur during conversion from UTF-16 to UTF-8, due to expansion.
| Scenario 3
|| Encoding source
Value
| Data encoding
ISO-8859-1 input data, with or without an appropriate encoding declaration

| type
Character
| Host variable
| declared CCSID
|
819

|
(XMLPARSE(DOCUMENT CAST(? AS CLOB) PRESERVE WHITESPACE))
| Data loss: None.
| Truncation: None.
| Scenario 4
|| Encoding source
Value
| Data encoding
Shift_JIS input data, with or without an appropriate encoding declaration

| type
Graphic
| Host variable
| declared CCSID
|
943

| INSERT INTO T1 VALUES (?)
| INSERT INTO T1 VALUES
|
(XMLPARSE(DOCUMENT CAST(? AS DBCLOB)))
| Data loss: None.
| Truncation: None.
| Encoding scenarios for retrieval of XML data with implicit serialization:
| The following examples demonstrate how the target encoding and application code page affect data
| conversion, truncation, and internal encoding during XML data retrieval with implicit serialization.
316
|
|
Only scenario 1 and scenario 2 apply to Java applications, because the application code page for Java
applications is always Unicode because character strings in Java are always Unicode.
Scenario 1
||
Encoding source
Value
Target data encoding
UTF-8 Unicode
|
|
Target host variable

data type
Binary
|
|
|
Host variable
declared CCSID
Not applicable
|
|
Example output statements:
Data loss: None.
Truncation: None.
|
|
|
Internal encoding in the serialized data: For applications other than Java applications, the data is prefixed by
the following XML declaration:
|
|
|
For Java applications, no encoding declaration is added, unless you cast the data as the
com.ibm.db2.jcc.DB2Xml type, and use a getDB2Xmlxxx method to retrieve the data. The declaration that is
added depends on the getDB2Xmlxxx that you use.
Scenario 2
||
Encoding source
Value
UTF-16 Unicode
|
|

data type
Graphic
|
|
|
Host variable
declared CCSID
1200 or 13488
|
|
Character conversion: Data is converted from UTF-8 to UTF-16.
Data loss: None.
Truncation: Truncation can occur during conversion from UTF-8 to UTF-16, due to expansion.
|
|
|
Internal encoding in the serialized data: For applications other than Java or .NET applications, the data is
prefixed by a UTF-16 Byte Order Mark (BOM) and the following XML declaration:
SELECT XMLCOL FROM T1
<?xml version="1.0" encoding="UTF-8" ?>
SELECT XMLCOL FROM T1
SQL programming
317
| For Java applications, no encoding declaration is added, unless you cast the data as the
| com.ibm.db2.jcc.DB2Xml type, and use a getDB2Xmlxxx method to retrieve the data. The declaration that is
| added depends on the getDB2Xmlxxx that you use.
| Scenario 3
|| Encoding source
Value
| Target data encoding ISO-8859-1 data

| Target host variable
| data type
Character
| Host variable
| declared CCSID
|
819
| Example output statements:

| SELECT XMLCOL FROM T1
| Character conversion: Data is converted from UTF-8 to CCSID 819.
| Data loss: Possible data loss. Some UTF-8 characters cannot be represented in CCSID 819. The DB2
| database system generates an error.
| Truncation: None.
| Internal encoding in the serialized data: The data is prefixed by the following XML declaration:
| <?xml version="1.0" encoding="ISO-8859-1" ?>
| Scenario 4
|| Encoding source
Value
| Target data encoding Windows-31J data (superset of Shift_JIS)

| data type
Graphic
| Host variable
| declared CCSID
|
943

| SELECT XMLCOL FROM T1
| Data loss: Possible data loss. Some UTF-8 characters cannot be represented in CCSID 943. The DB2
| database system generates an error.
| Truncation: Truncation can occur during conversion from UTF-8 to CCSID 943 due to expansion.
| Internal encoding in the serialized data: The data is prefixed by the following XML declaration:
| <?xml version="1.0" encoding="Windows-31J" ?>
318
Encoding scenarios for retrieval of XML data with explicit XMLSERIALIZE:
|
|
|
The following examples demonstrate how the target encoding and application code page affect data
conversion, truncation, and internal encoding during XML data retrieval with an explicit XMLSERIALIZE
invocation.
|
|
Only scenario 1 and scenario 2 apply to Java and .NET applications, because the application code page
for Java applications is always Unicode.
Scenario 1
||
Encoding source
Value
UTF-8 Unicode
|
|

data type
Binary
|
|
|
Host variable
declared CCSID
Not applicable
|
|
Data loss: None.
Truncation: None.
|
|
Internal encoding in the serialized data: The data is prefixed by the following XML declaration:
Scenario 2
||
Encoding source
Value
UTF-16 Unicode
|
|

data type
Graphic
|
|
|
Host variable
declared CCSID
1200 or 13488
|
|
Character conversion: Data is converted from UTF-8 to UTF-16.
Data loss: None.
Truncation: Truncation can occur during conversion from UTF-8 to UTF-16, due to expansion.
|
|
|
|
Internal encoding in the serialized data: None, because EXCLUDING XMLDECLARATION is specified. If
INCLUDING XMLDECLARATION is specified, the internal encoding indicates UTF-8 instead of UTF-16.
This can result in XML data that cannot be parsed by application processes that rely on the encoding
name.
SELECT XMLSERIALIZE(XMLCOL AS BLOB(1M) INCLUDING XMLDECLARATION) FROM T1
SELECT XMLSERIALIZE(XMLCOL AS CLOB(1M) EXCLUDING XMLDECLARATION) FROM T1
SQL programming
319
| Scenario 3
|| Encoding source
Value
| Target data encoding ISO-8859-1 data

| data type
Character
| Host variable
| declared CCSID
|
819

| SELECT XMLSERIALIZE(XMLCOL AS CLOB(1M) EXCLUDING XMLDECLARATION) FROM T1
| Data loss: Possible data loss. Some UTF-8 characters cannot be represented in CCSID 819. If a character
| cannot be represented in CCSID 819, the DB2 database manager inserts a substitution character in the
| output and issues a warning.
| Truncation: None.
|
|
|
|
INCLUDING XMLDECLARATION is specified, the database manager adds internal encoding for UTF-8
instead of ISO-8859-1. This can result in XML data that cannot be parsed by application processes that
rely on the encoding name.
| Scenario 4
|| Encoding source
Value
| Target data encoding Windows-31J data (superset of Shift_JIS)

| data type
Graphic
| Host variable
| declared CCSID
|
943

| SELECT XMLSERIALIZE(XMLCOL AS CLOB(1M) EXCLUDING XMLDECLARATION) FROM T1
| Data loss: Possible data loss. Some UTF-8 characters cannot be represented in CCSID 943. If a character
| cannot be represented in CCSID 943, the database manager inserts a substitution character in the output
| and issues a warning.
| Truncation: Truncation can occur during conversion from UTF-8 to CCSID 943 due to expansion.
|
|
|
|
INCLUDING XMLDECLARATION is specified, the internal encoding indicates UTF-8 instead of
Windows-31J. This can result in XML data that cannot be parsed by application processes that rely on the
encoding name.
320
|
|
|
|
Mappings of encoding names to effective CCSIDs for stored XML data
The QlgCvtTextDescToDesc API is used for mapping the IANA encoding name to the CCSID.
|
|
|
Mappings of CCSIDs to encoding names for serialized XML output data
|
|
That declaration has the following form:
|
|
|
In general, the character set identifier in the encoding declaration describes the encoding of the characters
in the output string. For example, when XML data is serialized to the CCSID that corresponds to the
target application data type, the encoding declaration describes the target application variable CCSID.
|
|
|
Where possible, the DB2 database manager chooses the IANA registry name for the CCSID, as prescribed
by the XML standard. The QlgCvtTextDescToDesc API is used for mapping the CCSID to the IANA
encoding name.
|
|
|
|
Annotated XML schema decomposition, also referred to as "decomposition" or "shredding," is the process
of storing content from an XML document in columns of relational tables. Annotated XML schema
decomposition operates based on annotations specified in an XML schema. After an XML document is
decomposed, the inserted data has the SQL data type of the column that it is inserted into.
|
|
|
|
|
An XML schema consists of one or more XML schema documents. In annotated XML schema
decomposition, or schema-based decomposition, you control decomposition by annotating a document's
XML schema with decomposition annotations. These annotations specify details such as:
v the name of the target table and column the XML data is to be stored in
v the default SQL schema for when a target table's SQL schema is not identified
v any transformation of the content before it is stored
|
|
Refer to the summary of decomposition annotations for further examples of what can be specified
through these annotations.
|
|
The annotated schema documents must be stored in and registered with the XML schema repository
(XSR). The schema must then be enabled for decomposition.
|
|
After the successful registration of the annotated schema, decomposition can be performed by calling the
decomposition stored procedure.
|
|
|
The data from the XML document is always validated during decomposition. If information in an XML
document does not comply with its specification in an XML schema then the data is not inserted into the
table.
|
|
|
|
Decomposing XML documents with annotated XML schemas
|
|
To decompose XML documents using annotated XML schemas:

1. Annotate the schema documents with XML decomposition annotations.
If data that you store in an XML column is in a binary application variable, or is an internally encoded
XML type, the DB2 database manager examines the data to determine the encoding. If the data has an
encoding declaration, the database manager maps the encoding name to a CCSID.
As part of an implicit or explicit XMLSERIALIZE operation, the DB2 database manager adds an encoding
declaration at the beginning of serialized XML output data.
<?xml version="1.0" encoding="encoding-name"?>
When you want to store pieces of an XML document in columns of one or more tables, you can use
annotated XML schema decomposition. This type of decomposition breaks an XML document down for
storage in tables, based on the annotations specified in a registered annotated XML schema.
SQL programming
321
| 2. Register the schema documents and enable the schema for decomposition.
| 3. If any of the registered schema documents that belong to the XML schema have changed, then all
|
XML schema documents for this XML schema must be registered again and the XML schema must be
|
enabled for decomposition again.
| 4. Decompose the XML document by calling the SYSPROC.XDBDECOMPXML stored procedure.
| Registering and enabling XML schemas for decomposition
| Once an annotated schema has been successfully registered and enabled for decomposition, you can use
| it to decompose XML documents.
| v Ensure that at least one element or attribute declaration in the XML schema is annotated with an XML
|
decomposition annotation. This annotated element or attributes must be a descendant of, or itself be, a
|
global element of complex type.
|
|
|
|
|
To register and enable XML schemas for decomposition:

1. Call the XSR_REGISTER stored procedure, passing in the primary schema document.
2. If the XML schema consists of more than one schema document, call the XSR_ADDSCHEMADOC
stored procedure for each of the schema documents that have not yet been registered.
3. Call the XSR_COMPLETE stored procedure with the issuedfordecomposition parameter set to 1.
| Sources for annotated XML schema decomposition

| Annotated XML schema decomposition can be performed on elements or attributes in an XML document,
| and on the results of the db2-xdb:contentHandling or db2-xdb:expression annotations.
| Annotated XML schema decomposition supports decomposition of the following types of content:
| v The value of an attribute or element in the XML document.
| v The value of an element in the XML document, where the exact content depends on the value of the
|
<db2-xdb:contentHandling> annotation. <db2-xdb:contentHandling> values are:
Character data from the element, but not from its descendants
text
|
|
stringValue
Character data from the element and its descendants
|
serializedSubtree
|
Markup of all content between the element's start tag and end tag
| v Values that are generated through the db2-xdb:expression annotation:
|
A value that is based on the content of a mapped attribute or element in the XML document.
|
A generated value that is independent of any values in the XML document.
|
A constant.
|
|
An expression that is specified through the db2-xdb:expression is invoked once for every element or
attribute with which it is associated.
|
|
|
|
|
XML decomposition annotations
|
|
|
|
|
The XML decomposition annotations belong to the http://www.ibm.com/xmlns/prod/db2/xdb1

namespace and are identified by the "db2-xdb" prefix throughout the documentation. You can select your
own prefix; however, if you do, you must bind your prefix to the following namespace:
http://www.ibm.com/xmlns/prod/db2/xdb1. The decomposition process recognizes only annotations
that are under this namespace at the time the XML schema is enabled for decomposition.
Annotated XML schema decomposition relies on annotations added to XML schema documents. These
decomposition annotations function as mappings between the elements or attributes of the XML
document to their target tables and columns in the database. Decomposition processing refers to these
annotations to determine how to decompose an XML document.
322
|
|
|
|
|
The decomposition annotations are recognized by the decomposition process only if they are added to
element and attribute declarations, or as global annotations, in the schema document. They are either
specified as attributes or as part of an <xs:annotation> child element of the element or attribute
declaration. Annotations added to complex types, references, or other XML schema constructs are
ignored.
|
|
|
Although these annotations exist in the XML schema documents, they do not affect the original structure
of the schema document, nor do they participate in the validation of XML documents. They are referred
to only by the XML decomposition process.
|
|
|
|
|
Two annotations that are core features of the decomposition process are: db2-xdb:rowSet and
db2-xdb:column. These annotations specify the decomposed value's target table and column, respectively.
These two annotations must be specified in order for the decomposition process to successfully complete.
Other annotations are optional, but can be used for further control of how the decomposition process
operates.
Specification and scope of XML decomposition annotations:
|
|
You can specify annotations for decomposition as element or attribute declarations in an XML schema
document.
|
|
|
You can do that in either of the following ways:

v As simple attributes in element or attribute declarations
v As structured (complex) child elements of simple element or attribute declarations
Annotations as attributes:
|
|
Annotations specified as simple attributes on element or attribute declarations apply only to that element
or attribute on which it is specified.
|
|
|
|
For example, the db2-xdb:rowSet and db2-xdb:column decomposition annotations can be specified as
attributes. These annotations would be specified as follows:
The db2-xdb:rowSet and db2-xdb:column annotations apply only to this element named isbn.
Annotations as structured child elements:
|
|
|
Annotations specified as structured children elements of an element or attribute declaration must be

specified in the schema document within the <xs:annotation><xs:appinfo></xs:appinfo></xs:annotation>
hierarchy defined by XML Schema.
|
|
|
|
|
|
|
|
|
|
|
|
For example, the db2-xdb:rowSet and db2-xdb:column annotations can be specified as children elements
(they are children of the <db2-xdb:rowSetMapping> annotation) as follows:
<xs:element name="isbn" type="xs:string"

db2-xdb:rowSet="TEXTBOOKS" db2-xdb:column="ISBN"/>
<xs:element name="isbn" type="xs:string">

<xs:annotation>
<xs:appinfo>
<db2-xdb:rowSetMapping>
<db2-xdb:rowSet>TEXTBOOKS</db2-xdb:rowSet>
<db2-xdb:column>ISBN</db2-xdb:column>
</db2-xdb:rowSetMapping>
</xs:appinfo>
</xs:annotation>
</xs:element>
SQL programming
323
|
|
|
|
|
Specifying the db2-xdb:rowSet and db2-xdb:column annotations as children elements is equivalent to

specifying these annotations as attributes. While more verbose than the method of specifying annotations
as attributes, specifying annotations as children elements is required when you need to specify more than
one <db2-xdb:rowSetMapping> for an element or attribute; that is, when you need to specify multiple
mappings on the same element or attribute declaration.
| Global annotations:
| When an annotation is specified as a child of the <xs:schema> element, it is a global annotation that
| applies to all of the XML schema documents that make up the XML schema.
|
|
|
|
|
|
|
|
|
|
|
For example, the <db2-xdb:defaultSQLSchema> annotation indicates the default SQL schema for all
unqualified tables referenced in the XML schema. <db2-xdb:defaultSQLSchema> must be specified as a
child element of <xs:schema>:
<xs:schema>
<xs:annotation>
<xs:appinfo>
<db2-xdb:defaultSQLSchema>admin</db2-xdb:defaultSQLSchema>
</xs:appinfo>
</xs:annotation>
...
</xs:schema>
| This declaration specifies that all unqualified tables across all schema documents that form this XML
| schema will have the SQL schema of "admin".
| XML decomposition annotations - Summary:
|
|
|
|
DB2 supports a set of annotations used by the annotated XML schema decomposition process to map
elements and attributes from an XML document to target database tables. The following summary of
some of the XML decomposition annotations is grouped by the tasks and actions you use the annotations
to perform.
| For more information about a specific annotation, refer to the detailed documentation about it.
|
Table 55. Specifying the SQL schema
Action
XML decomposition annotation
|
|
Specify the default SQL schema for all tables that do not
specify their SQL schema
db2-xdb:defaultSQLSchema
|
|
|
Specify an SQL schema different from the default for a

specific table
db2-xdb:table (<db2-xdb:SQLSchema> child element)
Table 56. Mapping XML elements or attributes to target base tables
Action
|
|
Map a single element or attribute to single column and

table pair
db2-xdb:rowSet with db2-xdb:column as attribute

annotations or db2-xdb:rowSetMapping
|
|
Map a single element or attribute to one or more distinct db2-xdb:rowSetMapping

column and table pairs
|
|
Map multiple elements or attributes to single column

and table pair
db2-xdb:table
|
|
|
Specify ordering dependencies between target tables
db2-xdb:rowSetOperationOrder, db2-xdb:rowSet,
db2-xdb:order
324
Table 57. Specifying the XML data to be decomposed
Action
|
|
Specify the type of content to be inserted for an element

of complex type (text, string, or markup)
db2-xdb:contentHandling
|
|
Specify any content transformation to be applied before

insertion
db2-xdb:normalization, db2-xdb:expression,
db2-xdb:truncate
|
|
|
|
Filter the data to be decomposed based on the item's

content or the context in which it appears
db2-xdb:condition db2-xdb:locationPath
Related reference:
|
|
|
|
|
|
|
|
|
|
|
|
db2-xdb:defaultSQLSchema decomposition annotation on page 326

The db2-xdb:defaultSQLSchema annotation specifies the default SQL schema for all table names
referenced in the XML schema that are not explicitly qualified using the db2-xdb:table annotation.
db2-xdb:table decomposition annotation on page 331
The db2-xdb:table annotation maps multiple XML elements or attributes to the same target column; or
enables you to specify a target table that has an SQL schema different from the default SQL schema
specified by <db2-xdb:defaultSQLSchema>.
db2-xdb:rowSet decomposition annotation on page 327
The db2-xdb:rowSet annotation specifies an XML element or attribute mapping to a target base table.
db2-xdb:column decomposition annotation on page 333
The db2-xdb:column annotation specifies a column name of the table to which an XML element or
attribute has been mapped.
|
|
|
db2-xdb:rowSetMapping decomposition annotation on page 354

The db2-xdb:rowSetMapping annotation maps an XML element or attribute to a single target table and
column to multiple target columns of the same table or to multiple tables and columns.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
db2-xdb:contentHandling decomposition annotation on page 344

The db2-xdb:contentHandling annotation specifies the type of content that will be decomposed into a
table for an element of complex type or simple type.
db2-xdb:normalization decomposition annotation on page 348
The db2-xdb:normalization annotation specifies the normalization of whitespace in the XML data to be
inserted or to be substituted for $DECOMP_CONTENT (when used with db2-xdb:expression).
db2-xdb:expression decomposition annotation on page 338
The db2-xdb:expression annotation specifies a customized expression, the result of which is inserted into
the table this element is mapped to.
db2-xdb:truncate decomposition annotation on page 352
The db2-xdb:truncate annotation specifies whether truncation is permitted when an XML value is inserted
into a character target column.
db2-xdb:condition decomposition annotation on page 341
The db2-xdb:condition annotation specifies a condition that determines if a row will be inserted into a
table. A row that satisfies the condition might be inserted (depending on other conditions for the rowSet,
if any); a row that does not satisfy the condition will not be inserted.
db2-xdb:locationPath decomposition annotation on page 335
The db2-xdb:locationPath annotation maps an XML element or attribute to different table and column
pairs, depending on the path of the element or attribute.
db2-xdb:order decomposition annotation on page 350
The db2-xdb:order annotation specifies the insertion order of rows among different tables.
db2-xdb:rowSetOperationOrder decomposition annotation on page 356
The db2-xdb:rowSetOperationOrder annotation is a parent for one or more db2-xdb:order elements. See
the section for db2-xdb:order for details on usage in defining order of insertion of rows among different
tables.
SQL programming
325
| db2-xdb:defaultSQLSchema decomposition annotation:

| The db2-xdb:defaultSQLSchema annotation specifies the default SQL schema for all table names
| referenced in the XML schema that are not explicitly qualified using the db2-xdb:table annotation.
| Annotation type
| Child element of <xs:appinfo> that is a child of a global <xs:annotation> element.
| How to specify
|
|
|
|
|
|
|
|
|
|
db2-xdb:defaultSQLSchema is specified in the following way (where value represents a valid value for the
annotation):
<xs:schema>
<xs:annotation>
<xs:appinfo>
<db2-xdb:defaultSQLSchema>value</db2-xdb:defaultSQLSchema>
</xs:appinfo>
</xs:annotation>
...
</xs:schema>
| Namespace
| http://www.ibm.com/xmlns/prod/db2/xdb1
| Valid values
|
|
|
|
Either an ordinary or delimited SQL schema name. Ordinary, or undelimited, SQL schema names are
case-insensitive. To specify a delimited SQL schema, use quotation marks that are normally used to
delimit SQL identifiers. SQL schema names that contain the special characters '<' and '&' must be escaped
in the XML schema document.
| Details
|
|
|
|
|
|
All tables referenced in annotated schemas must be qualified with their SQL schema. Tables can be
qualified in two ways, either by explicitly specifying the <db2-xdb:SQLSchema> child element of the
<db2-xdb:table> annotation or by using the <db2-xdb:defaultSQLSchema> global annotation. For any
unqualified table name, the value specified in <db2-xdb:defaultSQLSchema> is used as its SQL schema
name. If multiple schema documents in an annotated schema specify this annotation, all values must be
the same.
| Example
|
|
|
|
|
|
|
|
|
|
|
The following example shows how the ordinary, or undelimited, SQL identifier admin is defined as the
SQL schema for all unqualified tables in the annotated schema:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:db2-xdb="http://www.ibm.com/xmlns/prod/db2/xdb1">
<xs:annotation>
<xs:appinfo>
</xs:appinfo>
</xs:annotation>
...
</xs:schema>
326
|
|
|
|
|
|
|
|
|
|
|
|
The following example shows how the delimited SQL identifier admin schema is defined as the SQL
schema for all unqualified tables in the annotated schema. Note that admin schema must be delimited
with quotation marks:
db2-xdb:rowSet decomposition annotation:
The db2-xdb:rowSet annotation specifies an XML element or attribute mapping to a target base table.
Annotation type
|
|
Attribute of <xs:element> or <xs:attribute>, or child element of <db2-xdb:rowSetMapping> or

<db2-xdb:order>.
How to specify
|
|
|
|
|
|
|
|
|
|
|
|
|
|
db2-xdb:rowSet is specified in any of the following ways (where value represents a valid value for the
annotation):
v <xs:element db2-xdb:rowSet="value" />
v <xs:attribute db2-xdb:rowSet="value" />
v <db2-xdb:rowSetMapping>
Namespace
http://www.ibm.com/xmlns/prod/db2/xdb1
Valid values
|
|
Any identifier that adheres to the rules for SQL identifiers. Refer to the identifiers documentation for
more information.
Details
|
|
|
|
|
|
The db2-xdb:rowSet annotation maps an XML element or attribute to a target base table. This annotation
can either identify a table name directly, or identify a rowSet name in more complex mappings, where the
rowSet is then associated with a table name through the db2-xdb:table annotation. In simple mappings,
this annotation specifies the name of the table the value is to be decomposed into. In more complex
mappings, where multiple rowSets (each with a distinct name) map to the same table, then this
annotation names the rowSet, rather than the table name.
<xs:annotation>
<xs:appinfo>
<db2-xdb:defaultSQLSchema>"admin schema"</db2-xdb:defaultSQLSchema>
</xs:appinfo>
</xs:annotation>
...
</xs:schema>
<db2-xdb:rowSet>
value</db2-xdb:rowSet>
...
v <db2-xdb:order>
<db2-xdb:rowSet>
value</db2-xdb:rowSet>
...
</db2-xdb:order>
SQL programming
327
| The target base table into which this XML element's or attribute's value will be decomposed is
| determined by the presence of other annotations in the set of schema documents that form the annotated
| schema:
| v If the value of db2-xdb:rowSet does not match any of the <db2-xdb:rowSet> children elements of the
|
<db2-xdb:table> global annotation, then the name of the target table is the value specified by this
|
annotation, qualified by an SQL schema defined by the <db2-xdb:defaultSQLSchema> global
|
annotation. This usage of db2-xdb:rowSet is for the case in which, for a particular table, there is only
|
one set of elements or attributes that maps to the table.
| v If the value of db2-xdb:rowSet matches a <db2-xdb:rowSet> child element of the <db2-xdb:table>
|
global annotation, then the name of the target table is the table named in the <db2-xdb:name> child of
|
<db2-xdb:table>. This usage of db2-xdb:rowSet is for the more complex case in which, for a particular
|
table, there are multiple (possibly overlapping) sets of elements or attributes that map to that table.
| Important: Ensure that the table that this annotation refers to exists in the database when the XML
|
schema is registered with the XML schema repository. (The columns specified in the
|
db2-xdb:column annotations must also exist when registering the XML schema.) If the table
|
does not exist, then an error is returned when the XML schema is enabled for decomposition.
|
If <db2-xdb:table> specifies an object other than a table, then an error is returned as well.
|
|
|
|
|
|
When the db2-xdb:rowSet annotation is used, either the db2-xdb:column annotation or the
db2-xdb:condition annotation must be specified. The combination of db2-xdb:rowSet and db2-xdb:column
describe the table and column to which this element or attribute will be decomposed into. The
combination of db2-xdb:rowSet and db2-xdb:condition specifies the condition that must be true for any
rows of that rowSet to be inserted into the table (referred to either directly, or indirectly through the
<db2-xdb:table> annotation).
| Example
| There are two ways of using db2-xdb:rowSet listed above.
| Single set of elements or attributes mapped to a table
| Assume for the following section of an annotated schema that the BOOKCONTENTS table belongs to the
| SQL schema specified by <db2-xdb:defaultSQLSchema>, and that there is no global <db2-xdb:table>
| element present which has a <db2-xdb:rowSet> child element that matches "BOOKCONTENTS".
| <xs:element name="book">
|
<xs:complexType>
|
<xs:sequence>
|
<xs:element name="authorID" type="xs:integer" />
|
<xs:element name="chapter" type="chapterType" maxOccurs="unbounded" />
|
</xs:sequence>
|
<xs:attribute name="isbn" type="xs:string"
|
db2-xdb:rowSet="BOOKCONTENTS" db2-xdb:column="ISBN" />
|
<xs:attribute name="title" type="xs:string" />
|
</xs:complexType>
|
</xs:element>
|
|
<xs:complexType name="chapterType">
|
<xs:sequence>
|
<xs:element name="paragraph" type="paragraphType" maxOccurs="unbounded"
|
db2-xdb:rowSet="BOOKCONTENTS" db2-xdb:column="CHPTCONTENT" />
|
</xs:sequence>
|
<xs:attribute name="number" type="xs:integer"
|
db2-xdb:rowSet="BOOKCONTENTS" db2-xdb:column="CHPTNUM" />
|
<xs:attribute name="title" type="xs:string"
|
db2-xdb:rowSet="BOOKCONTENTS" db2-xdb:column="CHPTTITLE" />
|
</xs:complexType>
328
|
|
|
|
<xs:simpleType name="paragraphType">
<xs:restriction base="xs:string"/>
</xs:simpleType>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Consider the following element from an XML document:
The BOOKCONTENTS table is then populated as follows:
Table 58. BOOKCONTENTS
ISBN
CHPTNUM
CHPTTITLE
CHPTCONTENT
1-11-111111-1
Introduction to XML
XML is fun...
1-11-111111-1
XML and Databases
XML can be used with...
...
...
...
...
|
|
1-11-111111-1
10
Further Reading
Recommended tutorials...
Multiple sets of elements or attributes mapped to the same table
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For the case where there exists a <db2-xdb:rowSet> child element of the <db2-xdb:table> global
annotation that matches the value specified in the db2-xdb:rowSet annotation, the element or attribute is
mapped to a table through the <db2-xdb:table> annotation. Assume for the following section of an
annotated schema that the ALLBOOKS table belongs to the SQL schema specified by
<db2-xdb:defaultSQLSchema>.
<book isbn="1-11-111111-1" title="My First XML Book">

<authorID>22</authorID>

<chapter number="1" title="Introduction to XML">
<paragraph>XML is fun...</paragraph>
...
</chapter>
<chapter number="2" title="XML and Databases">
<paragraph>XML can be used with...</paragraph>
</chapter>
...
<chapter number="10" title="Further Reading">
<paragraph>Recommended tutorials...</paragraph>
</chapter>
...
</book>


<xs:annotation>
<xs:appinfo>
<db2-xdb:table>
<db2-xdb:name>ALLBOOKS</db2-xdb:name>
<db2-xdb:rowSet>book</db2-xdb:rowSet>
<db2-xdb:rowSet>textbook</db2-xdb:rowSet>
</db2-xdb:table>
</xs:appinfo>
</xs:annotation>
<xs:element name="book">
<xs:complexType>
<xs:sequence>
<xs:element name="authorID" type="xs:integer"
db2-xdb:rowSet="book" db2-xdb:column="AUTHORID" />
</xs:sequence>
db2-xdb:rowSet="book" db2-xdb:column="ISBN" />
SQL programming
329
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
db2-xdb:rowSet="book" db2-xdb:column="TITLE" />

</xs:complexType>
</xs:element>
<xs:element name="textbook">
<xs:complexType>
<xs:sequence>
db2-xdb:rowSet="textbook" db2-xdb:column="ISBN" />
<xs:element name="title" type="xs:string"
db2-xdb:rowSet="textbook" db2-xdb:column="TITLE" />
<xs:element name="primaryauthorID" type="xs:integer"
db2-xdb:rowSet="textbook" db2-xdb:column="AUTHORID" />
<xs:element name="coauthorID" type="xs:integer"
minOccurs="0" maxOccurs="unbounded" />
<xs:element name="subject" type="xs:string" />
<xs:element name="edition" type="xs:integer" />
</xs:sequence>
</xs:complexType>
</xs:element>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Consider the following elements from an XML document:
<xs:sequence>
<xs:element name="paragraph" type="paragraphType" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="number" type="xs:integer" />
</xs:complexType>
</xs:simpleType>

</chapter>
</chapter>
</chapter>
</book>
<textbook>
<isbn>0-11-011111-0</isbn>
<title>Programming with XML</title>
<primaryauthorID>435</primaryauthorID>
<subject>Programming</subject>
<edition>4</edition>
<chapter number="1" title="Programming Basics">
<paragraph>Before you being programming...</paragraph>
</chapter>
<chapter number="2" title="Writing a Program">
<paragraph>Now that you have learned the basics...</paragraph>
</chapter>
...
<chapter number="10" title="Advanced techniques">
<paragraph>You can apply advanced techniques...</paragraph>
</chapter>
</textbook>
330
|
|
|
In this example, there are two sets of elements or attributes that map to the table ALLBOOKS:
v /book/@isbn, /book/@authorID, /book/title
v /textbook/isbn, /textbook/primaryauthorID, /textbook/title
The sets are distinguished by associating different rowSet names to each.
Table 59. ALLBOOKS
ISBN
TITLE
AUTHORID
1-11-111111-1
My First XML Book
22
|
|
0-11-011111-0
Programming with XML
435
db2-xdb:table decomposition annotation:
|
|
|
The db2-xdb:table annotation maps multiple XML elements or attributes to the same target column; or
enables you to specify a target table that has an SQL schema different from the default SQL schema
specified by <db2-xdb:defaultSQLSchema>.
Annotation type
Global child element of <xs:appinfo> (which is a child element of <xs:annotation>)
Namespace
Valid structure
|
|
The following are supported children elements of db2-xdb:table, listed in the order in which they must
appear if they are specified:
|
|
<db2-xdb:SQLSchema>
(Optional) The SQL schema of the table.
|
|
|
|
|
<db2-xdb:name>
The name of the base table. This table name, when qualified with the value of either the
preceding <db2-xdb:SQLSchema> annotation or the <db2-xdb:defaultSQLSchema> annotation,
must be unique among all <db2-xdb:table> annotations across the set of XML schema documents
that form the annotated schema.
|
|
|
|
|
|
|
<db2-xdb:rowSet>
All elements and attributes that specify the same value for <db2-xdb:rowSet> form a row.
Because more than one <db2-xdb:rowSet> element can be specified for the same value of
<db2-xdb:name>, more than one set of mappings can be associated with a single table. The
combination of the <db2-xdb:rowSet> value with the columns specified in the db2-xdb:column
annotation allows more than one set of elements or attributes from a single XML document to be
mapped to columns of the same table.
|
|
|
At least one <db2-xdb:rowSet> element must be specified, and each <db2-xdb:rowSet> element
must be unique among all <db2-xdb:table> annotations across the set of XML schema documents
that form the annotated schema, for the annotation to be valid.
|
|
|
|
Whitespace within the character content of the children elements of db2-xdb:table is significant and not
normalized. Content of these elements must follow the spelling rules for SQL identifiers. Undelimited
values are case-insensitive; for delimited values, quotation marks are used as the delimiter. SQL
identifiers that contain the special characters '<' and '&', must be escaped.
SQL programming
331
| Details
| The db2-xdb:table annotation must be used in either of the following cases:
| v when multiple paths are mapped to the same column of a table.
| v when the table that is to hold the decomposed data is not of the same SQL schema as is defined by the
|
<db2-xdb:defaultSQLSchema> annotation.
| Only base tables can be specified; other types of tables, such as temporary or materialized query tables,
| are not supported for this mapping. Views and table aliases are not permitted for this annotation.
| Example
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following example shows how the db2-xdb:table annotation can be used to group related elements
and attributes together to form a row, when multiple location paths are being mapped to the same
column. Consider first the following elements from an XML document (modified slightly from examples
used for other annotations).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Assume that the purpose of this decomposition mapping is to insert rows that consist of author IDs and
their corresponding email addresses into the same table, AUTHORSCONTACT. Notice that author IDs
and email addresses appear in both the <book> element and the <author> element. Thus, more than one
location path will need to be mapped to the same columns of the same table. The <db2-xdb:table>
annotation, therefore, must be used. A section from the annotated schema is presented next, showing how
<db2-xdb:table> is used to associate multiple paths to the same table.
<root>
...
<email>author22@anyemail.com</email>
...
</chapter>
</chapter>
...
</chapter>
</book>
...
<author ID="0800" email="author800@email.com">
<firstname>Alexander</firstname>
<lastname>Smith</lastname>
<activeStatus>0</activeStatus>
</author>
...
<root>


<xs:annotation>
<xs:appinfo>
<db2-xdb:defaultSQLSchema>adminSchema</db2-xdb:defaultSQLSchema>
<db2-xdb:table>
<db2-xdb:SQLSchema>user1</db2-xdb:SQLSchema>
<db2-xdb:name>AUTHORSCONTACT</db2-xdb:name>
<db2-xdb:rowSet>bookRowSet</db2-xdb:rowSet>
<db2-xdb:rowSet>authorRowSet</db2-xdb:rowSet>
</db2-xdb:table>
</xs:appinfo>
</xs:annotation>
332
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<xs:complexType>
<xs:sequence>
<xs:element name="authorID" type="xs:integer"
db2-xdb:rowSet="bookRowSet" db2-xdb:column="AUTHID" />
<xs:element name="email" type="xs:string"
db2-xdb:rowSet="bookRowSet" db2-xdb:column="EMAILADDR" />
</xs:sequence>
<xs:attribute name="isbn" type="xs:string" />
</xs:complexType>
</xs:element>
<xs:element name="author">
<xs:complexType>
<xs:sequence>
<xs:element name="firstname" type="xs:string" />
<xs:element name="lastname" type="xs:string" />
<xs:element name="activeStatus" type="xs:boolean" />
</xs:sequence>
<xs:attribute name="ID" type="xs:integer"
db2-xdb:rowSet="authorRowSet" db2-xdb:column="AUTHID" />
<xs:attribute name="email" type="xs:string"
db2-xdb:rowSet="authorRowSet" db2-xdb:column="EMAILADDR" />
</xs:complexType>
</xs:element>
|
|
|
|
|
|
|
The db2-xdb:table annotation identifies the name of the target table for a mapping with the
db2-xdb:name child element. In this example, AUTHORSCONTACT is the target table. To ensure that the
ID and email addresses from the <book> element are kept separate from those of the <author> element
(that is, each row contains logically related values), the <db2-xdb:rowSet> element is used to associate
related items. Even though in this example, the <book> and <author> elements are separate entities, there
can be cases where the entities to be mapped are not separate and require a logical separation, which can
be achieved through the use of rowSets.
|
|
|
Note that the AUTHORSCONTACT table exists in an SQL schema different from the default SQL schema,
and the <db2-xdb:SQLSchema> element is used to specify this. The resulting AUTHORSCONTACT table
is shown below:
Table 60. AUTHORSCONTACT
AUTHID
EMAILADDR
22
author22@anyemail.com
|
|
0800
author800@email.com
db2-xdb:column decomposition annotation:
|
|
The db2-xdb:column annotation specifies a column name of the table to which an XML element or
attribute has been mapped.
Annotation type
Attribute of <xs:element> or <xs:attribute>, or child element of <db2-xdb:rowSetMapping>
How to specify
|
|
db2-xdb:column is specified in any of the following ways (where value represents a valid value for the
annotation):
SQL programming
333
| v <xs:element db2-xdb:rowSet="value" db2-xdb:column="value" />

| v <xs:attribute db2-xdb:rowSet="value" db2-xdb:column="value" />
| v <db2-xdb:rowSetMapping>
|
<db2-xdb:rowSet>value</db2-xdb:rowSet>
|
<db2-xdb:column>value</db2-xdb:column>
|
...
|
| Namespace
| Valid values
| Any base table column name.
| Details
| v Undelimited column names are case-insensitive.
| v When special characters, such as double quotation marks ("), ampersands (&), or less-than signs (<) are
|
part of SQL identifiers, those special characters need to be replaced by their equivalent XML notations.
|
For example, replace " with ", & with &, and < with <.
| v db2-xdb:column is an optional child element of db2-xdb:rowSetMapping if the db2-xdb:locationPath
|
annotation is present.
| Example
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following example shows how content from the <book> element can be inserted into columns of a
table called BOOKCONTENTS, using the db2-xdb:column annotation. A section of the annotated schema
is presented first.
<xs:complexType>
<xs:sequence>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:sequence>
db2-xdb:rowSet="BOOKCONTENTS"
db2-xdb:column="CHPTCONTENT" />
</xs:sequence>
db2-xdb:column="CHPTNUM" />
db2-xdb:column="CHPTTITLE" />
</xs:complexType>
</xs:simpleType>
334
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The <book> element that is being mapped is presented next, followed by the resulting BOOKCONTENTS
table after the decomposition has completed.
ISBN
CHPTNUM
CHPTTITLE
CHPTCONTENT
1-11-111111-1
Introduction to XML
XML is fun...
1-11-111111-1
XML and Databases
...
...
...
...
|
|
1-11-111111-1
10
Further Reading
Recommended tutorials...
db2-xdb:locationPath decomposition annotation:
|
|
The db2-xdb:locationPath annotation maps an XML element or attribute to different table and column
pairs, depending on the path of the element or attribute.
|
|
The db2-xdb:locationPath annotation is used to describe the mappings for elements or attributes that are
either declared globally or as part of :
|
|
|
v A named model group

v A named attribute group
v A global complex type declaration
v A global element or attribute of simple or complex type
Annotation type
Attribute of <xs:element> or <xs:attribute>, or attribute of <db2-xdb:rowSetMapping>>
How to specify
|
|
|
|
|
|
|
|
|
db2-xdb:locationPath is specified in any of the following ways (where value represents a valid value for
the annotation):
v <xs:element db2-xdb:locationPath="value" />
v <xs:attribute db2-xdb:locationPath="value" />
v

...
</chapter>
</chapter>
...
</chapter>
</book>
<db2-xdb:rowSetMapping> db2-xdb:locationPath="value">
...
</db2-xdb:rowSetMapping>>
SQL programming
335
| Namespace
| Valid values
| The value of db2-xdb:locationPath must have the following syntax:
|
name /
prefix
name
prefix
name
prefix
|
An element or attribute name.
| name
| prefix A namespace prefix.

The namespace prefix must be associated with a namespace in the schema document that
contains the annotation with db2-xdb:locationPath. A namespace prefix binding can be created by
adding a namespace declaration to the <xs:schema> element of the schema document.
|
|
|
| Details
| For element or attribute declarations that cannot be reused (local declarations that are not part of named
| complex type definitions or named model or attribute groups), the db2-xdb:locationPath annotation has
| no effect.
|
|
|
|
|
|
|
|
|
db2-xdb:locationPath should be used when global element or attribute declarations are used as references
from other paths (for example: <xs:element ref="abc">). Because annotations cannot be specified directly
on references, the annotations must be specified on the corresponding global element or attribute
declaration. A global element or attribute can be referenced from many different contexts within the XML
schema. In general, db2-xdb:locationPath should be used to distinguish the mappings in different
contexts. For named complex types, model groups, and attribute groups, the element and attribute
declarations should be annotated for each context in which they are mapped for decomposition. The
db2-xdb:locationPath annotation should be used to specify the target rowSt and column pair for each
path. The same db2-xdb:locationPath value can be used for different rowSet and column pairs.
|
|
|
|
|
When a default namespace and the attributeFormDefault ="unqualified" are specified, decomposition
annotations for unqualified attributes are ignored because the annotation processing treats the attribute as
it if belongs to the default namespace. However, the attributeFormDetail = "unqualified" setting indicates
that the attribute actually belongs to the global namespace. In this case, the mapping for this attribute is
ignored and no value is inserted.
| Example
| The following example shows how the same attribute can be mapped to different tables depending on
| the context in which this attribute appears. A section of the annotated schema is presented first.
|

|
|
db2-xdb:rowSet="BOOKS"
|
db2-xdb:column="TITLE"
|
db2-xdb:locationPath="/books/book/@title">
|
<xs:annotation>
|
<xs:appinfo>
|
<db2-xdb:rowSetMapping> db2-xdb:locationPath="/books/book/chapter/@title">
|
<db2-xdb:rowSet>BOOKCONTENTS</db2-xdb:rowSet>
336
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<db2-xdb:column>CHPTTITLE</db2-xdb:column>
</xs:appinfo>
</xs:annotation>
</xs:attribute>
<xs:element name="books">
<xs:complexType>
<xs:sequence>
<xs:complexType>
<xs:sequence>
</xs:sequence>
<xs:attribute name="isbn" type="xs:string" />
<xs:attribute ref="title" />
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:sequence>
<xs:element name="paragraph" type="paragraphType" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="number" type="xs:integer" />
<xs:attribute ref="title" />
</xs:complexType>
</xs:simpleType>
|
|
|
|
|
Note that there is only one attribute declaration named "title", but there are two references to this
attribute in different contexts. One reference is from the <book> element, and the other is from the
<chapter> element. The value of the "title" attribute needs to be decomposed into different tables
depending on the context. This annotated schema specifies that a "title" value is decomposed into the
BOOKS table if it is a book title and into the BOOKCONTENTS table if it is a chapter title.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The <books> element that is being mapped is presented next, followed by the resulting BOOKS table
after the decomposition has completed.
<books>
...
</chapter>
</chapter>
...
</chapter>
</book>
...
</books>
SQL programming
337
Table 62. BOOKS
ISBN
TITLE
CONTENT
|
|
NULL
My First XML Book
NULL
ISBN
CHPTNUM
CHPTTITLE
CHPTCONTENT
NULL
NULL
Introduction to XML
NULL
NULL
NULL
XML and Databases
NULL
...
...
...
...
|
|
NULL
NULL
Further Reading
NULL
| db2-xdb:expression decomposition annotation:

| The db2-xdb:expression annotation specifies a customized expression, the result of which is inserted into
| the table this element is mapped to.
| Annotation type
| Attribute of <xs:element> or <xs:attribute>, or optional child element of <db2-xdb:rowSetMapping>,
| effective only on annotations that include a column mapping
| How to specify
| db2-xdb:expression is specified in any of the following ways (where value represents a valid value for the
| annotation):
| v <xs:element db2-xdb:expression="value" db2-xdb:column="value" />
| v <xs:attribute db2-xdb:expression="value" db2-xdb:column="value" />
| v
|
|
|
<db2-xdb:column>value</db2-xdb:column>
|
<db2-xdb:expression>value</db2-xdb:expression>
|
...
|
| Namespace
| Valid values
| The value of db2-xdb:expression must have the following syntax, which constitutes a subset of SQL
| expressions:
| expression:
|
|
338
function-name ( expression
)
constant
$DECOMP_CONTENT
$DECOMP_DOCUMENTID
( scalar-fullselect )
expression
+
expression
*
/
CONCAT
( expression )
special-register
CAST ( expression AS data-type )
XML-function
|
|
Details
|
|
|
The db2-xdb:expression annotation enables you to specify a customized expression, which is applied to
the content of the XML element or attribute that is annotated when $DECOMP_CONTENT is used. The
result of evaluating this expression is inserted into the column that is specified during decomposition.
|
|
db2-xdb:expression is useful in cases where you want to insert constant values (such as the name of an
element), or generated values that do not appear in the document.
|
|
|
|
|
db2-xdb:expression must be specified using valid SQL expressions, and the type of the evaluated
expression must be statically determinable and compatible with the type of the target column that the
value is to be inserted into. The following subset of SQL expressions are supported; any other SQL
expressions not described below are unsupported and have an undefined behavior in the context of this
annotation.
|
|
Schema names, table names, and column names in the db2-xdb:expression annotation must use SQL
naming for qualification and are case sensitive only if the names are delimited.
|
|
|
function ( expression-list )
A built-in or user-defined SQL scalar function. A scalar function returns a single value (possibly
null).
|
|
constant
A value that is a string constant or a numeric constant.
|
|
|
$DECOMP_CONTENT
The value of the mapped XML element or attribute from the document, constructed according to
the setting of the db2-xdb:contentHandling annotation.
|
|
|
$DECOMP_DOCUMENTID
The string value specified in the documentid input parameter of the XDBDECOMPXML stored
procedure, which identifies the XML document being decomposed.
|
|
|
( scalar-fullselect )
A fullselect, enclosed in parentheses, that returns a single row consisting of a single column
value. If the fullselect does not return a row, the result of the expression is the NULL value.
|
|
|
expression operator expression

The result of two supported expression operands, as defined in the supported values listing
above.
SQL programming
339
| ( expression )
|
An expression enclosed in parentheses that conforms to the list of supported expressions defined
|
above.
| special-register
|
The name of a supported special register. This setting evaluates to the value of the special register
|
for the current server.
| CAST ( expression AS data-type )
|
The expression cast to the specified SQL data type, if the expression is not NULL. If the
|
expression is NULL, the result is a null value of the SQL data type specified. When inserting a
|
NULL value into a column, the expression must cast NULL into a compatible column type (for
|
example: CAST (NULL AS INTEGER), for an integer column).
| XML-function
|
Any supported SQL/XML function.
| Example
| This example demonstrates the types of operations that you can perform with db2-xdb:expression
| annotations. The example also demonstrates cases in which XML input must be cast to an SQL type.
|
|
|
|
The input XML document looks like this:

<num>
1000.99
</num>
| The annotated XML schema produces a row for a table with the following definition:
| CREATE TABLE TAB1
|
(ASIS
DECIMAL(9,2),
|
ADD
INTEGER,
|
TAX
INTEGER,
|
STR
VARCHAR(25),
|
LITERAL DECIMAL(5,1)
|
SELECT VARCHAR(25))
| The annotated XML schema uses a table with the following definition:
| CREATE TABLE SCH1.TAB2
|
(ID
INTEGER,
|
COL1 VARCHAR(25))
| Table SCH1.TAB2 contains one row with the values (100, 'TAB2COL1VAL').
| <xs:element name="num" type="xs:double">
|
<xs:annotation>
|
<xs:appinfo>
|
<xdb:rowSetMapping>
|
<xdb:rowSet>TAB1</xdb:rowSet>
|
<xdb:column>ASIS</xdb:column>
|
</xdb:rowSetMapping>
|
<xdb:rowSetMapping>
|
|
<xdb:column>ADD</xdb:column>
|
<xdb:expression>
|
CAST(XDB.ADD(1234,CAST($DECOMP_CONTENT AS INTEGER)) AS INTEGER)
|
</xdb:expression>
|
|
<xdb:rowSetMapping>
|
|
<xdb:column>TAX</xdb:column>
|
<xdb:expression>
|
CAST(XDB.TAX(CAST($DECOMP_CONTENT AS DOUBLE)) AS INTEGER)
|
</xdb:expression>
340
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<xdb:rowSetMapping>
<xdb:column>STR</xdb:column>
<xdb:expression>
CAST($DECOMP_CONTENT AS VARCHAR(25))
</xdb:expression>
<xdb:rowSetMapping>
<xdb:column>LITERAL</xdb:column>
<xdb:expression>32.3</xdb:expression>
<xdb:rowSetMapping>
<xdb:column>SELECT</xdb:column>
<xdb:expression>
(SELECT "COL1" FROM "SCH1"."TAB2" WHERE "ID" = 100)
</xdb:expression>
</xs:appinfo>
</xs:annotation>
</xs:element>
|
|
Assume that there is a user-defined function called AuthNumBooks that takes an integer parameter,
which represents the author's ID, and returns the total number of books that author has in the system.
Table 64. TAB1
ASIS
ADD
TAX
STR
LITERAL
SELECT
|
|
1000.99
2234
300
1000.99
32.3
TAB2COL1VAL
db2-xdb:condition decomposition annotation:
|
|
|
The db2-xdb:condition annotation specifies a condition that determines if a row will be inserted into a
table. A row that satisfies the condition might be inserted (depending on other conditions for the rowSet,
if any); a row that does not satisfy the condition will not be inserted.
|
|
The condition is applied regardless of whether the annotation to which it belongs contains a column
mapping.
Annotation type
Attribute of <xs:element> or <xs:attribute>, or optional child element of <db2-xdb:rowSetMapping>.
How to specify
|
|
|
|
|
|
|
|
|
db2-xdb:condition is specified in any of the following ways (where value represents a valid value for the
annotation):
v <xs:element db2-xdb:condition="value" />
v <xs:attribute db2-xdb:condition="value" />
v <db2-xdb:rowSetMapping>
Namespace
<db2-xdb:condition>value</db2-xdb:condition>
...
SQL programming
341
| Valid values
| SQL predicates of the following types:
|
|
|
|
|
|
|
|
v
v
v
v
v
v
v
v
basic
quantified
BETWEEN
DISTINCT
EXISTS
IN
LIKE
NULL
| The predicates must also consist of expressions that are supported by the db2-xdb:expression annotation,
| column names, or both.
| Details
| If the db2-xdb:condition annotation is specified on multiple element or attribute declarations of the same
| rowSet, then the row will be inserted only when the logical AND of all conditions evaluate to true.
| Column names in db2-xdb:condition
|
|
|
|
|
|
|
Because db2-xdb:condition consists of SQL predicates, column names can be specified in this annotation.
If a db2-xdb:condition annotation involving a rowSet contains an unqualified column name, there must
exist a mapping to that column among all of the mappings involving that rowSet. Other column names,
when used in predicates containing SELECT statements, must be qualified. If db2-xdb:condition specifies
an unqualified column name, but the element or attribute for which db2-xdb:condition is specified does
not have a column mapping specified, then when the condition is evaluated, the value that is evaluated
is the content of the element or attribute that maps to the referenced column name.
| Consider the following example:

| <xs:element name="a" type="xs:string"
|
db2-xdb:rowSet="rowSetA" db2-xdb:condition="columnX=abc" />
| <xs:element name="b" type="xs:string"
|
db2-xdb:rowSet="rowSetB" db2-xdb:condition="columnX" />
|
|
|
|
|
|
Notice that <a> does not have a column mapping specified, but the condition references the column
"columnX". When the condition is evaluated, "columnX" in the condition will be replaced with the value
from <b>, because <b> has specified a column mapping for "columnX", while <a> does not have a
column mapping. If the XML document contained:
<a>abc</a>
<b>def</b>
| then the condition would evaluate to false in this case, because the value from <b>, "def", is evaluated in
| the condition.
|
|
|
|
|
|
|
If $DECOMP_CONTENT (a decomposition keyword that specifies the value of the mapped element or
attribute as character data), instead of the column name, is used in the db2-xdb:condition attached to the
element <a> declaration, then the condition is evaluated using the value of <a>, rather than <b>.
<xs:element name="a" type="xs:string"
db2-xdb:rowSet="rowSetA" db2-xdb:condition="$DECOMP_CONTENT=abc" />
<xs:element name="b" type="xs:string"
db2-xdb:rowSet="rowSetB" db2-xdb:column="columnX" />
| If the XML document contained:
342
|
|
<a>abc</a>
<b>def</b>
|
|
then the condition would evaluate to true in this case, because the value from <a>, "abc", is used in the
evaluation.
|
|
|
This conditional processing, using column names and $DECOMP_CONTENT, can be useful in cases
where you want to decompose only a value based on the value of another element or attribute that will
not be inserted into the database.
Conditions specified on mapped elements or attributes absent from the document
|
|
|
|
|
|
If a condition is specified on an element or attribute, but that element or attribute does not appear in the
XML document, then the condition is still applied. For example, consider the following element mapping
from an annotated schema document:
|
|
|
|
If the <intElem> element does not appear in the XML document, the condition "colInt > 100" is still
evaluated. Because <intElem> does not appear, a default value of 0 is used in the condition evaluation for
"colInt". The condition is then evaluated as: 0 > 100, which evaluates to false. The corresponding row is
therefore not inserted during decomposition.
Example
|
|
|
|
|
|
Consider the following <author> element from an XML document:
|
|
Depending on the conditions specified by db2-xdb:condition, the values from this <author> element
might or might not be inserted into the target tables during decomposition. Two cases are presented next.
All conditions satisfied
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following section from the annotated schema that corresponds to the <author> element above,
specifies that this element should only be decomposed if the author's ID falls between 1 and 999, the
<firstname> and <lastname> elements are not NULL, and the value of the <activeStatus> element equals
1:
<xs:element name="intElem" type="xs:integer"

db2-xdb:rowSet="rowSetA" db2-xdb:column="colInt"
db2-xdb:condition="colInt > 100" default="0" />
<author ID="0800">
</author>
<xs:complexType>
<xs:sequence>
<xs:element name="firstname" type="xs:string"
db2-xdb:rowSet="AUTHORS" db2-xdb:column="GIVENNAME"
db2-xdb:condition="$DECOMP_CONTENT IS NOT NULL" />
<xs:element name="lastname" type="xs:string"
db2-xdb:rowSet="AUTHORS" db2-xdb:column="SURNAME"
<xs:element name="activeStatus" type="xs:integer"
db2-xdb:rowSet="AUTHORS" db2-xdb:column="statusCode"
db2-xdb:condition="$DECOMP_CONTENT=1" />
db2-xdb:rowSet="AUTHORS" db2-xdb:column="AUTHID"
db2-xdb:condition="$DECOMP_CONTENT BETWEEN 1 and 999 />
</xs:sequence>
</xs:complexType>
</xs:element>
SQL programming
343
| Because all of the conditions specified by db2-xdb:condition are satisfied by the values in the example
| <author> element above, the AUTHORS table is populated with the data from the <author> element.
|
Table 65. AUTHORS
AUTHID
GIVENNAME
SURNAME
STATUSCODE
NUMBOOKS
|
|
0800
Alexander
Smith
NULL
| One condition fails

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following annotated schema specifies that the <author> element should only be decomposed if the
author's ID falls between 1 and 100, and the <firstname> and <lastname> elements are not NULL:
|
|
|
|
|
Although the <firstname> and <lastname> elements of the example <author> element meet the
conditions specified, the value of the ID attribute does not, and so the entire row is not inserted during
decomposition. This is because the logical AND of all three conditions specified on the AUTHORS table
is evaluated. In this case, one of the conditions is false, and so the logical AND evaluates to false, and
therefore, no rows are inserted.
<xs:complexType>
<xs:sequence>
db2-xdb:rowSet="AUTHORS" db2-xdb:column="GIVENNAME"
db2-xdb:condition="$DECOMP_CONTENT IS NOT NULL"/>
<xs:element name="activeStatus" type="xs:integer" />
db2-xdb:condition="$DECOMP_CONTENT BETWEEN 1 and 100" />
</xs:sequence>
</xs:complexType>
</xs:element>
| db2-xdb:contentHandling decomposition annotation:

| The db2-xdb:contentHandling annotation specifies the type of content that will be decomposed into a
| table for an element of complex type or simple type.
| Annotation type
| Attribute of <xs:element>, or attribute of <db2-xdb:rowSetMapping>, that applies to complex type or
| simple type element declarations
| How to specify
|
|
|
|
|
|
|
db2-xdb:contentHandling is specified in any of the following ways (where value represents a valid value
for the annotation):
v <xs:element db2-xdb:contentHandling="value" />
v <db2-xdb:rowSetMapping db2-xdb:contentHandling="value">
...
| Namespace
344
Valid values
One of the following case-sensitive tokens:
|
|
|
v text
v stringValue
v serializeSubtree
Details
|
|
|
The db2-xdb:contentHandling annotation, specified as an attribute in the declaration of an XML element,

indicates what value is to be inserted into the tables and columns specified by db2-xdb:rowSet and
db2-xdb:column, respectively, during decomposition.
The three valid values for db2-xdb:contentHandling are:
text
|
|
|
|
|
|
|
|
|
|
|
v What is inserted: the concatenation of character data (including character content of CDATA
sections) within this element.
v What is excluded: this element's comments and processing instructions, CDATA section
delimiters ("<![CDATA[" "]]>"), as well as this element's descendants (including tags and
content).
stringValue
v What is inserted: the concatenation of this element's character data (including character content
of CDATA sections) with the character data in this element's descendants, in document order.
v What is excluded: comments, processing instructions, CDATA section delimiters ("<![CDATA["
"]]>"), and the start and end tags of this element's descendants.
serializeSubtree
|
|
|
v What is inserted: the markup of everything between this element's start and end tags,
including this element's start and end tags. This includes comments, processing instructions,
and CDATA section delimiters ("<![CDATA[" "]]>").
|
|
|
|
|
|
|
|
|
|
|
|
|
v What is excluded: nothing.

v Notes: The serialized string that is inserted might not be identical to the corresponding section
in the XML document because of factors such as: default values specified in the XML schema,
expansion of entities, order of attributes, whitespace normalization of attributes, and processing
of CDATA sections.
Because the serialized string that results from this setting is an XML entity, there are CCSID
issues that should be considered. If the target column is of character or graphic types, the XML
fragment is inserted in the column's CCSID. When such an entity is passed by an application
to an XML processor, the application must explicitly inform the processor of the entity's
encoding, because the processor would not automatically detect encodings other than UTF-8. If
the target column is of type BLOB, however, then the XML entity is inserted in UTF-8
encoding. In this case, the XML entity can be passed to the XML processor without needing to
specify an encoding.
|
|
|
|
If an XML element declaration that is annotated for decomposition is of complex type and contains
complex content but does not have db2-xdb:contentHandling specified, then the default behavior follows
the "serializeSubtree" setting. For all other cases of annotated element declarations, the default behavior if
db2-xdb:contentHandling is not specified follows the "stringValue" setting.
|
|
|
If an element is declared to be of complex type and has an element-only or empty content model (that is,
the "mixed" attribute of the element declaration is not set to true or 1), then db2-xdb:contentHandling
cannot be set to "text".
SQL programming
345
| Specifying the db2-xdb:contentHandling annotation on an element does not affect the decomposition of
| any of the element's descendants.
| The setting of db2-xdb:contentHandling affects the value that is substituted for $DECOMP_CONTENT in
| either of the db2-xdb:expression or db2-xdb:condition annotations. The substituted value is first processed
| according to the db2-xdb:contentHandling setting, before it is passed for evaluation.
| Example
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following example illustrates how the different settings of the db2-xdb:contentHandling annotation
can be used to yield different results in the target table. The annotated schema is presented first, showing
how the <paragraph> element is annotated with db2-xdb:contentHandling. (The annotated schema is
presented only once, with db2-xdb:contentHandling set to "text". Subsequent examples in this section
assume the same annotated schema, which differ only by the value db2-xdb:contentHandling is set to.)
<xs:schema>
<xs:complexType>
<xs:sequence>
<xs:complexType>
<xs:sequence>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:sequence>
db2-xdb:rowSet="BOOKCONTENTS" db2-xdb:column="CHPTCONTENT"
db2-xdb:contentHandling="text" />
</xs:sequence>
db2-xdb:rowSet="BOOKCONTENTS" db2-xdb:column="CHPTNUM" />
db2-xdb:rowSet="BOOKCONTENTS" db2-xdb:column="CHPTTITLE" />
</xs:complexType>
<xs:complexType name="paragraphType" mixed="1">
<xs:choice>
<xs:element name="b" type="xs:string" minOccurs="0" maxOccurs="unbounded" />
</xs:choice>
</xs:complexType>
</xs:schema>
| The <books> element that is being mapped is presented next.

| <books>
|
|
|
|
<paragraph>XML is <b>lots of</b> fun...</paragraph>
|
</chapter>
|
|
<paragraph>XML can be used with...</paragraph>
|
<paragraph><?processInstr example?>
|
Escape characters such as <![CDATA[ <, >, and & ]]>...</paragraph>
346
|
|
|
|
|
|
|
|
</chapter>
...
</chapter>
</book>
...
<books>
|
|
The next three tables show the result of decomposing the same XML element with differing values for
db2-xdb:contentHandling.
|
|
|
Note: The resulting tables below contain quotation marks around the values in the CHPTTITLE and
CHPTCONTENT columns. These quotation marks do not exist in the columns, but are presented
here only to show the boundaries and whitespaces of the inserted strings.
db2-xdb:contentHandling="text"
ISBN
CHPTNUM
CHPTTITLE
1-11-111111-1
"Introduction to XML" "XML is fun..."
1-11-111111-1
"XML and Databases"
"XML can be used with..."
1-11-111111-1
"XML and Databases"
"
|
|
CHPTCONTENT
Escape characters such as <, >,

and & ..."
...
...
...
...
|
|
1-11-111111-1
10
"Further Reading"
"Recommended tutorials..."
|
|
|
|
|
Observe how the content of the <b> element of the first paragraph of chapter 1 is not inserted when the
"text" setting is used. This is because the "text" setting excludes any content from descendants. Notice also
that the comment and processing instruction from the first paragraph of chapter 2 are excluded when the
"text" setting is used. Whitespace from the concatenation of character data from the <paragraph>
elements is preserved.
db2-xdb:contentHandling="stringValue"
ISBN
CHPTNUM
CHPTTITLE
1-11-111111-1
"Introduction to XML" "XML is lots of fun..."
1-11-111111-1
"XML and Databases"
"XML can be used with..."
1-11-111111-1
"XML and Databases"
"
|
|
CHPTCONTENT
Escape characters such as <, >,

and & ..."
...
...
...
...
|
|
1-11-111111-1
10
"Further Reading"
"Recommended tutorials..."
|
|
|
|
The difference between this table and the previous table is found in the CHPTCONTENT column of the
first row. Notice how the string "lots of", which comes from the <b> descendant of the <paragraph>
element, has been inserted. When db2-xdb:contentHandling was set to "text", this string was excluded,
because the "text" setting excludes the content of descendants. The "stringValue" setting, however,
SQL programming
347
| includes content from descendants. Like the "text" setting, comments and processing instructions are not
| inserted, and whitespace is preserved.
| db2-xdb:contentHandling="serializeSubtree"
|
ISBN
CHPTNUM
CHPTTITLE
|
|
1-11-111111-1
"Introduction to XML" "<paragraph>XML is <b>lots of</b>

fun...</paragraph>"
|
|
1-11-111111-1
"XML and Databases"
"<paragraph>XML

can be used with...</paragraph>"
1-11-111111-1
"XML and Databases"
"<paragraph><?processInstr example?>
|
|
CHPTCONTENT
Escape characters such as

<![CDATA[ <, >, and & ]]>...</paragraph>"
...
...
...
...
|
|
|
1-11-111111-1
10
"Further Reading"
"<paragraph>Recommended
tutorials...</paragraph>"
|
|
|
|
|
The difference between this table and the previous two tables is that all markup from the descendants of
<paragraph> elements are inserted (including the <paragraph> start and end tags). This includes the <b>
start and end tags in the CHPTCONTENT column of the first row, as well as the comment and
processing instruction in the second and third rows, respectively. As in the previous two examples,
whitespace from the XML document has been preserved.
| db2-xdb:normalization decomposition annotation:

| The db2-xdb:normalization annotation specifies the normalization of whitespace in the XML data to be
| inserted or to be substituted for $DECOMP_CONTENT (when used with db2-xdb:expression).
| Annotation type
| Attribute of <xs:element> or <xs:attribute>, or attribute of <db2-xdb:rowSetMapping>>
| How to specify
|
|
|
|
|
|
|
|
db2-xdb:normalization is specified in any of the following ways (where value represents a valid value for
the annotation):
v <xs:element db2-xdb:normalization="value" />
v <xs:attribute db2-xdb:normalization="value" />
v <db2-xdb:rowSetMapping> db2-xdb:normalization="value">
...
| Namespace
| Valid values
| One of the following case-sensitive tokens:
348
|
|
|
|
canonical
Before the XML value is inserted into the target column, or is substituted for occurrences of
$DECOMP_CONTENT that are in the same mapping as this db2-xdb:normalization annotation,
the XML value is converted to its canonical form according to its XML schema type.
|
|
|
|
|
original
$DECOMP_CONTENT that are in the same mapping as this db2-xdb:normalization annotation,
no modification of the XML is done except for possible processing by an XML parser. This is the
default.
|
|
|
whitespaceStrip
$DECOMP_CONTENT that are in the same mapping as this db2-xdb:normalization annotation:
v All leading and trailing whitespace is removed from the XML value.
v Consecutive whitespace is collapsed into a single whitespace character.
|
|
|
Details
|
|
|
db2-xdb:normalization is applicable when an element or attribute has one of the following atomic XML
schema types:
v byte, unsigned byte
|
|
|
v integer, positiveInteger, negativeInteger, nonPositiveInteger, nonNegativeInteger

v int, unsignedInt
v long, unsignedLong
|
|
|
v short, unsignedShort
v decimal
v float
|
|
|
|
v
v
v
v
v dateTime
|
|
|
|
The target column must have one of the following data types:
v CHAR
v VARCHAR
v CLOB
|
|
|
v DBCLOB
v GRAPHIC
v VARGRAPHIC
db2-xdb:normalization will be ignored if specified for any other types.
Example
|
|
|
|
|
|
The following example shows how whitespace normalization can be controlled with the
db2-xdb:normalization annotation. The annotated schema is presented first.
double
boolean
time
date
<xs:complexType>
<xs:sequence>
SQL programming
349
|
|
|
|
|
|
|
|
|
|
|
|
|
db2-xdb:rowSet="AUTHORS" db2-xdb:column="FIRSTNAME" />

db2-xdb:normalization="whitespaceStrip" />
<xs:element name="activeStatus" type="xs:boolean"
db2-xdb:rowSet="AUTHORS" db2-xdb:column="ACTIVE"
db2-xdb:normalization="canonical" />
db2-xdb:normalization="whitespaceStrip" />
</xs:sequence>
</xs:complexType>
</xs:element>
| The <author> element that is being mapped is presented next (notable whitespaces are represented below
| by the '_' underscore character for the purpose of demonstration), followed by the resulting AUTHORS
| table after the decomposition has completed.
| <author ID="__22">
|
<firstname>Ann</firstname>
|
<lastname>__Brown_</lastname>
|
|
</author>
|
Table 69. AUTHORS
AUTHID
FIRSTNAME
SURNAME
ACTIVE
NUMBOOKS
|
|
22
Ann
__Brown_
true
NULL
|
|
|
|
|
The db2-xdb:normalization="whitespaceStrip" annotation on the ID attribute causes the leading and

trailing whitespace to be removed before the data is inserted into the AUTHORS table. The
db2-xdb:normalization.="canonical" annotation on the <activeStatus> element causes its boolean value to
be replaced with the canonical representation of that value before insertion into the AUTHORS table. The
element has a boolean type. The canonical representation of a boolean type is true or false.
| db2-xdb:order decomposition annotation:

| The db2-xdb:order annotation specifies the insertion order of rows among different tables.
| Annotation type
| Child element of <db2-xdb:rowSetOperationOrder>.
| How to specify
| db2-xdb:order is specified in the following way (where value represents a valid value for the annotation):
| <xs:schema>
|
<xs:annotation>
|
<xs:appinfo>
|
<db2-xdb:rowSetOperationOrder>
|
<db2-xdb:order>
|
|
...
|
</db2-xdb:order>
|
</db2-xdb:rowSetOperationOrder>
|
</xs:appinfo>
|
</xs:annotation>
|
...
| </xs:schema>
350
Namespace
Valid structure
The following are supported children elements of <db2-xdb:order>:
|
|
db2-xdb:rowSet
Specifies an XML element or attribute mapping to a target base table.
Details
|
|
|
|
|
The db2-xdb:order annotation is used to define the order of insertion of the rows belonging to a given
rowSet, relative to the rows belonging to another rowSet. This enables XML data to be inserted into target
tables in a way consistent with any referential integrity constraints defined on the tables as part of the
relational schema. The number of db2-xdb:rowSet elements that can appear in db2-xdb:order element can
be any number greater than 1.
|
|
|
|
|
|
All rows of a given rowSet RS1 are inserted before any rows belonging to another rowSet RS2 if RS1 is
listed before RS2 within db2-xdb:order. Multiple instances of this element can be specified in order to
define multiple insert order hierarchies. For rowSets that do not appear in any element, their rows may
be inserted in any order, relative to the rows of any other rowSet. Also, the content of each
<db2-xdb:rowSet> element must be either an explicitly defined rowSet or the name of an existing table
for which no explicit rowSet declaration was made.
|
|
Multiple rowSet insertion hierarchies can be defined, though a rowSet can appear in only one instance of
the <db2-xdb:order> element, and it can appear only once within that element.
|
|
|
For delimited SQL identifiers specified in the children elements, the quotation marks delimiter must be
included in the character content and need not be escaped. The &' and <' characters used in SQL
identifiers, however, must be escaped.
Example
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following example demonstrates the use of the db2-xdb:order annotation.
|
|
|
|
|
|
Two disjoint hierarchies for order of insertion are specified in the above example. The first hierarchy
specifies that all content for the CUSTOMER rowSet or table is inserted prior to any content collected for
PURCHASE_ORDER, and the second hierarchy specifies that all content for the ITEMS_MASTER rowSet
or table will be inserted before any content is inserted into PO_ITEMS. Note that the order between the
two hierarchies is undefined. For example, any content for the PURCHASE_ORDER rowSet or table may
be inserted before or after any content is inserted into ITEMS_MASTER
<xs:schema>
<xs:annotation>
<xs:appinfo>
<db2-xdb:order>
<db2-xdb:rowSet>CUSTOMER</db2-xdb:rowSet>
<db2-xdb:rowSet>PURCHASE_ORDER</db2-xdb:rowSet>
</db2-xdb:order>
<db2-xdb:order>
<db2-xdb:rowSet>ITEMS_MASTER</db2-xdb:rowSet>
<db2-xdb:rowSet>PO_ITEMS</db2-xdb:rowSet>
</db2-xdb:order>
</xs:appinfo>
</xs:annotation>
</xs:schema>
SQL programming
351
| db2-xdb:truncate decomposition annotation:

| The db2-xdb:truncate annotation specifies whether truncation is permitted when an XML value is inserted
| into a character target column.
| Annotation type
| Attribute of <xs:element> or <xs:attribute>, or attribute of <db2-xdb:rowSetMapping>>
| How to specify
| db2-xdb:truncate is specified in any of the following ways (where value represents a valid value for the
| annotation):
| v <xs:element db2-xdb:truncate="value" />
| v <xs:attribute db2-xdb:truncate="value" />
| v <db2-xdb:rowSetMapping> db2-xdb:truncate="value">
|
|
...
|
| Namespace
| Valid values
| One of the following values:
| 0 or false
|
The value cannot be truncated before insertion, If the value is too long, an error occurs and the
|
value is not inserted. This is the default.
| 1 or true
|
The value can be truncated before insertion.
| Details
|
|
|
|
|
|
|
An XML value being inserted into a target character column might be larger than the column size; in this
case, the value must be truncated for a successful decomposition. The db2-xdb:truncate attribute indicates
whether or not truncation will be permitted when the value is too large for the target column. If this
attribute is set to "false" or "0", to indicate that truncation is not permitted, and the XML value being
inserted is too large for the target column, an error occurs during decomposition of the XML document
and the value is not inserted. The "true" or "1" setting indicates that data truncation is allowed during
insertion.
| db2-xdb:truncate is applicable only for the following mappings:

||
XML data type
Column data type
|
|
|
|
|
|
Any compatible type
CHAR
VARCHAR
CLOB
GRAPHIC
VARGRAPHIC
DBCLOB
xs:date
DATE
xs:time
TIME
352
XML data type
Column data type
|
|
xs:dateTime
TIMESTAMP
|
|
|
If the db2-xdb:expression annotation is specified on the same element or attribute declaration as

db2-xdb:truncate, then the value of db2-xdb:truncate is ignored, as the expression can perform truncation
if it is defined as such.
|
|
For an annotations that decompose XML datatime values into DATE, TIME, or TIMESTAMP columns, if
the XML data can have a timezone, db2-xdb:truncate must be set to "true" or "1".
Example
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following example shows how truncation can be applied to an <author> element. A section of the
annotated schema is presented first.
|
|
|
|
|
|
|
The <author> element that is being mapped is presented next.
|
|
|
Assume that the FIRSTNAME column was defined as a CHAR SQL type of size 7, and that the
ACTIVEDATE column was defined as a DATE SQL type. The AUTHORS table that results after the
decomposition has completed is presented next.
|
|
|
|
Table 70. AUTHORS
|
|
|
|
Because the <firstname> value "Alexander" is larger than the SQL column size, truncation is necessary in
order to insert the value. Notice also that because the <activated> element contained a timezone in the
XML document, db2-xdb:truncate was set to "true" to ensure the date was successfully inserted during
decomposition.
|
|
|
|
Because truncation is required in order to insert the value from the <firstname> element or the
<activated> element, if db2-xdb:truncate was not specified, then the default value of db2-xdb:truncate is
assumed (truncation not permitted), and an error would have been generated to indicate that a row has
not been inserted.
<xs:complexType>
<xs:sequence>
db2-xdb:rowSet="AUTHORS" db2-xdb:column="FIRSTNAME"
db2-xdb:truncate="true" />
<xs:element name="lastname" type="xs:string" />
<xs:element name="activeStatus" type="xs:boolean" />
<xs:element name="activated" type="xs:date"
db2-xdb:truncate="true" />
<xs:attribute name="ID" type="xs:integer" />
<xs:sequence>
</xs:complexType>
</xs:element>
<author ID="0800">
<activated>2001-10-31Z</activated>
</author>
AUTHID
FIRSTNAME
SURNAME
ACTIVE
ACTIVEDATE
NUMBOOKS
NULL
Alexand
NULL
NULL
2001-10-31
NULL
SQL programming
353
| db2-xdb:rowSetMapping decomposition annotation:

| The db2-xdb:rowSetMapping annotation maps an XML element or attribute to a single target table and
| column to multiple target columns of the same table or to multiple tables and columns.
| Annotation type
| Child element of <xs:appinfo> (which is a child element of <xs:annotation>) that is a child element of
| <xs:element> or <xs:attribute>
| How to specify
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
db2-xdb:rowSetMapping is specified in any of the following ways (where value represents a valid value
for the annotation):
v <xs:element>
<xs:annotation>
<xs:appinfo>
...
</xs:appinfo>
</xs:annotation>
...
</xs:element>
v <xs:attribute>
<xs:annotation>
<xs:appinfo>
...
</xs:appinfo>
</xs:annotation>
...
</xs:attribute>
| Namespace
| Valid structure
| The following are supported attributes of <db2-xdb:rowSetMapping>:
| db2-xdb:contentHandling
|
Enables specification of the type of content that will be decomposed into a table for an element
|
that is of complex type.
| db2-xdb:locationPath
|
Enables mapping of an XML element or attribute declared as part of a reusable group, to
|
different table and column pairs, depending on the ancestry of the element or attribute.
| db2-xdb:normalization
|
Enables specification of the normalization behavior for the content of the XML element or
|
attribute mapped to a character target column, before the content is inserted.
| db2-xdb:truncate
|
Enables specification of whether truncation is permitted when an XML value is inserted into a
|
character target column.
354
|
|
The following are supported children elements of <db2-xdb:rowSetMapping>, listed in the order in which
they must appear if they are specified:
|
|
<db2-xdb:rowSet>
Maps an XML element or attribute to a target base table.
|
|
|
<db2-xdb:column>
Maps an XML element or attribute to a base table column. This element is optional if
db2-xdb:condition or db2-xdb:locationPath annotation is present.
|
|
|
<db2-xdb:expression>
Specifies a customized expression, the result of which is inserted into the table named by the
db2-xdb:rowSet attribute. This element is optional.
|
|
<db2-xdb:condition>
Specifies a condition or evaluation. This element is optional.
Details
If db2-xdb:expression and db2-xdb:truncate are specified together, db2-xdb:truncate is ignored.
|
|
For mapping to a single table and column, specification of db2-xdb:rowSetMapping is equivalent to

specifying a combination of db2-xdb:rowSet and db2-xdb:column annotations.
|
|
|
|
All whitespace in the character content of the child elements of <db2-xdb:rowSetMapping> is significant;
no whitespace normalization is performed. For delimited SQL identifiers specified in the children
elements, the quotation marks delimiter must be included in the character content and not escaped. The
&' and <' characters used in SQL identifiers, however, must be escaped.
Example
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following example shows how a single attribute, named "isbn", can be mapped to more than one
table with the <db2-xdb:rowSetMapping> annotation. A section of the annotated schema is presented
first. It shows how the isbn value is mapped to both the BOOKS and BOOKCONTENTS tables.
|
|
The <book> element that is being mapped is presented next, followed by the resulting BOOKS and
BOOKCONTENTS tables after the decomposition has completed.
<xs:complexType>
<xs:sequence>
<xs:element name="authorID" type="xs:integer"/>
</xs:sequence>
<xs:attribute name="isbn" type="xs:string">
<xs:annotation>
<xs:appinfo>
<db2-xdb:rowSet>BOOKS</db2-xdb:rowSet>
</xs:appinfo>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
SQL programming
355
| <book isbn="1-11-111111-1" title="My First XML Book">

|
|
|
|
|
...
|
</chapter>
|
...
| </book>
|
Table 71. BOOKS
ISBN
TITLE
CONTENT
|
|
1-11-111111-1
NULL
NULL
ISBN
CHPTNUM
CHPTTITLE
CHPTCONTENT
|
|
1-11-111111-1
NULL
NULL
NULL
| Alternative mapping using combination of <db2-xdb:rowSetMapping> and db2-xdb:rowSet and

| db2-xdb:column
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following section of an annotated schema is equivalent to the XML schema fragment presented
above, as it yields the same decomposition results. The difference between the two schemas is that this
schema replaces one mapping with the db2-xdb:rowSet and db2-xdb:column combination, instead of
using only the <db2-xdb:rowSetMapping> annotation.
<xs:complexType>
<xs:sequence>
</xs:sequence>
db2-xdb:rowSet="BOOKS" db2-xdb:column="ISBN" >
<xs:annotation>
<xs:appinfo>
</xs:appinfo>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
| db2-xdb:rowSetOperationOrder decomposition annotation:

| The db2-xdb:rowSetOperationOrder annotation is a parent for one or more db2-xdb:order elements. See
| the section for db2-xdb:order for details on usage in defining order of insertion of rows among different
| tables.
| Annotation type
| Child element of <xs:appinfo> that is a child of a global <xs:annotation> element.
356
How to specify
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
db2-xdb:rowSetOperationOrder is specified in the following way (where value represents a valid value for
the annotation):
Namespace
Valid structure
The following are supported children elements of <db2-xdb:rowSetOperationOrder>:
db2-xdb:order
Details
|
|
<db2-xdb:rowSetOperationOrder> groups together <db2-xdb:order> elements. Multiple instances of the

child <db2-xdb:order> element can be present, allowing the definition of multiple insertion hierarchies.
|
|
|
|
By allowing you to control the order in which contents of XML documents are inserted, the
db2-xdb:rowSetOperationOrder and db2-xdb:order annotations together provide a way to ensure that the
XML schema decomposition process respects any referential integrity constraints on target tables, as well
as any other application requirements that rows of a table be inserted before rows of another table.
The db2-xdb:rowSetOperationOrder annotation can appear only once in an XML schema.
Example
|
|
See db2-xdb:order decomposition annotation on page 350 for examples of specifying the order of
rowSet insertion.
Keywords for annotated XML schema decomposition:
|
|
Annotated XML schema decomposition offers decomposition keywords for use in the db2-xdb:condition
and db2-xdb:expression annotations.
|
|
|
|
$DECOMP_CONTENT
The value of the mapped XML element or attribute from the document. The value is constructed
according to the setting of the db2-xdb:contentHandling annotation. The value of
$DECOMP_CONTENT has a character type.
|
|
<xs:schema>
<xs:annotation>
<xs:appinfo>
<db2-xdb:order>
...
</db2-xdb:order>
</xs:appinfo>
</xs:annotation>
...
</xs:schema>
$DECOMP_CONTENT can be used to process the value of the mapped element or attribute,
using customized expressions, rather than directly inserting that value.
SQL programming
357
If db2-xdb:expression specifies $DECOMP_CONTENT and db2-xdb:normalization is specified in

the same mapping, the $DECOMP_CONTENT value for db2-xdb:expression is normalized before
it is passed to the expression for evaluation.
|
|
|
| $DECOMP_DOCUMENTID
|
The string value specified in the documentid input parameter of the XDBDECOMPXML stored
|
procedure, which identifies the XML document that is being decomposed. When the document is
|
decomposed, the input value that is provided to the stored procedure is used as the value
|
substituted for $DECOMP_DOCUMENTID.
$DECOMP_DOCUMENTID can be used to insert unique identifiers that are not present in the
XML document. Applications can pass uniquely generated document IDs into
XDBDECOMPXML. These IDs can then be directly inserted into a table in the database. The IDs
can also be passed into expressions that generate unique identifiers for elements or attributes.
|
|
|
|
| Treatment of CDATA sections in annotated XML schema decomposition

| If elements that are annotated for decomposition contain CDATA sections, the decomposition process
| inserts the contests of the CDATA sections into tables, without the CDATA section delimiters
| ("<![CDATA[" and "]]>").
| Carriage return and line feed pairs (U+000D and U+000A) or carriage returns (U+000D) within the
| CDATA section are replaced with line feeds (U+000A).
|
|
|
|
If the XML element declaration in the XML schema is annotated with the attribute db2xdb:contentHandling="serializeSubtree", the contents of the CDATA section are inserted into tables with
the following changes:
v CDATA section delimiters ("<![CDATA[" and "]]>") are removed.
| v Each ampersand (&) in the CDATA section is replaced by the string &amp:.
| v Each left angle bracket (<) in the CDATA section is replaced by the string &lt:.
| The content of the CDATA section after decomposition is logically equivalent to the original content of
| the CDTATA section.
| NULL values and empty strings in annotated XML schema decomposition
| Annotated XML schema decomposition inserts NULL values or empty strings under certain conditions.
| XML elements
| The following table shows when an empty string or a NULL value is inserted into the database for
| elements in the XML document.
|
Table 73. NULL handling for mapped elements
Condition
Element missing from document
|
|
|
|
Element satisfies all of the following conditions:
v is present in the document

v contains the xsi:nil="true" or xsi:nil="1" attribute
in the start tag
358
Empty string
NULL value
Table 73. NULL handling for mapped elements (continued)
Condition
Empty string
|
|
|
|
|
|
|
|
|
|
Element satisfies all of the following conditions:
|
|
|
|
|
Note:
XML attributes
|
|
The following table shows when an empty string or a NULL value is inserted into the database when
XML attributes annotated for decomposition contain NULL values in the document or are missing.
Table 74. NULL handling for mapped attributes
Condition
|
|
|
Attribute missing from document (either because no

validation was performed, or there was no default value
provided by validation)
|
|
|
|
|
|
|
|
Attribute satisfies all of the following conditions:
|
|
|
Note: If a mapping involves the db2-xdb:condition or db2-xdb:expression annotations, then the empty string or
NULL value (as shown in this table) is passed as the argument for expression evaluation.
|
|
|
Checklist for annotated XML schema decomposition
|
|
|
Annotated XML schema decomposition requires you to map possibly multiple XML elements and
attributes to multiple columns and tables in the database. This mapping can also involve transforming
the XML data before inserting it, or applying conditions for insertion.
|
|
|
|
|
|
The following are items to consider when annotating your XML schema, along with pointers to related
documentation:
v Understand what decomposition annotations are available to you.
v Ensure, during mapping, that the type of the column is compatible with the XML schema type of the
element or attribute it is being mapped to.
v Ensure complex types derived by restriction or extension are properly annotated.
NULL value
v is present and empty in the document

v does not contain the xsi:nil="true" or xsi:nil="1"
attribute in the start tag
v is derived from or declared to be of list type, union
type, complex type with mixed content, or the
following atomic built-in types: xsd:string,
xsd:normalizedString, xsd:token, xsd:hexBinary,
xsd:base64Binary, xsd:anyURI, xsd:anySimpleType;
any other types will result in an error.
1. If a mapping involves the db2-xdb:condition or db2-xdb:expression annotations, then the empty string or NULL
value (as shown in this table) is passed as the argument for expression evaluation.
2. If a target column is of type CHAR or GRAPHIC, an empty string is inserted as a string of blank characters.
Empty string
NULL value
X
v is present and empty in the document

v is derived from or declared to be of list type, union
type, or the following atomic built-in types:
xsd:string, xsd:normalizedString, xsd:token,
xsd:hexBinary, xsd:base64Binary, xsd:anyURI,
xsd:anySimpleType; any other types will result in an
error.
Annotated XML schema decomposition can become complex. To make the task more manageable, you
should take several things into consideration.
SQL programming
359
| v Confirm that no decomposition limits and restrictions are violated.

| v Ensure that the tables and columns referenced in the annotation exist at the time the schema is
|
registered with the XSR.
|
Examples of mappings in annotated XML schema decomposition
|
|
|
|
Annotated XML schema decomposition relies on mappings to determine how to decompose an XML
document into tables. Mappings are expressed as annotations added to the XML schema document. These
mappings describe how you want an XML document to be decomposed into tables. The following
examples show some common mapping scenarios.
| Common mapping scenarios:

| Annotations of derived complex types
| XML schemas can contain complex types that are derived by restriction or extension (specified by
| complexType elements that include restriction or extension elements).
| When you annotate those complex types for decomposition, you need to apply additional mappings.
| If a complex type is referred to in multiple places in an XML schema, you can map it to different tables
| and columns depending on its location in the schema, using the db2-xdb:locationPath annotation.
| Complex types that are derived by restriction require that the common elements and attributes from the
| base type are repeated in the definition of the derived type. Therefore, decomposition annotations that are
| present in the base type must also be included in the derived type.
|
|
|
|
In the definition of complex types that are derived by extension, only the elements and attributes that are
in addition to the base type are specified. If the decomposition mappings for the derived type differ from
the mappings of the base type, you must add decomposition annotations to the base type to clearly
differentiate the mappings of the base from the derived types.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example: In the following XML schema document, outOfPrintBookType is derived by extension. It is

mapped to a different table than its base type, which is bookType. The db2-xdb:locationPath annotation is
specified in the bookType base type to clearly differentiate which mappings apply to the base type, and
which apply to the derived type. The <lastPublished> and <publisher> elements of the derived type
outOfPrintType do not require the db2-xdb:locationPath annotation in this example, because these
elements are involved in only a single mapping.
<xs:annotation>
<xs:appinfo>
<db2-xdb:table>
<db2-xdb:name>BOOKS</db2-xdb:name>
<db2-xdb:rowSet>inPrintRowSet</db2-xdb:rowSet>
</db2-xdb:table>
<db2-xdb:table>
<db2-xdb:name>OUTOFPRINT</db2-xdb:name>
<db2-xdb:rowSet>outOfPrintRowSet</db2-xdb:rowSet>
</db2-xdb:table>
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:choice>
<xs:element name="book" type="bookType"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="outOfPrintBook" type="outOfPrintBookType"
minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
</xs:complexType>
360
Note 1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</xs:element>
<xs:complexType name="bookType">
<xs:sequence>
<xs:element name="chapter" type="chapterType" maxOccurs="unbounded"/>
</xs:sequence>
Note 2a
db2-xdb:locationPath="/books/book/@title"
db2-xdb:rowSet="inPrintRowSet" db2-xdb:column="TITLE">
<xs:annotation>
<xs:appinfo>
<db2-xdb:rowSetMapping db2-xdb:locationPath="/books/outOfPrintBook/@title">
<db2-xdb:column>TITLE</db2-xdb:column>
</xs:appinfo>
</xs:annotation>
</xs:attribute>
Note 2b
db2-xdb:locationPath="/books/book/@isbn"
db2-xdb:rowSet="inPrintRowSet" db2-xdb:column="ISBN">
<xs:annotation>
<xs:appinfo>
<db2-xdb:rowSetMapping db2-xdb:locationPath="/books/outOfPrintBook/@isbn">
</xs:appinfo>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="outOfPrintBookType">
<xs:complexContent>
<xs:extension base="bookType">
<xs:sequence>
<xs:element name="lastPublished" type="xs:date"
Note 3
db2-xdb:rowSet="outOfPrintRowSet" db2-xdb:column="LASTPUBDATE"/>
<xs:element name="publisher" type="xs:string"
db2-xdb:rowSet="outOfPrintRowSet" db2-xdb:column="PUBLISHER"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:simpleType>
<xs:sequence>
db2-xdb:locationPath="/books/book/chapter/paragraph"
db2-xdb:rowSet="inPrintRowSet" db2-xdb:column="CONTENT">
<xs:annotation>
<xs:appinfo>
<db2-xdb:rowSetMapping
db2-xdb:locationPath="/books/outOfPrintBook/chapter/paragraph">
<db2-xdb:rowSet>outOfPrintBook</db2-xdb:rowSet>
<db2-xdb:column>CONTENT</db2-xdb:column>
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="number" type="xs:integer"/>
<xs:attribute name="title" type="xs:string"/>
</xs:complexType>
</xs:schema>
SQL programming
361
| The annotations indicate that values from the <book> element are decomposed into the BOOKS table,
| and values from the <outOfPrintBook> element will be decomposed into the OUTOFPRINT table.
| Notes for the annotated XML schema document:
| 1
|
|
A <books> document can have two types of elements: a <book> element or an <outOfPrintBook>
element. Information from the two types of elements is decomposed into different tables. The
<outOfPrintBook> element definition has extensions to the <book> element definition.
| 2a and 2b
|
In the XML schema, the title and isbn attributes have the same definition for <book> elements
|
or <outOfPrintBook> elements, but in-print and out-of-print book information goes into different
|
tables. Therefore, you need db2-xdb:locationPath annotations to distinguish between titles and
|
ISBN numbers for in-print and out-of-print books.
| 3
|
The lastPublished and publisher elements are unique to <outOfPrintBook> elements, so no

db2-xdb:locationPath annotation is necessary for them.
| Suppose that you use this XML schema document to decompose the following XML document:
| <books>
|
|
|
|
|
</chapter>
|
|
|
</chapter>
|
</book>
|
<outOfPrintBook isbn="7-77-777777-7" title="Early XML Book">
|
|
<chapter number="1" title="Introductory XML">
|
<paragraph>Early XML...</paragraph>
|
</chapter>
|
<chapter number="2" title="What is XML">
|
<paragraph>XML is an emerging technology...</paragraph>
|
</chapter>
|
<lastPublished>2000-01-31</lastPublished>
|
<publisher>Early Publishers Group</publisher>
|
</outOfPrintBook>
| </books>
| The decomposition produces the following tables:
|
Table 75. BOOKS
ISBN
TITLE
CONTENT
1-11-111111-1
My First XML Book
XML is fun...
|
|
1-11-111111-1
My First XML Book
Table 76. OUTOFPRINT
ISBN
TITLE
CONTENT
LASTPUBDATE
PUBLISHER
7-77-777777-7
Early XML Book
Early XML...
2000-01-31
Early Publishers Group
|
|
|
7-77-777777-7
Early XML Book
XML is an emerging
technology...
2000-01-31
Early Publishers Group
362
Rowsets in annotated XML schema decomposition
|
|
The db2-xdb:rowSet annotation identifies the target table and row into which a value in an XML
document is decomposed.
The value of the db2-xdb:rowSet annotation can be a table name or a rowset name.
|
|
The db2-xdb:rowSet annotation can be an attribute of an element or attribute declaration, or a child of the
<db2-xdb:rowSetMapping> annotation.
|
|
|
In an XML schema, there can be multiple occurrences of an element or attribute, and all of those elements
or attributes can have a db2-xdb:rowSet annotation with the same target table value. Each of those
db2-xdb:rowSet annotations defines a row in the target table.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example: Suppose that you want to decompose this document so that each book's isbn and title value is
inserted into the ALLPUBLICATIONS table.
|
|
You need to define the following rowsets:

v A rowset to group the isbn value for a textbook with its title
v A rowset to group the isbn value for a children's book with its title
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The annotated XML schema look like this:
<publications>
<textbook title="Programming with XML">
<isbn>0-11-011111-0</isbn>
<author>Mary Brown</author>
<author>Alex Page</author>
<publicationDate>2002</publicationDate>
<university>University of London</university>
</textbook>
<childrensbook title="Childrens Fables">
<isbn>5-55-555555-5</isbn>
<author>Bob Carter</author>
<author>Melanie Snowe</author>
</childrensbook>
</publications>
xmlns:db2-xdb="http://www.ibm.com/xmlns/prod/db2/xdb1"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:annotation>
<xs:appinfo>
<db2-xdb:table>
<db2-xdb:name>ALLPUBLICATIONS</db2-xdb:name>
Note 1
<db2-xdb:rowSet>textbk_rowSet</db2-xdb:rowSet>
<db2-xdb:rowSet>childrens_rowSet</db2-xdb:rowSet>
</db2-xdb:table>
</xs:appinfo>
</xs:annotation>
<xs:element name="publications">
<xs:complexType>
<xs:sequence>
<xs:element name="textbook" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
Note 2a
db2-xdb:rowSet="textbk_rowSet" db2-xdb:column="PUBS_ISBN"/>
<xs:element name="author" type="xs:string" maxOccurs="unbounded"/>
<xs:element name="publicationDate" type="xs:gYear"/>
<xs:element name="university" type="xs:string"
SQL programming
363
|
maxOccurs="unbounded"/>
|
</xs:sequence>
|
<xs:attribute name="title" type="xs:string" use="required"Note 2b
|
db2-xdb:rowSet="textbk_rowSet" db2-xdb:column="PUBS_TITLE"/>
|
</xs:complexType>
|
</xs:element>
|
<xs:element name="childrensbook" maxOccurs="unbounded">
|
<xs:complexType>
|
<xs:sequence>
|
Note 3a
|
db2-xdb:rowSet="childrens_rowSet" db2-xdb:column="PUBS_ISBN"/>
|
|
|
</xs:sequence>
|
<xs:attribute name="title" type="xs:string" use="required"Note 3b
|
db2-xdb:rowSet="childrens_rowSet" db2-xdb:column="PUBS_TITLE"/>
|
</xs:complexType>
|
</xs:element>
|
</xs:sequence>
|
</xs:complexType>
|
</xs:element>
| </xs:schema>
| Notes for the annotated XML schema document:
| 1
|
|
In the global <xs:annotation>, the textbk_rowSet rowset and the childrens_rowSet rowset are
declared for later reference in the XML schema. The <db2-xdb:name> annotation names the table
(ALLPUBLICATIONS) to which the rowsets refer.
| 2a and 2b
|
The textbk_rowSet annotation is specified on the isbn element declaration and the title attribute
|
declaration in the <textbook> element. This indicates that isbn and title information from
|
<textbook> elements gets decomposed into a row of the ALLPUBLICATIONS table.
| 3a and 3b
|
The childrens_rowSet annotation is specified on the isbn element declaration and the title
|
attribute declaration in the <childrensbook> element. This indicates that isbn and title information
|
from <childrensbook> elements gets decomposed into a row of the ALLPUBLICATIONS table.
| The following table results from decomposing the previously shown document with the annotated XML
| schema:
|
Table 77. ALLPUBLICATIONS
ISBN
PUBS TITLE
0-11-011111-0
|
|
5-55-555555-5
Children's Fables
| The previous example shows a simple case of decomposing using rowsets. Rowsets can be used in more
| complex mappings to group together multiple items from different parts of an XML schema to form rows
| on the same table and column pair.
| Conditional transformations
| Rowsets let you apply different transformations to the values that are being decomposed, depending on
| the values themselves.
| Example: The following two instances of an element named temperature have different attribute values:
| <temperature unit="Celsius">49</temperature>
| <temperature unit="Farenheit">49</temperature>
364
|
|
|
|
If you decompose these values into the same table, you need to map all elements with the attribute
unit="Celsius" to one rowset and all elements with the attribute unit="Farenheit" to another rowset. Then
you can apply a conversion formula to values for one rowset so that all values are in the same
temperature units before you insert the values into the table.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following annotated XML schema demonstrates this technique.
Notes for the annotated XML schema document:
|
|
In the global <xs:annotation>, the temp_celcius rowset and the temp_farenheit rowset are
declared for later reference in the XML schema.
|
|
|
|
A conversion formula converts values in the temp_farenheit rowset to Celsius units so that all
values are in Celsius units when you insert them into a table. The expression annotation must
contain CAST specifications to cast the arguments and the return type of the function to the
corresponding SQL data types with which the function is defined.
|
|
All elements with the attribute unit="Celsius" are mapped to the temp_celcius rowset, and all
elements with the attribute unit="Farenheit" are mapped to the temp_farenheit rowset.
<db2-xdb:name>TEMPERATURE_DATA</db2-xdb:name>
<db2-xdb:rowSet>temp_celcius</db2-xdb:rowSet>
<db2-xdb:rowSet>temp_farenheit</db2-xdb:rowSet>
</db2-xdb:table>
...
Note 1
<xs:element name="temperature">
<xs:annotation>
<xs:appinfo>
<db2-xdb:column>col1</db2-xdb:column>
<db2-xdb:column>col1</db2-xdb:column>
<db2-xdb:expression>CAST(myudf_convertToCelcius(CAST($DECOMP_CONTENT AS FLOAT)) AS FLOAT)
</db2-xdb:expression>
Note 2
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:attribute name="unit" type="xs:string">
<xs:annotation>
<xs:appinfo>
Note 3
<db2-xdb:condition>$DECOMP_CONTENT = Celsius</db2-xdb:condition>
<db2-xdb:condition>$DECOMP_CONTENT = Farenheit</db2-xdb:condition>
</xs:appinfo>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
SQL programming
365
| Decomposition annotation example: Mapping to an XML column

| In annotated XML schema decomposition, you can map an XML fragment to a column defined using the
| XML data type.
| Consider the following XML document:
| <publications>
|
|
<isbn>0-11-011111-0</isbn>
|
|
|
|
|
</textbook>
| </publications>
|
|
|
|
If you wanted to store the <textbook> XML element and book title as follows, you would add
annotations to the declarations of the <textbook> element and title attribute in the corresponding XML
schema document. The annotations should specify the DETAILS and TITLE columns, where the DETAILS
column has been defined with the XML type, as well as the TEXTBOOKS table.
Table 78. TEXTBOOKS
TITLE
DETAILS
||
|
|
|
|
|
|
|

<isbn>0-11-011111-0</isbn>
</textbook>
| Depending on the annotation, an annotation can be specified in the schema document as an attribute or
| an element. Some annotations can be specified as either. Refer to the documentation for each specific
| annotation to determine how a particular annotation can be specified.
| Specify the target table and column using either db2-xdb:rowSet and db2-xdb:column as attributes of
| <xs:element> or <xs:attribute> or the <db2-xdb:rowSet> and <db2-xdb:column> children elements of
| <db2-xdb:rowSetMapping>. Specifying these mappings as elements or attributes are equivalent.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following fragment of the XML schema document shows how two mappings are added to the
<textbook> element and title attribute by specifying annotations as attributes.
<xs:complexType>
<xs:sequence>
<xs:element name="textbook" maxOccurs="unbounded"
db2-xdb:rowSet="TEXTBOOKS" db2-xdb:column="DETAILS">
<xs:complexType>
<xs:sequence>
<xs:element name="isbn" type="xs:string"/>
<xs:element name="university" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="title" type="xs:string" use="required"
db2-xdb:rowSet="TEXTBOOKS" db2-xdb:column="TITLE"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
366
|
|
|
|
|
|
The db2-xdb:rowSet annotations specify the name of the target table, and the db2-xdb:column annotations
specify the name of the target column. Because the <textbook> element is of complex type and contains
complex content, and the db2-xdb:contentHandling annotation was not specified, by default, all markup
within the element (including its start and end tags) is inserted into the XML column according to the
serializeSubtree setting of db2-xdb:contentHandling. Whitespace within the XML document is preserved.
Refer to the db2-xdb:contentHandling documentation for more detail.
|
|
|
|
|
Decomposition annotation example: A value mapped to a single table that yields a

single row
|
|
|
|
|
|
|
The result of this mapping depends on the relationship between items mapped to the same rowSet. If the
values that are mapped together in a single rowSet have a one to one relationship, as determined by the
value of the maxOccurs attribute of the element or the containing model group declaration, a single row
will be formed for each instance of the mapped item in the XML document. If the values in a single
rowSet have a one to many relationship, where one value appears only once in the document for multiple
instances of another item, as indicated by the value of the maxOccurs attribute, then multiple rows will
result when the XML document is decomposed.
|
|
|
|
|
|
|
|
|
|
Consider the following XML document:
|
|
|
|
If you wanted the values of the <isbn> and <publicationDate> elements, as well as the title attribute, to
be decomposed into the TEXTBOOKS table as follows, you need to add annotations to the declarations
for these elements and attributes in the corresponding XML schema document. The annotations would
specify the table and column names that each item is mapped to.
Table 79. TEXTBOOKS
ISBN
TITLE
DATE
|
|
0-11-011111-0
2002
|
|
|
|
To map a value to a single table and column pair, you need to specify the table and column on the value
that you want to map. Do that by using one of the following sets of annotations:
v db2-xdb:rowSet and db2-xdb:column as attributes of <xs:element> or <xs:attribute>
v <db2-xdb:rowSet> and <db2-xdb:column> as child elements of <db2-xdb:rowSetMapping>
|
|
|
|
|
|
|
|
|
|
|
The following annotated XML schema specifies the db2-xdb:rowSet and db2-xdb:column annotations as
attributes.
Mapping a value from an XML document to a single table and column pair is a simple form of mapping
in annotated XML schema decomposition. This example shows the simpler case of a one to one
relationship between values in a rowSet.
<publications>
<isbn>0-11-011111-0</isbn>
</textbook>
</publications>

<xs:annotation>
<xs:appinfo>
<db2-xdb:defaultSQLSchema>"MYSCHEMA"</db2-xdb:defaultSQLSchema>
</xs:appinfo>
</xs:annotation>
SQL programming
367
|
| <xs:element name="publications">
|
<xs:complexType>
|
<xs:sequence>
|
|
<xs:complexType>
|
<xs:sequence>
|
<xs:element name="isbn" type="xs:string" maxOccurs="1"
|
db2-xdb:rowSet="TEXTBOOKS"
|
db2-xdb:column="ISBN"/>
|
|
<xs:element name="publicationDate" type="xs:gYear" maxOccurs="1"
|
|
db2-xdb:column="DATE"/>
|
|
</xs:sequence>
|
|
|
db2-xdb:column="TITLE"/>
|
</xs:complexType>
|
</xs:element>
|
</xs:sequence>
|
</xs:complexType>
| </xs:element>
| </xs:schema>
| The maxOccurs attribute for the elements that go into the rowset is 1, so the items that are mapped to the
| TEXTBOOKS table have a one-to-one relationship with each other. Therefore, a single row is formed for
| each instance of the <textbook> element.
| Decomposition annotation example: A value mapped to a single table that yields
| multiple rows
| Mapping a value from an XML document to a single table and column pair is a simple form of mapping
| in annotated XML schema decomposition. This example shows the more complex case of a one to many
| relationship between values in a rowSet.
|
|
|
|
|
|
|
The result of this mapping depends on the relationship between items mapped to the same rowSet. If the
values that are mapped together in a single rowSet have a one to one relationship, as determined by the
value of the maxOccurs attribute of the element or the containing model group declaration, a single row
will be formed for each instance of the mapped item in the XML document. If the values in a single
rowSet have a one to many relationship, where one value appears only once in the document for multiple
instances of another item, as indicated by the value of the maxOccurs attribute, then multiple rows will
result when the XML document is decomposed.
| Consider the following XML document:

| <textbook title="Programming with XML">
|
<isbn>0-11-011111-0</isbn>
|
|
|
|
| </textbook>
| If you wanted to store the ISBN and authors for a textbook as follows, you would add annotations to the
| declarations of the <isbn> and <author> elements in the corresponding XML schema document. The
| annotations should specify the ISBN and AUTHNAME columns, as well as the TEXTBOOK_AUTH table.
|
Table 80. TEXTBOOKS_AUTH
ISBN
AUTHNAME
0-11-011111-0
Mary Brown
368
Table 80. TEXTBOOKS_AUTH (continued)
ISBN
AUTHNAME
|
|
0-11-011111-0
Alex Page
|
|
|
Depending on the annotation, an annotation can be specified in the schema document as an attribute or
an element. Some annotations can be specified as either. Refer to the documentation for each specific
annotation to determine how a particular annotation can be specified.
|
|
|
|
To map a value to a single table and column pair, you need to specify the table and column on the value
that you want to map. Do that by using one of the following sets of annotations:
v db2-xdb:rowSet and db2-xdb:column as attributes of <xs:element> or <xs:attribute>
v <db2-xdb:rowSet> and <db2-xdb:column> as child elements of <db2-xdb:rowSetMapping>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following annotated XML schema specifies the <db2-xdb:rowSet> and <db2-xdb:column> annotations
as elements.
<xs:annotation>
<xs:appinfo>
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence maxOccurs="unbounded">
<xs:annotation>
<xs:appinfo>
<db2-xdb:rowSet>TEXTBOOKS_AUTH</db2-xdb:rowSet>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="author" type="xs:string" maxOccurs="unbounded">
<xs:annotation>
<xs:appinfo>
<db2-xdb:rowSet>TEXTBOOKS_AUTH</db2-xdb:rowSet>
<db2-xdb:column>AUTHNAME</db2-xdb:column>
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="title" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
</xs:schema>
SQL programming
369
| Notice how the <isbn> element is mapped only once to the ISBN column, yet it appears in two rows in
| the table. This happens automatically during the decomposition process because there are multiple
| authors per ISBN value. The value of <isbn> is duplicated in each row for every author.
| This behavior occurs because a one to many relationship is detected between the <isbn> and <author>
| elements, as the maxOccurs attribute for <author> is greater than 1.
| Note that a one to many relationship can involve more than two items, and include sets of items. The one
| to many relationship can also be deeply nested, where an item already involved in a one to many
| relationship can participate in another one to many relationship.
| Decomposition annotation example: A value mapped to multiple tables
| A single value from an XML document can be mapped to multiple tables. This example shows how to
| annotate an XML schema document to map a single value to two tables.
| Consider the following XML document.
| <textbook title="Programming with XML">
|
<isbn>0-11-011111-0</isbn>
|
|
|
|
| </textbook>
| To map a textbook's ISBN to the following two tables, you need to create two mappings on the <isbn>
| element. This can be done by adding multiple <db2-xdb:rowSetMapping> elements to the <isbn> element
| declaration in the XML schema document.
|
Table 81. TEXTBOOKS
ISBN
TITLE
|
|
0-11-011111-0
Table 82. SCHOOLPUBS
ISBN
SCHOOL
|
|
0-11-011111-0
University of London
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following fragment of the XML schema document shows how two mappings are added to the <isbn>
element declaration to specify the mappings to two tables. The value of the title attribute and
<university> element also included in the mappings.
<xs:annotation>
<xs:appinfo>
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:annotation>
<xs:appinfo>
370
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<db2-xdb:rowSet>SCHOOLPUBS</db2-xdb:rowSet>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="university" type="xs:string" maxOccurs="unbounded">
<xs:annotation>
<xs:appinfo>
<db2-xdb:rowSet>SCHOOLPUBS</db2-xdb:rowSet>
<db2-xdb:column>SCHOOL</db2-xdb:column>
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="title" type="xs:string" use="required">
<xs:annotation>
<xs:appinfo>
<db2-xdb:column>TITLE</db2-xdb:column>
</xs:appinfo>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
|
|
|
|
|
|
Decomposition annotation example: Grouping multiple values mapped to a single

table
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For example, consider the following XML document:
In annotated XML schema decomposition, you can map multiple values from unrelated elements to the
same table, while preserving the relationship between logically-related values. This is possible by
declaring multiple rowSets, which are used to group related items to form a row, as shown in this
example.
<publications>
<isbn>0-11-011111-0</isbn>
</textbook>
<childrensbook title="Childrens Fables">
<isbn>5-55-555555-5</isbn>
<author>Bob Carter</author>
<author>Melaine Snowe</author>
</childrensbook>
</publications>
SQL programming
371
| To generate the following table after decomposition, you need to ensure that values relating to a textbook
| are not grouped in the same row as values associated with a children's book. Use multiple rowSets to
| group related values and yield logically meaningful rows.
|
Table 83. ALLPUBLICATIONS
PUBS_ISBN
PUBS_TITLE
0-11-011111-0
|
|
5-55-555555-5
Children's Fables
| In a simple mapping scenario, where you are mapping a single value to a single table and column pair,
| you could just specify the table and column you want to map the value to.
|
|
|
|
|
This example shows a more complex case, however, where multiple values are mapped to the same table
and must be logically grouped. If you were to simply map each ISBN and title to the PUBS_ISBN and
PUBS_TITLE columns, without the use of rowSets, the decomposition process would not be able to
determine which ISBN value belonged with which title value. By using rowSets, you can group logically
related values to form a meaningful row.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following XML schema document shows how two rowSets are defined to distinguish values of the
<textbook> element from values of the <childrensbook> element.
<xs:annotation>
<xs:appinfo>
<db2-xdb:table>
<db2-xdb:name>ALLPUBLICATIONS</db2-xdb:name>
<db2-xdb:rowSet>testbk_rowSet</db2-xdb:rowSet>
<db2-xdb:rowSet>childrens_rowSet</db2-xdb:rowSet>
</db2-xdb:table>
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:complexType>
db2-xdb:rowSet="testbk_rowSet"
db2-xdb:column="PUBS_ISBN"/>
</xs:sequence>
db2-xdb:rowSet="testbk_rowSet"
db2-xdb:column="PUBS_TITLE"/>
</xs:complexType>
</xs:element>
<xs:element name="childrensbook">
<xs:complexType>
db2-xdb:rowSet="childrens_rowSet"
db2-xdb:column="PUBS_ISBN"/>
372
|
|
|
|
|
|
|
|
|
|
|
|
|
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
|
|
|
|
Notice how the db2-xdb:rowSet mappings in each of the element and attribute declarations do not specify
the name of a table, but rather the name of a rowSet. The rowSets are associated with the
ALLPUBLICATIONS table in the <db2-xdb:table> annotation, which must be specified as a child of
<xs:schema>.
|
|
By specifying multiple rowSets that map to the same table, you can ensure that logically related values
form a row in the table.
|
|
|
|
|
Decomposition annotation example: Multiple values from different contexts

mapped to a single table
|
|
|
|
|
|
|
|
|
|
For example, consider the following XML document:
|
|
You can map both the author and the publisher to the same table that contains contacts for a particular
book.
Table 84. BOOKCONTACTS
ISBN
CONTACT
1-11-111111-1
Alice Braun
|
|
1-11-111111-1
Math Pubs
|
|
|
The values in the CONTACT column of the resulting table come from different parts of the XML
document: one row might contain an author's name (from the <author> element, while another row
contains a publisher's name (from the <publisher> element).
|
|
|
|
|
|
|
|
The following XML schema document shows how multiple rowSets can be used to generate this table.

</xs:sequence>
db2-xdb:rowSet="childrens_rowSet"
db2-xdb:column="PUBS_TITLE"/>
</xs:complexType>
</xs:element>
In annotated XML schema decomposition, you can map multiple values to the same table and column,
such that a single column can contain values that have come from different parts of a document. This is
possible by declaring multiple rowSets, as shown in this example.
<publications>
<textbook title="Principles of Mathematics">
<isbn>1-11-111111-1</isbn>
<author>Alice Braun</author>
<publisher>Math Pubs</publisher>
</textbook>
</publications>

<xs:annotation>
<xs:appinfo>
SQL programming
373
|
<db2-xdb:table>
|
<db2-xdb:name>BOOKCONTACTS</db2-xdb:name>
|
<db2-xdb:rowSet>author_rowSet</db2-xdb:rowSet>
|
<db2-xdb:rowSet>publisher_rowSet</db2-xdb:rowSet>
|
</db2-xdb:table>
|
</xs:appinfo>
| </xs:annotation>
|
|
|
<xs:complexType>
|
|
|
|
<xs:complexType>
|
<xs:sequence>
|
|
|
<xs:annotation>
|
<xs:appinfo>
|
|
|
|
|
|
|
|
|
</xs:appinfo>
|
</xs:annotation>
|
</xs:element>
|
|
<xs:element name="author" type="xs:string" maxOccurs="unbounded">
|
<xs:annotation>
|
<xs:appinfo>
|
|
|
<db2-xdb:column>CONTACT</db2-xdb:column>
|
|
</xs:appinfo>
|
</xs:annotation>
|
</xs:element>
|
|
<xs:element name="publisher" type="xs:string">
|
<xs:annotation>
|
<xs:appinfo>
|
|
|
<db2-xdb:column>CONTACT</db2-xdb:column>
|
|
</xs:appinfo>
|
</xs:annotation>
|
</xs:element>
|
|
|
<xs:element name="university"
|
type="xs:string" maxOccurs="unbounded"/>
|
</xs:sequence>
|
<xs:attribute name="title" type="xs:string" use="required"/>
|
</xs:complexType>
|
</xs:element>
|
|
</xs:sequence>
|
</xs:complexType>
|
</xs:element>
| </xs:schema>
374
|
|
|
Notice how the db2-xdb:rowSet mappings in each of the element declarations do not specify the name of
a table, but rather the name of a rowSet. The rowSets are associated with the BOOKCONTACTS table in
the <db2-xdb:table> annotation, which must be specified as a child of <xs:schema>.
|
|
|
XML schema to SQL types compatibility for annotated schema decomposition
|
|
The following tables list XML schema data types and compatible SQL character, graphic, and date data
types for XML schema decomposition.
|
|
Table 85. Compatible XML schema and SQL data types
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Annotated XML schema decomposition supports the decomposition of XML values into columns that are
of a compatible SQL type.
SQL type
T
I
M
E
S
T
A
M
P
XML schema type
C
H
A
R
V
A
R
C
H
A
R
string, normalizedString, token
1a*
1a
base64Binary,
2*
No
No
No
hexBinary
2*
No
No
No
byte, unsigned byte
3*
No
No
No
integer, positiveInteger, negativeInteger, nonNegativeInteger,

nonPositiveInteger
3*
No
No
No
int, unsignedInt
3*
No
No
No
long, unsignedLong
3*
No
No
No
short, unsignedShort
3*
No
No
No
decimal
3*
No
No
No
float
3*
No
No
No
double
3*
No
No
No
boolean
3*
No
No
No
time
4*
No
10
No
dateTime
4*
11
12
13
duration, gMonth, gYear, gDay, gMonthDay, gYearMonth
4*
No
No
No
D
A
T
E
T
I
M
E
date
4*
14
No
No
Name, NCName, NOTATION, ID, IDREF, QName,

NMTOKEN, ENTITY
1a*
1a
No
No
No
ENTITIES, NMTOKENS, IDREFS, list types
1b*
1b
No
No
No
anyURI
6*
No
No
No
language
1a*
1a
No
No
No
anySimpleType, union types
5*
No
No
No
Notes
|
|
If the length of the input XML string is less than the defined length of the target column, then the
string is right-padded with blanks when inserted.
No
Data types are not compatible for annotated XML schema decomposition.
|
|
|
|
|
1a
Compatible if the length of the XML input string, in characters, is less than or equal to the length
of the target column in characters. If the input string is longer than the target column, then the
string is compatible only if db2-xdb:truncate is set to "true" or "1" for this column mapping.
String length is computed after normalization, where the input string is normalized according to
the whitespace facet of the XML schema type.
|
|
|
1b
Compatible according to the conditions described in 1a. The value that is inserted into the target
column is the string of concatenated list items, each separated by a single space (in accordance
with the "collapse" whitespace facet for lists).
SQL programming
375
| 2
|
|
|
|
string is compatible only if db2-xdb:truncate is set to "true" or "1" for this column mapping. The
input string is normalized according to the whitespace facet of the XML schema type. The
encoded (original) sting is inserted.
| 3
|
|
Compatible is the length of the XML input string, computed after processing according to the
db2-xdb:normalization setting, is less than or equal to the length of the target column. Also
compatible if db2-xdb:truncate is set to "true" or "1" for this column mapping.
| 4
|
|
|
Compatible if the number of characters is the string representation of the XML input value,
computed after processing according to the db2-xdb:normalization setting, is less than or equal to
the length of the target column in characters. Also compatible if db2-xdb:truncate is set to "true"
or "1" for this column mapping.
| 5
|
|
|
|
value that is inserted into the target column in either case is the character content of the element
or attribute.
| 6
|
|
|
Compatible if the string length of URI, in characters, is less than or equal to the length of the
target column in characters. If the input string is longer than the target column, then the string is
compatible only if db2-xdb:truncate is set to "true" or "1" for this column mapping. Note that the
URI itself, not the resource the URI points to, is inserted.
| 7
Compatible if the string is of a valid date format: yyyy-mm-dd, mm/dd/yyyy, or dd.mm.yyyy.
| 8
Compatible if the string is of a valid time format: hh.mm.ss, hh:mm AM or PM, or hh:mm:ss.
| 9
Compatible if the string is of a valid timestamp format: yyyy-mm-dd-hh.mm.ss.nnnnnn.
| 10
|
|
For XML values that contain subseconds, compatible only if the decomposition annotation
specifies db2-xdb:truncate as "true" or "1". For XML values with timezone indicators and
db2-xdb:truncate is set to "true" or "1" , timezone indicators are inserted without the timezone.
| 11
Compatible if the year is composed of four digits and is not preceded by the '-' sign.
| 12
|
Compatible if the XML value does not have a timezone indicator. If the XML value has a
timezone indicator, then the values are compatible if db2-xdb:truncate is set to "true" or "1".
| 13
|
|
|
Compatible if the year is composed of four digits and is not preceded by the '-' sign. For XML
values with timezone indicators, compatible if db2-xdb:truncate is set to "true" or "1". If
subseconds are specified with more than six digits, compatible if db2-xdb:truncate is set to "true"
or "1".
| 14
|
|
Compatible if the year is composed of four digits and is not preceded by the '-' sign. For XML
values with timezone indicators, compatible if db2-xdb:truncate is set to "true" or "1". (Date
values are inserted without the timezone in this case.)
| Table 86. Compatible XML schema and SQL data types

|
|
|
|
|
|
|
|
|
|
|
|
|
SQL type
V
A
R
G
R
A
P
H
I
C
C
L
O
B
D
B
C
L
O
B
XML schema type
G
R
A
P
H
I
C
1a*
1a
1a
1a*
base64Binary,
No
No
No
376
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 86. Compatible XML schema and SQL data types (continued)
SQL type
XML schema type
G
R
A
P
H
I
C
V
A
R
G
R
A
P
H
I
C
C
L
O
B
D
B
C
L
O
B
hexBinary
No
No
No
byte, unsigned byte
No
No
No
integer, positiveInteger, negativeInteger, nonNegativeInteger,

nonPositiveInteger
No
No
No
int, unsignedInt
No
No
No
long, unsignedLong
No
No
No
No
No
No
decimal
No
No
No
float
No
No
No
double
No
No
No
boolean
No
No
No
time
No
No
No
dateTime
No
No
No
No
No
No
date
No
No
No
Name, NCName, NOTATION, ID, IDREF, QName, NMTOKEN,

ENTITY
1a*
1a
1a
1a*
1b*
1b
1b
1b*
anyURI
No
No
No
language
No
No
1a
No
2a*
2a
2a
2a*
Notes
|
|
No
|
|
|
|
|
1a
Compatible if the length of the XML input string, in double-byte characters, is less than or equal
to the length of the target column in characters. If the input string is longer than the target
column, then the string is compatible only if db2-xdb:truncate is set to "true" or "1" for this
column mapping. String length is computed after normalization, where the input string is
normalized according to the whitespace facet of the XML schema type.
|
|
|
1b
|
|
|
|
|
2a
value that is inserted into the target in either case is the character content of the element or
attribute.
|
|
|
|
|
input string is normalized according to the whitespace facet of the XML schema type. The
encoded (original) sting is inserted.
SQL programming
377
| 4
|
|
Compatible if the length of the XML string, computed after processing according to the
db2-xdb:normalization setting, is less than or equal to the length of the target column in
characters. Also compatible if db2-xdb:truncate is set to "true" or "1" for this column mapping.
| 5
|
|
|
Compatible if the number of characters in the string representation of the XML input value,
computed after processing according to the db2-xdb:normalization setting, is less than or equal to
the length of the target column in characters. Also compatible if db2-xdb:truncate is set to "true"
or "1" for this column mapping.
| 6
|
|
|
Compatible if the string length of URI, in characters, is less than or equal to the length of the
target column in characters. If the input string is longer than the target column, then the string is
compatible only if db2-xdb:truncate is set to "true" or "1" for this column mapping. Note that the
URI itself, not the resource the URI points to, is inserted.
| The following table lists XML schema data types and compatible SQL binary data types for XML schema
| decomposition.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SQL type
XML schema type
B
I
N
A
R
Y
V
A
R
B
I
N
A
R
Y
B
L
O
B
1a*
1a
1a
base64Binary,
1a
1a
1a
hexBinary
2*
byte, unsigned byte
No
No
No
integer, positiveInteger, negativeInteger, nonNegativeInteger, nonPositiveInteger
No
No
No
int, unsignedInt
No
No
No
long, unsignedLong
No
No
No
No
No
No
decimal
No
No
No
float
No
No
No
double
No
No
No
boolean
No
No
No
time
No
No
No
dateTime
No
No
No
No
No
No
date
No
No
No
Name, NCName, NOTATION, ID, IDREF, QName, NMTOKEN, ENTITY
1a*
1a
1a
1b*
1b
1b
anyURI
1a
1a
1a
language
1a*
1a
1a
3*
| Notes
|
|
| No
| 1a
|
|
|
|
value that is inserted into the target in either case is the character content of the element or
attribute.
378
|
|
|
1b
|
|
|
|
|
Compatible if the length of the XML input string, in bytes, is less than or equal to the length of
the target column in bytes. If the input string is longer than the target column, then the string is
compatible only if db2-xdb:truncate is set to "true" or "1" for this column mapping. String length
is computed after normalization, where the input string is normalized according to the
whitespace facet of the XML schema type. The encoded (original) string is inserted.
|
|
|
|
|
Compatible if the length of the XML input string, in bytes, is less than or equal to the length of
the target column in bytes. If the input string is longer than the target column, then the string is
compatible only if db2-xdb:truncate is set to "true" or "1" for this column mapping. The value that
is inserted into the target column in either case is the character content of the element or
attribute.
|
|
The following tables list XML schema data types and compatible SQL numeric data types for XML
schema decomposition.
|
|
Table 88. Compatible XML schema and SQL data types
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SQL type
XML schema type

S
M
A
L
L
I
N
T
I
N
T
E
G
E
R
B
I
G
I
N
T
R
E
A
L
D
O
U
B
L
E
base64Binary,
No
No
No
No
No
No
hexBinary
No
No
No
No
No
No
byte, unsigned byte
integer, positiveInteger, negativeInteger,

nonNegativeInteger, nonPositiveInteger
int, unsignedInt
long, unsignedLong
decimal
float
double
boolean
time
No
No
No
No
No
No
dateTime
No
No
No
No
No
No
duration, gMonth, gYear, gDay, gMonthDay,

gYearMonth
No
No
No
No
No
No
date
No
No
No
No
No
No
Name, NCName, NOTATION, ID, IDREF, QName,

NMTOKEN, ENTITY
No
No
No
No
No
No
No
No
No
No
No
No
anyURI
No
No
No
No
No
No
language
No
No
No
No
No
No
No
No
No
No
No
No
Notes
No
Compatible if the following conditions are true:
|
|
|
D
E
C
F
L
O
A
T
v The string complies with the XML schema lexical representation rules for the target type.
v The string can be converted to the numeric value without truncation or loss of significant
digits.
SQL programming
379
| 2
Compatible, and where -0 is in the value space of the XML type, -0 is stored in the database.
| 3
|
Compatible if the XML type is in the range of the SQL type. Where -0 is in the value space of the
XML type, -0 is stored in the database.
| 4
|
Compatible if value can be converted to the numeric value without truncation of loss of
significant digits. Where -0 is in the value space of the XML type, -0 is stored in the database.
| 5
|
Compatible if the value can be converted to the numeric value without truncation or loss of
significant digits, and the value is not "INF", "-INF", or "NaN". -0 is stored as 0 in the database.
| 6
Compatible is the value is not "INF", "-INF", or "NaN". -0 is stored as 0 in the database.
| 7
Compatible, and the value inserted is '0' (for false) or '1' (for true).

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
XML schema type

SQL type
D
E
C
I
M
A
L
N
U
M
E
R
I
C
base64Binary,
No
No
hexBinary
No
No
byte, unsigned byte
integer, positiveInteger, negativeInteger, nonNegativeInteger, nonPositiveInteger
int, unsignedInt
long, unsignedLong
decimal
float
double
boolean
time
No
No
dateTime
No
No
No
No
date
No
No
Name, NCName, NOTATION, ID, IDREF, QName, NMTOKEN, ENTITY
No
No
No
No
anyURI
No
No
language
No
No
No
No
| Notes
| No
| 1
|
|
|
Compatible if the following conditions are true:

v The string complies with the XML schema lexical representation rules for the target type.
v The string can be converted to the numeric value without truncation or loss of significant
digits.
| 2
Compatible, and where -0 is in the value space of the XML type, -0 is stored in the database.
| 3
|
Compatible if the XML type is in the range of the SQL type. Where -0 is in the value space of the
XML type, -0 is stored in the database.
| 4
|
Compatible if value can be converted to the numeric value without truncation of loss of
significant digits. Where -0 is in the value space of the XML type, -0 is stored in the database.
380
|
|
Compatible if the value can be converted to the numeric value without truncation or loss of
significant digits, and the value is not "INF", "-INF", or "NaN". -0 is stored as 0 in the database.
Compatible is the value is not "INF", "-INF", or "NaN". -0 is stored as 0 in the database.
Compatible, and the value inserted is '0' (for false) or '1' (for true).
|
|
Limits and restrictions for annotated XML schema decomposition
Limits
Table 90. Limits for annotated XML schema decomposition
Condition
Limit value
Maximum size of document to be decomposed
2 GB
|
|
Maximum number of tables referred to in a single

annotated XML schema
100
Maximum length of a string value of db2-xdb:expression
1024 bytes
Maximum length of a string value of db2-xdb:condition
1024 bytes
Maximum number of steps in db2-xdb:locationPath
128
|
|
Maximum number of unique annotation in an XML

schema
64 KB
|
|
|
Maximum string length of the value of db2-xdb:name

(table name), db2-xdb:column, db2xdb:defaultSQLSchema, or db2-xdb:SQLSchema
Same as the limit for the corresponding DB2 object
|
|
Maximum string length of the value of db2-xdb:rowSet
same as the limit for db2-xdb:name
Restrictions
|
|
Annotated XML schema decomposition does not support the following:

v Decomposition of element of attribute wildcards
|
|
|
|
|
|
|
|
|
|
Elements or attributes in the XML document that correspond to the <xs:any> or <xs:anyAttribute>
declaration in the XML schema are not decomposed.
However, if these elements or attributes are children of elements that are decomposed with
db2-xdb:contentHandling set to serializeSubtree or stringValue, the contents of the wildcard
elements or attributes are decomposed as part of the serialized subtree or string value. These wildcard
elements or attributes must satisfy the namespace constraints that are specified in the corresponding
<xs:any> or <xs:anyAttribute> declarations.
v Substitution groups
An error is generated if a member of a substitution group appears in an XML document where the
group head appears in the XML schema.
|
|
|
|
|
|
|
|
|
v Runtime substitution using xsi:type

An element is decomposed according to the mappings in the schema type that is associated with the
element name in the XML schema. Use of xsi:type to specify a different type for an element in the
document results in a decomposition error.
v Recursive elements (elements that refer to themselves)
Annotated XML schemas that contain recursive element declarations cannot be enabled for
decomposition.
v Updates or deletes of existing rows in target tables
Currently, decomposition can only insert new rows into target tables.
v Referential constraints between tables that are updated by decomposition
Certain limits and restrictions apply to annotated XML schema decomposition.
SQL programming
381
|
|
To circumvent this restriction, use different annotated schemas for multiple decomposition operations
on the same instance document, to control the order in which the parent or child tables are updated.
| v Attributes of simple type derived from NOTATION: decomposition inserts only the notation name.
| v Attributes of type ENTITY: decomposition inserts only the entity name.
| v Multiple mappings to the same rowSet and column with db2-xdb:expression and db2-xdb:condition:
|
where multiple items can be legally mapped to the same rowSet and column, according to mapping
|
rules, the mappings must not contain the db2-xdb:expression or db2-xdb:condition annotations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Schema for XML decomposition annotations

Annotated XML schema decomposition supports a set of decomposition annotations that enable you to
specify how XML documents are to be decomposed and inserted into database tables. This topic shows
the XML schema for the annotated schema as defined by XML decomposition.
xmlns="http://www.ibm.com/xmlns/prod/db2/xdb1"
targetNamespace="http://www.ibm.com/xmlns/prod/db2/xdb1"
elementFormDefault="qualified" >
<xs:element name="defaultSQLSchema" type="xs:string"/>
<xs:attribute name="rowSet" type="xs:string"/>
<xs:attribute name="column" type="xs:string"/>
<xs:attribute name="locationPath" type="xs:string"/>
<xs:attribute name="truncate" type="xs:boolean"/>
<xs:attribute name="contentHandling">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="serializeSubtree"/>
<xs:enumeration value="stringValue"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="normalization" >
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="original"/>
<xs:enumeration value="whitespaceStrip"/>
<xs:enumeration value="canonical"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="expression" type="xs:string"/>
<xs:attribute name="condition" type="xs:string"/>
<xs:element name="table">
<xs:complexType>
<xs:sequence>
<xs:element name="SQLSchema" type="xs:string" minOccurs="0"/>
<xs:element name="name" type="xs:string"/>
<xs:element name="rowSet" type="xs:string"
maxOccurs="unbounded" form="qualified"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="rowSetMapping">
<xs:complexType>
<xs:sequence>
<xs:element name="rowSet" type="xs:string" />
<xs:element name="column" type="xs:string" minOccurs="0"/>
<xs:element name="expression" type="xs:string" minOccurs="0" />
<xs:element name="condition" type="xs:string" minOccurs="0"/>
</xs:sequence>
<xs:attribute ref="truncate" />
<xs:attribute ref="locationPath" />
<xs:attribute ref="normalization" />
<xs:attribute ref="contentHandling" />
</xs:complexType>
382
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</xs:element>
<xs:element name=rowSetOperationOrder>
<xs:complexType>
<xs:choice minOccurs=1 maxOccurs=1>
<xs:element name=order type=orderType minOccurs=1
maxOccurs=unbounded/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:complexType name=orderType>
<xs:sequence>
<xs:element name=rowSet type=xsd:string minOccurs=2
maxOccurs=unbounded/>
</xs:sequence>
</xs:complexType>
</xs:schema>
Using SQL in different environments

You can use SQL in many different environments.
Using a cursor
It is used within an SQL program to maintain a position in the result table. SQL uses a cursor to work
with the rows in the result table and to make them available to your program. Your program can have
several cursors, although each must have a unique name.
Statements related to using a cursor include the following:
v A DECLARE CURSOR statement to define and name the cursor and specify the rows to be retrieved
with the embedded select statement.
v OPEN and CLOSE statements to open and close the cursor for use within the program. The cursor
must be opened before any rows can be retrieved.
v A FETCH statement to retrieve rows from the cursor's result table or to position the cursor on another
row.
v An UPDATE ... WHERE CURRENT OF statement to update the current row of a cursor.
v A DELETE ... WHERE CURRENT OF statement to delete the current row of a cursor.
Related reference:
Updating data as it is retrieved from a table on page 114
You can update rows of data as you retrieve them by using a cursor.
CLOSE
DECLARE CURSOR
DELETE
FETCH
UPDATE
Types of cursors
SQL supports serial and scrollable cursors. The type of cursor determines the positioning methods that
can be used with the cursor.
Serial cursor
A serial cursor is one defined without the SCROLL keyword.
SQL programming
383
For a serial cursor, each row of the result table can be fetched only once per OPEN of the cursor. When
the cursor is opened, it is positioned before the first row in the result table. When a FETCH is issued, the
cursor is moved to the next row in the result table. That row is then the current row. If host variables are
specified (with the INTO clause on the FETCH statement), SQL moves the current row's contents into
your program's host variables.
This sequence is repeated each time a FETCH statement is issued until the end-of-data (SQLCODE = 100)
is reached. When you reach the end-of-data, close the cursor. You cannot access any rows in the result
table after you reach the end-of-data. To use a serial cursor again, you must first close the cursor and
then re-issue the OPEN statement. You can never back up using a serial cursor.
Scrollable cursor
For a scrollable cursor, the rows of the result table can be fetched many times. The cursor is moved
through the result table based on the position option specified on the FETCH statement. When the cursor
is opened, it is positioned before the first row in the result table. When a FETCH is issued, the cursor is
positioned to the row in the result table that is specified by the position option. That row is then the
current row. If host variables are specified (with the INTO clause on the FETCH statement), SQL moves
the current row's contents into your program's host variables. Host variables cannot be specified for the
BEFORE and AFTER position options.
This sequence is repeated each time a FETCH statement is issued. The cursor does not need to be closed
when an end-of-data or beginning-of-data condition occurs. The position options enable the program to
continue fetching rows from the table.
The following scroll options are used to position the cursor when issuing a FETCH statement. These
positions are relative to the current cursor location in the result table.
NEXT
Positions the cursor on the next row. This is the default if no position is
specified.
PRIOR
Positions the cursor on the previous row.
FIRST
Positions the cursor on the first row.
LAST
Positions the cursor on the last row.
BEFORE
Positions the cursor before the first row.
AFTER
Positions the cursor after the last row.
CURRENT
Does not change the cursor position.
RELATIVE n
Evaluates a host variable or integer n in relationship to the cursor's current

position. For example, if n is -1, the cursor is positioned on the previous row of
the result table. If n is +3, the cursor is positioned three rows after the current
row.
For a scrollable cursor, the end of the table can be determined by the following:
FETCH AFTER FROM C1
Once the cursor is positioned at the end of the table, the program can use the PRIOR or RELATIVE scroll
options to position and fetch data starting from the end of the table.
Examples: Using a cursor

These examples show the SQL statements that you can include in a program to define and work with a
serial and a scrollable cursor.
Suppose that your program examines data about people in department D11. You can use either a serial or
a scrollable cursor to obtain information about the department from the CORPDATA.EMPLOYEE table.
384
For the serial cursor example, the program processes all of the rows from the table, updating the job for
all members of department D11 and deleting the records of employees from the other departments.
Table 91. A serial cursor example
Serial cursor SQL statement
Described in section
Step 1: Defining the cursor on page 386.
EXEC SQL
DECLARE THISEMP CURSOR FOR
SELECT EMPNO, LASTNAME,
WORKDEPT, JOB
FOR UPDATE OF JOB
END-EXEC.
Step 2: Opening the cursor on page 387.
EXEC SQL
OPEN THISEMP
END-EXEC.
EXEC SQL
WHENEVER NOT FOUND
GO TO CLOSE-THISEMP
END-EXEC.
EXEC SQL
FETCH THISEMP
INTO :EMP-NUM, :NAME2,
:DEPT, :JOB-CODE
END-EXEC.
... for all employees
in department D11, update
the JOB value:
Step 3: Specifying what to do when the

end of data is reached on page 387.
Step 4: Retrieving a row using a cursor

on page 388.
Step 5a: Updating the current row on

page 389.
EXEC SQL
SET JOB = :NEW-CODE
END-EXEC.
... then print the row.
... for other employees,
delete the row:
Step 5b: Deleting the current row on

page 389.
EXEC SQL
DELETE FROM CORPDATA.EMPLOYEE
END-EXEC.
Branch back to fetch and process the next row.
Step 6: Closing the cursor on page 389.
CLOSE-THISEMP.
EXEC SQL
CLOSE THISEMP
END-EXEC.
SQL programming
385
For the scrollable cursor example, the program uses the RELATIVE position option to obtain a
representative sample of salaries from department D11.
Table 92. A scrollable cursor example
Scrollable cursor SQL statement
Described in section
Step 1: Defining the cursor.
EXEC SQL
DECLARE THISEMP DYNAMIC SCROLL CURSOR FOR
SELECT EMPNO, LASTNAME,
SALARY
WHERE WORKDEPT = 'D11'
END-EXEC.
Step 2: Opening the cursor on page 387.
EXEC SQL
OPEN THISEMP
END-EXEC.
EXEC SQL
WHENEVER NOT FOUND
GO TO CLOSE-THISEMP
END-EXEC.
...initialize program summation
salary variable
EXEC SQL
FETCH RELATIVE 3 FROM THISEMP
INTO :EMP-NUM, :NAME2,
:JOB-CODE
END-EXEC.
...add the current salary to
program summation salary
...branch back to fetch and
process the next row.
Step 3: Specifying what to do when the end of

data is reached on page 387.
Step 4: Retrieving a row using a cursor on page

388.
...calculate the average

salary
Step 6: Closing the cursor on page 389.
CLOSE-THISEMP.
EXEC SQL
CLOSE THISEMP
END-EXEC.
Step 1: Defining the cursor:

To define a cursor to access the result table, use the DECLARE CURSOR statement.
The DECLARE CURSOR statement names a cursor and specifies a select-statement. The select-statement
defines a set of rows that, conceptually, make up the result table. For a serial cursor, the statement looks
like this (the FOR UPDATE OF clause is optional):
EXEC SQL
DECLARE cursor-name CURSOR FOR
SELECT column-1, column-2 ,...
FROM table-name , ...
FOR UPDATE OF column-2 ,...
END-EXEC.
386
For a scrollable cursor, the statement looks like this (the WHERE clause is optional):
EXEC SQL
DECLARE cursor-name SCROLL CURSOR FOR
SELECT column-1, column-2 ,...
FROM table-name ,...
WHERE column-1 = expression ...
END-EXEC.
The select-statements shown here are rather simple. However, you can code several other types of clauses
in a select-statement within a DECLARE CURSOR statement for a serial and a scrollable cursor.
If you intend to update any columns in any or all of the rows of the identified table (the table named in
the FROM clause), include the FOR UPDATE OF clause. It names each column you intend to update. If
you do not specify the names of columns, and you specify either the ORDER BY clause or FOR READ
ONLY clause, a negative SQLCODE is returned if an update is attempted. If you do not specify the FOR
UPDATE OF clause, the FOR READ ONLY clause, the ORDER BY clause, and the result table is not
read-only and the cursor is not scrollable, you can update any of the columns of the specified table.
You can update a column of the identified table even though it is not part of the result table. In this case,
you do not need to name the column in the SELECT statement. When the cursor retrieves a row (using
FETCH) that contains a column value you want to update, you can use UPDATE ... WHERE CURRENT
OF to update the row.
For example, assume that each row of the result table includes the EMPNO, LASTNAME, and
WORKDEPT columns from the CORPDATA.EMPLOYEE table. If you want to update the JOB column
(one of the columns in each row of the CORPDATA.EMPLOYEE table), the DECLARE CURSOR
statement should include FOR UPDATE OF JOB ... even though JOB is omitted from the SELECT
statement.
For information about when the result table and cursor are read-only, see DECLARE CURSOR in the SQL
reference topic collection.
Step 2: Opening the cursor:
To begin processing the rows of the result table, issue the OPEN statement.
When your program issues the OPEN statement, SQL processes the select-statement within the DECLARE
CURSOR statement to identify a set of rows, called a result table, using the current value of any host
variables specified in the select-statement. A result table can contain zero, one, or many rows, depending
on the extent to which the search condition is satisfied. The OPEN statement looks like this:
EXEC SQL
OPEN cursor-name
END-EXEC.
Step 3: Specifying what to do when the end of data is reached:

The end-of-data condition occurs when the FETCH statement has retrieved the last row in the result table
and your program issues a subsequent FETCH statement.
To find out when the end of the result table is reached, test the SQLCODE field for a value of 100 or test
the SQLSTATE field for a value of '02000' (that is, end of data).
For example:
SQL programming
387
...
IF SQLCODE =100 GO TO DATA-NOT-FOUND.
or
IF SQLSTATE =02000 GO TO DATA-NOT-FOUND.
An alternative to this technique is to code the WHENEVER statement. Using WHENEVER NOT FOUND
can result in a branch to another part of your program, where a CLOSE statement is issued. The
WHENEVER statement looks like this:
EXEC SQL
WHENEVER NOT FOUND GO TO symbolic-address
END-EXEC.
Your program should anticipate an end-of-data condition whenever a cursor is used to fetch a row, and
should be prepared to handle this situation when it occurs.
When you are using a serial cursor and the end of data is reached, every subsequent FETCH statement
returns the end-of-data condition. You cannot position the cursor on rows that are already processed. The
CLOSE statement is the only operation that can be performed on the cursor.
When you are using a scrollable cursor and the end of data is reached, the result table can still process
more data. You can position the cursor anywhere in the result table using a combination of the position
options. You do not need to close the cursor when the end of data is reached.
Step 4: Retrieving a row using a cursor:
To move the contents of a selected row into the host variables of your program, use the FETCH
statement.
The SELECT statement within the DECLARE CURSOR statement identifies rows that contain the column
values your program wants. However, SQL does not retrieve any data for your application program until
the FETCH statement is issued.
When your program issues the FETCH statement, SQL uses the current cursor position as a starting point
to locate the requested row in the result table. This changes that row to the current row. If an INTO
clause was specified, SQL moves the current row's contents into your program's host variables. This
sequence is repeated each time the FETCH statement is issued.
SQL maintains the position of the current row (that is, the cursor points to the current row) until the next
FETCH statement for the cursor is issued. The UPDATE statement does not change the position of the
current row within the result table, although the DELETE statement does.
The serial cursor FETCH statement looks like this:
EXEC SQL
FETCH cursor-name
INTO :host variable-1[, :host variable-2] ...
END-EXEC.
The scrollable cursor FETCH statement looks like this:

EXEC SQL
FETCH RELATIVE integer
FROM cursor-name
INTO :host variable-1[, :host variable-2] ...
END-EXEC.
388
Step 5a: Updating the current row:

When your program has positioned the cursor on a row, you can update the row by using the UPDATE
statement with the WHERE CURRENT OF clause. The WHERE CURRENT OF clause specifies a cursor
that points to the row that you want to update.
The UPDATE ... WHERE CURRENT OF statement looks like this:
EXEC SQL
UPDATE table-name
SET column-1 = value [, column-2 = value] ...
WHERE CURRENT OF cursor-name
END-EXEC.
When used with a cursor, the UPDATE statement:

v Updates only one rowthe current row
v Identifies a cursor that points to the row to be updated
v Requires that the columns updated be named previously in the FOR UPDATE OF clause of the
DECLARE CURSOR statement, if an ORDER BY clause was also specified
After you update a row, the cursor's position remains on that row (that is, the current row of the cursor
does not change) until you issue a FETCH statement for the next row.
Step 5b: Deleting the current row:
When your program has retrieved the current row, you can delete the row by using the DELETE
statement with the WHERE CURRENT OF clause. The WHERE CURRENT OF clause specifies a cursor
that points to the row that you want to delete.
The DELETE ... WHERE CURRENT OF statement looks like this:
EXEC SQL
DELETE FROM table-name
WHERE CURRENT OF cursor-name
END-EXEC.
When used with a cursor, the DELETE statement:

v Deletes only one rowthe current row
v Uses the WHERE CURRENT OF clause to identify a cursor that points to the row to be deleted
After you delete a row, you cannot update or delete another row using that cursor until you issue a
FETCH statement to position the cursor.
You can use the DELETE statement to delete all rows that meet a specific search condition. You can also
use the FETCH and DELETE ... WHERE CURRENT OF statements when you want to obtain a copy of
the row, examine it, and then delete it.
Step 6: Closing the cursor:
If you have processed the rows of a result table using a serial cursor, and you want to use the cursor
again, issue a CLOSE statement to close the cursor before opening it again.
The statement looks like this:
EXEC SQL
CLOSE cursor-name
END-EXEC.
SQL programming
389
If you processed the rows of a result table and you do not want to use the cursor again, you can let the
system close the cursor. The system automatically closes the cursor when:
v A COMMIT without HOLD statement is issued and the cursor is not declared using the WITH HOLD
clause.
v A ROLLBACK without HOLD statement is issued.
v The job ends.
v The activation group ends and CLOSQLCSR(*ENDACTGRP) was specified on the precompile.
v The first SQL program in the call stack ends and neither CLOSQLCSR(*ENDJOB) or
CLOSQLCSR(*ENDACTGRP) was specified when the program was precompiled.
v The connection to the application server is ended using the DISCONNECT statement.
v The connection to the application server was released and a successful COMMIT occurred.
v An *RUW CONNECT occurred.
Because an open cursor still holds locks on referred-to-tables or views, you should explicitly close any
open cursors as soon as they are no longer needed.
Using the multiple-row FETCH statement

The multiple-row FETCH statement can be used to retrieve multiple rows from a table or view with a
single FETCH statement. The program controls the blocking of rows by the number of rows requested on
the FETCH statement (The Override Database File (OVRDBF) command has no effect.).
The maximum number of rows that can be requested on a single fetch call is 32 767. After the data is
retrieved, the cursor is positioned on the last row retrieved.
There are two ways to define the storage where fetched rows are placed: a host structure array or a row
storage area with an associated descriptor. Both methods can be coded in all of the languages supported
by the SQL precompilers, with the exception of the host structure array in REXX. Both forms of the
multiple-row FETCH statement allow the application to code a separate indicator array. The indicator
array should contain one indicator for each host variable that is null capable.
The multiple-row FETCH statement can be used with both serial and scrollable cursors. The operations
used to define, open, and close a cursor for a multiple-row FETCH remain the same. Only the FETCH
statement changes to specify the number of rows to retrieve and the storage where the rows are placed.
After each multiple-row FETCH, information is returned to the program through the SQLCA. In addition
to the SQLCODE and SQLSTATE fields, the SQLERRD provides the following information:
v SQLERRD3 contains the number of rows retrieved on the multiple-row FETCH statement. If
SQLERRD3 is less than the number of rows requested, then an error or end-of-data condition occurred.
v SQLERRD4 contains the length of each row retrieved.
v SQLERRD5 contains an indication that the last row in the table was fetched. It can be used to detect
the end-of-data condition in the table being fetched when the cursor does not have immediate
sensitivity to updates. Cursors which do have immediate sensitivity to updates should continue
fetching until an SQLCODE +100 is received to detect an end-of-data condition.
Related concepts:
Multiple-row FETCH using a host structure array:
To use the multiple-row FETCH statement with the host structure array, the application must define a
host structure array that can be used by SQL.
Each language has its own conventions and rules for defining a host structure array. Host structure arrays
can be defined by using variable declarations or by using compiler directives to retrieve External File
Descriptions (such as the COBOL COPY directive).
390
The host structure array consists of an array of structures. Each structure corresponds to one row of the
result table. The first structure in the array corresponds to the first row, the second structure in the array
corresponds to the second row, and so on. SQL determines the attributes of elementary items in the host
structure array based on the declaration of the host structure array. To maximize performance, the
attributes of the items that make up the host structure array should match the attributes of the columns
being retrieved.
Consider the following COBOL example:
EXEC SQL INCLUDE SQLCA
END-EXEC.
...
01 TABLE-1.
02 DEPT OCCURS 10 TIMES.
05 EMPNO
PIC X(6).
05 LASTNAME.
49 LASTNAME-LEN PIC S9(4) BINARY.
49 LASTNAME-TEXT PIC X(15).
05 WORKDEPT PIC X(3).
05 JOB
PIC X(8).
01 TABLE-2.
02 IND-ARRAY OCCURS 10 TIMES.
05 INDS PIC S9(4) BINARY OCCURS 4 TIMES.
...
EXEC SQL
DECLARE D11 CURSOR FOR
SELECT EMPNO, LASTNAME, WORKDEPT, JOB
WHERE WORKDEPT = "D11"
END-EXEC.
...
EXEC SQL
OPEN D11
END-EXEC.
PERFORM FETCH-PARA UNTIL SQLCODE NOT EQUAL TO ZERO.
ALL-DONE.
EXEC SQL CLOSE D11 END-EXEC.
...
FETCH-PARA.
EXEC SQL WHENEVER NOT FOUND GO TO ALL-DONE END-EXEC.
EXEC SQL FETCH D11 FOR 10 ROWS INTO :DEPT :IND-ARRAY
END-EXEC.
...
In this example, a cursor was defined for the CORPDATA.EMPLOYEE table to select all rows where the
WORKDEPT column equals 'D11'. The result table contains eight rows. The DECLARE CURSOR and
OPEN statements do not have any special syntax when they are used with a multiple-row FETCH
statement. Another FETCH statement that returns a single row against the same cursor can be coded
elsewhere in the program. The multiple-row FETCH statement is used to retrieve all of the rows in the
result table. Following the FETCH, the cursor position remains on the last row retrieved.
SQL programming
391
The host structure array DEPT and the associated indicator array IND-ARRAY are defined in the
application. Both arrays have a dimension of ten. The indicator array has an entry for each column in the
result table.
The attributes of type and length of the DEPT host structure array elementary items match the columns
that are being retrieved.
When the multiple-row FETCH statement has successfully completed, the host structure array contains
the data for all eight rows. The indicator array, IND_ARRAY, contains zeros for every column in every
row because no NULL values were returned.
The SQLCA that is returned to the application contains the following information:
v SQLCODE contains 0
v SQLSTATE contains '00000'
v SQLERRD3 contains 8, the number of rows fetched
v SQLERRD4 contains 34, the length of each row
v SQLERRD5 contains +100, indicating the last row in the result table is in the block
Related reference:
Multiple-row FETCH using a row storage area:
Before using a multiple-row FETCH statement with the row storage area, the application must define a
row storage area and an associated description area.
The row storage area is a host variable defined in the application. The row storage area contains the
results of the multiple-row FETCH statement. A row storage area can be a character variable with enough
bytes to hold all of the rows that are requested on the multiple-row FETCH statement.
An SQLDA that contains the SQLTYPE and SQLLEN for each returned column is defined by the
associated descriptor used on the row storage area form of the multiple-row FETCH. The information
provided in the descriptor determines the data mapping from the database to the row storage area. To
maximize performance, the attribute information in the descriptor should match the attributes of the
columns retrieved.
Consider the following PL/I example:
*....+....1....+....2....+....3....+....4....+....5....+....6....+....7...*
EXEC SQL INCLUDE SQLDA;
...
DCL DEPTPTR PTR;
DCL 1 DEPT(20) BASED(DEPTPTR),
3 EMPNO CHAR(6),
3 LASTNAME CHAR(15) VARYING,
3 WORKDEPT CHAR(3),
3 JOB CHAR(8);
DCL I BIN(31) FIXED;
DEC J BIN(31) FIXED;
DCL ROWAREA CHAR(2000);
...
392
ALLOCATE SQLDA SET(SQLDAPTR);

EXEC SQL
DECLARE D11 CURSOR FOR
SELECT EMPNO, LASTNAME, WORKDEPT, JOB
WHERE WORKDEPT = D11;
...
EXEC SQL
OPEN D11;
/* SET UP THE DESCRIPTOR FOR THE MULTIPLE-ROW FETCH */
/* 4 COLUMNS ARE BEING FETCHED
*/
SQLD = 4;
SQLN = 4;
SQLDABC = 366;
SQLTYPE(1) = 452; /* FIXED LENGTH CHARACTER - */
/* NOT NULLABLE
*/
SQLLEN(1) = 6;
SQLTYPE(2) = 456; /*VARYING LENGTH CHARACTER
*/
/* NOT NULLABLE
*/
SQLLEN(2) = 15;
SQLLEN(3) = 3;
/* NOT NULLABLE
*/
SQLLEN(4) = 8;
/*ISSUE THE MULTIPLE-ROW FETCH STATEMENT TO RETRIEVE*/
/*THE DATA INTO THE DEPT ROW STORAGE AREA
*/
/*USE A HOST VARIABLE TO CONTAIN THE COUNT OF */
/*ROWS TO BE RETURNED ON THE MULTIPLE-ROW FETCH
*/
J = 20;
/*REQUESTS 20 ROWS ON THE FETCH
...
EXEC SQL
WHENEVER NOT FOUND
GOTO FINISHED;
EXEC SQL
WHENEVER SQLERROR
GOTO FINISHED;
EXEC SQL
FETCH D11 FOR :J ROWS
USING DESCRIPTOR :SQLDA INTO :ROWAREA;
/* ADDRESS THE ROWS RETURNED
DEPTPTR = ADDR(ROWAREA);
/*PROCESS EACH ROW RETURNED IN THE ROW STORAGE
/*AREA BASED ON THE COUNT OF RECORDS RETURNED
/*IN SQLERRD3.
DO I = 1 TO SQLERRD(3);
IF EMPNO(I) = 000170 THEN
DO;
:
END;
END;
IF SQLERRD(5) = 100 THEN
DO;
/* PROCESS END OF FILE */
END;
FINISHED:
*/
*/
*/
*/
*/
In this example, a cursor has been defined for the CORPDATA.EMPLOYEE table to select all rows where
the WORKDEPT column equal 'D11'. The sample EMPLOYEE table in the Sample Tables shows the result
table contains multiple rows. The DECLARE CURSOR and OPEN statements do not have special syntax
when they are used with a multiple-row FETCH statement. Another FETCH statement that returns a
SQL programming
393
single row against the same cursor can be coded elsewhere in the program. The multiple-row FETCH
statement is used to retrieve all rows in the result table. Following the FETCH, the cursor position
remains on the final row in the block.
The row area, ROWAREA, is defined as a character array. The data from the result table is placed in the
host variable. In this example, a pointer variable is assigned to the address of ROWAREA. Each item in
the rows that are returned is examined and used with the based structure DEPT.
The attributes (type and length) of the items in the descriptor match the columns that are retrieved. In
this case, no indicator area is provided.
After the FETCH statement is completed, the ROWAREA contains all of the rows that equal 'D11', in this
case 11 rows. The SQLCA that is returned to the application contains the following:
v
v
v
v
SQLCODE contains 0
SQLSTATE contains '00000'
SQLERRD3 contains 11, the number of rows returned
SQLERRD4 contains 34, for the length of the row fetched
v SQLERRD5 contains +100, indicating the last row in the result table was fetched
In this example, the application has taken advantage of the fact that SQLERRD5 contains an indication of
the end of the file being reached. As a result, the application does not need to call SQL again to attempt
to retrieve more rows. If the cursor has immediate sensitivity to inserts, you should call SQL in case any
records were added. Cursors have immediate sensitivity when the commitment control level is something
other than *RR.
Related reference:
collections.
SQLDA (SQL descriptor area)
Unit of work and open cursors

When your program completes a unit of work, it should commit or roll back the changes that you have
made.
Unless you specified HOLD on the COMMIT or ROLLBACK statement, all open cursors are
automatically closed by SQL. Cursors that are declared with the WITH HOLD clause are not
automatically closed on COMMIT. They are automatically closed on a ROLLBACK (the WITH HOLD
clause specified on the DECLARE CURSOR statement is ignored).
If you want to continue processing from the current cursor position after a COMMIT or ROLLBACK, you
must specify COMMIT HOLD or ROLLBACK HOLD. When HOLD is specified, any open cursors are left
open and keep their cursor position so processing can resume. On a COMMIT statement, the cursor
position is maintained. On a ROLLBACK statement, the cursor position is restored to just after the last
row retrieved from the previous unit of work. All record locks are still released.
After issuing a COMMIT or ROLLBACK statement without HOLD, all locks are released and all cursors
are closed. You can open the cursor again, but you will begin processing at the first row of the result
table.
Note: Specification of the ALWBLK(*ALLREAD) parameter of the Create SQL (CRTSQLxxx) commands
can change the restoration of the cursor position for read-only cursors. For information about the
use of the ALWBLK parameter and other performance-related options on the CRTSQLxxx
commands, see Dynamic SQL applications on page 395.
Related concepts:
394
Commitment control
Dynamic SQL applications

Dynamic SQL allows an application to define and run SQL statements at program run time. An
application that uses dynamic SQL either accepts an SQL statement as input or builds an SQL statement
in the form of a character string. The application does not need to know the type of the SQL statement.
The application:
v Builds or accepts as input an SQL statement
v Prepares the SQL statement for running
v Runs the statement
v Handles SQL return codes
Notes:
v The processing of dynamic SQL can have substantially higher overhead than the processing of
static SQL because the statement might need to be fully processed at run time. In the worst
case, the statement must be fully prepared, bound, and optimized by the database before it is
run. In many other cases, if the statement has been run before, parts of the processing can be
skipped because of the algorithms used and caches maintained by the database. These features
allow the DB2 for i database to provide good performance for dynamic SQL statements. If
performance for your dynamic application is critical, consider using the extended dynamic
capability through the Process Extended Dynamic SQL (QSQPRCED) API. This feature allows
the application to maintain a persistent cache of SQL statements and substantially reduces
runtime overhead when the application runs.
v Programs that contain an EXECUTE or EXECUTE IMMEDIATE statement and that use a FOR
READ ONLY clause to make a cursor read-only experience better performance because blocking
is used to retrieve rows for the cursor.
The ALWBLK(*ALLREAD) CRTSQLxxx option will imply a FOR READ ONLY declaration for
all cursors that do not explicitly code FOR UPDATE OF or have positioned deletes or updates
that refer to the cursor. Cursors with an implied FOR READ ONLY will benefit from the second
item in this list.
Some dynamic SQL statements require the use of pointer variables. RPG/400 programs require the aid of
PL/I, COBOL, C, or ILE RPG programs to manage the pointer variables.
Related concepts:
Using interactive SQL on page 410
Interactive SQL allows a programmer or a database administrator to quickly and easily define, update,
delete, or look at data for testing, problem analysis, and database maintenance.
Related reference:
Actions allowed on SQL statements
Process Extended Dynamic SQL (QSQPRCED) API
Unit of work and open cursors on page 394
When your program completes a unit of work, it should commit or roll back the changes that you have
made.
Designing and running a dynamic SQL application

To issue a dynamic SQL statement, use the statement with either an EXECUTE statement or an EXECUTE
IMMEDIATE statement, because dynamic SQL statements are prepared at run time, not at precompile
time.
The EXECUTE IMMEDIATE statement causes the SQL statement to be prepared and run dynamically at
program run time.
SQL programming
395
There are two basic types of dynamic SQL statements: SELECT statements and non-SELECT statements.
Non-SELECT statements include such statements as DELETE, INSERT, and UPDATE.
Client/server applications that use interfaces such as Open Database Connectivity (ODBC) typically use
dynamic SQL to access the database.
Related concepts:
System i Access for Windows: Programming
CCSID of dynamic SQL statements

An SQL statement is normally a host variable. The coded character set identifier (CCSID) of the host
variable is used as the CCSID of the statement text.
Dynamic SQL statements are processed using the CCSID of the statement text. This affects variant
characters. For example, the not sign () is located at 'BA'X in CCSID 500. This means that if the CCSID
of your statement text is 500, SQL expects the not sign () to be represented by the value 'BA'X.
If the statement text CCSID is 65535, SQL processes variant characters as if they had a CCSID of 37. This
means that SQL looks for the not sign () at '5F'X.
Processing non-SELECT statements

Before building a dynamic SQL non-SELECT statement, you need to verify that this SQL statement is
allowed to be run dynamically.
To run a dynamic SQL non-SELECT statement:
1. Run the SQL statement using EXECUTE IMMEDIATE, or PREPARE the SQL statement, then
EXECUTE the prepared statement.
2. Handle any SQL return codes that might result.
The following is an example of an application running a dynamic SQL non-SELECT statement (stmtstrg):
EXEC SQL
EXECUTE IMMEDIATE :stmtstrg;
Related concepts:
Using interactive SQL on page 410
Using the PREPARE and EXECUTE statements:
If the non-SELECT statement does not contain parameter markers, you can run it dynamically using the
EXECUTE IMMEDIATE statement. However, if the non-SELECT statement contains parameter markers,
you must run it using the PREPARE and EXECUTE statements.
The PREPARE statement prepares the non-SELECT statement (for example, the DELETE statement) and
gives it a statement name you choose. If DLYPRP (*YES) is specified on the CRTSQLxxx command, the
preparation is delayed until the first time the statement is used in an EXECUTE or DESCRIBE statement,
unless the USING clause is specified on the PREPARE statement. After the statement has been prepared,
it can be run many times within the same program, using different values for the parameter markers. The
following example is of a prepared statement being run multiple times:
DSTRING = DELETE FROM CORPDATA.EMPLOYEE WHERE EMPNO = ?;
/*The ? is a parameter marker which denotes
that this value is a host variable that is
to be substituted each time the statement is run.*/
EXEC SQL PREPARE S1 FROM :DSTRING;
396
/*DSTRING is the delete statement that the PREPARE statement is

naming S1.*/
DO UNTIL (EMP =0);
/*The application program reads a value for EMP from the
display station.*/
EXEC SQL
EXECUTE S1 USING :EMP;
END;
In routines similar to the example above, you must know the number of parameter markers and their
data types, because the host variables that provide the input data are declared when the program is being
written.
Note: All prepared statements that are associated with an application server are destroyed whenever the
connection to the application server ends. Connections are ended by a CONNECT (Type 1)
statement, a DISCONNECT statement, or a RELEASE followed by a successful COMMIT.
Processing SELECT statements and using a descriptor

The basic types of SELECT statements are fixed list and varying list.
To process a fixed-list SELECT statement, an SQL descriptor is not necessary.
To process a varying-list SELECT statement, you must first declare an SQL descriptor area (SQLDA)
structure or ALLOCATE an SQLDA. Both forms of SQL descriptors can be used to pass host variable
input values from an application program to SQL and to receive output values from SQL. In addition,
information about SELECT list expressions can be returned in a PREPARE or DESCRIBE statement.
Fixed-list SELECT statements:
In dynamic SQL, a fixed-list SELECT statement retrieves data of a predictable number and type. When
using this statement, you can anticipate and define host variables to accommodate the retrieved data so
that an SQL descriptor area (SQLDA) is not necessary.
Each successive FETCH returns the same number of values as the last, and these values have the same
data formats as those returned for the last FETCH. You can specify host variables in the same manner as
for any SQL application.
You can use fixed-list dynamic SELECT statements with any SQL-supported application program.
To run fixed-list SELECT statements dynamically, your application must:
1. Place the input SQL statement into a host variable.
2. Issue a PREPARE statement to validate the dynamic SQL statement and put it into a form that can be
run. If DLYPRP (*YES) is specified on the CRTSQLxxx command, the preparation is delayed until the
first time the statement is used in an EXECUTE or DESCRIBE statement, unless the USING clause is
specified on the PREPARE statement.
3. Declare a cursor for the statement name.
4. Open the cursor.
5. FETCH a row into a fixed list of variables (rather than into a descriptor area, as if you were using a
varying-list SELECT statement.
6. When end of data occurs, close the cursor.
7. Handle any SQL return codes that result.
For example:
SQL programming
397
MOVE SELECT EMPNO, LASTNAME FROM CORPDATA.EMPLOYEE WHERE EMPNO>?

TO DSTRING.
EXEC SQL
PREPARE S2 FROM :DSTRING END-EXEC.
EXEC SQL
DECLARE C2 CURSOR FOR S2 END-EXEC.
EXEC SQL
OPEN C2 USING :EMP END-EXEC.
PERFORM FETCH-ROW UNTIL SQLCODE NOT=0.
EXEC SQL
CLOSE C2 END-EXEC.
STOP-RUN.
FETCH-ROW.
EXEC SQL
FETCH C2 INTO :EMP, :EMPNAME END-EXEC.
Note: Remember that because the SELECT statement, in this case, always returns the same number and
type of data items as previously run fixed-list SELECT statements, you do not need to use an SQL
descriptor area.
Varying-list SELECT statements:
In dynamic SQL, a varying-list SELECT statement is used when the number and format of the result
columns are not predictable; that is, you do not know the data types or the number of variables that you
need.
Therefore, you cannot define host variables in advance to accommodate the result columns returned.
Note: In REXX, steps 5.b, 6, and 7 are not applicable. REXX only supports SQL descriptors defined using
the SQLDA structure; it does not support allocated SQL descriptors.
If your application accepts varying-list SELECT statements, your program has to:
1. Place the input SQL statement into a host variable.
2. Issue a PREPARE statement to validate the dynamic SQL statement and put it into a form that can
be run. If DLYPRP (*YES) is specified on the CRTSQLxxx command, the preparation is delayed until
the first time the statement is used in an EXECUTE or DESCRIBE statement, unless the USING
clause is specified on the PREPARE statement.
3. Declare a cursor for the statement name.
4. Open the cursor (declared in step 3) that includes the name of the dynamic SELECT statement.
5. For an allocated SQL descriptor, run an ALLOCATE DESCRIPTOR statement to define the descriptor
you intend to use.
6. Issue a DESCRIBE statement to request information from SQL about the type and size of each
column of the result table.
Notes:
a. You can also code the PREPARE statement with an INTO clause to perform the functions
of PREPARE and DESCRIBE with a single statement.
b. If using an SQLDA and the SQLDA is not large enough to contain column descriptions
for each retrieved column, the program must determine how much space is needed, get
storage for that amount of space, build a new SQLDA, and reissue the DESCRIBE
statement.
398
If using an allocated SQL descriptor and the descriptor is not large enough, deallocate the
descriptor, allocate it with a larger number of entries, and reissue the DESCRIBE
statement.
7. For an SQLDA descriptor, allocate the amount of storage needed to contain a row of retrieved data.
8. For an SQLDA descriptor, put storage addresses into the SQLDA to tell SQL where to put each item
of retrieved data.
9. FETCH a row.
10. Process the data returned in the SQL descriptor.
11. Handle any SQL return codes that might result.
12. When end of data occurs, close the cursor.
13. For an allocated SQL descriptor, run a DEALLOCATE DESCRIPTOR statement to delete the
descriptor.
Related reference:
Example: A SELECT statement for allocating storage for SQLDA on page 402
Suppose that your application needs to handle a dynamic SELECT statement that changes from one use
to the next. This statement can be read from a display, passed in from another application, or built
dynamically by your application.
SQL descriptor areas:
Dynamic SQL uses an SQL descriptor area to pass information about an SQL statement between SQL and
your application.
A descriptor is required for running the DESCRIBE, DESCRIBE INPUT and DESCRIBE TABLE
statements, and can also be used on the PREPARE, OPEN, FETCH, CALL, and EXECUTE statements.
The meaning of the information in a descriptor depends on its use. In PREPARE and DESCRIBE, a
descriptor provides information to an application program about a prepared statement. In DESCRIBE
INPUT, the SQL descriptor area provides information to an application program about parameter markers
in a prepared statement. In DESCRIBE TABLE, the descriptor provides information to an application
program about the columns in a table or view. In OPEN, EXECUTE, CALL, and FETCH, a descriptor
provides information about host variables. For example, you can read values into the descriptor by using
a DESCRIBE statement, change the data values in the descriptor to use the host variables, and then reuse
the same descriptor in a FETCH statement.
If your application allows you to have several cursors open at the same time, you can code several
descriptors, one for each dynamic SELECT statement.
There are two types of descriptors. One is defined with the ALLOCATE DESCRIPTOR statement. The
other is defined with the SQLDA structure.
ALLOCATE DESCRIPTOR is not supported in REXX. SQLDAs can be used in C, C++, COBOL, PL/I,
REXX, and RPG. Because RPG/400 does not provide a way to set pointers, the SQLDA must be set
outside the RPG/400 program by a PL/I, C, C++, COBOL, or an ILE RPG program. That program must
then call the RPG/400 program.
Related reference:
SQLDA (SQL descriptor area)
SQLDA format:
An SQL descriptor area (SQLDA) consists of four variables followed by an arbitrary number of
occurrences of a sequence of six variables collectively named SQLVAR.
SQL programming
399
Note: The SQLDA in REXX is different.

When an SQLDA is used in OPEN, FETCH, CALL, and EXECUTE, each occurrence of SQLVAR describes
a host variable.
The fields of the SQLDA are as follows:
SQLDAID
SQLDAID is as used an 'eyecatcher" for storage dumps. It is a string of 8 characters that have the
value SQLDA after the SQLDA is used in a PREPARE or DESCRIBE statement. This variable is
not used for FETCH, OPEN, CALL, or EXECUTE.
Byte 7 can be used to determine if more than one SQLVAR entry is needed for each column.
Multiple SQLVAR entries may be needed if there are any LOB or distinct type columns. This flag
is set to a blank if there are not any LOBs or distinct types.
SQLDAID is not applicable in REXX.
SQLDABC
SQLDABC indicates the length of the SQLDA. It is a 4-byte integer that has the value
SQLN*LENGTH(SQLVAR) + 16 after the SQLDA is used in a PREPARE or DESCRIBE statement.
SQLDABC must have a value equal to or greater than SQLN*LENGTH(SQLVAR) + 16 before it is
used by FETCH, OPEN, CALL, or EXECUTE.
SQLABC is not applicable in REXX.
SQLN SQLN is a 2-byte integer that specifies the total number of occurrences of SQLVAR. It must be set
before being used by any SQL statement to a value greater than or equal to 0.
SQLN is not applicable in REXX.
SQLD SQLD is a 2-byte integer that specifies the number of occurrences of SQLVAR, in other words, the
number of host variables or columns described by the SQLDA. This field is set by SQL on a
DESCRIBE or PREPARE statement. In other statements, this field must be set before being used to
a value greater than or equal to 0 and less than or equal to SQLN.
SQLVAR
This group of values are repeated once for each host variable or column. These variables are set
by SQL on a DESCRIBE or PREPARE statement. In other statements, they must be set before
being used. These variables are defined as follows:
SQLTYPE
SQLTYPE is a 2-byte integer that specifies the data type of the host variable or column.
See SQLTYPE and SQLLEN for a table of the valid values. Odd values for SQLTYPE
show that the host variable has an associated indicator variable addressed by SQLIND.
SQLLEN
SQLLEN is a 2-byte integer variable that specifies the length attribute of the host variable
or column.
SQLRES
SQLRES is a 12-byte reserved area for boundary alignment purposes. Note that, in IBM i,
pointers must be on a quad-word boundary.
SQLRES is not applicable in REXX.
SQLDATA
SQLDATA is a 16-byte pointer variable that specifies the address of the host variables
when the SQLDA is used on OPEN, FETCH, CALL, and EXECUTE.
When the SQLDA is used on PREPARE and DESCRIBE, this area is overlaid with the
following information:
400
The CCSID of a character or graphic field is stored in the third and fourth bytes of
SQLDATA. For BIT data, the CCSID is 65535. In REXX, the CCSID is returned in the
variable SQLCCSID.
SQLIND
SQLIND is a 16-byte pointer that specifies the address of a small integer host variable
that is used as an indication of null or not null when the SQLDA is used on OPEN,
FETCH, CALL, and EXECUTE. A negative value indicates null and a non-negative
indicates not null. This pointer is only used if SQLTYPE contains an odd value.
When the SQLDA is used on PREPARE and DESCRIBE, this area is reserved for future
use.
SQLNAME
SQLNAME is a variable-length character variable with a maximum length of 30. After a
PREPARE or DESCRIBE, this variable contains the name of selected column, label, or
system column name. In OPEN, FETCH, EXECUTE, or CALL, this variable can be used
to pass the CCSID of character strings. CCSIDs can be passed for character and graphic
host variables.
The SQLNAME field in an SQLVAR array entry of an input SQLDA can be set to specify
the CCSID. See CCSID values in SQLDATA or SQLNAME for the layout of the CCSID
data in this field.
Note: It is important to remember that the SQLNAME field is only for overriding the
CCSID. Applications that use the defaults do not need to pass CCSID information.
If a CCSID is not passed, the default CCSID for the job is used.
The default for graphic host variables is the associated double-byte CCSID for the job
CCSID. If an associated double-byte CCSID does not exist, 65535 is used.
SQLVAR2
This is the Extended SQLVAR structure that contains 3 fields. Extended SQLVARs are needed for
all columns of the result if the result includes any distinct type or LOB columns. For distinct
types, they contain the distinct type name. For LOBs, they contain the length attribute of the host
variable and a pointer to the buffer that contains the actual length. If locators are used to
represent LOBs, these entries are not necessary. The number of Extended SQLVAR occurrences
needed depends on the statement that the SQLDA was provided for and the data types of the
columns or parameters being described. Byte 7 of SQLDAID is always set to the number of sets
of SQLVARs necessary.
If SQLD is not set to a sufficient number of SQLVAR occurrences:
v SQLD is set to the total number of SQLVAR occurrences needed for all sets.
v A +237 warning is returned in the SQLCODE field of the SQLCA if at least enough were
specified for the Base SQLVAR Entries. The Base SQLVAR entries are returned, but no
Extended SQLVARs are returned.
v A +239 warning is returned in the SQLCODE field of the SQLCA if enough SQLVARs were not
specified for even the Base SQLVAR Entries. No SQLVAR entries are returned.
SQLLONGLEN
SQLLONGLEN is a 4-byte integer variable that specifies the length attribute of a LOB
(BLOB, CLOB, or DBCLOB) host variable or column.
SQLDATALEN
SQLDATALEN is a 16-byte pointer variable that specifies the address of the length of the
host variable. This variable is used for LOB (BLOB, CLOB, and DBCLOB) host variables
only. It is not used for DESCRIBE or PREPARE.
SQL programming
401
If this field is NULL, then the actual length of the data is stored in the 4 bytes
immediately before the start of the data, and SQLDATA points to the first byte of the
field length. The length indicates the number of bytes for a BLOB or CLOB, and the
number of characters for a DBCLOB.
If this field is not NULL, it contains a pointer to a 4-byte long buffer that contains the
actual length in bytes (even for DBCLOB) of the data in the buffer pointed to by the
SQLDATA field in the matching base SQLVAR.
SQLDATATYPE_NAME
SQLDATATYPE_NAME is a variable-length character variable with a maximum length of
30. It is only used for DESCRIBE or PREPARE. This variable is set to one of the
following:
v For a distinct type column, the database manager sets this to the fully qualified distinct
type name. If the qualified name is longer than 30 bytes, it is truncated.
v For a label, the database manager sets this to the first 20 bytes of the label.
v For a column name, the database manager sets this to the column name.
Related tasks:
Coding SQL statements in REXX applications
Related reference:
Example: A SELECT statement for allocating storage for SQLDA
Example: A SELECT statement for allocating storage for SQLDA:
In other words, you don't know exactly what this statement is going to be returning every time. Your
application needs to handle the varying number of result columns with data types that are unknown
ahead of time.
For example, the following statement needs to be processed:
SELECT WORKDEPT, PHONENO
WHERE LASTNAME = PARKER
Note: This SELECT statement has no INTO clause. Dynamic SELECT statements must not have an INTO
clause, even if they return only one row.
The statement is assigned to a host variable. The host variable, in this case named DSTRING, is then
processed by using the PREPARE statement as shown:
EXEC SQL
PREPARE S1 FROM :DSTRING;
Next, you need to determine the number of result columns and their data types. To do this, you need an
SQLDA.
The first step in defining an SQLDA is to allocate storage for it. (Allocating storage is not necessary in
REXX.) The techniques for acquiring storage are language-dependent. The SQLDA must be allocated on a
16-byte boundary. The SQLDA consists of a fixed-length header that is 16 bytes in length. The header is
followed by a varying-length array section (SQLVAR), each element of which is 80 bytes in length.
402
The amount of storage that you need to allocate depends on how many elements you want to have in the
SQLVAR array. Each column you select must have a corresponding SQLVAR array element. Therefore, the
number of columns listed in your SELECT statement determines how many SQLVAR array elements you
should allocate. Because this SELECT statement is specified at run time, it is impossible to know exactly
how many columns will be accessed. Consequently, you must estimate the number of columns. Suppose,
in this example, that no more than 20 columns are ever expected to be accessed by a single SELECT
statement. In this case, the SQLVAR array should have a dimension of 20, ensuring that each item in the
select-list has a corresponding entry in SQLVAR. This makes the total SQLDA size 20 x 80, or 1600, plus
16 for a total of 1616 bytes
Having allocated what you estimated to be enough space for your SQLDA, you need to set the SQLN
field of the SQLDA equal to the number of SQLVAR array elements, in this case 20.
Having allocated storage and initialized the size, you can now issue a DESCRIBE statement.
EXEC SQL
DESCRIBE S1 INTO :SQLDA;
When the DESCRIBE statement is run, SQL places values in the SQLDA that provide information about
the select-list for your statement. The following tables show the contents of the SQLDA after the
DESCRIBE is run. Only the entries that are meaningful in this context are shown.
Table 93. SQLDA header
Description
Value
SQLAID
'SQLDA'
SQLDABC
1616
SQLN
20
SQLD
SQLDAID is an identifier field initialized by SQL when a DESCRIBE is run. SQLDABC is the byte count
or size of the SQLDA. The SQLDA header is followed by 2 occurrences of the SQLVAR structure, one for
each column in the result table of the SELECT statement being described:
Table 94. SQLVAR element 1
Description
Value
SQLTYPE
453
SQLLEN
SQLDATA (3:4)
37
SQLNAME
8 WORKDEPT

Description
Value
SQLTYPE
453
SQLLEN
SQLDATA(3:4)
37
SQLNAME
7 PHONENO
Your program might need to alter the SQLN value if the SQLDA is not large enough to contain the
described SQLVAR elements. For example, suppose that instead of the estimated maximum of 20
columns, the SELECT statement actually returns 27. SQL cannot describe this select-list because the
SQLVAR needs more elements than the allocated space allows. Instead, SQL sets the SQLD to the actual
SQL programming
403
number of columns specified by the SELECT statement and the remainder of the structure is ignored.
Therefore, after a DESCRIBE, you should compare the SQLN value to the SQLD value. If the value of
SQLD is greater than the value of SQLN, allocate a larger SQLDA based on the value in SQLD, as
follows, and perform the DESCRIBE again:
EXEC SQL
IF SQLN <= SQLD THEN
DO;
/*Allocate a larger SQLDA using the value of SQLD.*/
/*Reset SQLN to the larger value.*/
EXEC SQL
END;
If you use DESCRIBE on a non-SELECT statement, SQL sets SQLD to 0. Therefore, if your program is
designed to process both SELECT and non SELECT statements, you can describe each statement after it is
prepared to determine whether it is a SELECT statement. This example is designed to process only
SELECT statements; the SQLD value is not checked.
Your program must now analyze the elements of SQLVAR returned from the successful DESCRIBE. The
first item in the select-list is WORKDEPT. In the SQLTYPE field, the DESCRIBE returns a value for the
data type of the expression and whether nulls are applicable or not.
In this example, SQL sets SQLTYPE to 453 in SQLVAR element 1. This specifies that WORKDEPT is a
fixed-length character string result column and that nulls are permitted in the column.
SQL sets SQLLEN to the length of the column. Because the data type of WORKDEPT is CHAR, SQL sets
SQLLEN equal to the length of the character column. For WORKDEPT, that length is 3. Therefore, when
the SELECT statement is later run, a storage area large enough to hold a CHAR(3) string will be needed.
Because the data type of WORKDEPT is CHAR FOR SBCS DATA, the first 4 bytes of SQLDATA were set
to the CCSID of the character column.
The last field in an SQLVAR element is a varying-length character string called SQLNAME. The first 2
bytes of SQLNAME contain the length of the character data. The character data itself is typically the
name of a column used in the SELECT statement, in this case WORKDEPT. The exceptions to this are
select-list items that are unnamed, such as functions (for example, SUM(SALARY)), expressions (for
example, A+B-C), and constants. In these cases, SQLNAME is an empty string. SQLNAME can also
contain a label rather than a name. One of the parameters associated with the PREPARE and DESCRIBE
statements is the USING clause. You can specify it this way:
EXEC SQL
DESCRIBE S1 INTO:SQLDA
USING LABELS;
If you specify:
NAMES (or omit the USING parameter entirely)
Only column names are placed in the SQLNAME field.
SYSTEM NAMES
Only the system column names are placed in the SQLNAME field.
LABELS
Only labels associated with the columns listed in your SQL statement are entered here.
ANY
404
Labels are placed in the SQLNAME field for those columns that have labels; otherwise, the
column names are entered.
BOTH Names and labels are both placed in the field with their corresponding lengths. Remember to
double the size of the SQLVAR array because you are including twice the number of elements.
ALL
Column names, labels, and system column names are placed in the field with their corresponding
lengths. Remember to triple the size of the SQLVAR array
In this example, the second SQLVAR element contains the information for the second column used in the
select: PHONENO. The 453 code in SQLTYPE specifies that PHONENO is a CHAR column. SQLLEN is
set to 4.
Now you need to set up to use the SQLDA to retrieve values when running the SELECT statement.
After analyzing the result of the DESCRIBE, you can allocate storage for variables that are to contain the
result of the SELECT statement. For WORKDEPT, a character field of length 3 must be allocated; for
PHONENO, a character field of length 4 must be allocated. Since both of these results can be the NULL
value, an indicator variable must be allocated for each field as well.
After the storage is allocated, you must set SQLDATA and SQLIND to point to the allocated storage
areas. For each element of the SQLVAR array, SQLDATA points to the place where the result value is to
be put. SQLIND points to the place where the null indicator value is to be put. The following tables show
what the structure looks like now. Only the entries that are meaningful in this context are shown:
Table 96. SQLDA header
Description
Value
SQLAID
'SQLDA'
SQLDABC
1616
SQLN
20
SQLD

Description
Value
SQLTYPE
453
SQLLEN
SQLDATA
Pointer to area for CHAR(3) result
SQLIND
Pointer to 2 byte integer indicator for result column

Description
Value
SQLTYPE
453
SQLLEN
SQLDATA
Pointer to area for CHAR(4) result
SQLIND
Pointer to 2 byte integer indicator for result column
You are now ready to retrieve the SELECT statements results. Dynamically defined SELECT statements
must not have an INTO statement. Therefore, all dynamically defined SELECT statements must use a
cursor. Special forms of the DECLARE, OPEN, and FETCH are used for dynamically defined SELECT
statements.
The DECLARE statement for the example statement is:
EXEC SQL DECLARE C1 CURSOR FOR S1;
SQL programming
405
As you can see, the only difference is that the name of the prepared SELECT statement (S1) is used
instead of the SELECT statement itself. The actual retrieval of result rows is made as follows:
EXEC SQL
OPEN C1;
EXEC SQL
FETCH C1 USING DESCRIPTOR :SQLDA;
DO WHILE (SQLCODE = 0);
/*Process the results pointed to by SQLDATA*/
EXEC SQL
FETCH C1 USING DESCRIPTOR :SQLDA;
END;
EXEC SQL
CLOSE C1;
The cursor is opened. The result rows from the SELECT are then returned one at a time using a FETCH
statement. On the FETCH statement, there is no list of output host variables. Instead, the FETCH
statement tells SQL to return results into areas described by your SQLDA. The results are returned into
the storage areas pointed to by the SQLDATA and SQLIND fields of the SQLVAR elements. After the
FETCH statement has been processed, the SQLDATA pointer for WORKDEPT has its referenced value set
to 'E11'. Its corresponding indicator value is 0 since a non-null value was returned. The SQLDATA pointer
for PHONENO has its referenced value set to '4502'. Its corresponding indicator value is also 0 since a
non-null value was returned.
Related reference:
Varying-list SELECT statements on page 398
In dynamic SQL, a varying-list SELECT statement is used when the number and format of the result
columns are not predictable; that is, you do not know the data types or the number of variables that you
need.
SQLDA format on page 399
An SQL descriptor area (SQLDA) consists of four variables followed by an arbitrary number of
occurrences of a sequence of six variables collectively named SQLVAR.
Example: A SELECT statement using an allocated SQL descriptor:
to the next. This statement can be read from a display, passed from another application, or built
In other words, you don't know exactly what this statement is going to be returning every time. Your
application needs to be able to handle the varying number of result columns with data types that are
unknown ahead of time.
For example, the following statement needs to be processed:
Note: This SELECT statement has no INTO clause. Dynamic SELECT statements must not have an INTO
clause, even if they return only one row.
The statement is assigned to a host variable. The host variable, in this case named DSTRING, is then
processed by using the PREPARE statement as shown:
EXEC SQL
PREPARE S1 FROM :DSTRING;
Next, you need to determine the number of result columns and their data types. To do this, you need to
allocate the largest number of entries for an SQL descriptor that you think you will need. Assume that no
more than 20 columns are ever expected to be accessed by a single SELECT statement.
406
EXEC SQL
ALLOCATE DESCRIPTOR mydescr WITH MAX 20;
Now that the descriptor is allocated, the DESCRIBE statement can be done to get the column information.
EXEC SQL
DESCRIBE S1 USING DESCRIPTOR mydescr;
When the DESCRIBE statement is run, SQL places values that provide information about the statement's
select-list into the SQL descriptor area defined by 'mydescr'.
If the DESCRIBE determines that not enough entries were allocated in the descriptor, SQLCODE +239 is
issued. As part of this diagnostic, the second replacement text value indicates the number of entries that
are needed. The following code sample shows how this condition can be detected and shows the
descriptor allocated with the larger size.
/* Determine the returned SQLCODE from the DESCRIBE statement */
EXEC SQL
GET DIAGNOSTICS CONDITION 1: returned_sqlcode = DB2_RETURNED_SQLCODE;
if returned_sqlcode = 239 then do;
/* Get the second token for the SQLCODE that indicated
not enough entries were allocated */
EXEC SQL
GET DIAGNOSTICS CONDITION 1: token = DB2_ORDINAL_TOKEN_2;
/* Move the token variable from a character host variable into an integer host variable */
EXEC SQL
SET :var1 = :token;
/* Deallocate the descriptor that is too small */
EXEC SQL
DEALLOCATE DESCRIPTOR mydescr;
/* Allocate the new descriptor to be the size indicated by the retrieved token */
EXEC SQL
ALLOCATE DESCRIPTOR mydescr WITH MAX :var1;
/* Perform the describe with the larger descriptor */
EXEC SQL
DESCRIBE s1 USING DESCRIPTOR mydescr;
end;
At this point, the descriptor contains the information about the SELECT statement. Now you are ready to
retrieve the SELECT statement results. For dynamic SQL, the SELECT INTO statement is not allowed.
You must use a cursor.
EXEC SQL
DECLARE C1 CURSOR FOR S1;
You will notice that the prepared statement name is used in the cursor declaration instead of the
complete SELECT statement. Now you can loop through the selected rows, processing them as you read
them. The following code sample shows how this is done.
EXEC SQL
OPEN C1;
EXEC SQL
FETCH C1 INTO SQL DESCRIPTOR mydescr;
do while not at end of data;
/* process current data returned (see below for discussion of doing this) */
/* then read the next row */
EXEC SQL
FETCH C1 INTO SQL DESCRIPTOR mydescr;
SQL programming
407
end;
EXEC SQL
CLOSE C1;
The cursor is opened. The result rows from the SELECT statement are then returned one at a time using a
FETCH statement. On the FETCH statement, there is no list of output host variables. Instead, the FETCH
statement tells SQL to return results into the descriptor area.
After the FETCH has been processed, you can use the GET DESCRIPTOR statement to read the values.
First, you must read the header value that indicates how many descriptor entries were used.
EXEC SQL
GET DESCRIPTOR mydescr :count = COUNT;
Next you can read information about each of the descriptor entries. After you determine the data type of
the result column, you can do another GET DESCRIPTOR to return the actual value. To get the value of
the indicator, specify the INDICATOR item. If the value of the INDICATOR item is negative, the value of
the DATA item is not defined. Until another FETCH is done, the descriptor items will maintain their
values.
do i = 1 to count;
GET DESCRIPTOR mydescr VALUE :i /* set entry number to get */
:type = TYPE,
/* get the data type */
:length = LENGTH,
/* length value */
:result_ind = INDICATOR;
if result_ind >= 0 then
if type = character
GET DESCRIPTOR mydescr VALUE :i
:char_result = DATA;
/* read data into character field */
else
if type = integer
GET DESCRIPTOR mydescr VALUE :i
:int_result = DATA;
/* read data into integer field */
else
/* continue checking and processing for all data types that might be returned */
end;
There are several other descriptor items that you might need to check to determine how to handle the
result data. PRECISION, SCALE, DB2_CCSID, and DATETIME_INTERVAL_CODE are among them. The
host variable that has the DATA value read into it must have the same data type and CCSID as the data
being read. If the data type is varying length, the host variable can be declared longer than the actual
data. For all other data types, the length must match exactly.
NAME, DB2_SYSTEM_COLUMN_NAME, and DB2_LABEL can be used to get name-related values for
the result column. See GET DESCRIPTOR for more information about the items returned for a GET
DESCRIPTOR statement and for the definition of the TYPE values
Parameter markers:
A parameter marker is a question mark (?) that appears in a dynamic statement string. The question mark
can appear where a host variable might appear if the statement string were a static SQL statement.
In the example used, the SELECT statement that was dynamically run had a constant value in the
WHERE clause:
If you want to run the same SELECT statement several times, using different values for LASTNAME, you
can use an SQL statement that looks like this:
408

WHERE LASTNAME = ?
When using parameter markers, your application does not need to set the data types and values for the
parameters until run time. By specifying a descriptor on the OPEN statement, you can substitute the
values for the parameter markers in the SELECT statement.
To code such a program, you need to use the OPEN statement with a descriptor clause. This SQL
statement is used to not only open a cursor, but to replace each parameter marker with the value of the
corresponding descriptor entry. The descriptor name that you specify with this statement must identify a
descriptor that contains a valid definition of the values. This descriptor is not used to return information
about data items that are part of a SELECT list. It provides information about values that are used to
replace parameter markers in the SELECT statement. It gets this information from the application, which
must be designed to place appropriate values into the fields of the descriptor. The descriptor is then
ready to be used by SQL for replacing parameter markers with the actual values.
When you use an SQLDA for input to the OPEN statement with the USING DESCRIPTOR clause, not all
of its fields need to be filled in. Specifically, SQLDAID, SQLRES, and SQLNAME can be left blank
(SQLNAME can be set if a specific CCSID is needed.) Therefore, when you use this method for replacing
parameter markers with values, you need to determine:
v How many parameter markers there are
v The data types and attributes of these parameters markers (SQLTYPE, SQLLEN, and SQLNAME)
v Whether an indicator variable is needed
In addition, if the routine is to handle both SELECT and non-SELECT statements, you might want to
determine what category of statement it is.
If your application uses parameter markers, your program has to perform the following steps. This can
be done using either an SQLDA or an allocated descriptor.
1. Read a statement into the DSTRING varying-length character string host variable.
2. Determine the number of parameter markers.
3. Allocate an SQLDA of that size or use ALLOCATE DESCRIPTOR to allocate a descriptor with that
number of entries. This is not applicable in REXX.
4. For an SQLDA, set SQLN and SQLD to the number of parameter markers. SQLN is not applicable in
REXX. For an allocated descriptor, use SET DESCRIPTOR to set the COUNT entry to the number of
parameter markers.
5. For an SQLDA, set SQLDABC equal to SQLN*LENGTH(SQLVAR) + 16. This is not applicable in
REXX.
6. For each parameter marker:
a. Determine the data types, lengths, and indicators.
b. For an SQLDA, set SQLTYPE and SQLLEN for each parameter marker. For an allocated descriptor,
use SET DESCRIPTOR to set the entries for TYPE, LENGTH, PRECISION, and SCALE for each
parameter marker.
c. For an SQLDA, allocate storage to hold the input values.
d. For an SQLDA, set these values in storage.
e. For an SQLDA, set SQLDATA and SQLIND (if applicable) for each parameter marker. For an
allocated descriptor, use SET DESCRIPTOR to set entries for DATA and INDICATOR (if
applicable) for each parameter marker.
f. If character variables are used and they have a CCSID other than the job default CCSID, or graphic
variables are used and they have a CCSID other than the associated DBCS CCSID for the job
CCSID,
SQL programming
409
v For an SQLDA, set SQLNAME (SQLCCSID in REXX) accordingly.

v For an allocated SQL descriptor, use SET DESCRIPTOR to set the DB2_CCSID value.
g. Issue the OPEN statement with a USING DESCRIPTOR clause (for an SQLDA) or USING SQL
DESCRIPTOR clause (for an allocated descriptor) to open your cursor and substitute values for
each of the parameter markers.
The statement can then be processed normally.
Related reference:
Example: A SELECT statement for allocating storage for SQLDA on page 402
Example: A SELECT statement using an allocated SQL descriptor on page 406
to the next. This statement can be read from a display, passed from another application, or built
Using interactive SQL

A programmer, using interactive SQL, can insert rows into a table and test the SQL statements before
running them in an application program. A database administrator can use interactive SQL to grant or
revoke privileges, create or drop schemas, tables, or views, or select information from system catalog
tables.
After an interactive SQL statement is run, a completion message or an error message is displayed. In
addition, status messages are normally displayed during long-running statements.
You can see help about a message by positioning the cursor on the message and pressing F1 (Help).
The basic functions supplied by interactive SQL are:
v The statement entry function allows you to:
Type in an interactive SQL statement and run it.
Retrieve and edit statements.

Prompt for SQL statements.
Page through previous statements and messages.
Call session services.
Start the list selection function.

Exit interactive SQL.
v The prompt function allows you to type either a complete SQL statement or a partial SQL statement,
press F4 (Prompt), and then be prompted for the syntax of the statement. It also allows you to press F4
to get a menu of supported SQL statements. From this menu, you can select a statement and be
prompted for the syntax of the statement.
v The list selection function allows you to select from lists of your authorized relational databases,
schemas, tables, views, columns, constraints, or SQL packages.
The selections you make from the lists can be inserted into the SQL statement at the cursor position.
v The session services function allows you to:
Change session attributes.
Print the current session.
410
Remove all entries from the current session.

Save the session in a source file.
Related concepts:
Dynamic SQL applications on page 395
Dynamic SQL allows an application to define and run SQL statements at program run time. An
application that uses dynamic SQL either accepts an SQL statement as input or builds an SQL statement
in the form of a character string. The application does not need to know the type of the SQL statement.
Related reference:
Processing non-SELECT statements on page 396
Before building a dynamic SQL non-SELECT statement, you need to verify that this SQL statement is
allowed to be run dynamically.
Starting interactive SQL

To start using interactive SQL, enter STRSQL from an IBM i command line.
The Enter SQL Statements display appears. This is the main interactive SQL display. From this display,
you can enter SQL statements and use:
v F4=prompt
v F13=Session services
v F16=Select collections
v F17=Select tables
v F18=Select columns
Enter SQL Statements
Type SQL statement, press Enter.
Current connection is to relational database rdjacque.
===>_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
Bottom
F3=Exit
F4=Prompt
F12=Cancel
F6=Insert line
F13=Services
F9=Retrieve
F10=Copy line
F24=More keys
Press F24=More keys to view the remaining function keys.

_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
Bottom
F14=Delete line
F15=Split line
F17=Select tables
(files)
F16=Select collections (libraries)

F18=Select columns
F24=More keys
(fields)
SQL programming
411
Note: If you are using the system naming convention, the names in parentheses appear instead of the
names shown above.
An interactive session consists of:
v Parameter values you specified for the STRSQL command.
v SQL statements you entered in the session along with corresponding messages that follow each SQL
statement
v Values of any parameters you changed using the session services function
v List selections you have made
Interactive SQL supplies a unique session-ID consisting of your user ID and the current workstation ID.
This session-ID concept allows multiple users with the same user ID to use interactive SQL from more
than one workstation at the same time. Also, more than one interactive SQL session can be run from the
same workstation at the same time from the same user ID.
If an SQL session exists and is being re-entered, any parameters specified on the STRSQL command are
ignored. The parameters from the existing SQL session are used.
Related reference:
Start SQL Interactive Session (STRSQL) command
Using the statement entry function

The statement entry function is the function that you first enter when selecting interactive SQL. You
return to the statement entry function after processing each interactive SQL statement.
In the statement entry function, you type or prompt for the entire SQL statement and then submit it for
processing by pressing the Enter key.
The statement you type on the command line can be one or more lines long. You can type bracketed
comments (/* */) in interactive SQL. However, you should not use simple comments (that is, comments
starting with --) in interactive SQL because these comments then include the remainder of the SQL
statement within the comment. When the statement has been processed, the statement and the resulting
message are moved upward on the display. You can then enter another statement.
If a statement is recognized by SQL but contains a syntax error, the statement and the resulting text
message (syntax error) are moved upward on the display. In the input area, a copy of the statement is
shown with the cursor positioned at the syntax error. You can place the cursor on the message and press
F1=Help for more information about the error.
You can page through previous statements, commands, and messages. If you press F9=Retrieve with your
cursor on the statement entry line, your previous statement is copied to the input area. Pressing F9 again
causes it to scroll back one more statement and copy that to the input area. Continuing to press F9 allows
you to scroll back through your previous statements until you find the one that you want. If you need
more room to type an SQL statement, page down on the display.
Prompting
The prompt function helps you provide the necessary information for the syntax of the statement that
you want to use. The prompt function can be used in any of these statement processing modes: *RUN,
*VLD, and *SYN. Prompting is not available for all SQL statements and is not complete for many SQL
statements. When prompting a statement using a period (.) for qualifying names in *SYS naming mode,
the period will be changed to a slash (/). The GRANT and REVOKE statements do not support
prompting when using the period in *SYS naming.
You have two options when using the prompter:
v Type the verb of the statement before pressing F4=Prompt.
412
The statement is parsed and the clauses that are completed are filled in on the prompt displays.
If you type SELECT and press F4=Prompt, the following display appears:
Specify SELECT Statement
Type SELECT statement information.
FROM tables . . . . .
SELECT columns . . .
WHERE conditions . .
GROUP BY columns . .
HAVING conditions . .
ORDER BY columns . .
FOR UPDATE OF columns
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Press F4 for a list.
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
Bottom
Type choices, press Enter.

DISTINCT rows in result table . . . . . . . . .
UNION with another SELECT . . . . . . . . . . .
Specify additional options . . . . . . . . . . .
F3=Exit
F10=Copy line
F4=Prompt
F12=Cancel
N
N
N
Y=Yes, N=No
Y=Yes, N=No
Y=Yes, N=No
F5=Refresh F6=Insert line

F9=Specify subquery
F14=Delete line F15=Split line F24=More keys
v Press F4=Prompt before typing anything on the Enter SQL Statements display. You are shown a list of
statements. The list of statements varies and depends on the current interactive SQL statement
processing mode. For syntax check mode with a language other than *NONE, the list includes all SQL
statements. For run and validate modes, only statements that can be run in interactive SQL are shown.
You can select the number of the statement you want to use. The system prompts you for the
statement you selected.
If you press F4=Prompt without typing anything, the following display appears:
Select SQL Statement
Select one of the following:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
ALTER TABLE
CALL
COMMENT ON
COMMIT
CONNECT
CREATE ALIAS
CREATE COLLECTION
CREATE INDEX
CREATE PROCEDURE
CREATE TABLE
CREATE VIEW
DELETE
DISCONNECT
DROP ALIAS
More...
Selection
__
F3=Exit
F12=Cancel
If you press F21=Display Statement on a prompt display, the prompter displays the formatted SQL
statement as it was filled in to that point.
When Enter is pressed within prompting, the statement that was built through the prompt screens is
inserted into the session. If the statement processing mode is *RUN, the statement is run. The prompter
remains in control if an error is encountered.
SQL programming
413
Syntax checking:
The syntax of the SQL statement is checked when it enters the prompter.
The prompter does not accept a syntactically incorrect statement. You must correct the syntax or remove
the incorrect part of the statement or prompting will not be allowed.
Statement processing mode:
The statement processing mode can be selected on the Change Session Attributes display.
In *RUN (run) or *VLD (validate) mode, only statements that are allowed to run in interactive SQL can
be prompted. In *SYN (syntax check) mode, all SQL statements are allowed. The statement is not actually
run in *SYN or *VLD modes; only the syntax and existence of objects are checked.
Subqueries:
Subqueries can be selected on any display that has a WHERE or HAVING clause.
To see the subquery display, press F9=Specify subquery when the cursor is on a WHERE or HAVING
input line. A display appears that allows you to type in subselect information. If the cursor is within the
parentheses of the subquery when F9 is pressed, the subquery information is filled in on the next display.
If the cursor is outside the parentheses of the subquery, the next display is blank.
CREATE TABLE prompting:
You can enter column definitions individually when you are prompted for a CREATE TABLE statement.
Place your cursor in the column definition section of the display, and press F4=Prompt. A display that
provides room for entering all the information for one column definition is shown.
To enter a column name longer than 18 characters, press F20=Display entire name. A window with
enough space for a 30 character name will be displayed.
The editing keys, F6=Insert line, F10=Copy line, and F14=Delete line, can be used to add and delete
entries in the column definition list.
Entering DBCS data:
The rules for processing double-byte character set (DBCS) data across multiple lines are the same on the
Enter SQL Statements display and in the SQL prompter.
Each line must contain the same number of shift-in and shift-out characters. When processing a DBCS
data string that requires more than one line for entering, the extra shift-in and shift-out characters are
removed. If the last column on a line contains a shift-in and the first column of the next line contains a
shift-out, the shift-in and shift-out characters are removed by the prompter when the two lines are
assembled. If the last two columns of a line contain a shift-in followed by a single-byte blank and the first
column of the next line contains a shift-out, the shift-in, blank, shift-out sequence is removed when the
two lines are assembled. This removal allows DBCS information to be read as one continuous character
string.
As an example, suppose the following WHERE condition were entered. The shift characters are shown
here at the beginning and end of the string sections on each of the two lines.
414
Specify SELECT Statement

Type SELECT statement information.
FROM tables . . . . . . . .
SELECT columns . . . . . .
WHERE conditions . . . . .
GROUP BY columns . .
HAVING conditions . .
ORDER BY columns . .
FOR UPDATE OF columns
.
.
.
.
.
.
.
.
.
.
.
.
Press F4 for a list.
TABLE1_______________________________________
*____________________________________________
COL1 = <AABBCCDDEEFFGGHHIIJJKKLLMMNNOOPPQQ>
<RRSS>______________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
When Enter is pressed, the character string is put together, removing the extra shift characters. The
statement looks like this on the Enter SQL Statements display:
SELECT * FROM TABLE1 WHERE COL1 = <AABBCCDDEEFFGGHHIIJJKKLLMMNNOOPPQQRRSS>
Using the list selection function

You can access the list selection function by pressing F4 (Prompt) on certain prompt displays. To access
the function on the Enter SQL Statements display, press F16 (Select collections), F17 (Select tables), or F18
(Select columns).
After pressing the function key, you are given a list of authorized relational databases, schemas, tables,
views, aliases, columns, constraints, procedures, parameters, or packages from which to choose. If you
request a list of tables, but you have not previously selected a schema, you are asked to select a schema
first.
On a list, you can select one or more items, numerically specifying the order in which you want them to
appear in the statement. When the list function is exited, the selections you made are inserted at the
position of the cursor on the display you came from.
Always select the list you are primarily interested in. For example, if you want a list of columns, but you
believe that the columns you want are in a table not currently selected, press F18. Then, from the column
list, press F17 to change the table. If the table list were selected first, the table name will be inserted into
your statement. You do not have a choice for selecting columns.
You can request a list at any time while typing an SQL statement on the Enter SQL Statements display.
The selections you make from the lists are inserted on the Enter SQL Statements display. They are
inserted where the cursor is located in the numeric order that you specified on the list display. Although
the selected list information is added for you, you must type the keywords for the statement.
The list function tries to provide qualifications that are necessary for the selected columns, tables, and
SQL packages. However, sometimes the list function cannot determine the intent of the SQL statement.
You need to review the SQL statement and verify that the selected columns, tables, and SQL packages are
properly qualified.
Related reference:
Starting interactive SQL on page 411
To start using interactive SQL, enter STRSQL from an IBM i command line.
Example: Using the list selection function:
This example shows how to use the list selection function to build a SELECT statement.
Assume you have:
v Just entered interactive SQL by typing STRSQL on an IBM i command line.
v Made no list selections or entries.
SQL programming
415
v Selected *SQL for the naming convention.

Note: The example shows lists that are not on your server. They are used as an example only.
Begin using SQL statements:
1. Type SELECT on the first statement entry line.
2. Type FROM on the second statement entry line.
3. Leave the cursor positioned after FROM.
===> SELECT
FROM _
4. Press F17=Select tables to obtain a list of tables, because you want the table name to follow FROM.
Instead of a list of tables appearing as you expected, a list of collections appears (the Select and
Sequence collections display). You have just entered the SQL session and have not selected a schema
to work with.
5. Type a 1 in the Seq column next to YOURCOLL2 schema.
Select and Sequence Collections
Type sequence numbers (1-999) to select collection, press Enter.
Seq
1
Collection
YOURCOLL1
YOURCOLL2
YOURCOLL3
YOURCOLL4
Type
SYS
SYS
SYS
SYS
Text
Company benefits
Employee personal data
Job classifications/requirements
Company insurances
6. Press Enter.
The Select and Sequence Tables display appears, showing the tables existing in the YOURCOLL2
schema.
7. Type a 1 in the Seq column next to PEOPLE table.
Select and Sequence Tables
Type sequence numbers (1-999) to select tables, press Enter.
Seq Table
EMPLCO
1
PEOPLE
EMPLEXP
EMPLEVL
EMPLBEN
EMPLMED
EMPLINVST
Collection
YOURCOLL2
YOURCOLL2
YOURCOLL2
YOURCOLL2
YOURCOLL2
YOURCOLL2
YOURCOLL2
Type
TAB
TAB
TAB
TAB
TAB
TAB
TAB
Text
Employee
Employee
Employee
Employee
Employee
Employee
Employee
company data
personal data
experience
evaluation reports
benefits record
medical record
investments record
8. Press Enter.
The Enter SQL Statements display appears again with the table name, YOURCOLL2.PEOPLE, inserted
after FROM. The table name is qualified by the schema name in the *SQL naming convention.
416

===> SELECT
FROM YOURCOLL2.PEOPLE _
9. Position the cursor after SELECT.

10. Press F18=Select columns to obtain a list of columns, because you want the column name to follow
SELECT.
The Select and Sequence Columns display appears, showing the columns in the PEOPLE table.
11. Type a 2 in the Seq column next to the NAME column.
12. Type a 1 in the Seq column next to the SOCSEC column.
Select and Sequence Columns
Type sequence numbers (1-999) to select columns, press Enter.
Seq
2
1
Column
NAME
EMPLNO
SOCSEC
STRADDR
CITY
ZIP
PHONE
Table
PEOPLE
PEOPLE
PEOPLE
PEOPLE
PEOPLE
PEOPLE
PEOPLE
Type
CHARACTER
CHARACTER
CHARACTER
CHARACTER
CHARACTER
CHARACTER
CHARACTER
Length
6
30
11
30
20
9
20
Scale
13. Press Enter.

The Enter SQL Statements display appears again with SOCSEC, NAME appearing after SELECT.
===> SELECT SOCSEC, NAME
FROM YOURCOLL2.PEOPLE
14. Press Enter.

The statement you created is now run.
Once you have used the list function, the values you selected remain in effect until you change them or
until you change the list of schemas on the Change Session Attributes display.
Session services description

You can change session attributes from the Session Services display. You can also print, clear, or save the
session to a source file.
To access the Session Services display, press F13 (Services) on the Enter SQL Statements display.
Option 1 (Change session attributes) displays the Change Session Attributes display, which allows you to
select the current values that are in effect for your interactive SQL session. The options shown on this
display change based on the statement processing option selected.
The following session attributes can be changed:
SQL programming
417
v
v
v
v
v
v
v
v
v
v
v
v
Commitment control attributes.

The statement processing control.
The SELECT output device.
The list of schemas.
The list type to select either all your system and SQL objects, or only your SQL objects.
The data refresh option when displaying data.
The allow copy data option.
The naming option.
The programming language.
The date format.
The time format.
The date separator.
v
v
v
v
The
The
The
The
time separator.
decimal point representation.
SQL string delimiter.
sort sequence.
v The language identifier.

v The SQL rules.
v The CONNECT password option.
Option 2 (Print current session) accesses the Change Printer display, which lets you print the current
session immediately and then continue working. You are prompted for printer information. All the SQL
statements you entered and all the messages displayed are printed just as they appear on the Enter SQL
Statements display.
Option 3 (Remove all entries from current session) lets you remove all the SQL statements and messages
from the Enter SQL Statements display and the session history. You are prompted to ensure that you
really want to delete the information.
Option 4 (Save session in source file) accesses the Change Source File display, which lets you save the
session in a source file. You are prompted for the source file name. This function lets you embed the
source file into a host language program by using the source entry utility (SEU).
Note: Option 4 allows you to embed prototyped SQL statements in a high-level language (HLL) program
that uses SQL. The source file created by option 4 may be edited and used as the input source file
for the Run SQL Statements (RUNSQLSTM) command.
Exiting interactive SQL

To exit the interactive SQL environment, press F3 (Exit) on the Enter SQL Statements display. Several
options are available for exiting.
v Save and exit session. Leave interactive SQL. Your current session will be saved and used the next time
you start interactive SQL.
v Exit without saving session. Leave interactive SQL without saving your session.
v Resume session. Remain in interactive SQL and return to the Enter SQL Statements display. The current
session parameters remain in effect.
v Save session in source file. Save the current session in a source file. The Change Source File display is
shown to allow you to select where to save the session. You cannot recover and work with this session
again in interactive SQL.
Notes:
418
1. Option 4 allows you to embed prototype SQL statements in a high-level language (HLL)
program that uses SQL. Use the source entry utility (SEU) to copy the statements into your
program. The source file can also be edited and used as the input source file for the Run SQL
Statements (RUNSQLSTM) command.
2. If rows have been changed and locks are currently being held for this unit of work and you
attempt to exit interactive SQL, a warning message is displayed.
Using an existing SQL session

If you saved only one interactive SQL session by selecting option 1 (Save and exit session) on the Exit
Interactive SQL display, you can resume the session at any workstation.
However, if you use option 1 to save two or more sessions on different workstations, interactive SQL will
first attempt to resume a session that matches your workstation. If no matching sessions are available,
then interactive SQL will increase the scope of the search to include all sessions that belong to your user
ID. If no sessions for your user ID are available, the system will create a new session for your user ID
and current workstation.
For example, you saved a session on workstation 1 and saved another session on workstation 2 and you
are currently working at workstation 1. Interactive SQL will first attempt to resume the session saved for
workstation 1. If that session is currently in use, interactive SQL will then attempt to resume the session
that was saved for workstation 2. If that session is also in use, then the system will create a second
session for workstation 1.
However, suppose you are working at workstation 3 and want to use the ISQL session associated with
workstation 2. You then may need to first delete the session from workstation 1 by using Option 2 (Exit
without saving session) on the Exit Interactive SQL display.
Recovering an SQL session

If the previous SQL session ended abnormally, interactive SQL presents the Recover SQL Session display
at the start of the next session when you enter the Start SQL Interactive Session (STRSQL) command.
From this display, you can choose to do either of the following two things.
v Recover the old session by selecting option 1 (Attempt to resume existing SQL session).
v Delete the old session and start a new session by selecting option 2 (Delete existing SQL session and
start a new session).
If you choose to delete the old session and continue with the new session, the parameters you specified
when you entered STRSQL are used. If you choose to recover the old session, or are entering a previously
saved session, the parameters you specified when you entered STRSQL are ignored and the parameters
from the old session are used. A message is returned to indicate which parameters were changed from
the specified value to the old session value.
Accessing remote databases with interactive SQL

In interactive SQL, you can communicate with a remote relational database by using the SQL CONNECT
statement. Interactive SQL uses the CONNECT (Type 2) semantics (distributed unit of work) for
CONNECT statements.
Interactive SQL establishes an implicit connection to the local relational database when starting an SQL
session. When the CONNECT statement is completed, a message shows the relational database
connection that was established. If interactive SQL is starting a new session and COMMIT(*NONE) was
not specified, or if interactive SQL is restoring a saved session and the commitment control level saved
with the session was not *NONE, the connection will be registered with commitment control. This
implicit connection and possible commitment control registration might influence subsequent connections
to remote databases. It is suggested that you perform one of the following tasks before connecting to the
remote database:
SQL programming
419
v When you are connecting to an application server that does not support distributed unit of work, issue
a RELEASE ALL statement followed by a COMMIT statement to end previous connections, including
the implicit connection to the local database.
v When you are connecting to an application server other than DB2 for i, issue a RELEASE ALL
statement followed by a COMMIT statement to end previous connections, including the implicit
connection to the local database, and change the commitment control level to at least *CHG.
When you are connecting to an application server other than DB2 for i, some session attributes are
changed to attributes that are supported by that application server. The following table shows the
attributes that change.
Table 99. Values table
Session attribute
Original value
New value
*YMD
*ISO
*DMY
*EUR
*MDY
*USA
*JUL
*USA
*HMS with a : separator *HMS with

any other separator
*JIS
Date format
Time format
*EUR
Commitment control
*CS Repeatable Read

*CHG,
*NONE
*ALL
Naming convention
*SYS
*SQL
Allow copy data
*NO, *YES
*OPTIMIZE
Data refresh
*ALWAYS
*FORWARD
Decimal point
*SYSVAL
*PERIOD
Sort sequence
Any value other than *HEX
*HEX
Note: When you are connected to a DB2 for Linux, UNIX, and Windows or DB2 for z/OS application
server, the date and time formats specified must be the same.
After the connection is completed, a message is sent stating that the session attributes have been changed.
The changed session attributes can be displayed by using the session services display. While interactive
SQL is running, no other connection can be established for the default activation group.
When connected to a remote system with interactive SQL, a statement processing mode of syntax-only
checks the syntax of the statement against the syntax supported by the local system instead of the remote
system. Similarly, the SQL prompter and list support use the statement syntax and naming conventions
supported by the local system. The statement is run, however, on the remote system. Because of
differences in the level of SQL support between the two systems, syntax errors may be found in the
statement on the remote system at run time.
420
Lists of schemas and tables are available when you are connected to the local relational database. Lists of
columns are available only when you are connected to a relational database manager that supports the
DESCRIBE TABLE statement.
When you exit interactive SQL with connections that have pending changes or connections that use
protected conversations, the connections remain. If you do not perform additional work over the
connections, the connections are ended during the next COMMIT or ROLLBACK operation. You can also
end the connections by doing a RELEASE ALL and a COMMIT before exiting interactive SQL.
Using interactive SQL for remote access to application servers other than DB2 for i might require some
setup.
Note: In the output of a communications trace, there may be a reference to a 'CREATE TABLE XXX'
statement. This is used to determine package existence; it is part of normal processing, and can be
ignored.
Related concepts:
Related reference:
Determining the connection type on page 440
When a remote SQL connection is established, it uses either an unprotected or a protected network
connection.
Using the SQL statement processor

The SQL statement processor allows SQL statements to be run from a source member or a source stream
file. The statements in the source can be run repeatedly or changed without compiling the source. This
makes the setup of a database environment easier.
The SQL statement processor is available through the Run SQL Statements (RUNSQLSTM) command.
The following statements can be used with the SQL statement processor:
v ALTER FUNCTION
v
v
v
v
ALTER PROCEDURE
ALTER SEQUENCE
ALTER TABLE
CALL
v
v
v
v
v
v
v
v
COMMENT
COMMIT
CREATE ALIAS
CREATE FUNCTION
CREATE INDEX
CREATE PROCEDURE
CREATE SCHEMA
CREATE SEQUENCE
v
v
v
| v
v
v
CREATE TABLE
CREATE TRIGGER
CREATE TYPE
CREATE VARIABLE
CREATE VIEW
SQL programming
421
v
v
v
v
v
v
v
v
v
v
v
v
DELETE
DROP
GRANT
INSERT
LABEL
LOCK TABLE
MERGE
REFRESH TABLE
RELEASE SAVEPOINT
RENAME
REVOKE
ROLLBACK
v
v
v
v
SAVEPOINT
SET CURRENT DEGREE
v SET ENCRYPTION PASSWORD

v SET PATH
v SET SCHEMA
v SET TRANSACTION
v UPDATE
In the source, SQL statements do not begin with EXEC SQL. Each statement ends with a semicolon. For a
source member, the default right margin is 80. If the record length of the source member is longer than
80, only the first 80 characters are read. You can change the right margin to some other value by using
the MARGINS parameter on the RUNSQLSTM command. For a source stream file, the entire file is read;
no margin is used.
Comments in the source can be either line comments or block comments. Line comments begin with a
double hyphen (--) and end at the end of the line. Block comments start with /* and can continue across
many lines until the corresponding */ is reached. Block comments can be nested.
|
|
|
|
SQL statements, CL commands, and comments are allowed in the source file. A CL command must be
prefixed by 'CL:'. For example:
CL: ADDLIBLE MYLIB;
INSERT INTO T1 VALUES(A, 17);
| The output listing containing the resulting messages for the SQL statements and CL commands is sent to
| a print file. The default print file is QSYSPRT.
| The OPTION parameter lets you choose to get an output listing or to have errors written to the joblog.
| There is also an option to generate a listing only when errors are encountered during processing.
To perform syntax checking only on all statements in the source, specify the PROCESS(*SYN) parameter
on the RUNSQLSTM command. To see more details for error messages in the listing, specify the
SECLVLTXT(*YES) parameter.
Related reference:
Run SQL Statement (RUNSQLSTM) command
422
Execution of statements after errors occur

If a statement returns an error with a severity higher than the value specified for the error level
(ERRLVL) parameter of the Run SQL Statements (RUNSQLSTM) command, the statement fails.
The rest of the statements in the source are parsed to check for syntax errors, and will not be run. Most
SQL errors have a severity of 30. If you want to continue processing after an SQL statement fails, set the
ERRLVL parameter of the RUNSQLSTM command to 30 or higher. DROP statements issue a severity
level 20 error if the object is not found to be dropped. Setting the ERRLVL parameter to have a value of
20 allows you to ignore these errors for DROP statements while not allowing processing to continue for
other higher severity errors.
Commitment control in the SQL statement processor

A commitment-control level is specified on the Run SQL Statements (RUNSQLSTM) command.
If a commitment-control level other than *NONE is specified, the SQL statements are run under
commitment control. If all of the statements successfully runs, a COMMIT is done at the completion of
the SQL statement processor. Otherwise, a ROLLBACK is done. A statement is considered successful if its
return code severity is less than or equal to the value specified on the ERRLVL parameter of the
RUNSQLSTM command.
The SET TRANSACTION statement can be used within the source member to override the level of
commitment control specified on the RUNSQLSTM command.
Note: The job must be at a unit of work boundary to use the SQL statement processor with commitment
control.
Source listing for the SQL statement processor

This example shows an output source listing for the SQL statement processor.
Note: By using the code examples, you agree to the terms of Code license and disclaimer information
on page 491
SQL programming
423
xxxxSS1 VxRxMx yymmdd

Run SQL Statements
Source file...............CORPDATA/SRC
Member....................SCHEMA
Commit....................*NONE
Naming....................*SYS
Generation level..........10
Date format...............*JOB
Date separator............*JOB
Right margin..............80
Time format...............*HMS
Time separator ...........*JOB
Default collection........*NONE
IBM SQL flagging..........*NOFLAG
ANS flagging..............*NONE
Decimal point.............*JOB
Sort sequence.............*JOB
Language ID...............*JOB
Printer file..............*LIBL/QSYSPRT
Source file CCSID.........65535
Job CCSID.................37
Statement processing......*RUN
Allow copy of data........*OPTIMIZE
Allow blocking............*ALLREAD
SQL rules.................*DB2
Decimal result options:
Maximum precision.......31
Maximum scale...........31
Minimum divide scale....0
Source member changed on 11/01/07 11:54:10
SCHEMA
02/15/08 15:35:18
Page
Figure 1. QSYSPRT listing for SQL statement processor

Run SQL Statements
SCHEMA
02/15/08 15:35:18 Page 2
Record *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+... 8 SEQNBR Last change
1
2
DROP SCHEMA DEPT;
3
DROP SCHEMA MANAGER;
4
5
CREATE SCHEMA DEPT
6
CREATE TABLE EMP (EMPNAME CHAR(50), EMPNBR INT)
7
-- EMP will be created in schema DEPT
8
CREATE INDEX EMPIND ON EMP(EMPNBR)
9
-- EMPIND will be created in DEPT
10
GRANT SELECT ON EMP TO PUBLIC; -- grant authority
11
12
INSERT INTO DEPT/EMP VALUES(JOHN SMITH, 1234);
13
/* table must be qualified since no
14
longer in the schema */
15
16
CREATE SCHEMA AUTHORIZATION MANAGER
17
-- this schema will use MANAGERs
18
-- user profile
19
CREATE TABLE EMP_SALARY (EMPNBR INT, SALARY DECIMAL(7,2),
20
LEVEL CHAR(10))
21
CREATE VIEW LEVEL AS SELECT EMPNBR, LEVEL
22
FROM EMP_SALARY
23
CREATE INDEX SALARYIND ON EMP_SALARY(EMPNBR,SALARY)
24
25
GRANT ALL ON LEVEL TO JONES GRANT SELECT ON EMP_SALARY TO CLERK
26
-- Two statements can be on the same line
* * * * * E N D O F S O U R C E * * * * *
Figure 2. QSYSPRT listing for SQL statement processor (continued)
424

Run SQL Statements
SCHEMA
02/15/08 15:35:18 Page 3
Record *...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+... 8 SEQNBR Last change
MSG ID SEV RECORD TEXT
SQL7953 0
1 Position 1 Drop of DEPT in QSYS complete.
SQL7953 0
3 Position 3 Drop of MANAGER in QSYS complete.
SQL7952 0
5 Position 3 Schema DEPT created.
SQL7950 0
6 Position 8 Table EMP created in DEPT.
SQL7954 0
8 Position 8 Index EMPIND created in DEPT on table EMP in
DEPT.
SQL7966 0
10 Position 8 GRANT of authority to EMP in DEPT completed.
SQL7956 0
10 Position 40 1 rows inserted in EMP in DEPT.
SQL7952 0
13 Position 28 Schema MANAGER created.
SQL7950 0
19 Position 9 Table EMP_SALARY created in schema
MANAGER.
SQL7951 0
21 Position 9 View LEVEL created in MANAGER.
SQL7954 0
23 Position 9 Index SALARYIND created in MANAGER on table
EMP_SALARY in MANAGER.
SQL7966 0
25 Position 9 GRANT of authority to LEVEL in MANAGER
completed.
SQL7966 0
25 Position 37 GRANT of authority to EMP_SALARY in MANAGER
completed.
Message Summary
Total
Info
Warning
Error
Severe
Terminal
13
13
0
0
0
0
00 level severity errors found in source
* * * * * E N D O F L I S T I N G * * * * *
Figure 3. QSYSPRT listing for SQL statement processor (continued)
Using the RUNSQL CL command
|
|
The RUNSQL CL command allows an SQL statement to be run from within a CL program without
needing a source file.
|
|
The following statements can be used by RUNSQL:

v ALTER FUNCTION
|
|
|
v ALTER PROCEDURE
v ALTER SEQUENCE
v ALTER TABLE
|
|
|
|
|
|
|
|
|
v
v
v
v
v
v
v
v
v
CALL
COMMENT
COMMIT
CREATE ALIAS
CREATE FUNCTION
CREATE INDEX
CREATE PROCEDURE
CREATE SCHEMA
CREATE SEQUENCE
|
|
|
|
|
|
|
v
v
v
v
v
v
v
CREATE TABLE
CREATE TRIGGER
CREATE TYPE
CREATE VARIABLE
CREATE VIEW
DELETE
|
|
v DROP
v GRANT
SQL programming
425
|
|
|
|
|
|
|
|
|
|
|
|
v
v
v
v
v
v
v
v
v
v
v
v
INSERT
LABEL
MERGE
REFRESH TABLE
RELEASE SAVEPOINT
RENAME
REVOKE
ROLLBACK
SAVEPOINT
SET CURRENT DEGREE
|
|
|
|
v
v
v
v
SET
SET
SET
SET
ENCRYPTION PASSWORD
PATH
SCHEMA
TRANSACTION
| v UPDATE
| The statement string can be up to 5000 characters long. It must not end with a semicolon.
|
|
|
|
Comments are allowed in the statement string. A line comment begins with a double hyphen (--) and
ends at the end of the line (a carriage return and/or line feed) or at the end of the string. Block
comments start with /* and continue until the corresponding */ is reached. Block comments can be
nested.
| If any file is opened by RUNSQL, it is closed before control is returned to the caller. If commitment
| control is active, it is up to the users application to perform the commit or rollback.
| The command runs in the invokers activation group. If RUNSQL is included in a compiled CL program,
| the activation group of the program is used.
|
|
|
|
No output listing is generated. If a failure occurs, the SQL message is sent as an escape message to the
caller. For a complex SQL statement that returns a syntax error, you can use the database monitor to help
find the cause of the error. Start a database monitor, run the RUNSQL command, and analyze the
database monitor using System i Navigator.
| Run an INSERT statement from CL:

| RUNSQL SQL(INSERT INTO prodLib/work_table VALUES(1, CURRENT TIMESTAMP))
| In a CL program, you could use the Receive File (RCVF) command to read the results of the table
| generated for this query:
| RUNSQL SQL(CREATE TABLE qtemp.worktable AS
|
(SELECT * FROM qsys2.systables WHERE table_schema = MYSCHEMA) WITH DATA)
|
COMMIT(*NONE) NAMING(*SQL)
| Create a CL program that constructs and runs an SQL statement using an input parameter as part of the
| statement:
| RUNSQL1: PGM PARM(&LIB)
|
DCL &LIB TYPE(*CHAR) LEN(10)
|
DCL &SQLSTMT TYPE(*CHAR) LEN(1000)
|
CHGVAR VAR(&SQLSTMT) +
426
|
|
|
|
VALUE(DELETE FROM qtemp.worktable1 +

WHERE table_schema = || &LIB || )
RUNSQL SQL(&SQLSTMT) COMMIT(*NONE) NAMING(*SQL)
RUNSQL1: ENDPGM
Distributed relational database function and SQL

computer systems.
These relational databases can be of the same type (for example, the DB2 for i database) or of different
types (DB2 for z/OS, DB2 for VSE and VM, or non-IBM database management systems that support
Distributed Relational Database Architecture (DRDA)). Each relational database has a relational database
manager to manage the tables in its environment. The database managers communicate and cooperate
with each other in a way that allows a given database manager access to run SQL statements on a
relational database on another system.
The application requester supports the application side of a connection. The application server is the local
or remote database to which an application requester is connected. DB2 for i provides support for DRDA
to allow an application requester to communicate with application servers. In addition, DB2 for i can call
exit programs to allow access to data on other database management systems that do not support DRDA.
These exit programs are called application requester driver (ARD) programs.
DB2 for i supports the following levels of distributed relational database:
v Remote unit of work (RUW)
A remote unit of work is where the preparation and running of SQL statements occurs at only one
application server during a unit of work. DB2 for i supports RUW over either Advanced
Program-to-Program Communication (APPC) or TCP/IP.
v Distributed unit of work (DUW)
A distributed unit of work is where the preparation and running of SQL statements can occur at multiple
application servers during a unit of work. However, a single SQL statement can only refer to objects
located at a single application server. DB2 for i supports DUW over APPC and DUW over TCP/IP.
Related concepts:
Introduction to DB2 for i Structured Query Language on page 4
Structured Query Language (SQL) is a standardized language for defining and manipulating data in a
relational database. These topics describe the System i implementation of the SQL using the DB2 for i
database and the IBM DB2 Query Manager and SQL Development Kit for i licensed program.
SQL packages on page 13
An SQL package is an object that contains the control structure produced when the SQL statements in an
application program are bound to a remote relational database management system (DBMS).
DB2 for i distributed relational database support

The IBM DB2 Query Manager and SQL Development Kit for i licensed program supports interactive
access to distributed databases.
DB2 Query Manager and SQL Development Kit for IBM i provides distributed relational database
support through the following SQL statements:
v CONNECT
v
v
v
v
SET CONNECTION
DISCONNECT
RELEASE
DROP PACKAGE
SQL programming
427
v GRANT PACKAGE
v REVOKE PACKAGE
Additional support is provided by the development kit through parameters on the SQL precompiler
commands:
v Create SQL ILE C Object (CRTSQLCI) command
v Create SQL ILE C++ Object (CRTSQLCPPI) command
v Create SQL COBOL Program (CRTSQLCBL) command
v Create SQL ILE COBOL Object (CRTSQLCBLI) command
v Create SQL PL/I Program (CRTSQLPLI) command
v Create SQL RPG Program (CRTSQLRPG) command
v Create SQL ILE RPG Object (CRTSQLRPGI) command
Related tasks:
Related reference:
DB2 for i CL command descriptions on page 491
DB2 for i provides these CL commands for SQL.
CONNECT (Type 1)
CONNECT (Type 2)
DISCONNECT
DROP
GRANT (Package Privileges)
REVOKE (Package Privileges)
RELEASE (Connection)
SET CONNECTION
DB2 for i distributed relational database example program

A relational database example program that uses remote unit of work is included with the SQL product.
Several files and members within the QSQL library can help you set up an environment that runs a
distributed DB2 for i example program.
To use these files and members, you need to run the SETUP batch job located in the file
QSQL/QSQSAMP. The SETUP batch job allows you to customize the example to do the following:
v Create the QSQSAMP library at the local and remote locations.
v Set up relational database directory entries at the local and remote locations.
v Create application panels at the local location.
v Precompile, compile, and run programs to create distributed example application schemas, tables,
indexes, and views.
v Load data into the tables at the local and remote locations.
v Precompile and compile programs.
v Create SQL packages at the remote location for the application programs.
v Precompile, compile, and run the program to update the location column in the department table.
Before running the SETUP, you may need to edit the SETUP member of the QSQL/QSQSAMP file.
Instructions are included in the member as comments. To run the SETUP, specify the following command
on the system command line:
========> SBMDBJOB QSQL/QSQSAMP SETUP
428
Wait for the batch job to complete.

To use the example program, specify the following command on the command line:
========> ADDLIBLE QSQSAMP
To call the first display that allows you to customize the example program, specify the following
command on the command line.
========> CALL QSQ8HC3
The following display opens. From this display, you can customize your database example program.
SAMPLE ORGANIZATION APPLICATION
ACTION...........:
A
D
(ADD)
(DISPLAY)
OBJECT...........:
DE (DEPARTMENT)
DS (DEPT STRUCTURE)
EM (EMPLOYEE)
SEARCH CRITERIA..:
DI (DEPARTMENT ID)
DN (DEPARTMENT NAME)
MI (MANAGER ID)
MN (MANAGER NAME)
EI (EMPLOYEE ID)
EN (EMPLOYEE NAME)
LOCATION.........:
E (ERASE)
U (UPDATE)
(BLANK IMPLIES LOCAL LOCATION)
DATA.............:
Bottom
F3=Exit
SQL package support

The IBM i operating system supports SQL packages. The object type is *SQLPKG.
The SQL package contains the control structures and access plans necessary to process SQL statements on
the application server when running a distributed program. An SQL package can be created when:
v The RDB parameter is specified on the CRTSQLxxx command and the program object is successfully
created. The SQL package will be created on the system specified by the RDB parameter.
If the compile is unsuccessful or the compile only creates the module object, the SQL package will not
be created.
v Using the CRTSQLPKG command. The CRTSQLPKG can be used to create a package when the
package was not created at precompile time or if the package is needed at an RDB other than the one
specified on the precompile command.
The Delete SQL Package (DLTSQLPKG) command allows you to delete an SQL package on the local
system.
An SQL package is not created unless the privileges held by the authorization ID associated with the
creation of the SQL package includes appropriate authority for creating a package on the remote system
(the application server). To run the program, the authorization ID must include EXECUTE privileges on
the SQL package. On the IBM i operating system, the EXECUTE privilege includes system authority of
*OBJOPR and *EXECUTE.
Related reference:
Create SQL Package (CRTSQLPKG) command
SQL programming
429
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 for i that refer to a remote database that is not DB2 for i can use executable
SQL statements supported by the remote database. The precompiler continues 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 returns 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 OS/400 V5R2 or IBM i V5R3, or
later, with the following exception. An application requester that is not running on the IBM i operating
system can issue read-only, insensitive scrollable cursor operations on an IBM i 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.
Related information:
Characteristics of SQL statements
Considerations for creating an SQL package

When you create an SQL package, consider these aspects.
CRTSQLPKG authorization:
When you create an SQL package on the IBM i operating system, the authorization ID used must have
*USE authority to the Create SQL Package (CRTSQLPKG) command.
Creating a package on a database other than DB2 for i:
When you create a program or an SQL package on a database other than DB2 for i, and try to use SQL
statements that are unique to the other database, you must set the GENLVL parameter on the Create SQL
(CRTSQLxxx) commands to 30.
The program will be created unless a message with a severity level of greater than 30 is issued. If a
message is issued with a severity level of greater than 30, the statement is probably not valid for any
relational database. For example, undefined or unusable host variables or constants that are not valid
generate a message severity greater than 30.
The precompiler listing should be checked for unexpected messages when running with a GENLVL value
greater than 10. When you are creating a package for a DB2 product, you must set the GENLVL
parameter to a value less than 20.
If the RDB parameter specifies a database that is not DB2 for i, the following options should not be used
on the CRTSQLxxx command:
v COMMIT(*NONE)
v OPTION(*SYS)
v DATFMT(*MDY)
v
v
v
v
v
v
DATFMT(*DMY)
DATFMT(*JUL)
DATFMT(*YMD)
DATFMT(*JOB)
DYNUSRPRF(*OWNER)
TIMFMT(*HMS) if TIMSEP(*BLANK) or TIMSEP(',') is specified
430
v
v
v
v
SRTSEQ(*JOBRUN)
SRTSEQ(*LANGIDUNQ)
SRTSEQ(*LANGIDSHR)
SRTSEQ(library-name/table-name)
Note: When you connect to a DB2 server, the following additional rules apply:
v The specified date and time formats must be the same format
v A value of *BLANK must be used for the TEXT parameter
v Default schemas (DFTRDBCOL) are not supported
v The CCSID of the source program from which the package is being created must not be 65535; if 65535
is used, an empty package is created.
Target release (TGTRLS) parameter:
When you create the package, the SQL statements are checked to determine which release can support
the function.
This release is set as the restore level of the package. For example, if the package contains a CREATE
TABLE statement which adds a FOREIGN KEY constraint to the table, then the restore level of the
package will be Version 3 Release 1, because FOREIGN KEY constraints were not supported before this
release. TGTRLS message are suppressed when the TGTRLS parameter is *CURRENT.
SQL statement size:
The create SQL package function might not be able to handle an SQL statement of the same size that the
precompiler can process.
While the SQL program is being precompiled, the SQL statement is placed into the associated space of
the program. When this occurs, each token is separated by a blank. In addition, when the RDB parameter
is specified, the host variables of the source statement are replaced with an 'H'. The create SQL package
function passes this statement to the application server, along with a list of the host variables for that
statement. The addition of the blanks between the tokens and the replacement of host variables can cause
the statement to exceed the maximum SQL statement size (SQL0101 reason 5).
Statements that do not require a package:
In some cases, you might try to create an SQL package, but the SQL package is not created and the
program still runs. This situation occurs when the program contains only SQL statements that do not
require an SQL package to run.
For example, a program that contains only the SQL statement DESCRIBE TABLE will generate message
SQL5041 during SQL package creation. The SQL statements that do not require an SQL package are:
v COMMIT
v CONNECT
v
v
v
v
v
v
v
DESCRIBE TABLE
DISCONNECT
RELEASE
RELEASE SAVEPOINT
ROLLBACK
SAVEPOINT
SET CONNECTION
SQL programming
431
Package object type:

SQL packages are always created as non-ILE objects and always run in the default activation group.
ILE programs and service programs:
ILE programs and service programs that bind several modules containing SQL statements must have a
separate SQL package for each module.
Package creation connection:
The type of connection used for the package creation is based on the type of connection specified by the
RDBCNNMTH parameter.
If RDBCNNMTH(*DUW) was specified, commitment control is used and the connection may be a
read-only connection. If the connection is read-only, then the package creation will fail.
Unit of work:
Because package creation implicitly performs a commit or rollback, the commit definition must be at a
unit of work boundary before the package creation is attempted.
The following conditions must all be true for a commit definition to be at a unit of work boundary:
v SQL is at a unit of work boundary.
v There are no local or DDM files open using commitment control and no closed local or DDM files with
pending changes.
v There are no API resources registered.
v There are no LU 6.2 resources registered that are not associated with DRDA or DDM.
Creating packages locally:
The name specified on the RDB parameter can be the name of the local system.
If it is the name of the local system, the SQL package is created on the local system. The SQL package can
be saved (Save Object (SAVOBJ) command) and then restored (Restore Object (RSTOBJ) command) to
another system. When you run the program with a connection to the local system, the SQL package is
not used. If you specify *LOCAL for the RDB parameter, an *SQLPKG object is not created, but the
package information is saved in the *PGM object.
Labels:
You can use the LABEL ON statement to create a description for an SQL package.
Consistency token:
The program and its associated SQL package contain a consistency token that is checked when a call is
made to the SQL package.
The consistency tokens must match; otherwise, the package cannot be used. It is possible for the program
and SQL package to appear to be uncoordinated. Assume that the program and the application server are
on two distinct IBM i operating systems. The program is running in session A and it is re-created in
session B (where the SQL package is also re-created). The next call to the program in session A might
cause a consistency token error. To avoid locating the SQL package on each call, SQL maintains a list of
addresses for SQL packages that are used by each session. When session B re-creates the SQL package,
the old SQL package is moved to the QRPLOBJ library. The address to the SQL package in session A is
432
still valid. You can avoid this situation by creating the program and SQL package from the session that is
running the program, or by submitting a remote command to delete the old SQL package before creating
the program.
To use the new SQL package, you should end the connection with the remote system. You can either sign
off the session and then sign on again, or you can use the interactive SQL (STRSQL) command to issue a
DISCONNECT for unprotected network connections or a RELEASE followed by a COMMIT for protected
connections. RCLDDMCNV should then be used to end the network connections. Call the program again.
SQL and recursion:
If you start SQL from an attention key program while you are already precompiling, you will receive
unpredictable results.
The Create SQL (CRTSQLxxx), Create SQL Package (CRTSQLPKG), and Start SQL Interactive Session
(STRSQL) commands and the SQL runtime environment are not recursive. They produce unpredictable
results if recursion is attempted. Recursion occurs if, while one of the commands is running (or running a
program with embedded SQL statements), the job is interrupted before the command has completed, and
another SQL function is started.
CCSID considerations for SQL

If you are running a distributed application and one of your systems is not a System i product, the server
on the System i platform cannot have the job coded character set identifier (CCSID) value set to 65535.
Before requesting that the remote system create an SQL package, the application requester always
converts the name specified on the RDB parameter, the SQL package name, the library name, and the text
of the SQL package from the CCSID of the job to CCSID 500. This is required by Distributed Relational
Database Architecture (DRDA). When the remote system is a System i product, the names are not
converted from CCSID 500 to the job CCSID.
It is recommended that delimited identifiers not be used for table, view, index, schema, library, or SQL
package names. Conversion of names does not occur between systems with different CCSIDs. Consider
the following example with system A running with a CCSID of 37 and system B running with a CCSID
of 500.
v Create a program that creates a table with the name "ab|c" on system A.
v Save program "ab|c" on system A, then restore it to system B.
v The code point for in CCSID 37 is x'5F' while in CCSID 500 it is x'BA'.
v On system B the name displays "a[b]c". If you created a program that referenced the table whose name
was "ab|c.", the program will not find the table.
The at sign (@), pound sign (#), and dollar sign ($) characters should not be used in SQL object names.
Their code points depend on the CCSID used. If you use delimited names or the three national extenders,
the name resolution functions may possibly fail in a future release.
Connection management and activation groups

SQL connections are managed at the activation group level. Each activation group within a job manages
its own connections and these connections are not shared across activation groups.
Before the use of TCP/IP by Distributed Relational Database Architecture (DRDA), the term connection
was not ambiguous. It referred to a connection from the SQL point of view. That is, a connection starts
when you run the CONNECT TO statement to connect to some relational database (RDB), and ends
when you run the DISCONNECT or RELEASE ALL statement followed by a successful COMMIT
operation. The Advanced Program-to-Program Communication (APPC) conversation might or might not
SQL programming
433
have been kept up, depending on the DDMCNV attribute value of the job and whether the conversation
was with a System i product or with other types of systems.
TCP/IP terminology does not include the term conversation. A similar concept exists, however. With the
advent of TCP/IP support by DRDA, use of the term conversation is replaced, in this topic, by the more
general term connection, unless the discussion is specifically about an APPC conversation. Therefore, there
are now two different types of connections about which the reader must be aware: SQL connections of
the type described above, and network connections which replace the term conversation.
Where there might be the possibility of confusion between the two types of connections, the word will be
qualified by SQL or network to help the reader to understand the intended meaning.
The following is an example of an application that runs in multiple activation groups. This example is
used to illustrate the interaction between activation groups, connection management, and commitment
control. It is not a recommended coding style.
Source code for PGM1

Here is the source code for PGM1.
...
EXEC SQL
CONNECT TO SYSB
END-EXEC.
EXEC SQL
SELECT ...
END-EXEC.
CALL PGM2.
...
Figure 4. Source code for PGM1
Command to create program and SQL package for PGM1:

CRTSQLCBL PGM(PGM1) COMMIT(*NONE) RDB(SYSB)

434
...
EXEC SQL
CONNECT TO SYSC;
EXEC SQL
DECLARE C1 CURSOR FOR
SELECT ...;
EXEC SQL
OPEN C1;
do {
EXEC SQL
FETCH C1 INTO :st1;
EXEC SQL
UPDATE ...
SET COL1 = COL1+10
WHERE CURRENT OF C1;
PGM3(st1);
} while SQLCODE == 0;
EXEC SQL
CLOSE C1;
EXEC SQL COMMIT;
...
Command to create program and SQL package for PGM2:

CRTSQLCI OBJ(PGM2) COMMIT(*CHG) RDB(SYSC) OBJTYPE(*PGM)

...
EXEC SQL
INSERT INTO TAB VALUES(:st1);
EXEC SQL COMMIT;
...
Commands to create program and SQL package for PGM3:

CRTSQLCI OBJ(PGM3) COMMIT(*CHG) RDB(SYSD) OBJTYPE(*MODULE)
CRTPGM PGM(PGM3) ACTGRP(APPGRP)
CRTSQLPKG PGM(PGM3) RDB(SYSD)
SQL programming
435
In this example, PGM1 is a non-ILE program created using the CRTSQLCBL command. This program
runs in the default activation group. PGM2 is created using the CRTSQLCI command, and it runs in a
system-named activation group. PGM3 is also created using the CRTSQLCI command, but it runs in the
activation group named APPGRP. Because APPGRP is not the default value for the ACTGRP parameter,
the CRTPGM command is issued separately. The CRTPGM command is followed by a CRTSQLPKG
command that creates the SQL package object on the SYSD relational database. In this example, the user
has not explicitly started the job level commitment definition. SQL implicitly starts commitment control.
1. PGM1 is called and runs in the default activation group.
2. PGM1 connects to relational database SYSB and runs a SELECT statement.
3. PGM1 then calls PGM2, which runs in a system-named activation group.
436
4. PGM2 does a connect to relational database SYSC. Because PGM1 and PGM2 are in different
activation groups, the connection started by PGM2 in the system-named activation group does not
disconnect the connection started by PGM1 in the default activation group. Both connections are
active. PGM2 opens the cursor and fetches and updates a row. PGM2 is running under commitment
control, is in the middle of a unit of work, and is not at a connectable state.
5. PGM2 calls PGM3, which runs in activation group APPGRP.
6. The INSERT statement is the first statement run in activation group APPGRP. The first SQL statement
causes an implicit connect to relational database SYSD. A row is inserted into table TAB located at
relational database SYSD. The insert is then committed. The pending changes in the system-named
activation group are not committed, because commitment control was started by SQL with a commit
scope of activation group.
7. PGM3 is then exited and control returns to PGM2. PGM2 fetches and updates another row.
8. PGM3 is called again to insert the row. An implicit connect was done on the first call to PGM3. It is
not done on subsequent calls because the activation group did not end between calls to PGM3.
Finally, all the rows are processed by PGM2 and the unit of work associated with the system-named
activation group is committed.
Multiple connections to the same relational database

If different activation groups are connected to the same relational database, each SQL connection has its
own network connection and its own application server job.
If activation groups are run with commitment control, changes committed in one activation group do not
commit changes in other activation groups unless the job-level commitment definition is used.
SQL programming
437
Implicit connection management for the default activation group

An application requester can be implicitly connected to an application server.
Implicit SQL connection occurs when the application requester detects the first SQL statement is being
issued by the first active SQL program for the default activation group and the following items are true:
v The SQL statement being issued is not a CONNECT statement with parameters.
v SQL is not active in the default activation group.
For a distributed program, the implicit SQL connection is to the relational database specified on the RDB
parameter. For a nondistributed program, the implicit SQL connection is to the local relational database.
SQL will end any active connections in the default activation group when SQL becomes not active. SQL
becomes not active when:
v The application requester detects the first active SQL program for the process has ended and the
following are all true:
There are no pending SQL changes
A SET TRANSACTION statement is not active
No programs that were precompiled with CLOSQLCSR(*ENDJOB) were run.
438
If there are pending changes, protected connections, or an active SET TRANSACTION statement, SQL
is placed in the exited state. If programs precompiled with CLOSQLCSR(*ENDJOB) were run, SQL will
remain active for the default activation group until the job ends.
v At the end of a unit of work, if SQL is in the exited state. This occurs when you issue a COMMIT or
ROLLBACK command outside of an SQL program.
v At the end of a job.
Related reference:
Ending connections on page 444
Because remote SQL connections use resources, you need to end the connections that are no longer used,
as soon as possible. You can end connections implicitly or explicitly.
Implicit connection management for nondefault activation groups

An application requester can be implicitly connected to an application server. Implicit SQL connection
occurs when the application requester detects that the first SQL statement issued for the activation group
is not a CONNECT statement with parameters.
For a distributed program, the implicit SQL connection is made to the relational database specified on the
RDB parameter. For a nondistributed program, the implicit SQL connection is made to the local relational
database.
Implicit disconnect can occur at the following times in a process:
v When the activation group ends, if commitment control is not active, activation group level
commitment control is active, or the job level commitment definition is at a unit of work boundary.
If the job level commitment definition is active and not at a unit of work boundary, SQL is placed in
the exited state.
v If SQL is in the exited state, when the job level commitment definition is committed or rolled back.
v At the end of a job.
Related reference:
Ending connections on page 444
Distributed support
DB2 for i supports these levels of distributed relational database.
v Remote unit of work (RUW)
Remote unit of work is where the preparation and running of SQL statements occurs at only one
application server during a unit of work. An activation group with an application process at an
application requester can connect to an application server and, within one or more units of work, run
any number of static or dynamic SQL statements that refer to objects on the application server. Remote
unit of work is also referred to as DRDA level 1.
v Distributed unit of work (DUW)
Distributed unit of work is where the preparation and running of SQL statements can occur at multiple
applications servers during a unit of work. However, a single SQL statement can only refer to objects
located at a single application server. Distributed unit of work is also referred to as DRDA level 2.
Distributed unit of work allows:
Update access to multiple application servers in one logical unit of work
or
Update access to a single application server with read access to multiple application servers, in one
logical unit of work.
SQL programming
439
Whether multiple application servers can be updated in a unit of work is dependent on the existence
of a sync point manager at the application requester, sync point managers at the application servers,
and two-phase commit protocol support between the application requester and the application servers.
The sync point manager is a system component that coordinates commit and rollback operations
among the participants in the two-phase commit protocol. When running distributed updates, the sync
point managers on the different systems cooperate to ensure that resources reach a consistent state. The
protocols and flows used by sync point managers are also referred to as two-phase commit protocols. If
two-phase commit protocols will be used, the connection is a protected resource; otherwise the
connection is an unprotected resource.
Determining the connection type

When a remote SQL connection is established, it uses either an unprotected or a protected network
connection.
With regards to committable updates, this SQL connection may be read-only, updatable, or unknown
whether it is updatable when the connection is established. A committable update is any insert, delete,
update, or DDL statement that is run under commitment control. If the connection is read-only, changes
using COMMIT(*NONE) can still be run. After a CONNECT or SET CONNECTION, SQLERRD(4) of the
SQLCA and DB2_CONNECTION_TYPE of the SQL diagnostic area indicate the type of connection.
DB2_CONNECTION_TYPE specific values are:
1.
2.
3.
4.
The
The
The
The
connection
connection
connection
connection
is
is
is
is
to
to
to
to
the local relational database and the connection is protected.

a remote relational database and the connection is unprotected.
a remote relational database and the connection is protected.
an application requester driver program and the connection is protected.
SQLERRD(4) specific values are:

1. The connection is to a remote relational database and the connection is unprotected. Committable
updates can be performed on the connection. This will occur when any of the following are true:
v The connection is established using remote unit of work (RUW).
v If the connection is established using distributed unit of work (DUW) then all the following are
true:
The connection is not local.
The application server does not support distributed unit of work.
The commitment control level of the program issuing the connect is not *NONE.
Either no connections to other application servers (including local) exist that can perform
committable updates or all connections are read-only connections to application servers that do
not support distributed unit of work.
There are no open updatable local files under commitment control for the commitment
definition.
There are no open updatable DDM files that use a different connection under commitment
control for the commitment definition.
There are no API commitment control resources for the commitment definition.
There are no protected connections registered for the commitment definition.
If running with commitment control, SQL will register a one-phase updatable DRDA resource for
remote connections or a two-phase updatable DRDA resource for local and ARD connections.
2. The connection is to a remote relational database and the connection is unprotected. The connection is
read-only. This will occur only when the following are true:
v The connection is not local.
v The application server does not support distributed unit of work
v At least one of the following is true:
440
The commitment control level of the program issuing the connect is *NONE.
Another connection exists to an application server that does not support distributed unit-of-work
and that application server can perform committable updates
Another connection exists to an application server that supports distributed unit-of-work
(including local).
There are open updatable local files under commitment control for the commitment definition.
There are open updatable DDM files that use a different connection under commitment control
for the commitment definition.
There are no one-phase API commitment control resources for the commitment definition.
There are protected connections registered for the commitment definition.
If running with commitment control, SQL will register a one-phase DRDA read-only resource.
3. The connection is to a remote relational database and the connection is protected. It is unknown if
committable updates can be performed. This will occur when all of the following are true:
v The commitment control level of the program issuing the connect is not *NONE.
v The application server supports both distributed unit of work and two-phase commit protocol
(protected connections).
If running with commitment control, SQL will register a two-phase DRDA undetermined resource.
4. The connection is to a remote relational database and the connection is unprotected. It is unknown if
committable updates can be performed. This will occur only when all of the following are true:
v The application server supports distributed unit of work
v Either the application server does not support two-phase commit protocols (protected connections)
or the commitment control level of the program issuing the connect is *NONE.
If running with commitment control, SQL will register a one-phase DRDA undetermined resource.
5. The connection is to the local database or an application requester driver (ARD) program and the
connection is protected. It is unknown if committable updates can be performed. If running with
commitment control, SQL will register a two-phase DRDA undetermined resource.
The following table summarizes the type of connection that will result for remote distributed unit of
work connections. SQLERRD(4) is set on successful CONNECT and SET CONNECTION statements.
Table 100. Summary of connection type
Connect under
commitment control
Application server
supports two-phase
commit
Application server
supports distributed
unit of work
Other updatable
one-phase resource
registered
SQLERRD(4)
No
No
No
No
No
No
No
Yes
No
No
Yes
No
No
No
Yes
Yes
No
Yes
No
No
No
Yes
No
Yes
No
Yes
Yes
No
No
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
Yes
Yes
No
Yes
No
4
SQL programming
441
Table 100. Summary of connection type (continued)

Connect under
commitment control
Application server
supports two-phase
commit
Application server
supports distributed
unit of work
Other updatable
one-phase resource
registered
SQLERRD(4)
Yes
No
Yes
Yes
Yes
Yes
No
No
N/A 1
Yes
Yes
No
Yes
N/A 1
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
DRDA does not allow protected connections to be used to application servers that support only remote unit of work
(DRDA1). This includes all DB2 for IBM i TCP/IP connections.
Related concepts:
Commitment control
Related reference:
Accessing remote databases with interactive SQL on page 419
In interactive SQL, you can communicate with a remote relational database by using the SQL CONNECT
statement. Interactive SQL uses the CONNECT (Type 2) semantics (distributed unit of work) for
CONNECT statements.
Connect and commitment control restrictions

There are restrictions on when you can establish the connection using commitment control. The
restrictions also apply if you attempt to run statements using commitment control, but you specified
COMMIT(*NONE) on the connection.
If a two-phase undetermined or updatable resource is registered or a one-phase updatable resource is
registered, another one-phase updatable resource cannot not be registered.
Furthermore, when protected connections are inactive and the DDMCNV job attribute is *KEEP, these
unused DDM connections will also cause the CONNECT statements in programs compiled with RUW
connection management to fail.
If running with RUW connection management and using the job-level commitment definition, then there
are some restrictions.
v If the job-level commitment definition is used by more than one activation group, all RUW connections
must be to the local relational database.
v If the connection is remote, only one activation group may use the job-level commitment definition for
RUW connections.
Determining the connection status

A CONNECT statement without parameters can be used to determine whether the current connection is
updatable or read-only for the current unit of work.
A value of 1 or 2 is returned in SQLERRD(3) in the SQLCA or DB2_CONNECTION_STATUS in the SQL
diagnostic area. The value is determined as follows:
1. Committable updates can be performed on the connection for the unit of work.
This will occur when one of the following is true:
v The connection is established using remote unit of work (RUW).
v If the connection is established using distributed unit of work (DUW) and all of the following are
true:
442
No connection exists to an application server that does not support distributed unit of work
which can perform committable updates.
One of the following is true:
- The first committable update is performed on a connection that uses a protected connection, is
performed on the local database, or is performed on a connection to an ARD program.
- There are open updatable local files under commitment control. .
- There are open updatable DDM files that use protected connections.
- There are two-phase API commitment control resources.
- No committable updates have been made.
v If the connection is established using distributed unit of work (DUW) and all of the following are
true:
No other connections exist to an application server that does not support distributed unit of
work which can perform committable updates.
The first committable update is performed on this connection or no committable updates have
been made.
There are no open updatable DDM files that use protected connections.
There are no open updatable local files under commitment control.
There are no two-phase API commitment control resources.
2. No committable updates can be performed on the connection for this unit of work.
This will occur when one of the following is true:
v If the connection is established using distributed unit of work (DUW) and one of the following are
true:
A connection exists to an updatable application server that only supports remote unit of work.
The first committable update is performed on a connection that uses an unprotected connection.
v If the connection is established using distributed unit of work (DUW) and one of the following are
true:
A connection exists to an updatable application server that only supports remote unit of work.
The first committable update was not performed on this connection.
There are open updatable DDM files that use protected connections.
There are open updatable local files under commitment control.
There are two-phase API commitment control resources.
The following table summarizes how the connection status is determined based on the connection type
value, if there is an updatable connection to an application server that only supports remote unit of work,
and where the first committable update occurred.
Table 101. Summary of determining connection status values
Connection method
Connection exists to
updatable remote unit of
work application server
Where first committable

update occurred 1
RUW
SQLERRD(3) or
DB2_CONNECTION_STATUS
1
DUW
Yes
DUW
No
no updates
DUW
No
one-phase
DUW
No
this connection
DUW
No
two-phase
SQL programming
443
Table 101. Summary of determining connection status values (continued)

Connection method
Connection exists to
updatable remote unit of
work application server
Where first committable

update occurred 1
SQLERRD(3) or
DB2_CONNECTION_STATUS
The terms in this column are defined as:
v No updates indicates no committable updates have been performed, no DDM files open for update using a
protected connection, no local files are open for update, and no commitment control APIs are registered.
v One-phase indicates the first committable update was performed using an unprotected connection or DDM files are
open for update using unprotected connections.
v Two-phase indicates a committable update was performed on a two-phase distributed-unit-of-work application
server, DDM files are open for update using a protected connection, commitment control APIs are registered, or
local files are open for update under commitment control.
If an attempt is made to perform a committable update over a read-only connection, the unit of work will
be placed in a rollback required state. If an unit of work is in a rollback required state, the only statement
allowed is a ROLLBACK statement; all other statements will result in SQLCODE -918.
Distributed unit of work connection considerations

When you connect in a distributed unit of work application, consider these points.
v If the unit of work will perform updates at more than one application server and commitment control
will be used, all connections over which updates will be done should be made using commitment
control. If the connections are done not using commitment control and later committable updates are
performed, read-only connections for the unit of work are likely to result.
v Other non-SQL commit resources, such as local files, DDM files, and commitment control API
resources, will affect the updatable and read-only status of a connection.
v If you connect using commitment control to an application server that does not support distributed
unit of work (for example, a V4R5 system using TCP/IP), that connection is either updatable or
read-only. If the connection is updatable, it is the only updatable connection. Since V5R3, Distributed
Relational Database Architecture (DRDA) two-phase-commit operations have taken the following
updates into consideration:
Updates done as a result of triggers
Updates done as a result of user-defined functions that are activated during a database query
Ending connections
Connections can be explicitly ended by either the DISCONNECT statement or the RELEASE statement
followed by a successful COMMIT. The DISCONNECT statement can only be used with connections that
use unprotected connections or with local connections. The DISCONNECT statement will end the
connection when the statement is run. The RELEASE statement can be used with either protected or
unprotected connections. When the RELEASE statement is run, the connection is not ended but instead
placed into the released state. A connection that is in the release stated can still be used. The connection is
not ended until a successful COMMIT is run. A ROLLBACK or an unsuccessful COMMIT will not end a
connection in the released state.
When a remote SQL connection is established, a distributed data management (DDM) network
connection (Advanced Program-to-Program Communication (APPC) conversation or TCP/IP connection)
is used. When the SQL connection is ended, the network connection might either be placed in the unused
state or dropped. Whether a network connection is dropped or placed in the unused state depends on the
DDMCNV job attribute. If the job attribute value is *KEEP and the connection is to a server on the
System i platform, the connection becomes unused. If the job attribute value is *DROP and the connection
444
is to a server on the System i platform, the connection is dropped. If the connection is to a server on a
non-System i platform, the connection is always dropped. *DROP is desirable in the following situations:
v When the cost of maintaining the unused connection is high and the connection will not be used
relatively soon.
v When running with a mixture of programs, some compiled with RUW connection management and
some programs compiled with DUW connection management. Attempts to run programs compiled
with RUW connection management to remote locations will fail when protected connections exist.
v When running with protected connections using either DDM or DRDA. Additional overhead is
incurred on commits and rollbacks for unused protected connections.
The Reclaim DDM connections (RCLDDMCNV) command may be used to end all unused connections, if
they are at a commit boundary.
Related reference:
Implicit connection management for the default activation group on page 438
An application requester can be implicitly connected to an application server.
Implicit connection management for nondefault activation groups on page 439
An application requester can be implicitly connected to an application server. Implicit SQL connection
occurs when the application requester detects that the first SQL statement issued for the activation group
is not a CONNECT statement with parameters.
Distributed unit of work

Distributed unit of work (DUW) allows access to multiple application servers within the same unit of
work.
Each SQL statement can access only one application server. Using distributed unit of work allows
changes at multiple application servers to be committed or rolled back within a single unit of work.
Managing distributed unit of work connections

You can use the CONNECT, SET CONNECTION, DISCONNECT, and RELEASE statements to manage
connections in the distributed unit of work (DUW) environment.
A distributed unit of work CONNECT is run when the program is precompiled using
RDBCNNMTH(*DUW), which is the default. This form of the CONNECT statement does not disconnect
existing connections but instead places the previous connection in the dormant state. The relational
database specified on the CONNECT statement becomes the current connection. The CONNECT
statement can only be used to start new connections; if you want to switch between existing connections,
the SET CONNECTION statement must be used. Because connections use system resources, connections
should be ended when they are no longer needed. The RELEASE or DISCONNECT statement can be
used to end connections. The RELEASE statement must be followed by a successful commit in order for
the connections to end.
The following is an example of a C program running in a DUW environment that uses commitment
control.
SQL programming
445
...
EXEC SQL WHENEVER SQLERROR GO TO done;
EXEC SQL WHENEVER NOT FOUND GO TO done;
...
EXEC SQL
DECLARE C1 CURSOR WITH HOLD FOR
SELECT PARTNO, PRICE
FROM PARTS
WHERE SITES_UPDATED = N
FOR UPDATE OF SITES_UPDATED;
/*
Connect to the systems
*/
EXEC SQL CONNECT TO LOCALSYS;
EXEC SQL CONNECT TO SYSB;
EXEC SQL CONNECT TO SYSC;
/* Make the local system the current connection */
EXEC SQL SET CONNECTION LOCALSYS;
/* Open the cursor */
EXEC SQL OPEN C1;
while (SQLCODE==0)
{
/* Fetch the first row */
EXEC SQL FETCH C1 INTO :partnumber,:price;
/* Update the row which indicates that the updates have been
propagated to the other sites */
EXEC SQL UPDATE PARTS SET SITES_UPDATED=Y
WHERE CURRENT OF C1;
/* Check if the part data is on SYSB */
if ((partnumber > 10) && (partnumber < 100))
{
/* Make SYSB the current connection and update the price */
EXEC SQL SET CONNECTION SYSB;
EXEC SQL UPDATE PARTS
SET PRICE=:price
WHERE PARTNO=:partnumber;
}
/* Check if the part data is on SYSC */
if ((partnumber > 50) && (partnumber < 200))
{
/* Make SYSC the current connection and update the price */
EXEC SQL SET CONNECTION SYSC;
EXEC SQL UPDATE PARTS
SET PRICE=:price
WHERE PARTNO=:partnumber;
}
/* Commit the changes made at all 3 sites */
EXEC SQL COMMIT;
/* Set the current connection to local so the next row
can be fetched */
}
done:
EXEC SQL WHENEVER SQLERROR
/* Release the connections
EXEC SQL RELEASE SYSB;
EXEC SQL RELEASE SYSC;
/* Close the cursor */
EXEC SQL CLOSE C1;
/* Do another commit which
The local connection is
released. */
EXEC SQL COMMIT;
...
CONTINUE;
that are no longer being used */
will end the released connections.

still active because it was not
Figure 7. Example of distributed unit of work program
446
In this program, there are three application servers active: LOCALSYS which the local system, and two
remote systems, SYSB and SYSC. SYSB and SYSC also support distributed unit of work and two-phase
commit.
Initially all connections are made active by using the CONNECT statement for each of the application
servers involved in the transaction. When using DUW, a CONNECT statement does not disconnect the
previous connection, but instead places the previous connection in the dormant state. After all the
application servers have been connected, the local connection is made the current connection using the
SET CONNECTION statement. The cursor is then opened and the first row of data fetched. It is then
determined at which application servers the data needs to be updated. If SYSB needs to be updated, then
SYSB is made the current connection using the SET CONNECTION statement and the update is run. The
same is done for SYSC. The changes are then committed.
Because two-phase commit is being used, it is guaranteed that the changes are committed at the local
system and the two remote systems. Because the cursor was declared WITH HOLD, it remains open after
the commit. The current connection is then changed to the local system so that the next row of data can
be fetched. This set of fetches, updates, and commits is repeated until all the data has been processed.
After all the data has been fetched, the connections for both remote systems are released. They cannot be
disconnected because they use protected connections. After the connections are released, a commit is
issued to end the connections. The local system is still connected and continues processing.
Checking the connection status

When it is possible to have a read-only connection, your program should check the status of the
connection before doing any committable updates. This prevents the unit of work from entering the
rollback required state.
The following COBOL example shows how to check the connection status.
...
EXEC SQL
SET CONNECTION SYS5
END-EXEC.
...
* Check if the connection is updatable.
EXEC SQL CONNECT END-EXEC.
* If connection is updatable, update sales information otherwise
* inform the user.
IF SQLERRD(3) = 1 THEN
EXEC SQL
INSERT INTO SALES_TABLE
VALUES(:SALES-DATA)
END-EXEC
ELSE
DISPLAY Unable to update sales information at this time.
...
Figure 8. Example of checking connection status
Cursors and prepared statements

Cursors and prepared statements are scoped to the compilation unit and also to the connection.
Scoping to the compilation unit means that a program called from another separately compiled program
cannot use a cursor or prepared statement that was opened or prepared by the calling program. Scoping
to the connection means that each connection within a program can have its own separate instance of a
cursor or prepared statement.
SQL programming
447
The following distributed unit of work example shows how the same cursor name is opened in two
different connections, resulting in two instances of cursor C1.
...
EXEC SQL DECLARE C1 CURSOR FOR
SELECT * FROM CORPDATA.EMPLOYEE;
/* Connect to local and open C1 */
EXEC SQL CONNECT TO LOCALSYS;
EXEC SQL OPEN C1;
/* Connect to the remote system and open C1 */
EXEC SQL CONNECT TO SYSA;
EXEC SQL OPEN C1;
/* Keep processing until done */
while (NOT_DONE) {
/* Fetch a row of data from the local system */
EXEC SQL FETCH C1 INTO :local_emp_struct;
/* Fetch a row of data from the remote system */
EXEC SQL SET CONNECTION SYSA;
EXEC SQL FETCH C1 INTO :rmt_emp_struct;
/* Process the data */
...
}
/* Close the cursor on the remote system */
EXEC SQL CLOSE C1;
/* Close the cursor on the local system */
EXEC SQL CLOSE C1;
...
Figure 9. Example of cursors in a DUW program
DRDA stored procedure considerations

The i5/OS Distributed Relational Database Architecture (DRDA) server supports the return of one or
more result sets in a stored procedure.
You can generate result sets in a stored procedure by opening one or more SQL cursors associated with
SELECT statements. In addition, a maximum of one array result set can also be returned. Before V5R3,
only one instance of a query opened in a stored procedure was allowed to be open at one time. Now you
can make multiple calls to the same stored procedure without closing the result set cursors so that more
than one instance of a query can be opened simultaneously.
Related concepts:
Related reference:
SET RESULT SETS
CREATE PROCEDURE (SQL)
CREATE PROCEDURE (External)
|
WebSphere MQ with DB2
| WebSphere MQ is a message handling system that enables applications to communicate in a distributed

| environment across different operating systems and networks.
448
|
|
|
WebSphere MQ handles the communication from one program to another by using application
programming interfaces (APIs). You can use any of the following APIs to interact with the WebSphere
MQ message handling system:
|
|
|
v Message Queue Interface (MQI)

v WebSphere MQ classes for Java
v WebSphere MQ classes for Java Message Service (JMS)
|
|
|
|
DB2 provides its own application programming interface to the WebSphere MQ message handling system
through a set of external user-defined functions, which are called DB2 MQ functions. You can use these
functions in SQL statements to combine DB2 database access with WebSphere MQ message handling. The
DB2 MQ functions use the MQI APIs.
WebSphere MQ messages
WebSphere MQ uses messages to pass information between applications.
|
|
|
Messages consist of the following parts:

v The message attributes, which identify the message and its properties.
v The message data, which is the application data that is carried in the message.
|
|
|
WebSphere MQ message handling
|
|
In WebSphere MQ, a destination is called a message queue, and a queue resides in a queue manager.
Applications can put messages on queues or get messages from them.
|
|
DB2 communicates with the WebSphere message handling system through a set of external user-defined
functions, which are called DB2 MQ functions. These functions use the MQI APIs.
When you send a message by using the MQI APIs, you must specify following three components:
|
|
message data
Defines what is sent from one program to another.
|
|
|
|
service
|
|
|
|
policy Defines how the message is handled. Policies control such items as:
v The attributes of the message, for example, the priority.
v Options for send and receive operations, for example, whether an operation is part of a unit of
work.
|
|
|
|
|
MQ functions use the services and policies that are defined in two DB2 tables,
SYSIBM.MQSERVICE_TABLE and SYSIBM.MQPOLICY_TABLE. These tables are automatically created by
DB2, but once created, they are user-managed and typically maintained by a system administrator. DB2
initially provides each table with a row for the default service and default policy. The default service is
DB2.DEFAULT.SERVICE and the default policy is DB2.DEFAULT.POLICY.
|
|
|
The application program does not need to know the details of the services and policies that are defined
in these tables. The application need only specify which service and policy to use for each message that it
sends and receives. The application specifies this information when it invokes a DB2 MQ function.
Conceptually, the WebSphere MQ message handling system takes a piece of information (the message)
and sends it to its destination. MQ guarantees delivery despite any network disruptions that might occur.
Defines where the message is going to or coming from. The parameters for managing a queue are
defined in the service, which is typically defined by a system administrator. The complexity of
the parameters in the service is hidden from the application program.
SQL programming
449
| DB2 MQ services:
|
|
|
|
A service describes a destination to which an application sends messages or from which an application
receives messages. DB2 MQ services are defined in the DB2 table SYSIBM.MQSERVICE_TABLE. When an
application program invokes a DB2 MQ function, the program selects a service from
SYSIBM.MQSERVICE_TABLE by specifying it as a parameter.
| The SYSIBM.MQSERVICE_TABLE is automatically created by DB2, but once created, it is user-managed

| and typically maintained by a system administrator. DB2 initially provides a row for the default service.
| The default service is DB2.DEFAULT.SERVICE.
| A new service can be added simply by issuing an INSERT statement. For example, the following
| statement adds a new service called MYSERVICE. The MQ default queue manager and the MYQUEUE
| input queue will be used for this new service.
|
INSERT INTO SYSIBM.MQSERVICE_TABLE (SERVICENAME, QUEUEMANAGER, INPUTQUEUE)
|
VALUES(MYSERVICE, SPACE(48), MYQUEUE)
|
|
|
|
|
|
|
|
|
A service can be changed (including the default service) simply by issuing an UPDATE statement. For
performance reasons, DB2 caches the service information so any existing job that has already used an MQ
function will typically not detect a concurrent change to a service. The following statement updates the
service called MYSERVICE by changing the input queue to MYQUEUE2.
|
|
|
|
|
|
|
|
|
|
Note: The default input queue initially used by the default service DB2.DEFAULT.SERVICE is the MQ
model queue called SYSTEM.DEFAULT.LOCAL.QUEUE. The default input queue used by other DB2
products is DB2MQ_DEFAULT_Q. For compatibility with other DB2 products, you may wish to create a
new input queue called DB2MQ_DEFAULT_Q and update the default service. For example:
UPDATE SYSIBM.MQSERVICE_TABLE
SET INPUTQUEUE = MYQUEUE2
WHERE SERVICENAME = MYSERVICE
CL: CRTMQMQ QNAME(DB2MQ_DEFAULT_Q) QTYPE(*LCL);

UPDATE SYSIBM.MQSERVICE_TABLE
SET INPUTQUEUE = DB2MQ_DEFAULT_Q
WHERE SERVICENAME = DB2.DEFAULT.SERVICE
| DB2 MQ policies:
| A policy controls how the MQ messages are handled. DB2 MQ policies are defined in the DB2 table
| SYSIBM.MQPOLICY_TABLE. When an application program invokes a DB2 MQ function, the program
| selects a policy from SYSIBM.MQPOLICY_TABLE by specifying it as a parameter.
| The SYSIBM.MQPOLICY_TABLE is automatically created by DB2, but once created, it is user-managed
| and typically maintained by a system administrator. DB2 initially provides a row for the default policy.
| The default policy is DB2.DEFAULT.POLICY .
| A new policy can be added simply by issuing an INSERT statement. For example, the following
| statement adds a new policy called MYPOLICY. Since the value of the SYNCPOINT column is 'N', any
| MQ functions that use MYPOLICY will not run under a transaction.
|
INSERT INTO SYSIBM.MQPOLICY_TABLE (POLICYNAME, SYNCPOINT, DESCRIPTION)
|
VALUES(MYPOLICY, N, Policy to not run under a transaction)
|
| A policy can be changed (including the default policy) simply by issuing an UPDATE statement. For
| performance reasons, DB2 caches the policy information so any existing job that has already used an MQ
450
|
|
|
|
|
|
function will typically not detect a concurrent change to a policy. The following statement updates the
policy called MYPOLICY by changing the retry interval to 5 seconds.
DB2 MQ functions
|
|
You can use the DB2 MQ functions to send messages to a message queue or to receive messages from the
message queue. You can send a request to a message queue and receive a response.
|
|
The DB2 MQ functions support the following types of operations:

v Send and forget, where no reply is needed.
|
|
|
v Read or receive, where one or all messages are either read without removing them from the queue, or
received and removed from the queue.
v Request and response, where a sending application needs a response to a request.
|
|
The WebSphere MQ server is located on the same System i as DB2. The DB2 MQ functions are registered
with DB2 and provide access to the WebSphere MQ server by using the MQI APIs.
The following table describes the DB2 MQ scalar functions.
Table 102. DB2 MQ Scalar Functions
Scalar function
Description
|
|
|
|
MQREAD
MQREAD returns a message in a VARCHAR variable from the MQ location specified

by receive-service, using the policy defined in service-policy. This operation does not
remove the message from the head of the queue but instead returns it. If no messages
are available to be returned, a null value is returned.
|
|
|
|
MQREADCLOB
MQREADCLOB returns a message in a CLOB variable from the MQ location

specified by receive-service, using the policy defined in service-policy. This operation
does not remove the message from the head of the queue but instead returns it. If no
messages are available to be returned, a null value is returned.
|
|
|
|
|
|
MQRECEIVE
MQRECEIVE returns a message in a VARCHAR variable from the MQ location

removes the message from the queue. If correlation-id is specified, the first message
with a matching correlation identifier is returned; if correlation-id is not specified, the
message at the beginning of queue is returned. If no messages are available to be
returned, a null value is returned.
|
|
|
|
|
|
MQRECEIVECLOB
MQRECEIVECLOB returns a message in a CLOB variable from the MQ location

removes the message from the queue. If correlation-id is specified, the first message
with a matching correlation identifier is returned; if correlation-id is not specified, the
message at the head of queue is returned. If no messages are available to be returned,
a null value is returned.
|
|
|
|
MQSEND
MQSEND sends the data in a VARCHAR or CLOB variable msg-data to the MQ

location specified by send-service, using the policy defined in service-policy. An optional
user-defined message correlation identifier can be specified by correlation-id. The
return value is 1 if successful or 0 if not successful.
|
|
|
|
Notes:
The following table describes the DB2 MQ table functions.
UPDATE SYSIBM.MQPOLICY_TABLE
SET SEND_RETRY_INTERVAL = 5000
WHERE POLICYNAME = MYPOLICY
1. You can send or receive messages in VARCHAR variables or CLOB variables. The maximum length for a
message in a VARCHAR variable is 32000. The maximum length for a message in a CLOB variable is 2 MB.
SQL programming
451
Table 103. DB2 MQ Table Functions
Table function
Description
|
|
|
|
|
MQREADALL
MQREADALL returns a table that contains the messages and message metadata in
VARCHAR variables from the MQ location specified by receive-service, using the
policy defined in service-policy. This operation does not remove the messages from the
queue. If num-rows is specified, a maximum of num-rows messages is returned; if
num-rows is not specified, all available messages are returned.
|
|
|
|
|
MQREADALLCLOB
MQREADALLCLOB returns a table that contains the messages and message metadata
in CLOB variables from the MQ location specified by receive-service, using the policy
defined in service-policy. This operation does not remove the messages from the queue.
If num-rows is specified, a maximum of num-rows messages is returned; if num-rows is
not specified, all available messages are returned.
|
|
|
|
|
|
|
MQRECEIVEALL
MQRECEIVEALL returns a table that contains the messages and message metadata in
VARCHAR variables from the MQ location specified by receive-service, using the
policy defined in service-policy. This operation removes the messages from the queue.
If correlation-id is specified, only those messages with a matching correlation identifier
are returned; if correlation-id is not specified, all available messages are returned. If
num-rows is specified, a maximum of num-rows messages is returned; if num-rows is
not specified, all available messages are returned.
|
|
|
|
|
|
|
MQRECEIVEALLCLOB
MQRECEIVEALLCLOB returns a table that contains the messages and message

metadata in CLOB variables from the MQ location specified by receive-service, using
the policy defined in service-policy. This operation removes the messages from the
queue. If correlation-id is specified, only those messages with a matching correlation
identifier are returned; if correlation-id is not specified, all available messages are
returned. If num-rows is specified, a maximum of num-rows messages is returned; if
num-rows is not specified, all available messages are returned.
|
|
|
|
|
Notes:
1. You can send or receive messages in VARCHAR variables or CLOB variables. The maximum length for a
message in a VARCHAR variable is 32000. The maximum length for a message in a CLOB variable is 2 MB.
2. The first column of the result table of a DB2 MQ table function contains the message.
| DB2 MQ dependencies
| In order to use the DB2 MQ functions, IBM MQSeries for IBM i must be installed, configured, and
| operational.
| Detailed information on installation and configuration can be found in the Websphere MQSeries
| Information Center. At a minimum, the following steps are necessary once you have completed the install
| of IBM MQSeries for IBM i:
| 1. Start the MQSeries subsystem
|
CL: STRSBS SBSD(QMQM/QMQM);
|
| 2. Create a default MQ message queue manager. For example:
|
CL: ADDLIBLE QMQM;
|
CL: CRTMQM MQMNAME(MJAQM) DFTQMGR(*YES);
|
|
Ensure that the job default CCSID is set to the primary use for MQ since the CCSID of the MQ
|
message queue manager is set to the job default CCSID when it is created.
| 3. Start the default MQ message queue manager.
|
CL: STRMQM MQMNAME(MJAQM);
|
452
DB2 MQ tables
The DB2 MQ tables contain service and policy definitions that are used by the DB2 MQ functions.
|
|
|
|
|
The DB2 MQ tables are SYSIBM.MQSERVICE_TABLE and SYSIBM.MQPOLICY_TABLE. These tables are
user-managed. The tables are initially created by DB2 and populated with one default service
(DB2.DEFAULT.SERVICE) and one default policy (DB2.DEFAULT.POLICY). You may modify the
attributes of the default service and policy by updating the rows in the tables. You can add additional
services and policies by inserting additional rows in the tables.
The following table describes the columns for SYSIBM.MQSERVICE_TABLE.
Table 104. SYSIBM.MQSERVICE_TABLE column descriptions
Column name
Description
|
|
SERVICENAME
This column contains the service name, which is an optional input parameter of
the MQ functions.
|
|
|
This column is the primary key for the SYSIBM.MQSERVICE_TABLE table.

QUEUEMANAGER
|
|
This column contains the name of the queue manager where the MQ functions
are to establish a connection.
If the column consists of 48 blanks, the name of the default MQSeries queue
manager is used.
|
|
INPUTQUEUE
This column contains the name of the queue from which the MQ functions are to
send and retrieve messages.
|
|
CODEDCHARSETID
This column contains the character set identifier (CCSID) for data in the messages
that are sent and received by the MQ functions.
|
|
|
This column corresponds to the CodedCharSetId field (MDCSI) in the message

descriptor (MQMD). MQ functions use the value in this column to set the
CodedCharSetId field.
|
|
The default value for this column is -3, which causes DB2 to set the
CodedCharSetId field (MDCSI) to the default job CCSID.
|
|
ENCODING
This column contains the encoding value for the numeric data in the messages
that are sent and received by the MQ functions.
|
|
|
This column corresponds to the Encoding field (MDENC) in the message

descriptor (MQMD). MQ functions use the value in this column to set the
Encoding field.
|
|
The default value for this column is 0, which sets the Encoding field (MDENC) to
the value MQENC_NATIVE.
|
|
DESCRIPTION
The following table describes the columns for SYSIBM.MQPOLICY_TABLE.
Table 105. SYSIBM.MQPOLICY_TABLE column descriptions
Column name
Description
|
|
POLICYNAME
This column contains the policy name, which is an optional input parameter of
the MQ functions.
This column contains the detailed description of the service.
This column is the primary key for the SYSIBM.MQPOLICY_TABLE table.
SQL programming
453
Table 105. SYSIBM.MQPOLICY_TABLE column descriptions (continued)
Column name
Description
SEND_PRIORITY
This column contains the priority of the message.
|
|
This column corresponds to the Priority field in the message descriptor (MQMD).
MQ functions use the value in this column to set the Priority field.
|
|
The default value for this column is -1, which sets the Priority field in the MQMD
to the value MQQPRI_PRIORITY_AS_Q_DEF.
|
|
SEND_PERSISTENCE
This column indicates whether the message persists despite any system failures or
instances of restarting the queue manager.
|
|
This column corresponds to the Persistence field in the message descriptor

(MQMD). MQ functions use the value in this column to set the Persistence field.
This column can have the following values:
|
|
Sets the Persistence field in the MQMD to the value

MQPER_PERSISTENCE_AS_Q_DEF. This value is the default.
|
|
Sets the Persistence field in the MQMD to the value

MQPER_PERSISTENT.
|
|
Sets the Persistence field in the MQMD to the value MQPER_NOT_

PERSISTENT.
SEND_EXPIRY
This column contains the message expiration time, in tenths of a second.
|
|
This column corresponds to the Expiry field in the message descriptor (MQMD).
MQ functions use the value in this column to set the Expiry field.
|
|
The default value is -1, which sets the Expiry field to the value
MQEI_UNLIMITED.
|
|
SEND_RETRY_COUNT
|
|
|
The default value is 5.

SEND_RETRY_INTERVAL
|
|
|
|
This column contains the number of times that the MQ function is to try to send
a message if the procedure fails.
This column contains the interval, in milliseconds, between each attempt to send
a message.
The default value is 1000.
SEND_NEW_CORRELID
This column specifies how the correlation identifier is to be set if a correlation

identifier is not passed as an input parameter in the MQ function. The correlation
identifier is set in the CorrelId field in the message descriptor (MQMD).
This column can have one of the following values:
|
|
Sets the CorrelId field in the MQMD to binary zeros. This value is the
default.
|
|
|
|
Specifies that the queue manager is to generate a new correlation

identifier and set the CorrelId field in the MQMD to that value. This 'Y'
value is equivalent to setting the MQPMO_NEW_CORREL_ID option in
the Options field in the put message options (MQPMO).
454
Column name
Description
|
|
SEND_RESPONSE_MSGID
This column specifies how the MsgId field in the message descriptor (MQMD) is
to be set for report and reply messages.
|
|
This column corresponds to the Report field in the MQMD. MQ functions use the
value in this column to set the Report field.
|
|
Sets the MQRO_NEW_MSG_ID option in the Report field in the MQMD.

This value is the default.
Sets the MQRO_PASS_MSG_ID option in the Report field in the MQMD.
|
|
SEND_RESPONSE_CORRELID
This column specifies how the CorrelID field in the message descriptor (MQMD)
is to be set for report and reply messages.
|
|
This column corresponds to the Report field in the MQMD. MQ functions use the
value in this column to set the Report field.
|
|
Sets the MQRO_COPY_MSG_ID_TO_CORREL_ID option in the Report

field in the MQMD. This value is the default.
|
|
Sets the MQRO_PASS_CORREL_ID option in the Report field in the

MQMD.
|
|
SEND_EXCEPTION_ACTION
This column specifies what to do with the original message when it cannot be
delivered to the destination queue.
|
|
This column corresponds to the Report field in the message descriptor (MQMD).
MQ functions use the value in this column to set the Report field.
|
|
Sets the MQRO_DEAD_LETTER_Q option in the Report field in the

MQMD. This value is the default.
|
|
Sets the MQRO_DISCARD_MSG option in the Report field in the

MQMD.
|
|
Sets the MQRO_PASS_DISCARD_AND_EXPIRY option in the Report

field in the MQMD.
|
|
|
SEND_REPORT_EXCEPTION
This column specifies whether an exception report message is to be generated

when a message cannot be delivered to the specified destination queue and if so,
what that report message should contain.
|
|
|
|
Specifies that an exception report message is not to be generated. No

options in the Report field are set. This value is the default.
Sets the MQRO_EXCEPTION option in the Report field in the MQMD.
|
|
Sets the MQRO_EXCEPTION_WITH_DATA option in the Report field in

the MQMD.
|
|
Sets the MQRO_EXCEPTION_WITH_FULL_DATA option in the Report

field in the MQMD.
SQL programming
455
Column name
Description
|
|
|
SEND_REPORT_COA
This column specifies whether the queue manager is to send a confirm-on-arrival

(COA) report message when the message is placed in the destination queue, and
if so, what that COA message is to contain.
|
|
|
|
Specifies that a COA message is not to be sent. No options in the Report

field are set. This value is the default
Sets the MQRO_COA option in the Report field in the MQMD
|
|
Sets the MQRO_COA_WITH_DATA option in the Report field in the

MQMD.
|
|
Sets the MQRO_COA_WITH_FULL_DATA option in the Report field in

the MQMD.
|
|
|
|
SEND_REPORT_COD
This column specifies whether the queue manager is to send a

confirm-on-delivery (COD) report message when an application retrieves and
deletes a message from the destination queue, and if so, what that COD message
is to contain.
|
|
|
|
Specifies that a COD message is not to be sent. No options in the Report

field are set. This value is the default.
Sets the MQRO_COD option in the Report field in the MQMD.
|
|
Sets the MQRO_COD_WITH_DATA option in the Report field in the

MQMD.
|
|
Sets the MQRO_COD_WITH_FULL_DATA option in the Report field in

the MQMD.
|
|
|
SEND_REPORT_EXPIRY
This column specifies whether the queue manager is to send an expiration report
message if a message is discarded before it is delivered to an application, and if
so, what that message is to contain.
|
|
|
|
Specifies that an expiration report message is not to be sent. No options

in the Report field are set. This value is the default.
Sets the MQRO_EXPIRATION option in the Report field in the MQMD.
|
|
Sets the MQRO_EXPIRATION_WITH_DATA option in the Report field in

the MQMD.
|
|
Sets the MQRO_EXPIRATION_WITH_FULL_DATA option in the Report

field in the MQMD.
456
Column name
Description
|
|
SEND_REPORT_ACTION
This column specifies whether the receiving application sends a positive action
notification (PAN), a negative action notification (NAN), or both.
|
|
|
|
Specifies that neither notification is to be sent. No options in the Report

field are set. This value is the default.
Sets the MQRO_PAN option in the Report field in the MQMD.
Sets the MQRO_NAN option in the Report field in the MQMD.
|
|
Sets both the MQRO_PAN and MQRO_NAN options in the Report field
in the MQMD.
SEND_MSG_TYPE
This column contains the type of message.
|
|
This column corresponds to the MsgType field in the message descriptor

(MQMD). MQ functions use the value in this column to set the MsgType field.
|
|
DTG
Sets the MsgType field in the MQMD to MQMT_DATAGRAM. This

value is the default.
REQ
Sets the MsgType field in the MQMD to MQMT_REQUEST.
RLY
Sets the MsgType field in the MQMD to MQMT_REPLY.
RPT
Sets the MsgType field in the MQMD to MQMT_REPORT.
|
|
REPLY_TO_Q
This column contains the name of the message queue to which the application
that issued the MQGET call is to send reply and report messages.
|
|
This column corresponds to the ReplyToQ field in the message descriptor

(MQMD). MQ functions use the value in this column to set the ReplyToQ field.
|
|
|
|
The default value for this column is SAME AS INPUT_Q, which sets the name to
the queue name that is defined in the service that was used for sending the
message. If no service was specified, the name is set to the name of the queue
manager for the default service.
|
|
REPLY_TO_QMGR
This column contains the name of the queue manager to which the reply and
report messages are to be sent.
|
|
|
This column corresponds to the ReplyToQMgr field in the message descriptor

(MQMD). MQ functions use the value in this column to set the ReplyToQMgr
field.
|
|
|
|
The default value for this column is SAME AS INPUT_QMGR, which sets the
name to the queue manager name that is defined in the service that was used for
sending the message. If no service was specified, the name is set to the name of
the queue manager for the default service.
|
|
RCV_WAIT_INTERVAL
This column contains the time, in milliseconds, that DB2 is to wait for messages
to arrive in the queue.
|
|
|
This column corresponds to the WaitInterval field in the get message options
(MQGMO). MQ functions use the value in this column to set the WaitInterval
field.
The default is 10.
SQL programming
457
Column name
Description
|
|
|
RCV_CONVERT
This column indicates whether to convert the application data in the message to
conform to the CodedCharSetId and Encoding values that are defined in the
service used for the function.
|
|
This column corresponds to the Options field in the get message options
(MQGMO). MQ functions use the value in this column to set the Options field.
|
|
Sets the MQGMO_CONVERT option in the Options field in the

MQGMO. This value is the default.
Specifies that no data is to be converted.
|
|
RCV_ACCEPT_TRUNC_MSG
This column specifies the behavior of the MQ function when oversized messages
are retrieved.
|
|
This column corresponds to the Options field in the get message options
(MQGMO). MQ functions use the value in this column to set the Options field.
|
|
Sets the MQGMO_ACCEPT_TRUNCATED_MSG option in the Options

field in the MQGMO. This value is the default.
|
|
Specifies that no messages are to be truncated. If the message is too large

to fit in the buffer, the MQ function terminates with an error.
|
|
|
Recommendation: Set this column to Y. In this case, if the message buffer is too
small to hold the complete message, the MQ function can fill the buffer with as
much of the message as the buffer can hold.
REV_OPEN_SHARED
This column specifies the input queue mode when messages are retrieved.
|
|
This column corresponds to the Options parameter for an MQOPEN call. MQ

functions use the value in this column to set the Options parameter.
Sets the MQOO_INPUT_SHARED option. This value is the default.
Sets the MQ option MQOO_INPUT_EXCLUSIVE option.
Sets the MQ option MQOO_INPUT_AS_Q_DEF option.
|
|
SYNCPOINT
This column indicates whether the MQ function is to operate within the protocol
for a normal unit of work.
|
|
|
Specifies that the MQ function is to operate within the protocol for a

normal unit of work. Use this value if you want the MQ function to run
under a transaction. This value is the default.
|
|
|
Specifies that the MQ function is to operate outside the protocol for a

normal unit of work. Use this value if you do not want the MQ function
to run under a transaction.
|
|
DESCRIPTION
DB2 MQ CCSID conversion
This column contains the long description of the policy.
| When a message is sent, the message sent may be converted to the job CCSID by DB2. When a message
| is read or received, it may be converted to a specified CCSID by Websphere MQ.
458
|
|
|
|
|
The msg-data parameter on the MQSEND function is defined to be in the job CCSID. If a string is passed
for msg-data, it will be converted to the job CCSID. For example, if a string is passed for msg-data that has
a CCSID 1200, it will be converted to the job CCSID before the message data is passed to Websphere MQ.
If the string is defined to be bit data or the CCSID of the string is the job CCSID, no conversion will
occur.
|
|
|
|
|
|
|
|
Websphere MQ does not perform CCSID conversions of the message data when MQSEND is executed.
The message data passed from DB2 will be sent unchanged along with a CCSID which will inform the
receiver of the message how to interpret the message data. The CCSID that is sent depends on the value
specified for the CODEDCHARSETID of the service used on the MQSEND function. The default for
CODEDCHARSETID is -3 which indicates that the CCSID passed will be the job default CCSID. If a
value other then -3 is used for CODEDCHARSETID, the invoker must ensure that the message data
passed to MQSEND will not get converted to the job CCSID by DB2 and that the string is encoded in
that specified CCSID.
|
|
|
|
|
When a message is read or received by a DB2 MQ scalar or table function, the msg-data return parameter
(and the MSG result column for the DB2 MQ table functions) are also defined be in job default CCSID.
DB2 does no conversions and relies on Websphere MQ to perform any necessary conversions. Whether
Websphere will convert the message data can be controlled by setting the RCV_CONVERT value to 'N' in
the specified policy.
|
|
|
|
|
|
If the specified service has a value for CODEDCHARSETID of -3, DB2 will instruct Websphere MQ to
convert any message read or received into the job CCSID. If a value other then -3 is used for
CODEDCHARSETID, DB2 will instruct Websphere MQ to convert any message read or received into that
CCSID. Specifying something other than -3 for CODEDCHARSETID in a service used to read or receive
messages is not recommended since the msg-data return parameter and MSG result column are defined by
DB2 to be in job default CCSID.
|
|
|
When reading or receiving a message, truncation may occur. If the specified policy has a value for
RCV_ACCEPT_TRUNC_MSG of 'Y', the message may be truncated without any warning. If the value for
RCV_ACCEPT_TRUNC_MSG is 'N' and the message is too long, the function ends with an error.
Websphere MQ transactions
|
|
|
Websphere MQ can send and receive messages as part of a transaction or outside a transaction. If a
message is sent or received as part of a transaction, the transaction can include other resource such as
DB2 operations.
|
|
|
Websphere MQ can serve as the transaction manager itself or participate as a resource manager to other
transaction managers (such as CICS, Encina, and Tuxedo). Detailed information on transactions and
supported external transaction managers can be found in the Websphere MQSeries Information Center.
|
|
|
|
|
|
|
|
|
|
Websphere can also participate in transactions managed by IBM i commitment control. Commitment
control is automatically started by DB2 when an SQL statement is executed and it is determined that
commitment control is not yet started. By default, the commitment definition scope is *ACTGRP. In order
for MQ functions and DB2 operations that occur in the same job to participate in the same transaction
managed by IBM i commitment control, commitment control must be started with a scope of *JOB. For
example, the following two CL commands end the current commitment definition and starts one with a
scope of *JOB:
|
|
|
|
In order to start commitment control with a scope of *JOB in a server job, the end and start commitment
control CL commands must be performed together in a procedure. The following steps will create a
sample procedure called START_JOB_LEVEL_COMMIT which can then be called with an SQL CALL
statement :
ENDCMTCTL
STRCMTCTL LCKLVL(*CHG) CMTSCOPE(*JOB)
SQL programming
459
| 1. Enter the following source in a source file member JOBSCOPE in MJASRC/CL:

|
PGM
|
ENDCMTCTL
|
STRCMTCTL LCKLVL(*CHG) CMTSCOPE(*JOB)
|
ENDPGM
|
| 2. Create the CL program using the following default MQ message queue manager:
|
CRTCLPGM PGM(MJATST/JOBSCOPE) SRCFILE(MJASRC/CL)
|
| 3. Create the SQL external procedure that references the CL program:
|
CREATE PROCEDURE MJATST.START_JOB_LEVEL_COMMIT ()
|
EXTERNAL NAME MJATST/JOBSCOPE
|
PARAMETER STYLE GENERAL
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The procedure can typically be called once in a job. Once the commitment definition with a *JOB scope is
started, MQ operations and DB2 operations can be performed as part of a transaction. For example, the
following INSERT statement and the MQSEND function will be performed under the same transaction. If
the transaction is committed, both operations are committed. If the transaction is rolled back, both
operations are rolled back.
|
|
|
|
|
Websphere MQ can send and receive messages as part of a transaction or outside a transaction. In a DB2
MQ function this is controlled by the specified policy. Each policy has a SYNCPOINT attribute. If the
SYNCPOINT column for a policy has a value of 'N', any DB2 MQ function that uses that policy will not
participate in a transaction. If the SYNCPOINT column for a policy has a value of 'Y', any DB2 MQ
function that uses that policy and changes the input queue will participate in a transaction.
Basic messaging with WebSphere MQ
CALL MJATST.START_JOB_LEVEL_COMMIT;
INSERT INTO MJATST.T1
VALUES(1);
VALUES MQSEND(A commit test message);
COMMMIT;
INSERT INTO MJATST.T1
VALUES(2);
VALUES MQSEND(A rollback test message);
ROLLBACK;
| The most basic form of messaging with the DB2 MQ functions occurs when all database applications
| connect to the same DB2 database server. Clients can be local to the database server or distributed in a
| network environment.
|
|
|
|
|
In a simple scenario, client A invokes the MQSEND function to send a user-defined string to the location
that is defined by the default service. DB2 executes the MQ functions that perform this operation on the
database server. At some later time, client B invokes the MQRECEIVE function to remove the message at
the head of the queue that is defined by the default service, and return it to the client. DB2 executes the
MQ functions that perform this operation on the database server.
| Database clients can use simple messaging in a number of ways:

| v Data collection
|
|
|
| v
Information is received in the form of messages from one or more sources. An information source can
be any application. The data is received from queues and stored in database tables for additional
processing.
Workload distribution
460
|
|
|
|
|
|
|
|
|
Work requests are posted to a queue that is shared by multiple instances of the same application.
When an application instance is ready to perform some work, it receives a message that contains a
work request from the head of the queue. Multiple instances of the application can share the workload
that is represented by a single queue of pooled requests.
v Application signaling
In a situation where several processes collaborate, messages are often used to coordinate their efforts.
These messages might contain commands or requests for work that is to be performed. For more
information about this technique, see Application to application connectivity with WebSphere MQ on
page 463.
|
|
|
|
The following scenario extends basic messaging to incorporate remote messaging. Assume that machine
A sends a message to machine B.
1. The DB2 client executes an MQSEND function call, specifying a target service that has been defined to
be a remote queue on machine B.
|
|
|
|
|
2. The MQ functions perform the work to send the message. The WebSphere MQ server on machine A
accepts the message and guarantees that it will deliver it to the destination that is defined by the
service and the current MQ configuration of machine A. The server determines that the destination is
a queue on machine B. The server then attempts to deliver the message to the WebSphere MQ server
on machine B, retrying as needed.
|
|
3. The WebSphere MQ server on machine B accepts the message from the server on machine A and
places it in the destination queue on machine B.
4. A WebSphere MQ client on machine B requests the message at the head of the queue.
|
|
|
|
|
|
|
|
|
If an error is returned from an MQI API, the specified DB2 MQ function will return an error. The error
will contain the name of the MQ API that failed and the MQ condition code and MQ reason code. To
determine the cause of the failure it is necessary to refer to the Websphere MQSeries Information Center.
For example, if a service contains the name of an MQSeries queue manager that does not exist, the
following error is returned:
|
|
The message indicates that the MQCONN API failed for reason code 2058. The Websphere MQSeries
Information Center contains the detailed description of reason code 2058.
Sending messages with WebSphere MQ
|
|
|
When you send messages with WebSphere MQ, you choose what data to send, where to send it and
when to send it. This type of messaging is called send and forget; the sender sends a message and relies
on WebSphere MQ to ensure that the message reaches its destination.
|
|
|
|
To send messages with WebSphere MQ, use MQSEND. If you send more than one column of information,
separate the columns with a blank character. For example:
|
|
|
|
|
|
The following example uses the default service DB2.DEFAULT.SERVICE and the default policy
DB2.DEFAULT.POLICY which has a SYNCPOINT value of 'Y'. Because this MQSEND function runs
under a transaction, the COMMIT statement ensures that the message is added to the queue.
SQL State: 38401

Vendor Code: -443
Message: [SQL0443] cc=2:rc=2058:MQCONN FAILED
VALUES MQSEND(LASTNAME CONCAT CONCAT FIRSTNAME);
VALUES MQSEND(Testing msg);

COMMIT;
SQL programming
461
| When you use a policy that contains a SYNCPOINT value of 'N', you do not need to use a COMMIT
| statement. For example, assume that policy MYPOLICY2 has a SYNCPOINT value of 'N'. The following
| SQL statement causes the message to be added to the queue without the need for a COMMIT statement.
|
VALUES MQSEND(DB2.DEFAULT.SERVICE, MYPOLICY2, Testing msg)
|
|
|
|
|
|
|
|
|
|
Message content can be any combination of SQL statements, expressions, functions, and user-specified
data. Assume that you have an EMPLOYEE table, with VARCHAR columns LASTNAME, FIRSTNAME,
and DEPARTMENT. To send a message that contains this information for each employee in
DEPARTMENT 5LGA, issue the following SQL SELECT statement:
Retrieving messages with WebSphere MQ
SELECT MQSEND(LASTNAME CONCAT CONCAT FIRSTNAME CONCAT CONCAT DEPARTMENT)

FROM EMPLOYEE
WHERE DEPARTMENT = 51GA;
COMMIT;
| With WebSphere MQ, programs can read or receive messages. Both reading and receiving operations
| return the message at the head of the queue. However, the reading operation does not remove the
| message from the queue, whereas the receiving operation does.
| A message that is retrieved using a receive operation can be retrieved only once, whereas a message that
| is retrieved using a read operation allows the same message to be retrieved many times.
|
|
|
|
|
|
The following SQL statement reads the message at the head of the queue that is specified by the default
service and policy. The SQL statement returns a VARCHAR(32000) string. If no messages are available to
be read, a null value is returned. Because MQREAD does not change the queue, you do not need to use a
COMMIT statement.
|
|
|
|
|
|
|
|
The following SQL statement causes the contents of a queue to be returned as a result set. The result
table T of the table function consists of all the messages in the queue, which is defined by the default
service, and the metadata about those messages. The first column of the materialized result table is the
message itself, and the remaining columns contain the metadata. The SELECT statement returns both the
messages and the metadata.
VALUES MQREAD()
SELECT T.*
FROM TABLE ( MQREADALL() ) AS T;
| The following statement only returns the messages. The result table T of the table function consists of all
| the messages in the queue, which is defined by the default service, and the metadata about those
| messages.
|
SELECT T.MSG
|
FROM TABLE ( MQREADALL() ) AS T;
|
|
|
|
|
|
|
|
The following SQL statement receives (removes) the message at the head of the queue. The SELECT
statement returns a VARCHAR(32000) string. Because this MQRECEIVE function runs under a
transaction, the COMMIT statement ensures that the message is removed from the queue. If no messages
are available to be retrieved, a null value is returned, and the queue does not change.
VALUES MQRECEIVE()
COMMIT;
462
|
|
|
|
|
|
|
Assume that you have a MESSAGES table with a single VARCHAR(32000) column. The following SQL
INSERT statement inserts all of the messages from the default service queue into the MESSAGES table:
Application to application connectivity with WebSphere MQ
|
|
|
Application-to-application connectivity is typically used when putting together a diverse set of

application subsystems. To facilitate application integration, WebSphere MQ provides the means to
interconnect applications.
|
|
|
|
|
The request-and-reply communication method enables one application to request the services of another
application. One way to do this is for the requester to send a message to the service provider to request
that some work be performed. When the work has been completed, the provider might decide to send
results, or just a confirmation of completion, back to the requester. Unless the requester waits for a reply
before continuing, WebSphere MQ must provide a way to associate the reply with its request.
|
|
|
|
|
WebSphere MQ provides a correlation identifier to correlate messages in an exchange between a requester

and a provider. The requester marks a message with a known correlation identifier. The provider marks
its reply with the same correlation identifier. To retrieve the associated reply, the requester provides that
correlation identifier when receiving messages from the queue. The first message with a matching
correlation identifier is returned to the requester.
|
|
|
|
|
|
The following SQL SELECT statement sends a message consisting of the string "Msg with corr id" to the
service MYSERVICE, using the policy MYPOLICY with correlation identifier CORRID1. Because the
policy MYPOLICY has the SYNCPOINT attribute of 'N', WebSphere MQ adds the message to the queue,
and you do not need to use a COMMIT statement.
|
|
|
|
|
|
The following SQL statement receives the first message that matches the identifier CORRID1 from the
queue that is specified by the service MYSERVICE, using the policy MYPOLICY. The SQL statement
returns a VARCHAR(32000) string. If no messages are available with this correlation identifier, a null
value is returned, and the queue does not change.
INSERT INTO MESSAGES

SELECT T.MSG
FROM TABLE ( MQRECEIVEALL() ) AS T;
COMMIT;
VALUES MQSEND(MYSERVICE, MYPOLICY, Msg with corr id, CORRID1)
VALUES MQRECEIVE(MYSERVICE, MYPOLICY, CORRID1)
Reference
Reference information for SQL programming includes sample tables and CL commands.
DB2 for i sample tables

collections.
Along with the tables are the SQL statements for creating the tables.
As a group, the tables include information that describes employees, departments, projects, and activities.
This information forms a sample application that demonstrates some of the features of the IBM DB2
Query Manager and SQL Development Kit for i licensed program. All examples assume that the tables
are in a schema named CORPDATA (for corporate data).
SQL programming
463
A stored procedure is included as part of the system that contains the data definition language (DDL)
statements to create all of these tables and the INSERT statements to populate them. The procedure
creates the schema specified on the call to the procedure. Because this is an external stored procedure, it
can be called from any SQL interface, including interactive SQL and System i Navigator. To call the
procedure where SAMPLE is the schema that you want to create, issue the following statement:
CALL QSYS.CREATE_SQL_SAMPLE (SAMPLE)
The schema name must be specified in uppercase. The schema must not already exist.
Note: In these sample tables, a question mark (?) indicates a null value.
Related reference:
Referential integrity and tables on page 18
Referential integrity is the condition of a set of tables in a database in which all references from one table
to another are valid.
Multiple-row FETCH using a row storage area on page 392
Before using a multiple-row FETCH statement with the row storage area, the application must define a
row storage area and an associated description area.
Department table (DEPARTMENT)

The department table describes each department in the enterprise and identifies its manager and the
department that it reports to.
The department table is created with the following CREATE TABLE and ALTER TABLE statements:
CREATE TABLE DEPARTMENT
(DEPTNO
CHAR(3)
DEPTNAME VARCHAR(36)
MGRNO
CHAR(6)
ADMRDEPT CHAR(3)
LOCATION CHAR(16),
PRIMARY KEY (DEPTNO))
NOT NULL,
NOT NULL,
,
NOT NULL,
ALTER TABLE DEPARTMENT

ADD FOREIGN KEY ROD (ADMRDEPT)
REFERENCES DEPARTMENT
ON DELETE CASCADE
The following foreign key is added later.

ALTER TABLE DEPARTMENT
ADD FOREIGN KEY RDE (MGRNO)
REFERENCES EMPLOYEE
ON DELETE SET NULL
The following indexes are created.

CREATE UNIQUE INDEX XDEPT1
ON DEPARTMENT (DEPTNO)
CREATE INDEX XDEPT2
ON DEPARTMENT (MGRNO)
CREATE INDEX XDEPT3
ON DEPARTMENT (ADMRDEPT)
The following alias is created for the table.

CREATE ALIAS DEPT FOR DEPARTMENT
The following table shows the content of the columns.
464
Table 106. Columns of the department table

Column name
Description
DEPTNO
Department number or ID.
DEPTNAME
A name describing the general activities of the department.
MGRNO
Employee number (EMPNO) of the department manager.
ADMRDEPT
The department (DEPTNO) to which this department reports; the department at the
highest level reports to itself.
LOCATION
Location of the department.
DEPARTMENT:
Here is a complete listing of the data in the DEPARTMENT table.
DEPTNO
DEPTNAME
A00
MGRNO
ADMRDEPT
LOCATION
SPIFFY COMPUTER SERVICE DIV. 000010
A00
B01
PLANNING
000020
A00
C01
INFORMATION CENTER
000030
A00
D01
DEVELOPMENT CENTER
A00
D11
000060
D01
D21
000070
D01
E01
SUPPORT SERVICES
000050
A00
E11
OPERATIONS
000090
E01
E21
SOFTWARE SUPPORT
000100
E01
F22
BRANCH OFFICE F2
E01
G22
BRANCH OFFICE G2
E01
H22
BRANCH OFFICE H2
E01
I22
BRANCH OFFICE I2
E01
J22
BRANCH OFFICE J2
E01
Employee table (EMPLOYEE)

The employee table identifies every employee by an employee number and lists basic personnel
information.
The employee table is created with the following CREATE TABLE and ALTER TABLE statements:
CREATE TABLE EMPLOYEE
(EMPNO
CHAR(6)
FIRSTNME
VARCHAR(12)
MIDINIT
CHAR(1)
LASTNAME
VARCHAR(15)
WORKDEPT
CHAR(3)
PHONENO
CHAR(4)
HIREDATE
DATE
JOB
CHAR(8)
EDLEVEL
SMALLINT
SEX
CHAR(1)
BIRTHDATE DATE
SALARY
DECIMAL(9,2)
BONUS
DECIMAL(9,2)
COMM
DECIMAL(9,2)
PRIMARY KEY (EMPNO))
NOT
NOT
NOT
NOT
NULL,
NULL,
NULL,
NULL,
,
,
,
,
NOT NULL,
,
,
,
,
SQL programming
465
ALTER TABLE EMPLOYEE

ADD FOREIGN KEY RED (WORKDEPT)
ON DELETE SET NULL
ALTER TABLE EMPLOYEE
ADD CONSTRAINT NUMBER
CHECK (PHONENO >= 0000 AND PHONENO <= 9999)
The following indexes are created:

CREATE UNIQUE INDEX XEMP1
ON EMPLOYEE (EMPNO)
CREATE INDEX XEMP2
ON EMPLOYEE (WORKDEPT)
The following alias is created for the table:

CREATE ALIAS EMP FOR EMPLOYEE
The table below shows the content of the columns.

Column name
Description
EMPNO
Employee number
FIRSTNME
First name of employee
MIDINIT
Middle initial of employee
LASTNAME
Family name of employee
WORKDEPT
ID of department in which the employee works
PHONENO
Employee telephone number
HIREDATE
Date of hire
JOB
Job held by the employee
EDLEVEL
Number of years of formal education
SEX
Sex of the employee (M or F)
BIRTHDATE
Date of birth
SALARY
Yearly salary in dollars
BONUS
Yearly bonus in dollars
COMM
Yearly commission in dollars
EMPLOYEE:
Here is a complete listing of the data in the EMPLOYEE table.
466
EMP NO
000010
000020
000030
000050
000060
000070
000090
000100
000110
000120
000130
000140
000150
000160
000170
000180
000190
000200
000210
000220
000230
000240
000250
000260
000270
000280
000290
000300
000310
000320
000330
000340
200010
200120
200140
200170
200220
200240
200280
200310
200330
200340
FIRST
NAME
CHRISTINE
MICHAEL
SALLY
JOHN
IRVING
EVA
EILEEN
THEODORE
VINCENZO
SEAN
DOLORES
HEATHER
BRUCE
ELIZABETH
MASATOSHI
MARILYN
JAMES
DAVID
WILLIAM
JENNIFER
JAMES
SALVATORE
DANIEL
SYBIL
MARIA
ETHEL
JOHN
PHILIP
MAUDE
RAMLAL
WING
JASON
DIAN
GREG
KIM
KIYOSHI
REBA
ROBERT
EILEEN
MICHELLE
HELENA
ROY
MID
INIT
I
L
A
B
F
D
W
Q
G
M
A
R
J
S
H
T
K
J
M
S
P
L
R
R
X
F
V
R
J
N
K
M
R
F
R
LASTNAME
HAAS
THOMPSON
KWAN
GEYER
STERN
PULASKI
HENDERSON
SPENSER
LUCCHESSI
OCONNELL
QUINTANA
NICHOLLS
ADAMSON
PIANKA
YOSHIMURA
SCOUTTEN
WALKER
BROWN
JONES
LUTZ
JEFFERSON
MARINO
SMITH
JOHNSON
PEREZ
SCHNEIDER
PARKER
SMITH
SETRIGHT
MEHTA
LEE
GOUNOT
HEMMINGER
ORLANDO
NATZ
YAMAMOTO
JOHN
MONTEVERDE
SCHWARTZ
SPRINGER
WONG
ALONZO
WORK
DEPT
A00
B01
C01
E01
D11
D21
E11
E21
A00
A00
C01
C01
D11
D11
D11
D11
D11
D11
D11
D11
D21
D21
D21
D21
D21
E11
E11
E11
E11
E21
E21
E21
A00
A00
C01
D11
D11
D21
E11
E11
E21
E21
PHONE
NO
3978
3476
4738
6789
6423
7831
5498
0972
3490
2167
4578
1793
4510
3782
2890
1682
2986
4501
0942
0672
2094
3780
0961
8953
9001
8997
4502
2095
3332
9990
2103
5698
3978
2167
1793
2890
0672
3780
8997
3332
2103
5698
HIRE DATE
1965-01-01
1973-10-10
1975-04-05
1949-08-17
1973-09-14
1980-09-30
1970-08-15
1980-06-19
1958-05-16
1963-12-05
1971-07-28
1976-12-15
1972-02-12
1977-10-11
1978-09-15
1973-07-07
1974-07-26
1966-03-03
1979-04-11
1968-08-29
1966-11-21
1979-12-05
1969-10-30
1975-09-11
1980-09-30
1967-03-24
1980-05-30
1972-06-19
1964-09-12
1965-07-07
1976-02-23
1947-05-05
1965-01-01
1972-05-05
1976-12-15
1978-09-15
1968-08-29
1979-12-05
1967-03-24
1964-09-12
1976-02-23
1947-05-05
JOB
PRES
MANAGER
MANAGER
MANAGER
MANAGER
MANAGER
MANAGER
MANAGER
SALESREP
CLERK
ANALYST
ANALYST
DESIGNER
DESIGNER
DESIGNER
DESIGNER
DESIGNER
DESIGNER
DESIGNER
DESIGNER
CLERK
CLERK
CLERK
CLERK
CLERK
OPERATOR
OPERATOR
OPERATOR
OPERATOR
FILEREP
FILEREP
FILEREP
SALESREP
CLERK
ANALYST
DESIGNER
DESIGNER
CLERK
OPERATOR
OPERATOR
FIELDREP
FIELDREP
ED
LEVEL
18
18
20
16
16
16
16
14
19
14
16
18
16
17
16
17
16
16
17
18
14
17
15
16
15
17
12
14
12
16
14
16
18
14
18
16
18
17
17
12
14
16
SEX
F
M
F
M
M
F
F
M
M
M
F
F
M
F
M
F
M
M
M
F
M
M
M
F
F
F
M
M
F
M
M
M
F
M
F
M
F
M
F
F
F
M
BIRTH DATE
1933-08-24
1948-02-02
1941-05-11
1925-09-15
1945-07-07
1953-05-26
1941-05-15
1956-12-18
1929-11-05
1942-10-18
1925-09-15
1946-01-19
1947-05-17
1955-04-12
1951-01-05
1949-02-21
1952-06-25
1941-05-29
1953-02-23
1948-03-19
1935-05-30
1954-03-31
1939-11-12
1936-10-05
1953-05-26
1936-03-28
1946-07-09
1936-10-27
1931-04-21
1932-08-11
1941-07-18
1926-05-17
1933-08-14
1942-10-18
1946-01-19
1951-01-05
1948-03-19
1954-03-31
1936-03-28
1931-04-21
1941-07-18
1926-05-17
SALARY
BONUS
52750 1000
41250 800
38250 800
40175 800
32250 500
36170 700
29750 600
26150 500
46500 900
29250 600
23800 500
28420 600
25280 500
22250 400
24680 500
21340 500
20450 400
27740 600
18270 400
29840 600
22180 400
28760 600
19180 400
17250 300
27380 500
26250 500
15340 300
17750 400
15900 300
19950 400
25370 500
23840 500
46500 1000
29250 600
28420 600
24680 500
29840 600
28760 600
26250 500
15900 300
25370 500
23840 500
COMM
4220
3300
3060
3214
2580
2893
2380
2092
3720
2340
1904
2274
2022
1780
1974
1707
1636
2217
1462
2387
1774
2301
1534
1380
2190
2100
1227
1420
1272
1596
2030
1907
4220
2340
2274
1974
2387
2301
2100
1272
2030
1907
Employee photo table (EMP_PHOTO)

The employee photo table contains a photo of each employee identified by an employee number.
The employee photo table is created with the following CREATE TABLE and ALTER TABLE statements:
CREATE TABLE EMP_PHOTO
(EMPNO CHAR(6) NOT NULL,
PHOTO_FORMAT VARCHAR(10) NOT NULL,
PICTURE BLOB(100K),
EMP_ROWID CHAR(40) NOT NULL DEFAULT ,
PRIMARY KEY (EMPNO,PHOTO_FORMAT))
ALTER TABLE EMP_PHOTO
ADD COLUMN DL_PICTURE DATALINK(1000)
LINKTYPE URL NO LINK CONTROL
ALTER TABLE EMP_PHOTO
ADD FOREIGN KEY (EMPNO)
REFERENCES EMPLOYEE
ON DELETE RESTRICT
The following index is created:

CREATE UNIQUE INDEX XEMP_PHOTO
ON EMP_PHOTO (EMPNO,PHOTO_FORMAT)
SQL programming
467
Column name
Description
EMPNO
Employee number
PHOTO_FORMAT
Format of image stored in PICTURE
PICTURE
Photo image
EMP_ROWID
Unique row ID, not currently used
EMP_PHOTO:
Here is a complete listing of the data in the EMP_PHOTO table.
EMPNO
PHOTO_FORMAT
PICTURE
000130
bitmap
000130
gif
000140
bitmap
000140
gif
000150
bitmap
000150
gif
000190
bitmap
000190
gif
EMP_ROWID
Employee resum table (EMP_RESUME)

The employee resum table contains a resum for each employee identified by an employee number.
The employee resum table is created with the following CREATE TABLE and ALTER TABLE statements:
CREATE TABLE EMP_RESUME
(EMPNO CHAR(6) NOT NULL,
RESUME_FORMAT VARCHAR(10) NOT NULL,
RESUME CLOB(5K),
EMP_ROWID CHAR(40) NOT NULL DEFAULT ,
PRIMARY KEY (EMPNO,RESUME_FORMAT))
ALTER TABLE EMP_RESUME
ADD COLUMN DL_RESUME DATALINK(1000)
LINKTYPE URL NO LINK CONTROL
ALTER TABLE EMP_RESUME
ADD FOREIGN KEY (EMPNO)
REFERENCES EMPLOYEE
ON DELETE RESTRICT

CREATE UNIQUE INDEX XEMP_RESUME
ON EMP_RESUME (EMPNO,RESUME_FORMAT)

Column name
Description
EMPNO
Employee number
RESUME_FORMAT
Format of text stored in RESUME
RESUME
Resum
EMP_ROWID
Unique row id, not currently used
468
EMP_RESUME:
Here is a complete listing of the data in the EMP_RESUME table.
EMPNO
RESUME_FORMAT
RESUME
000130
ascii
000130
html
000140
ascii
000140
html
000150
ascii
000150
html
000190
ascii
000190
html
EMP_ROWID
Employee to project activity table (EMPPROJACT)

The employee to project activity table identifies the employee who participates in each activity listed for
each project. The employee's level of involvement (full-time or part-time) and the activity schedule are
also included in the table.
The employee to project activity table is created with the following CREATE TABLE and ALTER TABLE
statements:
CREATE TABLE EMPPROJACT
(EMPNO
CHAR(6)
PROJNO
CHAR(6)
ACTNO
SMALLINT
EMPTIME DECIMAL(5,2)
EMSTDATE DATE
EMENDATE DATE
NOT NULL,
NOT NULL,
NOT NULL,
,
,
)
ALTER TABLE EMPPROJACT

ADD FOREIGN KEY REPAPA (PROJNO, ACTNO, EMSTDATE)
REFERENCES PROJACT
ON DELETE RESTRICT
The following aliases are created for the table:

CREATE ALIAS EMPACT FOR EMPPROJACT
CREATE ALIAS EMP_ACT FOR EMPPROJACT

Table 107. Columns of the Employee to project activity table
Column name
Description
EMPNO
Employee ID number
PROJNO
PROJNO of the project to which the employee is assigned
ACTNO
ID of an activity within a project to which an employee is assigned
EMPTIME
A proportion of the employee's full time (between 0.00 and 1.00) to be spent on
the project from EMSTDATE to EMENDATE
EMSTDATE
Start date of the activity
EMENDATE
Completion date of the activity
SQL programming
469
EMPPROJACT:
Here is a complete listing of the data in the EMPPROJACT table.
EMPNO
PROJNO
ACTNO
EMPTIME
EMSTDATE
EMENDATE
000010
AD3100
10
.50
1982-01-01
1982-07-01
000070
AD3110
10
1.00
1982-01-01
1983-02-01
000230
AD3111
60
1.00
1982-01-01
1982-03-15
000230
AD3111
60
.50
1982-03-15
1982-04-15
000230
AD3111
70
.50
1982-03-15
1982-10-15
000230
AD3111
80
.50
1982-04-15
1982-10-15
000230
AD3111
180
.50
1982-10-15
1983-01-01
000240
AD3111
70
1.00
1982-02-15
1982-09-15
000240
AD3111
80
1.00
1982-09-15
1983-01-01
000250
AD3112
60
1.00
1982-01-01
1982-02-01
000250
AD3112
60
.50
1982-02-01
1982-03-15
000250
AD3112
60
1.00
1983-01-01
1983-02-01
000250
AD3112
70
.50
1982-02-01
1982-03-15
000250
AD3112
70
1.00
1982-03-15
1982-08-15
000250
AD3112
70
.25
1982-08-15
1982-10-15
000250
AD3112
80
.25
1982-08-15
1982-10-15
000250
AD3112
80
.50
1982-10-15
1982-12-01
000250
AD3112
180
.50
1982-08-15
1983-01-01
000260
AD3113
70
.50
1982-06-15
1982-07-01
000260
AD3113
70
1.00
1982-07-01
1983-02-01
000260
AD3113
80
1.00
1982-01-01
1982-03-01
000260
AD3113
80
.50
1982-03-01
1982-04-15
000260
AD3113
180
.50
1982-03-01
1982-04-15
000260
AD3113
180
1.00
1982-04-15
1982-06-01
000260
AD3113
180
1.00
1982-06-01
1982-07-01
000270
AD3113
60
.50
1982-03-01
1982-04-01
000270
AD3113
60
1.00
1982-04-01
1982-09-01
000270
AD3113
60
.25
1982-09-01
1982-10-15
000270
AD3113
70
.75
1982-09-01
1982-10-15
000270
AD3113
70
1.00
1982-10-15
1983-02-01
000270
AD3113
80
1.00
1982-01-01
1982-03-01
000270
AD3113
80
.50
1982-03-01
1982-04-01
000030
IF1000
10
.50
1982-06-01
1983-01-01
000130
IF1000
90
1.00
1982-10-01
1983-01-01
000130
IF1000
100
.50
1982-10-01
1983-01-01
000140
IF1000
90
.50
1982-10-01
1983-01-01
000030
IF2000
10
.50
1982-01-01
1983-01-01
000140
IF2000
100
1.00
1982-01-01
1982-03-01
470
EMPNO
PROJNO
ACTNO
EMPTIME
EMSTDATE
EMENDATE
000140
IF2000
100
.50
1982-03-01
1982-07-01
000140
IF2000
110
.50
1982-03-01
1982-07-01
000140
IF2000
110
.50
1982-10-01
1983-01-01
000010
MA2100
10
.50
1982-01-01
1982-11-01
000110
MA2100
20
1.00
1982-01-01
1983-03-01
000010
MA2110
10
1.00
1982-01-01
1983-02-01
000200
MA2111
50
1.00
1982-01-01
1982-06-15
000200
MA2111
60
1.00
1982-06-15
1983-02-01
000220
MA2111
40
1.00
1982-01-01
1983-02-01
000150
MA2112
60
1.00
1982-01-01
1982-07-15
000150
MA2112
180
1.00
1982-07-15
1983-02-01
000170
MA2112
60
1.00
1982-01-01
1983-06-01
000170
MA2112
70
1.00
1982-06-01
1983-02-01
000190
MA2112
70
1.00
1982-01-01
1982-10-01
000190
MA2112
80
1.00
1982-10-01
1983-10-01
000160
MA2113
60
1.00
1982-07-15
1983-02-01
000170
MA2113
80
1.00
1982-01-01
1983-02-01
000180
MA2113
70
1.00
1982-04-01
1982-06-15
000210
MA2113
80
.50
1982-10-01
1983-02-01
000210
MA2113
180
.50
1982-10-01
1983-02-01
000050
OP1000
10
.25
1982-01-01
1983-02-01
000090
OP1010
10
1.00
1982-01-01
1983-02-01
000280
OP1010
130
1.00
1982-01-01
1983-02-01
000290
OP1010
130
1.00
1982-01-01
1983-02-01
000300
OP1010
130
1.00
1982-01-01
1983-02-01
000310
OP1010
130
1.00
1982-01-01
1983-02-01
000050
OP2010
10
.75
1982-01-01
1983-02-01
000100
OP2010
10
1.00
1982-01-01
1983-02-01
000320
OP2011
140
.75
1982-01-01
1983-02-01
000320
OP2011
150
.25
1982-01-01
1983-02-01
000330
OP2012
140
.25
1982-01-01
1983-02-01
000330
OP2012
160
.75
1982-01-01
1983-02-01
000340
OP2013
140
.50
1982-01-01
1983-02-01
000340
OP2013
170
.50
1982-01-01
1983-02-01
000020
PL2100
30
1.00
1982-01-01
1982-09-15
Project table (PROJECT)

The project table describes each project that the business is currently undertaking. Data contained in each
row include the project number, name, person responsible, and schedule dates.
The project table is created with the following CREATE TABLE and ALTER TABLE statements:
SQL programming
471
CREATE TABLE PROJECT

(PROJNO
CHAR(6)
PROJNAME VARCHAR(24)
DEPTNO
CHAR(3)
RESPEMP
CHAR(6)
PRSTAFF
DECIMAL(5,2)
PRSTDATE DATE
PRENDATE DATE
MAJPROJ
CHAR(6)
PRIMARY KEY (PROJNO))
NOT
NOT
NOT
NOT
NULL,
NULL DEFAULT,
NULL,
NULL,
,
,
,
,
ALTER TABLE PROJECT

ADD FOREIGN KEY (DEPTNO)
ON DELETE RESTRICT
ALTER TABLE PROJECT
ADD FOREIGN KEY (RESPEMP)
REFERENCES EMPLOYEE
ON DELETE RESTRICT
ALTER TABLE PROJECT
ADD FOREIGN KEY RPP (MAJPROJ)
REFERENCES PROJECT
ON DELETE CASCADE

CREATE UNIQUE INDEX XPROJ1
ON PROJECT (PROJNO)
CREATE INDEX XPROJ2
ON PROJECT (RESPEMP)
The following alias is created for the table:

CREATE ALIAS PROJ FOR PROJECT
The table below shows the contents of the columns:

Column name
Description
PROJNO
Project number
PROJNAME
Project name
DEPTNO
Department number of the department responsible for the project
RESPEMP
Employee number of the person responsible for the project
PRSTAFF
Estimated mean staffing
PRSTDATE
Estimated start date of the project
PRENDATE
Estimated end date of the project
MAJPROJ
Controlling project number for sub projects
PROJECT:
Here is a complete listing of the data in the PROJECT table.
PROJNO
PROJNAME
AD3100
AD3110
472
DEPTNO
RESPEMP
PRSTAFF
PRSTDATE
PRENDATE
MAJPROJ
ADMIN SERVICES D01
000010
6.5
1982-01-01
1983-02-01
GENERAL ADMIN D21

SYSTEMS
000070
1982-01-01
1983-02-01
AD3100
PROJNO
PROJNAME
DEPTNO
RESPEMP
PRSTAFF
PRSTDATE
PRENDATE
MAJPROJ
AD3111
PAYROLL
PROGRAMMING
D21
000230
1982-01-01
1983-02-01
AD3110
AD3112
PERSONNEL
PROGRAMMING
D21
000250
1982-01-01
1983-02-01
AD3110
AD3113
ACCOUNT
PROGRAMMING
D21
000270
1982-01-01
1983-02-01
AD3110
IF1000
QUERY SERVICES
C01
000030
1982-01-01
1983-02-01
IF2000
USER
EDUCATION
C01
000030
1982-01-01
1983-02-01
MA2100
WELD LINE
AUTOMATION
D01
000010
12
1982-01-01
1983-02-01
MA2110
WL
PROGRAMMING
D11
000060
1982-01-01
1983-02-01
MA2100
MA2111
W L PROGRAM
DESIGN
D11
000220
1982-01-01
1982-12-01
MA2110
MA2112
W L ROBOT
DESIGN
D11
000150
1982-01-01
1982-12-01
MA2110
MA2113
W L PROD CONT
PROGS
D11
000160
1982-02-15
1982-12-01
MA2110
OP1000
OPERATION
SUPPORT
E01
000050
1982-01-01
1983-02-01
OP1010
OPERATION
E11
000090
1982-01-01
1983-02-01
OP1000
OP2000
GEN SYSTEMS
SERVICES
E01
000050
1982-01-01
1983-02-01
OP2010
SYSTEMS
SUPPORT
E21
000100
1982-01-01
1983-02-01
OP2000
OP2011
SCP SYSTEMS
SUPPORT
E21
000320
1982-01-01
1983-02-01
OP2010
OP2012
APPLICATIONS
SUPPORT
E21
000330
1982-01-01
1983-02-01
OP2010
OP2013
DB/DC SUPPORT
E21
000340
1982-01-01
1983-02-01
OP2010
PL2100
WELD LINE
PLANNING
B01
000020
1982-01-01
1982-09-15
MA2100
Project activity table (PROJACT)

The project activity table describes each project activity that the business is currently undertaking. Data
contained in each row includes the project number, activity number, and schedule dates.
The project activity table is created with the following CREATE TABLE and ALTER TABLE statements:
CREATE TABLE PROJACT
(PROJNO CHAR(6) NOT NULL,
ACTNO SMALLINT NOT NULL,
ACSTAFF DECIMAL(5,2),
ACSTDATE DATE NOT NULL,
ACENDATE DATE ,
PRIMARY KEY (PROJNO, ACTNO, ACSTDATE))
ALTER TABLE PROJACT
ADD FOREIGN KEY RPAP (PROJNO)
REFERENCES PROJECT
ON DELETE RESTRICT
SQL programming
473
The following foreign key is added later:

ALTER TABLE PROJACT
ADD FOREIGN KEY RPAA (ACTNO)
REFERENCES ACT
ON DELETE RESTRICT

CREATE UNIQUE INDEX XPROJAC1
ON PROJACT (PROJNO, ACTNO, ACSTDATE)
The table below shows the contents of the columns:

Column name
Description
PROJNO
Project number
ACTNO
Activity number
ACSTAFF
Estimated mean staffing
ACSTDATE
Activity start date
ACENDATE
Activity end date
PROJACT:
Here is a complete listing of the data in the PROJACT table.
PROJNO
ACTNO
ACSTAFF
ACSTDATE
ACENDATE
AD3100
10
1982-01-01
AD3110
10
1982-01-01
AD3111
60
1982-01-01
AD3111
60
1982-03-15
AD3111
70
1982-03-15
AD3111
80
1982-04-15
AD3111
180
1982-10-15
AD3111
70
1982-02-15
AD3111
80
1982-09-15
AD3112
60
1982-01-01
AD3112
60
1982-02-01
AD3112
60
1983-01-01
AD3112
70
1982-02-01
AD3112
70
1982-03-15
AD3112
70
1982-08-15
AD3112
80
1982-08-15
AD3112
80
1982-10-15
AD3112
180
1982-08-15
AD3113
70
1982-06-15
AD3113
70
1982-07-01
AD3113
80
1982-01-01
AD3113
80
1982-03-01
474
PROJNO
ACTNO
ACSTAFF
ACSTDATE
ACENDATE
AD3113
180
1982-03-01
AD3113
180
1982-04-15
AD3113
180
1982-06-01
AD3113
60
1982-03-01
AD3113
60
1982-04-01
AD3113
60
1982-09-01
AD3113
70
1982-09-01
AD3113
70
1982-10-15
IF1000
10
1982-06-01
IF1000
90
1982-10-01
IF1000
100
1982-10-01
IF2000
10
1982-01-01
IF2000
100
1982-01-01
IF2000
100
1982-03-01
IF2000
110
1982-03-01
IF2000
110
1982-10-01
MA2100
10
1982-01-01
MA2100
20
1982-01-01
MA2110
10
1982-01-01
MA2111
50
1982-01-01
MA2111
60
1982-06-15
MA2111
40
1982-01-01
MA2112
60
1982-01-01
MA2112
180
1982-07-15
MA2112
70
1982-06-01
MA2112
70
1982-01-01
MA2112
80
1982-10-01
MA2113
60
1982-07-15
MA2113
80
1982-01-01
MA2113
70
1982-04-01
MA2113
80
1982-10-01
MA2113
180
1982-10-01
OP1000
10
1982-01-01
OP1010
10
1982-01-01
OP1010
130
1982-01-01
OP2010
10
1982-01-01
OP2011
140
1982-01-01
OP2011
150
1982-01-01
OP2012
140
1982-01-01
OP2012
160
1982-01-01
OP2013
140
1982-01-01
?
SQL programming
475
PROJNO
ACTNO
ACSTAFF
ACSTDATE
ACENDATE
OP2013
170
1982-01-01
PL2100
30
1982-01-01
Activity table (ACT)

The activity table describes each activity.
The activity table is created with the following CREATE TABLE statement:
CREATE TABLE ACT
(ACTNO SMALLINT NOT NULL,
ACTKWD CHAR(6) NOT NULL,
ACTDESC VARCHAR(20) NOT NULL,
PRIMARY KEY (ACTNO))

CREATE UNIQUE INDEX XACT1
ON ACT (ACTNO)
CREATE UNIQUE INDEX XACT2
ON ACT (ACTKWD)
The table below shows the contents of the columns.

Column name
Description
ACTNO
Activity number
ACTKWD
Keyword for activity
ACTDESC
Description of activity
ACT:
Here is a complete listing of the data in the ACT table.
ACTNO
ACTKWD
ACTDESC
10
MANAGE
MANAGE/ADVISE
20
ECOST
ESTIMATE COST
30
DEFINE
DEFINE SPECS
40
LEADPR
LEAD PROGRAM/DESIGN
50
SPECS
WRITE SPECS
60
LOGIC
DESCRIBE LOGIC
70
CODE
CODE PROGRAMS
80
TEST
TEST PROGRAMS
90
ADMQS
ADM QUERY SYSTEM
100
TEACH
TEACH CLASSES
110
COURSE
DEVELOP COURSES
120
STAFF
PERS AND STAFFING
130
OPERAT
OPER COMPUTER SYS
140
MAINT
MAINT SOFTWARE SYS
150
ADMSYS
ADM OPERATING SYS
476
ACTNO
ACTKWD
ACTDESC
160
ADMDB
ADM DATA BASES
170
ADMDC
ADM DATA COMM
180
DOC
DOCUMENT
Class schedule table (CL_SCHED)

The class schedule table describes each class, the start time for the class, the end time for the class, and
the class code.
The class schedule table is created with the following CREATE TABLE statement:
CREATE TABLE CL_SCHED
(CLASS_CODE
"DAY"
STARTING
ENDING
CHAR(7),
SMALLINT,
TIME,
TIME)
The table below gives the contents of the columns.

Column name
Description
CLASS_CODE
Class code (room:teacher)
DAY
Day number of 4 day schedule
STARTING
Class start time
ENDING
Class end time
CL_SCHED:
Here is a complete listing of the data in the CL_SCHED table.
CLASS_CODE
DAY
STARTING
ENDING
042:BF
12:10:00
14:00:00
553:MJA
10:30:00
11:00:00
543:CWM
09:10:00
10:30:00
778:RES
12:10:00
14:00:00
044:HD
17:12:30
18:00:00
In-tray table (IN_TRAY)

The in-tray table describes an electronic in-basket that contains the timestamp when a message is
received, the user ID of the person who sent the message, and the content of the message.
The in tray table is created with the following CREATE TABLE statement:
CREATE TABLE IN_TRAY
(RECEIVED
SOURCE
SUBJECT
NOTE_TEXT
TIMESTAMP,
CHAR(8),
CHAR(64),
VARCHAR(3000))

Column name
Description
RECEIVED
Date and time received
SQL programming
477
Column name
Description
SOURCE
User ID of person sending the note
SUBJECT
Brief description of the note
NOTE_TEXT
The note
IN_TRAY:
Here is a complete listing of the data in the IN_TRAY table.
RECEIVED
SOURCE
SUBJECT
NOTE_TEXT
1988-12-2517.12.30.000000
BADAMSON
FWD: Fantastic year! 4th Quarter

Bonus.
To: JWALKER Cc: QUINTANA,

NICHOLLS Jim, Looks like our
hard work has paid off. I have
some good beer in the fridge if
you want to come over to
celebrate a bit. Delores and
Heather, are you interested as
well? Bruce <Forwarding from
ISTERN> Subject: FWD: Fantastic
year! 4th Quarter Bonus. To:
Dept_D11 Congratulations on a
job well done. Enjoy this year's
bonus. Irv <Forwarding from
CHAAS> Subject: Fantastic year!
4th Quarter Bonus. To:
All_Managers Our 4th quarter
results are in. We pulled together
as a team and exceeded our plan!
I am pleased to announce a bonus
this year of 18%. Enjoy the
holidays. Christine Haas
1988-12-2308.53.58.000000
ISTERN
FWD: Fantastic year! 4th Quarter

Bonus.
To: Dept_D11 Congratulations on

a job well done. Enjoy this year's
bonus. Irv <Forwarding from
CHAAS> Subject: Fantastic year!
4th Quarter Bonus. To:
All_Managers Our 4th quarter
1988-12-2214.07.21.136421
CHAAS
Fantastic year! 4th Quarter

Bonus.
To: All_Managers Our 4th quarter

Organization table (ORG)

The organization table describes the organization of the corporation.
The organization table is created with the following CREATE TABLE statement:
478
CREATE TABLE ORG

(DEPTNUMB SMALLINT NOT NULL,
DEPTNAME VARCHAR(14),
MANAGER SMALLINT,
DIVISION VARCHAR(10),
LOCATION VARCHAR(13))

Column name
Description
DEPTNUMB
Department number
DEPTNAME
Department name
MANAGER
Manager number for the department
DIVISION
Division of the department
LOCATION
Location of the department
ORG:
Here is a complete listing of the data in the ORG table.
DEPTNUMB
DEPTNAME
MANAGER
DIVISION
LOCATION
10
Head Office
160
Corporate
New York
15
New England
50
Eastern
Boston
20
Mid Atlantic
10
Eastern
Washington
38
South Atlantic
30
Eastern
Atlanta
42
Great Lakes
100
Midwest
Chicago
51
Plains
140
Midwest
Dallas
66
Pacific
270
Western
San Francisco
84
Mountain
290
Western
Denver
Staff table (STAFF)

The staff table describes the background information about employees.
The staff table is created with the following CREATE TABLE statement:
CREATE TABLE STAFF
(ID SMALLINT NOT NULL,
NAME VARCHAR(9),
DEPT SMALLINT,
JOB CHAR(5),
YEARS SMALLINT,
SALARY DECIMAL(7,2),
COMM DECIMAL(7,2))
The table below shows the contents of the columns.

Column name
Description
ID
Employee number
NAME
Employee name
DEPT
Department number
JOB
Job title
YEARS
Years with the company

SQL programming
479
Column name
Description
SALARY
Employee's annual salary
COMM
Employee's commission
STAFF:
Here is a complete listing of the data in the STAFF table.
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
10
Sanders
20
Mgr
18357.50
20
Pernal
20
Sales
18171.25
612.45
30
Marenghi
38
Mgr
17506.75
40
O'Brien
38
Sales
18006.00
846.55
50
Hanes
15
Mgr
10
20659.80
60
Quigley
38
Sales
16508.30
650.25
70
Rothman
15
Sales
16502.83
1152.00
80
James
20
Clerk
13504.60
128.20
90
Koonitz
42
Sales
18001.75
1386.70
100
Plotz
42
Mgr
18352.80
110
Ngan
15
Clerk
12508.20
206.60
120
Naughton
38
Clerk
12954.75
180.00
130
Yamaguchi
42
Clerk
10505.90
75.60
140
Fraye
51
Mgr
21150.00
150
Williams
51
Sales
19456.50
637.65
160
Molinare
10
Mgr
22959.20
170
Kermisch
15
Clerk
12258.50
110.10
180
Abrahams
38
Clerk
12009.75
236.50
190
Sneider
20
Clerk
14252.75
126.50
200
Scoutten
42
Clerk
11508.60
84.20
210
Lu
10
Mgr
10
20010.00
220
Smith
51
Sales
17654.50
992.80
230
Lundquist
51
Clerk
13369.80
189.65
240
Daniels
10
Mgr
19260.25
250
Wheeler
51
Clerk
14460.00
513.30
260
Jones
10
Mgr
12
21234.00
270
Lea
66
Mgr
18555.50
280
Wilson
66
Sales
18674.50
811.50
290
Quill
84
Mgr
10
19818.00
300
Davis
84
Sales
15454.50
806.10
310
Graham
66
Sales
13
21000.00
200.30
320
Gonzales
66
Sales
16858.20
844.00
330
Burke
66
Clerk
10988.00
55.50
340
Edwards
84
Sales
17844.00
1285.00
480
ID
NAME
DEPT
JOB
YEARS
SALARY
COMM
3650
Gafney
84
Clerk
13030.50
188.00
Sales table (SALES)

The sales table describes the information about each sale for each sales person.
The sales table is created with the following CREATE TABLE statement:
CREATE TABLE SALES
(SALES_DATE DATE,
SALES_PERSON VARCHAR(15),
REGION VARCHAR(15),
SALES INTEGER)

Column name
Description
SALES_DATE
Date the sale was made
SALES_PERSON
Person making the sale
REGION
Region where the sale was made
SALES
Number of sales
SALES:
Here is a complete listing of the data in the SALES table.
SALES_DATE
SALES_PERSON
REGION
SALES
12/31/1995
LUCCHESSI
Ontario-South
12/31/1995
LEE
Ontario-South
12/31/1995
LEE
Quebec
12/31/1995
LEE
Manitoba
12/31/1995
GOUNOT
Quebec
03/29/1996
LUCCHESSI
Ontario-South
03/29/1996
LUCCHESSI
Quebec
03/29/1996
LEE
Ontario-South
03/29/1996
LEE
Ontario-North
03/29/1996
LEE
Quebec
03/29/1996
LEE
Manitoba
03/29/1996
GOUNOT
Ontario-South
03/29/1996
GOUNOT
Quebec
03/29/1996
GOUNOT
Manitoba
03/30/1996
LUCCHESSI
Ontario-South
03/30/1996
LUCCHESSI
Quebec
03/30/1996
LUCCHESSI
Manitoba
03/30/1996
LEE
Ontario-South
03/30/1996
LEE
Ontario-North
03/30/1996
LEE
Quebec
SQL programming
481
SALES_DATE
SALES_PERSON
REGION
SALES
03/30/1996
LEE
Manitoba
03/30/1996
GOUNOT
Ontario-South
03/30/1996
GOUNOT
Quebec
18
03/30/1996
GOUNOT
Manitoba
03/31/1996
LUCCHESSI
Manitoba
03/31/1996
LEE
Ontario-South
14
03/31/1996
LEE
Ontario-North
03/31/1996
LEE
Quebec
03/31/1996
LEE
Manitoba
03/31/1996
GOUNOT
Ontario-South
03/31/1996
GOUNOT
Quebec
04/01/1996
LUCCHESSI
Ontario-South
04/01/1996
LUCCHESSI
Manitoba
04/01/1996
LEE
Ontario-South
04/01/1996
LEE
Ontario-North
04/01/1996
LEE
Quebec
04/01/1996
LEE
Manitoba
04/01/1996
GOUNOT
Ontario-South
04/01/1996
GOUNOT
Ontario-North
04/01/1996
GOUNOT
Quebec
04/01/1996
GOUNOT
Manitoba
| Sample XML tables

| These sample tables can be used for working with XML concepts.
| Along with the tables are the SQL statements for creating the tables.
|
|
|
|
|
|
A stored procedure is included as part of the system that contains the data definition language (DDL)
statements to create all of these tables and the INSERT statements to populate them. The procedure
creates the schema specified on the call to the procedure. Because this is an external stored procedure, it
can be called from any SQL interface, including interactive SQL and System i Navigator. To call the
procedure where SAMPLEXML is the schema that you want to create, issue the following statement:
CALL QSYS.CREATE_XML_SAMPLE (SAMPLEXML)
| The schema name must be specified in uppercase. The schema will be created if it does not already exist.
| Make sure your job's CCSID is set to something other than 65535 before calling the procedure or it will
| get errors.
| Note: In these sample tables, a question mark (?) indicates a null value.
| Product table (PRODUCT)
| The product table identifies every product by a product ID and lists the product information.
| The product
| CREATE TABLE
|
(
|
482
table is created with the following CREATE TABLE statement:

PRODUCT
PID
NAME
VARCHAR(10) NOT NULL,

VARCHAR(128),
|
|
|
|
|
|
PRICE
PROMOPRICE
PROMOSTART
PROMOEND
DESCRIPTION
PRIMARY KEY
DECIMAL(30,2),
DECIMAL(30,2),
DATE,
DATE,
XML,
(PID) )
PRODUCT:
Here is a complete listing of the data in the PRODUCT table.
||
|
|
|
PID
|
|
|
|
|
|
|
|
|
|
|
|
100-100-01 Snow Shovel,

Basic 22 inch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
NAME
PRICE
PROMO
PRICE
PROMO
START
9.99
7.25
11/19/2004 12/19/2004
<product pid="100-100-01">
<description>
<name>Snow Shovel, Basic
22 inch</name>
<details>Basic Snow Shovel,
22 inches wide, straight
handle with D-Grip
</details>
<price>9.99</price>
<weight>1 kg</weight>
</description>
</product>
100-101-01 Snow Shovel, 19.99

Deluxe 24 inch
15.99
12/18/2005 02/28/2006
<product pid="100-101-01">
<description>
<name>Snow Shovel, Deluxe
24 inch</name>
<details>A Deluxe Snow Shovel,
24 inches wide,
ergonomic curved handle
with D-Grip</details>
<price>19.99</price>
</description>
</product>
100-103-01 Snow Shovel,

Super Deluxe
26 inch
39.99
12/22/2005 02/22/2006
<product pid="100-103-01">
<description>
<name>Snow Shovel, Super Deluxe
26 inch</name>
<details>Super Deluxe Snow
Shovel, 26 inches wide,
ergonomic battery heated
curved handle with
upgraded D-Grip
</details>
</description>
</product>
49.99
PROMO
END
DESCRIPTION, shown as it appears

using the XMLSERIALIZE scalar
function to convert it to serialized
character data
SQL programming
483
| PID
|
|
|
NAME
| 100-201-01 Ice Scraper,

|
Windshield 4
|
inch
|
|
|
|
|
|
|
|
PRICE
PROMO
PRICE
PROMO
START
PROMO
END
DESCRIPTION, shown as it appears

using the XMLSERIALIZE scalar
function to convert it to serialized
character data
3.99
<product pid="100-201-01">
<description>
<name>Ice Scraper, Windshield
4 inch</name>
<details>Basic Ice Scraper
4 inches wide, foam
handle</details>
<price>3.99</price>
</description>
</product>
| Purchase order table (PURCHASEORDER)

| The purchase order table identifies every purchase order by a purchase order ID and lists basic purchase
| order information.
| The purchase order table is created with the following CREATE TABLE and ALTER TABLE statements:
| CREATE TABLE PURCHASEORDER
|
( POID
BIGINT NOT NULL,
|
STATUS
VARCHAR(10) NOT NULL WITH DEFAULT(Unshipped),
|
CUSTID
BIGINT
|
ORDERDATE
DATE
|
PORDER
XML
|
COMMENTS
VARCHAR(1000),
|
PRIMARY KEY (POID) )
|
| ALTER TABLE PURCHASEORDER
|
ADD FOREIGN KEY FK_PO_CUST(CUSTID)
|
REFERENCES CUSTOMER(CID)
|
ON DELETE CASCADE
484
PURCHASEORDER:
Here is a complete listing of the data in the PURCHASEORDER table.
||
|
|
POID
STATUS
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5000
Unshipped 1002
02/18/2006
<PurchaseOrder PoNum="5000"
OrderDate="2006-02-18"
Status="Unshipped">
<item>
<partid>100-100-01</partid>
22 inch
</name>
<price>9.99</price>
</item>
<item>
<name>Snow Shovel, Super
Deluxe 26 inch
</name>
</item>
</PurchaseOrder>
THIS IS A NEW
PURCHASE ORDER
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5001
Shipped
02/03/2005
Status="Shipped">
<item>
24 inch
</name>
</item>
<item>
Deluxe 26 inch
</name>
</item>
<item>
4 inch
</name>
<price>3.99</price>
</item>
</PurchaseOrder>
THIS IS A NEW
PURCHASE ORDER
CUSTID
1003
ORDERDATE PORDER, shown as it appears using

COMMENTS
the XMLSERIALIZE scalar function to
convert it to serialized character data
SQL programming
485
| POID
|
|
STATUS
CUSTID

COMMENTS
| 5002
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Shipped
1001
02/29/2004
Status="Shipped">
<item>
22 inch
</name>
<price>9.99</price>
</item>
<item>
24 inch
</name>
</item>
<item>
4 inch
</name>
<price>3.99</price>
</item>
</PurchaseOrder>
THIS IS A NEW
PURCHASE ORDER
| 5003
|
|
|
|
|
|
|
|
|
|
|
Shipped
1002
02/28/2005
Status="UnShipped">
<item>
22 inch
</name>
<price>9.99</price>
</item>
</PurchaseOrder>
THIS IS A NEW
PURCHASE ORDER
486
|
|
|
POID
STATUS
CUSTID

COMMENTS
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5004
Shipped
1005
11/18/2005
Status="Shipped">
<item>
22 inch
</name>
<price>9.99</price>
</item>
< item>
Deluxe 26 inch
</name>
</item>
</PurchaseOrder>
THIS IS A NEW
PURCHASE ORDER
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5005
Shipped
1002
03/01/2006
Status="Shipped">
<item>
22 inch
</name>
<price>9.99</price>
</item>
<item>
24 inch
</name>
</item>
<item>
4 inch
</name>
<price>3.99</price>
</item>
</PurchaseOrder>
THIS IS A NEW
PURCHASE ORDER
|
|
Customer table (CUSTOMER)
The customer table is created with the following CREATE TABLE statement:
The customer table identifies every customer by a customer ID and lists basic customer information.
SQL programming
487
| CREATE TABLE CUSTOMER

|
( CID
|
INFO
|
HISTORY
|
PRIMARY KEY
BIGINT NOT NULL,

XML,
XML,
(CID) )
| CUSTOMER:
| Here is a complete listing of the data in the CUSTOMER table.
|| CID
|
INFO, shown as it appears using the XMLSERIALIZE

scalar function to convert it to serialized character data
HISTORY
| 1000
|
|
|
|
|
|
|
|
|
</addr>
</customerinfo>
| 1001
|
|
|
|
|
|
|
|
|
</addr>
</customerinfo>
| 1002
|
|
|
|
|
|
|
|
|
</addr>
</customerinfo>
| 1003
|
|
|
|
|
|
|
|
|
|
|
|
<city>Aurora</city>
</addr>
<phone type="cell">905-555-8743</phone>
<phone type="cottage">613-555-3278</phone>
</customerinfo>
488
|
|
CID
INFO, shown as it appears using the XMLSERIALIZE

scalar function to convert it to serialized character data
HISTORY
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1004
</addr>
<assistant>
</assistant>
</customerinfo>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1005
<name>Larry Menard</name>
<street>223 Nature Valley Road</street>
<pcode-zip>M4C 5K8</pcode-zip>
</addr>
<assistant>
<name>Goose Defender</name>
</assistant>
</customerinfo>
|
|
Catalog table (CATALOG)
|
|
|
|
|
The catalog table is created with the following CREATE TABLE statement:
CATALOG:
The CATALOG table contains no data.
|
|
Suppliers table (SUPPLIERS)
|
|
|
|
|
The suppliers table is created with the following CREATE TABLE statement:
The catalog table describes each catalog.
CREATE TABLE CATALOG

( NAME
CATLOG
XML,
PRIMARY KEY (NAME) )
The suppliers table identifies every supplier and lists basic supplier information.
CREATE TABLE SUPPLIERS

( SID
ADDR
XML,
PRIMARY KEY (SID) )
SQL programming
489
| SUPPLIERS:
| Here is a complete listing of the data in the SUPPLIERS table.
|| SID
ADDR
| 100
|
|
|
|
|
|
|
|
<supplierinfo xmlns="http://posample.org" Sid="100">

<name>Harry Suppliers</name>
</addr>
</supplierinfo>
| 101
|
|
|
|
|
|
|
|
|
<supplierinfo xmlns="http://posample.org" Sid="101">

<name>Johnston Suppliers</name>
<street>302 NatureValley Road</street>
<pcode-zip>M4C 5K8</pcode-zip>
</addr>
</supplierinfo>
| Inventory table (INVENTORY)

| The inventory table describes the inventory based on a product ID.
| The inventory table is created with the following CREATE TABLE statement:
| CREATE TABLE INVENTORY
|
( PID
|
QUANTITY
INTEGER,
|
LOCATION
VARCHAR(128),
|
PRIMARY KEY (PID) )
| INVENTORY:
| Here is a complete listing of the data in the INVENTORY table.
|| PID
QUANTITY
LOCATION
| 100-100-01
| 100-101-01
25
Store
| 100-103-01
55
Store
| 100-201-01
|
99
Warehouse
| Product Supplier table (PRODUCTSUPPLIER)

| The product supplier table describes the relationship between a product and its supplier.
| The product
| CREATE TABLE
|
(
|
|
490
supplier table is created with the following CREATE TABLE statement:

PRODUCTSUPPLIER
PID
SID
PRIMARY KEY (PID, SID) )
PRODUCTSUPPLIER:
Here is a complete listing of the data in the PRODUCTSUPPLIER table.
||
PID
SID
100-101-01
100
|
|
100-201-01
101
DB2 for i CL command descriptions

DB2 for i provides these CL commands for SQL.
v Create SQL Package (CRTSQLPKG) command
v Delete SQL Package (DLTSQLPKG) command
v Print SQL Information (PRTSQLINF) command
v Run SQL Statement (RUNSQLSTM) command
v Start SQL Interactive Session (STRSQL) command
Related reference:
DB2 for i distributed relational database support on page 427
The IBM DB2 Query Manager and SQL Development Kit for i licensed program supports interactive
access to distributed databases.
Code license and disclaimer information

IBM grants you a nonexclusive copyright license to use all programming code examples from which you
can generate similar function tailored to your own specific needs.
SUBJECT TO ANY STATUTORY WARRANTIES WHICH CANNOT BE EXCLUDED, IBM, ITS
PROGRAM DEVELOPERS AND SUPPLIERS MAKE NO WARRANTIES OR CONDITIONS EITHER
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR
CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND
NON-INFRINGEMENT, REGARDING THE PROGRAM OR TECHNICAL SUPPORT, IF ANY.
UNDER NO CIRCUMSTANCES IS IBM, ITS PROGRAM DEVELOPERS OR SUPPLIERS LIABLE FOR
ANY OF THE FOLLOWING, EVEN IF INFORMED OF THEIR POSSIBILITY:
1. LOSS OF, OR DAMAGE TO, DATA;
2. DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES, OR FOR ANY ECONOMIC
CONSEQUENTIAL DAMAGES; OR
3. LOST PROFITS, BUSINESS, REVENUE, GOODWILL, OR ANTICIPATED SAVINGS.
SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF DIRECT,
INCIDENTAL, OR CONSEQUENTIAL DAMAGES, SO SOME OR ALL OF THE ABOVE LIMITATIONS
OR EXCLUSIONS MAY NOT APPLY TO YOU.
SQL programming
491
492
Appendix. Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that
only that IBM product, program, or service may be used. Any functionally equivalent product, program,
or service that does not infringe any IBM intellectual property right may be used instead. However, it is
the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or
service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not grant you any license to these patents. You can send
license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
3-2-12, Roppongi, Minato-ku, Tokyo 106-8711
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some
states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this
statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
493
Software Interoperability Coordinator, Department YBWA

3605 Highway 52 N
Rochester, MN 55901
U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases,
payment of a fee.
The licensed program described in this document and all licensed material available for it are provided
by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement,
IBM License Agreement for Machine Code, or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the
results obtained in other operating environments may vary significantly. Some measurements may have
been made on development-level systems and there is no guarantee that these measurements will be the
same on generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their
specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without
notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for the operating platform for
which the sample programs are written. These examples have not been thoroughly tested under all
conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
Each copy or any portion of these sample programs or any derivative work, must include a copyright
notice as follows:
(your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs.
Copyright IBM Corp. _enter the year or years_.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Programming interface information

This SQL programming publication documents intended Programming Interfaces that allow the customer
to write programs to obtain the services of IBM i.
494
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at
Copyright and trademark information at www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks
of Adobe Systems Incorporated in the United States, and/or other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other
countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, or service names may be trademarks or service marks of others.
Terms and conditions

Permissions for the use of these publications is granted subject to the following terms and conditions.
Personal Use: You may reproduce these publications for your personal, noncommercial use provided that
all proprietary notices are preserved. You may not distribute, display or make derivative works of these
publications, or any portion thereof, without the express consent of IBM.
Commercial Use: You may reproduce, distribute and display these publications solely within your
enterprise provided that all proprietary notices are preserved. You may not make derivative works of
these publications, or reproduce, distribute or display these publications or any portion thereof outside
your enterprise, without the express consent of IBM.
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either
express or implied, to the publications or any information, data, software or other intellectual property
contained therein.
IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of
the publications is detrimental to its interest or, as determined by IBM, the above instructions are not
being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable
laws and regulations, including all United States export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE
PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF
MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.
Appendix. Notices
495
496
IBM
Printed in USA

Rbafy-Database SQL Programming 7.1

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Rbafy-Database SQL Programming 7.1

Caricato da

Copyright:

Formati disponibili

IBM

What's new for IBM i 7.1 . . . . . . . . ..

Defining field procedures. . . . . . . ..

IBM i: Database SQL programming

Including subqueries in the WHERE or

Example 1: Calling a stored procedure

Improving implementation of procedures and

Exercise 2: Inserting XML documents into

IBM i: Database SQL programming

Using the PREPARE and EXECUTE

Source code for PGM2 . . . . . . ..

IBM i: Database SQL programming

Employee resum table (EMP_RESUME) ..

What's new for IBM i 7.1

Result sets returned to programs

Copyright IBM Corp. 1998, 2010

Arrays in SQL procedures

WebSphere MQ with DB2

| Other functional changes to the SQL programming information

What's new as of April 2015

What's new as of October 2014

Pipelined table functions

IBM i: Database SQL programming

SQL variable debug for SQL routines

What's new as of February 2013

Multiple event triggers

System name for tables, views, and indexes

What's new as of October 2012

Defaults for procedure parameters and using parameter names in CALL

CREATE TABLE referencing a remote table

SQL and external routine management

RUNSQLSTM OPTION parameter

What's new as of April 2012

Insert from a remote table

What's new as of April 2011

How to see what's new or changed

image to mark where new or changed information begins.

PDF file for SQL programming

Saving PDF files

Downloading Adobe Reader

Introduction to DB2 for i Structured Query Language

IBM i: Database SQL programming

SQL relational database and system terminology

Library. Groups related objects and allows you to find

Schema. Consists of a library, a journal, a journal

Physical file. A set of records.

IBM i: Database SQL programming

Table 1. Relationship of system terms to SQL terms (continued)

Record. A set of fields.

Row. The horizontal part of a table containing a serial

Field. One or more characters of related information of

View. A subset of columns and rows of one or more

SQL and system naming conventions

System naming (*SYS)

SQL naming (*SQL)

Types of SQL statements

SQL schema statements

SQL data statements

SQL data change statements

SQL connection statements

SQL transaction statements

SQL session statements

Dynamic SQL statements

Embedded SQL host language statements