"SQL" compiler option was not effect

chavinash2004 · New User Joined: 30 Jun 2010 Posts: 37 Location: hyderabad

While compling i am getting this error please any one solve my ASAP

EXEC SQL" statement was found, but the "SQL" compiler option was not
effect. The statement was discarded.

enrico-sorichetti · Posted: Fri Oct 15, 2010 4:10 pm

if You have ASAP issues hire a consultant
he will be glad to agree to Your terms negotiating a proper fee

our replies are
on our time
our equipment
free of charge

the compilation procedures are site dependent, ask Your support for the process/proc to be followed/used

dick scherrer · Posted: Fri Oct 15, 2010 7:16 pm

Hello,

Every environment has standard compile processes in place. For whatever reason, you chose to use something of your own (or used the wrong compile process - there will most likely be multiple compile processes depending on the code to be compiled).

Your technical support can tell you which is the proper process to use on your system.

haronrasheed · New User Joined: 27 Dec 2007 Posts: 4 Location: Chennai

I recently faced this issue (IGYXX0225-S) and was able to solve the problem. In general, technical support won't interfere with activities that affect program compilation. Atleast not without a formal communication to warn the users. So you can bet that it is something with your program.

Solution:
My problem was that the I did not start the "EXEC SQL INCLUDE SQLCA END-EXEC." in column 12. I believe you too had the same issue.

If your issue was different, please post on what the cause was. Will help us learn.

Akatsukami · Posted: Mon Jun 17, 2013 3:11 pm

Given that IGY is the COBOL prefix, either Avinash has posted to the wrong forum, or what you write is irrelevant.

Garry Carroll · Posted: Mon Jun 17, 2013 4:08 pm

Have you the PP(SQL'options') compile option specified and the DB2 library available to the compiler?

Garry

dick scherrer · Posted: Mon Jun 17, 2013 6:47 pm

Hello,

Bill Woodger · Posted: Mon Jun 17, 2013 9:16 pm

Although, curiously, the original does turn out to be a COBOL compiler diagnostic message :-)

prino · Posted: Mon Jun 17, 2013 9:43 pm