Our users are always looking for information in different formats. They want to see it on a screen, in a report, in a PDF document, in an email, or in a spreadsheet. There are many ways of achieving all of these but most require third-party products or quite a bit of study to master a new programming technique.

Well, there is a very easy way to generate the spreadsheets your users require using nothing more then Excel, RPG, CGIDEV2, and a little knowledge of XML (no experience required).

Excel (as of Excel 2002, I believe) allows you to save a

Among the many enhancements that V6R1 provided for System i and i5/OS are several for Run SQL Scripts, which improve its function and broaden its usability. Run SQL Scripts is part of the Database function in System i Navigator.

Save Script to System i Source File

Prior to V6R1, scripts for Run SQL Scripts (a.k.a. SQL Script Center) could only be saved as PC files with a .SQL extension, either on a PC or on the System i IFS. Starting with V6R1, these script files can now be saved on the System i as a member in System i source

My shop ran its first high availability failover test in 2007. We’ve since run many more tests where we configured two different System i 550 Capacity BackUp (CBU) units to impersonate other systems. We’ve also made many mistakes in the process. Today, I’m focusing on common CBU failover problems and how to avoid them. Hopefully, this information will help make your failover process run smoothly.

Meet the CBU

In the i5/OS world, a CBU system is a specially configured Power i, System i, or iSeries machine that communicates with your production machine to continuously replicate production data and applications using