×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 3/14/2011 3:17 AM, Schmidt, Mihael wrote:
...
Now as I understand it IBM i 7.1 lets you compile RPG modules with
teraspace as the storage model. Does that also mean that the CEE API
uses memory from teraspace and does it mean that I can use 1TB with
the same api and just a different compile setting (
STGMDL(*TERASPACE) ) ? I have no chance to test this as we are on 6.1
still.
There are two aspects to the storage model changes for RPG in 7.1.
1. Allocating teraspace heap storage using %ALLOC etc.
2. Running in the teraspace storage model.
If you only need teraspace heap storage, then use the ALLOC keyword.
Only use STGMDL(*TERASPACE) if you really need to. The reason is that
any one activation group can run either teraspace storage model or
single-level storage model. If you just change one program to use the
teraspace storage model, it will have to run in a different activation
group from the other programs. So using STGMDL(*TERASPACE) requires full
understanding of the existing activation groups used by an application,
and careful planning of the changes required by any programs or service
programs that will always use the teraspace storage model.
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.
midrange.com
