× 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.


  • Subject: Re: Accessing files In QTEMP and the utility of multi-memberfile s
  • From: John Hall <jhall@xxxxxxxxxxx>
  • Date: Thu, 19 Oct 2000 16:38:18 -0400

Actually the storing of source code in members of a file is a good
example of the weaknesses of multi member files.  How can you maintain
multiple versions of source code (say by date) on the 400?
Oh and keep them all in one library so that your general ledger is
functionally grouped for operational purposes?  Who created the member,
last accessed, days used, audit trails etc.

How do you, (maybe you can?), allow a user to create / delete a member
without giving them create/delete access to the file?

A member is not quite a file.  It has some of the information/security
on its own but not all.  The 400 limits you to three levels  (Library,
File, Member)  On other computers we would just use another layer of sub
directories.  Everything you can do with a multi member file you could
do with a x-tree in dos 15 years ago.

Sure I use multi member files for some things - Archiving data
transmissions by date.  But I have 3 separate transmissions (diff
Format) so three files with a member for each date.  The more logical
grouping of this would be a separate sub directory for each date with
the three files in it. 


John Hall

Anton Gombkötö wrote:
> 
> What about WRKMBRPDM? :-) OK, it's not a very good example for an
> application, but there's no reason why another program belonging to an
> application might not be able to handle members as well as PDM does.
> 
> Multi-member files are a feature that is good in my opinion. It's not a
> relict or something. It's a feature that puts OS/400 or the DB in a better
> position compared to the rest, and many people in the list are able to use
> this feature to their advantage. There were some techniques described in
> the mails before.
> 
> The only drawback i know is SQL from another platform - but whose fault (or
> perhaps better: weakness) is this?
> 
> Your mail does not explain *why* multi-member files "are a disaster". It's
> just trying to create a mood against it. Trying.
> 
> What are the reasons?
> 
> Please explain, i want to know!
> 
> Mit freundlichen Grüssen / best regards
> 
> Anton Gombkötö
>
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.