IBM ILOG ODM Enterprise V3.4 Fix Pack 2
---------------------------------------

Installation information
========================
This fix pack is designed to install “on top of” existing installation of IBM ILOG ODM Enterprise V3.4 or, V3.4.0.1 as an upgrade. There is no need to uninstall your current product before installing this fix pack.

 
Fixed Issues
============
This fix pack resolves the following APARs:

APAR ID 	Description
-------		-----------	

RS00232		Optimization server fails to solve on WAS 6.1 patch 27 and up, WAS 7 on AIX 

RS00322 	Spaces in table names result in errors or, incorrect output	

RS00332 	Cannot use non-ASCII characters as rule category when oracle or, DB2 is used as data persistence 

RS00388 	Error "unable to create IloProjectElement instance from memento 'NULL'" when starting an ODM application from the IDE

RS00389 	Incorrect path listed for Derby database

RS00397 	Default SQL statements generated in the datasources editor for .odmds are incorrectly translated to local language 

RS00399		Documentation incorrectly refers to class IloOdmsLogger instead of java.util.logging.Logger

RS00436		ArrayOutOfBoundsException when restoring the sort on a simple table if the column names have changed

RS00437		Chinese characters in deployment settings file prevents deployment to optimization server 

RS00438		Mixing input and output data in the same view that is marked as editable causes output data to be editable 

RS00439		Default settings file are not migrated when importing a ODM 3.3 project

RS00440		Migration may transform OPL element names when creating mapping 


Enhancements
============
(1) Enables the mapping of Application Data Model elements to OPL arrays, which complements existing functionality of mapping to tuple sets
(2) Ability to document OPL model elements and have the documentation propagated to the generated OPL model
(3) Availability of ODM Enterprise Deployment edition automated installer log for troubleshooting installation problems


Known Issues
============
(1) Using default location (C:\Program Files(x86)\IBM\ILOG\ODME\Developer) for installation of 32–bit ODM Enterprise Developer Edition on a Windows 64–bit  
system will cause the embedded WebSphere Application Server (WAS) installation to fail. This is because of parenthesis in installation path. Workaround is to specify a different location for installation that doesn't contain any of the un-supported characters listed below:

{ } : ; * ? " < > | % , = + & ' # ^ ! ` $ [ ] ( )

Also, ODM installation path should be shorter than 47 characters. This ensures that requirement by WAS for root install path to be below 60 characters is met.
