|
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Jonathan Mason
Sent: Wednesday, April 30, 2008 7:34 AM
To: midrange-l@xxxxxxxxxxxx
Subject: MCH2804 Message and Access Path Size
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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.