RE: Problem with view that uses an SQL function created from a procedure within a service program

Rob,

I am puzzled by what you mean here. Specifically that invalid numeric data
can only happen in a DDS defined table.

I work with a /34/36 legacy system where all of the tables were originally
program-described (flat) files. Over the years I have converted nearly all
of them to externally described files. Originally with DDS, lately with
DDL. If I try to copy the original data into the new file and it has
invalid numeric data, I get an error at that point regardless of the
definition type (DDS or DDL). If I try to use DFU to enter invalid data
into a numeric field, I get an error immediately with either a DDS or DDL
defined table.

But I admit that I did not run an exhaustive set of tests. For example, I
did not write a program defining the DDS table as program described and try
to put bad data into a record. So I do not know if I would get a MCHxxxx
error for either type of table definition.

Like I said, I am just puzzled.

Jerry C. Adams
You can never take back a fart. -An unnamed astronaut
IBM i Programmer/Analyst
--
NMM&D
615-832-2730

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of
Rob Berendt
Sent: Monday, November 02, 2020 7:32 AM
To: Midrange Systems Technical Discussion
Subject: RE: Problem with view that uses an SQL function created from a
procedure within a service program

Great tool.
But, invalid numeric data can only happen in a table defined with DDS as
opposed to a table defined with DDL. Right?

Rob Berendt