It also depends on the DFSORT-specific controls you put in place - as Dave 
Betten former keeper of the controls (currently on vacation) will tell 
you.

Cheers, Martin

Martin Packer,
zChampion, Principal Systems Investigator,
Worldwide Cloud & Systems Performance, IBM

+44-7802-245-584

email: [email protected]

Twitter / Facebook IDs: MartinPacker
Blog: 
https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker



From:   "R.S." <[email protected]>
To:     [email protected]
Date:   24/11/2015 20:31
Subject:        Re: AW: Re: z/OS and hiperspaces
Sent by:        IBM Mainframe Discussion List <[email protected]>



W dniu 2015-11-24 o 21:23, Vernooij, CP (ITOPT1) - KLM pisze:
> Ah, my mistake. Hiperspaces are addressed differently from dataspaces 
and somewhere I thought I remembered that therefor they could be larger. 
Maybe to allow 24-bit applications to use 2 GB storage areas with 
hiperspaces?
>
> I am still wondering what the current value of hiper- and dataspaces is, 
apart from being supported for older applications that were written to use 
them.
>
> The DFSORT tuning pages state that they make a well calculated decision 
about using hiperspaces, dataspaces, 64-bit storage (addressable) and 
64-bit objects (which's data must be moved to addressable storage to use 
it, like hiperspaces). Why not use 64-bit storage only, when it is 
available?
>
> In my system I did see DFSORT use all 4 area's for its work space.
> DFSORT people: please explain?
I'm not DFSORT folk, but I think, I can explain it.
Some time ago I was fighting with some job consuming to much memory. 
First I limited its storage with MEMLIMIT, but then DFSORT started using 
*spaces instead. Still a lot of memory.
The conclusion is simple: DFSORT use any of the memory kind which is 
available, with some preferences of course. Details depend on 
availability or given resources.

-- 
Radoslaw Skorupka
Lodz, Poland






--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by 
jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste 
adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej 
przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, 
rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie 
zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, 
prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale 
usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub 
zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. 
If you are not the intended addressee of this e-mail or the employee 
authorized to forward it to the addressee, be advised that any 
dissemination, copying, distribution or any other similar activity is 
legally prohibited and may be punishable. If you received this e-mail by 
mistake please advise the sender immediately by using the reply facility 
in your e-mail software and delete permanently this e-mail including any 
copies of it either printed or saved to hard drive.

mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: [email protected]
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego 
Rejestru Sdowego, nr rejestru przedsibiorców KRS 0000025237, NIP: 
526-021-50-88. Wedug stanu na dzie 01.01.2015 r. kapita zakadowy 
mBanku S.A. (w caoci wpacony) wynosi 168.840.228 zotych.


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




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

Reply via email to