IBM WebSphere Voice Response for Windows NT and Windows 2000 
ServicePak IP22595 README File
===================-===========================================================

Welcome to WebSphere Voice Response for Windows Version 3.1.3

This README contains information supplementary to the online help and the
publications; it includes helpful hints, tips, restrictions and corrections.
In many cases, this reflects features or functions which were changed or added
after the documentation went to publication.

This README is divided into the following sections:

 1. General information and installation instructions
 2. Description of new WebSphere Voice Response function
 3. Known Problems

									   

PART I: GENERAL INFORMATION AND INSTALLATION INSTRUCTIONS
---------------------------------------------------------
This release provides new functionality and service to WebSphere Voice Response
for Windows version 3.1 base code, program number 5724-C35. 


New functionality and updates included in this service release include:

  o Support for Intel Dialogic D/120-JCT Rev 2 telephony hardware. 
  o Support for VoiceXML Fetchaudio property.
  o Support for Australian English for VoiceXML programs.
  o Support for improved management of the Java/VoiceXML log file.
  o Support for the VoiceXML 2.0 feature to specify the language of a TTS prompt.
  o Support for User Definable Termination Tones

New function introduced in previous ServicePaks and also shipped in this 
    ServicePak:

  o Support of WebSphere Voice Server version 3.1
  o Support for two trunks worth of concurrent VR/TTS applications on a 
    suitably powered WebSphere Voice Response system.
  o Support for the VoiceXML <object> tag, including the ability to invoke 
    Java voice applications (written using JavaBeans) directly from within 
    a VoiceXML dialog.
  o Support for multilingual VoiceXML applications.
  o Support for Brazilian Portuguese Java Beans applications.
  o Support for Canadian French and Brazilian Portuguese VoiceXML applications.
  o Support for precompiled grammars in VoiceXML.
  o Support for N-best and confidence level in VoiceXML.
  o Support for Intel Dialogic D/320-JCT telephony hardware 
  o Revised documentation (HTML + PDF)
  
Updated software for the following products introduced in previous ServicePaks 
and also shipped in this ServicePak:
  
  o IBM Developer Kit for Windows (Java 1.3.1 Service Release 3)
  o IBM Object Rexx Interpreter Edition 2.1.1.0
  o Aculab Device Drivers and Configuration Tool 5.9.1
  o Aculab VisualCallGen

  

Warnings and Notes
------------------

Warnings:

This ServicePak is for installation on the following product and versions 
ONLY: 

o  IBM WebSphere Voice Response for Windows NT and Windows 2000 version 3.1
o  IBM WebSphere Voice Response for Windows NT and Windows 2000 version 3.1
   with an earlier ServicePak applied

Do not install it on any other version, and do not install this ServicePak if 
a later one has already been installed.  


Notes:

This document references the installation media for this ServicePak as being a
CD.  If the ServicePak has been downloaded from another source, please 
substitute all further references to the CD media with the root directory of
where the ServicePak is now stored.


Procedure to Determine Installed WebSphere Voice Response for Windows Version
-----------------------------------------------------------------------------
For a currently installed version of WebSphere Voice Response for Windows, the 
version can be obtained by running the Voice Response Configuration program and 
selecting Help -> Product Information from the menu bar.  The version number is
displayed beneath the product name.



Installing IBM Developer Kit for Windows (Java 1.3.1 Service Release 3)
-----------------------------------------------------------------------
This ServicePak requires the current version of Java SDK running on the 
WebSphere Voice Response to be "IBM Developer Kit, Java 2, 1.3.1" (Java 1.3.1
Service Release 3).  This version had been included in a previous ServicePak  
and should only be installed if not previously installed.  The installation 
package is included on the ServicePak CD within the \JAVA directory.

Prior to installation of Java version 1.3.1 Service Release 3, you should 
un-install any existing Java version installed on the machine.  WebSphere Voice 
Response for Windows previously shipped "IBM Cross Platform Technologies for 
Windows V2.0" (Java 1.3.0) " with version 3.1 and "IBM Developer Kit, Java 2, 
1.3.1" (Java 1.3.1 Service Release 2)" with ServicePak 1

To determine the current version of Java installed on your WebSphere Voice 
Response machine, open a command prompt window, and type:  

        Java -version        


