Re: SQL Statement failing in COBOL program

Birgitta,

Thanks for the suggestion. I used iNav to generate SQL for all files
involved, ran the statements to create an SQL version in a different library
with different names, but same fields. Then I did a copy file command
(CPYF) with the *add option, nothing else special. All records from all
three files copied from the DDS created file to the SQL described file with
no errors and no warnings.

Any other ideas?
Is it time to call IBM for support?

Jim

On 8/17/07, BirgittaHauser <Hauser@xxxxxxxxxxxxxxx> wrote:

Hi,

There are invalid numeric data in your DDS described physical file.
To detect the row that contains the invalid data try the following:
1. Create a duplicate of your physical file with SQL (not DDS!)
2. Copy the DDS described data into the SQL described file. Simply with
CPYF.
When writing data to a SQL described file numeric data get checked.
If you try to insert invalid data an error occurs and the copy process
get stopped.

May be you can detect which row causes problems and correct the numeric
data.

Just FYI: When writing to a DDS described physical file invalid numeric
data
can be inserted, because no check occurs.
But when working DDS described files, the data get checked when reading
from
the physical file. Native I/O, for examples RPG or Cobol, can handle these
invalid data, but not (embedded) SQL.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training
them
and keeping them!"
´
-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Jim Essinger
Gesendet: Friday, August 17, 2007 18:26
An: Midrange Systems Technical Discussion
Betreff: Re: SQL Statement failing in COBOL program


Ran the statement in iNav scripts - no error, returned the data I
expected.

As a work around I used the statement to create a file using STRSQL, put
the
code in a QMQry as an insert, and insert the records into a temp table
with
a CL wrapper. I then open the temp file with the COBOL program to
process.
That's the long way around! The temp file does not show any data
problems.


Jim