NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Cluster Services 1.01 Support Pack 2 TID #: 2959684 README FOR: cs1sp2.exe NOVELL PRODUCTS and VERSIONS: NetWare Cluster Services for NW5 ABSTRACT: This Support Pack contains updates for all components contained in the NetWare Cluster Services product only. If the Support Pack was downloaded, it must be extracted at the root of the drive because it contains directory paths that could exceed the DOS limits. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- INSTALLATION INSTRUCTIONS: NetWare Cluster Services 1.01 Support Pack 2 June 15, 2001 Overview This Support Pack contains updates for all components contained in the NetWare Cluster Services product only. If the Support Pack was downloaded, it must be extracted at the root of the drive because it contains directory paths that could exceed the DOS limits. The purpose of this Support Pack is to provide a bundle of fixes that have all been tested together. These files have undergone component testing, core OS testing, and integration testing with other Novell products. For information on the latest Support Pack issues, see TID 10058746 at http://support.novell.com/search/kb_index.htm. If you experience problems downloading large files, refer to TID 2947202. To order the Support Pack CD, go to http://support.novell.com/csp/orderinfo.html. Table of Contents 1.0 Prerequisites 2.0 Support Pack Installation 2.1 Rolling Upgrades 2.2 No Mixed Clusters 2.3 Adding a New Node to an Upgraded Cluster 2.4 Installing a New Support Pack Cluster 2.5 Installing the Support Pack 3.0 Issues 3.1 Install Cluster Services Support Pack on NetWare 5.1 3.2 Documentation 3.3 Novell Client Versions 3.4 Improved Volume Management 3.5 Shared Storage Protection during Install 3.6 ConsoleOne Time Zone Error in Windows 95/98/NT/2000 3.7 No Periods in Cluster Names or Resources 3.8 Support for Failover of Legacy Server Applications 3.9 Resources Stuck in NDS Sync State 3.10 Legacy Print Captures Lost on Workstation Reboot 3.11 Cluster-enabled Applications 3.12 ManageWise 2.7 Running on a NWCS Server 3.13 DHCP Fails Over Only to Nodes with NDS Read/Write Replica 3.14 Secondary IP Addresses Needed for DHCP Resources 3.15 Upgrading NetWare 5.0 to NetWare 5.1 3.16 Cluster-Aware NSS Tools 3.17 Loading CLSTRLIB on a Server with Multiple NICs 3.18 Debugger Options Limited 3.19 CPU Hog and Real Mode No Longer Cause Data Corruption 3.20 Cluster Statistics Tool 3.21 Leaky IO Problem Fixed 3.22 White Spaces in Scripts Ignored 3.23 Pervasive Updates 3.24 Server Abend after Installation 4.0 Changes Since Last Support Pack 5.0 Legal Information 5.1 Disclaimer, Export Notice, Copyright, and Patents 5.2 Trademarks 1.0 Prerequisites This Support Pack is for use only on servers with Cluster Services v1.0.1. Confirm that this is installed on the server by loading NWCONFIG.NLM and look in Installed Products for the entry NWCS 1.0.1. If the entry is 1.0.0, then install the Cluster Services Support Pack 1. You must first install the NetWare 5.1 Support Pack 3 before installing the NetWare Cluster Services Support Pack. All nodes in the cluster must have both the NetWare 5.1 Support Pack 3 and NetWare Cluster Services Support Pack before rejoining the cluster. All cluster nodes must be upgraded to NetWare 5.1 Consolidated Support Pack 6 before rejoining the cluster or rebooting the node. 2.0 Support Pack Installation To upgrade a cluster to a new Support Pack, we recommend that you take the cluster down, upgrade all nodes with the NetWare and Cluster Services Support Packs, reboot all servers, and allow the cluster to reform. See Section 2.5, "Installing the Support Pack", for more information. 2.1 Rolling Upgrades If you want to attempt a rolling upgrade (i.e., leaving the cluster up and running services during the upgrade), instead of taking the cluster down, you must do the following: 1) Determine which of the cluster nodes will be kept active while the other nodes are being upgraded. Roughly half of the cluster should be upgraded while the other half continues to run services. When the first half has been upgraded, it will then take over the services so that the other half can be upgraded. 2) Determine which services you want to keep active during the upgrade, and migrate these resources to the nodes that will remain active. 3) Modify the Preferred Nodes list of each of the resources you want to have active and ensure that it includes nodes that are in the other half of the cluster. This will allow the resources to be restarted on the upgraded nodes later. 4) Type "Cluster Leave" on each of the nodes that are going to be upgraded first. This will take those nodes out of the cluster. The rest of the cluster will remain active. 5) Upgrade the nodes that you've taken out of the cluster with the new version of NetWare and Cluster Services Support Packs. Do not reboot after the NetWare upgrade. 6) When both Support Pack upgrades are complete, reboot each server. As the upgraded nodes reboot, they will attempt to rejoin the cluster but will be unable to. The nodes will display a message that another node has acquired the SBD lock. This is expected behavior. 7) On one of the nodes that has not yet been upgraded, type "Cluster Down" to bring down the entire remaining cluster. The upgraded nodes that have been attempting to join the cluster will now form a new cluster and will start all the resources that were running on the other cluster. 8) Upgrade the other half of the cluster. As the nodes are upgraded and rebooted, they will rejoin the cluster. 2.2 No Mixed Clusters All nodes of a cluster must be running the same version of NetWare and the same versions of the NetWare and Cluster Services Support Pack. A cluster with a mix of NetWare 5.0 and 5.1 servers is not supported. 2.3 Adding a New Node to an Upgraded Cluster If you want to add a new node to a cluster that has been upgraded to the new Support Pack, follow these steps: 1) Using your original Novell Cluster Services 1.01 CD, add the new node by using the client-side installer, the same utility you have always used to add nodes. Do not reboot this node. 2) Upgrade the newly added node to the Support Pack level running on the active cluster. Do this before you reboot the newly added node or else it will fail to join the upgraded cluster running at a different software level. 2.4 Installing a New Support Pack Cluster If you are installing an entirely new cluster that includes these Support Pack changes, you have two choices: Image a new Cluster Services CD (recommended) or Use your original NCS 1.01 CD to create a NCS 1.01 Cluster, and then upgrade all cluster nodes to the NetWare 5.1 and Cluster Services Support Packs before any of them reboot. Some of the changes to the Cluster Services Support Pack involve the install program. You will not get the benefit of these changes unless you run a regular Cluster Services install, rather than just copying files as is done when installing a Support Pack. If you want to take advantage of these changes, we recommend creating a new Cluster Services CD image by copying the new support pack NLMs files over the existing Cluster Services 1.01 CD NLMs. 2.5 Installing the Support Pack To upgrade a cluster to a new Support Pack, you should take the cluster down, upgrade all nodes with the NetWare and Cluster Services support packs, reboot all servers, and allow the cluster to reform. Complete the following steps for each server in the cluster using NWCONFIG. If you are installing from CD, start with Step 2. 1) At a workstation DOS prompt, explode the file by entering B1CS1SP2. Explode the file on the server's volume SYS: or on another server volume. This compressed file contains directory paths that could exceed the DOS limits. The file must be extracted in a root-level directory on your local drive or on a NetWare volume that accepts longer paths. 2) At the server console prompt, enter NWCONFIG. 3) Select Product Options > Install a Product Not Listed. 4) Depending on where the NetWare Support Pack files are located, complete one of the following steps: - From the local volume SYS:, press F3, and then specify the path, including the volume name (for example, SYS:\). - From a different server on the network, press F3, and then specify the full path, including the server name (for example, \VOL1:\). You will be prompted for a login name and password for the other server. 5) Press Enter. 6) Press F10 to accept the marked options and continue. If you want to be able to uninstall the Support Pack later, you must select the option to back up files. 7) Press Esc after you read the Readme. 8) If you chose not to automatically reboot earlier, press Enter to end. 9) After the files are copied, review the .NCF files for accuracy. 10) At the server console, enter RESET SERVER. This resets (warm boot) the server and completes the installation of the Support Pack. The RESTART SERVER command will not activate the new SERVER.EXE file. You can also enter DOWN and then restart the server by entering SERVER.EXE. If Auto Purge is not set on your server, you may want to manually purge the volume to free disk space. 3.0 Issues 3.1 Install Cluster Services Support Pack on NetWare 5.1 This NetWare Cluster Services Support Pack should only be installed on NetWare 5.1. 3.2 Documentation In addition to this file, the following sources give information related to the Support Pack: - For more information on the latest Support Pack issues, see TID 10058746. - Updated documentation on NetWare Cluster Services is available at www.novell.com/documentation. 3.3 Novell Client Versions The Support Pack was tested with the following versions of the Novell Client: - Novell Client for Windows 95/98 3.3 Support Pack 1 - Novell Client for Windows NT/2000 4.8 Support Pack 1 3.4 Improved Volume Management Cluster resources are better integrated with NSS volume state and reflect both manual operations applied to volumes (dismounting a mounted volume for example) and I/O failures that cause volumes to be shutdown, in the corresponding cluster resource's state. 3.5 Shared Storage Protection during Install In the past, it was possible for the NetWare install to delete all the existing partitions located on shared storage if the server was attached to shared storage during the install. The new NetWare install protects shared partitions by checking the partition for the presence of a special cluster-specific partition, and not touching any devices that have such a partition. 3.6 ConsoleOne Time Zone Error in Windows 95/98/NT/2000 You may get incorrect time/date stamps in the cluster event log due to a known bug in Windows 95/98/2000 and NT. Time stamps may be recorded in GMT instead of your local time. To correct this problem, you must set the TZ variable in your AUTOEXEC.BAT or NT user environment. Set TZ=. 3.7 No Periods in Cluster Names or Resources Do not use periods in cluster names or cluster resources. NetWare and its clients generally interpret a period as a delimiter. 3.8 Support for Failover of Legacy Server Applications If you wish to fail over a server application that accesses data on a cluster-enabled volume, you must take a step to make sure the volume remains visible to the application on failover if the application searches for its data by server name instead of IP address. To make cluster volumes visible to such legacy applications, place the virtual server name of the volume in the SYS:/ETC/HOST file of each cluster node. The syntax for this is as follows: For example: 123.2.2.1 cluster_vol_server 3.9 Resources Stuck in NDS Sync State If your cluster resources get stuck in the NDS sync state too long, you should check the replica synchronization and run DSREPAIR if necessary. To do this, go to DSREPAIR, advanced options, replica and partition operations, select "Synchronize the replica on all servers". 3.10 Legacy Print Captures Lost on Workstation Reboot You will lose your permanent print captures to legacy print queues when you reboot your client workstation. The workaround for this is to map a drive in your login script to the print queue location through NDS prior to the capture command. 3.11 Cluster-enabled Applications Though all NetWare 5 applications will run on a cluster node, not all applications are capable of being configured as a cluster application and failed over to a new node. You should check the NetWare Cluster Services support page for a list of applications that are currently configured in a way that prevents their being failed over. 3.12 ManageWise 2.7 Running on a NWCS Server The IPGROPER.NLM in ManageWise is fairly CPU intensive. It can hog the CPU longer than 8 seconds (the default where clustering will cast the ManageWise Server out of the cluster). This is resolved in the ManageWise IPGROPER.NLM dated Jan 27, 2000 version 2.11 or later. 3.13 DHCP Fails Over Only to Nodes with NDS Read/Write Replica This version of NetWare Cluster Services supports DHCP failover. The only limitation is that DHCP can only be failed over to a node that is running a read/write replica of NDS. You must configure your failover scripts for the DHCP resource to include only nodes that run NDS replicas. 3.14 Secondary IP Addresses Needed for DHCP Resources If you are running DHCP as a cluster resource and are servicing segments across a router, then a secondary IP address should be assigned to the DHCP resource. Bootpfwd on the router(s) should be set to this address. For example: #add secondary ipaddress A.B.C.D should be added to the #resource's load script, and #del secondary ipaddress A.B.C.D should be added to the #resource's unload script. 3.15 Upgrading NetWare 5.0 to NetWare 5.1 If you are running Cluster Services on NetWare 5.0 and then upgrade your servers to NetWare 5.1, the NetWare 5.1 install will remove the licenses necessary to run Cluster Services. Following are the steps you should take to upgrade from NetWare 5.0 to NetWare 5.1 with Cluster Services: 1) Bring the cluster down by typing "Cluster Down" at any cluster node. 2) Install NW5.1 on each cluster server without licenses, but supply NICI Foundation Key file (*.NFK) 3) Obtain NWCS 1.01 for NW5.1 (which contains SBLU and CUAL licenses for NW5.1) 4) Using NWAdmin, remove SBLU and CUAL licenses for NW5.0. 5) Using NWAdmin, install SBLU and CUAL licenses for NW5.1. 3.16 Cluster-Aware NSS Tools The NSS tools that perform volume operations (NSS /MENU and NWCONFIG "NSS Disk Options") were previously not cluster aware. That allowed the possibility that changes made to a volume on one cluster node would not be correctly reflected on other cluster nodes, causing volume corruption. Those tools are now cluster aware, and ensure that volume operations done on any node are correctly reflected across cluster nodes. 3.17 Loading CLSTRLIB on a Server with Multiple NICs You can now load CLSTRLIB on a server with multiple NICs. 3.18 Debugger Options Limited It is no longer possible to proceed in the kernel debugger from a cluster node unless the Developer Option is set to On. Once a cluster node enters the debugger, returning to NetWare (by typing "g" for "go") is disabled. Further, this change prevents any NetWare code from running via the kernel debugger by, for example, single stepping or tracing through an instruction sequence. It is possible to debug using other kernel debugger instructions such as memory or stack commands. It is also possible to quit ("q") the debugger to DOS, where the server may be restarted normally. 3.19 CPU Hog and Real Mode No Longer Cause Data Corruption Entering real mode or having a process hog the CPU can cause a node to look dead to other cluster nodes and results in its being cast out of the cluster. In the past, these conditions could cause data corruption if the node recovered from these conditions and wrote to a shared volume before being cast out. This possibility for corruption has been eliminated, and any node that is in a CPU hog or real mode condition for longer than the cluster timeout period (default is eight seconds) will abend itself immediately upon returning from these conditions. 3.20 Cluster Statistics Tool Follow the instructions in the Statistics Tool documentation to use the clustering statistics tool. 3.21 Leaky IO Problem Fixed In rare cases a node could access the shared storage before eating a poison pill (being cast out of the cluster by the other nodes) even though another node had taken over the shared volume. Now, the node will wait up to tolerance time (default eight seconds) after giving a poison pill to a dead node before taking over its shared volumes (assuming the appeared dead node eats the poison pill in the tolerance time). 3.22 White Spaces in Scripts Ignored Load and Unload scripts are limited to six hundred characters. The six hundred characters do not include characters following the comment character "#". Also, the white spaces in between the last character of the command and the comment character are now ignored. 3.23 Pervasive Updates You can download the latest update (Pervasive SQL 2000i Service Pack 3) for the Pervasive database at: http://www.pervasive.com/support/updates/index.tml. This update lets Pervasive be installed and run on a clustered volume. It also provides the ability to work with failover. 3.24 Server Abend after Installation You may get an abend, CPU Hog Detected, after installing this Support Pack. To resolve this problem, get the latest CE100B.LAN file (1/07/01 v3.29) from Intel's Web site (http://support.intel.com/support/network/). The latest Novell certified version of this driver can be found at http://developer.novell.com/solutions/yes/. You can also use the E100B.LAN driver to work around this problem. 4.0 Changes Since Last Support Pack For a list of the changes made since the last Support Pack, see the CS1SP2\NWCS_CHG.TXT file. 5.0 Legal Information 5.1 Disclaimer, Export Notice, Copyright, and Patents Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. This product may require export authorization from the U.S. Department of Commerce prior to exporting from the U.S. or Canada. Copyright (C) 1999-2001 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent Nos. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,594,863; 5,608,903; 5,633,931; 5,652,854; 5,671,414; 5,677,851; 5,692,129. U.S. and Foreign Patents Pending. 5.2 Trademarks Novell, NetWare, GroupWise, and ManageWise are registered trademarks of Novell, Inc. in the United States and other countries. BorderManager, ConsoleOne, NetWare Loadable Module and NLM, Novell Client, and Novell Cluster Services are trademarks of Novell, Inc. All third-party trademarks are the property of their respective owners. ISSUE: n/a Self-Extracting File Name: cs1sp2.exe Files Included Size Date Time ..\ CS1SP2.TXT (This file) ..\CS1SP2\ NWCSSP2.DEU 27464 7-13-2001 12:33:38 pm NWCSSP2.ESN 28705 7-13-2001 3:11:48 pm NWCSSP2.FRA 29211 7-13-2001 12:36:18 pm NWCSSP2.PTB 25966 7-13-2001 12:36:30 pm NWCSSP2.TXT 23787 7-11-2001 3:16:18 pm NWCS_CHG.TXT 4497 7-12-2001 3:40:48 pm SPACK.IPS 9957 4-27-2001 9:09:34 am ..\CS1SP2\JAVA_INS\ C1INSTLL.JAR 64895 11-7-2000 6:06:50 pm CONSOLE1.ZIP 19868949 12-14-2000 12:58:26 pm ..\CS1SP2\JAVA_INS\NLS\ ..\CS1SP2\JAVA_INS\NLS\1\ C1_ZH_TW.ZIP 176805 12-6-2000 3:24:08 pm ..\CS1SP2\JAVA_INS\NLS\12\ C1_PT.ZIP 176249 12-6-2000 3:24:00 pm ..\CS1SP2\JAVA_INS\NLS\13\ C1_RU.ZIP 196300 12-6-2000 3:24:04 pm ..\CS1SP2\JAVA_INS\NLS\14\ C1_ES.ZIP 177055 12-6-2000 3:23:54 pm ..\CS1SP2\JAVA_INS\NLS\16\ C1_ZH_CN.ZIP 175591 12-6-2000 3:24:06 pm ..\CS1SP2\JAVA_INS\NLS\4\ ..\CS1SP2\JAVA_INS\NLS\6\ C1_FR.ZIP 180308 12-6-2000 3:23:56 pm ..\CS1SP2\JAVA_INS\NLS\7\ C1_DE.ZIP 179152 12-6-2000 3:23:52 pm ..\CS1SP2\JAVA_INS\NLS\8\ C1_IT.ZIP 177187 12-6-2000 3:23:56 pm ..\CS1SP2\JAVA_INS\NLS\9\ C1_JA.ZIP 184584 12-6-2000 3:23:58 pm ..\CS1SP2\NI\ ..\CS1SP2\NI\TEMP\ NCSPROXY.NLM 7325 4-17-2001 2:35:34 pm ..\CS1SP2\PUBLIC\ ..\CS1SP2\PUBLIC\WIN32\ ..\CS1SP2\PUBLIC\WIN32\SNAPINS\ NCSSNAP.DLL 153600 2-8-2000 4:27:00 pm ..\CS1SP2\SP\ APPEND.NLM 965 9-29-1998 2:26:08 pm C1.TXT 481 2-8-2001 9:12:02 am C1ENV.NCF 1239 2-29-2000 2:48:30 pm ICMD.NLM 32901 8-7-2000 6:50:36 am NCS.ZIP 259411 2-21-2001 12:13:40 am SILENT.ICS 11816 4-18-2001 11:36:58 am SPACK.ZIP 12905 4-26-2000 2:59:42 pm SPBR.NLM 21550 4-7-2000 12:06:12 pm STARTUP.ICS 5665 4-19-2001 12:05:44 pm ..\CS1SP2\SP\BACKUP\ BACKOUT.IPS 1138 1-26-2001 3:02:38 pm ..\CS1SP2\SP\NLS\ ..\CS1SP2\SP\NLS\1\ ICMD.MSG 5566 4-28-2000 12:04:08 pm ..\CS1SP2\SP\NLS\12\ ICMD.MSG 7321 5-2-2000 12:50:12 pm MSGVAR.RCF 2812 3-13-2001 10:06:48 am SPACK.ILS 1809 3-13-2001 10:06:40 am SPACKA.ILS 316 2-26-2001 5:39:34 pm ..\CS1SP2\SP\NLS\13\ ICMD.MSG 7234 4-28-2000 12:04:10 pm ..\CS1SP2\SP\NLS\14\ ICMD.MSG 7603 4-28-2000 12:04:06 pm MSGVAR.RCF 2967 3-13-2001 10:06:16 am SPACK.ILS 1768 3-13-2001 10:05:54 am SPACKA.ILS 313 2-26-2001 5:40:02 pm ..\CS1SP2\SP\NLS\16\ ICMD.MSG 5479 4-28-2000 12:04:08 pm ..\CS1SP2\SP\NLS\4\ ICMD.MSG 7331 8-7-2000 6:50:06 am MSGVAR.RCF 2622 3-5-2001 10:38:08 am SPACK.ILS 1646 3-5-2001 10:41:24 am SPACKA.ILS 313 12-7-2000 2:29:54 pm ..\CS1SP2\SP\NLS\6\ ICMD.MSG 7893 4-28-2000 12:04:04 pm MSGVAR.RCF 2995 3-13-2001 10:05:30 am SPACK.ILS 1759 3-13-2001 10:05:20 am SPACKA.ILS 316 2-26-2001 5:40:26 pm ..\CS1SP2\SP\NLS\7\ ICMD.MSG 7619 4-28-2000 12:04:06 pm MSGVAR.RCF 3193 3-13-2001 10:04:56 am SPACK.ILS 1734 3-13-2001 10:04:26 am SPACKA.ILS 317 2-26-2001 5:40:52 pm ..\CS1SP2\SP\NLS\8\ ICMD.MSG 7711 4-28-2000 12:04:06 pm ..\CS1SP2\SP\NLS\9\ ICMD.MSG 6552 4-28-2000 12:04:08 pm ..\CS1SP2\SYSTEM\ CLSTRLIB.NLM 119442 6-8-2001 4:51:48 pm CMA.NLM 164020 6-8-2001 2:45:12 pm CMON.NLM 14784 4-19-2001 4:59:16 pm CRM.NLM 161491 6-8-2001 5:15:36 pm CVSBIND.NLM 3442 4-19-2001 4:59:34 pm DELAY.NLM 1738 4-19-2001 4:59:38 pm GIPC.NLM 210596 4-19-2001 4:59:42 pm SBD.NLM 23661 6-8-2001 2:45:18 pm SBDLIB.NLM 8383 4-19-2001 4:59:54 pm TRUSTMIG.NLM 79633 5-8-2001 1:00:14 pm VLL.NLM 33594 4-19-2001 5:00:06 pm ..\CS1SP2\SYSTEM\NLS\ ..\CS1SP2\SYSTEM\NLS\12\ CLSTRLIB.MSG 6574 1-27-2000 1:46:40 pm CMA.MSG 2459 1-27-2000 1:51:50 pm CMON.MSG 1397 1-27-2000 1:57:18 pm CRM.MSG 11924 1-27-2000 2:03:02 pm CRMMON.MSG 2679 1-27-2000 2:12:10 pm GIPC.MSG 36460 1-27-2000 2:20:06 pm SBD.MSG 5434 1-27-2000 2:44:30 pm SBDLIB.MSG 1200 1-27-2000 2:52:00 pm TRUSTMIG.MSG 1822 1-27-2000 2:58:12 pm TRUSTOOL.MSG 1293 1-27-2000 3:40:26 pm VLL.MSG 5304 1-27-2000 3:55:26 pm ..\CS1SP2\SYSTEM\NLS\14\ CLSTRLIB.MSG 6706 1-27-2000 1:47:12 pm CMA.MSG 2470 1-27-2000 1:52:48 pm CMON.MSG 1439 1-27-2000 1:57:48 pm CRM.MSG 11916 1-27-2000 2:03:32 pm CRMMON.MSG 2679 1-27-2000 2:12:38 pm GIPC.MSG 36498 1-27-2000 2:21:50 pm SBD.MSG 5692 1-27-2000 2:45:04 pm SBDLIB.MSG 1257 1-27-2000 2:52:32 pm TRUSTMIG.MSG 1844 1-27-2000 2:58:44 pm TRUSTOOL.MSG 1314 1-27-2000 3:41:56 pm VLL.MSG 5588 1-27-2000 3:57:22 pm ..\CS1SP2\SYSTEM\NLS\4\ CLSTRLIB.MSG 6953 4-18-2001 5:07:18 pm CMA.MSG 2421 4-19-2001 9:42:52 am CMON.MSG 1338 4-18-2001 5:07:22 pm CRES.MSG 651 4-18-2001 5:07:24 pm CRM.MSG 12195 5-8-2001 12:51:30 pm CRMMON.MSG 2679 4-19-2001 10:22:02 am DELAY.MSG 174 4-18-2001 5:07:28 pm GIPC.MSG 36633 4-18-2001 5:07:32 pm RWAIT.MSG 890 4-18-2001 5:07:34 pm SBD.MSG 6029 4-18-2001 5:07:36 pm SBDLIB.MSG 1138 4-18-2001 5:07:38 pm TRUSTMIG.MSG 1891 5-8-2001 12:59:22 pm TRUSTOOL.MSG 1390 4-19-2001 10:22:16 am VLL.MSG 5314 4-18-2001 5:07:40 pm VLLTEST.MSG 3424 4-18-2001 5:07:40 pm ..\CS1SP2\SYSTEM\NLS\6\ CLSTRLIB.MSG 5316 1-27-2000 1:46:52 pm CMA.MSG 2551 1-27-2000 1:52:04 pm CMON.MSG 1551 1-27-2000 1:57:26 pm CRM.MSG 11961 1-27-2000 2:03:14 pm CRMMON.MSG 2679 1-27-2000 2:12:22 pm GIPC.MSG 36430 1-27-2000 2:20:30 pm SBD.MSG 5884 1-27-2000 2:44:38 pm SBDLIB.MSG 1245 1-27-2000 2:52:14 pm TRUSTMIG.MSG 1871 1-27-2000 2:58:24 pm TRUSTOOL.MSG 1328 1-27-2000 3:40:46 pm VLL.MSG 5494 1-27-2000 3:55:56 pm ..\CS1SP2\SYSTEM\NLS\7\ CLSTRLIB.MSG 6623 1-27-2000 1:47:04 pm CMA.MSG 2544 1-27-2000 1:52:30 pm CMON.MSG 1532 1-27-2000 1:57:40 pm CRM.MSG 11976 1-27-2000 2:03:22 pm CRMMON.MSG 2679 1-27-2000 2:12:32 pm GIPC.MSG 36489 1-27-2000 2:21:12 pm SBD.MSG 5941 1-27-2000 2:44:50 pm SBDLIB.MSG 1342 1-27-2000 2:52:24 pm TRUSTMIG.MSG 1923 1-27-2000 2:58:34 pm TRUSTOOL.MSG 1340 1-27-2000 3:41:24 pm VLL.MSG 5727 1-27-2000 3:56:48 pm ..\CS1SP2\SYSTEM\SCHEMA\ ORION2.SCH 10823 8-15-2000 10:54:56 am ..\CS1SP2\SYSTEM\TSTTOOLS\ CRES.NLM 4343 4-19-2001 4:59:20 pm CRMMON.NLM 57855 4-19-2001 4:59:30 pm RWAIT.NLM 4958 4-19-2001 4:59:46 pm TRUSTOOL.NLM 13571 5-21-2001 4:00:00 pm VLLTEST.NLM 14157 4-19-2001 5:00:10 pm ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------