SQR Question: Capturing "Command Aborted"?

["Rosteck, Mark" <RosteCkM@DNB.COM>]

Sybase 11.9.2
SQR 4.3.2.1
Windows NT4

Hello,

This is a bit of a newbie question and any help would be greatly
appreciated:

When using an SQR program to process data files and do database
inserts/updates, occasionally a problem such as corrupt data will cause SQR
to exit with a "Command aborted" message (for instance if a to_number()
function accidentally tries to convert a text character), with no simple way
to find out which record caused the problem.

What I would like is to have a chance to record the transaction or record
number that caused the problem before the whole SQR program aborts, or
preferably even skip over the errored record and continue with the
processing.
Is there any sort of general "error trapping" command or parameter in SQR
(similar to the ON-ERROR for SQL statements) which would for instance call
an error procedure before the program quits?  Or can you suggest anything
that would have a similar effect?