Wow, I never would have guessed.  but after I sent that last email, that's
what I figured out myself.  I increased the size of the tbl03 and
everything is hunkydory.

Gosh, I wish I didn't have to debug cobol... :)

So, in review, indexes are sort of like a pointer field?  (rpg or C)

what happens if you keep adding to the index, and it fills up all space
allocated to the program?  does it try to overwrite memory outside it's
bounds and blow up?

What's the benefit of indexing rather than subscripting tables?

Thanks again,


------original message-----------
If the value of  INDEX-TBL03 is something greater than 400, then it will
index03 to point to memory past TBL03 which would be TBL04.  Check for that
see what's in  INDEX-TBL03.

-----Original Message-----
From: rick.baird@xxxxxxxxxxxxxxx [mailto:rick.baird@xxxxxxxxxxxxxxx]
Sent: Thursday, June 10, 2004 4:27 PM
To: cobol400-l@xxxxxxxxxxxx
Subject: [COBOL400-L] RE: I'm stumped - working storage tables indexed
by -WTF?

ok,  now I'm really confused.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by 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.