|
Are there any questions about the code as posted? Trial 1: CALL AG03, fill in the name of a familiar source file like QRPGLESRC QGPL and press Enter. You see one page worth of members. If you put a 'P' next to one and press Enter, that member will be printed. The flow is fairly simple - AG03 calls AG02 to get a list of members AG03 calls AG01CL to print a member This is our "legacy" code. Trial 2: Just to show that a single named group will run exactly the same, change the H specs to h debug dftactgrp(*no) actgrp('QILE') option(*srcstmt: *nodebugio) and re-compile the 3 RPG programs. CALL AG03 and verify that the results are the same as trial 1. In such a simple application, there isn't a need to run outside *DAG, but let's imagine that the boss has laid out plans for a series of utilities for dealing with source members, so we're going to be building up a service program and using AG02 as the first module in that process. My next note (tomorrow) will have the service program and the binder language to create it with. Once that's posted, we can run trial 2 as a service program/client and see how it reacts under AG('QILE') --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.