This gives the above message in DFSMSG log - ICE039A F INSUFFICIENT MAIN STORAGE - ADD AT LEAST 28K BYTES
I tried giving OPTION MOSIZE=0 and later set the diagnostic message on by giving //SORTDIAG DD DUMMY
Please find the diagnostics messages for :-
JNF1JMSG
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
Code:
]//STEP005 EXEC PGM=ICETOOL,REGION=????
is what you need -- where ???? is a value dependent upon your site. You might try 4M (or 4096K) and adjust from there. If the default region size your site uses is insufficient, and that is what the message about adding 28K means, none of the parameter values you can change in ICETOOL will be able to impact the lack of region .
Thank you so much Robert for giving me a spark to look in the right direction. I had a region=6m parameter in jobcard. I changed it to region=0M and it worked. Thank you so much...
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
When posting information to preserve spacing, you need the Code tags, not Img tags.
Robert didn't suggest coding 0M, which is an entirely sloppy way to do it unless you have specific reason (if documentation says so).
Why did you use ICETOOL? It is an entirely routine SORT with JOINKEYS. Why use ICETOOL's SORT operator anyway, when you only want to copy the file. Why use OUTREC to leave the record unchanged? Why do you have 12 work-datasets? Take the DCB information off your output file. DFSORT will accurately provide it and you won't have two places to get it the same, and then keep the same during maintenance.
EXEC PGM=SORT, remove the DCB from the output defintion.
If either or both of the files are already in key sequence, specify SORTED,NOSEQCK for that JOINKEYS statement.
On file 3 of the spool for each job, compare the memory used for the ICETOOL step and the memory used for the above when you get it working. Any difference?
