|
midrange.com
That's a pretty good guess! So you are saying that an 890 (using 16
processors - our current platform for our biggest instance of World)
wouldn't support a like number of OneWorld users as it currently does World
users? Interesting. I'm wondering if that's still true if the iSeries is
the database server and not the application server? OneWorld is
basically batch application, right, primarily hitting ODBC, so why wouldn't
it support a like number of users? It seems the iSeries would have less of
a load using OneWorld than World. We do currently have A/R running
OneWorld on the same platform as the World users, but World is still by far
the biggest user of system resources (of course they have many more users).
I haven't gotten any solid reasons for this statement of direction, er,
hypothetically! It is a "five year plan" - we just bought an 890 that
is supposed to last 3 years, so I assume they are thinking they'll move
everyone in the 2 years after that! Realistically, I don't think that's
possible. "They" might not either, but that's the "direction."
It is my impression that Sun can't touch things like the iSeries LPAR
capability, backup & recovery, etc. Personally, I think the TIMI alone
is reason to stay on iSeries!
Admittedly, I know little about Sun. What are some of the things that the
iSeries does well that Sun doesn't do (and doesn't look like it will do)?
Jeff Carey
"Andy
Nolen-Parkhouse" To: "'Midrange Systems
Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
<aparkhouse@comcast. cc:
net> Subject: RE: Hypothetical
question
Sent by:
midrange-l-bounces@m
idrange.com
12/31/2003 05:40 AM
Please respond to
"Midrange Systems
Technical
Discussion"
Jeff,
I'm not sure that you've given enough information about your hypothetical
situation. Suppose, for instance, that you have a global company running
JDE World and OneWorld at their various locations. Suppose that you have
many instances of World, all of which are required to run on an iSeries.
Suppose that you have a few instances of OneWorld, all using the Sun
Solaris
hardware platform with an Oracle database server. The goal of the company
is to upgrade all of their locations to the currently supported version of
OneWorld and to utilize a common hardware platform in support of those
upgrades.
In upgrading from World to OneWorld, your existing World platforms are
toast. They just won't have the horsepower to support the same number of
users in a OneWorld configuration. In this case, the question you're
really
asking is "What is the most appropriate database server for multiple
instances of OneWorld?" The answer would include hardware/software/support
costs, staffing levels, and all of those other things traditionally
included
in that kind of analysis. If the scenario I describe above is accurate,
(or
close to accurate), then I don't think that it is necessarily a bad idea on
its face. I have to put my iSeries bigotry to the side to say this, but if
your hypothetical company has successful experience running OneWorld on the
Sun platform and does not have such experience with the iSeries, it is
reasonable to consider the Sun platform. You will throw out all of your
existing World platforms anyway.
There are legitimate reasons to go either way, and initial cost of the
platforms is a significant part of the executive decision-making process.
I
would not write off either direction as a bonehead mistake.
Is this close to your (hypothetical) situation?
Regards,
Andy Nolen-Parkhouse
> Say your company had several instances of JDE globally, mostly running on
> AS/400's. Say further that during a global meeting it was stated that
the
> direction of the company was to move from the AS/400 and iSeries to Sun
> Solaris.
>
> What are some key reasons that this would be a bad idea?
>
>
> Jeff Carey
_______________________________________________
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.
The information transmitted is intended only for the person(s)or entity
to which it is addressed and may contain confidential and/or legally
privileged material. Delivery of this message to any person other than
the intended recipient(s) is not intended in any way to waive privilege
or confidentiality. Any review, retransmission, dissemination or other
use of, or taking of any action in reliance upon, this information by
entities other than the intended recipient is prohibited. If you
receive this in error, please contact the sender and delete the
material from any computer.
For Translation:
http://www.baxter.com/email_disclaimer
As an Amazon Associate we earn from qualifying purchases.
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.
