× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We had a similar problem recently and given the size of FLP062 and the
alarming rate at which it grows we decided to totally clear it and then
just rebuild the drill downs for the user defined views which actually
needed drill down capability (we find that these are generally used to
view balances and the users are only likely to drill down if there is a
problem with the figures, so this drill down would only be required for
the month until GL is closed. Any drilldown that is deleted and then
required can easily be rebuilt and we'd rather do this than hold that
much unnecessary data.

It is probably worth finding out if all the user defined views are still
in use, we found that 60% were unused, so de-activating those made a
huge difference.

Unless you have a unlimited capacity for data, I think it would be much
better to handle the amount of data rather than 'fix' the files.

Regards,

Rose Clarke

-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx
[mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of
GManoovaloo@xxxxxxxxxxxxx
Sent: 04 August 2004 10:22
To: System 21 Users
Subject: [SYSTEM21] Fw: Access path size limit

We need some feedback/views  on the following situation : 

 2 weeks ago , GLUPDATE crashed because one of the logicals (GLBLINKT)
of 
FLP062 had reached the maximum size allowed . The message indicated 'no 
recovery' . 
 The attribute *ACCPTHSIZ OF the 3 logicals ( GLGLTRAN , GLBLINKT , 
GLBLALLT ) based on FLP062, was found to be set to  *MAX4GB . . After 
investigation ,and in view of the size of FLP062 , there was no 
alternative than to CHGLF the file GLBLINKT , setting the *ACCPTHSIZ to 
*MAX1TB , a value that is allowed after  O/S V3R6M0 . Since then , there

is no apparent problem . Has someone hit this problem before ? Is it
right 
to extend the CHGLF to the other logicals to prevent recurrence of
problem 
?  Also , what about additionally issuing a  CHGPF to set this same 
parameter for FLP062 ? 
Thank you any help 
 
Gilbert Manoovaloo
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.





As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.