To install Java 1.3.1 Service Release 3:

 1. Move to the \JAVA directory and run install.exe
 2. When asked, select your required installation language.
 3. Follow the on screen prompts to complete installation


Installing IBM Object Rexx Interpreter Edition 2.1.1.0
------------------------------------------------------
This ServicePak requires the current version of IBM Object Rexx Interpreter to 
be version 2.1.1.0.  This version update has already been included in an earlier  
ServicePak and need only be installed if your system has not already been 
updated to version 2.1.1.0. This update is only required if you are running 
TREXX applications, and requires version 2.1 to already be installed on your 
system.  Object Rexx version 2.1 was originally shipped with WebSphere Voice 
Response version 3.1, and should have been installed as part of the base 3.1 
installation.
 
To check your current installed version of REXX, open a command prompt window
and type:

        rexx -version

and confirm that the release is version 2.1.       

To install the service release 2.1.1.0 over version 2.1:
 
 1. Move to the \OBJREXX directory on the ServicePak CD-ROM.
 2. Run orxi211u.exe 
 3. When asked, select your required installation language.
 4. If prompted to terminate the Object REXX memory manager, select YES.
 5. Follow the on screen prompts to complete installation

Note.  When installing Object Rexx 2.1.1 service pack over Object Rexx 2.1 on
       Windows NT, the following error message may occur:

  1604: This setup does not contain the Windows Installer engine (INSTMSIW.EXE)
        required to run the installation on this operating system.
  
This messages indicates that the Object Rexx 2.1.1.0 service pack requires a 
newer version of Microsoft Windows Installer to be present on the machine 
before the Object Rexx 2.1.1.0 service pack can be applied.  Download the 
latest version of Microsoft Windows Installer from:
 
 http://download.microsoft.com/download/WindowsInstaller/Install/2.0/NT45/EN-US/InstMsiW.exe
 
Once downloaded, run InstMsiW.exe to install the latest version of Windows 
Installer on your WebSphere Voice Response system.  

Once the Windows Installer install package has completed, run orxi211u.exe 
again to install Object Rexx 2.1.1.0.


Aculab Device Drivers and Configuration Tool 5.9.1
--------------------------------------------------

This ServicePak requires the current version of Aculab Device Drivers to 
be version 5.9.1.  These device drivers have been shipped in a previous 
ServicePak and need only be installed if your system is not currently running 
version 5.9.1

These drivers resolve a number of known issues identified in existing releases 
using version 5.8.0.   These issues include:


  o Problem of high CPU usage when using Aculab network cards on some PC
  o Problem when configuring revision 1.52 Aculab network cards (acudetect.sys)
  o Windows 2000 native drivers now conform to Windows 2000 device driver model
  
These drivers are now shipped as two separate install packages, one for Windows 
2000 and the other for Windows NT.  Both install packages can be found in sub-
directories of the "\Aculab\Aculab Configuration Tool" directory of the 
ServicePak CD.  

Prior to installation of the Aculab 5.9.1 drivers, ensure that any existing 
Aculab drivers (5.8.0) are un-installed from the system.  Prior to un-installing
the existing drivers, it is recommended that the PATH environment variable is 
backed up, as total path deletion has been occasionally observed.  Refer to known
problems section for instructions on how to backup the path statement.

When configuring ISA cards under Windows 2000, additional Aculab software 
installation steps are required prior to running the Aculab Configuration tool.

Please refer to Appendix A of the revised WebSphere Voice Response Installation 
Guide for full installation and configuration instructions for Aculab 5.9.1


Aculab VisualCallGen
--------------------
The ServicePak CD also contains a revised version of the Aculab VisualCallGen 
application for testing and validation of telephony installations prior to 
installation of WebSphere Voice Response. This revised version has been shipped 
with an earlier ServicePak and should only be installed if required.


Installing WebSphere Voice Response Windows ServicePak
------------------------------------------------------
Before you can install this ServicePak you must have previously installed  
IBM WebSphere Voice Response for Windows NT or Windows 2000 version 3.1
If an earlier ServicePak has already been installed on the system you may 
install this ServicePak on top of the previous ServicePak.  If a previous 
ServicePak has not already been applied, then only this ServicePak need be 
applied as WebSphere Voice Response for Windows ServicePaks are accumulative.
 
To install the ServicePak:

 1. Close any running WebSphere Voice Response applications and stop the main
    GSI node.

 2. Insert the ServicePak CD into the CD-ROM drive on your personal computer.

 3. Install the WebSphere Voice Response ServicePak by opening the root 
    directory of the CD-ROM and double clicking on the Setup Launcher SETUP.EXE  
    If WebSphere Voice Response for Windows was originally installed by an 
    administrator, then you must have administrator rights to install the 
    ServicePak.  

    You will be asked whether you want to back up any files that are updated.  
    Click the Yes button to back up the files, or the No button if you do not 
    want a backup.  

    Notes: 

      (1) If you do not back up the files, you will not be able to uninstall 
          the ServicePak.  

      (2) Only one level of backup is available, so after applying this 
          ServicePak you can restore the previous version, if you back it up 
          on installation.  It is then not possible to restore earlier 
          ServicePaks without removing and re-installing the product and then 
          re-applying the required ServicePak.  

 4. After the ServicePak has been installed, WebSphere Voice Response 
    configuration MUST be run.  Normally this will run automatically after all
    of the files have been transferred to the workstation and just before the 
    installation program completes.  

    If you are in a special situation and manually edit the GSI configuration 
    file, you must first run the WebSphere Voice Response configuration before
    the manual editing.  Do not use an old copy from a previous configuration.

 5. WebSphere Voice Response for Windows with the ServicePak is ready for use.  


Procedure for Removing the ServicePak
-------------------------------------
If you decide you wish to remove the ServicePak after it has been installed, 
you can do so provided the backup option was used when the ServicePak was 
installed.  

To remove the ServicePak:

 1. Close all the WebSphere Voice Response sessions and stop the node.

 2. Open the CD-ROM drive object on your personal computer and double click 
    on the Setup Launcher SETUP.EXE.  

 3. Follow the screen prompts to complete the uninstallation, specifying that 
    you want to undo the update.  

 4. WebSphere Voice Response for Windows without the ServicePak is ready for 
    use.



PART II: DESCRIPTION OF NEW WEBSPHERE VOICE RESPONSE FUNCTION
-------------------------------------------------------------

Revised documentation
---------------------
The softcopy documentation supplied with WebSphere Voice Response for Windows
has been updated in this ServicePak.  The HTML documentation, if originally 
selected as part of the base 3.1 installation, is installed onto the WebSphere
Voice Response system.  

The revised documentation is also shipped in PDF format on the ServicePak CD.  
The PDF documentation is not installed as part of the ServicePak, and can be 
found in the \DOCS\PDF directory of the ServicePak CD.


Support for improved management of the Java/VoiceXML log file
-------------------------------------------------------------
Additional functionality has been added to the product to allow for better 
management of the NodeName.out files. This functionality is disabled by  
default, so no change to current operations will be seen.

The new functionality will backup the NodeName.out file, once it is at or above
a predefined limit, to a file called NodeName.out.YYYYMMDD_HHMMSS, where YYYY 
is the year, MM the month, DD the day, and HHMMSS represents the current time. 
A new NodeName.out file will then be created. It is the user's responsibility 
to maintain the file system. When the system is stopped and restarted, the  
NodeName.out* files from the previous run are backed up, with the extension 
.bak added to the file names. Any previous backup files are deleted. The log 
files are currently cycled when they reach 5MB in size. The output to the file 
is written on a line basis, so the exact file size may be a little over this  
value. 

The following details how to enable this new functionality:
  - edit dtj.ini and add the following line:
    log.usenewformat=true
  - stop the system, using dtjstop and dtjshost -exit.
  - Restart the HostManager (dtjshost) and the Nodes (dtjstart).


Support for the VoiceXML 2.0 feature to specify the language of a TTS prompt
----------------------------------------------------------------------------
The VoiceXML 2.0 feature to allow specification of the language of a TTS prompt 
has been implemented in the VoiceXML 1.0 browser shipped with WVR. If a locale 
is specified on a <prompt> tag this will be honoured, assuming the available 
TTS engines are appropriately configured. 

