• Subject: RE: Client/Server Applications - what to use?
  • From: Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>
  • Date: Wed, 30 Aug 2000 09:23:34 -0700

We are also moving from remote DQ via VB and CA to sockets.  Some
applications call the validation programs while other send to a DQ for
transaction processing.

Our main business is retail point of sale transaction processing and based
on a DQ.  This allows us to run multiple interfaces, communication programs,
into one queue with multiple server processing from the queue.

Our dedicated transaction processing systems can process 100 or more queue
entries per second.  They are keyed FIFO where the interface program send to
the DQ with a key value of zero, and waits for a response with the key value
equal to its job number, which is passed in the original queue entry.  This
give us the flexibility to change the application and re-set it with out
disrupting/resetting any communication jobs.  The servers read the next
entry with a key value of zero, FIFO.  If an entry was on the queue for more
than 3 seconds, we start another occurrence of the server.  If a server
times out, we start ending them.  We have a control data area that hold the
value of the minimum and maximum number of occurrences to be running.

This has been running without IPL for over a year at a time, on a CICS at
3.2 8>)



Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Gary R. Patterson [mailto:midrange-l@nexsource.com]
Sent: Wednesday, August 30, 2000 7:16 AM
To: MIDRANGE-L@midrange.com
Subject: RE: Client/Server Applications - what to use?


I think the "best" way depends on data volume and number of users.  For low
volume applications where response time and throughput are not essential,
xDO is easy.  Our experience has been that as volume increases, application
performance degrades.  Maybe recent releases are better.

Data queues are pretty fast and lightweight, but not portable.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.