I remember when I first started in the industry how difficult performance management was, especially in the area of memory. The good news was IBM provided clear defined service levels in regards to memory pools.

I’m not sure what year I discovered the guidelines, maybe in the 1980s, but I do remember that the published guidelines were so easy. In fact, I can still see the faded yellow sticky note on my desk with the following guidelines.

After managing the box for years and attending numerous performance sessions and the like, I discovered the guidelines were not only not talked

Dynamic compound statements are sure to be one of the most oft used new SQL features in IBM i 7.1. In general, this feature allows developers to execute a complex set of SQL statements that include variable use, error handling, and conditional logic on the fly without creating a permanent SQL routine such as a function or stored procedure.

Dynamic compound statements makes DB2 similar to other database platforms like SQL Server where SQL scripts can be written and executed on the fly. This feature comes in DB2 for i group PTF level 26, so make sure your database PTFs

In December, I began discussing four different approaches for moving an IBM i partition from an existing machine to a new location and the different tasks needed for each technique. I talked about using traditional system back-up and restore migration techniques last issue. This issue, I’ll focus on using high availability (HA) software to migrate a partition.

Four Ways To Move An IBM i

To review, there are four techniques for moving an IBM i partition to a different machine:

1. Restore the partition in place or to a new location using the same system name. This is a traditional restore