RE: SQL VIEWS over multi-member files -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: SQL VIEWS over multi-member files
From: Rob Berendt <rob@xxxxxxxxx>
Date: Wed, 14 Aug 2019 15:33:42 +0000
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@lists.midrange.com?subject=help>
List-id: RPG programming on IBM i <rpg400-l.lists.midrange.com>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

1) I'd argue that unless your software vendor just insists on using multi member files that there is ALWAYS a way around it instead and stop using them.
2) If cash is absolutely not a problem you could look at DB2 Multisystem. This allows multiple member (aka partitions in DB parlance) tables.
3) To point a view at a particular member normally requires you to do a OVRDBF prior to executing the CREATE VIEW statement.
4) See also the CREATE ALIAS. This allows you to reference a specific member. IDK if you can build a view over an ALIAS.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

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