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