KIT NAME: A1FCS_ECO01031 --------- OLD PRODUCT: ALL-IN-1 Office Server Options for OpenVMS AXP ------------ and OpenVMS VAX V3.1 NEW PRODUCT: ALL-IN-1 Office Server Options for OpenVMS AXP ------------ and OpenVMS VAX V3.1 APPRX BLK SIZE: 10,800 blocks --------------- DIGITAL Cover Letter for ALL-IN-1 Office Server Options for OpenVMS AXP and OpenVMS VAX V3.1 ECO Kit A1FCS_ECO01031.A. ECO Kit A1FCS_ECO01031 Description --------------------------------- This ECO kit contains a selection of code-level fixes for the File Cabinet Server component of ALL-IN-1 Version 3.1. If a patched system is later upgraded to TLC V2.5, the fixes supplied by patch A1FCS_ECO01031 will be lost. Under these circumstances this patch kit should be reapplied after the upgrade. The A1FCS_ECO01031 Release Notes contain a complete explanation of this release. Below is a brief description: o Problem 1 - 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 Problem 2 - Accessing the Distributed Sharing Option When the DSO licence 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 Problem 3 - FCS Error diagnostics Error and information messages inserted into FCS logfiles were insuffiently descriptive. These have now been improved to facilitate diagnostics. o Problem 4 - 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 Problem 5 - 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 Problem 6 - 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 Problem 7 - File Cabinet Server Connnection 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. This connection timeout defaults to 60 seconds. To change the length of this period, use the logical OAFC$CONNECT_TIMEOUT, as follows: 1. Stop the File Cabinet Server. 2. Define the logical name OAFC$CONNECT_TIMEOUT. For its value, specify the length, in seconds, of the timeout period you want to use. For example, to set the connection timeout period to 90 seconds, define the logical name as follows: DEFINE/SYSTEM OAFC$CONNECT_TIMEOUT 90 3. Restart the File Cabinet Server. o Problem 8 - 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 Problem 9 - 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 Problem 10 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 Problem 11 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 Problem 12 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 Problem 13 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 Problem 14 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. The monitor runs periodically, once a minute by default. To change this length of this period, use the logical OAFC$QUOTA_INTERVAL. For its value, specify the length, in seconds, of the monitor period you want to use. For example, to set the monitor period to 90 seconds, define the logical name as follows: $ DEFINE/SYSTEM/EXECUTIVE OAFC$QUOTA_INTERVAL "90" Define this value to "0" to suppress the quota monitoring tool altogether. The level of remaining resources required before messages are logged is 5% by default, but this can be changed using the logical OAFC$QUOTA_WARNING_LEVEL. Values between 1 and 99 (inclusive) are allowed. Out of range values will result in the default being applied. After the message has been logged 5 times the logging is turned off and a reply is issued to the ALL-IN-1 manager to warn that the server is low on resources and that the log file should be checked. This reply is issued once in every 10 times that the monitor runs. For example, to set the warning level to 10% , define the logical name as follows: $ DEFINE/SYSTEM/EXECUTIVE OAFC$QUOTA_WARNING_LEVEL "10" You will need to restart the File Cabinet Server for this change to become effective. o Problem 15 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 Problem 16 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 Overview --------------------- 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). 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). Copyright Digital Equipment Corporation 1996. All Rights reserved. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. This ECO has not been through an exhaustive field test process. Due to the experimental stage of this ECO/workaround, Digital makes no representations regarding its use or performance. The customer shall have the sole responsibility for adequate protection and back-up data used in conjunction with this ECO/workaround.