home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 30 fixes_v
/
30-fixes_v.zip
/
ip20665.lna
/
README.DLN
< prev
Wrap
Text File
|
1996-03-16
|
33KB
|
736 lines
===================================================
Adstar(*) Distributed Storage Manager:
Lotus Notes(**) Backup Agent for OS/2(*)
Licensed Materials - Property of IBM
(C) Copyright IBM Corporation 1990, 1996. All rights reserved.
Refer to Copyright Instructions Form Number G120-2083
Welcome to the ADSM Lotus Notes(**) Backup Agent.
This README.DLN file contains information you need for installing
the ADSM Lotus Notes(**) Backup Agent as well as information that
was not available for our printed publications.
ADSM Version 2 Release 1 Level 0.3
PTF IP20665
====================================================
This README.DLN file is divided into the following categories:
o Before You Install the ADSM Lotus Notes(**) Backup Agent
o Getting Help
o Installing the ADSM Lotus Notes(**) Backup Agent
o Late-Breaking News
- Limitations
- Document Updates
- General Information
- Known Problems
- Fix Information
o Trademarks
====================================================
====================================================
Before You Install the ADSM Lotus Notes(**) Backup Agent
====================================================
Software Requirements
---------------------
- OS/2(*) 2.0 or later
- Lotus Notes(**) 3.x client or Lotus Notes(**) 3.x server
- This package requires that the ADSM API for OS/2(*) be
be installed. This API is available with ADSM OS/2(*) Client V2.
NOTE: While this agent will run with version 1 ADSM API, use of
the latest available ADSM API version 2 package is highly recommended.
If a version 1 ADSM API library is used, it should be the latest
version 1 library available.
- The agent can run with either a version 1 or a version 2
ADSM server.
Hardware Requirements
----------------------
- Any appropriately configured Intel(**) 80386 or higher
hardware platform with at least 1.2 MB of disk storage
and 12 MB of memory. Recommend Intel(**) 80486 or
higher.
Note:
----
- For futher information on system requirements, please refer to
ADSM Installing the Clients, version 2 (SH26-4049-00).
====================================================
Getting Help
====================================================
To receive service and technical support for ADSM:
-----------------------------------------------
o Contact your ADSM administrator. This should be your first
step when having problems with ADSM.
o Your ADSM administrator will know how to contact IBM
for Technical Support on your behalf.
o For the latest information about ADSM, visit the ADSM home page on
the World Wide Web. The URL is:
http://www.storage.ibm.com/storage/software/adsm/adsmhome.htm
To participate in user discussions of ADSM:
o Subscribe to IBM's officially supported ADSM forum on CompuServe(**).
This is located in the IBM Storage Systems Forum (GO IBMSTORAGE ADSM)
o Subscribe to an Internet listserv forum for ADSM
This is not officially supported by IBM, but IBM support people
do participate in the discussions, along with other ADSM users.
You can subscribe by sending a note to listserv@vm.marist.edu
that contains:
SUBSCRIBE ADSM-L your_name
in the messages body, where your_name is your first and last name.
IBM also supports an anonymous FTP server where you can find
PTF maintenance and other ADSM-related materials. Three other
anonymous servers are unofficially maintained by non-IBM volunteers.
These servers are:
index.storsys.ibm.com (primary - California, IBM)
ftp.rx.uni-karlsruhe.de (mirror - Germany)
ftp.wu-wien.ac.at (mirror - Austria)
ftp.cac.psu.edu (mirror - Pennsylvania)
====================================================
Installing the ADSM Lotus Notes(**) Backup Agent
====================================================
1)Installation information can be found in the manual
"ADSM: Installing the Clients, Version 2 (SH26-4049-00)".
The major points, however, are given below:
a) The ADSM API should already have been successfully
installed on your machine. The API is available with the
ADSM OS/2(*) Client, version 2.
b) To begin installation of the agent insert the installation
diskette into the a: drive and enter
a:\install
c) The installation program asks you for two directories.
The first is the directory in which the files of the agent
will reside. The second is the directory in which the
Lotus Notes(**) notes.ini file ALREADY resides. It is extremely
important to specify the correct path for the notes.ini
directory. Errors may occur if this directory is not specified
correctly.
Allowing the installation program to update the
config.sys file automatically, also enables it to update
the notes.ini file automatically. If automatic update is not
chosen, then you will need to update both the notes.ini file
and the config.sys file manually.
d) The update to the config.sys file is just a matter of including
the directory in which the agent resides in the PATH
LIBPATH, and HELP.
The update to the notes.ini file is, essentially, to add the following
line to that file:
AddInMenus=<pathname of the dsmnotes.dll file>
An example would be:
AddInMenus=c:\dsmnotes\dsmnotes.dll
The dsmnotes.dll file is part of the agent.
e) A list of the files belonging to the agent is as follows:
File Name Description
dsmnotes.exe executable for dsmnotes command
dsmnotes.dll Agent dynamic link library
dsmnoted.dll Agent resources
dsmln.hlp Agent help file
optionsl.doc Summary of applicable ADSM options
readme.dln This file
2) The ADSM Notes(**) agent should have its own dsm.opt file. This file is separate
from the dsm.opt file for the ADSM Backup/Archive client.
3) It is likely that an ADSM Client and an ADSM Lotus Notes(**) agent will
reside on the same machine. In this situation, a separate node
name should be given to the ADSM Lotus Notes(**) agent.
Installing the ADSM Lotus Notes(**) Backup Agent on OS/2(*) using CID
___________________________________________________________
CID is an OS/2(*) based set of components that allows you to automate
the software installation. An administrator who wants to let
users install ADSM on their local machines through a LAN,
instead of diskettes, can put all of the installation files into a
single directory on a remotely attached disk or file server and
make the necessary changes to the response and command files.
Users can then link their workstations to theat disk or file server
and perform the installation by executing the CIDINSTL command
file.
Two files (CIDINSTL.CMD and ADSMLRESP.DAT) are part of the
installation package and can be edited to fit individual requirements.
To prepare for the CID installation, the administrator of the
file server must do the following:
1. Copy the ADSM Lotus Notes(**) Backup Agent diskette to the
file server. Use the COPY or XCOPY command.
2. Edit the CIDINSTL.CMD command file to:
- Change the InstallFilesDirectory variable so that it points
to the directory on the file server that contains the ADSM Agent
files.
- Change the ErrorLog variable to the path and file name you
want to use for the error log file.
3. If necessary, edit the ADSMLRESP.DAT response file (which is
used in conjunction with the CIDINSTL.CMD to change the following:
- FILE - The directory in which to install the ADSM Agent files.
- WORK - The directory in which to install the DLL files
- COMP - The components you want installed
- CFGUPDATE - Whether you want the CONFIG.SYS file updated
- DELETEBACKUP - Whether you want to delete a backup copy
of the agent (if it has been previously installed)
- OVERWRITE - Whether you want to overwrite existing files
- SAVEBACKUP - WHether you want to save a backup copy of the
client (if it has been previously installed)
The OS/2(*) user can now attach to the remote disk or file server and
start CIDINST.CMD to install the ADSM Notes(**) Backup Agent.
This procedure assumes that the CID environment is already set up.
To start CIDINSTL.CMD, either change your working directory to its
location on the file server or add the location to the beginning of
the PATH statement:
SET PATH=X:\dsmlinst;%PATH%
====================================================
"Late-Breaking" News
====================================================
New features in level 0.3 are:
1) Wildcard restore
2) "Verbose" option for the command line
3) New log.dsm messages
Wildcard restore
----------------
The command line "dsmnotes restore" function
now accepts a wildcard when merging data into an
existing database file. The intent of this support is to address
the situation where multiple Notes(**) database files have been restored
through the ADSM backup/archive client, and there is a desire to
restore incremental backup copies of Notes(**) documents on top of those
files. The rules for a wildcard on this restore command are the same
as those for a wildcare on a "dsmnotes incr" command. A lone asterisk
indicates that all database files in the Notes(**) data directory will be
processed. Subdirectories are included in the processing only with the
"-subdir=yes" option. A directory path appended with an asterisk indicates
that all the databases in that directory will be processed.
The following is an example of a command that restores all the
incrementally backed up notes to all the databases in the Notes(**)
data directory. The restore will include every database in that directory,
regardless of whether or not the file was restored from the ADSM
backup/archive client, so care should be taken to ensure that a
database is not inadvertantly overwritten.
dsmnotes restore -merge=y -fromdate=01/28/96 -todate=02/03/96 *
The following is an example of a command that restores all the
incrementally backed up notes to all the database in the current
directory.
dsmnotes restore -merge=y -fromdate=01/28/96 -todate=02/03/96 .\*
The following is an example of a command that restores all the
incrementally backed up notes to the mail subdirectory in the Notes(**)
data directory. It is assumed that the Notes(**) data directory is d:\notes\data.
dsmnotes restore -merge=y -fromdate=01/28/96 -todate=02/03/96
d:\notes\data\mail\*
"Verbose" Option
----------------
A new DSMNOTES option has been added to the notes.ini file the
keyword is DSMNOTES_STATS. The choices of settings are:
DSMNOTES_STATS=verbose
or
DSMNOTES_STATS=quiet
The default is "quiet."
If DSMNOTES_STATS=verbose is specified in the notes.ini file,
then all the "dsmnotes" command line functions will send messages
to the screen, indicating the number of documents that have been
transferred between the workstation and the ADSM server. The default
is for no status to be shown.
Two types of indicators may appear on the screen: (1) One or more
dots ('.') may appear on the screen to indicate processing is continuing.
Depending on the environment, there may be delays even between dots.
For example, searches of very large Notes(**) databases for deleted documents
can result in apparent delays between feedback to the user. There may
also be delays when waiting for offline media to be mounted.
(2) Messages will be sent to the screen to indicate document transfer.
These messages may also be subject to delay due to offline media mount
waits.
It should be noted that the display of status messages will impact
the performance of both an incremental backup and a restore, so if the
status messages are not required, there is an advantage to turning them
off.
New log.dsm Messages
--------------------
In conjunction with the new status option, there are new log messages
that are writtein to the log.dsm file. Regardless of whether or not
"DSMNOTES_STATS=verbose" is specified, The following new information
will be written to the log.dsm file for each incremental backup:
For incremental backup of a single database:
Summary:
Database: d:\notes\data\test\abc.nsf
Documents backed up: 100, documents deleted: 1
Total number of bytes sent: 60873
dsmnotes incr OK
For incremental backup of a multiple database (i.e. using a wildcard):
Summary:
Database: d\notes\data\test\abc.nsf
Documents backed up: 100, documents deleted: 1
Database: d\notes\data\test\def.nsf
Documents backed up: 500, documents deleted: 1
Total number of documents backed up: 600
Total number of documents deleted: 2
Total number of bytes sent: 1256.1 KB
dsmnotes incr OK
For restoring notes to a single database:
Summary:
Database: d:\notes\data\test\abc.nsf
Documents restored: 28, overwritten: 0, deletion stubs overwritten: 0
(dsmnotes restore OK)
For restoring notes to multiple databases (i.e. using a wildcard):
Summary:
Database: d:\notes\data\test\abc.nsf
Documents restored: 28, overwritten: 0, deletion stubs overwritten: 0
Database: d:\notes\data\test\xyz.nsf
Documents restored: 78, overwritten: 0, deletion stubs overwritten: 0
(dsmnotes restore OK)
NOTE: There is currently no provision to trim the log.dsm file automatically.
The file should be monitored and trimmed, deleted, or archived regularly
to control growth of the file.
For both the log.dsm messages and for any status messages from
the ADSM Notes(**) Agent, a "document" can be considered any object from
a Notes(**) database that has either data or design information associated
with it. It is this data or design information that will be backed up
in a backup storage pool on the ADSM server.
Changed Message
---------------
ANS0934W DSMNOTES_AUTO_PW set in notes.ini but no password files
Explanation: The notes.ini file contains the environment variable and
setting "DSMNOTES_AUTO_PW=on", but no dsmnotes.pwd file was found.
The first time this variable is set, the ADSM password must be specified
once to establish the file that will contain the automatically maintained
password. This specification can occur either through the "-adsmpw"
option on the command line or through setting the password via the
ADSM password dialog box.
System Action: Since this message is only a warning, the Notes(**) Agent
will continue to process. If the ADSM server requires a password, then
processing will ultimately be stopped because no password was provided.
If the ADSM server does not require a password, then processing will
continue.
User Response: If the password needs to be set initially for the
password handler, then use either the password dialog box on the GUI
interface or use the -adsmpw option on the dsmnotes command. If the
automatic password handler is not needed, then remove the DSMNOTES_AUTO_PW
entry from the notes.ini file or set DSMNOTES_AUTO_PW to "off".
The above messages replaces message "ANS0934E ADSM password needed."
====================================================
Limitations:
====================================================
1) The automatic password handler for this agent is valid for
only a single ADSM server.
Performance Notes:
------------------
1) Backing up or restoring a Notes(**) database on a notes level is
considerably slower than processing a database on a file level.
Incremental back up will work best for databases that have
a small percentage of changing notes over a period of time.
2) Long merges or rebuilds can tie up a screen, if they are invoked from
the Lotus Notes(**) Workspace. For such actions that are likely to take
a long time, it is preferable to invoke the action from the command line.
====================================================
Documentation Updates:
====================================================
1) The ADSM Lotus Notes(**) Backup Agent does not offer Open Registration
of an ADSM node name. The ADSM administrator should register a unique
node name for the agent.
2) Error and informational messages on agent functions executed either through
the dsmnotes command or through the Notes(**) workspace can be divided into
three catgories: (1) Messages from the ADSM Lotus Notes(**) agent, (2) Messages
from Lotus Notes(**), and (3) message from ADSM. Messages from the ADSM
Lotus Notes(**) agent display a message number that can be referenced in
the ADSM Messages guide. Messages from Lotus Notes(**) are prefixed with
"Notes: ". These messages can be referenced in Lotus online help or other
references that come with Lotus Notes(**). Messages from either ADSM or the
agent have message numbers that can be referenced in the ADSM Messages
manual.
3) The option "-updateall=y/n" can be specified only if
the "-merge=y" option is also specified. If the user is merging data
into an existing database, then he can specify the "-updateall=y"
option to ensure that all the notes in the database are "touched"
to ensure that they have the current date/time as their modification
date/time. The effect is as if someone has "cut and pasted" all
the notes back into the database. An example of a dsmnotes
incremental backup command that uses this option is as follows:
dsmnotes restore -adsmpw=pw -merge=y -updateall=y -fromdate=07/01/95
-todate=07/15/95 mktg1.nsf
In this example, it is assumed that the database file mktg1.nsf was restored
through the ADSM client, and the dsmnotes command is being used to
restore more recent backup copies of notes on top of that file. Since
processing all the notes in a database can be very costly, this option should
be used only when a restored database truly needs to appear as a
recently created database.
4) On a "dsmnotes incr" command, an asterisk can be specified for the
pathname of the database file to indicate that all database files in
the Notes(**) data directory are to be backed up incrementally. An example
of the syntax is:
dsmnotes incr -adsmpw=pw *
In addition, the -subdir=y option can be used to indicate that subdirectories
should be processed as well. Some care should be taken in processing
multiple databases, however, because of performance implications.
5) Use of the Include-Exclude list in the dsm.opt file is different from that
for the ADSM Backup/Archive Client. Notes(**) database files can be excluded
from an incremental backup with the following format:
EXCLUDE ?:\notes\mydata\abc.nsf\*
If the database to be excluded is in the Notes(**) data directory, then only the
database name is specified. For example,
EXCLUDE ?:\abc.nsf\*
If the database to be excluded is in a subdirectory of the Notes(**) data directory,
then only the subdirectory name and the database name is specified. For example,
for database c:\notes\data\example\abc.nsf, where the Notes(**) data directory is
c:\notes\data, the statement to exclude this database is
EXCLUDE ?:\example\abc.nsf\*
or
EXCLUDE ?:\...\example\abc.nsf\*
The INCLUDE option, however, can be used only to include or assign managment
classes to all Notes(**) databases affected by the incremental backup. For
example,
INCLUDE ?:* mgmt1
causes all the Notes(**) databases that are incrementally backed up to be assigned
the management class "mgmt1." Individual databases cannot be assigned different
management classes during a single incremental backup session.
Once incremental backup of a Notes(**) database begins, it is important not
to change the management class on any further incremental backups of that same
database. The reason is that the management class is assigned to each note as
it is backed up. if management classes with different "retain" values are assigned
to notes belonging to the same database, then rebuilding of an entire database
may not be possible.
In the include/exclude statement for the Notes(**) agent, the following should be
noted:
- There is no drive letter as with files in a filesystem, so
the drive letter in the include/exclude statement should always be "?".
- Use of an include statement applies to all the data in a backup session,
as noted above.
- The include/exclude statements must include a wildcard character ('*')
to imply that the statement applies to all notes in the specified database.
6) The "days" option on both the dsmnotes command and the
Notes(**) workspace interface indicates periods of time back from
the current date/time. For example, "-days=1" means the past
24 hours. Thus, "-days=2" means the past 48 hours or, roughly,
the past two days. Hence, the command "dsmnotes restdel -days=1 .\abc.nsf"
means restore all the notes in the database abc.nsf in my current directory
that have been deleted within the past 24 hours.
Rebuilding databases with unsorted views
_______________________________________
It is possible that an unsorted view in a rebuilt database will show
documents in a different order from what would be seen in the original
database. A sorted view will not be affected.
If an ADSM Backup/Archive Client is also Installed on the Workstation
_______________________________________________________________
There is no interoperability between the ADSM Notes(**) agent and the ADSM
backup/archive client. Hence, the agent is not aware of actions done
by the backup/archive client and vice versa.
Even so, the user should give a nodename to his ADSM Notes(**) agent that is
different from that for the ADSM client that resides on the same machine.
On the other hand, it is desirable to have both the ADSM Notes(**) agent
and the ADSM client running on one machine (each having a unique nodename
in the appropriate dsm.opt file). The reason is that each provides capabilities
that the other does not. The ADSM client is capable of backing up/restoring
or archiving/retrieving an entire Notes(**) database. The ADSM Notes(**) agent is
capable of backing up and restoring smaller pieces of data (notes). Actually,
without strict control of the environment, it is possible that the agent will not
be able to restore certain versions of an entire Notes(**) database. At times,
either the ADSM backup/archive client or the ADSM Notes(**) agent will be a more
appropriate solution. In addition, the ADSM backup/archive client can back up
the files on the machine, that are not Notes(**) database files.
Methods can be used to take advantage of both the ADSM backup/archive
client and the ADSM Notes(**) agent for a Notes(**) database. The alternative to
relying only on backup copies of notes to back up an entier database is to use
both the client and agent together. Backing up Notes(**) database files with the
ADSM backup/archive client periodically and then backing up the databases
incrementally more frequently is a method to avoid restoring data that has
been spread out among different media over a long period of time. This method
also helps to avoid "rolled off" data because the data backed up through the
ADSM client always provides a "latest copy possible" copy of the database.
An example of this method would be to back up a database through the
ADSM client once a month and then incrementally back up the database once
a day.
What Kind of Databases to Back Up Incrementally
Maximum benefit from incrementally backing up a Notes(**) database is likely to
occur with database in which only a small percentage of notes change over
time. A database in which a large percentage of notes change is a better candidate
for the ADSM client, which can back up an restore entire files more efficiently.
Incremental backup only applies to Lotus Notes(**) .NSF databases.
====================================================
Information for both ADSM Administrators and Notes(**) Users
====================================================
Filespaces
While the ADSM backup/archive client backs up files in filespaces
to the ADSM server, the ADSM Notes(**) agent backs up notes in database to the
ADSM server. On the ADSM server, a list of filespaces for the Notes(**) Agent
nodename will show a list of the Notes(**) database that have notes backed up on
that ADSM server.
Management Classes
Since each note is backed up as an individual object, it is important that
a single management class be assigned to all the notes in a given Notes(**)
database. If all notes in a database are not managed the same way, then
rebuilding an entire database from backup copies of single notes cannot
be guaranteed.
For optimal control in managing backup copies of notes, a separate
ADSM domain should be established for the nodes running the ADSM Notes(**) agent.
Performance Considerations
Backup of an entire Notes(**) database through incremental backup will be
significantly slower than backup of the database file through an ADSM client
the first time the incremental backup of a database is taken. The extra processing
occurs because the agent needs to interface with Lotus Notes(**) to break down
the contents of the database so that single notes can be restored later. The
user will need to decide whether backup/restore through the agent or through
the ADSM client better serves his purposes for a particular database.
Since the first incremental backup of a Notes(**) database can require more
processing, the user will need to decide wiether it is prudent to avoid using
wildcards for an incremental backup or, rather, work with individual databases
the first time around. As for restore performance, it may be desriable for the user
to back up Notes(**) database files periodically through the ADSM client (e.g. once
per month) and then take more frequent incremental backups of each Notes(**)
database (e.g. once per day). The reason is that backup copies of notes might be
spread to different media on the ADSM server, over time. A very large Notes(**)
database might have both very old and very recent data, whose backup data
are spread out among different volujes. The periodic backup of the entire file
offers an alternative to a database rebuild that might cause multiple media
mounts.
Collocation
Of course, ADSM collocation will also play a part in deciding the best setup for
each installation (See the ADSM Administrator's Guide for more information on
collocation). Since collocation is beneficial when a large number of objects need
to be restored together, its use is helpful for "rebuild" and "merge" capabilities.
Restoring Deletion Stubs
At least two versions, that is, an active version and at least one inactive version
should exist in your ADSM Notes(**) agent copy group, so you can restore deletion stubs.
What Happens Over Time
It is the combination of the way backup copies of notes are maintained on the
ADSM server and the nature of the Notes(**) database itself that will determine if
a particular version of the database can be rebuilt.
Backup version of notes on an ADSM server are similar to backup versions of
files on an ADSM server. For backup copies of files, the filespace in which the
copies reside correspones to a file system. For backup coies of notes, the
filespace in which a set of copies reside corresponds to a Notes(**) database.
The way in which backup copies are maintained over time will influence the
ability of a user to rebuild an entire Notes(**) database through backup coies of notes.
To explain the concept, we will imagine a Notes(**) database that has only two
notes in it. We will name the notes "A" and "B" Note A is update frequently.
Note B seldom changes. assume the database is backed up incrementally. Also
assume the ADSM server keeps one active backup copy and one inactive backup
copy of each notes. On day 1, after the very first incremental backup, there
is an active copy of both note A and note B on the ADSM serv. On day 2, say
note A gets updated in the Notes(**) database, but note B does not. At the end of
day 2, the second incremental backup takes place. Now there are 2 copies of
note A and one copy of note B on the server. On day 3, notes A gets updated
again, and, after the update, an incremental backup takes place. Since we
can keep a maximum of 2 copies of each note on the ADSM server, the backup
copy of note A taken on day 2 is rolled off.
So, in this scenario, what can we restore? We can rebuild the database back
to a "day 3" version, since we have backup copies of each note as it was on that
day. Similarly, we can rebuild the database back to a "day 2" version. We cannot,
however, rebuild a "day 1" version of the entire database because the "day 1"
version of note A was rolled off and is no longer available form the ADSM server.
If we wanted tor restore a "day 1" version only of note B, we could do that
because we still have a "day 1" version of note B on the server.
The above scenario suggest that it will be desirable to keep a particular number
of backup versions of notes on the ADSM server, depending on how far back in time
the user may want to rebuild a database. Since the rules for managing these
backup copies may be different from the rules for managing backup copies of
files or other data, the ADSM administrator may want to set up a separate domain
with a suitable default management class specifically for Notes(**) data. He might
also want to use collocation on the ADSM server.
====================================================
General Information:
====================================================
A redbook on the ADSM Lotus Notes(**) Backup Agent is available.
The book number is SG24-4534.
====================================================
Known Problems:
====================================================
1) On OS/2 Warp(*), a "dsmnotes incr" backup command that specifies
the root directory of a different drive from the current drive will
not search all the subdiretories for Notes(**) databases to back up.
For example, "dsmnotes incr -subdir=y c:\*" will not traverse
subdirectories when issued from drive d. Subdirectories will be
traversed, if any directory other than root is specified.
2) Database links that are backed up through the "dsmnotes incr"
command should be identifed to the command by its physical
location, rather than by its link file name in the Notes(**) data
directory. Directory links do not have this restriction.
====================================================
Fix Information:
====================================================
1) IC12350 - When trying , through the GUI, to restore a deleted
document that was backed up on tape, the agent did not wait
for the tape mount. The "days" value was also not being picked up
properly.
2) IC12649 (Internal APAR)
a) Wildcard restore
b) "Verbose" option for the command line
c) New log.dsm messages
See "Late-Breaking News" above for details on each
of these items.
====================================================
Trademarks
====================================================
(*) - Trademark or Registered trademark of the International Business Machine
Corporation.
(**) - The following terms are trademarks of the indicated company:
Lotus, Lotus Notes: Lotus Development Corpporation, an IBM Company
Intel: intel Corporation
CompuServe: Compuserve