Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.
When you have an EXEC SQL set option CLOSQLCSR=*ENDACTGRP in your SQL program it's understood to be a "compile time" option if I'm correct.
But if you compile the member with CRTSQLRPGI and specify command parm CLOSQLCSR(*ENDMOD) the compile then overrides the set option in the program that specified *ENDACTGRP, yes? This is what I am seeing. Am I seeing this right?
thanks
GF
The option in the source code overrides the same option on the compile command. If you think about it, when you compile with CRTSQLRPGI, you are really using ALL the parms on the compile command, even if they are default values. If those CRTSQLRPGI options had precedence, then what would be the point of using setting them in the source code?
Chris Ringer