In this article I will take a look at the basic rules and coding requirements for using commitment control within RPG programs.

A Database

Figure 1 – SQL used to create a sample schema and tables.

Note: The code show above is available for download here.

Figure 1 shows the SQL used to create a schema named COMMIT, which contains two related tables, called HEADER and DETAILS. The main points to note are as follows (refer to the corresponding letters in Figure 1):

A. Creating the schema COMMIT results in a library named COMMIT that contains a journal named

This article briefly explores the new client special registers that are now available in V6R1 and how they benefit client/server development. In case you missed them, Part 1 of this series discussed several query enhancements and explained how IBM is packing more functionality into a single statement. Part 2 of this series discussed the concept of super groups and grouping sets, which are very useful features that allow developers to add various aggregations to a result set.

Now back to the topic at hand. Since so much new DB2 development is client/server based, IBM created a useful set of special

My shop recently upgraded its email system from Novell GroupWise to Microsoft Exchange. Along with the server change, we also had to reconfigure six i5/OS partitions to use the new Exchange server as their SMTP relay. If you’re faced with this type of issue, here’s an easy checklist for painlessly making the change.

Three Easy Steps

Changing your iSeries/System i/Power i SMTP relay is a relatively easy process with one or two minor kinks. There are three keys to making this change.

1. Change the SMTP mail relay settings. This can be done either on the green-screen or in iSeries Navigator