On 11 January 2018 at 22:57, Hobart Spitz <[email protected]> wrote:
> Would I be wrong to say a sipping CALLPIPE in a loop might be a good > generalized solution for issuing multiple commands, and keeping the return > codes and messages properly timed? You could, but it probably does not give you much beyond a REXX loop over a stemmed variable with the commands.To me the benefit of unrolling the loop into a straight pipeline would be that it's easier to code (at least less code to write). The straight pipe really shines when you need to do something with the combined output (like keeping track of all users seen). Even more fun when the output generates new commands to issue (e.g. expanding the users in groups on a RACF access list). But when you're doing a CMS command for each input record, it's time to wonder whether you have the right tool for the job. :story. Decades ago, I had written a pipeline that would go through a large set of reports to compose an extract for a single user (which we used to clean up when a userid was removed). A colleague was burning a CPU on a weekly basis running the EXEC in a loop to build a report for all users, each time reading all the reports. That was simplified a lot by a new pipeline to produce what he wanted. :estory.
