RE: SQLCODE -907

[Scott Mildenberger <Smildenber@xxxxxxxxxxxx>]

Are you using the trigger buffer in your trigger program?  If you make your
trigger *before *insert and alwrepchg(*yes) then you can just update the
buffer to change the record before it hits the database.  That is what I do
whenever a trigger has to change the record that is being inserted/updated.

Scott Mildenberger

> -----Original Message-----
> From: tomh@simas.com [mailto:tomh@simas.com]
> Sent: Wednesday, March 13, 2002 9:58 AM
> To: midrange-l@midrange.com
> Subject: RE: SQLCODE -907
>
>
> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Not a red herring, but doesn't really help either.  The
> trigger time is
> *AFTER, trigger event is *INSERT.  We use SQL to 'INSERT
> INTO' the file,
> which causes the trigger to run, which in turn runs the program, which
> updates a field in the row we're inserting.
>
> On the SQL 'INSERT INTO' - if we use 'WITH CS' (isolation
> level: row is
> locked until end of current transaction) at the end of it, we get the
> SQLCODE -907.  If we leave the 'WITH CS' off, we get no error and the
> files are updated like we want but a ROLLBACK does nothing.
>
> What we want is to set an isolation level and not get the -907, and be
> able to do a ROLLBACK.  How do we accomplish that?  Do I need
> to post the
> C program to show how the files are being updated?
>
> Tom Hightower