×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
rob@xxxxxxxxx wrote:
The SQL SET OPTION is SQL's version of the H spec.
For example:
C/EXEC SQL
C+ Set Option
C+ Naming = *Sys,
C+ Commit = *None,
C+ UsrPrf = *User,
C+ DynUsrPrf = *User,
C+ CloSqlCsr = *EndMod
C/END-EXEC
Here's something you can do in a SET OPTION that you cannot do on an H
spec. Why?
C/EXEC SQL
C+ Set Option
C+ TgtRls = V5R1M0
C/END-EXEC
Rob Berendt
Will wonders never cease, eh?
I don't know how the SQL prep works, but generally, the RPG command
options that you can't code on the H-Spec are disallowed there
because we're already knee deep into the compile already. In
particular, when you specify a different release on the CRTBNDRPG or
CRTRPGMOD command, a completely different program is invoked to
compile the source code. Since the H-Spec's are compiled by that
source code, it's meaningless to specify which version to use on the
H-Spec.
I suppose when the H-Spec parsing sees that a different compiler
version is requested, we could abandon the compile and tell the
command to invoke a different version of compiler. But then, how
would the compiler handle the following H-Specs:
H/if defined(*V5R2M0)
H TGTRLS(*V5R1M0)
H/elseif defined(*V5R1M0)
H TGTRLS(*V5R2M0)
H/endif
H* ;-)
Cheers! Hans
This mailing list archive is Copyright 1997-2024 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.
midrange.com
