|DESCRIPTION OF ENHANCEMENTS
We recommend that you run option XMAUTOPURGE daily to purge your system of
The post-install routine, ^XMYPOST7, will run about 3 minutes per
1000 mailboxes. See the description above about what it will be doing.
*NOTE*: It will try to lock ^XMB(3.7). If it cannot lock it, it will not
run, and you will have to run it manually at a future time. So if you see
that ^XMYPOST7 stopped running as soon as it started, then you know it could
not get a lock.
^XMYPOST8 will not run. Do not run it.
1. This routine is usually mapped on systems that allow mapping,
so you will need to disable mapping for the affected routine.
2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This
option will load the KIDS package onto your system.
3. The patch has now been loaded into a Transport global on your
system. You now need to use KIDS to install the Transport global.
4. On the KIDS menu, under the 'Installation' menu, use the following
Verify Checksums in Transport Global
These "date purge" routines have been changed to
Print Transport Global
Compare Transport Global to Current System
Backup a Transport Global
5. MSM Sites - Answer YES to the question 'Want to MOVE routines to
other CPUs?'. Enter the names of your Compute and Print server(s).
6. AXP Sites, after patch has installed, rebuild your map set.
- improve efficiency
The second line of the routine now looks like:
;;7.1;MailMan;**[patch list]**;Jun 02, 1994
Name Checksum Checksum Patch List
XMA3 11195689 14547045 37
XMA30 5617809 7561526 37
XMA31 2140577 1080 27,37
XMA32 13342847 12437801 37
- make the coding clearer
XMA32A 11841830 9601895 27,37
XMADJF1B 4665477 4754529 10,16,37
XMDIRRCV 1862431 1909690 37
XMDIRSND 1508027 1583505 37
XMYPOST7 **new** 959425 37
XMYPOST8 **new** 649189 37
- recognize more internet date formats
- purge messages which think they are responses but really aren't
- purge responses which think they are original messages but really aren't
- recognize and comply with a task stop request
unreferenced messages. It runs approximately 40 minutes per 100,000 messages.
DD: file 4.3, field #4.304, 'MESSAGES NOT TO PURGE WEEKDAYS'
Makes the documentation in the routine and DD match the code in the routine.
Make sure that messages within the no-purge-days buffer aren't deleted.
Your mileage may vary.
DD: file 4.3, new field #142, 'NO-PURGE DAYS BUFFER'
Lets the site specify the no-purge number of days.
Routines are modified to improve efficiency and clarity.
STANDARD DATA DICTIONARY #4.3 -- KERNEL SITE PARAMETERS FILE 11/1/96 PAGE 127
STORED IN ^XMB(1, (1 ENTRY) SITE: MAILMAN RELEASED UCI: REL,NMM (VERSION 7.
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
4.3,142 NO-PURGE DAYS BUFFER .14;2 NUMBER
INPUT TRANSFORM: K:+X'=X!(X>10)!(X<1)!(X?.E1"."1N.N) X
LAST EDITED: OCT 08, 1996
HELP-PROMPT: Type a Number between 1 and 10, 0 Decimal
DESCRIPTION: This field is used during the
Option XMSTAT will show you the results of the last 20 purges: purge type,
un-referenced-messages purge to avoid purging
the last few messages in the message file,
according to their send date.
We subtract the NO-PURGE DAYS BUFFER from
today's date, giving a 'no-purge date'. Local
messages which were created on or after that
date are not subject to purge. Messages from
other sites are not affected by this buffer.
If this field is not filled in, it defaults to
7 days. One day is probably all that is
when they were run and how long they took, and how many messages were purged.
One situation in which this buffer may be
useful is in the case of a message sent only to
a remote site. Such a message is unreferenced
and would otherwise be subject to purge. If a
reply came from the remote site after the
original message had been purged, the sender
would have access only to the reply and not to
the original message. The NO-PURGE DAYS BUFFER
could be set to a reasonable number of days to
allow for a reply.
Delete Server messages from Postmaster's Mailbox after processing them.
While cleaning out Postmaster's ARRIVING basket, deletes any message which
is still arriving after 'NO-PURGE DAYS BUFFER' number of days.
MailMan patch XM*7.1*37 contains the following enhancements and bug fixes:
This problem was revealed during testing of this patch. MailMan does not
use FileMan to add messages to a user's basket; he does it himself, and that
includes updating the zero node. Up 'til now, when MM delivered a message to
a user's basket, he put the message number (not the number of messages) into
piece 4 of the zero node of the message multiple. This patch corrects that
mistake. ^XMYPOST7 goes through all message multiples of everyone's mailbox
and corrects the message multiple zero nodes.
The user status report now includes 'last sign on', as well as 'last mail use'.
This patch should be installed after hours, when user activity is at a
minimum. You should put the XMUSER Option out of order. No one should be
using MailMan. The filers (mail delivery tasks) should not be running.