Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp

more options
hp.com home
End of Jump to page title
HP Services Software Patches
Jump to content

» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

patches by topic
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

connection tools
» nameserver lookup
» traceroute
» ping

Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_MIME-V0100 Alpha V7.3 MIME ECO Summary
TITLE: OpenVMS VMS73_MIME-V0100 Alpha V7.3 MIME ECO Summary
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       For OpenVMS savesets, the name of the compressed saveset
       file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
       kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
       saveset is copied to your system, expand the compressed
       saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
       For PCSI files, once the PCSI file is copied to your system,
       rename the PCSI file to kitname.pcsi-dcx_axpexe or
       kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
       RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe.  The
       resultant file will be the PCSI installation file which can be
       used to install the ECO.

New Kit Date:       20-SEP-2002
Modification Date:  Not Applicable
Modification Type:  NEW KIT

Copyright (c) Compaq Computer Corporation 2002.  All rights reserved.

OP/SYS:     OpenVMS Alpha V7.3


SOURCE:     Compaq Computer Corporation


     ECO Kit Name:  VMS73_MIME-V0100
     ECO Kits Superseded by This ECO Kit: None
     ECO Kit Approximate Size:  432 Blocks
     Kit Applies To:  OpenVMS Alpha V7.3
     System/Cluster Reboot Necessary:  No
     Rolling Re-boot Supported:  Information Not Available
     Installation Rating:  INSTALL_3
                            3 - To be installed on all systems running
                                the listed versions of OpenVMS which
                                are experiencing the problems described.
     Kit Dependencies:

       The following remedial kit(s), or later, must be installed BEFORE
       installation of this, or any required kit:


       In order to receive all the corrections listed in this
       kit, the following remedial kits should also be installed:



An ECO kit exists for MIME on OpenVMS Alpha V7.3. This 
kit addresses the following problems: 


     o  Mime message corruption can occur for  messages  created  with
        OpenVMS  Mime  that  have  text of more than just a few lines.
        Messages appear to be truncated or text may appear garbled  or
        out  of  context.   This happens when the textual message part
        has a length (when combined with the Mime  header  area)  that
        exceeds 1024 characters.

          Images Affected:[SYSEXE]MIME.EXE

     o  Multipart messages created with OpenVMS  Mime  may  cause  the

        "Invalid boundary marker" when attempting to read (decode)
        the message.

          Images Affected:[SYSEXE]MIME.EXE

     o  The file name (known as the Disposition file name),  would  be
        added more than once when multiple edits and saves occur.

          Images Affected:[SYSEXE]MIME.EXE

     o  A SYSTEM-F-ACCVIO error can occur when a SAVE is performed  on
        a message when a message part has previously been removed.

          Images Affected:[SYSEXE]MIME.EXE

     o  When the MIME> LIST command is used for a  message  with  only
        one  main  part, (a single part message), no attachment number
        is listed.  This may confuse the user as to  which  attachment
        number  to specify with the EXTRACT command, which requires an
        attachment number.  On-line help has been modified to  specify
        attachment number one for single part messages, as follows:


        Format: EXTRACT/ATTACHMENT=attachment-number [filename]

        NOTE: The /ATTACHMENT qualifier is required with EXTRACT.
        This qualifier specifies the number of the attachment as
        displayed by the LIST command. In a single part message,
        o attachment number is displayed. For this case specify
        attachment number one.

          Images Affected:[SYSEXE]MIME.EXE

     o  Error messages can be overwritten or garbled when errors occur
        while reading a Mime message.

          Images Affected:[SYSEXE]MIME.EXE

     o  Problems occur while attempting to EXTRACT,  EDIT,  or  REMOVE
        message  parts due to an improper attachment range check or an
	illegal range of message  part  numbers  being  accepted  when
        actually  invalid.   Typically  the symptom is either the part
        fails to extract due to an erroneous error, or  the  incorrect
        part  is  extracted,  edited,  or  removed.   This may include
        removal  or  extraction  of  non-message  parts  or   non-leaf
        attachments, such as multipart or multipart alternative parts.

          Images Affected:[SYSEXE]MIME.EXE

     o  When exiting and prompted to save file, a typographical  error
        would  be  accepted  as a negative response and the file would
        not be saved.

          Images Affected:[SYSEXE]MIME.EXE

     o  While reading a message, the screen may be improperly restored
        which  causes  the  screen  output to be displayed improperly.
        This may happen when returning from  a  spawned  process  that
        provided  output  to the same screen device, executed commands
        in DCL that caused errors, and so forth.

          Images Affected:[SYSEXE]MIME.EXE

     o  Other miscellaneous errors and problems  that  were  corrected

          1.  Certain file errors were not  being  reported  or  handled
              properly during opening and editing of a message.

          2.  Fix regression where multiple SAVEs were  not  saving  the
              file and only the first save was being written.

          3.  Code optimization in remove attachment.

          4.  If an error occurred during  ADD,  the  message  would  be
              corrupted (there was no message recovery)

          5.  Under certain situations a  message  would  not  be  saved
              during a SAVE, EXIT, CLOSE, NEW, OPEN, and ^Z operation.

          6.  Errors would  occur  while  attempting  to  use  the  edit
              command as defined in MIME$MAILCAP.DAT.

          7.  No support for edit of HTML attachments  (Unix-style  file
              name parsing.

          8.  Errors on, or  failure  to  read  plain  text  due  to  an
              erroneous content-type parameter match on text style.

          9.  Update this version image IDENT,  MIME  Version  and  MIME
              HELP (MIME$HELP.HLB) to V1.7

         10.  Updated MIME HELP

          Images Affected:[SYSEXE]MIME.EXE

     o  For  a  large  MIME  message  (262  Mbyte)  comprised  of   40
        attachments,  attachments  are not listed properly.  Observing
        the output from the MIME> LIST command and typing  Control_S/Q
        shows  the  attachments  and the filenames.  However, manually
        scrolling back to review attachments and filenames results  in
        a  display  where attachment numbers and/or most filenames are
        omitted.  In trying to  duplicate  the  problem,  other  large
        messages with many attachments did not reproduce the problem.

          Images Affected:[SYSEXE]MIME.EXE


No reboot is necessary after successful installation of the kit.


Install this kit with the POLYCENTER Software installation  utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:


The kit location may be a tape drive, CD, or a disk directory that
contains the kit.

Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt

Special Installation Instructions:

     o  Scripting of Answers to Installation Questions

        During installation,  this  kit  will  ask  and  require  user
        response  to  several  questions.  If you wish to automate the
        installation of this kit and avoid having to provide responses
        to  these  questions,  you must create a DCL command procedure
        that includes the following definitions and commands:


           -  Add  the  following  qualifiers  to  the  PRODUCT  INSTALL
              command and add that command to the DCL procedure.


           -  De-assign the logicals assigned

        For  example,  a  sample   command   file   to   install   the
        VMS73_MIME-V0100 kit would be:

          $ exit

All trademarks are the property of their respective owners.
Files on this server are as follows:
privacy statement using this site means you accept its terms