RE: SQL update vs RPG/DDS update

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Gene Burns
>
> I see that I should have added more documentation with the code.

No, not really.  I don't actually care what the rest of the program is
doing, because there is only one line of code where your hypothesis can be
correct.  That is, after the CHAIN where the record is locked.  At that
point, the data in the mstrDS data structure MUST match the data in the
file.

Anything else is probably a logic error, and what you need to do is start at
a known bad point and walk backwards until you discover the point where your
data changes incorrectly.

So at what exact point in the code does a data structure contain data that
doesn't match your expectations, and why?  Tell me the exact sequence of
events of I/O instructions and moves to the data structure, and then tell me
what you expect and what you see, and exactly where in the code you are.


> Deletes are not allowed on this file, so there was no need to check the
> found condition.  If you got this far the record is known to exist.

Uh.  Yeah.  That's an awfully big hole to drive logic trucks through.  But
again, answer my previous question.

Joe