|
Sorry, perhaps I was not "clear"; I do NOT want to change the contents of the *FILE (PF), only the data in the "buffer" that is going to be returned to the actual application that issued the "read" (which caused the trigger to "fire"...). Mark ----- Original Message ----- From: "Booth Martin" <Booth@MartinVT.com> To: <midrange-l@midrange.com> Sent: Friday, November 22, 2002 10:06 PM Subject: Re: Anyone using the *AFTER *READ Triggers in V5R1/V5R2? > > By definition, wouldn't READ be limited to read? I'd think you might call > another program that would change the file though? > > (Have you looked at the *UPDATE and what *ALWAYS/*CHANGE does?) > > > --------------------------------------------------------- > Booth Martin http://www.MartinVT.com > Booth@MartinVT.com > --------------------------------------------------------- > > -------Original Message------- > > From: midrange-l@midrange.com > Date: Friday, November 22, 2002 11:39:44 PM > To: midrange-l@midrange.com > Subject: Anyone using the *AFTER *READ Triggers in V5R1/V5R2? > > Hello, all: > > Has anyone used the "native" *AFTER *READ triggers that were > introduced with V5R1? > > I tried using one, but no matter if I change data in the "original" > buffer or the "new" buffer, it does not seem to matter; the actual > data from the file is ALWAYS (apparently) returned to the calling > program, regardless of what the read trigger does. > > What the heck good is a read trigger if there is no way to alter > the data in the buffer? I mean, after all, you can alter the data > in other cases, such as an Insert or Update trigger, right? > > Thanks, > > Mark S. Waterbury > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > . > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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.