An out-of-band null is DataStage's internal representation of null. It's a single byte with only the high bit set (128 if it were a uint8).
An in-band null is a value that is legal for the domain of the field, but which your business model has designated will represent "unknown". For example you may have used -99 to represent "unknown" for a set of integer codes. -99 would be the in-band null for that field. Similarly you might choose "9999-12-31" to be the in-band null for a date type.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
when we use setnull() it would be out band null but how to convert out band null to in band null; makenull will do the vice versa how abt the other side?
And where do can we make a choice of using in band null or out band null for nullable fields?
ray.wurlod wrote:An out-of-band null is DataStage's internal representation of null. It's a single byte with only the high bit set (128 if it were a uint8).
Does datastage reserve one bit for sign and one bit for null indication and use the rest for holding the value
In such case for signed int8 the max value that can be held becomes 32
(int8:-signed integer with 1 byte for storage; please correct if wrong)