| DESCRIPTION OF ENHANCEMENTS |
Patch XM*7.1*131
Add status line showing number of new messages in new message list.
ROUTINES:
The second line of the routine now looks like:
;;7.1;MailMan;**[patch list]**;Jun 02, 1994
Before After
Name Checksum Checksum Patch List
-----------------------------------------------------------------
XMJBM 10706426 10732311 50,110,131
XMJMFA 6600695 6784168 50,110,131
XMJMFB 15590623 15929930 50,110,131
XMJML 11033330 11937833 50,131
XMJMLN 13840736 14755647 50,110,131
XMJMLR 14100278 14200855 50,110,131
XMJMOI 17925576 18181531 50,87,89,110,127,131
XMJMOR 13211462 14599384 50,75,110,131
XMJMORX 14207041 15388148 50,110,131
XMJMQ 15891582 15971466 40,57,70,50,96,110,131
XMJMQ1 7972269 8577594 40,50,110,130,131
XMJMSO 8232068 8539565 50,110,127,131
XMVGROUP 6851604 7521910 50,104,107,131
E3R 2404
XMXADDR 14565832 15038029 50,96,101,104,107,131
XMXAPI 6992361 7362843 50,110,131
XMXMSGS 9944188 10394514 50,110,124,131
XMXMSGS2 7381168 7750414 50,106,110,127,131
XMXPARM 14291441 15160844 50,96,107,127,131
XMXSEC1 12141474 12312603 50,95,110,130,131
XMXUTIL 11858021 12222792 40,50,107,127,131
* Checksums produced by CHECK^XTSUMBLD
This patch introduces no new routines.
Test Site: Biloxi, MS
===========================================================================
INSTALLATION:
NOTE: This patch should be installed during off hours, when user activity
is at a minimum. It requires MailMan patches XM*7.1*107, XM*7.1*124,
XM*7.1*127, and XM*7.1*130.
1. Users may be on the system during installation of this patch.
2. DSM Sites: If any of these routines is mapped, disable mapping for the
affected routine(s).
3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads
If a message is broadcast, then prompt sender for a vaporize date, if one
the patch into a Transport Global on your system.
4. You do not need to stop TaskMan or the background filer.
Users may be on the system.
5. On the KIDS:Installation menu, use the following options to install the
Transport Global:
Verify Checksums in Transport Global
Print Transport Global
Compare Transport Global to Current System
Backup a Transport Global
Install Package(s)
hasn't already been supplied.
Select INSTALL NAME: XM*7.1*131 Loaded from Distribution <date/time>
==========
Install Questions:
Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES
===
Want KIDS to INHIBIT LOGONs during the install? YES// NO
==
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO
==
Enter the Device you want to print the Install messages.
You can queue the install by enter a 'Q' at the device prompt.
Enter a '^' to abort the install.
DEVICE: HOME// <It's up to you. You may queue it if you wish.>
------------------------------------------------
6. DSM Sites: After patch has installed, rebuild your map set, if necessary.
===========================================================================
E3R 3417
Test Site: Biloxi, MS
Add an option to vaporize groups of messages.
Related help frames have been updated, and a new help frame,
XM-U-M-VAPORIZE EDIT-2, has been added.
A new API, VAPORMSG^XMXAPI, has been added.
E3R 6215
Test Site: Biloxi, MS
List broadcast recipients first during Q or QD.
E3R 14211
Test Site: Palo Alto, CA
NOIS TAM-0700-30683
Let site decide whether or not to let a user drop out of a non-self-enrolling
mail group. A new field has been added to file 4.3, MAILMAN SITE PARAMETERS,
and option XMKSP has been updated to include it. Here's the new field:
STANDARD DATA DICTIONARY #4.3 -- MAILMAN SITE PARAMETERS FILE
STORED IN ^XMB(1, (1 ENTRY) (VERSION 7.1)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
---------------------------------------------------------------------------
Test Site: Tampa, FL
4.3,22 DROP OUT OF RESTRICTED GROUP 2;2 SET
'0' FOR NO;
'1' FOR YES;
LAST EDITED: JUN 06, 2000
HELP-PROMPT: Let users drop out of non-self-enrolling mail
groups?
DESCRIPTION: Enter YES if you wish to allow users to drop
out of non-self-enrolling mail groups. The
users will be warned that this is a
If you new a message in the WASTE basket, it tells you,
non-self-enrolling group, and that they won't
be allowed to rejoin later, and then they will
be asked to re-confirm the decision to drop out.
Enter NO if you don't. (This is the default.)
Then users will have to contact IRM or the mail
group coordinator to ask to be dropped.
TECHNICAL DESCR: If a mail group is not a self-enrolling mail
group, then users can't just join. They must
"Message saved to basket." This patch fixes that.
be added by the mail group coordinator.
If a user no longer wishes to be a member of
such a group, he must ask the group coordinator
to drop him. But what if the group coordinator
has left the organization or is unresponsive?
Then what? Then the user will have to ask IRM
to help. This problem can be avoided by
setting this field to YES.
Some would argue that the coordinator added the
user to the group for a reason, and the user
should not be allowed to drop out. (Perhaps
the coordinator is the user's boss.) They
would argue that it is MailMan's job to prevent
the user from dropping out. (Set the field to
NO.) Others would argue that it is not
MailMan's job at all, but the boss's job to
prevent the user from dropping out, and to
discipline the user if he does. (Set the field
E3R 1305, 4838
to YES.)
*Note: If you do nothing with this new field, then this patch will not
change MailMan's behavior. Users will not be able to drop out of
non-self-enrolling mail groups.
Additionally,
This patch introduces two more new APIs:
$$TPMSGCT^XMXUTIL - returns # of new priority messages in a user's mailbox.
Test Site: Biloxi, MS
$$BPMSGCT^XMXUTIL - returns # of new priority messages in a user's basket.
This patch fixes a problem noticed on FORUM that could cause infinite looping
of error messages from remote sites.
NOTE: This patch should be installed during off hours, when user activity
is at a minimum. It requires MailMan patches XM*7.1*107, XM*7.1*124,
XM*7.1*127, and XM*7.1*130.
============================================================================
|
