Progress OpenEdge 11.5.0.0 Readme

Ports: All
Date: December, 2014
--------------------------------
Copyright (c) 1984-2014 Progress Software Corporation.  All rights reserved.


Read these On-line Release Notes
================================

It is important to read these on-line release notes.  They are the
exclusive release notes for this release.

The on-line release notes are on the distribution medium as one text file, readme.txt.

The readme.txt file includes a list of known issues followed by a list of the issues fixed in this release.

In addition, the distribution medium includes the following HTML report files which list the issues addressed
in this release -  organized by version, issue number (CR ID), or product component.

  * PROGRESS_OE_<release#>_VERSION.htm (Lists fixed issues by Version)
  * PROGRESS_OE_<release#>_ISSUE.htm (Lists fixed issues by Issue Number)
  * PROGRESS_OE_<release#>_COMPONENT.htm (Lists fixed issues by Component)

---------------------------------------

PRODUCT NOTES for 11.5.0.0

a. ADE Tools and Runtime

PSC00316376 : Correction to default dump names for schema tables
================================================================================
Dump and Load operations for the data of the _Partition* system tables now use
the entire table name when the dump name is unknown. 


PSC00200793 : Initial value rules for logical fields in the GUI Dictionary
================================================================================
By default, when you create a logical field through the GUI Data Dictionary, it
sets the Initial Value as the first value in the Format. For example, if the
Format is "male/female", the Initial value defaults to male. The exception to
the first item rule is when the format is "yes/no" or "true/false". For those
cases, the tool uses the OpenEdge default value for a logical field, "no" and
"false", respectively.


PSC00172720 : Mandatory fields are not marked as NOT NULL during protoodbc
================================================================================
When running a pro-to-odbc migration against a DB2 data source, fields marked
as "mandatory" in the OpenEdge database were being created in generated SQL
script and the foreign data source without the NOT NULL syntax.  This leads to
a situation where these fields are null capable in the foreign database.  

To make DB2 consistent with the MS SQL Server and Oracle DataServers, the
OpenEdge DataServer for ODBC will now set the NOT NULL constraint on SQL
columns derived from mandatory fields for DB2 data sources.


PSC00155578 : Generic comment deletion code removed from triggers
================================================================================
Deletion triggers have been updated to not generically remove comments,
security allocation and multi-media records due to performance impact. A new
ERWin trigger template db/af/erw/afercustrg.i has been provided that customers
can use to re-generate their own triggers without the generic deletion code.
Customers can also update their triggers with specific code to do the deletion
in such a specific way that should not have any performance impact.


PSC00240314 : Migrating Progress Dynamics to Release 11.0+
================================================================================
Before attempting any migration, convert the physical database to Release
11.0+, using the proutil conv1011. Progress Software Corporation recommends
making a backup at this time.

Before migrating to Release 11.0+, Progress Dynamics currently using Version
2.1B must upgraded to Version 2.1B02. The following steps are the only
supported path to migrate a Version 2.1B Repository to OpenEdge 10.2B:
- Ensure the Repository is upgraded to Version 2.1B02 (db version: 020030). The
migration does not work properly on earlier versions of the Repository.
- Create a new shortcut for the Dynamics Configuration Utility (DCU), based on
the existing shortcut from the install.
- Modify the -icfparam parameter in the target. Change
'DCUSETUPTYPE=ProgressSetup' to 'DCUSETUPTYPE=Migrate21Setup'.	
- Run the Dynamic Configuration Utility (DCU) from this shortcut to upgrade the
Repository from Version 2.1B02 to Release 11.0+.


To migrate from Release 10.0B05 to Release 11.0+, follow these steps:
- Ensure the Repository is upgraded to Release 10.0B05 (db version: 100005).
The migration does not work properly on earlier versions of the Repository.
- Create a new shortcut for the Dynamics Configuration Utility (DCU), based on
the existing shortcut from the install.
- Modify the -icfparam parameter in the target. Change
DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate100Setup.  
- Running the DCU from this shortcut upgrades the Repository from Release
10.0B05 to Release 11.0+.


To migrate from Release 10.1A02 to Release 11.0+, follow these steps:
- Ensure the Repository is upgraded to Release 10.1A02 (db version: 101002).
The migration does not work properly on earlier versions of the Repository.
- Create a new shortcut for the Dynamics Configuration Utility (DCU), based on
the existing shortcut from the install.
- Modify the -icfparam parameter in the target. Change
DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate101ASetup.  
- Running the DCU from this shortcut upgrades the Repository from Release
10.1A02 to Release 11.0+.


To migrate from Release 10.1B03 to Release 11.0+, follow these steps:
- Ensure the Repository is upgraded to Release 10.1B03 (db version: 101101).
The migration does not work properly on earlier versions of the Repository.
- Create a new shortcut for the Dynamics Configuration Utility (DCU), based on
the existing shortcut from the install.
- Modify the -icfparam parameter in the target. Change
DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate101BSetup.  
- Running the DCU from this shortcut upgrades the Repository from Release
10.1B03 to Release 11.0+.

To migrate from Release 10.1C to Release 11.0+, follow these steps:
- Ensure the Repository is upgraded to Release 10.1C (db version: 101201). The
migration does not work properly on earlier versions of the Repository. The
migration will also work for service packs 1 and 2.
- Create a new shortcut for the Dynamics Configuration Utility (DCU), based on
the existing shortcut from the install.
- Modify the -icfparam parameter in the target. Change
DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate101CSetup.  
- Running the DCU from this shortcut upgrades the Repository from Release 10.1C
to Release 11.0+.

To migrate from Release 10.2A to Release 11.0+, follow these steps:
- There were no updates made to the Repository between 10.2A and 11.0, and so
no migration is necessary.

To migrate from Release 10.2B to Release 11.0+, follow these steps:
- There were no updates made to the Repository between 10.2B and 11.0, and so
no migration is necessary.


PSC00178641 : DCU enforces MinVersion with migrations
================================================================================
If a setup XML file has migration setup types (defined by having a
migration_source_branch session property with a non-blank value), then a check
is performed to ensure that the DB version sequence matches that of the
MinimumVersion in the Database node of the setup_type. If these 2 versions
don't match an error is raised and a message shown.

This message is a new message and has a code of 'MSG_cannot_migrate', and
appears in the shipped setup101B.xml. If customers have created their own
setup.xml files, they need to add this message to all the setup types contained
in those XML files.


PSC00174297 : Dynamics translated application: performance problems on login
================================================================================
Support has been added for a session property called "cached_translations_only"
which is set via the session definition (in the XML file and/or repository). In
the absence of such a property in the session, the default is YES (the
historical value). If cached_translations_only is false, then translations are
not retrieved at startup, but rather on demand when an object is translated.


PSC00162290 : Static Object Deployment Tool - Option to generate source listing
================================================================================
The Deploy Static Objects tool has the ability to produce a listing file of all
the files that are packaged into a deployment produced by the tool. 

The listing file is specified in the UI before the deployment starts building.
If no listing file is specified, then the listing will not be produced. A
default value is provided by the tool, and is for a file called 'listing.log'
in the session's temporary directory.

The listing file consists of the following fields, tab-delimited:
File name
Relative path
Deployment type
Design-only flag

This functionality can be used to determine which files are required for
compilation on 64-bit platforms. A Dynamics client is only supported on
Windows, which is a 32-bit platform, and customers may connect to an AppServer
running on a 64-bit platform; in such a case the code would need to be compiled
against the 64-bit platform, and the listing file will give the ability to
determine which files are required.


PSC00140234 : Notes on using the Deploy Static Objects tool
================================================================================
When deploying static objects using the Deploy Static Objects tool, please note
the following:

1) You must specify the following extra directories in the Deploy Static
Objects tool, in order for a standard Progress Dynamics WebClient install to
work:
    adeicon 
    ry/img
    adm2/image	

adeicon.pl can be used instead of the adeicon directory, but you must manually
copy this file into the target directory. These image directories are not
required for a server install (AppServer of Web).

2) You must manually copy the adm2/dyntreew.wrx file into the target directory,
for WebClient installs.

3) You must manually copy adecomm.pl into the target directory for a WebClient
install.


PSC00314904 : The adm2/dyntreeview.w SmartObject only works in 32-bit installs
================================================================================
The adm2/dyntreeview SmartObject is implemented using a 32-bit OCX control. An
error message about the OCX not being registered or moved will be thrown if you
attempt to run or drop this SmartObject on a container in a 64-bit install.


PSC00240288 : The DynamicsVersion session property must be manually updated
================================================================================
If you are working in an OpenEdge release later than 10.2B, the DynamicsVersion
session property may be set to the wrong release number. This property is not
automatically updated.

To workaround this issue, modify
$DLC/src/dynamics/db/icf/dfd/update_dynamics_version_property.p so that the
value of the DYNAMICS-VERSION preprocessor is set to the relevant OpenEdge
release number (11.2, for example). Compile this file and copy to $DLC/gui,
which is important because the DCU does not run against source code.


PSC00224776 : ADM2 default data management ignores orphaned/unlinked SDOs on
Viewers
================================================================================
A SmartDataObject (SDO) placed on a Viewer without being linked to a data
source or to a field is not included in the container's first request to the
AppServer and will thus not get any data. This was not the case in old releases
of OpenEdge (before v10).  

You can uncheck the Appserver Aware option in the Procedure Settings of the
container to get the old behavior. This makes the SDOs revert to the old
request behavior with one AppServer request per SDO. Note that this can add a
substantial overhead to the data retrieval from the  AppServer. 

Alternatively, you can move the SDO to the SmartContainer and use the pass-thru
link mechanisms to make it accessible to the Viewer, or override
initializeObject in the Viewer and call openQuery in the SDO. This approach may
require one extra AppServer request specifically for the SDO. 


PSC00219897 : Dynamic SDO with join require calculated fields to be defined in
table order
================================================================================
In a Dynamic SDO based on a join, calculated fields will behave incorrectly
under these circumstances:
- Both tables in the join have calculated fields defined in the Repository's
entity definitions.
- Both tables also have one or more of these SDO Entity calculated fields
included in the SDO.
- The calculated fields from the right-hand table of the join appear before
those of the left-hand table in the list of fields in the SDO.

Symptoms include incorrect formatting and incorrect initial values being
provided, as well as calls to the SDO data logic procedure failing with errors
relating to temp-table schema mismatches.


PSC00207823 : dynlaunch.i fails in thin client with DATETIME, DATETIME-TZ, RAW
or ROWID param
================================================================================
Calling a PLIP using dynlaunch.i fails in a thin-client environment if the
procedure call includes DATETIME, DATETIME-TZ, RAW or ROWID parameters.

The client will report this error:
Mismatched number of parameters passed to routine <name>. (3234)

The AppServer agent will report these errors:
BUFFER-FIELD was not found in buffer ttSeqType. (7351)
Lead attributes in a chained-attribute expression (a:b:c) must be type HANDLE
or a user-defined type and valid (not UNKNOWN). (10068)

The workaround is to implement calls with these data types to run as external
procedure calls on the AppServer.  

e.g. RUN xxx on gshAstraAppServer (INPUT ...)

Alternatively, you might add CASE statements for the 4 data types in
obtainInitialValueField in adm2/caller.p. (This has not been tested, but is
assumed to be the problem.)


PSC00195316 : **Widget ID <n> not unique (<widget-name>) error for recursive
Dyn TreeViews
================================================================================
The "Runtime Widget-ID Assignment" tool assigns default gap values for the
imported SmartObjects.
These default values should work without problems in most cases. But, for
Dynamic TreeViews with structure nodes, the default gap value of 2000 for
"TreeNode" might not be large enough.
Since the nodes are created at runtime according to the database data, it is
impossible to know how many tree node levels are going to be created in the
Dynamic TreeView. If this happens and the default gap value of 2000 is not
enough, that default value should be increased as specified in the "Application
Development Environment (ADE) Addenda" Web paper in the "Widget IDs for ADM2
and Progress Dynamics" section.


PSC00194792 : Toolbar never creates a Band more than once per toolbar instance
================================================================================
The toolbar creates only a single instance of each Band for a toolbar instance.
However, the Repository allows multiple instances of the same Band on a
toolbar. Before Release 10.1C, the toolbar created the multiple instances of
the same Band, but the second instance had no menu items. In Release 10.1C, the
second instance of a Band is ignored completely.


PSC00180829 : DynLookup limit on number of joins may vary on DataServers
================================================================================
In Release 10.1C, the DynLookup supports a join with up to 18 tables instead of
10. But, this limit might not apply when using a DataServer, because there also
is a limit decided by the size of the ROWIDs in the tables. The ROWIDs of the
tables are added to an indexed RowIdent field and the ABL has a limit on the
size of an index. 

Starting with Release 10.1B, as long as -tmpbsize 4 (default) or larger is
used, temp-tables use large index keys and can store up to 1970 characters.
This means that, in theory, you can store and index up to 16 ROWIDs returned
from MSSQL server ( 16 * ( 116 + 1 ) - 1 = 1871 characters for rowids +
separators). The different DataServers will return ROWIDs with different
lengths, so the limit will vary. 

If this limit is an issue, then you can edit the af/app/afgettemp.p procedure
and remove the following index definition.
 
----
hTT:ADD-NEW-INDEX("idxRowIdent":U,FALSE,FALSE).
hTT:ADD-INDEX-FIELD("idxRowIdent":U,"RowIdent":U,"asc":U).
----

The index is used in certain reposition operations on the client. Removing it
has an affect on performance, but this might be unnoticeable or acceptable
since the operation is done on the temp-table on the client.


PSC00170305 : UndoChange action added to all tableio toolbars
================================================================================
Beginning with version 10.1B all shipped toolbars and tableio bands contain a
new UndoChange action. This action replaces the old Reset action as the default
in these toolbars.  

This constitutes a behavior change (label and accelerator) for existing
applications that use the shipped toolbars or bands, since the caption is
changed to "Undo" instead of "Reset" and the accelerator is changed to "CTRL-Z"
from "ALT-R". 

The new UndoChange action defines some of the translatable text needed for the
context sensitive text in the admmsgs.i include, message number 97.    

Customers that use the shipped toolbars or bands and want to remove the new
action and get the old one back need to customize the class or toolbar.
Customers that already have specific toolbars might need changes either to be
able to use the new action or to remove it.
 
To remove (hide) the new UndoChange action and get Reset back in shipped
toolbar or band:
-------------------------------------------------------------------
The Reset action is already present in the toolbar, so in order to make the
Reset into default, the UndoChange needs to be added to the comma-separated
HiddenActions property.   

Existing customer toolbars
--------------------------
Existing customer toolbars may or may not get the new UndoChange action. If the
toolbar or menu is defined with the "Tableio" category or one of the tableio
bands, then the action is added automatically. But, many toolbars add tableio
actions specifically in initAction() or initMenu() overrides in order to
control the order and add rules. The "UndoChange" will need to be added to
these.	 

