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


  • Subject: RE: re triggers
  • From: boothm@xxxxxxx
  • Date: Wed, 01 Jul 98 20:04:05 -0400
  • In-Reply-To: <0103750E92EFD111A1DF00A0247D844C2CD6@MANSRV>

We're on V4R2.  I tried this and it didn't work.  I ran it through with
debugging on, and the data structure changed, but not the record.

In <0103750E92EFD111A1DF00A0247D844C2CD6@MANSRV>, on 06/30/98 
   at 11:54 PM, Walden Leverich <walden@techsoftinc.com> said:

>One follow on. I believe this also requires V3R7 or later (maybe V3R6,
>but I don't think so).

>-Walden

>-----Original Message-----
>From: Nelson Smith [mailto:ncsmith@gate.net]
>Sent: Tuesday, June 30, 1998 12:19 AM
>To: MIDRANGE-L@midrange.com
>Subject: Re: re triggers


>If you use the "Before" trigger rather than the "After" side, you will be
>looking at the actual record data that is about to be updated.  Just
>change the fields to whatever you want them to be (in the "after" part of
>the record parameter that comes into the trigger). Then let the record
>update normally.  

>Note: this requires you to use the Allow Repeated Change option on the
>ADDPFTRG cmd.

>boothm@ibm.net wrote:
>>
>> I'd like to do a simple trigger program.  What I'd really like to do
>is to
>> fill in a "timestamp" and a "updated by" field on a record anytime it
>is
>> created or changed, regardless of where it is done.  The physical file
>is
>> in arrrival sequence and unindexed.   It seemed simple enough  - a
>> ADDPFTRG after *UPDATE with a simple program that moved the SDS's User
>> field, and a TIME command into the correct fields, and update.
>> 
>> That was where I realized I was in trouble...  how do I find the
>relative
>> record number that was just processed so I can easily find the correct
>> record?  Or is that the wrong approach altogether?
>> 
>> --
>> -----------------------------------------------------------
>> boothm@ibm.net
>> Booth Martin
>> -----------------------------------------------------------
>> 
>> +---
>> | 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
>> +---



-- 
-----------------------------------------------------------
boothm@ibm.net
Booth Martin
-----------------------------------------------------------

+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.