RE: sql union to control test results?

David,

The SET statement should only be necessary one time. Am I reading this right, and you have multiple SET statements?

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Wednesday, July 07, 2010 5:27 AM
To: Midrange Systems Technical Discussion
Subject: RE: sql union to control test results?

Thanks, Birgitta. I had SET OPTION Commit = *NONE just once at the beginning of the program. Didn't realize that it was needed again. You can tell from that what I know about commitment control!

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Birgitta Hauser
Envoyé : mercredi 7 juillet 2010 11:01 À : 'Midrange Systems Technical
Discussion'
Objet : AW: sql union to control test results?

Did you compile your program with commit *NONE?
If not recreate it with option COMMIT *NONE or better add a SET OPTION
Commit = *NONE to your source code.
When adding a SET OPTION statement it must physically precede all
other SQL statements in your source.


Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars."
(Les
Brown)
"If you think education is expensive, try ignorance." (Derek
Bok) "What is worse than training your staff and losing them?
Not training them and keeping them!"

Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.