Re: DDM Data Queue using RDB -- MIDRANGE-L

Subject: Re: DDM Data Queue using RDB
From: "D*B" <dieter.bender@xxxxxxxxxxxx>
Date: Mon, 19 Nov 2012 16:57:11 +0100
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

the trigger is fired in multiple jobs and every job would try to connect to the remote system and adopted authority wouldn't switch the user (would be possible by API. easier seems to me to have one job sitting on a local DataQ, running under a profile existing on the remote system, routing all it get's to its local DataQ, to the remote DataQ. Then let your trigger sent, what it wants to the local DataQ.

D*B

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.