In Part 1 of this series, I introduced the DB2 for i developer’s newest friend, the XML “slicer and dicer” table function: XMLTABLE. XMLTABLE is powerful because it can read an XML document and convert its content to a tabular format that can participate in a query with relational data.

The developer has to specify the mapping between the XML data and the intended tabular format by using XPath expressions that instruct XMLTABLE how to map the data from XML into rows and columns. In this article, I’d like to cover two additional topics: parsing XML documents containing namespaces, and

In the May 2, 2012, edition of this august publication, I shared how Brian Rusch’s shop uses an API to forward escape messages up the call stack in CL programs. The Resend Escape Message (QMHRSNEM) API works just as well in RPG subprocedures. Here’s how it’s easily done.

First, you need a prototype for QMHRSNEM, and you must define the first two parameters.

D ResendEscapeMsg...
D                 pr                  extpgm('QMHRSNEM')
D   MessageKey                   4a   const
D   ErrorCode                   10i 0 const

You can define the remaining parameters if you want, but make sure you mark them OPTIONS(*NOPASS). If you like, place the prototype in

One of my clients is working on a new build for their Windows 7 computers. They are deploying IBM i Access for Windows 7.1 (IBM i Access) on Windows 7 for the first time, and I’ve been evaluating using the product on that platform. Here are some issues and observations I’ve seen with the Personal Communications (Pcom) product that comes with version 7.1.

Run The Same May Not Run The Same In IBM i 7.1

Like IBM i Access for Windows’ predecessors such as Client Access Express for Windows, iSeries Access for Windows, etc., IBM i Access ships with a