This discussion has gone well in my meeting with the programming team.
One question they asked me, about our common SORT proc:
Is it acceptable to code this DFSPARM data in a single PDS member, and
then let it be the default for all our SORT calls? Is there any
potential problem with using this everywhere?
//DFSPARM DD *
OPTION DYNALLOC=(SYSDA,15),DYNSPC=768,HIPRMAX=OPTIMAL,MOSIZE=MAX,MOWRK
/*
(I put the data instream here, but we want to stick it into a system PDS
member.)
Thank you and best regards,
Billy Ashton
------ Original Message ------
From "Sri h Kolusu" <[email protected]>
To [email protected]
Date 7/5/2023 11:18:26 AM
Subject Re: SORTWK space usage
Also, I assume there is no way to force a Hipersort or a Dataspace sort? In
one of my tests this morning, I saw this:
Don,
If you want to force HIPERSORT, then you need to turn off other paths of code.
You can do that with the following.
MOSIZE=0,DSPSIZE=0,NOMOWRK,HIPRMAX=OPTIMAL
Similarly, if you want to run dataspace path then you need.
MOSIZE=0,NOMOWRK,HIPRMAX=0,DSPSIZE=MAX
Should I be concerned about the ICED180 and 188 messages showing they weren't
used?
NO. DFSORT executes 5 different paths and depending on the path used, the
message ICE165I, ICE199I, ICE299I, ICE399I, ICE180I and ICE188I will have a
non-zero value. In your case your job used Memory objects as work storage and
hence the other paths of code have ZERO values for usage.
Thanks,
Kolusu
DFSORT Development
IBM Corporation
----------------------------------------------------------------------
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
