Re: Identifying the driver? -- MIDRANGE-L

× 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.



> 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?

you'd have to look at the calcs.

nj

+---
| 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
+---

This mailing list archive is Copyright 1997-2025 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.