|
View previous topic :: View next topic
|
| Author |
Message |
Adam
New User
Joined: 17 Jun 2005
Posts: 7
|
|
|
|
Hi,
we've migrated from DB2 v9 CM to NFM on one test lpar.
Now our sorts "likes" hiperspace workfiles and reports high number of service units. Before that they choose rather other types of workfiles.
For example the same sort steps before and after migration:
| Code: |
STEPNAME PROCSTEP RC EXCP CONN TCB SRB CLOCK SERV WORKLOAD PAGE SWAP VIO SWAPS
SRT(CM) 00 122K 60898 .12 .00 .6 780K TSTBAT 0 0 0 0
SRT(NFM) 00 120K 27582 .11 .00 .7 10269K TSTBAT 0 0 0 0 |
(SRT(CM) use Data Space workfiles. Dfsort V1R5, z/OS 1.9)
If a batch jobs are rated for the SU i'ts not so good.
What can be cause? |
|
| Back to top |
|
 |
Dave Betten
New User
Joined: 24 Jan 2006
Posts: 26
|
|
|
|
| My guess is that there is now more storage available on the system so DFSORT is exploiting it for Hiperspace sorting. If you want to restrict DFSORT so that it cannot use available central storage fo sorting, you can modify your installation default like EXPMAX from the shipped default of MAX to something more restrictive. If you want to disable it completely, set EXPMAX=0. |
|
| Back to top |
|
|
Adam
New User
Joined: 17 Jun 2005
Posts: 7
|
|
|
|
Thanks for the reply and tips, Dave.
I decided to use HIPRMAX=0 to disable Hipersorting.
An additional unpredictable HPT overhead distorted our batch tests results.
I concerned to miss an unknown APAR or PTF so my subject ...
Regards |
|
| Back to top |
|
|
|
|
