Note: The code accompanying this article is available for download here.

In programming terms, recursion is the process whereby a function may call itself. Traditionally, this is something we are not used to in RPG. Programs and subroutines cannot call themselves. Or if you did somehow manage it (and you could), you would get unpredictable results.

But the introduction of subprocedures opened up the possibility of using recursion because subprocedures can call themselves.

It is usually very difficult to come up with practical examples of using recursion, and most of those examples are usually very specific to an application.

Note: The code accompanying this article is available for download here.

A couple of years ago I needed to develop a process where a group of items could be selected from a screen and a report listing those items could be generated. On the surface, a simple task. Of course, if you give a mouse a cookie, they’re going to want a glass of milk, or another report. . . and another. Again, not too complicated. All that should be needed is a way to submit a call to a variable list of programs. As long as each program

Your organization’s fiscal year may have ended on September 30. Meaning you could soon be visited by auditors looking for information on how your organization operates its AS/400-class machine (iSeries, System i, Power i). Your auditors will be particularly interested in your password configuration parameters and whether they meet standards. To that end, here’s a quick drill for retrieving password setup values at audit time.

What Auditors Want

Auditors generally require you to provide the following sets of password related parameters.

• Your password configuration parameters–The rules users follow for creating passwords.
• Configuration and program code for Password Validation Program

Note: The code accompanying this article is available for download here.

In programming terms, recursion is the process whereby a function may call itself. Traditionally, this is something we are not used to in RPG. Programs and subroutines cannot call themselves. Or if you did somehow manage it (and you could), you would get unpredictable results.

But the introduction of subprocedures opened up the possibility of using recursion because subprocedures can call themselves.

It is usually very difficult to come up with practical examples of using recursion, and most of those examples are usually very specific to an application.

Note: The code accompanying this article is available for download here.

A couple of years ago I needed to develop a process where a group of items could be selected from a screen and a report listing those items could be generated. On the surface, a simple task. Of course, if you give a mouse a cookie, they’re going to want a glass of milk, or another report. . . and another. Again, not too complicated. All that should be needed is a way to submit a call to a variable list of programs. As long as each program

Your organization’s fiscal year may have ended on September 30. Meaning you could soon be visited by auditors looking for information on how your organization operates its AS/400-class machine (iSeries, System i, Power i). Your auditors will be particularly interested in your password configuration parameters and whether they meet standards. To that end, here’s a quick drill for retrieving password setup values at audit time.

What Auditors Want

Auditors generally require you to provide the following sets of password related parameters.

• Your password configuration parameters–The rules users follow for creating passwords.
• Configuration and program code for Password Validation Program