customized initAction
---------------------
Since the getTableioUndoNew may need to load the actions if it is called from a
visual object before the toolbar is initialized, the toolbar initAction has
been changed to setIsActionsLoaded(true). Overrides of initAction that do not
call super must add the same call, using dynamic-function or the {set~ include.


PSC00167044 : The Export to Excel functionality removes leading zeros from
character strings
================================================================================
The Export to Excel functionality removes leading zeros from character strings.


PSC00162037 : IndexInformation property only contains information for primary
table(s)
================================================================================
The IndexInformation property has been changed to only contain index
information for the table(s) that are uniquely represented in one row in the
SDO query. The default table(s) are the EnabledTables or the first table for
read-only SDOs. 

The getIndexInfoTables function determines which tables' info is added to the
property. This is not implemented as a property, but can be overridden if
different behavior is needed. If you want the old behavior all data objects,
then add a custom version that returns the value from getTables (all tables in
the query).


PSC00161048 : Changes to how decimal values are managed in dynamic combos
================================================================================
There were several problems in previous releases developing decimal dynamic
combos with default flag values that contain a numeric decimal point and
deploying with different numeric formats.

Default flag values were always stored in the format used during development. 
This prevented deployment to numeric formats other than the one used for
development.  Either errors displayed and no data displayed in the combo or
incorrect data was stored in the repository for the <None> or <All> option.

With 2.1B01, 10.0B03 and 10.1A this has changed to store default flag values
with American numeric format.  They should be entered in the SmartDataField
maintenance tool using the session's format but the tool will replace the
numeric decimal point with a period in the stored value.  At runtime, any
stored periods in the data are replaced with the current session's numeric
decimal point.

A fix program runs as part of the DCU Upgrade to convert existing default flag
values for decimal dynamic combos to American format.  The DCU must run in the
format that was used to develop dynamic combos.

The fix program writes a message to the log file for each default flag value it
attempts to convert.  It writes a message when a value is converted
successfully or writes a message if the conversion fails.  Review the DCU log
file after the upgrade and manually correct any failures.  Any failures that
are not corrected may not behave properly at runtime as the runtime has changed
to attempt to convert stored American formats to the format of the running
session.

There are several Dynamics objects in the repository that store blank default
flag value instance attributes and give messages in the log file.  These are
for the cbSCMTool dynamic combo on the following viewer objects:

gsmsxgenviewv
gsmsxotviewv
gsmsxpmviewv

The messages for these objects are expected and you can ignore them.

Any dynamic combo instance attributes stored in static viewer code in your
application must be converted manually to American numeric format.


PSC00159054 : assignNewValue w/ invalid values behaves different in new lookup
API
================================================================================
The old and new lookup APIs behave differently when passing invalid value
parameters to assignNewValue if the lookup key field is different from the
lookup displayed field.

With the old API (pre-2.1B/10.0B02 behavior and 2.1B/10.0B02 behavior with
keep_old_api set to TRUE), passing an invalid key field value or an invalid
displayed field value to assignNewValue displays blank in the lookup field when
assignNewValue is invoked. If changes to the record are saved, blank is stored
in the record's key field.  

With the new API (2.1B/10.0B02 default behavior), passing an invalid key field
parameter displays blank in the lookup field when assignNewValue is invoked. If
changes to the record are saved, the previous value displays in the lookup
field and the value is not changed in the record's key field. Passing an
invalid displayed field parameter displays the invalid value in the lookup
field when assignNewValue is invoked. If changes to the record are saved, the
previous value displays in the lookup


PSC00158854 : Widgets on static SmartDataBrowser are not enabled on dynamic
containers
================================================================================
When a static SmartDataBrowser contains other objects on its frame, those
objects are not enabled when the static SmartDataBrowser is run on a dynamic
container.  When that static SmartDataBrowser is run on a static container,
those objects are enabled.


PSC00158601 : BaseQuery must have NO-LOCK after WHERE
================================================================================
A child SDO loses parent filter criteria if its BaseQuery has the NO-LOCK
option before the WHERE criteria.

When two SmartDataObjects are linked in a parent/child relationship, with or
without a SmartBusinessObject, the child SDO might lose its filtering by the
parent SDO. In previous versions, this happened if the child SDO was generated
by the Object Generator with Follow joins turned on. This generated a BaseQuery
with NO-LOCKs before the join criteria and caused the ADM to add the
foreignfield criteria to the query incorrectly. 

As a workaround, opening and saving the SDO in the AppBuilder alters the
BaseQuery to put the NO-LOCKs after the join criteria as expected by the ADM.


PSC00158372 : DynCombo support for a DataObject as data source does not include
static SDO
================================================================================
The option to define an SDO DataSource for a DynCombo is not supported for
static SDOs.


PSC00158340 : Sharing data object, browse and viewer out of sync showing data
================================================================================
The support for SharedData does not actively refresh viewers or browse
viewports when data is changed by another DataObject. To refresh a browse, you
must currently scroll the record out of the viewport. To refresh a viewer, you
must currently navigate to another record and back. Note that a viewer on a
hidden page does not refresh itself if it is on the same record as when it was
hidden. So, in this case, it does not help to navigate to another record and
back in the browser.


PSC00157892 : SDO Cache does not include Auditing & Comments tick-information
================================================================================
The data caching and data sharing support does not always cache auditing and
comment information. This information is retrieved only for certain instances
and would only be cached if the actual object that did the initial server
retrieval was set up to include this information. Data objects that retrieve
their data from the cache may thus be unable to show the correct tick-mark in
the toolbar if the initial server request did not include this information.


PSC00157071 : stripLookupfields is not used in the new lookup API
================================================================================
In previous versions, the stripLookupFields procedure was called on each
display to figure out if the SmartDataFields could be resolved by the viewer's
DataSource. The new lookup API does not use this procedure.


PSC00156968 : Setting of BaseQuery in initializeObject requires synchronization
of QueryWhere
================================================================================
If any other query manipulation has been done before changes to the BaseQuery
are made, you need to synchronize QueryWhere and possibly the QueryString. If
the BaseQuery is set in an initializeObject override before SUPER, you might
also need to synchronize QueryWhere in an SDO without any custom query
manipulation. The only cases where BaseQuery can be set without synchronizing
the QueryWhere are on the client (AsDivision = 'client') and in dynamic SDOs on
the server (AsDivision = 'server'). Static SDOs calls setOpenQuery, which calls
setQueryWhere, from the main block (query.i) when connected to the database.
Dynamic objects that are connected to the database will call prepareQuery from
createObjects.

Background: 
The BaseQuery is the design-time, fixed part of the query. It is part of the
object definition. The design philosophy is that runtime query manipulation can
be done without violating the integrity of this part of the expression.
Consequently, the BaseQuery should not be changed after any query manipulation
has been done.
However, it is quite common for applications to need to set this when an SDO
instance is launched. (For example, to filter data on department or company key
based on the userid.) 
Various examples and documentation have shown and stated that this can be done
in an initializeObject override before the call to SUPER. In particular, older
documentation examples showed this being done with setOpenQuery, which also
synchronizes the physical query by calling QueryWhere. This was a problem on a
client since setQueryWhere used to always prepare the physical query.
setQueryWhere has since become more lightweight, but setOpenQuery still calls
the server and should still be avoided in an AppServer session.


PSC00156174 : Translation tool does not include SmartDataBrowser search field
================================================================================
The optional search field of a SmartDataBrowser doesn't show up in the
translation window to allow you to add a translation.	    


PSC00156171 : The SmartDataBrowser sort profile is not used with SBO
data-sources
================================================================================
The sort profile saved for a SmartDataBrowser with a SmartBusinessObject as its
data-source is not used upon restart.


PSC00155989 : Changes in how Dynamics Window dimension profiles store
WINDOW-MAXIMIZED
================================================================================
Progress Dynamics windows now store the WINDOW-MAXIMIZED state together with
the previously stored dimensions in the user profile. The state is stored as a
5th entry in the profile value. In previous versions, this state just overwrote
the old profile. If you close a maximized window and no dimensions have been
saved previously, the window still stores "WINDOW-MAXIMIZED" as the only entry.


With the new behavior, a window can store the WINDOW-MAXIMIZED state without
loosing the stored dimensions for the previously saved WINDOW-NORMAL state. The
next time you launch the window, it displays maximized. But, when the
WINDOW-NORMAL state is applied, the window resumes its previously stored size.


PSC00154960 : Dynamic Lookup maintenance window does not destroy its
maintenenance SDO
================================================================================
The Dynamic Lookup maintenance window does not destroy its SDO and associated
Data Logic Procedure

Whenever you open the maintenance window of the dynamic lookup from the dynamic
lookup browse, the system launches a new instance of the maintenance window's
SDO and its associated DLP. However, these objects are not destroyed upon
closing the maintenance window.


PSC00154765 : Error messages for child SDO not returned when CLOB involved
================================================================================
A detailed error message may not be returned to the client while adding a
record to a SmartDataObject under the following circumstances:

- the SDO is running on AppServer
- the SDO contains large object fields
- AutoCommit is false (commit is used to commit multiple updates at once)

The client does receive an "update cancelled" message but should have a
detailed error.  The detailed error is written to the AppServer log file.  

This situation is more likely to occur with an SDO that is part of a
SmartBusinessObject.


PSC00154671 : SmartFrame objects stored with .w in object name may need two
translations
================================================================================
For SmartFrames or SmartWindows that are launched from a static container, the
object name for Title and Page Label translations is resolved from the
procedure:FILE-NAME without path and extension. Therefore, SmartFrame objects
that have the .w extension in their Repository object names might need two
translations, one without the extension for usage in static containers and one
with the extension for dynamic containers.


PSC00151672 : CallerProcedure, CallerObject, and CallerWindow are not set in
createObjects
================================================================================
The Session Manager's launch in Progress Dynamics sets properties like
CallerProcedure, CallerObject, and CallerWindow in the launched container.
These properties are set before the container is initialized and can thus be
used in an initializeObject override. However, they are not intended for use
during the construction (the execution of the main block) of the container. 
The createObjects call is typically done as part of the construction. However,
in previous releases, static non-window containers, like SmartFames and
SmartDataViewers, did call createObjects from initializeObject allowing these
properties to be used also in createObjects. 
Now, createObjects is called during the construction of almost all containers.
If a createObject override uses these properties, it is unlikely to work. Any
logic referring to these properties in createObjects should be moved to an
initializeObject override instead. Moving this logic to initializeObject should
not cause any change in behaviour.


PSC00150794 : Read only SDO tables can be specified to remain NO-LOCKed  during
transaction
================================================================================
The NoLockReadOnlyTables property can hold a comma-separated list of read-only
(non-updatable) tables that should remain NO-LOCKed during the transaction. A
value of 'ALL' means that all read-only tables should remain NO-LOCKed. Note
that read-only tables defined by this property also are excluded from the
optimistic lock check of changes.


PSC00144084 : Error 4054  (.. does not fit..) if ToolbarDrawDirection is
"vertical"
================================================================================
The Dynamics layout manager does not handle toolbars where the
ToolbarDrawDirection is set to 'vertical'.


PSC00140279 : Static browsers/browsers in static windows don't get Repository
column labels
================================================================================
Browsers running in static windows linked to a static SDO on an AppServer will
not get the column-label from the Repository's EntityField. Instead, the
browser gets the column-label from the database schema. This problem also
applies to any static browser.	 


PSC00140138 : A single toolbar cannot switch navigation between SDOs and SBOs
================================================================================
In a paged container where a SDO is the Data-source of a SBO, you cannot use a
single toolbar to navigate both the SDO and the SBO.


PSC00140135 : Loss of data when changing page while browse is in add
================================================================================
When adding a new record in a browser that is part of a tabbed user interface,
the entered data can be lost or appended to the next record in the browser
under the following conditions:

- The browser is the update source for an SDO. 
- The user did not enter all of the required fields in the browser row. 
- The user selects a different page before saving the new record.


PSC00133069 : ADM2 does not support the READ-ONLY attribute on browse columns
================================================================================
The ADM2 does not support setting the READ-ONLY attribute directly on browse
columns as a way to disable fields.  

Field enabling is controlled by the EnabledFields property, that is, you make
columns read-only by removing them from the enabled fields list. 

This is not considered to be a bug. Dynamic browser columns are all read-only
at start up, so it would be very difficult to implement a solution to detect if
the READ-ONLY attribute has been set in initializeObject. 


PSC00130471 : New records can be duplicated when reading new batch if added
while batching
================================================================================
If new records are created that sort higher than the last record in the current
batch, the new record is duplicated when a batch includes the new record. 

To prevent this, either ensure that the user is at the last batch when adding
the new records that will get key values that sort higher than the currently
last record or avoid batching when such records can be created.


PSC00130387 : RowObjUpd.ChangedFields is obsolete
================================================================================
Prior to Version 10.0A, the RowObjUpd.ChangedFields field was used to figure
out which fields to save in an SDO. This is now obsolete and no longer used.
The SDO now figures out which fields to save to the database tables based on a
comparison of the before-image and the changed record. The ChangedFields field
is not used in any logic, except for a call to bufferCollectChanges, which
updates this field. Since it does not capture all changes, this update is not
reliable and the method will be deprecated in the future.


PSC00129126 : Avoid changing Foreign Keys in Web Objects with joined queries
================================================================================
When you use the Detail Wizard to create a Web object that contains a join, do
not make the foreign key field updateable. If you change the value of the
foreign key in a record, the next stateless request might not be able to find
that record.

When this happens, you get an error that the query could not reposition to that
record.

If your application needs the ability to update the value of the foreign key in
a joined query, you must make sure that the list of ROWIDs in the
"CurrentRowids" attribute contains ROWIDs of the newly joined table, instead of
the originally-joined table.


PSC00128303 : Static data objects do not get initial value from Repository
================================================================================
Static SDO proxies (<sdo>_cl) do not get the INITIAL-VALUE from the
Repository's EntityField DefaultValue at run time. The temp-table's
INITIAL-VALUE attribute is a read-only attribute that is compiled into the SDO
temp-table definition from the SDO include.


PSC00124754 : Print Preview and Export to Excel do not work when the data
source is an SBO
================================================================================
Print Preview and Export to Excel options available on various browse	  
toolbars are not supported for visual objects whose data sources are	      
SmartBusinessObjects. These options will do nothing when chosen.


PSC00121785 : Record level transaction hooks must be implemented in the Data
Logic Procedure
================================================================================
You must implement a static SmartDataObject's record level transaction hooks
(create*, write*, and delete*) in the Data Logic Procedure. They will only fire
from the SDO if the SDO does not have a Data Logic Procedure.


PSC00156243 : Help cannot be mapped to static container run from the AppBuilder
================================================================================
It is not possible to map help for a static container that has been run from
the AppBuilder.  The container must be run from the Dynamic Launcher to map
help for it.


PSC00173682 : Progress Dynamics can't find the help file during AppServer
sessions
================================================================================
When the help file is set in the "security control" window, Progress Dynamics
can't find the help file using the help-menu-item in an AppServer session.


PSC00171808 : Translated labels and widgets on same row but different column
================================================================================
When translating static viewers where KeepChildPositions=Yes, translated labels
now use the existing label's width only. Also when translating static viewers,
the label's font, rather than the widget's font, is used to determine the width
of the label.

The translation of simple (LIST-ITEMS) combo-box labels is now supported for
dynamic viewers.

When translating dynamic viewers with KeepChildPositions=Yes, the label moves
to the bottom (back) so that it doesn't overlay any widgets to its left. The
label is not truncated, unless it is longer than the space available.


PSC00168877 : The DataView does not support Dynamics Comments and Auditing
================================================================================
There is no default support for Comments and Auditing when DataViews and
ProDataSets are used.

The following error is returned when attempting to save a comment for a
DataView:
									     
BUFFER-FIELD RowUserProp was not found in buffer <dataset-buffer-name>.(7351)

The Server Interface implementation could define a RowUserPropfield in the
entity temp-table to store the information needed to trigger Auto Comment and
show tick marks in the Dynamics toolbar's Auditing and Comment actions, similar
to how the SDO handles it. Using this field might make it easier to use
existing Repository Manager APIs and reuse existing SDO code. Note that the
Auditing and Comment information is stored with delimiters in the field. This
makes it difficult to use outside of the ADM and difficult to populate. The
population have to be done for each record and will likely affect performance.


PSC00155275 : Info for all users sent to client
================================================================================
When a user attempts to login in a client-AppServer configuration, the entire
list of users is sent from the AppServer back to the client. This may be an
expensive operation when there is a large number of users in the repository. To
reduce this overhead, adding the session property "abbreviatedUserTable" to all
client and AppServer session types and setting its value to "YES" will result
in only the user that is logging in having his data shipped across from the
AppServer, thereby reducing the traffic.


PSC00153575 : Static SmartDataFields (e.g. SmartSelect) cannot be translated.
================================================================================
SmartSelect objects are not presented for translation in the Translation window
at runtime.

The work around is to enter translations of SmartSelects in the Translation
Control tool. The same naming convention as for Lookups is used. You must
specify the Widget Type as 'FILL-IN' and the Widget Name as 'fiLookup' in all
cases. You must enter the Object Name as <viewer-name>:<field-name>.

If the static SmartDataViewer containing the SmartSelect is used in a static
container, you must enter the file name of the viewer, including the extension
(.w), in the Object Name. If the viewer is used in a dynamic container, you
must enter the object name of the viewer, without any extension.

This is an example based on a viewer for the Warehouse table using a
SmartSelect for the 'State' field. The file name of the viewer is
'warehousesdv.w'.

Translation for use in a static container:

Object Name: warehousesdv.w:state
Widget Type: Fill In
Widget Name: fiLookup

Translation for use in a dynamic container:

Object Name: warehousesdv:state
Widget Type: Fill In
Widget Name: fiLookup


PSC00201988 : Error: The Root node code must be specified. (AF:1) when creating
Dyn TreeViews
================================================================================
When entering data in the "Dynamic TreeView Builder" tool, you must enter the
"Object filename" value first. If you do not enter the Object filename first,
you see the "Root node code must be specified. (AF:1)" error upon saving the
data.


PSC00200646 : Error 7452 in Dynamics Dataset Export Filter
================================================================================
Customers using European numeric settings might see the 7452 error when
pressing the filter button on the Dataset Export screen.


PSC00155024 : Cascading security allocations does not work for Data Security
================================================================================
The option to cascade security allocations from a profile user does not   
work for Data security.


PSC00151136 : RTB: Problems when dyn object and super proc in different module
================================================================================
When modifying a dynamic object where the dynamic object and its super
procedure were created in different product modules, the following error may
occur:

The product module <product-module1> and the product module <product-module2>
must be the same. (AF:110)


PSC00146842 : Error 560 Generating Objects From SDO
================================================================================
Error 560 (Entry outside the range of list) is raised when the Object Generator
is used to create dynamic objects from a prebuilt SDO when the SDO has been
created by the Object Generator, and has subsequently had other tables manually
added, and the product module has sublevels in the path.


PSC00146243 : Client cache viewer tool returns errors
================================================================================
The client cache viewer tool no longer works when run against a current version
of the Repository API.


PSC00143666 : Copy-Paste in DynView is not keeping all the attributes of the
widgets
================================================================================
When copying widgets from a DynView to another DynView, some widget attribute
values are missed. For example, when a fill-in is copied, the values of the
ShowPopup and Label attributes are missed in the target DynView. This happens
for all attributes that are read from the Repository.


PSC00140156 : DataFields cut/copied then pasted are associated with RowObject
================================================================================
There is an issue when you cut or copy DataFields from one dynamic viewer and
then paste them to another dynamic viewer built from the same SDO. Until you
save and reopen the second viewer, the AppBuilder shows the new fields as being
associated with the RowObject table instead of their actual database table.


PSC00131772 : Toolbar object modifications are not updated in the Toolbar
================================================================================
011A90108
Toolbar data are cached on the client as soon as they have been read once    
from the server, so when actions, bands and/or toolbars are changed in the   
Toolbar and menu designer these changes will not always be reflected in new 
instances of toolbars.							       
       
Running the Dynamic Launcher and checking the 'Destroy ADM super-procedures' 
option will ensure that toolbar data are refreshed. The other option is to   
restart the session.						    


PSC00128502 : Fields hidden on DynView master layout in design mode if custom
layout exists
================================================================================
If a field on a master layout has its HIDDEN attribute set to TRUE, the viewer
typically displays the field in design mode. However, if a customized layout is
made for the viewer, the viewer does not display the hidden field when the
viewer reopens. This is inconsistent with the normal behavior for displaying
hidden fields in master layouts. If you need to modify a hidden field in this
situation, use the ROM tool. Do not modify the hidden field by using the 'List
Objects' button to bring up the property sheet. Doing so removes the field
instance.


PSC00125407 : scm_checks_on in Security Control is not supported
================================================================================
In Security Control, there is a toggle that switches on and off checks for the
use of an SCM tool. The use of this setting is not yet implemented in all the
places where it is relevant to check for this setting. SCM functionality is
always enabled when the SCM tool (Roundtable) is in use with Progress Dynamics.


PSC00247292 : Creating a .zip file on removable media from Visual Translator
causes errors
================================================================================
Creating .zip file on removable media from Visual Translator causes the
following errors:

Error occurred while accessing component property/method: MultiVolumeControl.
Out of present range.

Error code: 0x8002000a Zip adetran/common/_zipmgr.w (5890) Zip: Couldn't open
to write. (15).

Note:  Creating a .zip file on non-removable storage functions properly.


PSC00150235 : Changing the TranMan Language combo may cause error (132)
================================================================================
Changing the selected language on the TranMan Data Tab combo does not display
the correct translations after using the 'View', 'Sort' option from the pull
down Menu.

Double clicking on some rows might give the following error:
** This Translation already exists with Sequence number <number> Instance
Number <number> Language  Name "<language>". (132)


PSC00181371 : Two undo/reset buttons on the Standardtoolbar
================================================================================
The new UndoChange toolbar action is not supported in Dynamics Web.

By default, UndoChange replaces the Reset action in shipped toolbars and
Tableio bands. When these toobars and bands are realized in the Web, the Reset
button and menu item remain and function correctly. However, the UndoChange
action may also be realized at runtime as a non-functioning button and menu
item, labeled "Undo 1 (CTRL-Z)".

In order to suppress the UndoChange button and menu item, the UndoChange action
can be set to Hidden, or added to the HiddenActions property, for the toolbar.
For additional information, please see the note for the new UndoChange action
under GUIRENDR / SmartToolbar in this document.


PSC00144996 : The compileAll option in WebTools has a limitation of URL length
of 4096 chars
================================================================================
The compileAll option on AppManager in WebTools has a limitation of URL length
being more than 4096 chars, depending of what web browser is being used. Try to
limit the size of the compiles, number of files if you run into this problem.


PSC00139229 : HTML after WSTag not sent if WSTag runs another WebSpeed object
================================================================================
If a SpeedScript file contains a WSTag tag that runs another WebSpeed
object, the remaining HTML after the WSTag tag is not sent to the Web
browser.


PSC00130586 : WebSpeed detail program called from a WebSpeed report program
hangs
================================================================================
A WebSpeed detail program called from a WebSpeed report program might hang when
the Add button is used a second time or the Delete button is used. If the
detail program is used separately from the report program, the problem does not
occur.



b. Adapter for SonicESB

PSC00240333 : Connnection string limitation for session-managed native ESB
Adapter
================================================================================
The combined length of the connection string (composed of  a user-id, password,
and information fields) must not exceed 30,000 non-Unicode characters when
connecting to an AppServer. Exceeding the string length causes an AppServer
exception.


PSC00220618 : Agents remain locked when ESB Adapter returns a Fault in Sonic
Workbench
================================================================================
When using the OpenEdge Adapter for Sonic ESB with a session-free AppServer and
persistent procedures, it is important that you release the persistent
procedure when your ESB process completes, to prevent having a locked agent. 

When the adapter returns a fault, you must ensure the Release operation is done
in your Fault process. This requires you to keep track of your process ID and
have access to it in your Fault process.

In the Progress Developer Studio for OpenEdge/Sonic Workbench development
environment, Sonic intercepts all fault returns so that it can display the
result.  Consequently, Fault processes are never run. Setting the Command
Parameter ESB Fault Return Mode to "Continue Process with Fault"  discards the
original message where your Procedure ID is stored, so this is not a viable
solution.

To free up locked agents on the AppServer, you must restart your development
container.

Using Persistent Procedures within Sonic ESB processes is discouraged because
it greatly complicates the handling of Faults and makes your session-free
AppServer operate no differently than a session-managed AppServer.



c. AdminServer

PSC00323311 : Failure to remove the OpenEdge AdminService from Windows Services
during an uninstall
================================================================================
During a 64-bit OpenEdge uninstall, the OpenEdge AdminService will not be
removed if the AdminService is stopped. 

Workaround:
Be sure the AdminService is running before you start an OpenEdge 64-bit
uninstall. The installer checks the running status of AdminService. If the
OpenEdge AdminService is running, the installer stops it, removes it from
Windows Services, deletes all registry entries, and then completes the
uninstall.


PSC00322130 : Admin service fails to start from PROENV
================================================================================
Admin service does not start or work as expected when you install OpenEdge with
more than one space in the install (DLC) or Work (WRK) directories.  
When the Admin service is started from PROENV, it displays the following
message:
"Could not find or load main class
com.progress.chimera.adminserver.AdminServerType".

Effected version: All OpenEdge versions



d. AppServer

PSC00229780 : Startup time of AppServer broker increases when SSL is enabled
(Linux and UNIX)
================================================================================
After upgrading to OpenEdge Appserver V11, the AppServer broker's startup time
might increase if SSL is enabled.  This happens if /dev/random is not populated
with random data.  The SSL libraries used by the AppServer broker require
several kilobytes of random data to properly secure SSL connections to the
broker. 

To resolve the issue, ensure that /dev/random is populated with enough random
data.  There are two possible solutions:

- Move /dev/random to /dev/random_bak, and then add a simlink from /dev/random
to /dev/urandom.  This makes /dev/random reference /dev/urandom.  Note that
/dev/urandom is less secure.

-  Install and run rngd, the random number generator daemon.  It increases the
entropy pool used /dev/random to provide random data.


PSC00244975 : Support for Actional is removed
================================================================================
Support for Progress Actional (including all Actional interceptors for
OpenEdge), which was first introduced in OpenEdge 10.2B, is removed from
OpenEdge Release 11.1.



e. DATASERVER

PSC00305085 : Establishing backward compatibility to older server versions
================================================================================
Username/Password encryption feature was implemented in the OE 11.4.0 release
for MS SQL Server and Oracle DataServers.  With this new feature, users can
pass encrypted usernames and passwords to the server.  Encryption of
credentials have compatibility with versions of the DataServer clients and
servers going forward, but a pre-11.4.0 DataServer Server has no support for
the encrypted credentials.  When a DataServer client tries to connect to an
earlier version of the DataServer Server, it fails to decrypt the credentials,
and a connection failure results. 

Version 11.4 of both the MS SQL Server and Oracle DataServers continue to be
compatible only with their own 11.4 clients.  However in OpenEdge 11.5 release,
MSS and Oracle DataServer client has been improved to restore the broken server
compatibility which now restricts the server incompatibility to a specific
range. Connectivity with encryption in the 11.5 MSS DataServer is now only
incompatible with releases between 11.2.x to 11.3.x.  Connectivity with
encryption in the 11.5 Oracle DataServer is now only incompatible with 11.0.x
to 11.3.x releases.  

On the contrary, the DataServer client will also be capable of making a
compatible connection to a comparable DataServer server. For instance, if a MSS
DataServer client tries to connect to a release before 11.2.x version, it will
result in a successful connection with un-encrypted username/password. However,
if a MSS DataServer client tries to connect to a pre-11.4 MSS DataServer Server
in the range of 11.2.x and 11.3.x, the MSS DataServer client remains
incompatible with these versions. That is, DataServer Server fails to decrypt
the credentials and a connection failure results. 

To establish backward compatibility with older versions in the specified range
of incompatible servers, 11.2.x and 11.3.x of the MSS DataServer servers and
11.0.x - 11.3.x of the Oracle DataServer , use the connection-time switch
"-znoencrypt".	While this switch re-establishes backward compatibility it also
disables the encryption feature for that connection.


PSC00316718 : Oracle DataServer for coexistence of 32bit OE/64bit OE on 64bit
m/c
================================================================================
If a 64-bit oracle client and a 32-bit OpenEdge instance coexists with a 64 bit
OpenEdge instance on a Windows 64-bit machine
 and if the 32-Bit OpenEdge utilizes the Oracle DatServer and configures its
Oracle environment to connect to a 64-bit Oracle client library,
 the user gets the following error message:"Unable to load shared
library.(14945) error".


If a 32-bit oracle client and a 32-bit OpenEdge instance coexists with a 64 bit
OpenEdge instance on a Windows 64-bit machine
 and if the 64-Bit OpenEdge utilizes the Oracle DatServer and configures its
Oracle environment to connect to a 32-bit Oracle client library,
 the user gets the following error message:"Unable to load shared
library.(14945) error".


PSC00215517 : Techniques to load .d file when table has non-updatable column on
MSSQLServer
================================================================================
In MSS DataServers, there is a restriction to a load operation from a .d file
when the table has non-updatable columns (i.e. columns on MS SQL server are of
type 'identity' or 'timestamp' or 'rowguid').
You can work-around this restriction by following one of the two options
described below.

Option 1:-
Use dump/load tools of the foreign data source instead of data from a .d file
to load your foreign table.

Note: This is the only way to retain the original values from non-updatable
columns.

Option 2:-
If the user wants newly generated values for non-updatable columns stored along
side updatable fields from the given '.d' file, write an ABL program to read
data from the .d file into a temp table and then skip non-updatable fields
while writing the temp table records to the foreign table.

Sample ABL code provided below to perform this task.

Conside a table named "test" on SQL Server side with the sturcture as,

TABLE [test](
[fld1] [int] IDENTITY(1,1) NOT NULL,
[fld2] [varchar](50) NULL,
[fld3] [varchar](50) NULL
)

****** sample ABL code ******

/* define temp table with the name Temptbl for table test */
define temp-table Temptbl like test.

/* pouplate temp-table Temptbl from the records in the .d file name test.d */
INPUT FROM test.d.
REPEAT:
CREATE Temptbl.
IMPORT Temptbl.
/* create a record in the foreign DB */
CREATE test.
BUFFER-COPY Temptbl EXCEPT fld1 TO test.
END.
INPUT CLOSE.

*****************************


PSC00315675 : Establishing ROWID backward compatibility
================================================================================
In the OpenEdge 11.5 release, changes were made to ROWID memory layout area
copied into the record buffer for MSS DataServer. With this new enhancement,
the ROWID is stripped to be shorter in size. The changes were made to both
self-service and progress networking mode of DataServer configuration. The
reduced storage size of ROWID in the record buffer now enables MSS DataServer
to use reduced network bandwidth for every record transferred using the
network. However, if you have generated the ROWID prior to the 11.5 release and
are storing it in your database or to some other permanent location and then
try to retrieve the stored ROWID using 11.5, the application may fail or
display undefined behavior.

To establish backward compatibility with pre-11.5 ROWID, use the
connection-time switch "-Dsrv PRGRS_ROWID_VER,0" when using dataservers in
OpenEdge 11.5 FCS or above.  Allowed values for the switch PRGRS_ROWID_VER are
0 and 1 with default set to 1. This switch re-establishes backward
compatibility with the stored ROWID generated with older releases by retaining
the old format for ROWID. 

Additionally, the existing connection switch -Dsrv ZPRGRS_RECID_BUF_SIZE has
been modified to accept a RECID buffer size value as low as 13 starting in
OpenEdge 11.5 when PRGRS_ROWID_VER is set to 1.  In previous versions of
OpenEdge and when the PRGRS_ROWID_VER is set to 0 in OpenEdge 11.5 or higher,
the minimum size for the -Dsrv switch ZPRGRS_RECID_BUF_SIZE continues to be 52.


To set an optimal size for ZPRGRS_RECID_BUF_SIZE for a particular schema image
from MS SQL Server, it is recommended that you execute the following script
while connected to the MSS logical database of your schema holder.  

/****************************************************/
DEFINE VAR tot_recid_buf_siz AS INT INIT 0.
DEFINE VAR min_recid_buf_siz AS INT INIT 0.
DEFINE VAR headr_siz AS INT INIT 9.
DEFINE VAR ofst AS INT INIT 2.	/* 2 byte offset */
DEFINE VAR unknw AS INT INIT 1. /* 1 byte for UNKNOWN */
DEFINE VAR surrogate_key_size AS INT INIT 8.
DEFINE VAR largest_rowid_index AS CHARACTER.
DEFINE VAR filname AS CHARACTER.
DEFINE VARIABLE prgsrowidunq AS LOGICAL INIT NO.
DEFINE VAR numcomp AS INT.

/* variables for frame */
DEFINE VARIABLE min_recid_siz AS CHARACTER LABEL "RECID_SIZE" NO-UNDO.
DEFINE VARIABLE logicaldb AS CHARACTER LABEL "Logical Db" NO-UNDO.
DEFINE VARIABLE rowi_index AS CHARACTER LABEL "LargestROWIDIndex" NO-UNDO.
DEFINE VARIABLE tabname AS CHARACTER LABEL "TABLE" NO-UNDO.
DEFINE VARIABLE hasprgsrecidunq AS LOGICAL LABEL "PROGRESS RECID UNQIUE"
NO-UNDO.

DEFINE FRAME buf-size	
    min_recid_siz AT ROW 1  COLUMN 1
    logicaldb AT ROW 1 COLUMN 20
    rowi_index AT ROW 1  COLUMN 34
    tabname AT ROW 1 COLUMN 60
    hasprgsrecidunq AT ROW 1 COLUMN 80
    WITH  SIZE 100 by 100 TITLE "-Dsrv ZPRGRS_RECID_BUF_SIZE parameter can be
set no smaller than:" 
    USE-TEXT.

FOR EACH _db WHERE _db-type = 'MSS' WITH FRAME buf-size:
FOR EACH _file OF _db WHERE _hidden = NO:
     
    IF _fil-misc1[1] > 0 THEN DO: /* PROGRESS_RECID */
	numcomp = 1.
	tot_recid_buf_siz = headr_siz + 
			    (numcomp + 1) * ofst + 
			    surrogate_key_size.

	IF tot_recid_buf_siz > min_recid_buf_siz THEN DO:
	   min_recid_buf_siz = tot_recid_buf_siz.
	   largest_rowid_index = "PROGRESS_RECID".
	   filname = _file-name.
	END.
    END.
    ELSE DO:			 /* Other than PROGRESS_RECID */
	FOR EACH _index OF _file WHERE _idx-num = _fil-misc1[2]:
	      
	      ASSIGN numcomp = _num-comp.
	      IF INDEX(_I-misc2[1],"v") <> 0 THEN DO:
		 ASSIGN numcomp = _num-comp + 1 /*PROGRESS_RECID_UNIQUE */
		     tot_recid_buf_siz = tot_recid_buf_siz +
surrogate_key_size.
	      END.
			
	      ASSIGN tot_recid_buf_siz = headr_siz + 
					 numcomp * unknw + 
					 (numcomp + 1) * ofst. 

	    FOR EACH _index-field OF _index:
		FIND _field WHERE RECID (_field) = _index-field._field-recid.
		   tot_recid_buf_siz = tot_recid_buf_siz + _fld-misc1[3].
	    END.

	   IF tot_recid_buf_siz > min_recid_buf_siz THEN DO:
	      min_recid_buf_siz = tot_recid_buf_siz.
	      largest_rowid_index = _index-name.
	      filname = _file-name.
	      IF INDEX(_I-misc2[1],"v") <> 0 THEN
		  prgsrowidunq = YES.
	   END.
	END.
    END.

END.

DISP   STRING (min_recid_buf_siz) AT ROW 1 COLUMN 11  
       _db._db-name AT ROW 1 COLUMN 20 NO-LABEL
       largest_rowid_index FORMAT "x(30)" AT ROW 1 COLUMN 34 NO-LABEL
       filname FORMAT "x(20)" AT ROW 1 COLUMN 60 NO-LABEL
       prgsrowidunq  AT ROW 1 COLUMN 80 NO-LABEL.


END.
/****************************************************/


PSC00246724 : R-code compiled in OpenEdge 11 before and after this fix must be
recompiled
================================================================================
32-bit and 64-bit datasever r-code compiled in OpenEdge 11.2.0 is incompatible
with OE 11 releases before and after it due to a change of data stored in
r-code.  Corrections are required for all r-code compiled against the
DataServer for MS SQL Server in releases other than 11.2.0.  Release 11.2.0
r-code is only compatible with its own run-time.  Moving Release 11.2.0 MSS
DataServer r-code to later releases (11.2.1+ or 11.3+) requires a recompile
even if you recompiled once already in moving to 11.2.0.


PSC00246559 : Recompile r-code in 11.2.1/11.3.0 from OpenEdge 11.2 or previous
V11 versions
================================================================================
32-bit and 64-bit platform r-code compiled on OpenEdge 11.2 (or previous
versions) must be recompiled at least once before being executed on OpenEdge
11.2.1 or later versions.  Corrections were required for all r-code compiled
against the DataServer for MS SQL Server due to 64-bit alignment issues
associated with stored r-code that affect run-time capabilities on both 32 and
64 bit platforms.


PSC00242399 : Existing MSS logical schema requires an update to enable certain
LOB operations
================================================================================
In MS SQL DataServer, partial LOB operations with non-native MS SQL Server
drivers had resulted in an error. The schema image has been modified to include
additional information that allows for important LOB data type distinctions in
the non-native drivers. As a result, a newly created logical schema with
re-pulled server definitions will no longer experience errors when non-native
drivers are processing DataServer LOB operations. If you want to successfully
use an existing logical schema with non-native driver connections, you must
first run the attached, upd_sqlcols_buf.p, script and then re-pull your table
definitions with LOB data types from the server into the schema holder
database.


PSC00223191 : ZPRGRS_RECID_BUF_SIZE Option minimum value changed from 44 to 52
================================================================================
The minimum RECID buffer size has changed to 52 (from 44).

The ZPRGRS_RECID_BUF_SIZE option allows the RECID buffer size to be configured
to a customized size for the DataServer session.

NOTE: DO NOT INCREASE THIS VALUE IF THERE IS NO REQUIREMENT FOR IT.  INCREASED
BUFFER SIZES CAN HAVE A NEGATIVE EFFECT ON NETWORK PERFORMANCE RUNNING
DATASERVER'S CLIENT/SERVER.

This syntax is for setting the buffer size for the RECID area,

-Dsrv ZPRGRS_RECID_BUF_SIZE,nnnn
    (where nnnn is the new size of the area in bytes. The range limits for nnnn
are   inclusive of values between 52 to 1024.)


PSC00218590 : SQLError not getting message with SNAC-10 driver.
================================================================================
New trigger solution (CR#OE00178470) generates 'PSC-init' and 'PSC-end'
messages on trigger execution. Modified DataServer code gets these messages
using SQLFetch()- SQLError - api calls for 2 times. Observed that SNAC-10
driver is not returning the PSC-end message as part of the 2nd time SQLFetch()
with SQLError()- API calls.

This is a 3rd party SNAC-10 driver issue. Confirmed the same by using a sample
ODBC program.

Note: This behavior has NO impact on DataServer functionality. 


PSC00251163 : Recompile r-code in 11.2.1/11.3.0 from OpenEdge 11.2 or previous
versions
================================================================================
32-bit and 64-bit platform r-code compiled on OpenEdge 11.2 (or previous
versions) must be recompiled at least once before being executed on OpenEdge
11.2.1 or later versions.  Corrections were required due to the byte ordering
of data stored in r-code compiled against any DataServer (ODBC, MSS, or
ORACLE).  The byte-ordering of r-code storage and run-time retrieval affects
run-time capabilities on both Little Endian (LE) and Big Endian (BE) machine
types.



f. DB

PSC00317839 : Dropping support for clusters on Windows 2003 R2
================================================================================
Starting with OpenEdge 11.5.0, cluster failover for the RDBMS on Windows 2003
R2 is not supported.


PSC00220715 : dbutil.bat supports nine command line parameters
================================================================================
dbutil.bat supports 9 command line parameters.	Use proutil.bat if your command
line requires more than 9 parameters.  proutil.bat supports 27 parameters.  


PSC00220401 : An encryption-enabled, manual start db cannot be started by
failover clusters
================================================================================
You cannot start a database enabled for failover clusters with your operating
system cluster resource manager if it is also enabled for transparent data
encryption and configured for manual start.

Failover cluster and encryption-enabled databases must be configured for
autostart to be started by the cluster resource manager.

If you attempt to start an encryption-enabled database configured for manual
start with the operating system cluster resource manager, the actual startup
fails, 
but the cluster resource manager may incorrectly report that the database has
been started.  


PSC00226402 : Promon output format is changed to include additional fields
================================================================================
In Release 11.0.0, new columns are inserted into promon reports to provide
information on new fields, for example domains, tenants, and partitions.  Refer
to "OpenEdge Data Management:  Database Administration" for more details. 
Understanding the change in column location is particularly important if you
have scripts that parse promon output and act on the parsed results.


PSC00299582 : Utilities performing index operations on a UTF-8 database
requires -cpinternal UTF-8
================================================================================
Utilities performing index key operations within PROUTIL require you to include
"-cpinternal UTF-8" on the command line when operating on a UTF-8 database. If
PROUTIL detects that your database is a UTF-8 database and -cpinternal UTF-8 is
not specified, a message is generated and the utility exits.  

The utilities are:  LOAD, IDXACTIVATE, IDXFIX, IDXCHECK, IDXBUILD, CONV1011,
PARTITIONMANAGE SPLIT, PARTITIONMANAGE MERGE, PARTITIONMANAGE TRUNCATE, and
TPIDXBUILD.


PSC00256028 : Database log messages contain GMT timestamps
================================================================================
During regular execution, when OpenEdge processes write to the database log
file (.lg) the timestamp header of the message shows the time in local time
format. This header with local time information includes the offset of the
local time from Greenwich Mean Time (GMT).

For example: "[2013/04/25@11:00:34.123-0400]" which shows that the time is 4
hours offset from GMT.

On UNIX systems, when OpenEdge processes field exceptions (either internal
fatal errors or signals from other processes), messages may be written to the
database log (.lg) file from within the process' Signal Handler code. These
messages, when written from the Signal Handler, show a timestamp header in
Greenwich Mean Time (GMT) format.

For example: "[2013/04/25@15:01:07.000+0000]" which shows that the time is
actual GMT with 0 hours offset.

In addition, the time information written from the process' Signal Handler does
not show millisecond values.

This change in timestamp formatting allows OpenEdge to avoid calling certain
UNIX system functions which can cause a process to hang or not properly
terminate if called from within the Signal Handler code.



g. Doc

PSC00240336 : Problems with context-sensitve help in Progress Developer Studio
for OpenEdge
================================================================================
When launching context-sensitive help in Eclipse, Help Not Found errors
sometime occur even when help is available. The error message is, "The context
help for this user interface element could not be found."
 
If you get a Help Not Found error after pressing F1, or clicking the help icon
in the UI, try one of the following:

1. Click on some other element in the UI and press F1, or click the help icon
again.

2. Click on "Search for . . ." link in the help pane. A list of relevant topics
appears.


PSC00236766 : Infragistics assembly and namespace changes in version 2011.1
================================================================================
With support for Infragistics Version 2011.1, several of the assemblies, DLL's,
and corresponding namespaces have been changed in OpenEdge Release 11.0.

As a result, you will need to change any existing code that uses the affected
assemblies.

To see a list of the changes:

1. Go to the following URL: 
http://help.infragistics.com/NetAdvantage/WinForms/2011.1/CLR2.0/html/Win_Deplo
yment_Overview.html.

2. Select the link, "Known Issues and Breaking Changes".

3. Select the link, "Breaking Changes in 2011 Volume 1".


PSC00183192 : Search of PDF files for UNIX Platforms
================================================================================
On UNIX platforms, the search index is not automatically attached to the
documentation PDF files.  To attach the index file so that you will have search
capabilities, follow these steps:
 1. From the Adobe Acrobat Reader, click on the Search icon.  The Adobe Acrobat
Search dialog box appears.
 2. In the Adobe Acrobat Search dialog box, click on the Index button and
choose Add.
 3. From the drop down list of files, select the oeidx.pdx file and choose OK.


PSC00183191 : Non-existing examples mentioned in online help for CSSPIN
================================================================================
The CSSpin Active X Control Help file mentions the following example:
   Example Location 
   Project File Form/Basic File
   SPINDEMO.VBP SPINDEMO.FRM
These example files do not exist.


PSC00183184 : Online Help unavailable for editor's dialog boxes
================================================================================
Online help for dialog boxes in the Procedure Editor is not available. The Help
buttons on the dialog boxes do not work because the color-coding editor control
only supports MicrosoftRTM WinHelp (.hlp) files and not MicrosoftRTM  HTML
(.chm) files.


PSC00183183 : Microsoft Security Update may affect remote access of Online Help
================================================================================
If you receive the following error when accessing the help remotely: 
"Action cancelled Internet Explorer was unable to link the web page you
requested. The page might be temporarily unavailable", see the Microsoft
Knowledge Base article titled: "Certain Web sites and HTML Help features may
not work after you install security update 896358 or security update 890175"
located at http://support.microsoft.com/kb/892675/. The article describes the
reasons for the issue and provides workarounds.


PSC00183187 : Accessing online help for CSSPIN ActiveX Control
================================================================================
If you press F1 to get help on the CSSPIN ActiveX Control, you will get an
error indicating it cannot find the help file. To access the help for the
CSSPIN ActiveX Control, do the following:
 1. Select Start->Program->OpenEdge->Help. The OpenEdge Online Help file
appears.
 2. In the left pane, double-click the ActiveX Control Help folder to expand
it.  Then, select the CSSpin Control help topic.



h. GUI

PSC00244792 : Behavior changes when cropping and stretching images
================================================================================
In OpenEdge releases earlier than 11.3, cropping images (using the FROM option
of the Image phrase, or the optional parameters of the LOAD-IMAGE ( ) method)
and stretching images (using the STRETCH-TO-FIT attribute of the IMAGE widget)
did not always work as specified. In many cases, the cropping and stretching
were ignored or were performed incorrectly. These issues are fixed in OpenEdge
Release 11.3. Applications which use these features may display images
differently than in earlier releases.


PSC00238681 : VideoSoft IndexTab control does not display properly on certain
platforms
================================================================================
The VideoSoft vsIndexTab OCX does not display at runtime on certain platforms
(for example, Windows 7 64-bit).  This is a third-party issue, and occurs
whether developing in Visual Studio 2010 or with OpenEdge.


PSC00237832 : Crystal Reports XI causes crash in some environments
================================================================================
Adding an instance of the Crystal Reports XI ActiveX Report Viewer to a window
causes a crash on certain platforms (such as Windows 7 or Windows 2008 Server)
and with certain Report Viewer versions (namely V11.5 or later 11.X versions). 
This is a third-party issue, and occurs whether developing in Visual Studio
2010 or with OpenEdge.


PSC00317032 : Browse SCROLL-NOTIFY event may fire more often
================================================================================
Starting in OpenEdge Release 11.5, the browse widget's SCROLL-NOTIFY event may
fire in cases where it did not fire in previous releases. If the SCROLL-NOTIFY
events cause an issue, use the new SCROLL-VERTICAL and SCROLL-HORIZONTAL events
instead. SCROLL-VERTICAL and SCROLL-HORIZONTAL are more reliable and consistent
than SCROLL-NOTIFY.


PSC00258689 : AppBuilder in Developer Studio does not support SHIFT in
accelerators
================================================================================
The ABL does not support SHIFT as second modifier for modified single key
accelerators. Developer Studio bindings defined with ALT-SHIFT-X or
CTRL-SHIFT-X (The "x" refers to any printable char.) will thus not work when
the focus is in the design window. Progress will send CTRL-X or ALT-X to
Eclipse ignoring the SHIFT and fire corresponding bindings if defined. This
means that the ABL UI Designer do not respond to CTRL-SHIFT-W  (Close all) and
CTRL-SHIFT-S (save all) in the Developer Studio default Theme. 



i. Install

PSC00322913 : PSTIMER.OCX is not registered if an older OpenEdge version is
installed
================================================================================
If you have an existing OpenEdge version prior to 11.5 on your machine, and
then if you install OpenEdge 11.5, PSTIMER.OCX is not registered. Your older
OpenEdge version might continue to work with PSTIMER, but 11.5 will fail. To
address this, start an 11.5 proenv session, and run:
regsvr32 %DLC%\bin\system\pstimer.ocx


PSC00322063 : 32-bit client fails to load COM objects on a Win-64 machine
================================================================================
When you install 64-bit OpenEdge on a Win-64 machine that already has a 32-bit
OpenEdge (version before 11.5) installed, the existing 32-bit installation
generates the following error message when the client tries to load a COM
object:
  Error occurred  while creating CONTROL-FRAME: .
  0x800700c1
  Error code: 0x800700c1 (5898)
To resolve this issue, the following command from the 32-bit versionÆs proenv
prompt:
  regsvr32 %DLC%\bin\prox.dll


PSC00200154 : Sonic container startup shortcut requires quotes for directories
with spaces
================================================================================
If you install OpenEdge into a directory with a space in the name (e.g.
C:\Program Files\OpenEdge), the shortcut to start up the sonic container does
not function properly.	You can fix the problem by editing the shortcut and
enclosing the Target: and Start in: fields in double quotes.


PSC00322573 : Install to a logical disk fails when there are spaces in
pathnames
================================================================================
For few Dell machines, if you install an OpenEdge Product with spaces in the
pathname on a logical disk which is a extended partition provided by Dell
(usually a D drive) then the following issues show up:
		
		1. DLC and WRKDIR do not get set correctly in the proenv script
		2. The pasoe folder does not get created in %DLC%\servers
directory
		
It works perfectly fine if you install with spaces in pathnames on a newly
created logical disk or a partitioned drive. 


PSC00318269 : Add Components via Shortcut does not work as expected
================================================================================
Releases Found in: 11.3.0, 11.4.0, 11.5.0

Issue:
When you add components via the Add Components Shortcut, the wizard does not
allow you to select the components to be added, but when you click the Finish
button, an error message is displayed and the components are not added to the
existing installation.

Workaround:
To add components to an existing OpenEdge installation, rerun the installation
wizard, add the existing installed products by entering or importing the
control codes, select the Custom install option, select the components already
installed and any additional components to be added, and then follow the rest
of the installation process.


PSC00312355 : Install of Pacific Production Application Server for OpenEdge
over Pacific Development Application Server for OpenEdge removes instance
================================================================================
If you install Pacific Production Application Server for OpenEdge over an
existing Pacific Development Application Server for OpenEdge product, the
instances.windows file is removed. You should backup the instances.windows file
before installing Pacific Production Application Server for OpenEdge over an
existing Pacific Development Application Server for OpenEdge to avoid it.


PSC00196833 : .Net Framework not installed with unknown default language
================================================================================
Progress Developer Studio and OpenEdge Advanced UI Controls have a dependency
on the Microsoft .NET Framework v4.0.

The OpenEdge installation media includes the English version of the Microsoft
.NET Framework, and the OpenEdge installation process will automatically
install the framework if it is not already your system, provided that your
system's locale is set to English.  

If the locale on your system is set to something other than English and the
.NET Framework 4.0 for your locale is not already installed, then Progress
Developer Studio and OpenEdge Advanced UI Controls do not install properly. 
OpenEdge will not install the English version of the .NET Framework when the
system locale is not English, and the Advanced UI controls will not install
without the .NET Framework installed.

To work around this problem, install the Microsoft .NET Framework v4.0 for your
locale, prior to installing OpenEdge.  

To download different languages of the .NET Framework 4.0 as well as the
Windows 64-bit version:
  - Login to http://www.progress.com/esd
  - Choose "Progress OpenEdge Deployment Components"
  - Choose "Microsoft .NET Framework" download page


PSC00196736 : Unknown Publisher message with a Netsetup Install
================================================================================
After performing a Netsetup install on Windows the user may see an Unknown
Publisher message when running any OpenEdge .EXE files from a network drive. To
resolve this issue, add the network drive share to the client's trusted zone.

To add the network drive to your trusted zone:

1. Open the Internet Options Dialog Box from an Internet Explorer session.
2. Select the Security Tab.
3. Select the Local Intranet icon from the zones shown.
4. Click the Sites command button, which opens a Local Intranet Dialog Box.
5. Click the Advanced command button, which opens a dialog box where you 
add and remove websites from your intranet.
6. Add \\servername\ to the list of websites. Click Close, then OK to return to
the main Internet Options Dialog Box.

You may have to reboot the client for this to take effect.


PSC00216026 : The WebClient One-Click install fails as a Non-Admin User
================================================================================
The WebClient One-Click install (OCI) (over-the-web install) fails when run by
a non-admin on a system that does not already have the Installshield Setup
Player installed as an Add-On.	For this to work, the add-on must already be
installed/registered by an Administrator. Running the WebClient One-Click
install as Administrator just one time will get the Setup Player installed.
After this is done the WebClient One-Click install can be run as a
Non-Administrator. This issue only occurs when installing Over-the-Web. This
issue does not occur when running the WebClient installation directly via the
setup.exe file.


PSC00299643 : Personal install of WebClient fails with Internet Explorer
================================================================================
When you do a web-based install of WebClient using Internet Explorer, you get
the following error message:  

---------------------------
Feature transfer error
---------------------------
Feature:	Disk<1>
Component:	<Disk1>Disk1 Files(1)
File:		C:\Users\User.W764\AppData\Roaming\InstallShield Installation
Information\{59728F20-15EE-4C15-BB4F-780CDF156ADA}\
Error:		Access is denied.

This is a third party limitation. The only workaround is to use a cdimage
install of WebClient instead of the web-based install.


PSC00281096 : Cannot install WebClient using 64-bit Internet Explorer
================================================================================
The web-based WebClient installation fails if you use 64-bit Internet Explorer
(IE).

This is a third-party limitation. The workaround is to either use 32-bit IE or
use the cdimage install.


PSC00255748 : WebClient 11.2.x service pack fails to install on top of
WebClient 11.2.0
================================================================================
The WebClient 11.2.x service pack fails to install on top of WebClient 11.2.0
for a non-admin user. It is a problem in the WebClient 11.2.0 installation and
cannot be resolved in this service pack. To install the WebClient 11.2.x
service pack properly, you must uninstall the WebClient 11.2.0 and install the
WebClient 11.2.x service pack again.


PSC00238578 : Slow Webclient installation on the Windows 2003 Server
================================================================================
While installing WebClient on the Windows 2003 Server, the progress bar might
reach 90% and then stop for more than 20 minutes before completing the
installation. This happens for the non-administrator group users.



j. LANG

PSC00183853 : INT64 ActiveX support requires oleaut32.dll version 5.1.2600.2180
or later
================================================================================
To support the INT64 data type with ActiveX controls or ActiveX Automation
objects, C:\windows\system32\oleaut32.dll must be version 5.1.2600.2180 or
later. If your application uses an earlier version of oleaut32.dll and a
parameter of INT64 data type is passed to a COM object, the results are
unpredictable and may result in an error.  This is true even if it is an input
parameter and the number in the variable is within the 32-bit range. 
Therefore, if you do not have the correct version of oleaut32.dll, you should
not use the INT64 data type with COM objects.


PSC00183705 : CAN-FIND X field-list problem
================================================================================
The FIELDS clause does not guarantee the inclusion or exclusion of fields in
any given query.  The AVM may require additional fields, for example, to
accommodate a key value required by an index. 

The application must not reference fields that are missing from the FIELDS
list. In most cases when this occurs a run-time error is generated indicating
that the field is unavailable.	

There are situations, for example with a function that includes the NO-ERROR
attribute by default, where it is legitimate to satisfy function requirements
using a field that is missing from the FIELDS list.  Such instances equate the
missing field to the Unknown value (?) or null (for DataServers) in order to
resolve an expression. In other words, the ABL attempts to detect missing
fields with run-time errors where possible. However, there are cases where it
is legitimate to use a missing field in an expression.	In such cases, the
missing field will resolve to the Unknown value (?) or native data source null.


PSC00132307 : Thai characters or complex scripts do not display in command
prompt or console
================================================================================
The Windows command prompt or console is not enabled for Thai characters or
complex scripts on any version of Windows (XP, Vista or Windows 7). 

When trying to read Progress messages sent to the Console while using Thai or
complex scripts, you can:

* Use the English PROMSGS file.

* Use the Thai character or complex script PROMSGS file, but pipe the output of
the command to a file that can be read by any Windows editor.


PSC00169627 : Memory violation when connecting to a Web Service on AIX 5.3
================================================================================
In order to use WebServices on AIX 5.3, the minimum Operating System
requirement is AIX 5.3.04. You can find the version of AIX you are running
using the oslevel -r command.


PSC00151150 : Data types defined in imported schemas are not seen by the WSDL
Analyzer
================================================================================
RN# 100B-00168
==============
When a WSDL document contains an XML Schema import element, the type and
element definitions of the imported schema are not seen by the analyzer. A
message indicating that a type or element definition could not be found will
appear in the generated documentation.

To work around the problem, copy the xsd:schema elements (and their contents)
from the imported schema document and paste them as children of the wsdl:types
element of the WSDL document.  Also comment out the xsd:import element in the
xsd:schema element.

Double check namespace prefix definitions to ensure the prefixes in the copied
XML are properly defined and can be referenced by other parts of the WSDL
document.


PSC00148993 : Time zone information lost for some XML datatypes
================================================================================
The XML Schema datatypes, gYearMonth, gYear, gMonthDay, gDay, and gMonth, can
optionally include time zone information. OpenEdge does not handle time zone
information correctly for these datatypes. Any time zone input from the ABL is
lost, as is any time zone information returned from a Web service for these
datatypes. For example, "1953-10-4:00" becomes "1953-10". The one exception is
that Z, indicating Universal Time (UTC), is retained (for example, 1953-10Z
remains 1953-10Z).



k. Management

PSC00322062 : Generate Policy program doesn't work  for I18N chr
================================================================================
The "Generate Partition Policy program" in the Partition Policy wizard for OEM
generates a program with scrambled values for the fields when run with I18N
character set. Use the standalone Table Partitioning ABL API's for code
generation.


PSC00306049 : New policy detail has partitions for all indexes
================================================================================
The DataAdmin ABL API for Table Partition Management
PartitionPolicyDetail:Partitions collection includes partitions for all indexes
when referenced before the PartitionPolicyDetail is created. The collection
should only contain partitions for the indexes that are defined as local.
Partitions for global (non-local) indexes are ignored when the
PartitionPolicyDetail is created.     


PSC00305473 : Authentication error with the ABL API for Table Partition
Management split command
================================================================================
Authentication parameters (-U/-P) supplied to an ABL client do not get passed
to the ABL API for Table Partition Management split command, and the split may
fail with an authentication error.

Use the PROUTIL PARTITIONMANAGE SPLIT command instead.


PSC00322601 : Documentation correction
================================================================================
The OpenEdge Management online Help states that while creating a new table
partition policy, you can set a composite partition as read-only. This
information is incorrect. You can set a composite partition as read-only after
the policy has been created.


PSC00183176 : Cannot use an older version of PROMSGS with a current release
================================================================================
Through the automated OpenEdge installation process, Progress Software
Corporation programmatically ensures that a current OpenEdge installation has
the most recent OpenEdge messages in the PROMSGS files. This approach also
ensures that you always have the most up-to-date OpenEdge messages throughout a
release's lifecycle. Do not perform any tasks related to the PROMSGS files
outside of the standard OpenEdge installation process; for example, attempting
to use the PROMSGS environment variable to point to any versions of a PROMSGS
will have unpredictable and potentially undesirable results.

For example, the PROMSGS files installed with the OpenEdge Release 10.1B
contain the most up-to-date messages to support OpenEdge Release 10.1B. After
the initial install, if you install add-on products, or OpenEdge install
service packs that are released after the 10.1B Release date, Progress again
programmatically provides any newer or more recently updated PROMSGS files. As
each OpenEdge add-on product or service pack is installed, the installation
program checks to ensure that the newest copy of the PROMSGS file is being used
by all products.


PSC00183170 : ubroker.properties file is renamed ubroker.properties-sav
================================================================================
When uninstalling the ubroker.properties file is renamed ubroker.properties-sav
and copied to the temp directory.


PSC00183166 : Uninstall fails with Proshell.dll in use
================================================================================
The uninstall will fail if any of the files it attempts to remove are busy. Use
of the Windows Explorer has been known to cause this condition of rendering the
file proshell.dll as in use, thus preventing the uninstall from succeeding,
however this may not be obvious at the time of uninstall.


PSC00183165 : Error when default language not installed
================================================================================
While adding a product after an installation has been completed, if you attempt
to change the default language to a language that has not yet been installed,
and the language is one listed with a non-alphabetic character (e.g. -, (, ))
an error will result that will not accurately reflect the problem. The error
should not prevent the installation from continuing. This problem is apparent
on Windows/NT platforms only and does not occur on UNIX.  The workaround is to
select entries from the pull-down list boxes.


PSC00183164 : Random errors with mapped drives on MSW
================================================================================
Due to Microsoft Knowledge Base Article #294816, we do not support the running
of a Progress application from a Network Share for Windows Terminal Services or
Citrix running on Windows 2000 Server or Windows 2000 Advanced Server. Terminal
Services users might see errors like "Disk or Network Error" or "C0000006: In
Page I/O Error", etc.  This happens due to a bug in the Windows operating
system where the network redirector only creates one file control block (FCB)
for all user connections so that when the first user to open the files logs
off, the other users lose their connections to files. To work around this
problem, place the program and associated data files on a localvolume, not
network share.


PSC00309169 : Partitioning option is incorrectly enabled for pre-11.4 databases
================================================================================
The Table Partitioning "enable" option under "Database Features" for pre-11.4
databases is incorrectly enabled. This option should be disabled because the
Table Partitioning feature is not available for 11.3 and earlier databases.


PSC00182944 : Working with Properties
================================================================================
If an "-Xbootclasspath:", "-Xbootclasspath/a:", or "-Xbootclasspath/p:" entry
that contains spaces in the argument value has been added to the
JavaTools.properties or AdminServerPlugins.properties file, the entry must be
manually edited to include quotes around the entire argument value (value to
the right of the colon).



l. NETUI

PSC00211451 : All dates exchanged between ABL and .NET are now the same except
12
================================================================================
All dates going from .NET to ABL and from ABL to .NET will be exactly the same
except for 12 days. These are the dates 2/29 in the leap years that are
represented by the Julian Calendar (on the Progress side) but not represented
by the Gregorian Calendar (on the .NET side).

(Since the Gregorian Calendar was not created until 10/15/1582, the .NET
DateTime implementation is not correct.)

These dates are:

2/29/100
2/29/200
2/29/300
2/29/500
2/29/600
2/29/700
2/29/900
2/29/1000
2/29/1100
2/29/1300
2/29/1400
2/29/1500


PSC00210591 : ABL extended .NET object subscribed to .NET event may be deleted
prematurely
================================================================================
An ABL extended .NET object subscribed to a .NET event may be deleted
prematurely. This bug can be observed with the following conditions:

- An ABL extended .NET object, for example AForm, is visualized
- A .NET object, for example a button, is not on AForm, but one of AForm's
methods is subscribed as the handler for this button's event.
- There is no reference to the button in the implementation of AForm.

If AForm is closed, and therefore Disposed, and all ABL references to it go
away, it will be deleted even though the button subscription is still
outstanding.  In other words, the button, in essense, still has a reference to
the class due to the subscription.  But this does not prevent the object from
being deleted, as it should.


PSC00225230 : .NET controls that call back to the AVM on other threads are not
supported
================================================================================
A .NET object might call back to the AVM to handle an event on a thread other
than the main UI thread. It might also call a .NET method on a different thread
where the method was overridden in a derived ABL class. The AVM does not
support either of these cases and raises a run-time error if they occur.


PSC00204789 : Workaround for Elegant Ribbon control and
IsolatedStorageException
================================================================================
The Foss PersistentStateManager class automatically loads and saves application
state in isolated storage, which does not work with the current OpenEdge .NET
bridge architecture.  Setting the
LoadStateAutomaticallyFromIsolatedStorageForDomain property to FALSE disables
the automatic state loading at application startup.  Add this line to your
program that uses the Elegant Ribbon control:

Elegant.Ui.PersistentStateManager:LoadStateAutomaticallyFromIsolatedStorageForD
omain = FALSE.
 
This also means that changes in the quick access toolbar will not be loaded and
saved automatically.  If you need the changes to be kept, manually use the
Load() and Save() methods of the PersistentStateManager class.



m. Next Gen AppServer

PSC00321763 : PAS for OpenEdge	Windows installation failures when a path name
has spaces
================================================================================
Installation of Pacific Application Server for OpenEdge development or
production products  fails on a Windows system when the installation directory
(DLC) or working directory (WRKDIR) contains spaces.

Windows installation also fails for the Progress Developer Studio for OpenEdge
product (PDS for OE) that includes the the PAS for OE development product.

The only known workaround is to reinstall using  DLC and  WRKDIR paths that do
not contain spaces.


PSC00319054 : Undeploying an oeabl Web application does not update
openedge.properties
================================================================================
After you undeploy an oeabl Web application, its properties remain unchanged in
the openedge.properties file. This will not effect other Web applications that
are deployed. However, there may be issues with non-default property values if
you redeploy oeabl.war as the same Web application. Therefore, you should check
openedge.properties and confirm that settings are correct after a redeployment.


PSC00311081 : Crashed MSAgent processes is remain listed as active
================================================================================
An MSAgent that terminates after a crash remains on the SessionManager's list
of available agents. After a normal stop, terminated agents are removed from
the list.

As a result, queries for existing agents, using the REST Management or the JMX
APIs, could include agents that terminated ungracefully. Any operation on a
terminated agent results in internal server exception with the following error
message:

      Communication layer message: General Error: READPACKET IOException :
java.io.EOFException (null). (7175)


PSC00315839 : 10.2B .NET OpenClient fails to connect to PAS for OpenEdge
================================================================================
A.NET OpenClient may fail to  communicate properly to PAS for OpenEdge if
proxies were generated with OpenEdge Release 10.2B.  If this occurs, regenerate
the proxies using OpenEdge Release 11.5.


PSC00319995 : Multi-session Agent may crash when the Windows OS is suspended
================================================================================
The Multi-session Agent may crash when the Windows operating system is
suspended (for example, when a laptop is set to sleep mode when the laptop is
closed). To avoid this issue, shut down the Pacific Application Server for
OpenEdge before suspending the operating system.


PSC00318079 : CREATE DATABASE statement fails silently
================================================================================
The CREATE DATABASE statement may fail silently if the underlying procopy
fails.	While creating the database, any errors during copying are not
reported.  These errors may include such cases as the source database being
corrupt or incomplete, the destination directory being unwritable, or the copy
process being interrupted.


PSC00317929 : External Procedures cannot access stdin, stdout, or stderr
================================================================================
External procedures in a DLL or shared library cannot access  stdin, stdout, or
stderr when called from ABL code executed by the PAS for OpenEdge Multi-session
Agent.



n. OEBPM

PSC00306528 : OEBPM JSDO REST project requires recompilation
================================================================================
A sample REST project is shipped as part of OE BPM (available in
<DLC>\oebpm\studio\JSDO_Support\OEBPM-Rollbase). This exports BPM data (process
instances and task details) as OpenEdge service object. 

After importing the REST project in PDSOE (useful for Rollbase presentation
type), users should manually open the OEBPMEntity class file and select
compile. This recompiles and updates the class file (as the .r file is not up
to date) and also deploys on the AppServer if the REST project is added to that
server.


PSC00255318 : BP Server DataSet CLOB supports only UTF-8
================================================================================
When you populate a dataslot with a DataSet value that contains a CLOB field,
the format must be UTF-8.

If your source data is in another format, it must be converted to UTF-8 using
ABL statements.  

For example:

COPY-LOB FROM m2 TO etable1.clobFld CONVERT TARGET UTF-8.


PSC00321263 : For non-English users, DateTimeTZ cannot be saved
================================================================================
Non-English users will not be able to save DateTimeTZ in a UI workstep
involving the datetime dataslot and the DateTimeTZ field will be empty in the
next activity.


PSC00306259 : Maximum allowed width of LongChar and Character
================================================================================
The maximum allowed size in studio for a Character dataslot is 250 characters. 

The maximum allowed height and width for the text area in the LongChar dataslot
is 250.


PSC00288315 : Service Connection Details dynamically to OpenEdge
================================================================================
The service connection details can now be provided to OpenEdge dynamically and
OpenEdge Adapter is not suspended in OpenEdge BPM Portal. This can done by
providing ${bpsbrokerValue} for the Application server in the Configurator and
by configuring and specifying broker value (bpsbrokerValue property) in the
oebps.conf file.


PSC00256482 : EJB Server does not start when hostname has _
================================================================================
The EJB Server does not start when hostname has "_". This is a limitation with
JBoss application server.


PSC00322009 : Cluster tool help not displayed in Chrome.
================================================================================
The help system for Cluster Tool does not display properly when opened in
Google Chrome. This issue will be fixed in a later release. As a workaround, it
is suggested that the users launch Cluster tool Help using Internet Explorer or
Mozilla Firefox.



o. OEMobile

PSC00319825 : Mobile app creation fails after subscription upgrade
================================================================================
When you upgrade your Mobile App Builder subscription, users might get an error
message when trying to create mobile apps. 

Workaround: simply refresh the Mobile App Builder browser page and users should
be able to create apps.


PSC00320621 : JSDO addRecords() MODE_EMPTY change
================================================================================
Prior to Release 11.5, when the JSDO addRecords() method was called with the
merge mode specified as progress.data.JSDO.MODE_EMPTY, the working record set
for each JSDO table reference remained unchanged. This was not correct since
with the MODE_EMPTY mode, the JSDO memory is first cleared out, so the current
records are no longer valid.

In Release 11.5, when addRecords() is called with MODE_EMPTY, the working
record set for each JSDO table reference is now set to undefined.


PSC00322756 : Can't log in via HTTP from app loaded via HTTPS
================================================================================
Developers using PDSOE to generate Mobile apps may run into a problem testing
an app from the Mobile App  Builder due to a ômixed contentö problem. ôMixed
contentö means that a script that was loaded using the HTTPS protocol attempts
to load a resource that uses only HTTP. This is exactly what happens when a
developer tests an app from the MAB against a Mobile Web application that was
built using PDSOEÆs defaults for creating a Mobile Web application, because the
Mobile App Builder uses HTTPS but PDSOE generates a Web application that uses
HTTP. 
Firefox, Internet Explorer, and now recent releases of Chrome and Opera block
mixed-content requests by default.

There are two ways to handle this. One is to enable the Mobile Web application
for secure communication. This requires opening an SSL-enabled port, and then
ensuring that the serviceURI and catalogURIs values in the app's appconfig.js
file or Session Service Settings specify that port and the https protocol. This
is the recommended approach. To do this if you are using the Tomcat server that
comes with OpenEdge:
1.  Edit DLC/servers/tomcat/conf/server.xml
     Uncomment the <Connector> XML element that contains the attribute
secure="true"
2.  Define a TCP/IP port for the Tomcat server to use via environment variable
OPENEDGE_HTTPS_PORT ( this environment variable may be defined in
%WRKDIR%\proset.env )
3. Tomcat comes with a default server key and certificate located in
conf/default_server.p12.  Clients will need the CA certificate used to issue
the default_server key/certificate ( DLC/certs/d9855a82 ) to verify the Tomcat
server connection

Alternatively, most browsers have settings that enable a user to direct the
browser to allow mixed content. Chrome, for example, displays a small gray
shield at the right end of the address bar whenever it blocks mixed content; a
user can click on this shield to tell Chrome to go ahead and allow the mixed
content. Chrome also has a startup parameter that directs it to always load
mixed content, and other browsers have similar mechanisms, but changing these
introduces a security risk since they will apply to every page that the browser
loads.

For more information, see the posting on Progress Communities at 
   https://community.progress.com/community_groups/mobile/f/17/t/13569.aspx 
(the title is "Problem testing apps from Mobile App Builder").



p. Open Client

PSC00194437 : Multiple Dataset parameters and RPC Encoded Web Services with
Axis java clients
================================================================================
When defining multiple INPUT DATASET parameters for an OpenEdge web service
that uses RPC/Encoded SOAP messages, do not use the NAMESPACE-URI option in the
DEFINE DATASET statements.

The Apache Axis Java client does not properly handle namepsace declarations
when it sends a SOAP request for an RPC/Encoded SOAP message. As a result, an
incorrect message will be sent and the data will not be loaded into the
ProDataSet.

Axis may have similar issues with OUTPUT DATASET parameters. SOAP responses
from OpenEdge may not be properly deserialized.

If the NAMESPACE-URI option is required, then either define the OpenEdge Web
service to use Document/Literal or RPC/Literal SOAP messages. Alternatively,
avoid the issue by passing only one dataset in the Web service call.



q. PDSOE

PSC00313037 : Incorrectly placed double quotes in data definition file corrupt
Content Assist functionality
================================================================================
If a pair of double quotation marks (opening (ô) and closing (ö)) appear on
different lines in a data definition (.df) file, the Content Assist
functionality fails to work properly.á

To avoid this, ensure that the opening and closing double quotation marks are
on the same line in the .df file and then load the file to the database.


PSC00258444 : Error 5635 may occur when using AppBuilder in PDS to create
SmartObjects
================================================================================
The following error may occur when creating SmartObjects using the AppBuilder
feature in PDSOE:

Error 5635 ["SYSTEM ERROR: -s exceeded. Raising STOP condition and attempting
to write stack trace to file 'procore'. Consider increasing -s startup
parameter"] 

If this occurs, add "-s 128" to the project's startup parameters to increase
the project AVM's stack size.


PSC00240112 : Progress Developer Studio for OpenEdge debugger behavior change
================================================================================
Starting in OpenEdge Release 11.0 and continuing in all subsequent releases,
the Progress Developer Studio for OpenEdge debugger does not stop at the first
executable line. Instead, the debugger stops at the line containing the first
breakpoint. 


PSC00322693 : A generic sample URI is displayed when a Mobile project is
published to a Pacific Application Server for OpenEdge instance
================================================================================
When a Mobile project is published to a Pacific Application Server for OpenEdge
instance, the Edit Mobile Service wizard displays a generic sample URI. The
complete service URL, for Pacific Application Server for OpenEdge, uses the
project name in place of the first Mobile service name.
	
You can also view all the deployed applications, services, and their URL's in
OpenEdge Management or OpenEdge Explorer.

The URL for deployed applications is:
Resources / OpenEdge/ Pacific Application Server / <Server Name> / ABL
Applications / 

The URL for services is:
Resources / OpenEdge/ Pacific Application Server / <Server Name> / ABL
Applications / <Mobile projectname>


PSC00257927 : Support for starting non-modal .Net Forms in an AVM project
session
================================================================================
With release 11.5, Progress Developer Studio for OpenEdge uses the wait-for
System.Windows.Forms.Application:run () method as the top level wait-for method
in a projectÆs ABL session. This allows customized tools and _idestartup.p to
start non modal .Net forms in the project session.  

However, any code started on the project session with its own wait-for
System.Windows.Forms.Application:run () method (as in the previous releases)
returns an error. The wait-for System.Windows.Forms.Application:run () method
must be replaced with wait-for <form>:ShowDialog or Show() to work. The Show()
method allows the form to open in a non-modal mode so that you can use Eclipse
actions and tools like Check Syntax and Data Dictionary while the form is open.
   
   
Launch Configuration still does not allow the launch of .Net forms in a project
session.


PSC00320068 : REST Resource URI Editor allows mapping definitions only to
custom JSON content types
================================================================================
The REST Resource URI Editor in PDSOE allows you to use its Mapping Definitions
section to create a constant of any type (for instance, application/pdf), under
the Constants node, for an element of an HTTP request and then map it to the
content type node of an element of the HTTP response.

However, this mapping support is limited to only custom JSON content types. For
example: application/json, application/app1+json, etc.


PSC00317249 : PAS for OE status is not reflecting in PDSOE
================================================================================
If we start Pacific Application server for OpenEdge in command line i.e from
proenv. And open PDSOE server's view to check the respective server status. It
always shows as stopped even server is started.

Work around for this issue is: Refresh the instance page in OEE or Stop the PAS
instance from same command line (from proenv) and start server from either
OpenEdge Explorer or from PDSOE.


PSC00317138 : The Compile on Publish operation fails to work correctly for
remote Pacific Application Server for OpenEdge instances
================================================================================
For a remote Pacific Application Server for OpenEdge instance, if the Open
Publish r-code option is disabled and the Compile on Publish option is enabled
in the Server Editor, then the compile listing files are generated every time
the file is published, republished, or a clean operation is performed. These
compile listing files must be deleted after publishing the Pacific Application
Server for OpenEdge instance.

There is no runtime support for this in the 11.5 release.


PSC00222815 : OpenEdge cannot compile/run GUI for .NET code generated using
previous versions
================================================================================
When you edit GUI for .NET code generated using a previous version of OpenEdge
Visual Designer, the generated code is updated to the current version of
Progress Developer Studio for OpenEdge and thus might contain new language
constructs that are not compatible with the previous versions of the compiler
and the AVM, and wizard-generated code is incompatible with previous versions.
Such incompatibilities can occur even when you do not explicitly use new
features of the current version.

To compile and execute GUI for .NET code, you must use an OpenEdge version that
matches or is later than the Visual Designer version in which the code was
generated. For example, source code opened in version 11.0 of the Visual
Designer will no longer compile in 10.2B.



r. Porting

PSC00187938 : On Windows 7 platforms, sqlexp only works with a numeric port
number
================================================================================
On Windows 7 platforms, sqlexp can only connect to the database server if the
port is numeric. For example, specify the port number as 4050 rather than using
a service name like "mydbservice".


PSC00208050 : Windows 64bit requires more memory for the Operating System
================================================================================
In Windows 64-bit, the operating system requires 2GB of free memory for
acceptable OpenEdge performance.  If your shared memory allocation (database
buffer pool) leaves less that 2GB of free memory, then performing even simple
operations, such as finding a record that is in memory, is extremely slow.



s. REST Adapter

PSC00305570 : Unable to deploy REST application on a remote AdminServer
================================================================================
You might observe timeout issues when deploying a REST application on a remote
AdminServer. This can happen when large REST application zip files take longer
to deploy than the default request timeout allows.  Work around this issue by
increasing the fathom.activemq.timeout Java system property value.  By default,
this property is set to 20000ms.  Increase the value to 40000ms by adding
"fathom.activemq.timeout=40000" to the $DLC/fathom.init.params file.



t. SQL

PSC00192905 : ESQLC clients can specify an IP protocol version using a
parameter
================================================================================
ESQLC clients will default to using the IPv4 protocol.	The use of the IPv6
protocol can be selected by using the -ipv6 parameter on the connection URL. 
The following is an example of a connection URL where the use the of IPv6
protocol is desired:

progress:T:myhost:5000:mydb:[-ipv6]

The parameter is also available to use with connection URLs for the SQLDump,
SQLoad, and SQLSChema utilities.


PSC00287562 : Error in data access for TP table when data is not moved to
respective partitions.
================================================================================
For a TP table data access, user may experience failure when one or more
partitions of that table are marked for "prepare for split target". If query
tries to access such partitions, SQL server returns failure saying "Table is in
maintenance mode". This happens for local index scan and table scan. However,
SQL server does not report error when Global index scan is used by the query.
Below is the illustration of above behavior using an example.

--Alter the table to a list partition table
ALTER TABLE TAB
PARTITION BY LIST I USING TABLE AREA "tpCustomerArea60"
(
   PARTITION PART_1 VALUES IN (1),
   PARTITION PART_2 VALUES IN (2)
)USING INDEX IDX_TAB;

ALTER TABLE TAB PREPARE FOR SPLIT PRO_INITIAL  TARGET PARTITION PART_1;

--Access data using local index scan. Error shall be thrown in this case
SELECT * FROM TAB;
 [DataDirect][OpenEdge JDBC Driver][OpenEdge] Table "HUM.TAB" cannot be
accessed for a partition (partition id=1) due to incomplete db maintenance
operation.(17736)

--Access data using global index scan. We shall get result in this case
SELECT * FROM TAB FORCE(INDEX(INDX_GLOBAL)) WHERE I>0;
	  I
-----------
	  1
	  2

So, it is recommended  to the users to move the data to respective partition as
soon as the partition is marked as "prepare for split target" to have
unrestricted data access. 


PSC00318424 : Correlated scalar subqueries in an ON clause causes a crash or an
error
================================================================================
The SQL engine may crash or result in an internal error when correlated scalar
subqueries are used in the ON clause of an outer join query.


PSC00188599 : SQL uses the Java compiler to compile the Java code for a CREATE
================================================================================
TRIGGER or CREATE PROCEDURE statement. If the Java compiler finds errors in
this Java source code, it outputs diagnostic information describing the errors.

A subset of the diagnostics is appended to the SQL-92 error
message which is returned to the client.

The entire set of diagnostics is stored on the server, in the SQL server's
WRKDIR (working directory).  If the owner of the stored procedure/trigger is
OWNER, and the procedure/trigger name is XX, then all the diagnostics are in
the file named OWNER.XX.LST in the SQL server's WRKDIR (working directory).

The WRKDIR is identified by either the environment variable $WRKDIR, or on NT
by the registry entry WRKDIR under the registry key for the Progress software
installation.



u. Server Technology

PSC00222182 : 11.1 Webspeed Messenger installation behavior for Windows
================================================================================
From OpenEdge Release 11.1, Webspeed Messenger installation behavior on Windows
has changed as below: 

1) WebSpeed Messenger only installation: 

The msngrs.properties file is created in the $DLC/properties location. Prior to
OpenEdge Release 11.1, it used to be the ubroker.properties file. This changed
behavior on Windows is now consistent with the behavior on UNIX. 

Note: You can rename the msngrs.properties file to the ubroker.properties file.

2) WebSpeed Messenger only installation performed over the existing OpenEdge
installation: 

a) The msngrs.properties file is created in $DLC/properties. 
b) The existing ubroker.properties file is saved as ubroker.properties-sav. 

