× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.