This article expands the exploration of prototypes into the realm of subprocedures and explains how they can be used to replace subroutines.
Written by Joe Pluta
In a previous article, I showed you how to use a prototype to replace the PLIST in your programs. In this second installment of "Prototyping for Productivity," I'll show you how and why you would replace a subroutine with a subprocedure. The third and final article in the series will work with some of the keywords.
Do a DSPJRN to an outfile, and field JOESD is inscrutable. Learn how to make it readable.
Written by Sam Lennon
You know that journal entries contain useful "who did what to whom and when" information and that they can also help you understand data flow and changes in a suite of unfamiliar programs. You've probably used the DSPJRN command, and on the screen you can easily see the date and time the transaction occurred. You can also see the job name, user, and number. You can even see the program that made the transaction. But you can't (easily) see what changed! Usually, you see something like Figure 1, with a mishmash of special characters in the "Entry specific data" field.