Australia - Updated: 24-SEP-2003
hp.com home products and services support and drivers solutions how to buy
» contact hp
hp.com home hp OpenVMS ECOs

IMPORTANT NOTICE

The online distribution of OpenVMS and related product patches is being migrated to the HP ITRC (Information Technology Resource Center) patch distribution site. The new ITRC patch server will allow OpenVMS customers to take advantage of many enhanced features for patch searching and distribution.

Beginning August 1, 2003, OpenVMS and related Layered Product, publicly available patches will be available from the HP ITRC web site at

http://itrc.hp.com/service/patch/mainPage.do

The same patches will still be available from the existing patch server in Colorado Springs (http://www.support.compaq.com/patches/) through the end of October 2003, to give customers sufficient time to update their bookmarks and make the transition to the HP ITRC web site.

ECO kits will also be available by raw FTP from (ftp://ftp.itrc.hp.com/).

PLEASE UPDATE YOUR BOOKMARKS AND REGISTER ON THE NEW SITE NOW

Note: if you're having trouble connecting to the ITRC site, please delete any cookies for "itrc.hp.com" from your browser and try again. Report any difficulties with or suggestions to MrVMS

» Sydney CSC home page

Navigation
» ECOinfo main index
» Search ECOs
» Search FTP site
» Browse FTP site

ECO Indexes
» Chronological Index
» Indexed by Version
» Indexed by Rating
» Alpha Indexed by Name
» VAX Indexed by Name
» On Hold List

Associated Links
» OpenVMS Home Page
» OpenVMS News
» DIA/WIS Web Service

Feedback
» mail to CSC
.
Sydney Customer Support Centre OpenVMS ECO information
    Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)

VAXMIME02_072 VAX V7.2 MIME Fixes ECO Summary

To obtain this kit please call the Customer Support Centre or use the FTP site

Search for this ECO kit and dependencies
Search the Compaq FTP web site this kit (exact match)
Search the Compaq FTP web site this or related ECOs

    
      
    Copyright (c) Compaq Computer Corporation 2000.  All rights reserved.
    
    Modification Date:  19-OCT-2000
    Modification Type:  Updated Kit:  Supersedes VAXMIME01_072
    
    OP/SYS:     OpenVMS VAX
    
    COMPONENT:  MIME
    
    SOURCE:     Compaq Computer Corporation
    
    ECO INFORMATION:
    
         ECO Kit Name:  VAXMIME02_072
         ECO Kits Superseded by This ECO Kit:  VAXMIME01_072
         ECO Kit Approximate Size:  306 Blocks
         Kit Applies To:  OpenVMS VAX V7.2
         System/Cluster Reboot Necessary:  No
         Rolling Re-boot Supported:  Not Applicable
         Installation Rating:  INSTALL_2
                               2 - To be installed on all systems running
                                   the listed version(s) of OpenVMS and
                                   using the following feature(s):
    
                                     MIME Utility
    
    
         Kit Dependencies:
    
           The following remedial kit(s) must be installed BEFORE
           installation of this kit:
    
             VAXUPDATE01_072
    
           In order to receive all the corrections listed in this
           kit, the following remedial kits should also be installed:
    
             None
    
    
    ECO KIT SUMMARY:
    
    An ECO kit exists for MIME on OpenVMS VAX V7.2.  This kit addresses the
    following problems:
    
    Problems Addressed in VAXMIME02_072:
    
      o  The following problems were corrected in this MIME release:
    
           1.  Memory corruption occurred when using the OpenVMS MIME
               utility, especially when repeatedly opening and closing
               UUencoded files.
    
           2.  When composing a simple, single-part, MIME text message
               (with no attachments), the READ command would display
               properly until the file was saved, closed, and re-opened
               for reading.  Then extra headers for a text attachment
               would appear in the MIME header area, which resulted in an
               error:
    
                 %MIME-E-OPNFILERR, 'error opening file'
    
           3.  When using MIME to compose messages, the resulting MIME
               file did not have its MIME message boundary parameter
               string properly quoted.  The string is part of the
               'Content-Type:' multipart-mixed header field.
               Consequently, the message may not be read correctly.
    
           4.  An ANALYZE/RMS error would occur, if used on the zero
               allocated block file created, but never written to, by
               composing a MIME 'NEW' Message.
    
           5.  Attachments can be removed, but not saved, for READ only
               messages.  This behavior should not be allowed for READ
               only messages.
    
           6.  An ACCVIO error can occur when MIME attempts to display
               the VIEWER error message.  This occurs when a MIME file is
               opened for which no viewer exists.
    
           7.  Multiple memory leaks occur when repeatedly opening and
               closing UUencoded files.  This excessive use of memory
               resources may not be readily apparent to the user.
    
           8.  Extraneous files can be left behind by MIME, if the user
               performs a QUIT command, or after prompting and answering
               'no' to a file save operation on EXIT.
    
           9.  The OPEN MIME command with the /NEW qualifier would fail,
               which is redundant with the NEW command.  This was removed.
    
          10.  The MIME command OPEN would continue to parse for multiple
               files (up to eight), if none were specified with the OPEN
               command.  The operation would usually fail with the
               following errors:
    
                 %RMS-E-FNF, file not found
                 %MIME-W-NOMSGOPEN, No currently active message
    
          11.  Multiple error messages with the same error would be
               returned, if the file which was attempted to be opened was
               not found.
    
          12.  If one NEW MIME message that is writeable was closed, and
               a NEW one specified, the old data file could display from
               the previous edit session.  MIME was not cleaning up files
               during a close and not freeing memory.
    
          13.  File types (extensions), their Content-type/subtype and
               their encoding scheme optionally defined in MIME$FILETYPES.DAT
               file was not being read properly, nor would it allow error
               recovery.  Also, an error message may not display when the
               file had errors.
    
          14.  Sometimes informational messages get overwritten when MIME
               exits with the DCL prompt.
    
          MIME HELP (MIME$HELP.HLB) and MIME commands (MIMECMD.CLD) were
          updated to reflect the above changes.
    
            Images Affected:
              -  [SYSEXE]MIME.EXE
              -  [SYSHLP]MIME$HELP.HLB
    
    
    Problems Addressed in VAXMIME01_072:
    
      o  ACCVIO on OPEN message command.
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  NETSCAPE creates an error window 'unable to find the file'
         when NETSCAPE is defined in MIME$MAILCAP.DAT as the viewer of
         choice for text/html (type/subtype).
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  MIME file OPEN commands continuously ACCVIO with a specified
         file.  They also provide useless FAO Information:
    
           %SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual
                             address=!XH, PC=!XH
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  Composing a MIME message with an ADD/CONTENT="image/jpg"
         command causes the following error and then exit:
    
           %CLI-F-SYNTAX, error parsing 'ContentTypeValue' error and exits.
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  When opening and attempting to read a valid MIME encoded,
         multi-part message, MIME displays the text portion of the
         message correctly but, if the attachment is of a part/subpart
         that VMS does not understand (such as .DOC, .XLS etc.), it
         displays the message:
    
           <No Viewer for Attachment: (null)>
    
         MIME now displays the local filename if the disposition
         filename is empty rather than NULL
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  If a single $FAO argument (for $PUTMSG) is used in LIB$SIGNAL
         (and defined in MIME$MESSAGE.MSG, the status/error message is
         not printed out in its entirety - the text is missing and the
         actual !AZ FAO control parameter is printed instead.
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  A section with examples was added to the HLP file for
         MIME$MAILCAP.DAT content type/subtype definition file.
    
           Images Affected:  [SYSHLP]MIME$HELP.HLB
    
      o  Errors occur when attempting to OPEN/READ UUENCODED Files.
         Depending on the file, you may see SMG$ errors or 'junk' error
         messages:
    
           - %SMG-W-STRTERESC, illegal escape sequence embedded
                        in string, %MIME-E-OPNFILERR
    
                                     or
    
           MIME> open MAIL.MIME_MSG
                 %MIME-I-SAVEPART, Saving part
                  ´zêxzêéGêd|ê`|êü{êÌzê³Hxê.ø{êÌzêõI\|êd|ê`|êü/´êêà
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  When attempting to open a Compaq Corporate-generated message,
         MIME gives a MIME$_OPNFILERR when the MIME file has spaces
         within the filename (part of the UUencoded file).
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  Embedded filenames within MIME-encoded files that are non-ODS-2
         compliant would cause MIME to fail to open/create the
         file and instead would ACCVIO or produce the error message:
    
           %MIME-E-OPNFILERR
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  Added error codes:  MIME$_DBL_ERROR for condition handler and
         action routine and MIME$_FILENAMMOD informational for user
         when filename is modified, also INITERROR fatal, MIME$_INFO,
         and fixed /FAO=n to match parameters.
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  Mime ACCVIO's on an .XLS spreadsheet while incorrectly
         handling the extract of a non-multipart UUENCODED file.
    
           %SYSTEM-F-ACCVIO, access violation, reason mask=00,
              virtual address=0000000000000004,
              PC=0000000000031FD4, PS=0000001B
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  Fixed a memory leak.
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  MIME will ACCVIO if the user adds valid commands that invoke
         an application to read a MIME encoded (MAIL) file in the
         user's (or SYSTEM's) MIME$MAILCAP.DAT file. T he error message
         sent is:
    
           !%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual
             address=29776F64, PC=000085D4, PSL=03C00000
           !break on exception at STRING\cistrncmp\%LINE 360+2C
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  If an attachment was extracted more than once, an ACCVIO would
         result due to a stale pointer used that was previously freed.
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  On an attempt to open a MIME encoded file the process can
         ACCVIO and due to the nature of the Exception Handler, the
         process may loop with the ACCVIO error output (constant
         re-signaling).
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  MIME's ExceptionHandler() does not handle various argument
         length exceptions
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  A parent process will hang upon return of a spawned process,
         if that subprocess encounters an error (or warning) while
         spawned.
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  The MIME EDIT (attachment #) command fails to edit the part,
         edits the incorrect part, simply returns, or returns with the
         following error message:
    
           %CLI-W-IVVERB, unrecognized command verb - check validity and
                          spelling \TPU\
    
           Images Affected:  -  [SYSEXE]MIME.EXE
    
      o  The MIME SAVE command could fail with:
    
            %MIME-E-OPNFILERR, Error opening file -RMS-E-FEX, file already
                               exists
    
            Images Affected:  [SYSEXE]MIME.EXE
    
      o  When exiting MIME after an edit and save session, the user
         would be prompted to save the file.  This causes confusion,
         since the file was previously saved and there were no file
         modifications in the interim.
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  The user is not informed if a file is successfully saved.
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  When adding an attachment with the following MIME command and
         qualifier:
    
           MIME> ADD /CONTENT_TYPE="type/subtype"
    
         quotation marks are required as part of the qualifier syntax.
         However, when attempting to read that same file and
         attachment, the following error would result:
    
           <No Viewer for Attachment: file_name>
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  When attaching a message, the message ID is random characters.
    
           Images Affected:  [SYSEXE]MIME.EXE
    
      o  MIME HELP (MIME$HELP.HLB) has been updated to reflect user
         documentation.
    
           Images Affected:  [SYSHLP]MIME$HELP.HLB
    
    
    RELATED ARTICLES:
    
    Detailed articles describing the problems listed above may exist in
    the OPENVMS database.  To view these articles, open the appropriate
    product database and perform a query using either of the following
    search strings: 'VAXMIME02_072' or 'VAXMIME'.
      
    
    ECO KIT ORDERING INSTRUCTIONS:
    
    If after an evaluation you wish to obtain this kit, request it
    electronically using the appropriate Advanced Electronic Services
    (AES) Service Tool.  If you are not familiar with how to request
    kits electronically, open the DIA, WIS or DSNLINK database and
    review the article entitled:
    
         [AES] How To Electronically Request ECO Kits Using Service Tools
    
    
    INSTALLATION NOTES:
    
    The system/cluster does not need to be rebooted after this kit is
    installed.
    
    All trademarks are the property of their respective owners.
      
      ==========================================================================
      |                     Table of Kit Image Information                     |
      +----------------------------+----------+-----------------+--------------+
      |                            | Overall  | Image File      | Image Link   |
      | Image Name                 | Checksum | Identification  | Date/Time    |
      +----------------------------+----------+-----------------+--------------+
      | MIME.EXE                   |%X52933191| V1.4            | 22-SEP-2000  |
      |                                       |                 | 08:45:11.89  |
      +----------------------------+----------+-----------------+--------------+
    
privacy statement using this site means you accept its terms feedback to the webmaster
VMS rules VMS rocks OpenVMS rules OpenVMS rocks