SQL Stored Procedures - Call-Level Interface Version 2

Teradata Call-Level Interface Version 2 Reference for Mainframe-Attached Systems

Product
Call-Level Interface Version 2
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-07
dita:mapPath
jen1488824663137.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

The application sends the statements composing a procedure to the database, where they are compiled and saved for subsequent execution. The application that creates the procedure must do the following:

  1. Ascertain whether the Teradata Database supports stored procedures.
  2. Send a request containing the procedure that could exceed the maximum parcel size.
  3. Provide compilation options to the database.

To ascertain if the Teradata Database supports stored procedures, the DBCHQE CLIv2-limits query (or the deprecated Maximum-segment-size query) is used. If the segment length value returned by CLIv2-limits is zero, then SQL Stored Procedures are not supported (the deprecated Maximum-segment-size query will fail with a return code 359 if such procedures are not supported).