MAILWORKS-VMS A1MAIL_ECO3A013 MailWorks for OpenVMS V1.3A ECO Summary
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
The name of the compressed file will be kit_name-dcx_vaxexe
for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
Once the file is copied to your system, it can be expanded
by typing RUN compressed_file. The resultant file will
be the OpenVMS saveset or PCSI installation file which
can be used to install the ECO.
Copyright (c) Digital Equipment Corporation 1996.
All rights reserved.
PRODUCT: MailWorks for OpenVMS, Version 1.3A
OP/SYS: OpenVMS VAX, Version 5.5-2 or greater
OpenVMS Alpha, Version 6.1 or greater
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: A1MAIL_ECO3A013
ECO Kits Superseded by This ECO Kit: A1MAIL_ECO02013
ECO Kit Approximate Size: A1MAIL_ECO3A013.A - 1584 Blocks
A1MAIL_ECO3A013.B - 1134 Blocks
A1MAIL_ECO3A013.C - 2124 Blocks
A1MAIL_ECO3A013.D - 1512 Blocks
A1MAIL_ECO3A013.E - 10368 Blocks
A1MAIL_ECO3A013.F - 17010 Blocks
A1MAIL_ECO3A013.G - 3312 Blocks
Total of 7 files - 37044 Blocks
System Reboot Necessary: No
ECO KIT SUMMARY:
An ECO kit exists for MailWorks for OpenVMS V1.3A on OpenVMS VAX V5.5-2 or
greater or OpenVMS Alpha V6.1 or greater.
The MailWorks for OpenVMS release notes contain a complete explanation of the
fixes included in this ECO kit. Below is a brief description of each of
the fixes:
01-1 New mail notifications using NETBIOS will now work when multiple MUAS
Servers are configured.
01-2 The TCP/IP node name can now be different than the DECnet node name.
Previously it was a restriction that these names be the same.
01-3 Fixed the Connect Server hanging if a bodypart for a particular
message was not found while doing a search.
01-4 Fixed the MUAS Server access violating when attempting to
deliver a message where the first user id length was greater
than 72 characters.
01-5 TCP/IP notification now works with all supported TCP/IP products.
This includes TGV Multinet and Wollongong.
01-6 Fixed a security issue.
01-7 Clean install problem on OpenVMS Alpha regarding Message Router
has been fixed.
01-8 The MAIL drawer display name can now be modified using the VT
component.
01-9 The INIT_MEMMGR routine is now optional.
01-10 Improved Connect Server logging where the DS Servers do not start
up properly.
01-11 The collect command procedure, DMW$COLLECT_INFO.COM, has been
modified to collect additional information about the system to
help troubleshoot problems.
01-12 The SEND/LAST feature in the VT component now works correctly.
01-13 The FORWARD/COVER=filename feature in the VT component now works
correctly.
01-14 The problem where a KEYNOTFOU error would be displayed occasionally
upon exiting from the VT component has been resolved.
01-15 The ability to find documents by size from TeamLinks has been
added.
01-16 The release notes now reference the correct keyword.
01-17 The VT component now properly checks for the concurrent user VT
license.
02-1 Channels are now properly deallocated when attempting to perform
TCP/IP notification.
02-2 The interoperability issues between MailWorks and PathWorks V4.2-1
have been resolved.
02-3 The LIST command in X4MANAGER REMOTE_SERVER mode will now correctly
display the status of the specified servers when a node has been
temporarily removed from a cluster.
02-4 A check has been added to the Connect Server to defend against
corrupt data sizes being passed in. Additionally, logging has
been added to the Connect Server to help solve client memory leak
problems.
02-5 Removed error logging if option routine, INIT_MEMMGR, is not found.
02-6 Added logging to Connect Server to keep track of user logins to the
Connect server and detect any dropped connections.
The TCP/IP transport support has been modified to have quicker
time outs when PCs are turned off or rebooted and it has also been
modified to deal with the PCs running out of buffer space.
02-7 Modified the Connect Server to have better error checking of values
sent to some logging routines. Previously this could cause an
access violation.
02-8 The installation procedure will now put a copy of the kit's
A1MAIL$STARTUP.COM file on the system as .NEW. This was not
previously provided if the A1MAIL$STARTUP.COM on the system was
adequate.
02-9 The VT component has been modified to work correctly with TeamRoute
and the A1MAIL Directory Enhancement.
02-10 Network Access times are now correctly checked upon connection
to the Connect server.
02-11 The VT component now properly handles address templates that have
all fields pre-filled with information.
02-12 A timing problem that resulted in the DS Servers sometimes not
starting up correctly has been resolved.
02-13 The Connect Server now properly handles corrupt data in a message
that previously resulted in a process dump.
02-14 Additional checks have been added to the Connect Server to defend
against corrupt data being passed in.
02-15 The MUAS Server now properly handles the value in the reply
requested field.
02-16 The node check command procedure now properly checks for the
existence of a MUAS Server running on the system.
02-17 The dependency on NETBIOSSHR has been removed from the A1MAILMACSHR
image.
02-18 The MUAS Server now properly handles invalid UA content ids when
attempting to correlate reports.
02-19 The VT component now correctly handles the attempt to read or
list messages in the VMSmail submode if no folders or messages
exist in the VMSmail submode.
03-1 Resolved a problem where the TeamLinks clients were getting
disconnected.
03-2 The Connect Server properly handles a full buffer situation when
sending data to a PC over TCP/IP.
03-3 A memory leak in the Connect Server when performing various FIND
operations has been fixed.
03-4 Channels are now properly freed up when writing data to one of the
Connect Server log files.
03-5 An access violation in the Connect Server has been resolved.
03-6 Connect Server properly handles a NULL node name when CON logging is
enabled.
03-7 The TO: field is now properly displayed when listing messages in
the outbox with the TeamLinks client.
03-8 A new version of the broker, TLNK$REMOTE.EXE, V1.1-2, which is used
by TeamLinks V2.5 and later to connect via TeamLinks Remote
Connection Manager (Windows) or TeamLinks Remote Access (Macintosh).
INSTALLATION NOTES:
Install this kit with the VMSINSTAL utility by logging into the
SYSTEM account, and typing the following at the DCL prompt:
$ @SYS$UPDATE:VMSINSTAL A1MAIL_ECO3A013 [location of the saveset]
The ECO kit checks to ensure that a valid license is installed before
proceeding. If one is not found, the installation aborts.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
a1mail_eco02013.README
a1mail_eco3a013.CHKSUM
a1mail_eco3a013.CVRLET_TXT
a1mail_eco3a013.a-dcx_axpexe
a1mail_eco3a013.a-dcx_vaxexe
a1mail_eco3a013.b-dcx_axpexe
a1mail_eco3a013.b-dcx_vaxexe
a1mail_eco3a013.c-dcx_axpexe
a1mail_eco3a013.c-dcx_vaxexe
a1mail_eco3a013.d-dcx_axpexe
a1mail_eco3a013.d-dcx_vaxexe
a1mail_eco3a013.e-dcx_axpexe
a1mail_eco3a013.e-dcx_vaxexe
a1mail_eco3a013.f-dcx_axpexe
a1mail_eco3a013.f-dcx_vaxexe
a1mail_eco3a013.g-dcx_axpexe
a1mail_eco3a013.g-dcx_vaxexe
|
