Note: The code accompanying this article is available for download here.

Tomorrow, Lord willing, I will present a session entitled “An Alternative to Externally Described Printer Files” at the COMMON conference in Nashville. I’ll be sharing the report-building technique my reclusive colleague Cletus the Codeslinger introduced almost four years ago in this august publication. Since that time, various people have offered feedback, which Cletus and I have used to update the template that he provided. In this article, I present the updated template and two example programs: one using native I/O, one using SQL.

First, if you haven’t read

Here’s a third performance tip from one of your fellow subscribers, whose identity I have agreed to hold in confidence. I appreciate the feedback I have received in response to his previous tips and hope to publish some of your comments in the near future.

Here’s performance tip number 3: “Use CHGJRN to set MINENTDTA to *FLDBDY.”

When you journal a file, you record changes that are made to contents of the file. You keep a record of each record added to the file, each record that is removed from the file, and each record that is changed. All of

Last week, I began covering how to change the communications identity on an i5/OS box so that it can impersonate another system and take its place on the network. This week, I’ll conclude demonstrating my i5/OS impersonation techniques and offer a checklist for making one System i box look like another System i box on your network.

Why We Impersonate?

As covered last issue, system impersonation techniques come in handy in the following situations:

• When replacing an existing System i machine with a new box. During testing, setup, and cutover, both systems may need to run side-by-side and