RE: Embedded SQL question

True...but if the source member type is SQLRPG or SQLRPGLE & they don't
look through the code & rely on F specs...they're wrong....

The tip on putting *ENTRY PLIST in the comment area of the PI is a good
idea though ... Think I'll steal that one... 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, September 19, 2005 11:16 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Embedded SQL question

Coding the F spec just so that someone can see that a file is updated
sounds more confusing.  I would think that the /EXEC SQL would give them
enough pause to think what happens.  Especially when they start to
understand SQL and wonder why you left in the F spec.

And I do realize what you are trying to accomplish.  I converted all my
*ENTRY PLIST's to Procedure Interfaces as recommended by the Sorcerer's
Guide, yet for those who still scan for *entry I still put in
     D MYPGM           PI                        *ENTRY PLIST
Which probably won't come in good to the list since of wrapping, but
basically the *ENTRY PLIST is off in the comment section.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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.