×
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.
It may not be an issue in your environment but applications can wait
(intentionally) on a message queue to perform some action. Most would
probably use data queues now but there are still apps out there that
rely on messaging.
stephen.a.cochran.lists@xxxxxxxxx 11/26/2008 12:17:18 PM >>>
Al,
Your last sentence stuck home. I took over the IT team here and general
operations were not stable. I've never worked with an application that
was
so high maintenance/needy. I have talked to some other customers but I'm
not
sure how "unique" our problems are yet.
We get MSGWs on some kind of job at least once a week. Most often on
jobs
that are communicating with other services (CC processing, etc), but
also a
decent amount of time on some of the async processing jobs that the
application always has running. These can hold up new orders being
processed
into the system and yet everything else still works so we never hear a
complaint about them.
I don't have enough experience with the as400 and other applications to
know
how common MSGWs are, the feeling here has been that they happen and you
deal with them and move on. I came in with a very different attitude and
asked why the *ell they keep happening? That shouldn't be the case.
Steve
On Wed, Nov 26, 2008 at 1:32 PM, Al Mac Wheel <macwheel99@xxxxxxxxxx>
wrote:
If the software is well written and managed, getting a MSGW on
something
other than an interactive job should be extremely rare ... like once
in a
blue year.
midrange.com