This changed behavior on Windows is also consistent with the behavior on UNIX.


PSC00167391 : OpenEdge installation may install Sonic client and container code
================================================================================
RN#: 101A-00291
===============
The OpenEdge installation program may install Sonic Software client and
container code depending on which products get installed. Because the
installation program requires it run as ROOT on Unix, the Sonic Software code
gets installed with those permission set. The OpenEdge installation program
attempts to set the correct permissions for the Sonic code, but this fails on
the HPUX operating system. This will cause the Sonic ESB Container created by
OpenEdge to fail when started unless it is started as ROOT. To resolve this,
run the command 'chmod -R o+w *' from $DLC/sonic as ROOT.



v. WebClient

PSC00310993 : WebClient install fails from IIS
================================================================================
If hosting the WebClient install image on an IIS Web Server, the install might
fail with the following error message:
An error (-5005 : 0x8007000d) has occurred while running the setup.

If this occurs, make sure to define the following MIME types in your IIS web
server and re-try:
.inx	 application/octet-stream
.ini	 application/octet-stream
.hdr	 application/octet-stream


PSC00183963 : DLLs and EXEs That You May Have to Package with Your Application
================================================================================
Be aware that there may be Progress-supplied DLLs or EXEs that are used by your
application that are not included in the end-user WebClient install. Strictly
speaking, these DLLs and EXEs are not a part of ABL.  For example, there are
some DLLS or EXEs only used during application installation. Other DLLS may be
required if the application uses procedures in the adecomm or adeshar
directories that indirectly use DLLs.  Progress  excludes them from the install
to keep WebClient as small as possible and keep install time over the Internet
as fast as possible. If you need any of these files to install or run your
application, include them in your application installation.  Examples of these
files are listed below by category.

