The UDS online utility evaluates the status codes of the procedure commands which are sent to the DBH and in some cases responds to these.
If it can be recognized from the status code that a transaction has been terminated, subsequent DBH commands are not executed until the next READY within the same procedure cycle.
The predefined variables RCODE and STATUSCODE (see section “Predefined variables”) are initialized immediately before a DBH command is executed.
The following status codes result in the procedure aborting:
020, 022, 042, 092, 093, 099, 103, 113, 123, 131, 132, 134, 136, 137, 142, 144, 145, 146, 151, 152, 154, 155, 161, 163, 165, 166, 782, 783, 784, 785, 786, 789, 805, 901, 950, 954.
In all these cases a fault exists which is expected to be encountered again if a procedure cycle is executed again without additional measures being taken. The procedure is generally aborted only at the end of the current procedure cycle.
DML requests up to the end of the current procedure cycle are suppressed if it is clear that no further transaction is open. Other procedure requests (e.g. MOVE, SHOW, WAIT) are still executed until the procedure cycle ends.
In addition, status code 162 may occur during the execution of the DML FPASCAN, which also results in the procedure aborting.
A detailed description of the status codes is provided in the ”Application Programming” and “Messages” manuals.