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

Welcome back to this introduction to Python on our beloved iSeries. In this second part of the series, you’ll learn how to use Python in something resembling a real world context. You’re going to integrate Python with perhaps the most quintessentially “i” part of IBM i, DB2.

As with Part 1, all the Python scripts featured in this article are available for download here. Unless otherwise stated, all the Python scripts can be run like so:

PYTHON25/PYTHON PROGRAM('/path/to/the/python/script.py')

DB2 is a

Over the past few months I’ve been working on more articles dealing with the use of pointers in RPG programs. While I was working on my demo programs, I ran into a little snag while verifying that everything was working correctly. Let me tell you what I ran into and how I got around it.

I wanted to double-check the value of all the pointer variables. In the interactive green-screen debugger, which I was using, seeing the value of a pointer is no problem. Place the cursor on the pointer variable name and press F11, or use the EVAL command.

While upgrading Power i hardware is a hassle, the benefits in alleviating processing bottlenecks, providing new capabilities, and solving performance issues far outweigh the risks. Before an upgrade, however, management will want to consider any possible upgrade risks and how they can reduce your organization’s exposure to those risks. This issue, I’ll examine some common i/OS hardware upgrade risks and what you can do about them.

Getting the Vocabulary Right

In discussing risks, organizational requirements may require you to specify the following items when requesting monies for a new Power i hardware upgrade.

• Can you identify your upgrade risks and