XM*8.0*22 (5426)    BUILD (9.6)

Name Value
NAME XM*8.0*22
DATE DISTRIBUTED 2004-03-03 00:00:00
PACKAGE FILE LINK MAILMAN
TYPE SINGLE PACKAGE
DESCRIPTION OF ENHANCEMENTS
            * * * * * * * * * * * * * * * * * * * *
Patch XM*8.0*22
SEND: W XMSG ; S XMTRAN="S: "_XMSG D TRAN^XMC1  Replace MSG With MSG,!
                                                        ===      =====
  Replace <press enter>
          =============
   W XMSG,! ; S XMTRAN="S: "_XMSG D TRAN^XMC1

Select COMMUNICATIONS PROTOCOL NAME:

8. The Kernel Systems Manual tells you how to set up HFS (Host File Server)
devices.  (In v8, Chapter 18 on Host Files is pages 229-232.)  If your site

is using an HFS device to send mail to and receive mail from another site,
your settings should deviate from the recommendations in the manual as
follows:

Using FileMan:

Select OPTION: ENTER OR EDIT FILE ENTRIES  
               =====
INPUT TO WHAT FILE: COMMUNICATIONS PROTOCOL// DEVICE  
                                              ======
NOIS: CMC-0803-31054
EDIT WHICH FIELD: ALL// ASK HOST FILE
                        ========
THEN EDIT FIELD: ASK HFS I/O OPERATION
                 =======
THEN EDIT FIELD: <press enter>

Select DEVICE NAME: HFS        <=== Yours may be different
                    ===
ASK HOST FILE: YES//           <=== Must be YES
ASK HFS I/O OPERATION: YES//   <=== Must be YES
Test Sites: Tennessee Valley HCS (DSM/VMS); Murfreesboro CMOP (Cache/NT);

ASK HOST FILE should be set to YES, so that you will be prompted for
"HOST FILE NAME:".  The site creating the host file could accept the default
or select a name.  The site reading the host file would enter the name of
the file from the sending site.

ASK HFS I/O OPERATION should be set to YES, so that you will be prompted
"INPUT/OUTPUT OPERATION:".  The site creating the host file would answer
"NEW", and the site reading the host file would answer "READONLY".

            Charleston CMOP (Cache/NT); Portland, OR (Cache/VMS)
This is what it should look like when you use the options:

Option: Sequential Media Queue Transmission [XMS-SEQ-TRANSMIT]
          
This option lets you select only those queues which have messages.  If
you can't select a queue, it either doesn't exist or it has no messages.

Select DOMAIN NAME: DOMAIN.EXT                       1 msgs
DEVICE: HOME// HFS  DISK FILE
HOST FILE NAME: TMP.TMP//FORUM.DAT           INPUT/OUTPUT OPERATION: ?

Enter one of the following host file input/ouput operation:
                R = READONLY
                N = NEWVERSION
               RW = READ/WRITE
                                             INPUT/OUTPUT OPERATION: N

Dumping messages now ... Messages dumped: 1

Option: Sequential Media Message Reception [XMR-SEQ-RECEIVE]

Attempts to use the option Sequential Media Queue Transmission
DEVICE: HOME// HFS  DISK FILE
HOST FILE NAME: TMP.TMP//FORUM.DAT           INPUT/OUTPUT OPERATION: R

Messages received: 1
===========================================================================
[XMS-SEQ-TRANSMIT] fail with the variable ER undefined.
This patch fixes that.
 
                    !! A T T E N T I O N !!
IMPORTANT: If you are using the HFS device to receive the mail, you should
either have an HFS_IN device with the Open Parameter set to ReadOnly or set
the ASK HFS I/O OPERATION to YES and choose READONLY when using the device.

NOTE: This patch should be installed during off hours, when user activity
is at a minimum.  It has no patch pre-requisites.
============================================================================ 

ROUTINES:
The second line of the routine now looks like:
            You must manually CHECK entries in the
       ;;8.0;MailMan;**[patch list]**;Jun 28, 2002

              Before          After
Name          Checksum        Checksum        Patch List
------------------------------------------------------------------
XMCB           3553056         3880657        22
XMR           11613068        11821822        22
XMTDR         10257008        10279631        22
* Checksums produced by CHECK^XTSUMBLD

                       DEVICE FILE and
This patch introduces no new routines.
===========================================================================
 
INSTALLATION:
NOTE: This patch should be installed during off hours, when user activity
is at a minimum.  It has no patch pre-requisites.
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 
                 COMMUNICATIONS PROTOCOL FILE
    the patch into a Transport Global on your system.  
4.  Users may be on the system.  You do not need to stop TaskMan
    or the background filer.
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)
                and CORRECT them, if necessary.
 Select INSTALL NAME:    XM*8.0*22     Loaded from Distribution  <date/time>
                         =========
 Install Questions for XM*8.0*22

 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.
                       See instructions.
 Enter a '^' to abort the install.

 DEVICE: HOME// <You may queue it if you wish>
                ------------------------------
6.  DSM Sites: After patch has installed, rebuild your map set, if necessary.
7.  This is a repeat of the information provided in patch XM*7.1*193.
If you use the MailMan option for transferring VistA email messages via
disk/tape to another site, you will have problems if the SEND field
setting for the TAPE entry in the Communications Protocol file is wrong.
The SEND field for the TAPE entry must be set to:
            * * * * * * * * * * * * * * * * * * * *

SEND: W XMSG,! ; S XMTRAN="S: "_XMSG D TRAN^XMC1
            ==
Most of the entries we have found for this don't have the ",!" following
the "W XMSG".  Without the ",!" you don't get the line feed at the end of
each line. This causes a buffer overflow when you try to receive the
message.  Please look at your entry, and edit, if necessary:

Using FileMan:


Select OPTION: ENTER OR EDIT FILE ENTRIES  
               =====
INPUT TO WHAT FILE: COMMUNICATIONS PROTOCOL// <press enter>
EDIT WHICH FIELD: ALL// SEND
                        ====
THEN EDIT FIELD: <press enter>


Select COMMUNICATIONS PROTOCOL NAME: TAPE
                                     ====
TRACK PACKAGE NATIONALLY YES
BUILD COMPONENTS
  • ENTRIES:
    • XMCB
      ACTION:   SEND TO SITE
      CHECKSUM:   B13456133
    • XMTDR
      ACTION:   SEND TO SITE
      CHECKSUM:   B41286924
    • XMR
      ACTION:   SEND TO SITE
      CHECKSUM:   B46190194