The green screen PDM and the GUI Rational Developer for i (RDi) tools provide developers an easy way to search through source code to find a specified text literal. But what if these tools don’t have access to all your code, in particular the SQL code? Many developers may not be keeping an up-to-date source copy of their SQL persisted stored modules (functions, procedures and triggers) and further, may not be keeping a copy of the source at all. If this is the case in your shop, never fear, for DB2 for i maintains a record of the source statements

I advise, recommend, urge, admonish, and even cajole RPG programmers to quit using subroutines and start using subprocedures instead. Yet I still hear from people who work in shops that allow the use of RPG IV (a.k.a. ILE RPG), but do not allow binding to modules and service programs. Today I offer two ways to use subprocedures that do not require ILE binding.

But first, let’s have a quick review of ILE binding of subprocedures into programs.

1. Bind by copy

The object code of the subprocedures of a module is copied into the object code of a program

I want to add another batch job queue to my QBATCH subsystem for submitting reporting jobs that take a long time to process. I want to put them in their own job queue so they can just chug away in QBATCH without interfering with my other batch work. How do I add another job queue that I can submit these jobs to?

–Bob

Adding batch job queues to QBATCH is easy. All you have to do is perform the following steps and you’ll be able to create another QBATCH job queue in no time.

1. Check to see how many jobs