|
|
 |
HP Services Software Patches - a1fcs_eco01031
|
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: ALL-IN-1 Office Server Options for OpenVMS AXP and
OpenVMS VAX, V3.1
COMPONENT: File Cabinet Server
OP/SYS: OpenVMS Alpha V6.1 or later
OpenVMS VAX V5.5-2 or later
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: A1FCS_ECO01031
ECO Kits Superseded by This ECO Kit: None
NOTE: This ECO kit obsoletes the patch kits A1_FIX018031.BCK,
A1_FIX022031.BCK, A1_FIX025031.BCK, A1_FIX032031.A,
and A1_FIX035031.A.
ECO Kit Approximate Size: A1FCS_ECO01031.A - 10,800 Blocks
System Reboot Necessary: No
ECO KIT SUMMARY:
An ECO kit exists for ALL-IN-1 Office Server Options (File Server
Component) for OpenVMS AXP and OpenVMS VAX Version 3.1 on OpenVMS Alpha
V6.1 or later and OpenVMS VAX V5.5-2 or later.
The A1FCS_ECO01031 Release Notes contain a complete explanation of this
release. Below is a brief description:
o Improved FCS Error Trapping
The FCS error trapping mechanisms have been improved, particularly
around selected system service calls, which under certain conditions
caused the FCS process to stop processing client requests.
o Accessing the Distributed Sharing Option
When the DSO license is not installed on a system, any remote request
to that server fails (intentionally) with an information message in
the log file. Extra information is now added to such messages with
details of the user and originating node of the remote request.
o FCS Error diagnostics
Error and information messages inserted into FCS logfiles were
insufficiently descriptive. These have now been improved to
facilitate diagnostics.
o FCS shutdown leaves documents locked
Some exception conditions (alerts) cause documents to remain locked
after the FCS has finished handling them. Such documents could not
then be accessed until the FCS was restarted.
o MSG directory creation
When creating drawers from Teamlinks the File Cabinet Server doesn't
create a [.MSG] directory if the drawer isn't a Mail drawer.
Documents were filed in the top level directory and were unreadable
thereafter.
o FCS CPU loop
The File Cabinet Server sometimes enters a tight CPU loop when
accessing its internal cache of Drawer information. The FCS
stops services TeamLinks and IOS requests at this point.
o File Cabinet Server Connection hangs
To access an object in a remote file cabinet, the local File Cabinet
Server must connect to the remote FCS. While the local FCS is
establishing this connection, the requesting client cannot continue
with any work.
To avoid an indefinite period of inactivity resulting from a failure
to connect, a limit has been set to the time that a local File
Cabinet Server can take to establish a connection to a remote server.
If a connection cannot be established within this time, the attempt
is abandoned, and the client can continue with other work.
o Brokering between remote FCS processes
The FCS sometimes enters a CPU loop when performing a remote
operation if the remote FCS process encounters an unexpected failure
(eg internal access violation). The FCS stops services TeamLinks and
IOS requests at this point.
o Refiling documents with Attachments across Drawers
Occasionally when refiling documents with attachments across drawers,
the FCS 'thread' performing the refile operation on behalf of the
user will experience an Access Violation due to internal data
corruption.
o Creating RESERVATIONS.DAT and FILECAB.DAT under VMS V7.0
When running on OpenVMS V7.0 the server fails when creating
RESERVATIONS.DAT or FILECAB.DAT due to the call to lock the mutex
passing a parameter incorrectly.
o Reverse logic of OAFC$EXCLUSIVE_LOCK_OFF logical.
TLC V2.5 introduced the OAFC$EXCLUSIVE_LOCK_OFF logical to allow
exclusive locking to be turned off. This behaviour is now default.
In the unlikely event of requiring the original behaviour to be
restored to use exclusive locking, define the logical
OAFC$EXCLUSIVE_LOCK_OFF as follows:
$ DEFINE/SYSTEM OAFC$EXCLUSIVE_LOCK_OFF "N"
You will need to restart the File Cabinet Server for this change to
become effective.
o Connect/Disconnect timing problems.
The server will sometimes terminate or report fatal problems when the
server attempts to disconnect sessions that no longer exist.
o Document remains locked after attaching it to a message.
When sending a mail with an attachment from a shared drawer using
TeamLinks, the File Cabinet Server locks the DAF.DAT of the
attachment and fails to release it after the operation is complete.
This causes document locking problems.
o Server problems due to low resources.
This patch introduces a resource monitor to watch resource utilization
levels, and issue warnings to the log file when they reach set
boundaries.
o Distribution Lists created from TeamLinks cannot be used from VT
When a distribution list is created from TeamLinks you cannot use
this distribution list from ALL-IN-1. This has only been reported
against Brazilian version of ALL-IN-1 V3.0A, but will also occur with
other languages added for V3.0A. e.g. Hungarian, Polish, Russian,
Slovensky and Turkish for V3.0A and V3.1.
o Problems due to Server-Client Disconnects
When a client session connection is broken unintentionally (e.g. by
CTRL-Y, switching off a PC, or network breaks) during critical
processing the server may report an Access Violation and stop or
hang.
INSTALLATION NOTES:
Before you install patch A1FCS_ECO01031, you must shut down ALL-IN-1.
Use the Shutdown ALL-IN-1 (SDA) option on the ALL-IN-1 Administration
menu (ADM) of the Management subsystem. This will automatically shut
down your sender and fetcher processes and all servers.
See the ALL-IN-1 Management Guide for more details. TeamLinks users
will be temporarily unable to access the ALL-IN-1 file cabinet.
There are several stages to installing an ALL-IN-1 IOS V3.1 patch
kit, which vary according to the configuration of the target system
and the contents of each patch kit.
There will always be a primary installation - typically supplying
revised object modules (.OBJs), revised script files (.SCPs) or
revised named data for ALL-IN-1 forms (.FRMs).
This patch kit supplies revised image files and therefore you will
need to perform a primary installation AND a second architecture
installation (if you have a mixed architecture VMScluster).
The installation procedure will automatically relink the required
OA$FC$SERVER.EXE image and move this to its target directory.
To install this patch, log into the SYSTEM account and use the
command procedure SYS$UPDATE:VMSINSTAL.COM as follows:
$ SET DEFAULT SYS$UPDATE
$ @VMSINSTAL A1FCS_ECO01031 'device'
where 'device' is the name of the device on which the distribution
medium will be mounted or the device:directory where you have already
copied the kit to.
When the installation has completed successfully repeat the above
procedure on your second architecture system (if you run ALL-IN-1 on
a mixed architecture VMScluster).
Once you have installed A1FCS_ECO01031, do the following:
o Restart ALL-IN-1 by executing the following command
$ @SYS$STARTUP:A1V31START
If you run ALL-IN-1 on an Open VMScluster system, execute the
startup command procedure on every node of your VMScluster
where ALL-IN-1 is used.
o Reapply customizations if required.
|
Files on this server are as follows:
|
»a1fcs_eco01031.README
»a1fcs_eco01031.CHKSUM
»a1fcs_eco01031.CVRLET_TXT
»a1fcs_eco01031.a-dcx_axpexe
»a1fcs_eco01031.a-dcx_vaxexe
|
