|
Actually, let me add in my 0.02 too. (Mark, now you have 4 cents, buying coffee?) I've seen only parts of this thread, so forgive me if I repeat, but here is the other BIG problem with using a "journaling" type solution. I'm sure you don't want a note EVERYtime the customer record is read, do you? You don't want one during the nightly invoice processing run, do you? Or how about all the programs that chain to customer master to get the customer name? Or all the queries/SQLs that run? Etc. I think the only valid solution here is what Dan is suggesting, make the changes to the inquiry programs. At a minimum, on entry to the program get the highest note # for the customer. On exit if the note number hasn't increased then add a new note with text of "Unknown action." or some similar thing. At least you'll then have a note to trigger other events. -Walden -----Original Message----- From: D.BALE@handleman.com [mailto:D.BALE@handleman.com] Sent: Wednesday, September 20, 2000 11:08 AM To: MIDRANGE-L@midrange.com Subject: RE: Was RE: Journaling - Now how Mark, When your phone reps look up a customer on the system, how many *different* applications can the rep inquire from? I'm thinking that all the reps use the same, single inquiry program that does, at least, the initial customer lookup. If that's the case, it would seem you have just one program to modify to do your "journaling" hack - forget about using IBM's journaling for this purpose. Of course, if there's a level of complexity you haven't mentioned, like hundreds of programs that could do the initial customer lookup, then you're back to square one. Just my .02 Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 -------------------- Original Message -------------------- It is a 400 database basically just 4 fields, Customer #, Note (a 60 char field), User name (of who entered note) and a date. What is supposed to happen is that EVERY time someone looks up something on that customer (could be checking order status, change of address, customer called to change order, etc.) they are to put an entry into the Notepad. We need a way to track the "reads" of the customer file (and maybe a couple of others but customer is the biggie) and correspond that to see if a notepad entry was entered for that customer. 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 jt Sent: Wednesday, September 20, 2000 7:36 AM To: MIDRANGE-L@midrange.com Subject: RE: Was RE: Journaling - Now how to find who read Mark, I sure am curious about this Notepad application. I assume it would be too difficult to convert this data to a 400 database, and then analyze the current days changes directly. jt -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Mark Allen Sent: Tuesday, September 19, 2000 11:37 AM To: MIDRANGE-L@midrange.com Subject: RE: Was RE: Journaling - Now how to find who read 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 +--- | 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.