|
Bob, The journal shows the name of the program that actually did the physical write/update/delete. In your case, this is the Opticonnect transaction program. Not your application. Journaling does not know anything about Opticonnect (I suspect). Besides, if a program could spoof journaling, what would stop any program from spoofing it? Regards, Bob Crothers Cornerstone Communications, LLC www.faxserver401.com -----Original Message----- From: Bob Larkin [SMTP:blarkin@wt.net] Sent: Saturday, August 22, 1998 12:46 AM To: MIDRANGE-L@midrange.com Subject: I need your vote on this... << File: vcard.vcf >> This question concerns Opti-Connect, but your opinion would be appreciated, even if you are not using it. Opticonnect is the mechanism one of my clients uses to cluster several AS/400s. Data resides on machine A. Programs, Display Files, other small objects on Machine B, Machine C Mirrors data from A, and is used as a query machine. Here is the baackground on the question. A program on Machine A writes/updates/deletes a record on Machine B. This is done thru Opti-Connect using it's smoke and mirrors. Later, we look in the journals on Machine B, and find the record we just wrote/updated/deleted. When we look to see which program did the file I/O, we get the name of the IBM program that wrote the record for OptiConnect, not the name of our application program. My question...... Should the Journal contain my applications name, or the IBM programs name? We use these journals for diagnostics, among other things. Since we have files being updated by multiple applications, on multiple machines, seeing the Application Program's name, instead of the IBM program, would be helpful. Any opinions? TIA, Bob blarkin@wt.net +--- | 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 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.