|
-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de CRPence
Envoyé : jeudi 1 avril 2010 17:25
À : midrange-l@xxxxxxxxxxxx
Objet : Re: REXX AND ADDRESS EXECSQL
I expect there is a defect which would need to be reported
to your service provider. In my experience, the REXX is not
thoroughly tested in the lab, nor as well supported as for
with embedded SQL.
For example in REXX the SQL RENAME does not work [perhaps
only with FOR SYSTEM NAME, I do not recall] and SQL CALL for
INOUT parameters does not effect any updated parameter
values, and the lab had no intention to correct these when I
reported them years ago [although I made a private version of
the code in the lab which made the INOUT parametes function
as I expected].
Regards, Chuck
Jack Kingsley wrote:
<<SNIP per message from OP not on NG; using msg indirectly>>CL programs.
On Thu, Apr 1, 2010 at 6:17 AM, David FOXWELL wrote:
I've been using this little script for a while now without any
problems in order to use SQL from the command line or in
the joblog :
PARSE ARG iSql
RC=0
ADDRESS EXECSQL,
EXECSQL 'SET OPTION COMMIT = *NONE'
ADDRESS EXECSQL,
EXECSQL iSql
However, if I pass a CREATE ALIAS command, I get this in
--
STRREXPRC EXECSQL PARM('create alias myalias for myfile')
* Address EXECSQL EXECSQL iSql;
+ RC(-10)
SNDPGMMSG MSGID(SQL0901) MSGF(QSQLMSG)
Create table/index works fine.
Any ideas what might be different with create alias?
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list To post a message email:
MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,
please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.