I do my coding using Rational Developer for Power Systems (a.k.a. RDP). Most of the time, I open the source code in the editor in RDP much like SEU users would, in the sense that I open my source directly from a member in a source file in a library on IBM i. When I save from the RDP editor, the source is saved back to that same member.

Below is a picture of what my screen looks like when I’m working with RDP as described above. Note the highlighted library, source files, and members in the “Remote Systems” view

If an RPG programmer has a best friend, it may very well be the CHAIN opcode, which performs a random read on a keyed database file. It’s common programming practice in information-processing shops to read one file sequentially and to chain to read a host of others randomly. SQL handles this sort of thing differently. With SQL, joining is the proper way to retrieve data from two or more tables and/or views. The difference is even more pronounced when some of the random processing may or may not take place.

Suppose you’re responsible for a database that contains customer orders.

In an earlier column, I described how to solve problems when loading digital certificates into your IBM i Digital Certificate Manager (DCM). This week, I’ll review another DCM problem where the default certificate in the system certificate store (*SYSTEM) expires, and the system starts refusing connections from clients that use digital certificates. This week, let’s examine what happens when a *SYSTEM default certificate expires and how to renew that certificate in DCM.

Getting The Terminology Correct

To untangle what’s happening here, let’s first look at some terminology regarding your partition’s DCM.

A system certificate store, designated by *SYSTEM in DCM,