The link mentions that allowing null matters, but when I added in NOT NULL for all the other fields (which is something we generally do anyway, not sure why this source didn't have it), the IDs ended up one character off again (although completely different than before).
I built the SQL in I Nav and everything looks mostly the same.
Creating from DDS it gives "DEFAULT +0" instead of "DEFAULT 0" which it gives when translating from DDL.
Also, the DDS file ignores the REUSEDLT(*NO), so I tried setting that to yes when compiling the file, but that didn't affect the the format id.
Other than that, nothing sticks out to me.
Maybe it's time for a PMR.
-Kurt
---Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Wednesday, February 01, 2012 9:51 AM
To: RPG programming on the IBM i / System i
Subject: Re: Format Level ID
what about Allow NULL?
From Chuck's link, "and whether the field allows the null value."
How about doing a Retrieve SQL source on both objects from iNav and seeing if there are any differences there...
I'm thinking the SQL is allowing NULL on every field except the ones with the explicit NOT NULL clause, whereas DDS default to NOT NULL unless you specify ALWNULL.
Charles
On Wed, Feb 1, 2012 at 10:39 AM, Kurt Anderson <kurt.anderson@xxxxxxxxxxxxxx> wrote:
Nope. The field lengths, data type, buffer length, and buffer positions all match up.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
midrange.com
