Another limitation along the same lines is doing sorts with VSAM files as input. DFSORT queries the catalog for the data set statistics which "may be incorrect" (especially if the file has been open a long time to CICS) and can wind up not allocating sufficient sort work data sets.
FWIW, Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Monday, September 10, 2012 8:53 AM Letting DFSORT figure out how much SORTWK it needs is a good idea, much better than hard coding yourself. However, DFSORT can only make a good decision when it knows the input dataset(disk or tape), because it gets the record count, and other DCB info to do the estimate. If doing some kind of called sort(like COBOL internal, or the like) where records get passed to SORT one at a time, then there is no way for SORT to know how much dynamic space to allocate, unless you pass SORT an estimated record count. DB2 utilities do this, but not many home grown apps do this, and this is what causes the problem. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
