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



I wrote an application that used DDM data queues.  A program that performed 
database I/O was hosted on one AS/400 while a program that performed browser 
I/O was hosted on another.  The programs communicated via DDM data queues.  
Performance and reliability was okay, but not optimal.  There's latency 
associated with intersystem communication, and you're adding an extra point of 
failure to the architecture, and extra configuration steps, even though DDM 
makes it appear fairly seamless during runtime.
 
Distributed architecture has become so prevalent in the Wintel and J2EE worlds 
that people just assume it must be good.  It isn't, really.
 
Nathan M. Andelin



----- Original Message ----
From: Michael Ryan <michaelrtr@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Saturday, December 2, 2006 8:09:13 AM
Subject: Re: Using two boxes to share the load via ddm files


I've used and am using a fair amount of DDM - more than I'd like actually.
I'm currently using DDM over SNA (AnyNet). The performance is adequate - not
quite as good as being there, but acceptable. Once thing to be careful of is
how you make and break DDM connections. For instance, you have a client
program on system A communicating with a server program on system B.
Accessing data from remote system B is going to be pretty fast - as fast as
DDM and Anynet allow. Now take 300 client programs accessing system B.
Things will slow down appreciably, because basically you have two ways of
handling conversations - keep the conversation going, even if there's no
session; or drop the conversation when the session is done. The first way
causes the number of available modes to be used up, causing timeout errors
The second way is slower because of the dropping. We had a problem with the
first method and moved to the second. It's slower, but it works.

You might also look into data queues between the systems or remote SQL using
CONNECT TO. These will impact the system, but not as much as several client
programs accessing a remote system.

On 12/1/06, Rick DuVall <R_C_DuVall@xxxxxxxxxx> wrote:


 
____________________________________________________________________________________
Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.