I am having a problem with this error. Is there a solution? I am doing a large match.
NUMBER OF RECORDS IN TABLE= 14183962 LINES=8218965

When it goes into the next step. I get the foc920 error and the program stops. I cannot get past this point in my program. I am using FOCUS and not WebFocus.

This message has been edited. Last edited by: <Kathryn Henning>,

Hi Phillis,
Probably need to bump up your FOCTEMP AND FOCSORT allocations:

//FOCTEMP DD DSN=TEMP_DSN_NAME_HERE,
// DISP=(NEW,CATLG),
// UNIT=DISK,SPACE=(CYL,100,100)

My JCL is "very" rusty, but, hope you get the jist...

BTW, Welcome to the Forum...
Tom

Phillis, you are running WebFOCUS on windows ?

I would suggest swapping to external sort.

e.g.

SET EXTSORT = ON

Are you using MATCH FILE ?

Tom and Waz,

Thank you for your reply. I tried both suggestions and my final change was to add the following to my JCL:

//** ADDED THIS FOCSORT TO PREVENT PAGE LIMIT ERROR-524287
//FOCSORT DD UNIT=SYSDA,SPACE=(CYL,(600,500)),VOL=(,,,15)

I think increasing the FOCSORT was what I needed. However, I did also add the SET EXTSORT = ON to my program.

I think this Forum is very helpful!

Phillis

Phillis,

It may be a good idea to update your signature. It only states Windows as an OS.

This is an update to (FOC920) FOCSORT HAS REACHED ITS PAGE LIMIT 524287. The external FOCSORT in the JCL would not work. I could not get around the limit. I had to make my files smaller. I sorted off the records and made 3 separate files and then matched the smaller files together individually. This worked because it was not reaching the limit. I also did a 'more' to get the files back together and proceeded through the rest of the program and it finished correctly.

I think it very much depends on what you are doing to determine if you can use external sorting.

Good to know you got it working.

quote:

524287 [pages]

That's 2,147,479,552 bytes, exactly 4096 less than 2gb. It's a hard limit on the number of data pages in a FOCUS database -- and Focsort and the "internal matrix" are just that, FOCUS databases.

Ergo, using an external sort will be of no use -- that just interposes between reading the data rows and inserting them (presorted) into the internal matrix -- but ultimately your original request would still exceed that limit.

Now, if there were an option to use xfocus as the format of the internal matrix...

in which file u have added //FOCSORT DD UNIT=SYSDA,SPACE=(CYL,(600,500)),VOL=(,,,15)

because i have same issue of foc920 focsort stopped.

quote:

Originally posted by Phillis:
Tom and Waz,

Thank you for your reply. I tried both suggestions and my final change was to add the following to my JCL:

//** ADDED THIS FOCSORT TO PREVENT PAGE LIMIT ERROR-524287
//FOCSORT DD UNIT=SYSDA,SPACE=(CYL,(600,500)),VOL=(,,,15)

I think increasing the FOCSORT was what I needed. However, I did also add the SET EXTSORT = ON to my program.

I think this Forum is very helpful!

Phillis

Hi Waz,
I am getting same error (FOC920) FOCSORT EXCEEDED CURRENT PAGE LIMIT.

So i tried to use SET EXTSORT = ON but its not working in my code as i am using nosplit command and it does not support EXTSORT .
Can you please help me out here ?

quote:

Originally posted by Waz:
Phillis, you are running WebFOCUS on windows ?

I would suggest swapping to external sort.

e.g.

SET EXTSORT = ON

Are you using MATCH FILE ?

You're gonna need a bigger boat.

Can you post the code ?

I guess I'm wondering if there is another way to code this

If you are blowing all your FOCSORT and cannot allocate more, AND using NOSPLIT, then you must be pushing a very large volume of data into your report!

What output format are you intending to use? If it is HTML, have you asked yourself the question "Can my end-users browser handle this much report?".

If you haven't then it might be a good idea to do so! Especially if the intended device is a tablet or 32 bit machine (yes, people do still have them!) with limited memory available.

T

Three things to note:


1. The FOCSORT requirement is basically governed by the number of records times the size of the data records. See if you can eliminate extraneous data columns, or truncate text columns, to reduce the row-size of the records produced.

2. If you can utilize TABLEF at this step, that will sidestep the FOCSORT issue. Yes, there are things TABLE handles that TABLEF cannot -- but for intermediate HOLD steps you can often make adjustments to work that out. And couple TABLEF with EXTSORT=ON; given appropriate conditions, WF will arrange for the external sort package to rearrange the incoming reams of data to conform to the BY phrases of the TABLEF request.

3. Assuming your process will ultimately do some serious data reduction, the step where that SUM operation occurs will need only enough FOCSORT room to hold the (summarized) output rows. So see whether you can include the data reduction (or more of it) in this step of the process.