Many LFs each with an access path attached is bad and you are right, before the days of the system automatically sharing an access path you could kill a system real easy doing what we are doing but shared access path has taken care of that.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, March 13, 2008 8:14 AM
To: Midrange Systems Technical Discussion
Subject: Re: Are we insane? Unique use of native DB2
I did see a vendor application where they accessed only by the logicals.
The original LF may have had all fields. As the file got Y2K'd the
original LF only held the same fields as it used to. Granted, the dates
were shrunk back down to 6 characters or numbers so that existing programs
that touched this didn't need to be recompiled. If you wanted the full
dates, etc, you used one of the newer logical files.
However, they didn't use a separate LF on each program. I can still
remember John Sears lectures on the evil of too many LF's. Then I
remember an artical in iSeries 400 Experts Journal by Skip M that most of
the overhead of all those LF's was pretty much done away with several
Group Dekko Services, LLC
Kendallville, IN 46755
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