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



One of the purposes of journaling is auditing who did what to something.

If SYSA has a journaled physical file, and SYSB has a DDM file pointing to that physical file on SYSA, the journal entries on SYSA only show the local job (with user QUSER) and its current user (also QUSER), and the local program (QCNTEDDM), that did something to a record in the physical file.  I would like to capture the remote user, job and program if possible.

So far it doesn't seem possible, or even close.  The information doesn't appear to exist on SYSA, either in the journal entry, or a trigger program's parameters.  I can't add a trigger to the DDM file on SYSB.  There is no exit point on SYSB for a record add/update/delete.

Any ideas?

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /



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.