Since V4R2, I’ve watched SQL enhancements like a hawk, eagerly waiting to use the improvements IBM has given us. V5R4 SQL contains several new items that will be outlined here. Here are a few thoughts on this significant release, which I gleaned from the DB2 Summary sheet on IBM’s Web site.

• The SQL syntax in V5R4 meets the Core requirements for the 2003 SQL standard. A review of the 2003 SQL standard can be found by clicking here.
• Routines written in the SQL language will now have better execution times thanks to enhancements to the code generation engine,

Dear esteemed, highly skilled, and truly professional colleagues:

Even though WDSc is my development platform of choice, I have no choice but to use SEU at times. Can you say, “Yuck!”? Occasionally I even have to use SEU remotely through the Windows Telnet client. Can you say, “Double yuck!”? I feel like I’m back in the punch-card days. In any event, I have learned recently that some people make SEU harder than it has to be. Here are a few tips to reduce keystrokes. They’re good for everyday use, and even better when working remotely.

Tip 1: You don’t have

In a recent column, I discussed how to move printer devices and output queues between systems. While that article showed you how to migrate objects by using save and restore techniques, reader Bill Bremerman wrote in to remind me that you can also use the Retrieve Configuration Source command (RTVCFGSRC) to capture CL source code, which can be used to easily recreate devices, controllers, line descriptions, and several other i5/OS objects on any system.

Here is how it works.

My earlier article focused on migrating device objects to a new partition by using the i5/OS Save Configuration command (SAVCFG)