RE: Output field definitions in ILE SQL

The precompiler requires that host variables be defined as input or
(input/ouput) so in essence your fields are "defined" as output only
since they are in the printer file.  Which explains why adding the
fields to the "D" specs works.  If you remove the 'D' specs & recompile
you'll see that the printer file fields are defined only in the output
section of the listing. 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dwight Hogancamp
Sent: Thursday, November 10, 2005 9:22 AM
To: RPG400 List (E-mail)
Subject: Output field definitions in ILE SQL 

Some in our shop are having problems with SQL report programs.

We are on V5.2

Our RPGLE printer files define output the fields. We simply assign
values to
them and write them without defining them anywhere else.

When you have an externally defined print file in an SQL program with no
other field definition than the File output specs, WDSCI
says it is fine during verify.  When our precompiler gets the program,
it
says the output fields are not defined. Adding A D spec line
for each output field it claims isn't defined is taking care of the
issue
for us. We have programs that have compiled in the past and are
running that fetch into the output fields of the print file, but when we
make changes will not compile without defining more fields.

Is this behavior supposed to happen or is it something that was changed
for
a productive reason we and WDSCI don't understand?

Thanks in advance for any light anyone can shed on it?

Dwight