Re: Update or delete without prior input operation -- RPG400-L

Douglas,

C     DVNDNO        CHAIN     PAYABLES
C                   DOW       NOT %EOF


CHAIN does not set %EOF!!

CHAIN does not set %EOF on if no record is found. So this code isincorrect. This loop won't even be entered if the previous READ or READEoperation hit the end of file. Even if the CHAIN succeeds, it will neverenter the loop. Furthermore, if the CHAIN fails, it'll still enter theloop because CHAIN doesn't set %EOF!


You need to either do this:

  C     DVNDNO        SETLL     PAYABLES
  C     DVNDNO        READE     PAYABLES
  C                   DOW       NOT %EOF

Or this:

  C    DVNDNO         CHAIN     PAYABLES
  C                   IF        %FOUND
  C                   DOW       NOT %EOF

C                   READE     PAYABLES

Here you're reading a file that you just CHAINed to. That means, youskipped a record -- the one you read with CHAIN a moment ago will never beprocessed.

C                   IF        DREFNO = PREFNO
C                   DELETE    PAYABLES
C                   UPDATE    PAYABLES
C                   ELSE

Here you've just deleted a record. That record is no longer there! Nowyou're trying to update it? How can you update it, if it's no longerthere?

Even if you put the UPDATE before the DELETE, it wouldn't work becauseyou'd release your record lock the moment you update it, so the deletewould fail.

Not to mention that the whole idea of deleting a record you just updatedmakes no sense. Why update something you no longer want?

I am chaining to the file with no problem and I need to stay within the key
(which is why I am using the reade), I am checking for a specific refno and
if I find it I need to delete it, but the system is complaining that I have
not performed an input operation....I would have thought the reade performed
that, what is the proper way to handle this?

That's because you did a DELETE after the READE. When you try to updateit, you'll get the "need an input operation" error because you have toread a different record before updating it. As soon as you do an updateor delete, you lose the record lock, and you have to read again beforeissuing the next update or delete.

Not to mention that it makes absolutely no sense to delete a record andthen try to update it. OR update a record and then delete it. If youdon't want the record, just delete it. No need to do an update.