When ECRTP encounters an error, it produces a status file - status.in for inbound maps or status.out for outbound maps. The user can quickly and easily check to see whether errors occurred during a map run by checking for the existence of a status file. If no status.out or status.in file exists in the executables directory, then no errors occurred. If a file does exist, it contains an error code with an error count. The chart below lists the definition of each of the possible error codes. The creation of status.in and status.out can be turned off with the -ef switch. In addition to creating a status file, ECRTP exits with a numeric return value. See the table below for the meaning of the return values:
Return value |
Error code |
Definition |
|---|---|---|
0 |
Wrote ST or SE |
No errors |
1 |
W## - ## |
Errors but no transaction skipped |
2 |
BADTRAN W## |
Transaction skipped with ## errors |
3 |
UABORT W## |
User Abort Rule with ## errors |
4 |
USTOP W## |
User Stop Rule and ## errors |
5 |
EFATAL W## |
Fatal error stop and ## errors |
When application programs are linked to the RTP DLL files, no status file is produced. However, the status of the inbound or outbound run is returned to the calling program as a number (0 thru 5). This number corresponds to a return value in the chart above - the same value that is returned by the executables.
