On 2019-01-15 4:57 AM, Frank Kolmann wrote:
What I am showing is that the compiler has set
Allow null values . . . . . . . : *NO
Even though I have specified
Allow null values . . . . . . . : *USRCTL
Where are you seeing "Allow null values ... *NO"? As far as I know,
there's nothing in the actual module or program that DSPMOD or DSPPGM
would show about null-value support.
Are you specifying ALWNULL on the command or the H spec? If it's the H
spec, the first part of the listing will show the default of *NO, but
later in the listing, after it reads the H spec, it will show a section
with "Compiler options in effect" showing the actual settings of the
combined compile parameters plus H spec keywords.
My listing, where I have ALWNULL in the H spec, looks like this:
Fix numeric . . . . . . . . . . : *NONE
Target release . . . . . . . . . : *CURRENT
Allow null values . . . . . . . : *NO
Storage model . . . . . . . . . : *INHERIT
...
Line <---------------------- Source Specifications --
Number ....1....+....2....+....3....+....4....+....5...
S o u r c e L i s t i n g
1 ctl-opt alwnull(*UsrCtl);
2
*----------------------------------------------
* Compiler Options in Effect:
*----------------------------------------------
* Text 'description' . . . . . . . :
...
* Fix numeric . . . . . . . . . . : *NONE
* Allow null values . . . . . . . : *USRCTL
* Storage model . . . . . . . . . : *INHERIT
midrange.com
