Gibney, Dave wrote: >A frequent, even standard way to get past the size limit of a COBOL array, or >more appropriately table, was to define more "empty" space after it. Since >subscript bounds checking was always turned off for performance reasons, you >could effectively address substantially larger than the size limit of any >single 01 item.
Hmmm, it reminds me of a sort of patch area? I'm curious, what about usage of SSRANGE compile option and CHECK(ON) runtime option to avoid going over an array/table and getting an ABEND? Or will that subscript bounds checking not help you here? I'm also puzzled by that APARs and the comments in this thread. (We're still at COBOL v4, 5655-S71) Just following this thread out of curiousity. Groete / Greetings Elardus Engelbrecht Real programmers don't document their programs. If it was hard to write, it should be hard to understand. ;-) If a program is useless, it will have to be documented. There are 2 ways to write error-free programs; only the third one works. Those who can't write programs, write help files. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
