×
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.
On 13-Dec-2011 09:00 , Hockchai Lim wrote:
I'm getting this error in my joblog when trying to fetch result set
from a stored-procedure call. Any help would be appreciated:
Open of member AILOGPF was changed to SEQONLY(*NO).
Space offset X'FFFFFFFF' or X'0000000000000000' is outside current
limit for object MSRL3G684APALHC 039457.
SQL system error.
Ownership of object GPTFLST in QTEMP type *USRSPC changed.
Locator RS not valid.
Cursor C1 not open.
Cursor C1 not open.
Below is the RPG code: <<SNIP>>
The code does not check the SQLcode nor SQLstate after each Exec SQL,
so do you even know what statement is failing with the -901? The "SQL
system error", SQL0901 in QSQLMSG, is a "function check" error for the
SQL; effective equivalent of CPF9999 for [most of the rest of] the OS.
There is some tooling associated with the -901 for which automatic doc
collections occur, as made visible in the completion message for the
User Space. I do not recall the details, but have posted about it before.
In this case some program request failed with msgMCH0601, for what
appears to be a reference to the max offset, in a failed access to the
process automatic storage. Though given only a print screen or
copy\paste of the interactive joblog versus the actual spooled joblog
which includes the message identifiers, the context of the messaging,
and additionally the second level text, what that MCH0601 means can not
be divined.
Regards, Chuck
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.