Re: Track all records read from a table -- MIDRANGE-L

Subject: Re: Track all records read from a table
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Tue, 22 Mar 2016 13:51:54 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 3/22/2016 12:57 PM, Nathan Andelin wrote:

Except we use shared memory between the trigger
program and an external JOB which we call a database event handler to pass
record buffers, which is even faster than a data queue.

Can you share the mechanism you've chosen for sharing memory between two
jobs?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Track all records read from a table , Nathan Andelin

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.