×
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.
In addition to all of the other reasons people have posted... I find
that I can keep things much better organized in an IFS directory
structure. The fact that you can nest subdirectories within
subdirectories gives you more flexibility when organizing your code.
Granted, if you have only one source member, there's no benefit.
But let's say you have an order entry application -- a particular
software product you sell/distribute/whatever. Within order entry there
are 10 programs/service programs. Within each program you might have
multiple members for the RPG source, display file source, print file
source, CL source for overrides, whatever else... Within each service
program you'll have a copy book for prototypes et al, the main source,
maybe multiple modules... the list goes on.
For me, it's more convenient to organize as:
OrderEntry/program1/mainsrc.rpgle
OrderEntry/program1/ovrsrc.clle
OrderEntry/program1/displaysrc.dspf
OrderEntry/program1/printsrc.prtf
OrderEntry/srvpgm2/copybook.rpgle
OrderEntry/srvpgm2/mainsrc.rpgle
etc, etc... the ability to easily nest directories within directories
just makes things cleaner in my mind. Granted, you could have an
ORDERENTRY library with separate source PFs for prgoram1, srvpgm2, etc,
so this probably wasn't the best example... but the fact that you can
easily create subdirs on a whim and nest them as deep as you like can
make it much easier to manage. My opinion.
Bob Cagle wrote:
This begs the question - why would you store your source on the IFS? I
know it can be done, but I'm curious as to why? What are the benefits?
midrange.com
