I didn't see a post for B, so here is mine:
Inside your trigger routine, use SYSTEM(49) to dump the program stack.
@LOGNAME will give you the user running it. Report them in a fashion
most helpful to you, e.g. write it to a log, send an email, etc.
SYSTEM(51) may also be helpful.
In unidata:
1. Before image you could just read the record from the file.
2. After image is what's in the record parameter passed into the trigger
subroutine.
3. You need different subroutines for the BEFORE UPDATE trigger and the
BEFORE DELETE trigger, as they take different numbers of
PROTECTED] On Behalf Of Dave Davis
Sent: Wednesday, June 27, 2007 1:34 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Trigger help
In unidata:
1. Before image you could just read the record from the file.
2. After image is what's in the record parameter passed into the trigger
subroutine.
3