DLLs used by some procedures in adecomm/adeshar:
    dirsrch.dll
    fileinfo.dll
    proprint.dll

EXEs that could be used by your install:
* ini2reg.exe
* regsvr32.exe (A Microsoft tool usually, but not always, installed on a
typical PC)


PSC00183961 : Do Not Use Notepad to Edit .htm Files
================================================================================
Do not use Notepad to edit the webclient.htm file or bootstrap.htm file for
customizing your application install. When Notepad saves the file, it changes
the line terminator characters and may make the file work improperly in the
browser.


PSC00183171 : The WebClient install does not accurately calculate disk space
required
================================================================================
The WebClient install does not accurately calculate the amount of disk space
required on the client side to do the install.	Prior to the install the user
should probably have around 25 meg of available disk space. Some of this is for
temporary storage of installation files.



LIST OF ISSUES ADDRESSED

a. ADE Tools and Runtime

PSC00317147
=============================
Incremental Delta.df generated in OpenEdge 11 contains the unnecessary line
"MULTITENANT no" in Sequence definitions.


PSC00314027
=============================
When using the TEMP-DB Maintenance tool to import a fair number of procedures,
because of how it was written, it reports REPLACE/CONCAT, bfx: field to large
for a data item, or DITEM limit errors and cannot proceed.

The layout doesn't make this any easier to use because it imports all files in
the directory before giving the user the opportunity to choose a smaller subset
of files to process.

The tool uses selection lists that use LIST-ITEM-PAIRS to reference the
relative path name of a given file, while storing the full pathname in the
value part of the list.

This builds up a seemingly small list of programs to process, however when the
full pathnames of all the files are added to the mix, when the code references
the LIST-ITEM-PAIRS attributes of the selection lists, it doesn't take much to
blow out the limitations.


PSC00312184
=============================
UpdateActive is not set to FALSE for GroupAssign target when record is saved


PSC00312033
=============================
An SDO is supposed to ignore trailing whitespaces in character fields in the
database, when comparing if record was changed by other user.
There is a case where that doesn't work as intended, if the field names in the
SDO do not match the field names in the database table, and if one of the
fields in the database is an extent field (which becomes 'x' number of fields
in the SDO).


PSC00306772
=============================
When you select "Database" -> "Reports" -> "Detailed table Report" in the Data
Dictionary, wrong table "Field Count" is reported for the selected table, when
the new fields have been added or some have been deleted.


