Re: RPG SQL and Cursors

You are right if you are speaking about green-screen app. User do tends to
press enter, which will normally cancelled the job. But this usually is not
a big deal becuase interactive job tends to deal with very small volume of
data and user normally will let you know after two or three try. The
problem comes when it is a batch process that process millions of records.
If your SQL all the sudden crap out and the programmer forgot to handle the
SQL code, what the process is going to done next will become very
unpredictable. The best part is that the job will completed successfully.
Then one week later the Accounting department come to you and say they are
missing a few million dollar and they have to close the book this afternoon.



"Alan Campin" <alan0307d@xxxxxxxxx> wrote in message
news:mailman.15538.1290197494.2702.rpg400-l@xxxxxxxxxxxxxxx

<<When RLA/RPG encountered an unexpected error, the
program goes into MSGW and programmer can study the caused of problem and
handle the error appropriately.>>

Except for a little problem called a user. The second they see the error
they press enter and proceed on their happy way.