Re: Question concerning the RPG command DELETE(e)

Perhaps the commitment control is being used and the delete is rolled back?

Could a trigger program prevent the delete without signaling an
exception (note I don't know if its even possible)?


Only two things I can think of off the top of my head...

Note BLOCK(*NO) doesn't apply when updating/deleteing.

Charles

On Tue, Sep 29, 2009 at 3:57 PM, Alan Shore <AlanShore@xxxxxxxx> wrote:

Afternoon everyone

I have in a program, the following commands

c                   delete(e) telr
c                   if        %error
c                   goto      more
c                   endif

Does anyone know if there are in fact some errors that the above would NOT
catch

(Please - the goto is my act of desperation, and I usually don't use them,
but like I said, these are desperate times)

The situation is that the delete is NOT happening, but neither is the error

If anyone has any ideas, it would be MUCH appreciated

P.S. This program has the file defined as BLOCK(*NO), so from what I can
tell, the delete should be as instantaneous as possible, and not held in
the buffer.
P.P.S. I almost forgot - we are on V5r4 if that means anything


Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.