SQL descriptors allow for incredible flexibility when it comes to constructing dynamic SQL statements and/or processing the results of a dynamic SQL statement. But, since this is an introduction, let’s look at how they can be used in constructing dynamic SQL statements and leave their use in processing results for a later article.

Assume we want to embed the following SQL statement in an RPG program:

select workDept, empno, firstname, lastname from employee
   where workDept  = ?  and
         hireDate  >= ? and
         birthDate >= ?
   order by workDept, empno

The difficulty we have is that comparison values may or may

Almost eight years ago I gave you two good reasons to use a correlation name when SQL did not require one. A recent experience revealed to me another good reason to use an unnecessary correlation name, and I am happy to be able to share that information with you today!

A colleague of mine had an SQL query that ran to completion but produced the wrong results. He asked me to take a look at it, and I’m glad he did, because the experience taught me something. Let me set up the situation for you.

Assume two tables: a table

In Part 1 and Part 2 of this RCAC series, I covered row and column access control (RCAC) row permissions and column masks, and demonstrated how they can be used to add an additional layer of security to your DB2 for i database without necessarily having to change legacy applications. This tip will explore the RCAC topic a little further by discussing a few advanced concepts that may affect your implementation of RCAC.

Bypassing RCAC With SET SESSION AUTHORIZATION

When the SET SESSION AUTHORIZATION statement is executed, a SQL database connection is “impersonated” to run under the identity of another