![](//teradataforum.com/imgs/ptdfw1.gif) |
![](//teradataforum.com/imgs/ptdfw2.gif) |
Archives of the TeradataForum
Message Posted: Wed, 06 Apr 2005 @ 13:55:16 GMT
Subj: | | Re: BTEQ call to Stored Procedure |
|
From: | | Spiegel, Phil |
David,
We use stored procedures executed on the mainframe extensively. I'm not sure if this exactly fits your request to abend the BTEQ step that
runs the SP but thought it might help. We run our SPs as exports and include an error code, reason code and return code in the output. Various
edit checks are done in the procedures that might generate a non-zero code such as an activity count of zero or missing and invalid data. The
BTEQ step that executes the procedure always completes with a return code of zero so we wrote a program to read the export file that will abend if
a non-zero return code is passed. We display the error, return and reason codes so that information is easily accessible to Operations and/or the
support person handling the issue.
Phil Spiegel
Technical Consultant
Limited Brands
| |