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



> 1. Add a trigger to a file, specifying a predefined name and library. 2.
> Try looking everywhere on your system for your newly named trigger.
> Find it? 3. Look at the File Description for the file you just added the
> trigger to.  Note the values under the "Trigger Description" section.
> They should reflect your prescribed trigger name and library.  Not sure
> of the value of the info contained here but......

I already have a library containing several triggered files. Neither PDM,
nor WRKLNK, nor DSPLIB could find any objects relevant to the triggering
other than the files, the trigger program they share, nor did WRKLNK find
anything inside the file other than its data member. Neither does a DSPFD
show anything about the trigger other than the program name and which of
the six trigger hooks it's attached to.

On closer examination of the InfoCenter entries for ADDPFTRG in V5R1 and
V5R3, though, I note that starting with V5R1, there appear to be 300
triggering hooks, any of which can presumably be assigned any of the six
flavors, instead of the six fixed triggering hooks, one of each flavor,
that existed through V4R5, which explains why I've never heard of such
things.

Why one would NEED 300 triggers on a file, . . .

--
JHHL



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.