HP3000-L Archives

May 2006, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Craig Lalley <[log in to unmask]>
Reply To:
Craig Lalley <[log in to unmask]>
Date:
Thu, 18 May 2006 08:05:48 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Kent Wallace <[log in to unmask]> wrote:Both MPE/XL purge and MPEX YESPURGE were taking large amounts of
resources to purge the file, the "PURGEGROUP" worked in a few minutes.
Kent,

I am sure you are familiar with this, but maybe it will help out other sites.

On each volume set there are two (2) Transaction Manager Logfiles.   A User XM log, which everyone is familiar with and a System XM log which monitors directory structure changes.

The System XM log is much smaller, 16mb I believe. 

When a file is purged in the begining of the group (begining of the alphabit), all the record pointers for all the preceding files need to be updated.   This has a tendancy to fill up the System XM log quickly, causing system overhead and is very slow.

The trick is to purge them in reverse order, from the back of the alphabit, so to speak.

So to speed up the purge, try doing a 

:LISTF @,6 > MYOUT

reverse sort MYOUT
change 1 to "PURGE ", all

xeq MYOUT

This should go a lot faster.

HTH,

-Craig

		
---------------------------------
How low will we go? Check out Yahoo! Messenger’s low  PC-to-Phone call rates.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2