Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.development    |    Operating system development chatter    |    4,255 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,407 of 4,255    |
|    Joe Monk to All    |
|    Re: segmentation    |
|    05 Nov 22 02:17:55    |
      From: joemonk64@gmail.com              > Also, I thought the first 32 GiB or something was reserved for        > Java use or something? How does that work with a 2GiB limit?        >               IBM recommends that you do not make explicit storage requests from the 2G to       64G area because Java uses it. That doesnt mean you can't; it just means if       you do, watch out when the system programmers come looking for you...              ", USE2GTO64G = NO       , USE2GTO64G = YES       An optional keyword input that specifies whether this is an explicit       allocation request for 64-bit virtual storage in the 2G to 64G virtual storage       area. IBM suggests that you not use this parameter because Java and other       language runtimes use it. If        there is not enough memory available in this range, the language runtimes       could fail to start, or there could be increased memory usage and reduced       performance. This parameter relates to usage of the compressed references       feature, which is documented in        z/OS User Guide for IBM SDK, Java Technology Edition.       Check the RCE_USE2GTO64GENABLE bit in the IARRCE macro to ensure that the       system supports this keyword."              Now ... I'm gonna throw something else at you ...              "Note: The problem state caller running in PSW key 8-15 can use GETSTOR/DETACH       only when the primary address space is the home address space."              So, the other thing you have to check before doing a GETSTOR in unprivileged       mode is that your address space is correct. If it is not (i.e. you are in       primary or secondary rather than home), you must first do a space switch       before making your call for        memory...              As to your other point:              ",MEMLIMIT=NO       The 64-bit private memory object is not counted against the address space       MEMLIMIT. MEMLIMIT=NO is effective only when specified by authorized callers       in supervisor state or key 0-7. Requests for MEMLIMIT=NO by unauthorized       callers will result in a DC2        abend with reason code 19."              So an authorized, privileged caller can bypass the MEMLIMIT. Since you are       running unprivileged, you cant.              Joe              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca