There is no need to put the SET OPTION statement into a separate procedure.
Just code the SET OPTION statement after the global D-Specs.
It is even possible to include the SET OPTION statement in one of your
procedures, it is valid for the whole member/module and NOT for the
procedure.
The only rule is, the SET OPTION Statement must be your first SQL Statement
in your source code. The precompiler scans your source and picks out the SET
OPTION Statement.
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!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxx> On Behalf Of Charles Wilt
Sent: Dienstag, 4. Dezember 2018 23:31
To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
Subject: Re: SQL in a *SRVPGM
set options is a compile time statement...
I simply put them in a procedure by themselves at the top of the module...
//-----------------------------------------------------------------------
// SetSqlOptions
//
// The SQL SET OPTION statement is a compile time statement
// It must be physically the first SQL statement the compiler sees
// during compilation. the options are in effect for the entire
module
//
// Thus this dummy procedure that isn't ever called.
//-----------------------------------------------------------------------
dcl-proc SetSqlOptions;
exec sql set option naming =*sys, commit= *none, usrprf= *owner,
dynusrprf= *owner,datfmt= *iso, timfmt = *iso,
closqlcsr= *endactgrp, alwblk = *allread,
alwcpydta = *optimize, dlyprp = *yes;
return;
end-proc;
On Tue, Dec 4, 2018 at 3:26 PM Booth Martin <booth@xxxxxxxxxxxx> wrote:
I guess it's time to start using *SRVPGMs.
I have a service program with several procedures. One procedure has
exec sql set statements and that compiled and ran. When I added a
second procedure that has exec sql set statements the service program
won't compile. It's looking to me like I need to put the exec sql set
statements at the top? But I don't know how to do that; i can't
figure out where the top is. Or is the first reference in one of the
procedures good enough for the whole service program?
--
This is the RPG programming on the IBM i (AS/400 and iSeries)
(RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
