I dont know if SQL is better but I did work on a system with multi member files.
Multi member files are a total pain, IMO.

In the system I worked on each member represented a different company.
I was asked to fix a problem where the overrides were not properly implemented and one companies data was mixed up with others.

I decided to create multiple libraries, one for each company. Perhaps overkill, but how else could I ensure a fix I could guarantee to work?
I hardly needed no changes to the driving CLs, the overrides worked as usual even though each library had files with only one member.
There was a change needed to set the initial LL for when switching between companies.
Fixed the problem, back to single member files, such a relief.

Frank



On 03/09/2022 5:56 am, Peter Dow wrote:
I'm in favor! (stuck at 7.3 and 7.4).

On 9/2/2022 12:31 PM, Charles Wilt wrote:
Unfortunately, in order to create such a partitioned table, you need the
Db2 Multisystem product installed.
Prior to v7.5, this was a chargeable option that cost big bucks.

With 7.5, IBM now includes it as a no-charge option.
I wonder, for those of us on 7.4 or 7.3, can we ask IBM nicely for a
license key.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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