There is not even a point in pseudo-coding it. The use of a large table is the same as the use of a small, or middle-size, or any-sized, table.
To get some heap storage from the Language Environment involves a CALL. Not really worth pseudo-coding. There are readily-available examples of doing this in IBM manuals.
The code that may be additional for a requirement that is actually best-fulfilled by a/some huge table(s) is specific to that requirement, and is out-of-the-ordinary, and it is not much use to invent for a "general" situation when I feel that in almost all cases there are better ways to service the requirement.
Large tales in themselves are not difficult to code. Using LE Heap Storage is not difficult to code. Large tables and large amounts of Heap Storage are not generally good things to use in your environment. If I was doing a "code review" I would not let such a solution go further if there was a better way to do it differently. Which would mean your time wasted and your part of the project late as you have to start again.
Bill Woodger wrote:So, no, I'm not going to show you how to do it. It is simple enough coding that you can achieve your aim through research. Other than a knowledge exercise, I hope you don't do it.
