×
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.
Also, each LFM can reference more than one or *ALL PFM's from one or
more PF's.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, July 18, 2008 10:36 AM
To: Midrange Systems Technical Discussion
Subject: Re: Modernization and multi-member files
Logical files also have members.
ADDLFM FILE(MYLIB/MYLF) MBR(MYLFMBR) DTAMBRS((MYLIB/MYPF (MYPFMBR)))
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/18/2008 11:30 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
Re: Modernization and multi-member files
Simon Coulter wrote:
There is nothing wrong with multi-member files as a solution to a
problem. Not very relational but so what? That's not the only way to
design a database. Multiple members can be handled quite well using
OVRDBF and USROPN. Even SQL copes with them via OVRDBF or CREATE
ALIAS, and multiple members are how Rochester chose to implement
partitioned data files so they can't be all bad.
Just out of morbid curiosity (it doesn't impact anything I'm currently
doing, and I don't really have time to research it) what happens if you
try and create logical and/or join-logical files based on multi-member
physicals?
midrange.com