Thus the following example will use both the US English and German TTS engines:

   <vxml version="1.0" lang="en_US">
      <form>
       <block>
        Welcome.

            <prompt xml:lang="de_DE">Wilkommen.</prompt>

       </block>
      </form>
   </vxml>


Support for User Definable Termination Tones
--------------------------------------------
User defined termination tones have been included to allow up to ten new user 
definable tone definitions to be detected during a call (using Dialogic 
Global Tone Detection).  These tone definitions can be used to recognise far end
generated tones such as those  produced by answer machines etc. 

On recognition of one of the user defined termination tones, a DTMF value in the
range 'E'' through 'N' is returned to the calling voice application to signify 
which user tone has being detected.

These new tones are defined within the "Tone Detection Definitions" section of 
the "Voice Response Telephony Server Configuration" tool. Within this  
application , a new tone class called "User (Term)" has been included to the
existing classes of "Busy", "Ringback", "FAX/Modem" and "Hangup (HUP)" Up to 10 
new tone definitions can be included, each of which will be allocated to all 
configured telephony line during WebSphere Voice Response for Windows 
initialisation.

User defined tones are added in the same manner as existing tone definitions,  
however the "Tone ID" allocated must be a single digit in the range 'E' through 
'N'. The "Tone ID" value reflects the DTMF value which will be presented to the 
voice application on detection of the tone. 

These tones will be detected and presented in the same manner as the existing 
DTMF tones '0' through '9', 'A' through 'D', '#' and '*' when used as 
termination characters during actions such as playing voice segments and/or 
getting DTMF tone details.


Using user terminated tones in VoiceXML
---------------------------------------
A VoiceXML application can play audio segments using the <prompt> tag. Detected  
user tones definitions can be caught during play by the use of the 
<option dtmf=’'e'> tag (where the user tone has been allocated the ID of 
'E').

Using user terminated tones with the Java Beans
-----------------------------------------------
Under the current environment, if a playing voice segment or a voice recording  
is terminated by a DTMF input, the beans environment will populate the called  
java (Action) beans completionCode property with a value of DTMF_KEY_PRESSED 
(542).  

The java beans application can then check the actual DTMF tone which terminated  
the action using the entryField beans entryField.getInputField() method.  

A returned DTMF value in the range 'E' through 'N' can be determined to be a 
user termination tone and can be acted upon by the voice application as 
appropriate.

Using user terminated tones with TREXX
--------------------------------------
User tone detection will present itself via the TREXX actions as if a DTMF tone
had been detected.  Hence actions, such as Play_Module, which already offer a 
return code value of KEY_PRESSED (1) to identify a DTMF tone termination will 
present the same return code when detecting a user termination tone.  

A subsequent call to Get_a_Tone will still identify the DTMF tone received,  
however the values in the range 'E' through 'N' will now be valid.


Problems Fixed
--------------
Problems that have been fixed in this ServicePak include the following APARs:

WVRWIN Base APARS
IC35486 AFTER CSD2, USER ACTIONS FROM TREXX FAIL WITH EXH4019 ACTION <NAME>
        IS INVALID.
IC35733 Batch Node Manager stop_appls command failure.

WVRWin Java and VoiceXML APARS
IC35602 Invalid heartbeat failures for sleeping DTBE applications.
IC35767 US English DTBE Applications mis-pronounce year in date field.
IC35885 BROWSER DOES NOT RECOVER ON WWW SERVER FAILURE.  
IC35886 AFTER EXECUTING A CATCH BLOCK, THE NEXT FIELDS PROMPTS ARE NOT 
        PLAYED.
IC35887 APPLICATIONDATA SET TO THE WRONG VALUE AFTER VXML APP ENDS 


Problems that have been fixed in previous ServicePaks and are in this
ServicePak include the following APARS: 

WVRWIN Base APARS
IC33657 Connect_screen does not return from LUA session if no network             
IC34903 Changes to TRX files made using DWA and Notepad.exe are not saved.
IC34927 VPE programs do not execute correctly under 3.1.

