Full Report Browse

[DDP021]

Hello, we have a user who is loading a report to CMOD....This particular report loads over 8 MILLION pages (yes, PAGES, not bytes!)...This particular report already has over 20 indexes defined...The issue is, a select group of users that use this report want/need to have to capability to browse the entire report in order to do a find..Currently this report is still being loaded on the mainframe using ODE2.1 and the users are able to do a find across the entire version..But we need to stop this ingestion to the mainframe...We thought about utilizing the FULL REPORT BROWSE option on the thick client but have run into issues even getting the report to bring up to view after choosing the "View Full Report" option...Does anyone know of any restrictions for this option or any special setup requirements in order for it to work on such a large report?

[Justin Derrick]

Use Large Object Support, and set your number of pages to 1000.

Aside from that, I can't think of anything else -- please report back to let us know how you address this issue.

-JD.

[DDP021]

Thanks Justin...after I posted this, I had realized I had already posted something previously on this issue (back in March)...Had forgot about it with other things going on and this issue from the user getting put on the back burner forgot what was done.....In looking back at that earlier post, you had indicated about changing the large object size to 1000 and after doing so we still received the "insufficient memory to perform this function"...You're last reply after I indicated this was, " I know you're on 8.5.0.6, so you might be looking at the GSKit bug"...What is the GSKit Bug and how would we determine if this is the issue?

[Ed_Arnold]

APAR PI30612

ONDEMAND CLIENT ABENDS DURING FULL REPORT BROWSE SEARCH OF AFP
DOCUMENT


When viewing an AFP document using Full report browse, if a
Search->Find is done the OnDemand client may crash.

Planned fix is in the 9.5.0.1 client.

Ed