RE: NOT allowing null value into PF fields...

["Wilt, Charles" <CWilt@xxxxxxxxxxxx>]

No changes needed.

By default DDS defined files don't allow NULL.  You have to use the
ALWNULL keyword on a field to allow NULLs.

In contrast, SQL defined files allow NULLs unless specifically told not
to allow them.


HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx] 
> On Behalf Of Joseph Pascoguin
> Sent: Wednesday, October 04, 2006 2:03 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: NOT allowing null value into PF fields...
>
> Hi All,
>
> Below is my physical file,
>
> R XFILER
>   Ifutcod        4
>   Idescr        25
>   Iclient        4
>   Ioptcod        6
>   Noptcod        6
>   reason        25
>
> I donot want to allow NULL values into the fields NOPTCOD , 
> IOPTCOD when 
> copying or importing data into this file.
>
> what changes I should be making in this PF. Iam creating this 
> file to import 
> data from an xl sheet(CPYFRMIMPF).
>
> JoeP
>
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar - get it now! 
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>
> -- 
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.