In IBM i 7.1 Technology Refresh 4 (TR4), IBM gave SQL developers the ability to insert data into a local database table from a remote DB2 for i database table within the comfort of a single SQL statement. (See my article Copy Data From A Remote DB2 Database Using DB2 For i 7.1 for more info).

With Technology Refresh 5, specifically DB2 for i Group PTF Level 18 or later, you can dynamically create a local table and insert data into it directly from a remote DB2 for i database query using the CREATE TABLE … AS statement.

Recall that

As I was looking for something in the DB2 for i SQL reference, my eyes happened to see MERGE in the list of statements, and I realized that I had been doing something the hard way. I realized that I was about to abandon the method I had been using to update values in one database table (physical file) from data in another one.

Once in a while, someone requests that I use a list of values, which are usually stored in a spreadsheet, to mass update the database on the big computer. Fortunately, several years ago I learned how

IBM i administration has elements of old-time system operations and real-time monitoring. You need to ensure that everything is working correctly and that problems aren’t silently developing that can: a) interfere with customer processing; and b) violate customer service-level agreement (SLA) requirements or create audit violations. This week, let’s flesh out a checklist of items to help IBM i admins achieve these goals.

The Essential Piece

In order to catch trouble before it occurs, I highly recommend that you set up an IBM i monitoring system to catch developing situations and alert you via email or text when a problem