IBM Mainframe Forum

Hello,

Who came up with the "requirement" that the field neither have a value nor zero?

In the database world there is a concept about NULL (the absense of a value), but this is Not for data fields in a program. When the NULL concept is used in database, there is an additional "null indicator" that shows the presence or absence of a value. And there is not a "null value".

pulsar22 wrote:It is variable of a SP return cursor. The applications calling this Sp do not reside on Mainframe.

If the calling application gets any value in this field (even zero), they call some other application passing this value, but since zero is not a valid value this call is an overhead on system. They want me to return this field as null.

Ask the toy programmers to define "null".

Hello,

If the data returned to the apps is data delimited, they may be looking at a double delimiter as "nothing" . . . ?