|
I thought about journaling but the file is our Order file and it's constantly being updated. The journal will get quite large quickly. I only want data in the file when I know I have found a problem. And, I may still go with journaling. Especially since it looks like the information I'm looking for isn't available without it.
Thanks for your input.
______________________________________________________________________________________________
Randy Kesterson, Information Services
Market Transport Services - a UTi Worldwide Company| 110 N Marine Drive | Portland, OR 97217 | USA
rpkesterson@xxxxxxxxxxxxxxxxxxx | D +1 503.978.4353 | O +1 503.283.2405 x353 | F +1 503.978.4392
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob P. Roche
Sent: Thursday, March 05, 2009 6:59 AM
To: RPG programming on the IBM i / System i
Subject: Re: Calling Program information
Why not just journal the file? It gives you program name, user, time, all
sorts of useful info for this type of problem.
From:
"Kesterson, Randy" <RPKesterson@xxxxxxxxxxxxxxxxxxx>
To:
<rpg400-l@xxxxxxxxxxxx>
Date:
03/05/2009 08:53 AM
Subject:
Calling Program information
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx
Does anyone know if any of the "Information" data structures has the
name of the program, if any, that called the program you're in?
I'm going to put a trigger on one of the files in our system to save a
record in a separate file anytime a record is deleted or a specific
field within a record is blanked out. I'm tracking down the cause of
two separate issues here and it would be nice to be able to add a field
to the saved record that says what program called, or caused, this
trigger to run.
Thanks,
________________________________________________________________________
______________________
Randy Kesterson, Information Services
Market Transport Services - a UTi Worldwide Company| 110 N Marine Drive
| Portland, OR 97217 | USA
rpkesterson@xxxxxxxxxxxxxxxxxxx <mailto:rpkesterson@xxxxxxxxxxxxxxxxxxx>
| D +1 503.978.4353 | O +1 503.283.2405 x353 | F +1 503.978.4392
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
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.