Note: All of the files needed for this article are available for in one download here.

When we think of programming on IBM i, our minds usually turn to the venerable RPG, or maybe CL. Some of us will think of ILE C, and those who frequently entertain dinner guests from IBM will have the word “Java” seared into their brain, and mistakenly use “EGL” instead of friends’ names. However, ask a UNIX or Linux aficionado to name a scripting language, and they will probably come up with Perl, Ruby, or very likely, Python.

Python was created as an

It eventually happens to every developer. You write a stored procedure to return one or more sophisticated result sets to a Java or .NET client. Everyone is (temporarily) happy. Eventually, a need arises for an RPG or COBOL program to execute this stored procedure and process the result set(s). But, alas, high level language programs have no way to open and process a result set (except when using the cumbersome CLI API).

Phooey, that means we’ll need to duplicate the stored procedure code in an RPG friendly manner! But wait, here comes DB2 for i 7.1 to the long-anticipated rescue!

Recently I wrote several articles about some IBM i upgrades my shop performed this year. Such is the way of things in i shops that I’m already planning for another set of upgrades next year, in July 2011. If you’re in the same situation where new Power i boxes are just over the horizon, here’s some tips to help you plan your upgrade.

Your BP and You

Before you do anything else on your upgrade, first evaluate your business partner (BP). This is a moot point for many people but you should ask yourself if you’re happy with your business