As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
Prarie, i'm sure over half of those posts have been thanks for help i've received from you and everyone else, and applause for help i didn't even know i needed. This message has been edited. Last edited by: susannah,
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
Several approaches to try, depending on your data source and the ordering requirement for the result.
a. Look for a way to use TABLEF (rather than TABLE); then there is no FOCSORT involvement. If your source is a database server, "optimize" the request so that the server does the grouping.
b. If the table request can be converted from single-verb to multiple-verb, with a cascade of sorting phrases, the overall size of the internal matrix (really an on-the-fly hierarchical Focus file) may be considerably less than when a single verb is used, so it may beat the 2gb limit.
- Jack Gross WF through 8.1.05
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
For those of you without TechSupprt access, the main content (excluding EXTSORT) in the link I gave above is -
SET AUTOTABLEF = ON SET SAVEMATRIX = OFF
Using TABLEF as a default and avoiding the building of the internal matrix can considerably reduce the focsort requirements, as can reducing the number of BY phrases so that the internal 4 bytes required for each row for each BY field is reduced, thus reducing the total length of a single data row in the focsort.
e.g. If you have 12 BY phrases and you concatenate these fields into one and then sort by that, you could save 44 bytes per data row. If you have 1 million rows then that represents about 42 Mb(?).
If your data source is SQL then achieve all your collating and sorting of the output in your view or database definition so that you can just -
TABLEF FILE viewname (or SQLOUT) PRINT * ON TABLE HOLD AS whatever END
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004