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



No conditions are stated. That's what I meant. When not stated, we cannot
assume they belong.

You could be mistaken.
I could have chosen water.
We all could stop this madness.

None of those are conditional, as far as I know.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"United Nations: Where America feeds the hands that bite it."
-- Gregory Nunn


LOL - maybe I've been reading too much Richard Lederer of late -
Father's Day present from number one son!

Anyhow, seems to me that "you could" has always been conditional - it's
subjunctive, just as "would" and "should", albeit with different
intensity in different constructions.

Whew!!

Vern

On 6/29/2010 12:15 PM, Wintermute, Sharon wrote:
Apparently I changed it. :)

Sharon Wintermute


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Tuesday, June 29, 2010 12:10 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Utility to remove and re-add logical file members

Sorry, Sharon, I didn't see the word 'consider' anywhere below.
(Still
don't.) I saw 'you could,' which sounds unconditional, and which is
why
I
replied thus.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"There is a theory which states that if ever anyone discovers exactly
what
the Universe is for and why it is here, it will instantly disappear
and
be
replaced by something even more bizarrely inexplicable.

There is another theory which states that this has already happened."
-- The Hitchhiker's Guide to the Galaxy



That is one reason why I said consider it. Every shop has different
standards, so what works for one does not necessarily work for all.

Sometimes, a hint of a different approach is all someone needs to
reconsider their path.


Sharon Wintermute


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis
Lovelady
Sent: Tuesday, June 29, 2010 11:24 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Utility to remove and re-add logical file members

That's a good idea, Sharon, but MAINT(*REBUILD) is not an option
when
UNIQUE
is involved. So there is some merit to the approach depending upon
how
things are set up. Some installations that don't really understand
database
but are put in the position of designing for i have UNIQUE on
(almost)
everything.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Dear Lord, please make me the kind of person my cats think I am.



Rather than remove the members, you could just change the LF to
maint(*REBLD) instead of removing the members.

Then once you are done with the reorg, change them back to
maint(*Immed).

This way you don't lose the based-on member info. I have seen this
cause a problem when the logical is based on multiple physical

members.

Re-adding logical members isn't fun for multiple physical members.

Plus, if the LF has multiple members, its not fun either.



Sharon Wintermute


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



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.