It was a dark night on a network that knew how to keep its secrets. Actually, that was last night. Today was going to be a busy day working on the network that knew how to keep its secrets. I’d been temporarily moved from my nightshift role at the help desk to the daylight hours to cover for a coworker who was out with an extended illness, but I was beginning to wonder if my late-night auction surfing had attracted some attention I did not need.

My phone rang, and I paused for a moment as I considered that this

In Stored Procedure Parameter Defaults And Named Arguments In DB2 For i, I covered two new related features in DB2 for i 7.1 that were implemented in Technology Refresh 5 (DB2 for i Group PTF Level 18 or higher). In this tip, I’m going to cover a surprising limitation of this feature when coding in an ActiveX Data Objects (ADO) environment, whether using an IBM DB2 OLE DB provider or the iSeries Access ODBC provider.

Recall that stored procedure parameters now support a DEFAULT keyword that can be a literal, subquery, or expression (with limitations):

CREATE PROCEDURE DEV.CREATE_ORDER (

My Power i system is driving me crazy with RPG1218 record lock messages. Because of the way one of our applications was written, we receive RPG1218 messages several times a day. The record lock only lasts a minute. When we enter a retry on the locked record, the system is always able to update the record. Is there any way to auto-answer these record locks?

–Bert

Well the first thing I’d do is have your applications staff figure out why that program is causing so many record locks and fix it. (Ha.) Barring that, I may have a solution that