× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 10-Feb-2015 09:20 -0600, rob@xxxxxxxxx wrote:

Normally in the second program concept you do not have two programs
reading the file. It's often done like this:

myloop:
call ReaderProgram
dlyjob 300
goto myloop
endpgm

<<SNIP>>

Not in my experience. The implication of someone suggesting using two programs had been typically, to suggest the use of two distinct programs whereby each had coded both the identical DCLF and identical looping through the data with RCVF [terminating upon CPF0864], but each program performs different work against the data than the other.

The above-quoted CL example reflects what I expect would be described as having coded just _one program_ that accepts a parameter to describe what that one program does; the program would be called twice, and the parameter tells the program which _pass_ of the data, such that even if the caller were understood to be a program [rather than scripted calls], then that program would not be /counted/.

And what is shown in that quoted example, fails to explain how the ReaderProgram knows whether each particular invocation should perform the pass-one or pass-two.? I would expect that if someone were to respond with a two-program suggestion whereby only one does the DCLF, then they would be suggesting instead, something like the following?:

mainline: /* program: InvokeReaderProgram */
call ReaderProgram parm('*PASS1')
call ReaderProgram parm('*PASS2')
endpgm


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.