| DESCRIPTION OF ENHANCEMENTS |
Patch XM*7.1*50. The BIG patch! It is important that you read this patch
new manuals are in PDF documents on the infrastructure web site at:
a. This patch should be installed after hours, when user activity is at a
Just add the new name as a synonym.
===========================================================================
minimum. It should not be queued, because TaskMan should not be running.
b. This patch requires Kernel patches XU*8.0*67, XU*8.0*112, and XU*8.0*113.
c. For any site running MAS (all VAMCs), this patch requires FileMan patch
DI*22.0*1. Caution: KIDS will not check for this patch because not all
sites run MAS. It is up to each site running MAS to check for DI*22.0*1.
d. All MailMan users, including fictitious users, must have an access code,
or they will no longer receive mail.
e. To shorten installation time, which runs about 1 hour per 200,000 messages
in file 3.9, you might consider running the message purges the day before
http://www.vista.domain.ext/
the installation:
- XMMGR-PURGE-AI-XREF (AI x-Ref Purge of Received Network Messages)
- XMPURGE-BY-DATE (Purge Messages by Origination Date)
- XMAUTOPURGE (Automatic Purge of MailMan Messages)
f. DSM sites running SlotMaster may see routine mapping problems with ZSLOT
users, even after disabling mapping. Therefore, such sites should consider
the following steps:
- Shutdown ZSLOT on all nodes.
- Disable all mapped XM routines.
- Load this patch.
softserv/infrastr.uct/notebook/active/xm_patch_50_notebook.htm
- Enter manual edits.
- Rebuild mapped routine sets.
- Shutdown/restart all DSM configurations.
An alternative to the above steps is to disable all mapped XM routines about
a week before you load this patch. That way you wouldn't need to shutdown
ZSLOT or shutdown/restart DSM configurations.
g. If your site is running POP3, you should immediately load patch XM*7.1*71
after installing this patch.
============================================================================
- XM*7.1*50 Patch Description
This patch deletes the following routines:
XMZTERM (replaced by XMUTERM in this patch)
XMZTERM1 (replaced by XMUTERM1 in this patch)
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
- MailMan V.7.1 & XM*7.1*50 Release Notes
----------------------------------------------------------
XM 4976038 11416143 17,35,50
XM0 3346676 580 4,42,50
XMA 11666053 79959 4,18,50
XMA0 10480365 573755 15,36,50
XMA01 2847569 1068 36,50
XMA02 6053078 879 4,5,50
XMA03 7773789 66257 50
XMA0A 6404929 1148 7,16,50
XMA1 9717771 827 31,36,40,50
- MailMan V.7.1 & XM*7.1*50 Getting Started
XMA10 5587620 1067 50
XMA11 11668318 19543 50
XMA11A 6856608 291270 50
XMA11B 3593034 1468 39,50
XMA1A 3777724 1152 50
XMA1B 7260820 705206 50
XMA1C 1474193 99629 50
XMA1E 1530615 1172 50
XMA2 10059315 1214246 5,6,10,15,39,50
XMA20 4266922 1071 50
- MailMan V.7.1 & XM*7.1*50 User Manual
XMA21 11321545 1920696 4,31,50
XMA210 1920955 1364 31,50
XMA21A 7475211 1466 4,30,36,50
XMA21B 3903898 1472 50
XMA21FWD 406565 2649 50
XMA21G 11358760 1502 31,36,65,50
XMA22 7780497 887 50
XMA24 10721719 1091 31,50
XMA25 5071849 1096 50
XMA2B 4986311 4956922 50
- MailMan V.7.1 & XM*7.1*50 Programmer Manual
XMA2C 4163417 1166 46,53,50
XMA2C0 9088344 1454 24,27,50
XMA2R 4793721 3427633 27,50
XMA3 14700672 17147624 37,54,69,50
XMA30 7561526 7080895 37,50
XMA32 12437801 6537619 37,50
XMA32A 10902381 9900106 27,37,44,55,50
XMA4 1695677 839 50
XMA5 11192062 843 31,45,50
XMA50 4115522 1083 50
- MailMan V.7.1 & XM*7.1*50 Technical Manual
XMA51 3840890 1088 50
XMA5A 13683319 1168 31,36,50
XMA6 986923 847 50
XMA7 10080629 16522 10,47,50
XMA7G 5211523 1206 36,50
XMA7G1 1193700 1500 24,50
XMAD0 481945 1143 50
XMAD1 7275936 1148 24,27,36,50
XMAD1A 7330837 1538 36,70,50
XMAD1X 3265319 1676 50
XMAD2 2503657 208202 31,50
XMADA 1034 1034 50
XMADDOC 1992 1992 50
XMADDOC1 4357710 2578 50
XMADDOC2 3589 2392 50
XMADGO 2112000 10833 5,27,50
XMADGO1 788007 2075 50
XMADJ999 419074 2470 50
XMADJF0 5354543 2029 50
XMADJF1 9044468 2036 44,52,67,50
description and follow the install instructions.
Highlights of the patch:
XMADJF1A 912544 2556 50
XMADJF1B 4754529 2564 10,16,37,50
XMAH 5026238 1544316 5,16,50
XMAH0 1761641 1159 36,50
XMAH1 8757966 2172709 4,50
XMAI 4557700 923 50
XMAI0 1750753 1163 50
XMAI1 8026797 1168 43,50
XMAI2 1510945 3037343 36,50
XMAK 4457158 737 50
- Addresses 54 distinct NOIS and 40 distinct E3R.
XMAL0 7710735 1175 50
XMAL0A 7458546 1565 50
XMANON 836515 1806 7,50
XMAP 8826127 951 24,36,50
XMAP0 4991024 1191 27,50
XMAP1 3005830 1196 50
XMAPHOST 6157206 9890299 7,14,27,36,50
XMASEC 4454626 46560 33,50
XMB 7258608 4363515 3,7,24,26,27,50
XMB1 8930890 830 31,50
- For those sites requesting it, performs, along with follow-on patch
XMBGRP 8013060 8135589 13,36,56,50
XMBPOST 9856673 9626449 4,13,23,24,27,38,50
XMC 4113929 3216956 13,50
XMC1 6875049 7147079 4,13,20,27,50
XMC11 11677623 11806932 50
XMC11A 3517372 4391366 27,50
XMC2 12142809 12105966 13,23,27,50
XMC3 5809172 5862128 20,50
XMC4 5412826 991572 50
XMCD 5190692 5277071 50
XM*7.1*51, automatic domain name change from .DOMAIN.EXT to .DOMAIN.EXT, as
XMCTLK 9708749 9742452 10,27,50
XMD 4879878 6535767 33,50
XMDF 1706479 1431567 50
XMDIRQST 7236196 7357280 9,50
XMDIRRCV 1909690 1913144 37,50
XMDIRSND 1583505 1897078 37,50
XME 10528702 643 50
XME1 8041932 839 50
XMFAX 4957190 4921115 36,50
XMGAPI2 3885152 3885630 41,50
well as domain rename. This patch adds the new domain names as synonyms to
XMGAPI3 3505605 2171233 29,44,67,50
XMGAPI4 3952807 4204061 50
XMHIG 4741088 5360885 45,50
XMHIU * New * 5960638 50
XMJBL * New * 4523065 50
XMJBM * New * 12165199 50
XMJBM1 * New * 4157424 50
XMJBN * New * 10185228 50
XMJBU * New * 1507122 50
XMJDIR * New * 2003843 50
the current domain names. XM*7.1*51 will actually change the domain names.
XMJERR * New * 454500 50
XMJMA * New * 2991838 50
XMJMBULL * New * 1365629 50
XMJMC * New * 8169036 50
XMJMCODE * New * 11042686 50
XMJMD * New * 7370754 50
XMJMF * New * 18005162 50
XMJMFA * New * 6204287 50
XMJMFB * New * 15137131 50
XMJML * New * 11033330 50
(XM*7.1*51 will be released after all sites have installed XM*7.1*50.)
XMJMLN * New * 13240819 50
XMJMLR * New * 13545823 50
XMJMLR1 * New * 6523962 50
XMJMOI * New * 16872170 50
XMJMOIE * New * 4582157 50
XMJMOR * New * 14242356 50
XMJMORX * New * 14790879 50
XMJMORX1 * New * 2472219 50
XMJMP * New * 16472134 50
XMJMP1 11388791 14179283 40,50
- Adds many new APIs.
XMJMQ 15192669 16189088 40,57,70,50
XMJMQ1 3291603 3608941 40,50
XMJMR * New * 18651915 50
XMJMRO * New * 2449032 50
XMJMS * New * 6092728 50
XMJMSA * New * 1939332 50
XMJMSO * New * 12952439 50
XMJMT * New * 10637487 50
XMKP * New * 15443979 50
XMKPL * New * 2060011 50
- Replaces the old user help frames with an entire new set of help frames.
XMKPLQ * New * 9249196 50
XMKPO * New * 2606344 50
XMP 8440919 8546955 4,24,50
XMP2A 10037244 10101095 24,42,50
XMP3 7025241 6844934 24,50
XMPC 5263348 5352206 50
XMPG 4354526 4353568 50
XMPH 4842981 3963996 34,50
XMPSEC 5817282 7152889 50
XMR 6901880 14031423 30,34,65,50
(The IRM help frames have not been updated.)
XMR0 8606729 874 27,50
XMR0A 3476739 2289812 27,50
XMR0B 9564128 8875848 4,6,13,34,42,62,50
XMR0BLOB 5117794 4867143 50
XMR1 7053085 13292215 7,50
(Cache' sites may have a different 'before' checksum and)
(patch list for XMR1. Please disregard the differences.)
XMR1A 6979581 3017305 13,36,50
XMR2 7882048 6207716 50
XMRENT 2303842 2263450 31,50
- Makes many changes to the MailMan DDs.
XMRMSM 326967 339884 61,50
XMRONT 598867 621984 61,50
XMRPCTS0 5929098 6262116 6,12,31,55,50
XMRPCTS1 6929051 5691788 6,50
(Your XMRPCTS1 'before' checksum may be)
(different, because of your TWIX info. )
XMRPCTSA 3490824 3495721 6,31,61,50
XMRTCP 4812676 4798863 8,25,27,50
XMRUCX 357201 841742 27,34,50
XMS 5835931 5837542 8,20,34,48,50
- Renames file 3.7 from MAIL BOX to MAILBOX.
XMS0 9233148 9308250 13,8,20,23,27,34,55,50
XMS0A 8144942 9199959 2,13,55,50
XMS0BLOB 6815258 6975716 50
XMS1 7375190 1321634 13,8,23,50
XMS2 1293876 885 50
XMS3 13059868 12996474 22,50
XMS4 3616422 2836511 50
XMS5 12421886 13329767 13,8,23,27,55,58,50
XMS5A 3624422 3571279 55,50
XMSERR 3651687 3280474 32,50
- Renames file 4.3 from KERNEL SITE PARAMETERS to MAILMAN SITE PARAMETERS.
XMSM 10210546 7239792 4,6,13,20,50
XMSM1 1692536 1238 50
XMSMAIL 5893340 4937839 59,50
XMTDF * New * 3998255 50
XMTDL * New * 18249122 50
XMTDL1 * New * 5047763 50
XMTDL2 * New * 8743997 50
XMTDO * New * 1746764 50
XMTDT * New * 5385940 50
XMUDNC * New * 3683283 50
- Improves global integrity checker.
XMUPIN * New * 13825872 50
XMUT1 8603321 3818573 50
XMUT1A 4040808 3948769 50
XMUT2 4770720 4582154 50
XMUT4 4510855 17112758 50
XMUT4A 4424419 1411742 34,55,50
XMUT4B 8543914 18488496 50
XMUT4BA 8604816 15364896 50
XMUT4C 3745269 7228866 10,22,50
XMUT5 4455724 5739686 50
- Improves message search.
XMUT5B 2824190 2644064 50
XMUT5Q 8765057 8502082 50
XMUT6 2438497 2312993 50
XMUTERM * New * 15007949 50
XMUTERM1 * New * 14471083 50
XMUTPUR0 1145390 1365512 7,50
XMVGROUP * New * 6214836 50
XMVSURR * New * 2622785 50
XMVVITA * New * 4126813 50
XMVVITAE * New * 12045708 50
- Insists that users must have a mailbox and an access code in order to
XMXADDR * New * 18774539 50
XMXADDR1 * New * 12069509 50
XMXADDR2 * New * 6515109 50
XMXADDRD * New * 9657048 50
XMXADDRG * New * 15430701 50
XMXANSER * New * 2242310 50
XMXAPI * New * 6705900 50
XMXAPIB * New * 3472533 50
XMXAPIU * New * 596863 50
XMXBSKT * New * 12393935 50
receive messages. This is to ensure that messages do not accumulate in
XMXBULL * New * 5479615 50
XMXEDIT * New * 3880586 50
XMXLIST * New * 10429141 50
XMXLIST1 * New * 12554823 50
XMXMBOX * New * 1289002 50
XMXMSGS * New * 10966038 50
XMXMSGS1 * New * 9891647 50
XMXMSGS2 * New * 5670519 50
XMXPARM * New * 19704732 50
XMXPARM1 * New * 5916152 50
inactive mailboxes, never to be deleted. It is very important that any
XMXPARMB * New * 4788158 50
XMXPRT * New * 3036286 50
XMXREPLY * New * 4925239 50
XMXSEC * New * 18599731 50
XMXSEC1 * New * 12851118 50
XMXSEC2 * New * 20994061 50
XMXSEND * New * 10879355 50
XMXTO * New * 1915321 50
XMXUTIL 2338705 10432772 40,50
XMXUTIL1 * New * 5489564 50
ficticious user be properly set up so that mail deliveries to these users
XMXUTIL2 * New * 7762911 50
XMXUTIL3 * New * 3652490 50
XMXUTIL4 * New * 9117363 50
XMYMNEM 5559955 4398404 50
XMYPOST2 9070792 7919115 49,50
XMYPOST9 * New * 5996100 50
XMYPOSTA * New * 2107256 50
XMYPRE 4770905 3732264 50
XMYPRE2 * New * 12021025 50
XMYPRE2A * New * 15738292 50
are not stopped.
XMYPRE2B * New * 3451238 50
* Checksums produced by CHECK^XTSUMBLD
This patch introduces the following new routines:
Routine Callable at Description
---------------------------------------------------------------------------
XMHIU N/A
XMJBL N/A
Test Sites: DOMAIN.EXT; GATEWAY.DOMAIN.EXT; Indianapolis, IN;
- Implements message filtering.
XMJBM N/A
XMJBM1 N/A
XMJBN N/A
XMJBU N/A
XMJDIR N/A
XMJERR N/A
XMJMA N/A
XMJMBULL N/A
XMJMC N/A
XMJMCODE N/A
- Improves local message delivery system.
XMJMD N/A
XMJMF N/A
XMJMFA N/A
XMJMFB N/A
XMJML N/A
XMJMLN N/A
XMJMLR N/A
XMJMLR1 N/A
XMJMOI N/A
XMJMOIE N/A
- Adds 'full screen' user interface for managing and reading messages.
XMJMOR N/A
XMJMORX N/A
XMJMORX1 N/A
XMJMP N/A
XMJMR N/A
XMJMRO N/A
XMJMS N/A
XMJMSA N/A
XMJMSO N/A
XMJMT N/A
- Rewrites 'classic' user interface to improve maintainability.
XMKP N/A
XMKPL N/A
XMKPLQ N/A
XMKPO N/A
XMTDF N/A
XMTDL N/A
XMTDL1 N/A
XMTDL2 N/A
XMTDO N/A
XMTDT N/A
- Most ^XMA* routines have been superseded by other routines.
XMUDNC N/A
XMUPIN N/A
XMUTERM N/A
XMUTERM1 N/A
XMVGROUP N/A
XMVSURR N/A
XMVVITA N/A
XMVVITAE INIT Initialize user setup information
OTHER Setup as someone else
SELF Return to oneself
- (new) ^XMJ* routines comprise the user interface.
XMXADDR N/A
XMXADDR1 N/A
XMXADDR2 N/A
XMXADDRD N/A
XMXADDRG N/A
XMXANSER N/A
XMXAPI ADDRNSND Address and send a message (doesn't handle msg body)
ANSRMSG Answer a message
CRE8XMZ Create a new message in message file
DELMSG Delete messages from a basket
- (new) ^XMK* routines perform message posting.
FLTRMSG Filter messages
FWDMSG Forward messages
LATERMSG 'Later' messages
MOVEMSG Move messages from/to a basket
PRTMSG Print messages
PUTSERV Put a message in a server basket
REPLYMSG Reply to message
SENDBULL Send a bulletin (returns XMZ)
SENDMSG Send a message
TASKBULL Send a bulletin (quicker, but does not return XMZ)
- (new) ^XMT* routines perform message delivery.
TERMMSG Terminate messages
TOWHOM Check one message addressee
VSUBJ Validate a message subject
ZAPSERV Delete a message from a server basket
XMXAPIB CRE8BSKT Create a basket
CRE8MBOX Create a mailbox
DELBSKT Delete a basket
FLTRBSKT Filter messages in a basket
FLTRMBOX Filter all messages in a mailbox
LISTBSKT Get a list of baskets
- (new) ^XMX* routines comprise the APIs.
LISTMSGS Get a list of messages in one or all baskets.
(Search criteria may be used.)
NAMEBSKT Change the name of a basket
QBSKT Get info on a basket
QMBOX Query a mailbox
RSEQBSKT Resequence messages in a basket
TERMMBOX Remove all traces of a user from MM globals
XMXAPIU READ Read/Manage messages in Mailbox (interactive)
READNEW Read new messages in a Mailbox (interactive)
SEND Send a message (interactive)
- (new) ^XMV* routines comprise user identity.
TOWHOM Address a message (interactive)
XMXBSKT N/A
XMXBULL N/A
XMXEDIT CLOSED Toggle message 'closed'
CONFID Toggle message 'confidential'
CONFIRM Toggle message 'confirm receipt requested'
DELIVER Set/delete delivery basket
INFO Toggle message 'information only'
PRIORITY Toggle message 'priority'
SUBJ Change message subject
Montana HCS, MT; San Francisco, CA; SAIC Corp.;
- ^XMR* has been rewritten.
TEXT Replace message text
VAPOR Set/delete message vaporize date
XMXLIST N/A
XMXLIST1 N/A
XMXMBOX N/A
XMXMSGS N/A
XMXMSGS1 N/A
XMXMSGS2 N/A
XMXPARM N/A
XMXPARM1 N/A
- Improves the remote message xref, ^XMBX(3.9,"AI", by enabling it to handle
XMXPARMB N/A
XMXPRT N/A
XMXREPLY N/A
XMXSEC $$ACCESS May user access message?
$$ANSWER May user answer message?
$$BCAST Is this a broadcast message?
$$CLOSED Is this message closed?
$$CONFID Is this message confidential?
$$CONFIRM Is this message confirm receipt requested?
$$COPY May user copy message?
longer message IDs. Specifically, the xref has changed
$$DELETE May user delete message?
$$FORWARD May user forward message?
$$INFO Is this message information only?
$$LATER May user later message?
$$MOVE May user save/filter message?
$$ORIGIN8R Did user send this message?
$$POSTPRIV Does user have postmaster privilege?
$$PRIORITY Is this message priority?
$$READ May user read message?
$$REPLY May user reply to message?
from: ^XMBX(3.9,"AI",site@msgid,xmz)=fm date/time
$$RPRIV Does surrogate have read privilege?
$$RWPRIV Does surrogate have read/write privilege?
$$SEND May user send a message?
$$SURRACC May surrogate access message?
$$SURRCONF May surrogate *not* access message?
$$WPRIV Does surrogate have write privilege?
$$ZCLOSED Is this message closed?
$$ZCONFID Is this message confidential?
$$ZCONFIRM Is this message confirm receipt requested?
$$ZINFO Is this message information only?
to: ^XMBX(3.9,"AI",site,msgid,xmz)=fm date
$$ZORIGIN8 Did user send this message?
$$ZPOSTPRV Does user have postmaster privilege?
$$ZPRI Is this message priority?
XMXSEC1 $$COPYAMT May the copy contain the requested responses?
$$COPYLIMS Get the site's copy limits.
$$COPYRECP May the copy be sent to the original's recipients?
$$PAKMAN Is this a PackMan message?
CHKLINES May this message be sent to a remote site?
CHKMSG Is message really there & may user access it?
GETRESTR Get restrictions on what user may do with message
The post-init will reconfigure the xref. (This could take anywhere from 1/2
OPTGRP What may user do at basket/message group level?
XMXSEC2 $$EDIT May user edit message?
OPTEDIT If user may edit message, what may/may not be edited?
OPTMSG What may/may not the user do with this message?
XMXSEND N/A
XMXTO N/A
XMXUTIL $$BMSGCT Number of messages in user's basket
$$BNMSGCT Number of new messages in user's basket
$$BSKTNAME Basket name
$$NAME User's name
hour to several hours, depending on how large the global is.) Here's a tip:
$$NETNAME User's network name
$$NEWS Info on new messages in user's mailbox
$$TMSGCT Number of messages in user's mailbox
$$TNMSGCT Number of new messages in user's mailbox
KVAPOR Edit message vaporize date in user's basket
LASTACC Record info on user's last access of message
MAKENEW Make message new
NONEW Make message not new
PAGE Enter RETURN to continue or '^' to exit:
WAIT Press RETURN to continue:
You can cut down the time that this will take by running option
XMXUTIL1 $$CONVERT Convert InterNet date/time to FileMan date/time
$$CTRL Strip control characters
$$DECODEUP ~U~ to ^
$$ENCODEUP ^ to ~U~
$$GMTDIFF +-HHMM difference from GMT
$$INDT Convert FileMan date/time to InterNet date/time
$$MAXBLANK Reduce 3 or more consecutive blanks to 2
$$MELD Combine string and number
$$MMDT Convert FileMan date/time to MailMan date/time
$$SCRUB Strip control characters and leading/trailing blanks
XMMGR-PURGE-AI-XREF (AI x-Ref Purge of Received Network Messages)
$$STRIP Strip leading/trailing blanks
$$TIMEDIFF Decimal time difference to +-HHMM
$$TSTAMP Time stamp
$$ZONEDIFF +-HHMM from another time zone
XMXUTIL2 $$BSKT Which basket is message in?
$$DATE Get message date.
$$FROM Get message from.
$$KSEQN Get message sequence number in user's basket.
$$LINE How many lines are in the message?
$$NEW Is this message new for this user?
prior to installing this patch. This will reduce the number of xrefs in the
$$PRI Is this message priority?
$$QRESP Is this a response?
$$RESP How many responses are in the message?
$$SUBJ Get message subject.
$$ZDATE Get message date.
$$ZFROM Get message from.
$$ZNODE Get message zero node.
$$ZPRI Is this message priority?
$$ZREAD How many responses has the user read?
$$ZSUBJ Get message subject.
German Heart Institute, Berlin, Germany; San Francisco CIOFO
AI xref global.
INMSG Message info
INMSG1 General message info
INMSG2 Specific message info
INRESP Response info
INRESPS Message response info
XMXUTIL3 Q List message's addressees
QD List message's recipients
QL List message's later'd addressees
QN List message's network header lines
XMXUTIL4 N/A
- Enables message number recycling. To do this,
XMYPOST9 N/A
XMYPOSTA N/A
XMYPRE2 N/A
XMYPRE2A N/A
XMYPRE2B N/A
===========================================================================
INSTALLATION:
NOTES:
--A new field (17.1, MAX DIGITS FOR MESSAGE NUMBER) has been added to file
a. This patch should be installed after hours, when user activity is at a
minimum. It should not be queued, because TaskMan should not be running.
b. This patch requires Kernel patches XU*8.0*67, XU*8.0*112, and XU*8.0*113.
c. For any site running MAS (all VAMCs), this patch requires FileMan patch
DI*22.0*1. Caution: KIDS will not check for this patch because not all
sites run MAS. It is up to each site running MAS to check for DI*22.0*1.
d. All MailMan users, including fictitious users, must have an access code,
or they will no longer receive mail.
e. To shorten installation time, which runs about 1 hour per 200,000 messages
in file 3.9, you might consider running the message purges the day before
4.3, to let each site decide how large the numbers may get before they
the installation:
- XMMGR-PURGE-AI-XREF (AI x-Ref Purge of Received Network Messages)
- XMPURGE-BY-DATE (Purge Messages by Origination Date)
- XMAUTOPURGE (Automatic Purge of MailMan Messages)
f. DSM sites running SlotMaster may see routine mapping problems with ZSLOT
users, even after disabling mapping. Therefore, such sites should consider
the following steps:
- Shutdown ZSLOT on all nodes.
- Disable all mapped XM routines.
- Load this patch.
recycle and start again (from 100000). The post-init will set it to
- Enter manual edits.
- Rebuild mapped routine sets.
- Shutdown/restart all DSM c nfigurations.
An alternative to the above steps is to disable all mapped XM routines about
a week before you load this patch. That way you wouldn't need to shutdown
ZSLOT or shutdown/restart DSM configurations.
g. If your site is running POP3, you should immediately load patch XM*7.1*71
after installing this patch.
INSTRUCTIONS:
the maximum length of your site's existing message numbers. (If it's less
1. This patch replaces routine ^XMRPCTS1, which contains your site's TWIX
routing info. Before you install this patch, copy the current TWIX info
from that routine at your site. After you install this patch, edit
the new ^XMRPCTS1 to set your site's current TWIX info. Specifically:
XMRPCTS1 ;(KC-VAMC)/XXX-Simple PCTS front end to MailMan ;03/19/98 11:10
;;7.1;MailMan;**6,50**;Jun 02, 1994
N XMUS,XMFM,XMSTR,XMRI,XMTO,XMABORT
;+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
;All should be sent to XXX@VHA.DMIA the local PCTS Domain
;Edit these for your site. <---Copy your site's TWIX info
than 7, it will be set to 7. If it's greater than 14, it will be set to 14.)
S XMUS="XXXX" ;Local routing indicator <---from this line
S XMFM="YYYY" ;from line <---and this line
I XMUS="XXXX"!(XMFM="YYYY") S %="FIX Routing codes !!!"_XMPCTS0("ERR")
;-------------------------------------------------------------
2. The TIME ZONE field in file 4.3 must have your site's time zone in it.
Please check and ensure that it is there.
3. DSM SITES: Disable all mapped XM routines. In step 13, we'll rebuild
the map set with *different* routines, because many have become obsolete.
4. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option to load
the patch into a transport global.
You may change it afterward.
5. On the Manage MailMan:Local Delivery Management menu, use the following
option to stop the background filer:
STOP background filer (XMAD)
Are you sure you want the BACKGROUND FILERS to STOP delivering mail NO// YES
===
<<< Mail Deliveries will stop momentarily. >>>
<< Background filer will stop before delivering the next message !!! >>>
6. Stop TaskMan. You may also wish to shut down HL7 filers/LLP's and other
background tasks which may attempt to create new messages.
7. Place option XMUSER out of order. (We do it ourselves, instead of letting
--A new field (31, LOCAL CREATE DATE) has been added to file 3.9. The post-
KIDS do it, because we're going to place XMUSER back in order during the
post-init.) To place XMUSER out of order, enter FileMan, and:
VA FileMan 21.0
Select OPTION: ENTER OR EDIT FILE ENTRIES
==========================
INPUT TO WHAT FILE: OPTION// <press return>
==============
EDIT WHICH FIELD: ALL// OUT OF ORDER MESSAGE
====================
THEN EDIT FIELD: <press return>
init will go through the file 3.9, populate the new field with the date
==============
Select OPTION NAME: XMUSER MailMan Menu
======
OUT OF ORDER MESSAGE: Loading MailMan patch XM*7.1*50
===============================
Select OPTION NAME: <press return>
==============
Select OPTION: <press return>
==============
8. If you journal the global ^XMBX, your journal space may fill up when the
the message was sent, and create the new "C" xref. (This will take about
^XMBX(3.9,"AI", xref global is reconfigured. You may wish to disable
journaling. To disable journaling:
8a. DSM SITES: You may disable journaling for a particular global:
>D ^%GLOMAN
==========
Global Management Utility
Global > ^XMBX
====
^XMBX is currently defined
1 hour per 200,000 messages.) Here's a tip:
1. Show GLOBAL Characteristics
2. Change Access Privileges
3. Change Journaling Capability
4. Change DATA GROWTH AREA
Enter option > 3
=
Journaling [E=Enabled/D=Disabled] <E> D
=
You can cut down the time that this will take by running option
- Characteristics updated
1. Show GLOBAL Characteristics
2. Change Access Privileges
3. Change Journaling Capability
4. Change DATA GROWTH AREA
Enter option > <press return>
==============
Global > ^<press return>
XMPURGE-BY-DATE (Purge Messages by Origination Date)
==============
8b. CACHE SITES: You may disable journaling for a specific job:
%SYS>D DISABLE^%NOJRN
================
8c. MSM SITES: Consult MSM documentation for how to disable journaling.
9. 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
and XMAUTOPURGE (Automatic Purge of MailMan Messages)
Backup a Transport Global
Install Package(s)
Select INSTALL NAME: XM*7.1*50 Loaded from Distribution <date/time>
=========
=> <header> ;Created on <date/time>
This Distribution was loaded on <date/time> with header of
<header> ;Created on <date/time>
It consisted of the following Install(s):
XM*7.1*50
prior to installing this patch. This will reduce the number of messages
XM*7.1*50
Install Questions for XM*7.1*50
Incoming Files:
3.6 BULLETIN (Partial Definition)
Note: You already have the 'BULLETIN' File.
3.7 MAILBOX
in file 3.9.
*BUT YOU ALREADY HAVE 'MAIL BOX' AS FILE #3.7!
Shall I write over your MAIL BOX File? YES// <press enter>
=============
3.73 MESSAGES TO BE NEW AT A LATER DATE
Note: You already have the 'MESSAGES TO BE NEW AT A LATER DATE' File.
3.8 MAIL GROUP (Partial Definition)
Note: You already have the 'MAIL GROUP' File.
--The message purge processes have been changed to operate off LOCAL
3.9 MESSAGE
Note: You already have the 'MESSAGE' File.
4.2 DOMAIN (Partial Definition)
Note: You already have the 'DOMAIN' File.
4.2997 REMOTE USER DIRECTORY (Partial Definition)
Note: You already have the 'REMOTE USER DIRECTORY' File.
4.2999 MESSAGE STATISTICS (Partial Definition)
CREATE DATE. The date purge routine is now much faster, since it has an
Note: You already have the 'MESSAGE STATISTICS' File.
4.3 MAILMAN SITE PARAMETERS
*BUT YOU ALREADY HAVE 'KERNEL SITE PARAMETERS' AS FILE #4.3!
Shall I write over your KERNEL SITE PARAMETERS File? YES// <press enter>
=============
Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES
===
appropriate xref to work with. The weekday unreferenced messages purge can
----------------------------------------------------------------------
NOTE: If you want users to be able to use MailMan during the post-init,
it's important that you answer NO to the following question,
otherwise KIDS will place all options in this patch out of order until
the install is finished:
----------------------------------------------------------------------
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO
==
... <lots of installation stuff is shown> ...
The changes included in this patch are so extensive, that several of the
focus better and thus be more efficient.
----------------------------------------------------------------------
NOTE: When the POST-INIT starts, continue with steps 10 through 17.
The following is displayed when the post-init starts:
Running Post-Install Routine: ^XMYPOST9
Fire xrefs on 'timezone' field of the MailMan site parms file.
Check/Redo AI xref...
--Other fields have changed their focus from message number to the LOCAL
----------------------------------------------------------------------
... <lots of installation stuff is shown> ...
XM*7.1*50 Installed.
<shows date and time>
Install Message sent #<shows message number>
Starting Menu Rebuild: <shows date and time>
CREATE DATE:
... <shows rebuilding of menus> ...
Install Completed.
10. Start TaskMan. If you shut down HL7 filers/LLPs or any other background
tasks, you may restart them.
11. Start the background filer.
On the Manage MailMan:Local Delivery Management menu, use the following
option to start the background filer:
START background filer
<< Background filer will start soon. >>
File 3.7, MailBox:
12. Place option XMUSER back in order by entering FileMan and:
VA FileMan 21.0
Select OPTION: ENTER OR EDIT FILE ENTRIES
==========================
INPUT TO WHAT FILE: OPTION// <press return>
==============
EDIT WHICH FIELD: ALL// OUT OF ORDER MESSAGE
====================
THEN EDIT FIELD: <press return>
==============
3.7,1.2 MESSAGE @ REINSTATEMENT becomes DATE @ REINSTATEMENT (The post-
Select OPTION NAME: XMUSER MailMan Menu
======
OUT OF ORDER MESSAGE: Loading MailMan patch XM*7.1*50
Replace @
===
SURE YOU WANT TO DELETE? Y (Yes)
===
Select OPTION NAME: <press return>
==============
Select OPTION: <press return>
init will change any existing message numbers in this field to their equiv-
==============
13. DSM SITES: After patch has installed, rebuild your map set.
Many routines have become obsolete and should be removed from the map
set. Here is a new recommended list of routines to map, should your
site choose to map routines:
Minimum Additional
------- ----------
XM XMBPOST
XMC1 XMC,XMC1*
XMJ* XMD
alent dates.
XML1CRC,XML4CRC*,XMLSWP* XMK*
XMR,XMR0* XML
XMS,XMS0* XMR1*
XMS1,XMSMAIL
XMVVITAE
XMXSEC
XMXUTIL
14. This patch replaces routine ^XMRPCTS1, which contains your site's TWIX
routing info. In step 1, you copied the TWIX info for your site from
that routine. Now, edit the new ^XMRPCTS1 to set your site's TWIX info.
File 4.3, MailMan Site Parameters:
Specifically:
XMRPCTS1 ;(KC-VAMC)/XXX-Simple PCTS front end to MailMan ;03/19/98 11:10
;;7.1;MailMan;**6,50**;Jun 02, 1994
N XMUS,XMFM,XMSTR,XMRI,XMTO,XMABORT
;+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
;All should be sent to XXX@VHA.DMIA the local PCTS Domain
;Edit these for your site. <---Put your site's TWIX info
S XMUS="XXXX" ;Local routing indicator <---at this line
S XMFM="YYYY" ;from line <---and this line
I XMUS="XXXX"!(XMFM="YYYY") S %="FIX Routing codes !!!"_XMPCTS0("ERR")
4.3,4.301 NO-PURGE MESSAGES BUFFER becomes NO-PURGE DAYS BUFFER (The post-
;-------------------------------------------------------------
15. For those sites using class III ^ASKX820, you should edit routine
^ASKX820. It calls ENT^XMAD1, an illegal entry point which no longer exists.
Replace it with a call to ENT1^XMD.
16. For those sites running class III WordManager, you will have to find the
WordManager routine containing D OK^XMA22. For version 5.01, it's in
routine ^WMWTWM. It may be in other routines in other versions.
OK^XMA22 is an undocumented entry point into MailMan which no longer
exists. Edit the WordManager routine as follows:
Replace:
init will set this field to null, which defaults to 2 days. You may change
S ^XMB(3.9,XMZ,2,0)="^^"_(J-1)_"^"_(J-1)
EDIT ;
S DIE="^XMB(3.9,",DA=XMZ,DR=".01;3" D ^DIE
REC ;
S XMMG=$P(^DIC(3,DUZ,0),"^",1) D DES^XMA21 G:X="^" EXIT
SEND ;
S XMR="",XMTEXT="^XMB(3.9,XMZ,2," D OK^XMA22,EN1^XMD
EXIT U TRM S R7=ZR7,TRM=$I K ZR7,ZMM
with:
S ^XMB(3.9,XMZ,2,0)="^^"_(J-1)_"^"_(J-1)
MailMan manuals have been rewritten. The full patch description and the
it afterward.
EDIT ;
;S DIE="^XMB(3.9,",DA=XMZ,DR=".01;3" D ^DIE
REC ;
;S XMMG=$P(^DIC(3,DUZ,0),"^",1) D DES^XMA21 G:X="^" EXIT
SEND ;
;S XMR="",XMTEXT="^XMB(3.9,XMZ,2," D OK^XMA22,EN1^XMD
ERS ; EDIT, REC, SEND
N XMV,XMRESTR,XMINSTR,XMSUBJ,XMABORT
S XMABORT=0
S XMSUBJ=XMSUB
4.302,3 FIRST MESSAGE TO PROCESS becomes START PURGE DATE
D INIT^XMVVITAE
D ES^XMJMSO
D BODY^XMJMS(XMDUZ,XMZ,XMSUBJ,.XMRESTR,.XMABORT)
I XMABORT D KILLMSG^XMXUTIL(XMZ) G EXIT
D INIT^XMXADDR
D TOWHOM^XMJMT(XMDUZ,"Send",.XMINSTR,.XMRESTR,.XMABORT)
D:'XMABORT SENDMSG^XMJMSO(XMDUZ,XMZ,XMSUBJ,.XMINSTR,.XMRESTR,.XMABORT)
D:XMABORT KILLMSG^XMXUTIL(XMZ)
D CLEANUP^XMXADDR
EXIT U TRM S R7=ZR7,TRM=$I K ZR7,ZMM
4.302,4 LAST MESSAGE TO PROCESS becomes STOP PURGE DATE
17. For those sites using class III ^BJMAIL*, you should edit routine ^BJMAIL
to correct its egregious violations of the SAC. If you don't, MailMan will
will not function properly. Once you have edited ^BJMAIL, you may delete
routine ^BJMAIL1, since it will no longer be used. Edit ^BJMAIL as follows:
Replace:
MSG Q:'$D(T)
... thru ...
WRITE ;Write a message - not part of the main program.
With:
MSG ;
4.302,8 LAST MESSAGE PROCESSED becomes LAST DATE PROCESSED
N XMINSTR
Q:'$D(T)
Q:'$O(T(0))
D GROUP
Q:$O(TO(""))=""
I $G(CONFIRM) S XMINSTR("FLAGS")=$G(XMINSTR("FLAGS"))_"R"
I $G(PRIO) S XMINSTR("FLAGS")=$G(XMINSTR("FLAGS"))_"P"
I $G(INFO) S XMINSTR("FLAGS")=$G(XMINSTR("FLAGS"))_"I"
I '$D(FROM) S FROM=.5
D SETFROM^XMD(.FROM,.XMINSTR)
4.3,4.304 WEEKDAY MESSAGES TO PURGE becomes WEEKDAY DAYS TO PURGE (Any value
I '$D(TITLE) S TITLE="Title not specified by sender"
I $L(TITLE)>65 S TITLE=$E(TITLE,1,65)
I $L(TITLE)<3 S TITLE=TITLE_"..."
D SENDMSG^XMXAPI(FROM,TITLE,"T",.TO,.XMINSTR)
K CONFIRM,FROM,GROUP,INFO,PRIO,T,TITLE,TO
Q
GROUP ;
Q:$G(GROUP)=""
I +GROUP=GROUP S:$D(^XMB(3.8,GROUP,0)) TO($P(^XMB(3.8,GROUP,0),U))="" Q
S TO("G."_GROUP)=""
your site has in this field will be changed by the post-init from number of
Q
WRITE ;Write a message - not part of the main program
----------------------------------------------------------------------
NOTE: Once the POST-INIT stops, continue with steps 18 through the end.
----------------------------------------------------------------------
18. If you disabled journaling in step 8, you should enable it again here.
18a. DSM SITES:
>D ^%GLOMAN
messages to the equivalent number of days. You may change it afterward.)
Global Management Utility
Global > ^XMBX
====
^XMBX is currently defined
1. Show GLOBAL Characteristics
2. Change Access Privileges
3. Change Journaling Capability
4. Change DATA GROWTH AREA
4.3,142 NO-PURGE DAYS BUFFER becomes NO-PURGE DAYS BUFFER (LOCAL)
Enter option > 3
=
Journaling [E=Enabled/D=Disabled] <D> E
=
- Characteristics updated
1. Show GLOBAL Characteristics
2. Change Access Privileges
3. Change Journaling Capability
4. Change DATA GROWTH AREA
Enter option > <press return>
==============
Global > ^<press return>
==============
18b. CACHE SITES:
%SYS>D ENABLE^%NOJRN
===============
18c. MSM SITES: Consult MSM documentation for how to enable journaling.
19. For those sites running POP3, you should load patch XM*7.1*71 immediately
NOTES:
after loading this patch. Other sites may load patch XM*7.1*71 at their
leisure.
20. On the KIDS:Utilites menu, use the following option to review the
install:
Install File Print
Review the automatic domain name changes which occurred during the post-init.
If there were any errors noted for a particular domain, that domain did not
have its new name added as a synonym. (Error messages are preceded by ***,
and tell you what was wrong.) You must correct the error manually and add
the synonym manually. Remember, you are not to change any domain name.
|
