Just a note - if the command contains a CALL to a stored procedure, do not
use the SQLCODE - it will contain the result of the stored procedure and not
of the command. So if the command completes successfully but an embedded
stored procedure finds no rows, the SQLCODE will report a 100, not a 0. Use
the RBase error variable instead which I believe captures the command's
response.
----- Original Message -----
From: "Bill Downall" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 09, 2001 5:05 PM
Subject: Re: WAIT TIME IN COMMAND FILES
> Dan,
>
> Immediately after the important commands, you can check the
> SQLCODE variable for normal completion. If SQLCODE = 0, the
> command completed normally. If SQLCODE = 100, the command
> completed, but no rows were found, or the command had no effect,
> which is really the same thing.
>
> Many applications do this:
>
> UPDATE ...
> IF SQLCODE <> 0 THEN
> -- take corrective action, logging or looping or exiting
> ENDIF
>
>
> On Thu, 9 Aug 2001 08:55:27 -0700, Dan Goldberg wrote:
>
> >I read that if a command runs as part of a command file and the
> waiting period expires, R:BASE ignores the command and goes on to
> the next command.
> >
> >Does anybody know a command to detect if the wait period expired??
>
>
>
>
