|
>From: rob@dekko.com >Date: Wed, 3 Oct 2001 17:05:11 -0500 > >You're right, and what a sneaky way to find a use for the index. Snicker. >But wouldn't the MCH error only appear if I try to use the fields in the >based data structure after the last looping? After all, seems to be >working. Or would the error occur if I exceed the initial size of the user >space as created by QUSCRTUS? Or would the error occur if I exceed the >size of the user space as changed by the list api which output's data into >it? The MCH error would occur as soon as you set the pointer, if the limit was somewhere between the current pointer and the new offset. Maybe if your space is auto-extendable (is that possible?) _and_ you don't go over whatever is the absolute size-limit for a space, then maybe you won't get an error. But I know it's possible to get a MCH0601 from doing what you're doing, because I used to do it that way too, until I got the MCH0601. My program was working fine until I had some huge number of entries, and got near the end of the space. "Seems to be working" is usually the case with programs that use pointers illegally. Barbara Morris
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.