WVRWin Java and VoiceXML APARS
IC33622 Vxml record tag noinput block executes even after dtmf entry
IC33623 Exception from vxml when using submit tag.
IC33624 Incorrect pauses in <sayas> tag       
IC33625 Ending a <RECORD> with finalsilence causes the app to terminate 
IC33646 DEUTSCHLAND not recognized in german version of weather sample         
IC34122 E1 Single line transfer not supported from Beans application.
IC34273 Single line transfer fails from DTBeans app when switch response slow.
IC34277 Clear DTMFProperties to allow voice input after key input 
IC34464 DTJPLEX - Action exportvoicehost fails with nullpointerexception
IC35303 VXML root document variables reset on cache reload. 
IC35304 NULLPOINTEREXCEPTION if using INPUTMODES=DTMF and BARGEIN=TRUE
IC35305 VXMLAPP remains active after timeout badfetch



PART III: KNOWN PROBLEMS
------------------------
This section lists problems/restrictions that have been discovered which may 
or may not have a fix available, or may not be documented within the current 
WebSphere Voice Response documentation.


VoiceXML Weather Sample Program Produces Messages in Java Node Log
------------------------------------------------------------------
The VoiceXML Weather sample program will produce the following messages in the
Java node log (default Node1.out):
 
 E DTJ6300 E java.io.FileNotFoundException: /c:/dtalk/dtbe/samples/zh_CN/Version.wav
     (The system cannot find the path specified)
 E DTJ6300 E java.io.FileNotFoundException: /c:/dtalk/dtbe/samples/ja_JP/Version.wav 
     (The system cannot find the path specified)

The sample program is common to both the Windows and AIX platforms and now 
includes prompts for Chinese and Japanese. As these languages are not supported 
on the Windows platform they are omitted and will, therefore, not be spoken by 
the sample program. 

Apart from the above messages there is no other impact and the sample program 
will continue to perform as before.


Support for Echo Cancellation using Intel Dialogic D/320-JCT
------------------------------------------------------------
If an Intel Dialogic D/320-JCT PCI card is to be used as echo cancellation
resource card then the supplied Dialogic software package (SR5.1) fails to allow
the card to be configured correctly.  To configure echo cancellation correctly, 
change the following TDM Bus settings within the Dialogic Configuration 
Manager (DCM) software:
       
 1. Select TDM Bus -> Bus-0
 2. Set TDM Bus Type (User Defined)     to SCbus
 3. Set SCbus Clock Rate (User Defined) to 4MHz
 4. Set Using NETREF One (User Defined) to No
   

D/320SC ISA card cannot be configured as EC Resource
----------------------------------------------------
If an Intel Dialogic D/320SC ISA card is to be used as an echo cancellation
resource card then the supplied Dialogic software package (SR5.1) fails to allow
the card to be configured in this way.  Using the Dialogic Configuration Manager 
(DCM) the EC_Resource parameter is missing under the Misc tab and therefore 
it is not possible to select YES for this parameter.  To overcome this 
restriction:
 
 1. Edit the file \Dialogic\INF\hdbu.inf 
 2. Change the text in the [D/320SC.Properties] section from: 
     
     Misc = HDDevice.MiscProps        
       to:
     Misc = HDDevice.MiscProps_ECR

 3. Ensure that the EC_Resource parameter is added as a value in the registry
    for the installed card.  Use REGEDIT to create the entry:
     
     EC_Resource  REG_SZ  ON

    under, for example, the registry key:

     My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Dialogic\Installed Boards\Dialog\HD\D/320SC at ID 1

    This example assumes the ID switch setting for the D/320SC card is set to 1.


Problem with PCI slot usage on IBM Intellistation PC using revision 1.52 Aculab 
network card
-------------------------------------------------------------------------------
A problem has been discovered when using an Aculab revision 1.52 network card in
some models of IBM Intellistation (model 6849).  The Aculab network card works 
sucessfully in some PCI slots, but is not available in other slots.  The problem
is typically identified under Aculab 5.9.1 by the PC hanging when the Aculab call
driver or firmware are started.  The current resolution to this problem is to move
the card to another PCI slot.

Please contact your service representative for current status on this problem.


2 trunk WebSphere Voice Server Support 
--------------------------------------
A potential problem has been identified when running WebSphere Voice Response 
applications with WebSphere Voice Server voice recognition software enabled, 
on a Dialogic T1 network card with additional Dialogic echo cancellation 
resource cards.  It is possible that after a prolonged period of running, that 
a number of voice channels may hang.  This problem can usually be identified 
by the following message in the GSI log.

 EXH3999 Telephony Server Internal Error, report the following 2 messages:
 EXH3998   Component STO, instance <sto inst#> detected the error.  Error text-
 EXH3997   ecStopInstReq for inst <ec inst#> failed, state 3
       

