×
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.
Thank you for the in-depth explanation. As you say, using ADDRESS
EXECSQL followed by EXECSQL "statement" is a goofy but workable
solution. I neglected to research the SQL host programming information
for Rexx, so missed the double EXECSQL requirement.
Loyd Goodbar
Senior programmer/analyst
BorgWarner
TS Water Valley
662-473-5713
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Thursday, April 03, 2008 17:18
To: Midrange Systems Technical Discussion
Subject: Re: Rexx address command versus execsql
What you have documented is essentially what I was surmising when I
said I thought I knew the problem. (How did I let "no" for "know"
slip by? Sloppy!) I ran into this very problem recently. I have not
used SQL in Rexx for years and ran into the same problem. It took me
ages to determine the cause of RC being -10 because there is NO
information about the error in the job log.
<great follow through and explanation snipped>
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