PSC00261819
=============================
Missing "Load Complete" message after a warning is received when loading a .df.


PSC00256117
=============================
'New' as logical database name causes failure of load sequence values.



b. Adapter for SonicMQ

PSC00246476
=============================
The getDataset function for the OpenEdge Adapter for SonicMQ ABL-JMS API fails
after calling other ABL-JMS API functions inside the message handler.



c. AdminServer

PSC00283817
=============================
No error written to admserv.log when wrong IP or hostname is used to start the
AdminServer.
Error message appears on screen only when AdminServer is started from command
line.


PSC00268985
=============================
proadsv -all -query -port 20941 reports databases running against 20931
**********************************************************

When two AdminServers are running on the same machine against different ports.
proadsv -query reports databases running under the default port 20931




d. AppServer

PSC00313366
=============================
Appserver agent can get stuck in SENDING state after adminserver have performed
warm restart


PSC00311786
=============================
Querying the ports of running agents using a port scanner tool (like
Microsoft's PortQry) will cause (nearly) all agents to disconnect from the
broker.


PSC00310164
=============================
8297 error message can indicate timing issue associated with the startup of an
AppServer Broker.


PSC00310041
=============================
Appserver broker is vulnerable for SSL/TLS MiTM attack.


PSC00291761
=============================
AppServer Agent crashes when the TCP port of the agent is accessed via a
non-OpenEdge supported application/process


PSC00258997
=============================
Starting AppServer with password on UNIX fails with vague error
****************************************

Starting an AppServer on Unix systems with the password property set in the
ubroker.properties file, the following vague error is returned:

<broker name> is not responding (12076)

The asconfig -v command also returned no errors when validating the syntax of
the ubroker.properties file.  

A better error should be returned when starting the resource or when validating
the ubroker.properties file.

In the admserv.log file the following stack is generated:

* Exception executing jvmStart:
* java.lang.NullPointerException

java.lang.NullPointerException
 at com.progress.ubroker.tools.SvcControlCmd.startService(SvcControlCm
d.java:327)
 at com.progress.ubroker.tools.UBRemoteCommand.runIt(UBRemoteCommand.j
ava:350)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorIm
pl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc
cessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305
)
 at sun.rmi.transport.Transport$1.run(Transport.java:159)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
 at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.jav
a:535)
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTrans
port.java:790)
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransp
ort.java:649)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolE
xecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecu
tor.java:908)
 at java.lang.Thread.run(Thread.java:662)

While password is an invalid property to set for AppServers on Unix operating
systems, it is extremely difficult to find out this fact unless you happen to
re



e. DATASERVER

PSC00315387
=============================
Cannot connect an OpenEdge 11.4 stateless AppServer with one SH and multiple 
schema images when using a pf file


PSC00315200
=============================
Oracle DataServer trims the white spaces from the varchard2 characters when
retrieved from oracle using stored procedure call.


PSC00314885
=============================
DataServer for Oracle generates a SQL statement that uses the wrong parameter
in a sub-SELECT statement resulting in an Oracle error. Disabling server-side
joins (NO-JOIN-BY-SQLDB) avoids the issue.


PSC00314009
=============================
AppServer crashes when attempting to start if using one database to hold the
schemas for multiple foreign databases.



PSC00313797
=============================
Oracle DataServer returns error ORA-1008 "Not all variables bound" on nested
FOR EACH...WHERE...FIRST clause


PSC00313440
=============================
Owner name is encrypted and not able to pull objects into schema holder when
perform individual pull. The USERID function also returns an encrypted string
if the uid string passed to the Oracle Dataserver at connect time matches the
format :  <uid>@<service name>
This issue is reproduced only when uid is specified as <uid>@<service name>.
With <uid>/<pwd>@<service name> it works fine.


PSC00313065
=============================
Oracle DataServer truncates any numeric characters >34 when used in the WHERE
clause.


PSC00312183
=============================
If the port range for _probrkr is 5 digits for -dsminport and -dsmaxpoort, ABL
client shows error 5049 during the connection to foreign database. The _probrkr
starts fine but when client tries to connect using the _probrkr to foreign
database, it gives the error.


PSC00308378
=============================
When running two client sessions with the following startup parameters, the
second client crashes: 

-dslog <path>
-logthreshold <non zero value>
-Dsrv qt_debug,SQL

Instead of crashing, the following errors should appear:

Cannot open log file <path>\dataserv.lg, errno 32 (11076) 
Unable to open dataserver log file. (2683) 
Failed to connect to ORACLE database . (1451) 


The errors are in fact expected: When a non-zero value is specified for
-logthreshold, only one client process at a time can open the file specified by
the Client Logging (-clientlog) startup parameter. In this case it is
recommended that each client session specify a different file name.


PSC00305916
=============================
Value of the "Maximum Varchar Length" field resets to default after
opening/closing Advanced options, when using the DataServer migration utility
"OpenEdge DB to MS SQL Server" or "OpenEdge DB to ORACLE".


PSC00305842
=============================
The ABL client hangs instead of showing error 2624 with Oracle DataServer when
a record is locked by another ABL session after upgrading the OE 10.2B06
service pack to OE10.2B07 or OE10.2B08 service pack.


PSC00303486
=============================
CAN-DO is ignored when using query handle with prepare statement


PSC00281116
=============================
When using skip schema check the size of LOB-mapped LOBs are not being
converted to LOB locators.

Server LOB is mapped  to a LOB in OpenEdge via schema pull with -Dsrv
skip_schema_check. Crash or out of memory error ensues because the size of the
size of the LOB object is not adjusted to the LOB locator that maps its actual
length.


PSC00248280
=============================
recid does not work for SQL DataServer when "Try Primary for ROWID" is
selected.  The record found using recid function is not correct.


PSC00241769
=============================
Errors 6182 and 2651 querying NVARCHAR field in MSS DataServer
****************************************
Errors 6182 and 2651 occur when querying NVARCHAR field and value used in the
ABL WHERE clauses exceeds the max-width of the field in MSS:

"You tried to compare or to update a character field with a value longer than
the maximum length. (6182)
Field num: 3, value: 1234567890123456789012345678901234567890. (2651)


PSC00226097
=============================
Error 1101 and session death with MSS DataServer
****************************************
When updating a record with > 32K of data via the DataServer for MS SQL Server,
it is possible for the session to generate error 1101 and terminate



f. DB

PSC00317988
=============================
Prorest of an online backup of a database may fail with 9447 bkiowrite error on
the bi file.

The backup was created with the "bibackup active" option, which is the default.

The problem occurs when the active portion of the BI exceeds 2GB.  Because the
size of the active portion of the BI can vary from backup to backup, the
problem may occur and then not occur on subsequent backups.

It will not occur with the use of -bibackup all.


PSC00311756
=============================
PROMON sessions cannot be disconnected other than by closing the PROMON session
itself.


PSC00306576
=============================
Logical undo of JTA fails with:
(868)	SYSTEM ERROR: prevbiblk (rlrw.c) bad prev rlcounter.



g. Diagnostics

PSC00317163
=============================
Setting logginglevel to 3 or 4 with logentrytypes containing "4GLTrace" causes
a procedure to crash with a memory violation when passing the Unknown value to
a MEMPTR input parameter.


PSC00289374
=============================
The ABL client can crash when using QryInfo logging at logging level 3, if it
executes a FOR statement with one or more joins, where the first buffer has a
WHERE on ROWID() and one of the joined buffers has a NOT CAN-FIND() in it's
WHERE clause.



h. GUI

PSC00319061
=============================
When resizing a .Net form with an embedded ABL browse, the screen value of a
browse field represented as a toggle can change.


PSC00317101
=============================
When using the UTF-8 client with extended characters and ADM2 Applyentry, in
some cases the cursor position of a fill-in is not correct when entry is
applied to smartfields on different pages.


PSC00316197
=============================
If a window is maximized and then minimized, the children of the parent window
will not be visible on-screen when the parent window is restored.


PSC00315011
=============================
Images which use the STRETCH-TO-FIT option may redraw slowly. This is
especially noticeable if other widgets are overlaid on the image.


PSC00312465
=============================
When migrating code from Progress 9.x to OpenEdge 11.3 the PUT SCREEN statement
can leave artifacts on the screen.


PSC00311701
=============================
A small amount of memory is leaked each time a procedure is run in the
Procedure Editor in the 64-bit Windows GUI client.


PSC00308471
=============================
The LOAD-IMAGE() method returns yes even if the image file is not found.
LOAD-IMAGE should return no if it can't find the image file.


PSC00302494
=============================
Redisplaying a frame will cause its top level parent window to repaint if the
last input method (i.e. mouse vs keyboard) changed since the frame was
displayed. This gives the effect of the application flashing. 


PSC00220693
=============================
logical fields with UTF-8 extended character formats are corrupt
****************************************
When using logical fields that have UTF-8 extended character formats, on
display the fields can be corrupted and the wrong characters displayed.



i. Install

PSC00306845
=============================
sql-odbc-setup.exe is not creating 64-bit drivers when given the correct
parameters that should install the 64-bit ODBC drivers.



j. LANG

PSC00318161
=============================
When executing a statement that raises an error on passing parameters to the
NEW function for  an OOABL object within a RETURN statement the client crashes
in rnhdlbrnch.

This is a regression as it did not occur in 11.3.


PSC00317893
=============================
A ProDataSet object created via the CREATE-LIKE method does not get the
SERIALIZE-NAME and/or XML-NODE-NAME attributes values from the source
ProDataSet.


PSC00317319
=============================
Possible crash when running automatic transaction procedure on AppServer when
triggers are involved


PSC00316184
=============================
The performance of an application that uses temp-tables in OpenEdge 11.4
degrades over time if using FIND/CAN-FIND on a temp-table thas has not been
instantiated.


PSC00314968
=============================
Using the AddStringFilter method in a chained reference when firing
PushNotificationMessageBuilder:Send causes the client to crash.

For instance:
ASSIGN oPayload = PushNotificationMessageBuilder:Send(cMessage,
iBadgeCount):AddStringFilter ("token", "<UDID>",
OpenEdge.Mobile.PushNotificationFilterOperandEnum:Equals ):Payload.


PSC00314482
=============================
When executing a specific query from 11.X clients against a 10.X database
server, the following error may be returned and the _mprosrv process may crash:

Error reading socket, ret=0, errno=2 (778)

In the database log file, the following errors may be seen:
(5729)	Incompatible datatypes found during runtime conversion.
(49)	SYSTEM ERROR: Memory violation.


PSC00313792
=============================
ABL client crashes when compiling code that uses ACCUMULATE with x:y
expressions.


PSC00312561
=============================
The DDE interface, such as DDE INITIATE / DDE EXECUTE statements, do not
support Unicode strings. For example, when trying to load a file using the
interface, if the file has an extended non-ASCII character in its file name the
file cannot be found.


PSC00312419
=============================
When using a ProDataSet containing tables in a parent / child relationship with
the Combit List & Label .NET reporting control bound to a BindingSource using
the constructor with the reportMode (previously called batchMode) parameter set
to True, the wrong child data is displayed as follow:

* First parent
* Second parent
----  First Child of FIRST parent
----  Second Child of FIRST parent
----  
* Third parent
----  First Child of SECOND parent
----  Second Child of SECOND parent
----


PSC00311529
=============================
COPY-LOB used to populate a UTF-8 database table field may fail if the database
connection is client/server (-H -S) and succeeds for single-user/shared memory
connections.


PSC00311504
=============================
FOR EACH query fails to return expected result set on 64-Bit OpenEdge 10.2B.x
and 11.3.2.x products when the WHERE clause has more than 6 CONTAINS operators.


PSC00311240
=============================
Calling an OpenEdge Web Service from an ABL client asynchronously, then calling
CANCEL-REQUESTS followed by an execution of the PROCESS EVENTS statement,
exposes a core memory leak that causes the ABL client's memory consumption to
grow until the process runs out of memory.


PSC00310991
=============================
The ABL client crashes if GET-CODEPAGE(), FIX-CODEPAGE() or IS-CODEPAGE-FIXED()
functions are passed a public LONGCHAR property whose GET accessor does not
return any value.

E.g. 

CLASS MyClass:
    ....
    DEFINE PUBLIC PROPERTY MyProp AS LONGCHAR NO-UNDO
    GET():
    END GET.
    SET.    
    ....
END CLASS.

FIX-CODEPAGE(oclass:MyProp) = "UTF-8".


PSC00310804
=============================
If an AVM is running with a double-byte codepage or UTF-8 for -cpinternal, a
CHARACTER field or variable may contain malformed characters in the form of an
invalid lead-byte (a byte that is not a lead-byte, but is beyond the ASCII
range). Such malformed characters will not be detected if copied to a LONGCHAR
of the same codepage. 
Note that invalid trail-bytes following a valid lead-byte are successfully
detected.


PSC00310786
=============================
If a given buffer is used on a FIND statement, and then use that same buffer in
a FOR statement with the TABLE-SCAN option, subsequent FOR statements on that
same buffer in the given program behave as if TABLE-SCAN was specified for them
too.


PSC00309678
=============================
The READ-XMLSchema method of a dynamic ProDataSet can fail to properly import a
complex XSD file.  This happens when a parent-id-relation is created with
parent-fields-after, and there is a field in the parent table with
xml-node-type attribute.


PSC00309064
=============================
Data Dictionary Help string attributes are not always inherited when compiling
code.


PSC00307281
=============================
COMPILE XREF-XML crashes on a class, if the class has a public method that has
a .NET Generic type as the return value.
This is a follow-up on PSC00279280 - similar crash but for parameters to the
method. 


PSC00306795
=============================
If you use callback authentication with Client-Principal, it is possible to
insert a man-in-the-middle attack to reveal the user's plain text password.


PSC00306562
=============================
When running Asynchronous appserver procedures locally on the session handle,
this can cause error 8982 when the lower level event procedures are run:

Invalid event-procedure context encountered when trying to invoke event
procedure '<event-procedure-name>'. (8982)


PSC00305184
=============================
It is not possible to catch the timeout error message which is produced by the
-clientConnectTimeout parameter within the CONNECT() method.


PSC00300880
=============================
When a procedure executes a FIND on a BY-REFERENCE temp-table, the AVM can
allocate a database cursor but never release it. If such code executes more
than 16000 times, this can overflow an internal counter, and crash the AVM.
This can typically be seen on long running appserver agents. Trimming agents
periodically can avoid this problem.


PSC00298563
=============================
Calling the Parse() method on a JSON string containing an open comment ("/* ")
will hang the process, using 100% of the CPU.


PSC00297164
=============================
OS-DELETE ... RECURSIVE will not remove directories if one of the
sub-directories has a dot in its name.


PSC00296778
=============================
The OpenEdge Web Service client specifies xsi:nil="1" in a SOAP request for
elements that are defined in the WSDL's XML Schema as minOccurs="0".


PSC00294995
=============================
A unique FIND ... WHERE ... BEGINS  statement can return the wrong record if
the database is using an ICU collation, or for a temp-table, if the session is
using an ICU collation for -cpcoll. An example of this is where there is more
than one record that BEGINS with the required expression, but the unique FIND
returns one record instead of an error. 


PSC00293727
=============================
Query with OUTER-JOIN and BREAK-BY on a datetime(-tz) field crashes on
GET-NEXT(). This happens when there is a parent record with no children.


PSC00291314
=============================
The AVM can crash under the following circumstances:
- the -checkwidth 1 parameter is used
- while loading a .df file containing a field of type CHARACTER that has an
initial value other than ""
- the number of fields being added to a table from the .df file is greater than
the number of fields already in the table (e.g. the table contains 3 fields and
the .df file contains 5 new fields for that table)

Removing the -checkwidth 1 parameter for the .df load will allow the .df file
to be loaded without problems.


PSC00287358
=============================
If the Linux ABL client happens to be executing the localtime() function when a
SIGUSR1 is received, the client will hang while trying to generate the
protrace. The generate protrace file will contain only the following text:
PROGRESS stack trace as of 


PSC00267928
=============================
The compiler will generate error "Class method 'MethodName' has been referenced
as though it were a variable. (12929)" if you run this statement and the method
MethodName takes an input parameter:

run 'abc' on server SampleClass:MethodName('').


PSC00244965
=============================
COPY-LOB with UTF-8 client, creates file names with UTF-8 values
****************************************
COPY-LOB from a memptr to a file creates filenames with UTF-8 character values.
 This means that the files when viewed in Windows Explorer seem to have multi
byte character values that corrupt the expected file name.



k. Management

PSC00320435
=============================
Unable to use I18N characters for table partitioning policy details in OE
Management/Explorer 


PSC00319957
=============================
Progress OpenEdge 11.2 - Directory Traversal Vulnerability CVE: 2014-8555


PSC00319087
=============================
Auto-discovery is not fully disabled when set to false in
DLC\properties\management.properties.


PSC00317809
=============================
Unable to create / edit TP policy with -d dmy in OE Explorer/Management.


PSC00316532
=============================
An incorrect (false error) alert is being thrown by (MSS/Oracle/ODBC)
Dataserver broker LogFileMonitor under OE Management.


PSC00313305
=============================
OE Explorer error window is missing database path separators when a database is
started with dbman after opening the Database Control page in OE Management and
then trying to start the same database with OE Management.


PSC00312802
=============================
Accessing 2 versions of OE Management (or Explorer) within 1 browser can lead
to being asked for re-login onto 11.4 again.


PSC00311233
=============================
OEM Default_Mail_Action fails with 9612 error


PSC00310511
=============================
The DataAdminService GetUsers method is slow with large numbers of _user
records when connected to a remote database.



PSC00310339
=============================
The search text message for  OE_Replication> TCPIP_communication_error should
be 10664.



PSC00307730
=============================
OConcurrentModificationException when committing changes to resource watch
configuration for new resources
Error reads:
OConcurrentModificationException : Cannot UPDATE the record <number>1 because
the version is not the latest.


PSC00299010
=============================
No data for memory and virtual memory on a machine with unused swap (NaN for
system.memory.Memory).


PSC00280635
=============================
The DataAdminService should have an option to tell that the passwords that are
passed are encoded.


PSC00279881
=============================
DataCompactionUnlock job allows assigning wrong resource despite it's valid
only for FathomTrendDatabase.


PSC00261096
=============================
Improve error handling in the Extent class when the area and extent cannot be
saved because the database is not connected directly through shared memory.
This issue also applies to the utility classes for proutil, currently, merge,
split and deallocate. 


PSC00252828
=============================
OEM "Resources" customized view is not saved
****************************************
Every time one returns to the resources screen, the whole resource set is
displayed with the default settings. The previously set criteria are not saved.

There is no option to save or set the default criteria when opening the
resource screen.  The following settings are not saved:

- Position of the columns
- Column width
- Treeview expansion, enabling to show or hide some resources.


PSC00234774
=============================
After restarting OE Management (AdminServer) you might get an 9802 log file not
found error/alert, despite the fact that the file is present on the server.


PSC00221930
=============================
Cannot disable "LogFileNameChanged" alert in OE Management
****************************************
When ubroker logfile threshold limit is set, "LogFileNameChanged" can generate
many alerts. This is a "hard coded" alert at this time. There is no way to
disable this alert. 


PSC00212841
=============================
OpenEdge Explorer: cannot trim all AppServers
****************************************
Using Progress Explorer, a positive value of minSrvrInstance allows all
appservers to be manually trimmed. This is no longer the case using OE Explorer
management console.



l. NETUI

PSC00312431
=============================
When setting the Localizable attribute to TRUE	for a Form containing a User
Control (ABL inherited from .NET), the value(s) set in the property sheet for
any CHAR or LONGCHAR property of the User Control will not get set at runtime.
.


PSC00260586
=============================
System.IO.FileStream.Read() method throwing ArgumentNullException
****************************************
When reading a file in ABL using .NET by calling FileStream:Read() it throws an
ArgumentNullException at runtime even though the ByteArray passed in for the
first argument is not null.



m. OEBPM

PSC00305703
=============================
Cannot update common value for ABL dataslots from Instance Manager > Instances


PSC00294337
=============================
For Spanish User, the label for DueDate appears larger than other column
headers.


PSC00290159
=============================
Swim lane labels containing multi-byte characters (such as labels in Chinese,
Japanese etc. ) are rendered incorrectly on PSV Chart View page on BPM Portal.


PSC00278360
=============================
The DLC variable definition in the startdb/stopdb for OEBPS database cause the
scripts to not work if the host machine has more than one OpenEdge
installation.



n. Open Client

PSC00311246
=============================
When generating a Java proxy and the name of the AppObject differs only by case
from the Package name, error 7455 occurs:

"The first node of the Package cannot be the same value as any AppObject,
SubAppObject or ProcObject name."


PSC00308595
=============================
Complex dataset definitions (datasets with more than 2 tables) may not
serialize properly


PSC00308592
=============================
ProxyGen is not removing hyphens froma	method name which is causing the
compilation of the proxy to fail. Also, it is removing the hyphen sometimes
when it should not be i.e. when referencing the TableName  Ex.
Tables["dt_hypHen"]; should be: Tables["dt_hyp-hen"};


PSC00305578
=============================
A ProDataSet handle output parameter causes the following exception to be
thrown when using Temp-Tables that contain DATE EXTENT fields:

com.progress.open4gl.Open4GLException: java.util.Vector cannot be cast to
java.util.GregorianCalendar


PSC00304369
=============================
When connecting from host A to a non-existent / unavailable AppServer on host B
through a NameServer on host B, the Open4GLException incorrectly refers to host
A (should be B).


PSC00296019
=============================
The Progress.Open4GL.RunTimeProperties.TcpClientRetry and
Progress.Open4GL.RunTimeProperties.TcpClientRetryInterval runtime properties
for the .NET Open Client do not seem to have effect in OpenEdge 10.2B08. The
.NET Open Client seems to wait indefinitely for a response.



o. PDSOE

PSC00316807
=============================
Duplicate ABL Consoles appear in Progress Developer Studio for OpenEdge.


PSC00314576
=============================
When starting a launch configuration created in OE 11.3 (project was
re-imported into newly created oe11.4 workspace).


PSC00313442
=============================
Searching with PDSOE using the new Find References feature can result in a
NullPointerexception in the woprkspace .log file.  


PSC00312768
=============================
"Progress OpenEdge" option itself is missing from the right click context menu
of search results in 11.4. This is a regression issue.


PSC00309657
=============================
HTML5 editor error in browser when opening Mobile App Builder from Progress
Developer Studio O, followed by the Oh No! error page.


PSC00307737
=============================
REST Resource URI Editor does not recognize some abbreviations for ABL types
like i for int


PSC00306568
=============================
An error "The current project is not associated with any active database
connection" is displayed when creating a new business entity in Developer
Studio when a database is indeed connected.


PSC00289881
=============================
Under the following conditions when using Visual Designer, the AVM terminates
with an "Out of memory" error:
1. A form which contains user controls is open in Visual Designer.
2. The form is also open in the source code editor.
3. The Properties view is open in Visual Designer.
4. The user toggles between Visual Designer and the editor, opening user
controls and editing the code in their event handlers.


PSC00284452
=============================
For remote databases, the New Business Entity wizard shows the following error
message even though there is a connection to the database:
   
The current project is not associated with any active database connection.


PSC00257927
=============================
Replace the classic wait-for with the .NET equivalent in _server.p to allow
running .Net windows in the ABL project session.  


PSC00254774
=============================
Improvement for automatic completion of quote and double-quote


PSC00164527
=============================
The auto-completion does not work for certain widgets. The possible attributes
and methods are not displayed.



p. REST Adapter

PSC00311822
=============================
The requirements for the OpenEdge REST Services need to be documented. One of
those is a Java Container that uses the Java Servlet API 3.0.


PSC00307061
=============================
Cannot access Tomcat Manager app using valid credentials in Tomcat bundled with
OpenEdge 11.4



q. Replication

PSC00311834
=============================
Target ERO Clients crash while querying a table using the IDXMOVE (source)
index
cxSearchTree: ERO Reader Invalid block number 0 found on a find operation -
operation failed 


PSC00207385
=============================
Can't transition target database created online
****************************************
If the source database is enabled online and a target is created from that, you
can't transition the target database if the source database hasn't been
restarted before the transition.



r. SQL

PSC00312227
=============================
Certain incorrect password values could be used to successfully authenticate a
given user, when connecting to the database.
The incorrect values were not the user's actual password. The actual password
still functioned correctly.
For reasons of security and customer safety, the incorrect values are not
described in more detail in this Description.

This problem is fixed in the current release. Only the user's correct password
can be used to authenticate the user.


PSC00310851
=============================
In a multi-database ODBC setup if we try to access the table '_aud-audit-data'
for the auxiliary database, permission denied error is thrown even though
auditing is enabled for both primary and auxiliary databases and necessary
permission is also granted for both databases.
However this problem is not faced in case of the primary database only, where
the table '_aud-audit-data' is accessed successfully for the primary database.
Also, for a single database ODBC setup, this SQL query is working fine.
Example:
1)	Create two databases db1 and db2.
2)	Enable auditing for both primary and auxiliary database.
3)	Start both databases on different ports.
4)	Grant audit_admin to both databases:
	  GRANT AUDIT_ADMIN TO <user>
5)	Connect to db1 database using sqlexp.
6)	Connect to the auxiliary database using the SQL command:
	  CONNECT '/db/db2' AS CATALOG db2
7)	Fetch audit table for the auxiliary database:
	  Select * from db2.pub.'_aud-audit-data';  
