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

Hi Dan,

This is a very interesting question. I too have a need for a 'member
event' trigger.

So far the only things  I can find that are of use to me are the member
APIs - eg. QUSLMBR, lists all members in a file to a user space, and CL
command RTVMBRD to obtain member information.

To trigger an event when a member is added, changed, or deleted still
eludes me. I would be nice if IBM would add a data queue to a file,
rather like they do with an output queue. The entry of data into such a
queue would trigger a monitoring program.

I will follow this thread with interest.

Syd Nicholson



Dan Bale wrote:

>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.
>