Once you have busted a limit like this, it's probably time to rethink the design.
What is the data source? If you are processing this many records, are they from a single source? DB2 has a tablespace limit of 128TB. Does your file fit into that size? Loading a table that size with an index(es) that reflect your desired sort sequence would be a hog but could satisfy retrieval with an appropriate ORDER BY. ack On Fri, Jan 13, 2023 at 5:34 AM Charles Hardee <charleshhar...@gmail.com> wrote: > Yes, we've been informed that SYNCSORt doesn't have this limitation but > getting it in-house takes major efforts since it's a new product to us. > We were hoping for some other DFSORT option to at least let us move > forward. > > Thanks everyone for listening and your replies. > Chuck > > On Thu, Jan 12, 2023 at 12:21 PM rpinion865 < > 0000042a019916dd-dmarc-requ...@listserv.ua.edu> wrote: > > > This isn't an answer to your problem, and things may have changed > > considerably since the early 1980's. But, SYNCSORT used to have > > the TAPE sort option. Way be when, in the early 1980's, I bumped > > up against DF/SORT's limit of that time, we happened to have a > > trial copy of SYNCSORT. SYNCSORT saved the day, and that helped > > win the decision to replace DF/SORT with SYNCSORT. > > > > But, like I said, that's ancient history :) > > > > > > > > > > Sent with Proton Mail secure email. > > > > ------- Original Message ------- > > On Thursday, January 12th, 2023 at 1:01 PM, Charles Hardee < > > charleshhar...@gmail.com> wrote: > > > > > > > I have plenty of SORTWKxx DDs. > > > I don't think that is the problem. > > > > > > I am getting an IEX121A message. > > > According to the DFSORT Messages, Codes and Diagnosis Guide for z/OS > 2.5: > > > > > > ICE121A FILE SIZE IS TOO LARGE > > > Explanation > > > Critical. The amount of data to be sorted exceeded > > > a DFSORT implementation limit for the maximum > > > number of records that can be sorted. DFSORT cannot > > > handle the amount of data regardless of environmental > > > factors, such as the amount of work data set space > > > provided. Specific implementation limits include: > > > > > > 1. EQUALS in effect - 4294967295 records > > > > > > 2. VLSHRT in effect - 2147483647 records > > > > > > 3. Blockset technique not selected - 2147483647 records > > > > > > System action > > > The program terminates. > > > > > > Programmer response > > > For cases 1 and 2, perform the sort on subsets of the > > > data set containing less than the indicated maximum > > > number of records. Then merge the sorted subsets > > > into a single data set. > > > > > > For case 3, rerun the job with a SORTDIAG DD > > > statement to get message ICE800I, which indicates > > > the reason Blockset could not be used. If possible, > > > remove the condition preventing the use of Blockset. > > > Alternatively, perform the sort on subsets of the > > > data set containing less than the indicated maximum > > > number of records. Then merge the sorted subsets > > > into a single data set. > > > > > > My record count is roughly 250,000 more than the "implementation > maximum" > > > of 4294967295. > > > > > > As I indicated, this is a program doing several internal sorts against > > the > > > data so splitting, sorting and merging externally is not an option. > > > > > > Chuck > > > > > > On Thu, Jan 12, 2023 at 11:33 AM Farley, Peter < > > > 0000031df298a9da-dmarc-requ...@listserv.ua.edu> wrote: > > > > > > > Apologies for the typo, the Syncsort option is DYNALLOC, not DYNALOC. > > > > > > > > -----Original Message----- > > > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On > Behalf > > > > Of Farley, Peter > > > > Sent: Thursday, January 12, 2023 12:12 PM > > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > > Subject: Re: DFSORT maximum input records > > > > > > > > Not sure if DFSORT has an equivalent option, but Syncsort has a > > parameter > > > > DYNALOC that can change the maximum number of SORTWKnn DD's it will > > > > allocate. Our local Syncsort default is 64, but for really big sorts > > (when > > > > we get the Syncsort equivalent "too big to sort" message, which says > > "SORT > > > > CAPACITY EXCEEDED") we use DYNALOC(SYSDA,255). > > > > > > > > HTH > > > > > > > > Peter > > > > > > > > -----Original Message----- > > > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On > Behalf > > > > Of Charles Hardee > > > > Sent: Thursday, January 12, 2023 11:43 AM > > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > > Subject: DFSORT maximum input records > > > > > > > > Hello Listers, > > > > > > > > I've searched the IBM-MAIN archives and found nothing to help me so I > > > > thought I'd better ask the question. > > > > > > > > I am trying to sort roughly 4295217295, records using DFSORT. > > > > DFSORT issues a message that I have exceeded the sort input record > > maximum. > > > > It appears that this maximum is 4294967295. > > > > > > > > Since this is a program calling sort internally, and does so several > > > > times, I cannot do the "normal" thing of splitting the file down into > > > > smaller files, sort them, then merge them back together. > > > > > > > > Anyone have any thoughts on this? > > > > > > > > Thanks, > > > > Chuck > > > > -- > > > > > > > > This message and any attachments are intended only for the use of the > > > > addressee and may contain information that is privileged and > > confidential. > > > > If the reader of the message is not the intended recipient or an > > authorized > > > > representative of the intended recipient, you are hereby notified > that > > any > > > > dissemination of this communication is strictly prohibited. If you > have > > > > received this communication in error, please notify us immediately by > > > > e-mail and delete the message and any attachments from your system. > > > > > > > > > ---------------------------------------------------------------------- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to lists...@listserv.ua.edu with the message: INFO > IBM-MAIN > > > > > > > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
