Radoslaw Skorupka wrote: >EXPMAX Specifies the maximum total amount of available storage to be used at >any one time by all Hipersorting, memory object sorting, and dataspace sorting >applications.
>Is it the limit for all concurrently running DFsort jobs/tasks or it is per >job limitation? Hmmm, interesting question, but see this note (DFSORT Application Programming Guide): <quote - Note all quoted text has Vertical Bar as from z/OS v1.12>: DFSORT only uses memory object or Hiperspace storage when there is sufficient central storage available to back all the DFSORT work data. DFSORT's use of memory object and Hiperspace storage is very dynamic: multiple concurrent sort applications always know each other's storage needs and never try to back their memory objects or Hiperspaces with the same portion of storage. In addition, DFSORT checks the available storage throughout the run, and switches from using memory objects or Hiperspaces to using disk work data sets when either a storage shortage is predicted or the total Hipersorting, memory object sorting, and dataspace sorting activity on the system reaches the limits set by the EXPMAX, EXPOLD, and EXPRES installation options. <end quote> So, it seemed that whatever the limit is, DFSORT will check it anyways and all jobs are checking each other's usage. If one job is hogging storage, others will have to wait, reduce their demand or use other storage methods. Is the question related to a problem you're having? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
