Re: At the risk of sounding like an AS/400 rah-rah...

Well, that batch problem is something we have on the AS/400 too.  When we
run our end of day processing, no one can be logged into the system because
if any records are open the cycle won't run.

----- Original Message -----
From: "Wills, Mike N. (TC)" <MNWills@taylorcorp.com>
To: "'Midrange Systems Technical Discussion'" <midrange-l@midrange.com>
Sent: Thursday, January 16, 2003 4:51 PM
Subject: RE: At the risk of sounding like an AS/400 rah-rah...


> I can't believe companies think that 30 servers are better than 1. It is
one
> think if there is speed issues, but obviously there are ways to fix that
as
> well.
>
> -----Original Message-----
> From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
> Sent: Thursday, January 16, 2003 3:14 PM
> To: Midrange Systems Technical Discussion
> Subject: At the risk of sounding like an AS/400 rah-rah...
<snip>
> Everything here is so segmented and siloed, it's ridiculous. Forget the
> 20,000 users. We don't have nearly as many as that, and the servers crash
at
> least once every week or two. AND we can't run production batch jobs until
> our client service center goes down for the day, because of the negative
> impact the batch jobs have on the service center screens. It's crazy to
have
> to stay late to run these jobs. That's what queues and schedulers were
> invented for. I am taking a backwards step that I don't like.