RE:Identifying the driver?

[John Carr <74711.77@xxxxxxxxxxxxxx>]

RE:     Identifying the driver?

Actually,  In a growing number of processes there isn't a "Driver" file.
We are moving more and more to a paradigm where the "Driver" file is an
event.  What with Procedures, subprograms, etc.  A Realtime, Online, event
happens and the appropriate files get updated when necessary.  We still
have "Batch" style programs that reads a file and processes each record
(Kinda like your back ground <S36> and all most of ours) but it is less
and less over time.

But to really answer your question,  NO,  What are your standards?
Is the main loop highest in your program, calling low level subroutines
to process each instance?  If not, the answer is still NO.

John Carr
EdgeTech
74711.77@compuserve.com
804-739-7689


----------------------------
Hello,
Quick question.
What are the methods you people use to EASILY and QUICKLY identify the
driver (main input) file within a program?  Does anyone have any neat
way or do you just got to slug down to the Calcs and get at it.  Coming
from the S36 world you would normally easily be able to identify the
driver file of any program just by looking at the F-Specs, but on the
AS400 you will look at a programs F-Specs and see 25 files listed as IF
or UF, so rapidly identifying the driver is tedious.
Am I getting lazy or what?
----
Tim Truax
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---