Comments (1)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 localhost commented Permalink

I thought it was odd when I first wrote this. It turns out this is a RE-introduction of the parameter. (Must've been a rushed day.)<div>&nbsp;</div> But I thought it was worth commenting that one of the scenarios people worry most about with DFSORT performance is concurrent large sorts being unaware of each other. To which I have to say that - for many years - DFSORT Hipersorting and Large Memory Object Sorting use the STGTEST SYSEVENT at various points in the sort to minimise the risk of "concurrent sort collisions". And the DB2 Utilities twist on this is that it's quite easy to generate batches of concurrent sorts from a single utility job run.<div>&nbsp;</div> But I would be interested in installations' experiences with concurrent large utilities.