There is no reason to have ALWNULL() in your program unless you
coded a file in the F-specs that allows nulls.  ALWNULL() have no effect on
any embedded SQL.  By the way I do not see in (V5.1) RPG manual anything
about ALWNULL(*YES).  Could that be your problem?   *USRCTL means you test
and set on/off the null indicator used for Input/Output.  The other useful
option is *INPUTONLY allows testing of the null indicator but nothing else.
See page 203-209 in V5.1 RPG reference. 

Thank you,
Matt Tyler
WinCo Foods, Inc

-----Original Message-----
From: []
Sent: Thursday, February 13, 2003 14:53
Subject: ALWNULL(*USRCTL) v ALWNULL(*YES) was (strange SQL dumps)

Thanks Carel,
I still dont understand what is the difference between
I thought  (*USRCTL)  did everything (*YES) did and
more (dont know what more).

Anyone shed light on this, and does the precompiler
treat the ALWNULL parm differently to the RPG compiler.

Frank Kolmann

*********** REPLY SEPARATOR  ***********
from: "Carel Teijgeler" <>
subject: Re: Strange SQL dumps


ALWNULL(*USRCTL) gives you the possibility to use the %NULL bif.

I could not use that option, because my programmes run in batch and can
accept any kind of prepared SQL statement.

It is more a problem with the compilation, not the well-honoured and
all-loved precompiler (which appears to be older than RPG II).

Carel Teijgeler.

*********** REPLY SEPARATOR  ***********

On 13-2-03 at 10:29 wrote:

>Thanks Carel,
>I already have ALWNULL(*USRCTL) in the header.
>Is this different to ALWNULL(*YES)?
>But this is a SQLRPGLE  so I suspect it could be a
>problem with the <...censored..> SQL precompiler

This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email:
To subscribe, unsubscribe, or change list options,
or email:
Before posting, please take a moment to review the archives

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page