× 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.



Hi List

We had a process crash last night with an MCH2804 error message against a logical file. After checking the lists I found that this was due to the access path reaching the maximum 4 GB size.

The physical file had 210,598,846 records in it, and the decision was taken to purge the file rather than change the maximum size to 1 TeraByte. 3-4 hours in to the purge the job was cancelled by an operator to free up a job queue for overnight processing. The result was that 7,141,840 records were removed and the access path size was freed up by 14,680,064 bytes.

Today, however, the same process has crashed and the access path is back up to 4 GB. Only 90,548 records have been written to the physical.

The key for the access path is 9 bytes, and I was expecting there to be space for approx 1 million entries (allowing for pointers or suchlike) in the access path. Does anybody know why there would be significantly less? By my calculations it looks like each entry in the access path is taking 162 bytes.

Also, would running a RGZPFM after the purge free up any space in the access path? The fact it's "PFM" makes me think no, but I'm just wondering if it removes any allocated space from the access path too.

Any ideas, suggestions, advice or sympathy will be gratefully welcome.

Thanks

Jonathan


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.