I wish to continue this thread as it's related. I'm now running my program with internal calls to DFSORT and it works fine except for one issue that I have, namely that I get a lot of job log messages generated as a result of dynamic allocation of VIO sortwork files. DFSORT is invoked 1000's of times by the program (yes, I know but there is nothing I can do about that) and each time it creates a bunch of job log messages for VIO allocations. For performance I want all sorting to be performed in memory, and I don't really care at the moment whether it's in hiperspace or dataspace or whatever. I successfully used the FILSZ=Ennn parameter until I ran out of space, so I increased the value to match the reality and since then I cannot get rid of the dynamic allocation messages. I've tried DYNALLOC=OFF, HIPRMAX=0, DSPSIZE=0, DSA=0, FILSZ=U0, you name it! in all sorts of combinations in an attempt to prevent dynamic allocation of work files, all in vain. I've tried region sizes far! too big including REGION=0M. I've also tried preallocating SORTWKxx to VIO data sets, but DFSORT then allocates its own SORTDKxx data sets instead :(
So how can I successfully sort my records in storage without using dynamic allocation with all the rubbish job log messages as a result? Many thanks, Staffan ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
