ops, forgot about the MCH0601 error:
Message ID . . . . . . : MCH0601 Severity . . . . . . . : 40
Message type . . . . . : Escape
Date sent . . . . . . : 12/14/11 Time sent . . . . . . : 07:26:33
Message . . . . : Space offset X'FFFFFFFF' or X'0000000000000000' is
outside
current limit for object MSRL3G684APALHC 041074.
Cause . . . . . : A program tried to set a space pointer, tried to use
storage outside a space, or tried to use an unallocated page in teraspace.
The space class is X'03'. The space class designates the type of space:
00-primary associated space (includes space objects).
01-secondary associated space 0.
02-implicit process space for automatic storage.
03-implicit process space for static storage in activation group mark
X'0000000000000014'.
04-implicit process space for heap identifier X'00000000' in activation
group mark X'0000000000000014'.
05-constant space.
06-space for handle-based heap identifier X'00000000'.
07-teraspace offset X'0000000000000000'.
08-teraspace for System i5 PASE memory address X'0000000000000000'.
Offset X'FFFFFFFF' only applies to storage outside teraspace.
X'8000000000000000F079188635001000' is a pointer to the teraspace page or
the start of the implicit process space for the allocation.
Message ID . . . . . . : MCH0601 Severity . . . . . . . : 40
Date sent . . . . . . : 12/14/11 Time sent . . . . . . : 07:26:33
Message type . . . . . : Escape
From . . . . . . . . . : PALHC CCSID . . . . . . . . : 65535
From program . . . . . . . . . : QSQRUN4
From library . . . . . . . . : QSYS
From module . . . . . . . . : QSQASLOC
From procedure . . . . . . . : SQL_AssociateLocator
From statement . . . . . . . : 12845
To program . . . . . . . . . . : QSQRUN4
To library . . . . . . . . . : QSYS
To module . . . . . . . . . : QSQASLOC
To procedure . . . . . . . . : SQL_AssociateLocator
To statement . . . . . . . . : 12845
"CRPence" wrote in message
news:mailman.17752.1323813244.2520.rpg400-l@xxxxxxxxxxxx...
OK. But why continue keeping the details of the MCH0601 a secret?
While the text-based nature of the list\NG with most clients insisting
on wrapping at 72 to 80 bytes [without some effort to ensure otherwise]
may make messages "ugly" when including spooled joblog text, please
realize that continuing to use print-screen or copy\paste of the details
from an interactive joblog instead, is not conducive to allowing someone
to better assist.
Regardless, the -901 is an "internal error" which is in most cases
indicative of a defect with the SQL; even if reflected only in a poorly
programmed scenario for which the SQL chooses not to provide better
error handler for something that might either be rather complex or just
likely to be very rare. That is to suggest, if the embedded SQL is
presumably coded properly but still giving this error, the best option
is probably to apply any missing [DB group] PTFs, and report the problem
if [after applying PTFs] the problem persists.
Regards, Chuck
midrange.com
