|
Hypothetically, I could have an on-demand process that, with each call, performs the ADDPFTRG command to a file. Now this may seem a little extreme if we're talking about a file in a static library, but keep in mind, this process could be adding a trigger to a file in QTEMP. If I have 300 users executing this process, that would equate to 300 triggers. Just my rational guess....... -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of James H H Lampert Sent: Wednesday, June 16, 2004 4:14 PM To: midrange-l@xxxxxxxxxxxx Subject: RE: Trigger library - how is this used? > 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 -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.