×
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.
Charles, Yes, I've tried running it "with return" and just returning the
open cursor. I also tried declaring it without that and using the "set
result sets". Same results both times. I've also tried it with *endactgrp
and *endmod for the closqlcsr. Again, same results.
Buck, the message I'm referring to is the second level text for SQL7962:
Message . . . . : Cursor C1 opened.
Cause . . . . . : The cursor was opened with result set identifier of 0.
If the result set identifier is non-zero, the result table for this cursor
is eligible to be accessed as a stored procedure result set.
The only other message I get regarding this is SQL7995: 0 result sets
processed by the SET RESULT SETS.
Linda
Charles wrote:
Are you using DECLARE C1 CURSOR WITH RETURN FOR S1?
Also, make sure that nobody has change the default for CLSSQLCSR on the
CRTSQLxxx command ( or use a
SET OPTION statement in the code to control it)
HTH,
Charles Wilt
Buck wrote:
OK, what messages are you seeing in the job log? Can you post the message
ID (SQLnnnn)?
--buck
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
