|
Method for ensuring consistent Customer Service. Any time a customer service rep speaks to a customer or a sales rep they are Supposed to put an entry into our Notepad application. We want to do some checking to make sure that is happening, i.e. they looked at, did something (if they update yes the file is journal led, no commit control). have considered the option of opening for update but that would mean changing some underlying logic and lots of programs...... Mark Allen IS Manager Kelly's Kids markallen@kellyskids.com -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Cherryman, Oliver Sent: Tuesday, September 19, 2000 8:52 AM To: 'MIDRANGE-L@midrange.com' Subject: RE: Was RE: Journaling - Now how to find who read Please explain why do you need to know what was read in the first instance ? What's the business practice ? Are your files already journalled ? If so do your applications use commitment control ? Have you considered reading the file in update mode and doing a (dummy) update immediately afterwards to create a journal entry, or trigger a trigger program ? Regards Oliver -----Original Message----- From: Mark Allen [mailto:markallen@kellyskids.com] Sent: 19 September 2000 14:45 To: MIDRANGE-L@midrange.com Subject: RE: Was RE: Journaling - Now how to find who read Thanks but I need to know what record was read (i.e. Customer Master Key=1234567, etc.) Mark Allen IS Manager Kelly's Kids markallen@kellyskids.com -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Rob Dixon Sent: Monday, September 18, 2000 9:24 AM To: MIDRANGE-L@midrange.com Subject: Re: Was RE: Journaling - Now how to find who read Mark If you journal with OMTJRNE(*NONE) , then your joiurnal will record will record any opens and closes of journalled files. However, it does not tell you which records in a file were read only those which were changed. > Since this has come up here and I have been trying to find a "simple" way > (i.e. like journaling, no program changes) to find out who has "read" a file > and since Simon brought it up in his reply, does anyone have an idea of how > to in essence "journal" read op's??? Best wishes Rob ________________________________________________________ Erros plc 44 (0) 1844 239 339 http://www.erros.co.uk - The AS/400 Neural Database for the Internet _________________________________________________________ +--- | 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 +--- +--- | 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 +--- +--- | 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 +--- +--- | 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.