RE: dynamic SQL in RPG

Also, if you do not use journaling and commitment control, you'll probably
get burned by COMMIT(*CHG) being the compile default on the compile
commands.....  I have adopted Rob's practice of using the SQL options block
in my source, to protect me from memory lapse.  

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Steve Peel [mailto:Steve.Peel@xxxxxxxxxx]
Sent: Thursday, April 01, 2004 8:44 AM
To: RPG400-L@xxxxxxxxxxxx
Subject: Re: dynamic SQL in RPG


I have had similar problems with dynamic SQL, the program would work in
test when run by a developer but return an empty set in production. 
Lookout for differences in authority for 'Prepare' vs 'Select' and the
DYNUSRPRF(*OWNER) option on the program compile command.

Steve Peel
The information transmitted is confidential and is intended for the person 
or persons named above.  Any unauthorized reading, distribution, copying, 
or other use of this message or its attachments is strictly prohibited.  
If you received this message in error, contact the sender and then delete 
and destroy all copies of the material.

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