RE: embedded sql, procedure, and report output

Is this a main procedure?  If so the "C" specs have to come before the
"O" specs.  The only time that "C" specs come after the "O" spec is when
using internal procedures(not subroutines). 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx] On
Behalf Of Duane Kehoe
Sent: Wednesday, October 26, 2005 10:33 AM
To: RPG programming on the AS400 / iSeries
Subject: embedded sql, procedure, and report output

   I have a source member of type SQLRPGLE which contains a single
procedure
   made up of a few subroutines with embedded SQL and report output.
When I
   try to compile I can not get past the SQL precompiler, I keep getting
an
   error related to RPG Specification out or order on the very next line
   following the 'O' specs.  In the past I have placed the 'O' specs for
   procedures at the top of the source before the begin procedure
statement
   but this does not seem to work in this case.  Could someone please
point
   me in the right direction as to where the output specs for this
module
   need to be placed "physically" in the source member.  Thanks in
advance
   --

   Weyco Group -             
                             
       Florsheim, Brass Boot, Nunn Bush, Stacy Adams
   Duane Kehoe                       Phone # 414.908.1814 
   EC / Programmer / Analyst           Fax # 414.908.1601 
                             Email: dkehoe@xxxxxxxxxxxxxx
--
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.