These hanging channels can only be re-enabled by stopping and restarting the 
WebSphere Voice Response system and the Dialogic Configuration Manager (DCM) 
software.

Please contact your service representative for current status on this problem.


Deleted PATH environment variable whilst un-installing Aculab 5.8.0
-------------------------------------------------------------------
It has been recognised that occasionally the uninstalling of the Aculab 5.8.0 
drivers can cause the Windows PATH environment variable to be deleted.  

As the PATH statement contains information necessary for other installed 
applications and Windows itself, it is recommended that the PATH statement is
backed up prior to uninstalling Aculab 5.8.0.  To backup the path statement:

On Windows 2000 
  o  select from the Start menu
       Settings —> Control Panel —> System —>Advanced —> Environment Variables
  o  select the PATH system variable and select edit.  A new window should 
     appear.
  o  highlight the variables contents value
  o  Copy the contents using ctrl-C
  o  Close the window by clicking on OK.
  o  Select New to create a new system variable
  o  Name the new variable PATH_BACKUP
  o  Move to the new variables value filed and press ctrl-V to populate the
     field with the copied path variables contents
  o  select OK to create the new variable.
   
On Windows NT,select from the Start menu 
  o  select from the Start menu
       Settings —> Control Panel —> System —>Environment
  o  select the PATH system variable.  The contents of the variable is shown
     in the variable field at the bottom of the window
  o  Change the Variable name field value to PATH_BACKUP
  o  Create the new variable by selecting Set
        

To recover a lost path statement,  follow the above instructions to recreate
the PATH environment variable from the PATH_BACKUP environment variable.


Record/Playback signal levels with analog cards
-----------------------------------------------
Problems have been found with record and playback signal levels when using 
analog cards and in particular the D/41ESC network card.  This has been 
attributable to homologation standards that now require lower signals levels 
than previously provided.  When not directly connected to the public network, 
the following improvements have been recommended by Dialogic/Intel Tech Support

 1. To improve record signal levels set the Receive Gain parameter for each 
    analog card to RX_GAIN_P3 under the Country tab within Dialogic 
    Configuration Manager (DCM).  This will require the Dialogic service to 
    be stopped and then re-started before the change can take effect.  The 
    parameter selection is not available for all countries and selecting 
    United State could make this available.

 2. To improve playback signal levels, create the firmware parameter text file 
    with the following text;

      AREA=VOICE
      SIZE=WORD
      PARAM 11: (DECIMAL WORD) 58176  # -4 dBm playback volume low word
      PARAM 12: (DECIMAL WORD) 94     # -4 dBm playback volume high word

    Save this text in ..\Dialogic\data\fwpatch.prm.  Stop the Dialogic service 
    (using DCM) and within the properties for each analog card set the 
    Parameter File value under the Misc tab to fwpatch.prm.  Re-start the 
    Dialogic service to load both the standard firmware together with the 
    patched parameter value.


Either of these suggestions should work with any of the supported analog cards. 


Dialogic Hardware
-----------------
A number of countries have reported problems whilst ordering Dialogic telephony
boards.  This is due to Dialogic introducing a U to the product name which 
identifies the card as being Universal PCI bus (3.3 and 5.0 volt).  Hence a 
D/320JCT may now also be known as a D/320JCTU


Trademarks and Service Marks
============================

WebSphere Voice Response, IBM, and WebSphere are trademarks of IBM Corporation
in the United States, other countries, or both.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation
in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries,
or both.

Dialogic and Intel are trademarks of Intel Corporation in the United
States, other countries, or both.


Other company, product, and service names may be trademarks or service
marks of others.

The following paragraph does not apply to any country where such provisions
are inconsistent with local law:

IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING
WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH
RESPECT TO THE INFORMATION IN THIS DOCUMENT, IBM GRANTS NO LICENSES
TO ANY RELATED PATENTS OR COPYRIGHTS.

(C) Copyright International Business Machines Corporation 1991, 2003.
All rights reserved.


END OF FILE