Re: Putting current date/time into D/T/Z fields

[Pete Hall <peteh@xxxxxxxxxx>]

At 07:39 PM 7/8/98 -0400, Booth Martin wrote:
>What I have done is set a trigger on the physical file which calls a
>program that:
>
>  a) MOVEs the USER field from the System Data Structure to a 10-character
>field in the record, and 
>
>  b)  does  TIME to the Z data field, for a date&time stamp. (by the way,
>this is both date and time.)
>
>By doing it this way I should be able to ignore all further dealings with
>timestamping records in this file, or its logicals, right?

I'll bite. I'd say this is true.


>  This works well excepting the other question I intended to ask tonight:
>
>I can set a trigger for  insert, change, and delete.  Insert does not seem
>to be the same action as Adding a record?    Is "insert" different than
>"add"?  Or am I just not doing it right yet?

Insert is the same as "add". In this case, the original record image should be 
ignored, as should the new record image for a delete operation. Have you run 
ADDPFTRG for both update and insert? You can have separate trigger programs for 
each of the possible trigger time/operation values, so you need to run ADDPFTRG 
once for each time/operation that will cause your program to be called. While 
you're at it, have you set the update trigger's TRGUPDCND parameter to *CHANGE 
so that the trigger is only executed if the user actually changed something in 
the record? The current trigger settings can be checked with the DSPFD command.

Pete Hall
peteh@inwave.com 
http://www.inwave.com/~peteh/

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---