× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



DDL is the language syntax used in SQL to define database tables (Data Definition Language). While the resulting file objects are nearly identical, the DDL file will be a bit more efficient with I/O buffering and data validation.

There are numerous redbooks, redpieces, and whitepapers that compare the operational efficiencies of DDL vs DDS objects, as well as a few dozen threads on this in the archives.

hth,
Eric

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Erhardt, Bill
Sent: Friday, June 20, 2008 12:19 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Handling decimal data errors at the field level


Ok, I'll bite, what is DDL

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Friday, June 20, 2008 1:11 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Handling decimal data errors at the field level

Well, if you convert your DB2 files from DDS to DDL, then you could
never load the bad data into the file in the first place. DDS validates
data when reading from DASD, where DDL validates data when writing to
DASD.

I am definitely NOT a fan of FIXNBR....

Eric DeLong

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Thomas Garvey
Sent: Friday, June 20, 2008 11:40 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: Handling decimal data errors at the field level


Hi,

Has anyone had any experience handling decimal data errors at the field
level? I know you can trap for the decimal data error that happens when
a record is read that contains a decimal data error in one of the field
values, and I know you can set the FIXNBR parameter on the RPG compile
to automatically fix numeric values that are bad. But I want to know
which specific field(s) in the record were bad. It's OK that the
compiler will fix them for me, but I want to know which field(s) in the
record were fixed.

Any ideas?

Best Regards,

Thomas Garvey
630-462-3991

--
This is the RPG programming on the AS400 / iSeries (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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.