I have built system with field select logicals and they performed
wonderfully and I had my database independence. Need a new field. Just add
The problem, without a tool, development and maintenance was a bear. You
had to create a logical for every table in a program and you only had 10
characters to describe it that left you with something like GL0001_L01,
GL0001_L02, etc and try to remember what is what.
If you build a tool that lets you pick the file or files that you need,
then the fields and finally an existing index and have it generate a field
select logical, a data structure and update a very fast table (User Index?)
under a name you gave it. You then have a service program that has methods
for Opening, Close, Read, Write, etc. That service program only has to open
the field select logical and when it gets a record (Maybe using RLA in C?)
it just need to move the record into the buffer.
Anyway, that is my idea but again SQL does it all plus a ton more so why
On Fri, Apr 25, 2014 at 2:34 PM, John Yeung <gallium.arsenide@xxxxxxxxx>wrote:
On Fri, Apr 25, 2014 at 4:14 PM, Chris Bipes
Could not say for sure why it is a bad idea.
But it was *your opinion* that it was a bad idea:
On Fri, Apr 25, 2014 at 3:27 PM, Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>
That is exactly why programmers created Logical Files with just the
they needed for their program. You could change the physical but the
logical would remain unchanged. In my opinion that was a bad idea.
Are we talking about two different ideas, one of which is bad in your
opinion, and another which you are more on the fence about?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives