Re: Trigger job -- RPG400-L

Subject: Re: Trigger job
From: CRPence <crpbottle@xxxxxxxxx>
Date: Sun, 31 Jan 2016 15:32:04 -0700
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 19-Jan-2016 13:55 -0700, Englander, Douglas wrote:

Does anyone know if there is a way to capture any job information of
the job or program that is causing a trigger to execute? Can that be
captured somehow (in the trigger buffer) when the trigger program
gets called, so I can track what program or job is writing/updating a
record?

Might journaling the database TABLE [aka: DB physical file] be sufficient; i.e. perhaps no trigger program is even required? Use the Start Journaling Physical File (STRJRNPF) to effect the "capture", and then perform a review of the journal data via the Display Journal (DSPJRN) to "track" [down] the jobs\programs that performed any of the update\insert\delete I/O activity?

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.