×
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.
From what I remembered,
1 - It wasn't cheap.
2 - People who use multimembers tend to want to have control over the name
of the name of the member and do not want to put a column in the table
like MemberName and have that column in every row.
With DB2 MultiSystem you tell it how it should determine what member to
place the data. You may say stuff like if year of date field is 2008 then
use member 2008 or some such thing. If you are writing an invoice batch
setup then you would say put the name of the batch as a column in the
table (or field in the file) and use that to determine the member name.
Seems to me if you're going through all that, then why use members instead
of the extra column in the first place?
Rob Berendt
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.
midrange.com
