Re: system event trigger whenever a source file member is updated

V5R1 came out with new triggers and related stuff:
- a trigger based on just a column.  So they can change any field except
the one you care about and not invoke the overhead of the trigger.
- a list of all triggers on your system, created by SQL or not.  Look in
QSYS2 for SYSTRIG*.
- And, maybe what Dan is looking for:  An SQL statement level trigger.
Traditionally they were row based.  You delete/change one row and your
trigger is called once.  You delete/change 10 rows and your trigger is
called 10 times.  Now you can set up statement based and your trigger would
be called once for the 10 deletes/changes.
http://publib.boulder.ibm.com/html/as400/v5r1/ic2924/info/db2/rbafzmsthctrigger.htm#HDRHCTRIGGER
But I can't seem to prompt this in STRSQL.  I suppose that is another PMR
to open :-(

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "Dan Bale"
                    <dbale@samsa.com>         To:     <midrange-l@midrange.com>
                    Sent by:                  cc:
                    midrange-l-admin@mi       Fax to:
                    drange.com                Subject:     system event trigger 
whenever a source file member is
                                               updated

                    03/12/2002 06:07 PM
                    Please respond to
                    midrange-l






Am looking for a system event trigger of some sort that would tell an
application that a file's member has just been updated, deleted, or added.
All physical files, all members.  Specifically, all *source* physical
files.
I would be happy to know this at the file level, i.e., a "member event" has
just occurred on file DJBLIB/QSRC; then my app would interrogate the file
to
see which member(s) have just changed, or been deleted or added.

The idea behind all this is to utilize a WRKMBRPDM type tool (which I've
built and named FSM) that isn't limited to showing members for a single
library.

Currently, I run:
  DSPFD FILE(*ALL/*ALL) TYPE(*MBR) OUTPUT(*OUTFILE) FILEATR(*PF)
each night, and my FSM derives its member list from that.  This is
sufficient 99% of the time, but the other 1% has been known to burn me here
and there, as members get created, deleted, moved, etc.

Had high hopes pinned on journaling the QADBXREF file but, unfortunately,
the change timestamp does not get updated for any member event.  I could
still journal it to determine when source files are added or deleted.

There's just gotta be a system-maintained member-based file somewhere.  A
user-space maybe?  How does DSPFD TYPE(*MBR) gather its data?  I would be
willing to utilize an "unsupported" reference.

Leif, do you have something on this in your e-book?

TIA,
- Dan Bale



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.