RE: Trigger library - how is this used?

[rob@xxxxxxxxx]

Have you tried iSeries Navigator?  For instance, when I create a stored 
procedure no object is physically created in that library.  But if I open 
that 'schema' in iSeries Navigator that stored procedure shows up in 
there.  iSeries Navigator retrieves that from QSYS2/SYSPROCS.  Maybe it 
does the same thing for triggers?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"James H H Lampert" <jamesl@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/16/2004 03:14 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

Fax to

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.