8)	Observe error - permission denied (7677).


PSC00310491
=============================
Ability to have ODBC/JDBC clients log their IP address when they connect to the
database via an _sqlsrv2 process.


PSC00308808
=============================
The SQL REPLACE function fails when the replacement value is an empty string.
For example,

	    REPLACE('abcd', 'bc', '')

This example will returns 'abcd' rather than 'ad'.
This problem exists in all OpenEdge sql releases prior to the current service
pack 11.3.3.
This problem is fixed in version 11.3.3.


PSC00305472
=============================
INSERT of a 31 digit number into a DECIMAL field using a  Non Parameterized
Insert statement succeeds while INSERT of a 31 digit number into the same
DECIMAL field using a  Parameterized Insert statement generates the error:
"Overflow error (7485)"


PSC00305397
=============================
VIEW created using SELECT CAST(REPLACE(column,"char",chr(0)) AS INT) does not
return results)


PSC00298880
=============================
Prior to 11.3.3, large SQL-92 Stored-Procedure's definition stored in the
system table pub."_SysProctext" might be incorrect. This is fixed in 11.3.3. 



PSC00297895
=============================
Found High CPU Utilization when performing heavy volume of record updates.


PSC00288807
=============================
ODBC SQLPrepare() api call fails with error 7481 when adding an integer to the
result of Cast or Convert functions in parameterized queries.


PSC00283707
=============================
MDBQ error reporting is enhanced to give more information in case errors during
parsing property file and while adding auxiliary databases. These messages will
be printed to connection log file.

The name and location of the connection log are described in the SQL Reference
manual, under the SET PRO_CONNECT LOG statement.


PSC00262747
=============================
Passing negative numbers to Stored Procedures crashes _sqlsrv2
****************************************
The SQL Server crashes if a negative integer parameter is passed on to a Stored
Procedure.


PSC00260847
=============================
CREATE TABLE causes internal error at 11341 in ssm.cxx
****************************************
When performing a CREATE TABLE in a large transaction, the following error is
returned:

[DataDirect][OpenEdge JDBC Driver][OpenEdge] Encountered internal error in SQL
ENGINE at 11318 in Z:/vobs_sql/sql/src/rds/ssm.cxx. Contact Progress Technical
Support


PSC00260732
=============================
ODBC driver hangs while fetching special character data
****************************************
An ODBC client hangs when the driver is trying to fetch more than 16383 special
characters. This issue has been fixed. 


PSC00255656
=============================
Large IN predicate sets degrade performance or crash SQL session
****************************************
An SQL query with large IN predicates of set of elements degrades the query
performance and can crash the SQL ODBC or JDBC session.

The level of performance degredation is proportional to the number of elements
in the IN predicate set.  Increasing the number of elements in the IN
predicates set will ultimately crash the session.


PSC00250487
=============================
Enabling SQL Statement tracing crashes the server
****************************************
The SQL Server crashes if a long statement is executed after SQL Statement
logging has been enabled.


PSC00248849
=============================
Creation and use of "sysprogress" as tenant user name is not allowed. The user
"sysprogress" can only be created with default tenancy.

This problem was not detected in OpenEdge releases before Service Pack 11.3.3
and various internal errors could occur if a tenant named "sysprogress" 
connected to the OpenEdge sql server.
This restriction on use of "sysprogress" is now enforced as of 11.3.3.


PSC00247414
=============================
sqlschema utility fails silent when sql engine throws error
****************************************
sqlschema utility fails silently after dumping definitions of few tables when
sql engine throws error. Sqlschema fails to print error message that is
returned by sql engine.


PSC00227812
=============================
ODBC driver retrieves column names with hyphens as not updatable
****************************************
ODBC driver returns attribute SQL_DESC_UPDATABLE as 0 for columns with hyphens
in their names when the columns are in fact updatable.



s. Server Technology

PSC00305173
=============================
The timeout error message triggered by the -clientConnectTimeout parameter is
missing error number 9407



t. TTY

PSC00310680
=============================
The cursor may jump to the end of the line while editing text in character
mode. The cursor immediately returns to the correct position.



u. UI Controls

PSC00302641
=============================
The Appearance Image Editor that is shown when choosing an image to display
with an infragistics control remembers its last position and always displays
there even if it was on a secondary monitor and the current session is only
using one monitor.  This causes the appearance of the session hanging.

Note that this same behavior occurs in MS Visual Studio with Infragistics
controls only.



v. Web Services Adapter

PSC00318499
=============================
When using the RETURN ERROR statement with a Web Service procedure, the WSA
response gets double escaped.


PSC00314766
=============================
The WSA causes a memory leak in Apache Tomcat due the usage of ThreadLocal.
When Tomcat is shutdown the following error is returned:

-------------------------
SEVERE: The web application [/wsa] created a ThreadLocal with key of type
[com.progress.common.ehnlog.WsaLogContext$1] (value
[com.progress.common.ehnlog.WsaLog
Context$1@700a2462]) and a value of type [java.lang.String] (value []) but
failed to remove it when the web application was stopped. Threads are going to
be renewed over time to try and avoid a probable memory leak.
-------------------------


PSC00313131
=============================
Random TCP port opened when starting WSA stays open even after shutting down
WSA



w. WebSpeed

PSC00316555
=============================
Setting WebSpeed STATE_AWARE_ENBALED to NO causes error 1428 when used html
mapped web object application.


PSC00315521
=============================
"SESSION:BATCH-MODE" returns "no" for a webspeed agent.


PSC00310935
=============================
useConnId CGI variable remains 0 (zero) with script file (.wsc) configured to
use direct connection to the Webspeed broker.


PSC00306352
=============================
The wsisa.dll messenger has vulnerabilities which make it possible to execute a
Denial of Service (DoS) attack.


PSC00305895
=============================
When using the messenger script file (cgiip.wsc), the CGI variable 'useConnId'
is empty.



---------------------------------------
Third Party Acknowledgments
---------------------------------------


Release Notes - Documentation Third Party Acknowledgements

One or more products in the Progress OpenEdge v11.5 release includes
third party components covered by licenses that require that the
following documentation notices be provided.  If changes in third party
components occurred for the current release of the Product, the
following Third Party Acknowledgements may contain notice updates to any
earlier versions provided in documentation or README file.

Progress OpenEdge v11.5 may incorporate ANT v1.5.4.  Such technology is
subject to the following terms and conditions: The Apache Software
License, Version 1.1, applies to all versions of up to ant 1.6.0
included.  The Apache Software License, Version 1.1 - Copyright (C)
2000-2003 The Apache Software Foundation.  All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met: 1.  Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.  2.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.  3.
The end-user documentation included with the redistribution, if any,
must include the following acknowledgment:  "This product includes
software developed by the Apache Software Foundation
(http://www.apache.org/)." Alternately, this acknowledgment may appear
in the software itself, if and wherever such third-party acknowledgments
normally appear.  4.  The names "Ant" and "Apache Software Foundation"
must not be used to endorse or promote products derived from this
software without prior written permission.  For written permission,
please contact apache@apache.org.  5.  Products derived from this
software may not be called "Apache", nor may "Apache" appear in their
name, without prior written permission of the Apache Software
Foundation.  THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS  FOR A PARTICULAR  PURPOSE ARE
DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS  INTERRUPTION)  HOWEVER CAUSED AND ON ANY  THEORY
OF LIABILITY,  WHETHER  IN CONTRACT,  STRICT LIABILITY,  OR TORT
(INCLUDING  NEGLIGENCE OR  OTHERWISE) ARISING IN  ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many
individuals on behalf of the Apache Software Foundation.  For more
information on the Apache Software Foundation, please see
<http://www.apache.org/>.

