I think you are confusing two different things. There is the teraspace "storage model", and there are teraspace allocations... the storage model makes the compiler use teraspace for it's allocations, stacks, and various other things. Just doing teraspace allocations, however (when a programmer is writing code working with pointers, et al) does not require the teraspace storage model.

Teraspace allocations with _C_TS_malloc() and friends work fine with STGMDL(*SNGLVL), but do require teraspace capability in the pointers (and the routines within the OS that do pointer math.)

In ILE RPG, terapsace pointers will work as long as you compile for V4R4M0 or higher. No need for the storage model option. (Which was added more recently). No special compile option is needed.

In ILE C, you can enable teraspace pointers by compiling with TERASPACE(*YES).

I'm not totally sure about ILE CL. I think it has supported teraspace since pointers were added to the language, but I haven't used them, so I could be wrong on that one.

I have no idea about Cobol.

On 9/15/2015 2:18 PM, CRPence wrote:

As I recall the compile commands have changed since then, to be
/nicer/ for effecting Teraspace-capable storage; i.e. the capability is
available per the parameter defaults of the compile commands on newer
releases. But on the older releases [presumably that way on v5r4], the
CRTxxxPGM must have explicitly specified that the compiled code will be
allowed to utilize Teraspace storage by using Storage Model (STGMDL)
specification of *TERASPACE instead of the [default specification of]
*SNGLVL. And if the compile is not explicitly set [or the defaults
changed] to allow the Teraspace Storage Model, then the teraspace
methods will return the null result, as was seen.

This thread ...


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

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