After some Googling, I found the answer in an MQ Q&A site:

"For the LSQA getmain failure, it is possible that the Extended User Region Top 
for the CHIN job has hit the bottom of Extended LSQA because Virtual Storage 
Manager (VSM) private storage use is high, for example Subpool 0 Key 8 (SP0 
KEY8) and Subpool 131 Key 8 (SP131 KEY8)."

So the answer is: yes, it applies to private and extended private.

Kees.

From: Vernooij, Kees (ITOPT1) - KLM
Sent: 08 June, 2018 11:24
To: '[email protected]' <[email protected]>
Subject: Userarea and Systemarea crossing.

Hello,

When getmaining storage in my address space the user- and system-area cannot 
cross: the highest user area block (getmained from the bottom) cannot pass the 
lowest system area block (getmained from the top) and vica versa.
Is this a rule for both below and above 16 MB? I know it is for <16MB, but I 
cannot find if this is also true for >16MB.

Thanks,
Kees.

********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to