Progress OpenEdge v11.5 may incorporate Apache Avalon 2002/08/06, Apache
Batik v1.1, Apache Jakarta POI v1.1, Apache POI 2003/05/14, Regexp (Pure
Java Regular Expression) v1.2, and XMLTask v1.15.1  from The Apache
Software Foundation.  Such technologies are subject to the following
terms and conditions:  The Apache Software License, Version 1.1
Copyright (c) 2000 The Apache Software Foundation.  All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met: 1.  Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.  2.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.  3.
The end-user documentation included with the redistribution, if any,
must include the following acknowledgment: "This product includes
software developed by the Apache Software Foundation
(http://www.apache.org/)." Alternately, this acknowledgment may appear
in the software itself, if and wherever such third-party acknowledgments
normally appear.  4.  The names "Apache" and "Apache Software
Foundation" must not be used to endorse or promote products derived from
this software without prior written permission.  For written permission,
please contact apache@apache.org.  5.  Products derived from this
software may not be called "Apache", nor may "Apache" appear in their
name, without prior written permission of the Apache Software
Foundation.  THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This
software consists of voluntary contributions made by many individuals on
behalf of the Apache Software Foundation.  For more information on the
Apache Software Foundation, please see <http://www.apache.org/>.
Portions of this software are based upon public domain software
originally written at the National Center for Supercomputing
Applications, University of Illinois, Urbana-Champaign.

Progress OpenEdge v11.5 may incorporate Apache JAXP v1.3.04 from The
Apache Software Foundation.  Such technology is subject to the following
terms and conditions:  The Apache Software License, Version 1.1
Copyright (c) 1999-2003 The Apache Software Foundation.  All rights
reserved.  Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met: 1.  Redistributions of source code must retain the
above copyright notice, this list of conditions and the following
disclaimer.  2.  Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.  3.  The end-user documentation included with the
redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the Apache Software
Foundation (http://www.apache.org/)." Alternately, this acknowledgment
may appear in the software itself, if and wherever such third-party
acknowledgments normally appear.  4.  The names "Xalan" and "Apache
Software Foundation" must not be used to endorse or promote products
derived from this software without prior written permission.  For
written permission, please contact apache@apache.org.  5.  Products
derived from this software may not be called "Apache", nor may "Apache"
appear in their name, without prior written   permission of the Apache
Software Foundation.  THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE
FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.  This
software consists of voluntary contributions made by many individuals on
behalf of the Apache Software Foundation and was originally based on
software copyright (c) 1999, Lotus Development Corporation.,
http://www.lotus.com.  For more information on the Apache Software
Foundation, please see http://www.apache.org/.

Progress OpenEdge v11.5 may incorporate Crimson v1.1.3 as part of 1PDT
(Progress Extensions for Eclipse) v2.4.1.  Such technology is subject to
the following terms and conditions:  The Apache Software License,
Version 1.1 Copyright (c) 1999-2003 The Apache Software Foundation.  All
rights reserved.  Redistribution and use in source and binary forms,
with or without modification, are permitted provided that the following
conditions are met:  1.  Redistributions of source code must retain the
above copyright notice, this list of conditions and the following
disclaimer.  2.  Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.  3.  The end-user documentation included with the
redistribution, if any, must include the following acknowledgment: "This
product includes software developed by the Apache Software Foundation
(http://www.apache.org/)." Alternately, this acknowledgment may appear
in the software itself, if and wherever such third-party acknowledgments
normally appear.  4.  The names "Xerces" and "Apache Software
Foundation" must not be used to endorse or promote products derived from
this software without prior written permission.  For written permission,
please contact apache@apache.org.  5.  Products derived from this
software may not be called "Apache", nor may "Apache" appear in their
name, without prior written permission of the Apache Software
Foundation.  THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This
software consists of voluntary contributions made by many individuals on
behalf of the Apache Software Foundation and was originally based on
software copyright (c) 1999, International Business Machines, Inc.,
http://www.ibm.com.  For more information on the Apache Software
Foundation, please see <http://www.apache.org/>.

Progress OpenEdge v11.5 may incorporate jfor v0.7.2 from jfor.  Such
technology is subject to the following terms and conditions: jfor
Apache-Style Software License.  Copyright (c) 2002 by the jfor project.
All rights reserved.  Redistribution and use in source and binary forms,
with or without modification, are permitted provided that the following
conditions are met: 1.  Redistributions of source code must retain the
above copyright notice, this list of conditions and the following
disclaimer.  2.  Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.  3.  The end-user documentation included with the
redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the jfor project
(http://www.jfor.org)." Alternately, this acknowledgment may appear in
the software itself, if and wherever such third-party acknowledgments
normally appear.  4.  The name "jfor" must not be used to endorse or
promote products derived from this software without prior written
permission.  For written permission, please contact info@jfor.org.  5.
Products derived from this software may not be called "jfor", nor may
"jfor" appear in their name, without prior written permission of
info@jfor.org.  THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED.  IN NO EVENT SHALL THE JFOR PROJECT OR ITS CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,  EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate Apache LogKit v1.2 from The
Apache Software Foundation.  Such technologies are subject to the
following terms and conditions:  The Apache Software License, Version
1.1 -- Copyright (C) 1997-2003 The Apache Software Foundation.  All
rights reserved.  Redistribution and use in source and binary forms,
with or without modification, are permitted provided that the following
conditions are met: 1.  Redistributions of source code must retain the
above copyright notice, this list of conditions and the following
disclaimer.  2.  Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.  3.  The end-user documentation included with the
redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the Apache Software
Foundation (http://www.apache.org/)." Alternately, this acknowledgment
may appear in the software itself, if and wherever such third-party
acknowledgments normally appear.  4.  The names "LogKit", "Jakarta" and
"Apache Software Foundation" must not be used to endorse or promote
products derived from this software without prior written permission.
For written permission, please contact apache@apache.org.  5.  Products
derived from this software may not be called "Apache", nor may "Apache"
appear in their name, without prior written permission of the Apache
Software Foundation.  THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS  FOR A PARTICULAR
PURPOSE ARE  DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE
FOUNDATION  OR ITS CONTRIBUTORS  BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,BUT
NOT LIMITED TO, PROCUREMENT  OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS  INTERRUPTION)  HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER  IN CONTRACT,  STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many
individuals on behalf of the Apache Software Foundation.  For more
information on the Apache Software Foundation, please see
<http://www.apache.org/>.

Progress OpenEdge v11.5 may incorporate Xerces for Java XML Parser
v2.6.2.  Such technology is subject to the following terms and
conditions: The Apache Software License, Version 1.1 Copyright (c) 1999
The Apache Software Foundation.  All rights reserved.  Redistribution
and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met: 1.
Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.  2.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.  3.
The end-user documentation included with the redistribution, if any,
must include the following acknowledgment: "This product includes
software developed by the Apache Software Foundation
(http://www.apache.org/)." Alternately, this acknowledgment may appear
in the software itself, if and wherever such third-party acknowledgments
normally appear.  4.  The names "Xerces" and "Apache Software
Foundation" must not be used to endorse or promote products derived from
this software without prior written permission.  For written permission,
please contact apache@apache.org.  5.  Products derived from this
software may not be called "Apache", nor may "Apache" appear in their
name, without prior written permission of the Apache Software
Foundation.  THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This
software consists of voluntary contributions made by many individuals on
behalf of the Apache Software Foundation and was originally based on
software copyright (c) 1999, International Business Machines, Inc.,
http://www.ibm.com.  For more information on the Apache Software
Foundation, please see <http://www.apache.org/>.

Progress OpenEdge v11.5 may incorporate SOAP v2.3.1 from Apache
Foundation.  Such technology is subject to the following terms and
conditions: The Apache Software License, Version 1.1
Copyright (c) 1999 The Apache Software Foundation.  All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1.  Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2.  Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3.  The end-user documentation included with the redistribution, if any,
must include the following acknowledgment: "This product includes
software developed by the Apache Software Foundation
(http://www.apache.org/)."
Alternately, this acknowledgment may appear in the software itself, if
and wherever such third-party acknowledgments normally appear.
4.  The names "SOAP" and "Apache Software Foundation" must not be used
to endorse or promote products derived from this software without prior
written permission.  For written permission, please contact
apache@apache.org.
5.  Products derived from this software may not be called "Apache", nor
may "Apache" appear in their name, without prior written permission of
the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN
NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many
individuals on behalf of the Apache Software Foundation.  For more
information on the Apache Software Foundation, please see
<http://www.apache.org/>.

Progress OpenEdge v11.5 may incorporate ANTLR (Another Tool for Language
Recognition) v2.7.6.  Such technology is subject to the following terms
and conditions: ANTLR 3 License [The BSD License] Copyright (c)
2003-2006, Terence Parr All rights reserved.  Redistribution and use in
source and binary forms, with or without modification, are permitted
provided that the following conditions are met:  Redistributions of
source code must retain the above copyright notice, this list of
conditions and the following disclaimer.  Redistributions in binary form
must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials
provided with the distribution.  Neither the name of the author nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate Castor v0.9.3 from castor.org.
Such technology is subject to the following terms and conditions:
Original Intalio license - Copyright 1999-2004 (C) Intalio Inc., and
others.  All Rights Reserved.  Redistribution and use of this software
and associated documentation ("Software"), with or without modification,
are permitted provided that the following conditions are met: 1.
Redistributions of source code must retain copyright statements and
notices.  Redistributions must also contain a copy of this document.  2.
Redistributions in   binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.  3.
The name "ExoLab" must not be used to endorse    or promote products
derived from this Software without prior written permission of Intalio
Inc.  For written permission, please contact info@exolab.org.  4.
Products derived from this Software may not be called "Castor" nor may
"Castor" appear in their names without prior written permission of
Intalio Inc.  Exolab, Castor and Intalio are trademarks of Intalio Inc.
5.  Due credit should be given to the ExoLab Project
(http://www.exolab.org/).  THIS SOFTWARE IS PROVIDED BY INTALIO AND
CONTRIBUTORS ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
INTALIO OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate Decimal Conversion Code (dtoa.c;
g_fmt.c; rnd_prod.s; decstrod.c; decstrtof.c; dmisc.c; gdtoa.c; gdtoa.h;
gdtoaimp.h; gethex.c; gmisc.c; hd_init.c; misc.c; smisc.c; strtodg.c;
strtord.c; sum.c; ulp.c).  Such technologies are subject to the
following terms and conditions: dtoa.c License: The author of this
software is David M. Gay.  Copyright (c) 1991, 2000, 2001 by Lucent
Technologies.  Permission to use, copy, modify, and distribute this
software for any purpose without fee is hereby granted, provided that
this entire notice is included in all copies of any software which is or
includes a copy or modification of this software and in all copies of
the supporting documentation for such software.  THIS SOFTWARE IS BEING
PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY.  IN
PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY REPRESENTATION OR
WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR
ITS FITNESS FOR ANY PARTICULAR PURPOSE. g_fmt.c License: The author of
this software is David M. Gay.  Copyright (c) 1991, 1996 by Lucent
Technologies.  Permission to use, copy, modify, and distribute this
software for any purpose without fee is hereby granted, provided that
this entire notice is included in all copies of any software which is or
includes a copy or modification of this software and in all copies of
the supporting documentation for such software.  THIS SOFTWARE IS BEING
PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY.  IN
PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY REPRESENTATION OR
WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR
ITS FITNESS FOR ANY PARTICULAR PURPOSE.
rnd_prod.s License: The author of this software is David M. Gay.
Copyright (c) 1991 by Lucent Technologies.  Permission to use, copy,
modify, and distribute this software for any purpose without fee is
hereby granted, provided that this entire notice is included in all
copies of any software which is or includes a copy or modification of
this software and in all copies of the supporting documentation for such
software.  THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS
OR IMPLIED WARRANTY.  IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES
ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE
MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR
PURPOSE. decstrtod.c License: The author of this software is David M.
Gay.  Copyright (C) 1998-2001 by Lucent Technologies All Rights Reserved
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that the copyright notice and this permission notice and warranty
disclaimer appear in supporting documentation, and that the name of
Lucent or any of its entities not be used in advertising or publicity
pertaining to distribution of the software without specific, written
prior permission.  LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS. IN NO EVENT SHALL LUCENT OR ANY OF ITS ENTITIES BE LIABLE FOR
ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. decstrtof.c
License: The author of this software is David M. Gay.  Copyright (C)
1998, 2000 by Lucent Technologies All Rights Reserved Permission to use,
copy, modify, and distribute this software and its documentation for any
purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies
and that both that the copyright notice and this permission notice and
warranty disclaimer appear in supporting documentation, and that the
name of Lucent or any of its entities not be used in advertising or
publicity pertaining to distribution of the software without specific,
written prior permission.  LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD
TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS. IN NO EVENT SHALL LUCENT OR ANY OF ITS ENTITIES BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. dmisc.c
License: The author of this software is David M. Gay.  Copyright (C)
1998 by Lucent Technologies All Rights Reserved Permission to use, copy,
modify, and distribute this software and its documentation for any
purpose and without fee is hereby granted, provided that the above
copyright notice appear in all copies and that both that the copyright
notice and this permission notice and warranty disclaimer appear in
supporting documentation, and that the name of Lucent or any of its
entities not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission.
LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
LUCENT OR ANY OF ITS ENTITIES BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF
USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE. gdtoa.c License: The author of this
software is David M. Gay.  Copyright (C) 1998, 1999 by Lucent
Technologies All Rights Reserved Permission to use, copy, modify, and
distribute this software and its documentation for any purpose and
without fee is hereby granted, provided that the above copyright notice
appear in all copies and that both that the copyright notice and this
permission notice and warranty disclaimer appear in supporting
documentation, and that the name of Lucent or any of its entities not be
used in advertising or publicity pertaining to distribution of the
software without specific, written prior permission.  LUCENT DISCLAIMS
ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL LUCENT OR
ANY OF ITS ENTITIES BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
THIS SOFTWARE. gdtoa.h License: The author of this software is David M.
Gay.  Copyright (C) 1998 by Lucent Technologies All Rights Reserved
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies
and that both that the copyright notice and this permission notice and
warranty disclaimer appear in supporting documentation, and that the
name of Lucent or any of its entities not be used in advertising or
publicity pertaining to distribution of the software without specific,
written prior permission.  LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD
TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS. IN NO EVENT SHALL LUCENT OR ANY OF ITS ENTITIES BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
gdtoaimp.h License: The author of this software is David M. Gay.
Copyright (C) 1998-2000 by Lucent Technologies All Rights Reserved
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that the copyright notice and this permission notice and warranty
disclaimer appear in supporting documentation, and that the name of
Lucent or any of its entities not be used in advertising or publicity
pertaining to distribution of the software without specific, written
prior permission.  LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS. IN NO EVENT SHALL LUCENT OR ANY OF ITS ENTITIES BE LIABLE FOR
ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. gethex.c
License: The author of this software is David M. Gay.  Copyright (C)
1998 by Lucent Technologies All Rights Reserved Permission to use, copy,
modify, and distribute this software and its documentation for any
purpose and without fee is hereby granted, provided that the above
copyright notice appear in all copies and that both that the copyright
notice and this permission notice and warranty disclaimer appear in
supporting documentation, and that the name of Lucent or any of its
entities not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission.
LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
LUCENT OR ANY OF ITS ENTITIES BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF
USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE. gmisc.c License: The author of this
software is David M. Gay.  Copyright (C) 1998 by Lucent Technologies All
Rights Reserved Permission to use, copy, modify, and distribute this
software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies
and that both that the copyright notice and this permission notice and
warranty disclaimer appear in supporting documentation, and that the
name of Lucent or any of its entities not be used in advertising or
publicity pertaining to distribution of the software without specific,
written prior permission.  LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD
TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS. IN NO EVENT SHALL LUCENT OR ANY OF ITS ENTITIES BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. hd_init.c
License: The author of this software is David M. Gay.  Copyright (C)
2000 by Lucent Technologies All Rights Reserved Permission to use, copy,
modify, and distribute this software and its documentation for any
purpose and without fee is hereby granted, provided that the above
copyright notice appear in all copies and that both that the copyright
notice and this permission notice and warranty disclaimer appear in
supporting documentation, and that the name of Lucent or any of its
entities not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission.
LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
LUCENT OR ANY OF ITS ENTITIES BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF
USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE. misc.c License: The author of this
software is David M. Gay.  Copyright (C) 1998, 1999 by Lucent
Technologies All Rights Reserved Permission to use, copy, modify, and
distribute this software and its documentation for any purpose and
without fee is hereby granted, provided that the above copyright notice
appear in all copies and that both that the copyright notice and this
permission notice and warranty  disclaimer appear in supporting
documentation, and that the name of Lucent or any of its entities not be
used in advertising or publicity pertaining to distribution of the
software without specific, written prior permission.  LUCENT DISCLAIMS
ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL LUCENT OR
ANY OF ITS ENTITIES BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
THIS SOFTWARE. smisc.c License: The author of this software is David M.
Gay.  Copyright (C) 1998, 1999 by Lucent Technologies All Rights
Reserved Permission to use, copy, modify, and distribute this software
and its documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that the copyright notice and this permission notice and warranty
disclaimer appear in supporting documentation, and that the name of
Lucent or any of its entities not be used in advertising or publicity
pertaining to distribution of the software without specific, written
prior permission.  LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS. IN NO EVENT SHALL LUCENT OR ANY OF ITS ENTITIES BE LIABLE FOR
ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. strtodg.c
License: The author of this software is David M. Gay.  Copyright (C)
1998-2001 by Lucent Technologies All Rights Reserved Permission to use,
copy, modify, and distribute this software and its documentation for any
purpose and without fee is hereby granted, provided that the above
copyright notice appear in all copies and that both that the copyright
notice and this permission notice and warranty disclaimer appear in
supporting documentation, and that the name of Lucent or any of its
entities not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission.
LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
LUCENT OR ANY OF ITS ENTITIES BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF
USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE. strtord.c License: The author of this
software is David M. Gay.  Copyright (C) 1998, 2000 by Lucent
Technologies All Rights Reserved Permission to use, copy, modify, and
distribute this software and its documentation for any purpose and
without fee is hereby granted, provided that the above copyright notice
appear in all copies and that both that the copyright notice and this
permission notice and warranty disclaimer appear in supporting
documentation, and that the name of Lucent or any of its entities not be
used in advertising or publicity pertaining to distribution of the
software without specific, written prior permission.  LUCENT DISCLAIMS
ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL LUCENT OR
ANY OF ITS ENTITIES BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
THIS SOFTWARE. sum.c License: The author of this software is David M.
Gay.  Copyright (C) 1998 by Lucent Technologies All Rights Reserved
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that the copyright notice and this permission notice and warranty
disclaimer appear in supporting documentation, and that the name of
Lucent or any of its entities not be used in advertising or publicity
pertaining to distribution of the software without specific, written
prior permission.  LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS. IN NO EVENT SHALL LUCENT OR ANY OF ITS ENTITIES BE LIABLE FOR
ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ulp.c License:
The author of this software is David M. Gay.  Copyright (C) 1998, 1999
by Lucent Technologies All Rights Reserved Permission to use, copy,
modify, and distribute this software and its documentation for any
purpose and without fee is hereby granted, provided that the above
copyright notice appear in all copies and that both that the copyright
notice and this permission notice and warranty disclaimer appear in
supporting documentation, and that the name of Lucent or any of its
entities not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission.
LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
LUCENT OR ANY OF ITS ENTITIES BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF
USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.

Progress OpenEdge v11.5 may incorporate DOM4J v1.6.1 from MetaStuff,
Ltd.  Such technology is subject to the following terms and conditions:
Copyright 2001-2005 (C) MetaStuff, Ltd.  All Rights Reserved.
Redistribution and use of this software and associated documentation
("Software"), with or without modification, are permitted provided that
the following conditions are met: 1.  Redistributions of source code
must retain copyright statements and notices.  Redistributions must also
contain a copy of this document.  2.  Redistributions in binary form
must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials
provided with the distribution.  3.  The name "DOM4J" must not be used
to endorse or promote products derived from this Software without prior
written permission of MetaStuff, Ltd.  For written permission, please
contact dom4j-info@metastuff.com.  4.  Products derived from this
Software may not be called "DOM4J" nor may "DOM4J" appear in their names
without prior written permission of MetaStuff, Ltd.  DOM4J is a
registered trademark of MetaStuff, Ltd.  5.  Due credit should be given
to the DOM4J Project - http://www.dom4j.org THIS SOFTWARE IS PROVIDED BY
METASTUFF, LTD. AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN
NO EVENT SHALL METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate GraphicsMagick v1.3.14 from
GraphicsMagick Group.  Such technology is subject to the following terms
and conditions:
..  This text is in reStucturedText format, so it may look a bit odd.
..  See http://docutils.sourceforge.net/rst.html for details.
======================================
GraphicsMagick Copyrights and Licenses
======================================
This file is part of the GraphicsMagick software distributed by the
GraphicsMagick Group.
  [*Please note that the legal community considers 15 or more total
  lines of code or text (not necessarily contiguous) to
  be significant for the purposes of copyright.  Repeated changes such
  as renaming a symbol has similar significance
  to changing one line of code.*]
The licenses which components of this software fall under are as
follows.
1) In November 2002, the GraphicsMagick Group created GraphicsMagick
from ImageMagick Studio's ImageMagick and applied the "MIT" style
license:  Copyright (C) 2002 - 2012 GraphicsMagick Group
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions: The above copyright notice and this permission
notice shall be included in all copies or substantial portions of the
Software.  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
2) In October 1999, ImageMagick Studio assumed the responsibility for
the development of ImageMagick (forking from the distribution by E. I.
du Pont de Nemours and Company) and applied a new license:
Copyright (C) 2002 ImageMagick Studio, a non-profit organization
dedicated to making software imaging solutions freely available.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files
("ImageMagick"), to deal in ImageMagick without restriction, including
without limitation
  the rights to use, copy, modify, merge, publish, distribute,
  sublicense, and/or sell copies of ImageMagick, and to permit persons
  to whom the ImageMagick is furnished to do so, subject to the
  following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of ImageMagick.
The software is provided "as is", without warranty of any kind, express
or implied, including but not limited to the warranties of
merchantability, fitness for a particular purpose and noninfringement.
In no event shall ImageMagick Studio be liable for any claim, damages or
other liability, whether in an action of contract, tort or otherwise,
arising from, out of or in connection with ImageMagick or the use or
other dealings in ImageMagick.
Except as contained in this notice, the name of the ImageMagick Studio
shall not be used in advertising or otherwise to promote the sale, use
or other dealings in ImageMagick without prior written authorization
from the ImageMagick Studio.
3) From 1991 to October 1999 (through ImageMagick 4.2.9), ImageMagick
was developed and distributed by E. I. du Pont de Nemours and Company:
Copyright 1999 E. I. du Pont de Nemours and Company
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files
("ImageMagick"), to deal in ImageMagick without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of ImageMagick, and to permit
persons to whom the ImageMagick is furnished to do so, subject to the
following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of ImageMagick.
The software is provided "as is", without warranty of any kind, express
or implied, including but not limited to the warranties of
merchantability, fitness for a particular purpose and noninfringement.
In no event shall E. I. du Pont de Nemours and Company be liable for any
claim, damages or other liability, whether in an action of contract,
tort or otherwise, arising from, out of or in connection with
ImageMagick or the use or other dealings in ImageMagick.
Except as contained in this notice, the name of the E. I. du Pont de
Nemours and Company shall not be used in advertising or otherwise to
promote the sale, use or other dealings in ImageMagick without prior
written authorization from the E. I. du Pont de Nemours and Company.
4) The GraphicsMagick Base64Decode() and Base64Encode() functions are
based on source code obtained from OpenSSH. This source code is
distributed under the following license:  Copyright (c) 2000 Markus
Friedl.  All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1.  Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2.  Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR \`\`AS IS\'\' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
5) Many of the pattern images in coders/logo.c are derived from XFig,
which is distributed under the following license:
  | FIG : Facility for Interactive Generation of figures
  | Copyright (c) 1985-1988 by Supoj Sutanthavibul
  | Parts Copyright (c) 1989-2000 by Brian V. Smith
  | Parts Copyright (c) 1991 by Paul King
Any party obtaining a copy of these files is granted, free of charge, a
full and unrestricted irrevocable, world-wide, paid up, royalty-free,
nonexclusive right and license to deal in this software and
documentation files (the "Software"), including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons who receive
copies from any such party to do so, with the only requirement being
that this copyright notice remain intact.
6) The documentation for the composition operators is copied from the
rlecomp manual page, which is authored by Rod Bogart and John W.
Peterson.  Rlecomp is part of the Utah Raster Toolkit distributed by the
University of Michigan and the University of Utah.  The copyright for
this manual page is as follows: Copyright (c) 1986, University of Utah
This software is copyrighted as noted below.  It may be freely copied,
modified, and redistributed, provided that the copyright notice is
preserved on all copies.
There is no warranty or other guarantee of fitness for this software, it
is provided solely "as is".  Bug reports or fixes may be sent to the
author, who may or may not act on them as he desires.
You may not include this software in a program or other software product
without supplying the source, or without informing the end-user that the
source is available for no extra charge.
If you modify this software, you should include a notice giving the name
of the person performing the modification, the date of modification, and
the reason for such modification.
7) The source code comprising swab.c is originally derived from libtiff
which has the following license:
  | Copyright (c) 1988-1997 Sam Leffler
  | Copyright (c) 1991-1997 Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software and
its documentation for any purpose is hereby granted without fee,
provided  that (i) the above copyright notices and this permission
notice appear in all copies of the software and related documentation,
and (ii) the names of Sam Leffler and Silicon Graphics may not be used
in any advertising or publicity relating to the software without the
specific, prior written permission of Sam Leffler and Silicon Graphics.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND,
EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO
EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL,
INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY
DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER
OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF
LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
OF THIS SOFTWARE.
8) The C++ API known as "Magick++", and which resides in the Magick++
directory, is distributed under the following license: Copyright 1999 -
2003 Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Permission is hereby granted, free of charge, to any person obtaining a
copy of the source files and associated documentation files
("Magick++"), to deal in Magick++ without restriction, including without
limitation of the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of Magick++, and to permit
persons to whom the Magick++ is furnished to do so, subject to the
following conditions:
This copyright notice shall be included in all copies or substantial
portions of Magick++.  The copyright to Magick++ is retained by its
author and shall not be subsumed or replaced by any other copyright.
The software is provided "as is", without warranty of any kind, express
or implied, including but not limited to the warranties of
merchantability, fitness for a particular purpose and noninfringement.
In no event shall Bob Friesenhahn be liable for any claim, damages or
other liability, whether in an action of contract, tort or otherwise,
arising from, out of or in connection with Magick++ or the use or other
dealings in Magick++.
9) The GraphicsMagick HaldClutImagePixels() function in magick/hclut.c
is based on source code from the HaldCLUT package by Eskil Steenberg
(http://www.quelsolaar.com/technology/clut.html) which is distributed
under the following license: Copyright (c) 2005 Eskil Steenberg.  All
rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1.  Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2.  Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR \`\`AS IS\'\' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
10)  GraphicsMagick makes use of third-party "delegate" libraries to
support certain optional features.  These libraries bear their own
copyrights and licenses, which may be more or less restrictive than the
GraphicsMagick license.  For convenience, when GraphicsMagick is bundled
with (or compiled with) "delegate" libraries, a copy of the licenses for
these libraries is provided in a "licenses" directory.
--------------------------------------------------------------------------
...  |copy|   unicode:: U+000A9 ..  COPYRIGHT SIGN
Copyright |copy| GraphicsMagick Group 2002 - 2011

OVERVIEW and LEGAL ISSUES from jpeg.txt file (from GraphicsMagick):
The Independent JPEG Group's JPEG software
==========================================
README for release 6b of 27-Mar-1998
====================================
This distribution contains the sixth public release of the Independent
JPEG Group's free JPEG software.  You are welcome to redistribute this
software and to use it for any purpose, subject to the conditions under
LEGAL ISSUES, below.
Serious users of this software (particularly those incorporating it into
larger programs) should contact IJG at jpeg-info@uunet.uu.net to be
added to our electronic mailing list.  Mailing list members are notified
of updates and have a chance to participate in technical discussions,
etc.
This software is the work of Tom Lane, Philip Gladstone, Jim Boucher,
Lee Crocker, Julian Minguillon, Luis Ortiz, George Phillips, Davide
Rossi, Guido Vollbeding, Ge' Weijers, and other members of the
Independent JPEG
Group.  IJG is not affiliated with the official ISO JPEG standards
committee.
OVERVIEW
========
This package contains C software to implement JPEG image compression and
decompression.  JPEG (pronounced "jay-peg") is a standardized
compression
method for full-color and gray-scale images.  JPEG is intended for
compressing "real-world" scenes; line drawings, cartoons and other
non-realistic images are not its strong suit.  JPEG is lossy, meaning
that the output image is not exactly identical to the input image.
Hence you must not use JPEG if you have to have identical output bits.
However, on typical photographic images, very good compression levels
can be obtained with no visible change, and remarkably high compression
levels are possible if you can tolerate a low-quality image.  For more
details, see the references, or just experiment with various compression
settings.  This software implements JPEG baseline, extended-sequential,
and progressive compression processes.  Provision is made for supporting
all variants of these processes, although some uncommon parameter
settings aren't implemented yet.
For legal reasons, we are not distributing code for the
arithmetic-coding variants of JPEG; see LEGAL ISSUES.  We have made no
provision for supporting the hierarchical or lossless processes defined
in the standard.
We provide a set of library routines for reading and writing JPEG image
files, plus two sample applications "cjpeg" and "djpeg", which use the
library to perform conversion between JPEG and some other popular image
file formats.  The library is intended to be reused in other
applications.
In order to support file conversion and viewing software, we have
included considerable functionality beyond the bare JPEG coding/decoding
capability; for example, the color quantization modules are not strictly
part of JPEG decoding, but they are essential for output to colormapped
file formats or colormapped displays.  These extra functions can be
compiled out of the library if not required for a particular
application.  We have also included "jpegtran", a utility for lossless
transcoding between different JPEG processes, and "rdjpgcom" and
"wrjpgcom", two simple applications for inserting and extracting textual
comments in JFIF files.
The emphasis in designing this software has been on achieving
portability and flexibility, while also making it fast enough to be
useful.  In particular, the software is not intended to be read as a
tutorial on JPEG.  (See the REFERENCES section for introductory
material.)  Rather, it is intended to be reliable, portable,
industrial-strength code.  We do not claim to have achieved that goal in
every aspect of the software, but we strive for it.
We welcome the use of this software as a component of commercial
products.
No royalty is required, but we do ask for an acknowledgement in product
documentation, as described under LEGAL ISSUES.
LEGAL ISSUES
============
In plain English:
1.  We don't promise that this software works.  (But if you find any
bugs, please let us know!)
2.  You can use this software for whatever you want.  You don't have to
pay us.
3.  You may not pretend that you wrote this software.  If you use it in
a program, you must acknowledge somewhere in your documentation that
you've used the IJG code.
In legalese:
The authors make NO WARRANTY or representation, either express or
implied, with respect to this software, its quality, accuracy,
merchantability, or fitness for a particular purpose.  This software is
provided "AS IS", and you, its user, assume the entire risk as to its
quality and accuracy.
This software is copyright (C) 1991-1998, Thomas G. Lane.
All Rights Reserved except as specified below.
Permission is hereby granted to use, copy, modify, and distribute this
software (or portions thereof) for any purpose, without fee, subject to
these conditions:
(1) If any part of the source code for this software is distributed,
then this README file must be included, with this copyright and
no-warranty notice unaltered; and any additions, deletions, or changes
to the original files must be clearly indicated in accompanying
documentation.
(2) If only executable code is distributed, then the accompanying
documentation must state that "this software is based in part on the
work of the Independent JPEG Group".
(3) Permission for use of this software is granted only if the user
accepts full responsibility for any undesirable consequences; the
authors accept NO LIABILITY for damages of any kind.
These conditions apply to any software derived from or based on the IJG
code, not just to the unmodified library.  If you use our work, you
ought to acknowledge us.
Permission is NOT granted for the use of any IJG author's name or
company name in advertising or publicity relating to this software or
products derived from it.  This software may be referred to only as "the
Independent JPEG Group's software".
We specifically permit and encourage the use of this software as the
basis of commercial products, provided that all warranty or liability
claims are assumed by the product vendor.
ansi2knr.c is included in this distribution by permission of L. Peter
Deutsch, sole proprietor of its copyright holder, Aladdin Enterprises of
Menlo Park, CA.
ansi2knr.c is NOT covered by the above copyright and conditions, but
instead by the usual distribution terms of the Free Software Foundation;
principally, that you must include source code if you redistribute it.
(See the file ansi2knr.c for full details.)  However, since ansi2knr.c
is not needed as part of any program generated from the IJG code, this
does not limit you more than the foregoing paragraphs do.
The Unix configuration script "configure" was produced with GNU
Autoconf.
It is copyright by the Free Software Foundation but is freely
distributable.
The same holds for its supporting scripts (config.guess, config.sub,
ltconfig, ltmain.sh).  Another support script, install-sh, is copyright
by M.I.T. but is also freely distributable.
It appears that the arithmetic coding option of the JPEG spec is covered
by patents owned by IBM, AT&T, and Mitsubishi.  Hence arithmetic coding
cannot legally be used without obtaining one or more licenses.  For this
reason, support for arithmetic coding has been removed from the free
JPEG software.  (Since arithmetic coding provides only a marginal gain
over the unpatented Huffman mode, it is unlikely that very many
implementations will support it.)
So far as we are aware, there are no patent restrictions on the
remaining code.
The IJG distribution formerly included code to read and write GIF files.
To avoid entanglement with the Unisys LZW patent, GIF reading support
has been removed altogether, and the GIF writer has been simplified to
produce "uncompressed GIFs".  This technique does not use the LZW
algorithm; the resulting GIF files are larger than usual, but are
readable by all standard GIF decoders.
We are required to state that "The Graphics Interchange Format(c) is the
Copyright property of CompuServe Incorporated.  GIF(sm) is a Service
Mark property of CompuServe Incorporated."

Contents of png.txt file (from GraphicsMagick):
This copy of the libpng notices is provided for your convenience.  In
case of any discrepancy between this copy and the notices in the file
png.h that is included in the libpng distribution, the latter shall
prevail.
COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
If you modify libpng you may insert additional notices immediately
following this sentence.
libpng versions 1.0.7, July 1, 2000, through 1.2.0, September 1, 2001,
are Copyright (c) 2000 Glenn Randers-Pehrson and are distributed
according to the same disclaimer and license as libpng-1.0.6 with the
following individuals added to the list of Contributing Authors
   Simon-Pierre Cadieux
   Eric S. Raymond
   Gilles Vollant
and with the following additions to the disclaimer:
There is no warranty against interference with your enjoyment of the
library or against infringement.  There is no warranty that our efforts
or the library will fulfill any of your particular purposes or needs.
This library is provided with all faults, and the entire risk of
satisfactory quality, performance, accuracy, and effort is with the
user.
libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are
Copyright (c) 1998, 1999 Glenn Randers-Pehrson, and are distributed
according to the same disclaimer and license as libpng-0.96, with the
following individuals added to the list of Contributing Authors:
   Tom Lane
   Glenn Randers-Pehrson
   Willem van Schaik
libpng versions 0.89, June 1996, through 0.96, May 1997, are Copyright
(c) 1996, 1997 Andreas Dilger
Distributed according to the same disclaimer and license as libpng-0.88,
with the following individuals added to the list of Contributing
Authors:
   John Bowler
   Kevin Bracey
   Sam Bushell
   Magnus Holmgren
   Greg Roelofs
   Tom Tanner
libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright
(c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.  For the purposes of
this copyright and license, "Contributing Authors" is defined as the
following set of individuals:
   Andreas Dilger
   Dave Martindale
   Guy Eric Schalnat
   Paul Schmidt
   Tim Wegner
The PNG Reference Library is supplied "AS IS".  The Contributing Authors
and Group 42, Inc.  disclaim all warranties, expressed or implied,
including, without limitation, the warranties of merchantability and of
fitness for any purpose.  The Contributing Authors and Group 42, Inc.
assume no liability for direct, indirect, incidental, special,
exemplary, or consequential damages, which may result from the use of
the PNG Reference Library, even if advised of the possibility of such
damage.  Permission is hereby granted to use, copy, modify, and
distribute this source code, or portions hereof, for any purpose,
without fee, subject to the following restrictions:
1.  The origin of this source code must not be misrepresented.
2.  Altered versions must be plainly marked as such and must not be
misrepresented as being the original source.
3.  This Copyright notice may not be removed or altered from any source
or altered source distribution.
The Contributing Authors and Group 42, Inc.  specifically permit,
without fee, and encourage the use of this source code as a component to
supporting the PNG file format in commercial products.  If you use this
source code in a product, acknowledgment is not required but would be
appreciated.
A "png_get_copyright" function is available, for convenient use in
"about" boxes and the like:
   printf("%s",png_get_copyright(NULL));
Also, the PNG logo (in PNG format, of course) is supplied in the files
"pngbar.png" and "pngbar.jpg (88x31) and "pngnow.png" (98x31).
Libpng is OSI Certified Open Source Software.  OSI Certified Open Source
is a certification mark of the Open Source Initiative.
Glenn Randers-Pehrson
randeg@alum.rpi.edu
September 1, 2001

Contents of tiff.txt file (from GraphicsMagick):
Copyright (c) 1988-1997 Sam Leffler
Copyright (c) 1991-1997 Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software and
its documentation for any purpose is hereby granted without fee,
provided that (i) the above copyright notices and this permission notice
appear in all copies of the software and related documentation, and (ii)
the names of Sam Leffler and Silicon Graphics may not be used in any
advertising or publicity relating to the software without the specific,
prior written permission of Sam Leffler and Silicon Graphics.  THE
SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND,
EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL,
INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY
DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER
OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF
LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
OF THIS SOFTWARE.

Contents of zlib.txt file (from GraphicsMagick):
zlib 1.1.3 is a general purpose data compression library.  All the code
is thread safe.  The data format used by the zlib library is described
by RFCs (Request for Comments) 1950 to 1952 in the files
ftp://ds.internic.net/rfc/rfc1950.txt (zlib format), rfc1951.txt
(deflate format) and rfc1952.txt (gzip format).  These documents are
also available in other formats from
ftp://ftp.uu.net/graphics/png/documents/zlib/zdoc-index.html
All functions of the compression library are documented in the file
zlib.h (volunteer to write man pages welcome, contact jloup@gzip.org).
A usage example of the library is given in the file example.c which also
tests that the library is working correctly.  Another example is given
in the file minigzip.c.  The compression library itself is composed of
all source files except example.c and minigzip.c.
To compile all files and run the test program, follow the instructions
given at the top of Makefile.  In short "make test; make install" should
work for most machines.  For Unix: "configure; make test; make install"
For MSDOS, use one of the special makefiles such as Makefile.msc.
For VMS, use Make_vms.com or descrip.mms.
Questions about zlib should be sent to <zlib@quest.jpl.nasa.gov>, or to
Gilles Vollant <info@winimage.com> for the Windows DLL version.
The zlib home page is http://www.cdrom.com/pub/infozip/zlib/
The official zlib ftp site is ftp://ftp.cdrom.com/pub/infozip/zlib/
Before reporting a problem, please check those sites to verify that you
have the latest version of zlib; otherwise get the latest version and
check whether the problem still exists or not.
Mark Nelson <markn@tiny.com> wrote an article about zlib for the Jan.
1997 issue of  Dr.  Dobb's Journal; a copy of the article is available
in http://web2.airmail.net/markn/articles/zlibtool/zlibtool.htm
The changes made in version 1.1.3 are documented in the file ChangeLog.
The main changes since 1.1.2 are:
- fix "an inflate input buffer bug that shows up on rare but persistent
  occasions" (Mark)
- fix gzread and gztell for concatenated .gz files (Didier Le Botlan)
- fix gzseek(..., SEEK_SET) in write mode
- fix crc check after a gzeek (Frank Faubert)
- fix miniunzip when the last entry in a zip file is itself a zip file
  (J Lillge)
- add contrib/asm586 and contrib/asm686 (Brian Raiter)
  See http://www.muppetlabs.com/~breadbox/software/assembly.html
- add support for Delphi 3 in contrib/delphi (Bob Dellaca)
- add support for C++Builder 3 and Delphi 3 in contrib/delphi2 (Davide
Moretti)
- do not exit prematurely in untgz if 0 at start of block (Magnus
Holmgren)
- use macro EXTERN instead of extern to support DLL for BeOS (Sander
Stoks)
- added a FAQ file
plus many changes for portability.
Unsupported third party contributions are provided in directory
"contrib".  A Java implementation of zlib is available in the Java
Development Kit 1.1
http://www.javasoft.com/products/JDK/1.1/docs/api/Package-java.util.zip.html
See the zlib home page http://www.cdrom.com/pub/infozip/zlib/ for
details.
A Perl interface to zlib written by Paul Marquess
<pmarquess@bfsec.bt.co.uk>  is in the CPAN (Comprehensive Perl Archive
Network) sites, such as:
ftp://ftp.cis.ufl.edu/pub/perl/CPAN/modules/by-module/Compress/Compress-Zlib*
A Python interface to zlib written by A.M. Kuchling <amk@magnet.com> is
available in Python 1.5 and later versions, see
http://www.python.org/doc/lib/module-zlib.html
A zlib binding for TCL written by Andreas Kupries
<a.kupries@westend.com> is availlable at
http://www.westend.com/~kupries/doc/trf/man/man.html
An experimental package to read and write files in .zip format, written
on top of zlib by Gilles Vollant <info@winimage.com>, is available at
http://www.winimage.com/zLibDll/unzip.html and also in the
contrib/minizip directory of zlib.
Notes for some targets:
- To build a Windows DLL version, include in a DLL project zlib.def,
zlib.rc and all .c files except example.c and minigzip.c; compile with
-DZLIB_DLL
  The zlib DLL support was initially done by Alessandro Iacopetti and is
  now maintained by Gilles Vollant <info@winimage.com>.  Check the zlib
  DLL home page at http://www.winimage.com/zLibDll
  From Visual Basic, you can call the DLL functions which do not take a
  structure as argument: compress, uncompress and all gz* functions.
  See contrib/visual-basic.txt for more information, or get
  http://www.tcfb.com/dowseware/cmp-z-it.zip
- For 64-bit Irix, deflate.c must be compiled without any optimization.
With -O, one libpng test fails.  The test works in 32 bit mode (with the
-n32 compiler flag).  The compiler bug has been reported to SGI.
- zlib doesn't work with gcc 2.6.3 on a DEC 3000/300LX under OSF/1 2.1
it works when compiled with cc.
- on Digital Unix 4.0D (formely OSF/1) on AlphaServer, the cc option
-std1 is necessary to get gzprintf working correctly.  This is done by
configure.
- zlib doesn't work on HP-UX 9.05 with some versions of /bin/cc.  It
works with other compilers.  Use "make test" to check your compiler.
- gzdopen is not supported on RISCOS, BEOS and by some Mac compilers.
- For Turbo C the small model is supported only with reduced performance
to avoid any far allocation; it was tested with -DMAX_WBITS=11
-DMAX_MEM_LEVEL=3
- For PalmOs, see http://www.cs.uit.no/~perm/PASTA/pilot/software.html
Per Harald Myrvang <perm@stud.cs.uit.no>
Acknowledgments:
  The deflate format used by zlib was defined by Phil Katz.  The deflate
  and zlib specifications were written by L. Peter Deutsch.  Thanks to
  all the people who reported problems and suggested various
  improvements in zlib; they are too numerous to cite here.
Copyright notice:
 (C) 1995-1998 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied
warranty.  In no event will the authors be held liable for any damages
arising from the use of this software.
Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:
1.  The origin of this software must not be misrepresented; you must not
claim that you wrote the original software.  If you use this software in
a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2.  Altered source versions must be plainly marked as such, and must not
be misrepresented as being the original software.
3.  This notice may not be removed or altered from any source
distribution.
Jean-loup Gailly        Mark Adler
jloup@gzip.org          madler@alumni.caltech.edu
If you use the zlib library in a product, we would appreciate *not*
receiving lengthy legal documents to sign.  The sources are provided for
free but without warranty of any kind.  The library has been entirely
written by Jean-loup Gailly and Mark Adler; it does not include
third-party code.
If you redistribute modified sources, we would appreciate that you
include in the file ChangeLog history information documenting your
changes.

Progress OpenEdge v11.5 may incorporate International Classes for
Unicode (International Components for Unicode) v2.4 from IBM. Such
technology is subject to the following terms and conditions:  ICU
License - The ICU project is licensed under the X License (see also the
x.org original), which is compatible with GPL but non-copyleft.  The
license allows ICU to be incorporated into a wide variety of software
projects using the GPL license.  The X license is compatible with the
GPL, while also allowing ICU to be incorporated into non-open source
products.  License ICU License - ICU 1.8.1 and later COPYRIGHT AND
PERMISSION NOTICE Copyright (c) 1995-2003 International Business
Machines Corporation and others All rights reserved.  Permission is
hereby granted, free of charge, to any person obtaining a copy of this
software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, provided that the above copyright notice(s) and this
permission notice appear in all copies of the Software and that both the
above copyright notice(s) and this permission notice appear in
supporting documentation.  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR
ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Except as
contained in this notice, the name of a copyright holder shall not be
used in advertising or otherwise to promote the sale, use or other
dealings in this Software without prior written authorization of the
copyright holder.
-------------------------------------------------------------------------
All trademarks and registered trademarks mentioned herein are the
property of their respective owners.

Progress OpenEdge v11.5 may incorporate International Components for
Unicode v4.8.0.  Such technology is subject to the following terms and
conditions: ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION
NOTICE Copyright (c) 1995-2011 International Business Machines
Corporation and others All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, and/or sell copies of the Software, and to permit persons to
whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of
the Software and that both the above copyright notice(s) and this
permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF
THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS
INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT
OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall
not be used in advertising or otherwise to promote the sale, use or
other dealings in this Software without prior written authorization of
the copyright holder.
All trademarks and registered trademarks mentioned herein are the
property of their respective owners.

Progress OpenEdge v11.5 may incorporate java.net args4j v2.0.12 from
Kohsuke Kawaguchi.  Such technology is subject to the following terms
and conditions: Copyright (c) 2003, Kohsuke Kawaguchi All rights
reserved.  Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met:  *Redistributions of source code must retain the
above copyright notice, this list of conditions and the following
disclaimer.  *Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate Jaxen v1.1-beta-3 from
jaxen.org.  Such technology is subject to the following terms and
conditions:  Project License $Id: LICENSE.txt 1128 2006-02-05 21:49:04Z
elharo $ Copyright 2003-2006 The Werken Company.  All Rights Reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met: Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
Neither the name of the Jaxen Project nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.  THIS SOFTWARE IS PROVIDED BY
THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate Jing 20030619 as part of 1PDT
(Progress Extensions for Eclipse) v2.4.1.  Such technology is subject to
the following terms and conditions:  Jing Copying Conditions.  Copyright
(c) 2001-2003 Thai Open Source Software Center Ltd.  All rights
reserved.  Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met: Redistributions of source code must retain the above
copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
Neither the name of the Thai Open Source Software Center Ltd nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Third-party
JARs - This distribution includes some additional JAR files, which have
their own copying conditions:
saxon.jar Comes from the Saxon 6.5.2 distribution and is covered by
these conditions xercesImpl.jar xml-apis.jar Come from the Xerces-J
2.4.0 distribution and are covered by the Apache Software License
isorelax.jar Comes from ISO RELAX 2003/01/08 distribution and is covered
by the following license: Copyright (c) 2001-2002, SourceForge ISO-RELAX
Project (ASAMI Tomoharu, Daisuke Okajima, Kohsuke Kawaguchi, and MURATA
Makoto) Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation files
(the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions: The above copyright notice and this permission
notice shall be included in all copies or substantial portions of the
Software.  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Progress OpenEdge v11.5 may incorporate Sun's Jmaki framework v1.0 and
Sun's Jmaki framework v1.0.3 from Sun Microsystems, Inc.  Such
technology is subject to the following terms and conditions: Copyright
1994-2006 Sun Microsystems, Inc.  All Rights Reserved.  Redistribution
and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met: Redistribution
of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.  Redistribution in binary form
must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials
provided with the distribution.  Neither the name of Sun Microsystems,
Inc.  or the names of contributors may be used to endorse or promote
products derived from this software without specific prior written
permission.  This software is provided "AS IS," without a warranty of
any kind.  ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND
WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN
MICROSYSTEMS, INC. ("SUN") AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY
DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR
DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL SUN OR
ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR
DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE
DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY,
ARISING OUT OF THE USE OF OR INABILITY TO USE THIS SOFTWARE, EVEN IF SUN
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You acknowledge
that this software is not designed, licensed or intended for use in the
design, construction, operation or maintenance of any nuclear facility.

Progress OpenEdge v11.5 may incorporate Jmaki framework v1.8.0 from Sun
Microsystems, Inc.  Such technology is subject to the following terms
and conditions: Copyright 1994-2006 Sun Microsystems, Inc.  All Rights
Reserved.  Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met: * Redistribution of source code must retain the
above copyright notice, this list of conditions and the following
disclaimer.  * Redistribution in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.  Neither the name of Sun Microsystems, Inc.  or the names
of contributors may be used to endorse or promote products derived from
this software without specific prior written permission.  This software
is provided "AS IS," without a warranty of any kind.  ALL EXPRESS OR
IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN MICROSYSTEMS, INC. ("SUN")
AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY
LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE
OR ITS DERIVATIVES. IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR
ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL,
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND
REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR
INABILITY TO USE THIS SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. You acknowledge that this software is not
designed, licensed or intended for use in the design, construction,
operation or maintenance of any nuclear facility.

Progress OpenEdge v11.5 may incorporate JSTL v1.0 from Sun Microsystems,
Inc.  Such technologies are subject to the following terms and
conditions: Code sample License Copyright 1994-2006 Sun Microsystems,
Inc.  All Rights Reserved.  Redistribution and use in source and binary
forms, with or without modification, are permitted provided that the
following conditions are met: Redistribution of source code must retain
the above copyright notice, this list of conditions and the following
disclaimer.  Redistribution in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.  Neither the name of Sun Microsystems, Inc.  or the names
of contributors may be used to endorse or promote products derived from
this software without specific prior written permission.  This software
is provided "AS IS," without a warranty of any kind.  ALL EXPRESS OR
IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN MICROSYSTEMS, INC. ("SUN")
AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY
LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE
OR ITS DERIVATIVES. IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR
ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL,
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND
REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR
INABILITY TO USE THIS SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. You acknowledge that this software is not
designed, licensed or intended for use in the design, construction,
operation or maintenance of any nuclear facility.

Progress OpenEdge v11.5 may incorporate Looks v2.1.2 from JGoodies.
Such technology is subject to the following terms and conditions: The
BSD License for the JGoodies Looks - Copyright (c) 2001-2007 JGoodies
Karsten Lentzsch.  All rights reserved.  Redistribution and use in
source and binary forms, with or without modification, are permitted
provided that the following conditions are met: o Redistributions of
source code must retain the above copyright notice, this list of
conditions and the following disclaimer.  Redistributions in binary form
must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials
provided with the distribution.  Neither the name of JGoodies Karsten
Lentzsch nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior
written permission.  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS
AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE,  EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate OpenSSL v0.9.8 from The OpenSSL
Project.  Such technology is subject to the following terms and
conditions:  OpenSSL License.  Copyright (c) 1998-2006 The OpenSSL
Project.  All rights reserved.  Redistribution and use in source and
binary forms, with or without modification, are permitted provided that
the following conditions are met: 1.  Redistributions of source code
must retain the above copyright notice, this list of conditions and the
following disclaimer.  2.  Redistributions in binary form must reproduce
the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the
distribution.  3.  All advertising materials mentioning features or use
of this software must display the following acknowledgment: "This
product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit.  (http://www.openssl.org/)." 4.  The names "OpenSSL
Toolkit" and "OpenSSL Project" must not be used to endorse or promote
products derived from this software without prior written permission.
For written permission, please contact openssl-core@openssl.org.  5.
Products derived from this software may not be called "OpenSSL" nor may
"OpenSSL" appear in their names without prior written permission of the
OpenSSL Project.  6.  Redistributions of any form whatsoever must retain
the following acknowledgment:  "This product includes software developed
by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/)."  THIS SOFTWARE IS PROVIDED BY THE OpenSSL
PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
OpenSSL includes cryptographic software written by Eric Young
(eay@cryptsoft.com).  This product includes software written by Tim
Hudson (tjh@cryptsoft.com).  Original SSLeay License.  Copyright (C)
1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved.  This
package is an SSL implementation written by Eric Young
eay@cryptsoft.com).  The implementation was written so as to conform
with Netscapes SSL. This library is free for commercial and
non-commercial use as long as the following conditions are aheared to.
The following conditions apply to all code found in this distribution,
be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code.  The
SSL documentation included with this distribution is covered by the same
copyright terms except that the holder is Tim Hudson
(tjh@cryptsoft.com).  Copyright remains Eric Young's, and as such any
Copyright notices in the code are not to be removed.  If this package is
used in a product, Eric Young should be given attribution as the author
of the parts of the library used.  This can be in the form of a textual
message at program startup or in documentation (online or textual)
provided with the package.  Redistribution and use in source and binary
forms, with or without modification, are permitted provided that the
following conditions are met: 1.  Redistributions of source code must
retain the copyright notice, this list of conditions and the following
disclaimer.  2.  Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.  3.  All advertising materials mentioning features or use
of this software must display the following acknowledgement: "This
product includes cryptographic software written by Eric Young
(eay@cryptsoft.com)."  The word 'cryptographic' can be left out if the
routines from the library being used are not cryptographic related :-).
4.  If you include any Windows specific code (or a derivative thereof)
from the apps directory (application code) you must include an
acknowledgement:  "This product includes software written by Tim Hudson
(tjh@cryptsoft.com)." THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS''
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.  The licence and distribution terms for
any publically available version or derivative of this code cannot be
changed.  i.e.  this code cannot simply be copied and put under another
distribution licence [including the GNU Public Licence.]

Progress OpenEdge v11.5 may incorporate Quartz Enterprise Job Scheduler
v1.3.2 from James House.  Such technologies are subject to the following
terms and conditions: Copyright James House (c) 2001-2003 All rights
reserved.  Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met: 1.  Redistributions of source code must retain the
above copyright notice, this list of conditions and the following
disclaimer.  2.  Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.  THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION).  HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This
product uses and includes within its distribution, software developed by
the Apache Software Foundation   (http://www.apache.org/).

Progress OpenEdge v11.5 may incorporate SLF4J v1.6.2 and SLF4J Log4J
v1.6.1 from QOS.  Such technology is subject to the following terms and
conditions: Copyright (c) 2004-2008 QOS.ch All rights reserved.
Permission is hereby granted, free  of charge, to any person obtaining a
copy  of this  software  and  associated  documentation files  (the
"Software"), to  deal in  the Software without  restriction, including
without limitation  the rights to  use, copy, modify,  merge, publish,
distribute,  sublicense, and/or sell  copies of  the Software,  and to
permit persons to whom the Software  is furnished to do so, subject to
the following conditions: The  above  copyright  notice  and  this
permission  notice  shall  be included in all copies or substantial
portions of the Software.  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Progress OpenEdge v11.5 may incorporate SLF4J v1.7.7 from QOS.  Such
technology is subject to the following terms and conditions: Copyright
(c) 2004-2013 QOS.ch All rights reserved.  Permission is hereby granted,
free  of charge, to any person obtaining a  copy  of this  software  and
associated  documentation files  (the "Software"), to  deal in  the
Software without  restriction, including without limitation  the rights
to  use, copy, modify,  merge, publish, distribute,  sublicense, and/or
sell  copies of  the Software,  and to permit persons to whom the
Software  is furnished to do so, subject to the following conditions:
The  above  copyright  notice  and  this permission  notice  shall  be
included in all copies or substantial portions of the Software.  THE
SOFTWARE IS  PROVIDED  "AS  IS", WITHOUT  WARRANTY  OF ANY  KIND,
EXPRESS OR  IMPLIED, INCLUDING  BUT NOT LIMITED  TO THE  WARRANTIES OF
MERCHANTABILITY,    FITNESS    FOR    A   PARTICULAR    PURPOSE    AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE,  ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Progress OpenEdge v11.5 may incorporate STAX API (JSR 173) v3.1.1 from
Woodstox Project.  Such technology is subject to the following terms and
conditions: Copyright (c) 2004-2010, Woodstox Project
(http://woodstox.codehaus.org/)All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1.  Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2.  Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3.  Neither the name of the Woodstox XML Processor nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate Trang 20030619 as part of 1PDT
(Progress Extensions for Eclipse) v2.4.1.  Such technology is subject to
the following terms and conditions:  Copyright (c) 2002, 2003 Thai Open
Source Software Center Ltd.  All rights reserved.  Redistribution and
use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.  Redistributions
in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.  Neither the name of the
Thai Open Source Software Center Ltd nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.  THIS SOFTWARE IS PROVIDED BY
THE COPYRIGHT HOLDERS AND CONTRIBUTORS ôAS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate Xpp3 v1.1.3.4 from Indiana
University as part of 1PDT (Progress Extensions for Eclipse) v2.4.1.
Such technology is subject to the following terms and conditions:
Indiana University Extreme!  Lab Software License Version 1.1.1
Copyright (c) 2002 Extreme!  Lab, Indiana University.  All rights
reserved.  Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met: 1.  Redistributions of source code must retain the
above copyright notice, this list of conditions and the following
disclaimer.  2.  Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.  3.  The end-user documentation included with the
redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the Indiana University
Extreme!  Lab (http://www.extreme.indiana.edu/)." Alternately, this
acknowledgment may appear in the software itself, if and wherever such
third-party acknowledgments normally appear.  4.  The names "Indiana
Univeristy" and "Indiana Univeristy Extreme!  Lab" must not be used to
endorse or promote products derived from this software without prior
written permission.  For written permission, please contact
http://www.extreme.indiana.edu/.  5.  Products derived from this
software may not use "Indiana Univeristy" name nor may "Indiana
Univeristy" appear in their name, without prior written permission of
the Indiana University.  THIS SOFTWARE IS PROVIDED "AS IS" AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS, COPYRIGHT HOLDERS
OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate XStream v1.3.1 from XStream.
Such technology is subject to the following terms and conditions:
Copyright (c) 2003-2006, Joe Walnes Copyright (c) 2006-2007, XStream
Committers All rights reserved.  Redistribution and use in source and
binary forms, with or without modification, are permitted provided that
the following conditions are met: Redistributions of source code must
retain the above copyright notice, this list of conditions and the
following disclaimer.  Redistributions in binary form must reproduce the
above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the
distribution.  Neither the name of XStream nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.  THIS SOFTWARE
IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate YAJL v0.4.0 from Lloyd Hilaiel.
Such technology is subject to the following terms and conditions:
Copyright 2007, Lloyd Hilaiel.  Redistribution and use in source and
binary forms, with or without modification, are permitted provided that
the following conditions are met: 1.  Redistributions of source code
must retain the above copyright notice, this list of conditions and the
following disclaimer.  2.  Redistributions in binary form must reproduce
the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the
distribution.  3.  Neither the name of Lloyd Hilaiel nor the names of
its contributors may be used to endorse or promote products derived from
this software without specific prior written permission.  THIS SOFTWARE
IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate GNU ZLIB v1.1.4 and GNU ZLIB
v1.2.3 from Jean-loup Gailiy & Mark Alder.  Such technology is subject
to the following terms and conditions: Copyright notice: (C) 1995-2002
Jean-loup Gailly and Mark Adler This software is provided 'as-is',
without any express or implied warranty.  In no event will the authors
be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions: 1.  The origin of this
software must not be misrepresented; you must not claim that you wrote
the original software.  If you use this software in a product, an
acknowledgment in the product documentation would be appreciated but is
not required.  2.  Altered source versions must be plainly marked as
such, and must not be misrepresented as being the original software.  3.
This notice may not be removed or altered from any source distribution.
  Jean-loup Gailly        Mark Adler
  jloup@gzip.org          madler@alumni.caltech.edu

Progress OpenEdge v11.5 may incorporate ZLIB.NET Free v1.0.4 from
ComponentAce.  Such technology is subject to the following terms and
conditions: Copyright (c) 2006-2007, ComponentAce
http://www.componentace.com All rights reserved.  Redistribution and use
in source and binary forms, with or without modification, are permitted
provided that the following conditions are met: Redistributions of
source code must retain the above copyright notice, this list of
conditions and the following disclaimer.  Redistributions in binary form
must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials
provided with the distribution.  Neither the name of ComponentAce nor
the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate LALR Parser Generator in Java
v0.10k.  Such technology is subject to the following terms and
conditions:  CUP Parser Generator Copyright Notice, License, and
Disclaimer û Copyright 1996-1999 by Scott Hudson, Frank Flannery, C.
Scott Ananian - Permission to use, copy, modify, and distribute this
software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies
and that both the copyright notice and this permission notice and
warranty disclaimer appear in supporting documentation, and that the
names of the authors or their employers not be used in advertising or
publicity pertaining to distribution of the software without specific,
written prior permission.  The authors and their employers disclaim all
warranties with regard to this software, including all implied
warranties of merchantability and fitness.  In no event shall the
authors or their employers be liable for any special, indirect or
consequential damages or any damages whatsoever resulting from loss of
use, data or profits, whether in an action of contract, negligence or
other tortious action, arising out of or in connection with the use or
performance of this software.

Progress OpenEdge v11.5 includes the RSA Data Security, Inc.  MD5
Message-Digest Algorithm.  Copyright ¨1991-2, RSA Data Security, Inc.
Created 1991.  All rights reserved.  (MD5 Encryption Library v3.0 and
MD5 Encryption vMD5C.C) These technologies are subject to the following
terms and conditions:  RSA Data Security MD5 message-digest algorithm
RSA Data Security, Inc.  MD5C.C - RSA Data Security, Inc., MD5
message-digest algorithm Copyright (C) 1991-2, RSA Data Security, Inc.
Created 1991.  All rights reserved.  License to copy and use this
software is granted provided that it is identified as the "RSA Data
Security, Inc.  MD5 Message-Digest Algorithm" in all material mentioning
or referencing this software or this function.  License is also granted
to make and use derivative works provided that such works are identified
as "derived from the RSA Data Security, Inc.  MD5 Message-Digest
Algorithm" in all material mentioning or referencing the derived work.
RSA Data Security, Inc.  makes no representations concerning either the
merchantability of this software or the suitability of this software for
any particular purpose.  It is provided "as is" without express or
implied warranty of any kind.  These notices must be retained in any
copies of any part of this documentation and/or software.

Progress OpenEdge v11.5 may incorporate Saxon XSLT and XQuery Processor
v8.9; and Saxon XSLT and XQuery Processor v8.9.0.4 (saxon8.jar,
saxon8-xpath.jar, saxon8-xom.jar, saxon8-sql.jar, saxon8-jdom.jar,
saxon8-dom.jar) as part of 1PDT (Progress Extensions for Eclipse)
v2.4.1.  Such technologies are subject to the following terms and
conditions: The contents of these files are subject to the Mozilla
Public License Version 1.0 (the "License") provided in the product; you
may not use this file except in compliance with the License.  You may
also obtain a copy of the License at http://www.mozilla.org/MPL/.
Software distributed under the License is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied.  See the
License for the specific language governing rights and limitations under
the License.  PSC will, at LicenseeÆs request, provide a copy of the
source code for these third party technologies, including modifications,
if any, made by PSC. PSC may charge reasonable shipping and handling
charges for such distribution.  Licensee may also obtain the source code
for these third party technologies through
http://iue.progress.com/3dpartysoftwares/Pages/default.aspx by following
the instructions set forth therein.
For Saxon XSLT and XQuery Processor v8.9 û The Original Code of Saxon
comprises all those components which are not explicitly attributed to
other parties.  The Initial Developer of the Original Code is Michael
Kay.  Until February 2001 Michael Kay was an employee of International
Computers Limited (now part of Fujitsu Limited), and original code
developed during that time was released under this license by permission
from International Computers Limited.  From February 2001 until February
2004 Michael Kay was an employee of Software AG, and code developed
during that time was released under this license by permission from
Software AG, acting as a "Contributor".  Subsequent code has been
developed by Saxonica Limited, of which Michael Kay is a Director, again
acting as a "Contributor".  A small number of modules, or enhancements
to modules, have been developed by other individuals (either written
specially for Saxon, or incorporated into Saxon having initially been
released as part of another open source product).  Such contributions
are acknowledged individually in comments attached to the relevant code
modules.  All Rights Reserved.  If you produce a product that includes
or requires Saxon, please refer to it prominently as "The Saxon XSLT and
XQuery Processor from Saxonica Limited", and include the URL of the home
page, which is at http://www.saxonica.com/.
For Saxon XSLT and XQuery Processor v8.9.0.4 - The Original Code of
Saxon comprises all those components which are not explicitly attributed
to other parties.  The Initial Developer of the Original Code is Michael
Kay.  Until February 2001 Michael Kay was an employee of International
Computers Limited (now part of Fujitsu Limited), and original code
developed during that time was released under this license by permission
from International Computers Limited.  From February 2001 until February
2004 Michael Kay was an employee of Software AG, and code developed
during that time was released under this license by permission from
Software AG, acting as a "Contributor".  Subsequent code has been
developed by Saxonica Limited, of which Michael Kay is a Director, again
acting as a "Contributor".  A small number of modules, or enhancements
to modules, have been developed by other individuals (either written
specially for Saxon, or incorporated into Saxon having initially been
released as part of another open source product).  Such contributions
are acknowledged individually in comments attached to the relevant code
modules.  All Rights Reserved.

Progress OpenEdge v11.5 may incorporate Mozilla Rhino v1.6R1; and Saxon
v9.  The contents of these files are subject to the Mozilla Public
License Version 1.1 (the "License") provided in the product; you may not
use this file except in compliance with the License.  You may also
obtain a copy of the License at http://www.mozilla.org/MPL/.  Software
distributed under the License is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied.  See the
License for the specific language governing rights and limitations under
the License.  PSC will, at LicenseeÆs request, provide a copy of the
source code for these third party technologies, including modifications,
if any, made by PSC. PSC may charge reasonable shipping and handling
charges for such distribution.  Licensee may also obtain the source code
for these third party technologies through
http://iue.progress.com/3dpartysoftwares/Pages/default.aspx by following
the instructions set forth therein.
For Mozilla Rhino v1.6R1, The Original Code is Rhino code, released -
May 6, 1999.  - The Initial Developer of the Original Code is Netscape
Communications Corporation.  Portions created by Netscape are Copyright
(C) 1997-1999 Netscape Communications Corporation.  All Rights Reserved.
Contributor(s): Norris Boyd, Igor Bukanov, Roger Lawrence, Mike McCabe.
For Saxon v9, The Original Code is: All this file.  The Initial
Developer of the Original Code is Michael H. Kay.  Contributor(s): none.

Progress OpenEdge v11.5 may incorporate d3.js v3.4.11.  Such technology
is subject to the following terms and conditions: Copyright (c)
2010-2014, Michael Bostock All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* The name Michael Bostock may not be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL MICHAEL BOSTOCK BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.

Progress OpenEdge v11.5 may incorporate BeanShell v1.2b8 and Beanshell
v2.1.8.  Sun Public License Notice:  The contents of this file are
subject to the Sun Public License Version 1.0 (the "License"); you may
not use this file except in compliance with the License.  A copy of the
License is available at http://www.sun.com.  PSC will, at LicenseeÆs
request, provide a copy of the source code for these third party
technologies, including modifications, if any, made by PSC. PSC may
charge reasonable shipping and handling charges for such distribution.
Licensee may also obtain the source code for these third party
technologies through
http://iue.progress.com/3dpartysoftwares/Pages/default.aspx by following
the instructions set forth therein.
The Original Code is BeanShell.  The Initial Developer of the Original
Code is Pat Niemeyer.  Portions created by Pat Niemeyer are Copyright
(C) 2000.  All Rights Reserved.