Re: SQL Indicator Arrays

Here is a bit from the documentation on what are the uses of an SQL indicator variable - what else they are about -

An/indicator variable/is a halfword integer variable used to communicate additional information about its associated host variable.

* If the value for the result column is null, SQL puts a -1 in the
indicator variable.
* If you do not use an indicator variable and the result column is a
null value, a negative SQLCODE is returned.
* If the value for the result column causes a data mapping error, SQL
sets the indicator variable to -2.

You can also use an indicator variable to verify that a retrieved string value has not been truncated. If truncation occurs, the indicator variable contains a positive integer that specifies the original length of the string. If the string represents a large object (LOB), and the original length of the string is greater than 32 767, the value that is stored in the indicator variable is 32 767, because no larger value can be stored in a halfword integer.

I had not read up on the truncation thing - interesting!

Cheers
Vern

On 11/18/2016 10:37 AM, Peter Dow wrote:

What else is it about? A google for "SQL null indicator array" finds it. Are you saying /you/ use it for more than just nulls? Or the system does? If the system, what else does it use it for?


On 11/17/2016 9:11 PM, dlclark@xxxxxxxxxxxxxxxx wrote:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 11/17/2016
05:10:27 PM:

What would be nicer, imho, is if we didn't have to keep track of those
null indicators - let the system do it. Provide us with a function
%isNull(fieldname) or something, and let it figure it out. Sooo much
simpler.

To all the recent responses.... Keep in mind that the SQL
Indicator array is about so much more than just nulls. This is why it is
NOT called the SQL Null Indicator array.

Sincerely,

Dave Clark