|
SET OPTIONs are nothing else than compile options. The set option statement can be compared with the H-Specs in RPG. Instead of first searching through the source to find a SET OPTION statement, the source now can be scanned sequentially. Even when coding SQL triggers, stored procedures or user defined functions a set option statement must preceede all other statements. It even must be placed before the BEGIN in a multi-statement procedure, trigger or UDF. There is also an other restriction added with release V5R4. Before V5R4 several set option statements could be placed in a single member. With release V5R4 only a single SET OPTION statement will be allowed. Mit freundlichen Gru?en / Best regards Birgitta "Shoot for the moon, even if you miss, you'll land among the stars." (Les Brown) -----Ursprungliche Nachricht----- Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]Im Auftrag von Scott Klement Gesendet: Dienstag, 25. Juli 2006 18:31 An: RPG programming on the AS400 / iSeries Betreff: Re: Embedded sql Set Option on V5R4
This rule is enforced by the other precompilers available with the IBM DB2 Query Manager and SQL Development Kit for iSeries product, and has been previously documented in the DB2 UDB for iSeries SQL Reference topic: "If embedded in an application program, [the SET OPTION statement] is not executable and must precede any other SQL statements."
Seems to me that this should make *INZSR a *good* place to put the Set Option, rather than making it an error! Doesn't *INZSR get run before the rest of your calcs? What am I missing? -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.