And that's one of the landmines I was referring to in an earlier post.
Recovery Disaster....

My perennial favorite though is the developer that wanted access to
production data without copying it, so they create a logical in the
development library attached to the production file. Achieves the primary
goal. Then about 2 weeks later they create a program to manipulate that
data in some way thinking they were using test data, compiling into the
developer library, except the compiler picks up the logical pointed at
production. The developer tests the program which by mistake
deletes/updates lots and lots of records, in production. BAM landmine
going off.

Moral of the story is just don't do it......

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On Thu, Oct 21, 2021 at 10:59 AM Steve M via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I agree with Paul, but my all-time favorite, Richard, is the notorious
Join Logical that's in Library A using once file from Library B and one
file from Library C. Not enough head scratching in the world to understand
why on that one.

Steve M.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Sent: Thursday, October 21, 2021 10:49
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Logical files not in same library as physical files

Cross-library logicals are right up there with multi-member physical
files. You can, but you'd better have a VERY good idea!

Biggest issue is saving and restoring-- the connection from the LF to the
PF is like a rubber band-- you can stretch things all over the place when
you move the LF around, but it still connects back to the original PF.

Best idea I've come up with is moving the LF back to the PF's lib, do your
save/restore, then move the LF back where you want it.

--Paul E Musselman


-----Original Message-----
From: Midrange Systems Technical Discussion
Sent: Oct 21, 2021 11:10 AM
To: Midrange Systems Technical Discussion
Subject: Logical files not in same library as physical files


I know that we can create logical files in different libraries than the
physical files, but I don't like that idea. What are your thoughts as to
the advantages/drawbacks of the multi library approach?

All the best,

Richard Reeve

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related

Help support by shopping at with our affiliate

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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