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

A good friend of mine, who also happens to be president of our local user’s group, had been encouraging me to present a session at one of their meetings. I resisted for some time, but finally decided this was an exciting prospect. The topic I would choose became clear to me almost immediately. We use journaling in my shop for so many purposes that we simply couldn’t survive without it. I’ve always been very interested in journaling, especially in applications of the technology to forensics and recovery.

It’s

When you create a new database table (physical file), you should include those columns (fields) that are fully functionally dependent on the key fields. I would like to mention some additional columns that you might like to include also.

The columns to which I refer are ones that store creation and change data. For example, you may want to be able to tell who inserted a row (added a record) and who last changed it. Such information may allow you to give a quick answer to a user’s conundrum.

Look at this simple CREATE TABLE statement. Notice the last six

With corporate buy-outs, company spin-offs, and moving Power i servers to a centralized data center or a managed server provider, many shops are finding that they need to move their Power i partitions to a different network or a cloud provider. To that end, here’s a checklist I put together to help ensure that your Power i partitions can function without issue in a new environment.

Why We Move

There are many reasons you might need a playbook for moving a Power i partition from one location and network to another. Some of the more common situations include:

• Company sale