Rules For Call Arguments In BTEQ And CLIv2 - Analytics Database - Teradata Vantage

• An output host variable.
• A place holder such as a QUESTION MARK character.
• Any name other than the OUT parameter name specified in the procedure definition.

The following procedure call returns AMBIGUOUS, AMBIGUOUS as the information for the parameters p1 and resutl_1 with the expectation that during the execution phase, additional information will be forthcoming about the type of the parameter p1, which will determine the resulting type of result_1 parameter.

     CALL xsp2 (?, ?);

This following procedure call fails because there is no expectation that there will be additional information about what data type the result_1 parameter should return.

     CALL xsp1 (?, ?);

These examples show variations in the specification of OUT parameter names in a CALL statement issued from BTEQ. They s are based on the following CREATE PROCEDURE statement:

     CREATE PROCEDURE sp2 (OUT po1 INTEGER)
     BEGIN
       SET :po1 = 20;
     END;

In the following CALL statement, the OUT argument name p1 differs from the OUT parameter name po1 specified in the procedure definition:

     CALL sp2(p1);

Result:

      *** Procedure has been executed.
      *** Total elapsed time was 1 second.

The same CALL statement also works if you specify a placeholder character or host variable instead of the explicit parameter specification, as the two following examples show:

     CALL sp2(?);

Result:

      *** Procedure has been executed.
      *** Total elapsed time was 1 second.

     CALL sp2(:tx1);

Result:

      *** Procedure has been executed.
      *** Total elapsed time was 1 second.