>> and their intention is to use the common DFSPARM like I showed, but then to >> concatenate another line there with the FILSZ=E### value. This way, they >> don't need to specify everything again, and can focus on only the parameter >> they need.
Billy, Unfortunately, that would NOT work. You cannot have multiple OPTION statements. However, you can override the contents of DD of a proc in the JCL. So, you add the FILSZ parameter at the end of your parms. Or you need to add a COMMA at the end and have FILSZ parm on the next line. >> Is there some formula for the DYNSPC setting? the manual had a table, but it >> said it was showing a value for 6000-byte records...that doesn't sound >> overly useful The manual also mentions about the size of the file in MB in relation to DYNSPC. "Blockset is able to sort approximately 150 megabytes with DYNSPC=32 and approximately 1200 megabytes with DYNSPC=256." In your case you overrode DYNSPC=768 which would let your Sort 3600 megabytes(3.6 GB). However, your program is trying to sort about 69 GB of data. You cannot really tune DYNSPC for that size. You are better off providing the estimated filesize via DFSPARM with DYNALLOC and sort will automatically allocate the necessary disk space. ≫--is there a different setting for secondary allocation? Look up the parm WRKSEC which specifies whether DFSORT uses automatic secondary allocation for temporary JCL SORTWKdd data sets for which a secondary allocation amount is not specified. https://www.ibm.com/docs/en/zos/2.5.0?topic=statements-option-control-statement Thanks, Kolusu ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
