Conference orarep::nomahs::sql

Sounds right to me...

    "Stored procedures (or functions) support null values. As a result you
    *CANNOT* use indicator parameters with stored procedure(function)
    parameters."

	procedure P1 (in :a integer);
	begin
	if :a is null then ...
	end;

	Here :A as a parameter has NULL semantics.  No indicator is required
	nor can it be used.
    
    It continues: ... you must be sure to declare in the nonstored
    procedure that calls the stored procedure, an indicator parameter to
    ensure that you can process the NULL value...

	SQLMOD

	procedure DO_P1 (:a integer, :a_ind integer);
	    call P1 (:a indicator :a_ind);

	SQLPRE
	var
	   a, a_ind: integer;
	...
	exec sql
	    call P1 (:a indicator :a_ind);

	Here the call must provide the null indicator because neither SQLMOD
	nor SQLPRE support parameters or host variables with NULL semantics.
	(actually the 3GL's don't support it)

    Page 13-12 says (under callout 1):
    
    Because parameters in stored procedures allow Null values, each main
    parameter *SHOULD HAVE* a corresponding indicator parameter.
    
    *CANNOT* have or *SHOULD HAVE*?
    
	See the previous example.  If you leave off the INDICATOR clause
	then you can not pass IN a NULL value, and you may get an error
	if you ever pass back OUT a NULL value from a STORED PROCEDURE.

Ian

If examples such as these were in the documentation, it would
help users to understand the (sometimes confusing) descriptive
text.   That would also help reduce the number of such
questions in this conference and other forums.

Any chance we can ask the good doc folks to insert them in the
right places?

Bryan