Progress OpenEdge 10.1C04 Service Pack Readme

Progress OpenEdge 10.1C04 Service Pack Readme 

READMESP.txt 

Ports: All 

Date: June 2009 

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

Copyright(c) 1984-2009 Progress Software Corporation. All rights reserved. 

To access third party product licenses, go to the 'licenses' directory 

located in the OpenEdge installation directory. For example, go to 

C:/OpenEdge/licenses. 

Read these On-line Release Notes 

================================ 

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

primary release notes. The hard-copy release notes supplement them, 

but do not replace them. 

The on-line release notes are on the distribution medium as two 

text files: 

* READMESP 

* READMESP.txt 

The files have identical content that includes a list of known issues followed by a list of issues 

fixed in this release. 

In addition, the distribution medium includes the following HTML report 

files which list the issues addressed in all Service Packs for this 

release - organized by version, issue number (CR ID), or product component. 

* oe--version.htm (Lists fixed issues by Version) 

* oe--issue.htm (Lists fixed issues by Issue Number) 

* oe--component.htm (Lists fixed issues by Component) 

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

This readme file contains the following information: 

- Installation Instructions 

- Product Notes 

- List of Issues Addressed in this Service Pack 

======================================================================== 

INSTALLATION INSTRUCTIONS 

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

This section contains the following information: 

- Before you install this Service Pack. 

- About the Backup and Selective Install Functionality. 

- Starting the Service Pack Installation. 

- Installing the Service Pack in Silent or Batch Mode. 

- Recovering a Previous Installation. 

- Reporting Problems with the Service Pack Installation. 

BEFORE YOU INSTALL THIS SERVICE PACK: 

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

1. Make sure you shut down any instances of OpenEdge that you 

Page 1

READMESP.txt 

have running before installing this Service Pack. If you do not, 

when you run the Service Pack installation, you might receive messages 

indicating that some files could not be copied on top of other files 

(because they are locked/in use by another process). Check with your system 

administrator if you do not know how to shut down OpenEdge. 

2. Read through the entire INSTALLATION INSTRUCTIONS (see next section below) 

before proceeding. 

3. If your client and server are installed on the same physical machine 

and have different levels installed, your machine might experience shared 

memory problems. For more information about this issue, refer to the 

following Progress Solutions (accessible via the Progress Software Support 

Web site: http://www.progress.com/openedge/support) 

P132 :"What Type of Connection is Possible from Client to Server when the 

Progress versions differ?" 

P13987: "What causes shared memory version errors 1178 and 1423?" 

4. Log in as "Administrator" or as a user with Administrator privileges. If you 

do not know the Administrator password for your system, check with your 

system administrator. 

5. For UNIX only: Make sure the DLC environment variable is set to the directory 

that contains the OpenEdge installation you want to Service Pack. 

If the DLC variable has not been set, then enter one of the 

following commands to set it: 

Shell Commands (assume "/dlc" is the OpenEdge directory) 

------- ---------------------------------------------sh, 

ksh DLC=/dlc ; export DLC 

csh setenv DLC /dlc 

ABOUT THE BACKUP and SELECTIVE INSTALL FUNCTIONALITY 

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

The Service Pack installation offers you two key functions: 

* The option to create a backup of existing files. 

* The ability to install only those files relevant to your license. 

The Service Pack installation will ask if you want to backup existing 

files. If you choose to create a backup, you will have the option of 

changing or accepting the default backup location, and the backup will 

be created for only those files that are about to be updated via the 

Service Pack. 

The Service Pack installation will then determine what OpenEdge 

license(s) have been installed. Based on that information, the install 

will unpack from the Service Pack archives, only the files that are 

relevant for the license(s) installed. 

The end of the installation presents the option to review the Service 

Pack README file (this file) and the SP(n)-log.txt file which contains 

a list of files installed and backed up if a backup was executed. 

The installation saves the readmesp and log files to your Install directory 

so you can also view them later. 

Page 2

STARTING THE SERVICE PACK INSTALLATION 

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

READMESP.txt 

UNIX: 

----- 

1. If you have downloaded the Service Pack image, unpack the image to its own 

directory. 

OR 

If you have received the Service Pack on CD-ROM, mount the CD to your CD-ROM 

drive. 

2. From a directory other than the Service Pack cdimage directory, issue 

the following command: 

/ 

Windows: 

-------- 

1. If you have downloaded the Service Pack image, unpack the image to its own 

directory. 

OR 

If you have received the Service Pack on CD-ROM, insert the CD into your 

CD-ROM drive. 

2. Using Windows Explorer, go to the Service Pack directory, and double-click 

the 'Setup' icon to begin the installation. 

INSTALLING THE SERVICE PACK IN SILENT OR BATCH MODE 

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

Silent or batch install is available for Service Packs on UNIX and Windows. 

UNIX 

---- 

A normal (interactive) installation will prompt you for required 

information with dialog boxes. 

A batch install will not prompt for your input. It will read the required 

information from an installation INI file. By default, the batch install 

will look for the "install.ini" file in your current directory. 

You must create the INI file before you run a silent install. 

If no INI file is found, the installation will fail. 

Here are the contents of a sample INI file: 

[Service Pack] 

ProgressInstallDir=/usr/OpenEdge/101B/dlc 

ReInstall=1 

Backup=1 

BackupDir=/usr/OpenEdge/101B/SP_Backup 

BackupOverwrite=1 

To perform a batch install, run the following command (all one line): 

/proinst -b /install.ini -l 

Page 3

READMESP.txt 

If you do not specify a filename with the -l switch, the install script uses the 

install.log filename, by default. If you do not specify a directory for the -l 

switch, the install script uses the first of the following environment variables 

found: TMP, TEMP, TMPDIR. 

Windows 

------- 

A normal (non-silent) installation will prompt you for required information 

with dialog boxes. 

The silent install will not prompt for input. It will read the required 

information from a response file, typically named response.ini. A response.ini 

file is automatically generated when you run an interactive installation. There 

is a file named response.ini that is kept in the \install 

directory. 

You must create the response.ini file before you run a silent install. 

To have the install program create a response.ini file, run an interactive 

(non-silent) install and specify to record the user inputs with the following 

command: 

drive:\setup.exe -psc_r -psc_f1=c:\\response.ini 

Alternately, you can manually create a response.ini file. The following 

sample provides the default responses to an initial Service Pack install: 

========================== 

BEGIN SAMPLE RESPONSE FILE 

========================== 

[InstallShield Information] 

Version=7.1.100.1242 

[Application] 

Name=OpenEdge 

Version=10.1B 

Company=Progress Software 

File=Response File 

; 

; DESCRIPTION of Welcome Dialog 

; 

; Result - is used as the return code for this section. Only a value of 1 is 

; acceptable. 

; 

[Welcome Dialog] 

Result=1 

[Service Pack Backup Directory Dialog] 

_nSPBackup=0 

_sSPBackupDir=C:\Progress\OpenEdge\SPBackup 

Result=1 

; 

; DESCRIPTION of Summary Dialog 

; 

; Result - is used as the return code for this section. Only a value of 1 is 

; acceptable. 

; 

[Summary Dialog] 

Result=1 

[SdFinish] 

Page 4

Result=1 

bOpt1=0 

bOpt2=0 

========================== 

END SAMPLE RESPONSE FILE 

========================== 

READMESP.txt 

To perform a silent install, issue the following command: 

drive:\setup.exe -psc_s -psc_f1=c:\\response.ini 

[-psc_f2=c:\\setup.log] 

If you choose to create a log file, the contents of a successful silent install 

will be as follows: 

[InstallShield Silent] 

Version=v7.00 

File=Log File 

[ResponseResult] 

ResultCode=0 

RECOVERING A PREVIOUS INSTALLATION 

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

If you created a backup during the Service Pack installation, you can 

restore your installation to its original state if so desired. Because 

the backup saves the files just prior to installing the Service Pack 

it is possible only to return to that point. If multiple Service Packs 

have been installed, it is not possible to roll back through each 

Service Pack unless backups have been saved for each installation in 

separate directories. Each backup would have to be restored in the 

reverse order from which they were installed. 

To restore your installation to its original state prior to 

installing the Service Pack, do the following: 

UNIX: 

1. cd 

2. cp -R * 

WINDOWS: 

1. Using Windows Explorer, navigate to the 

/. 

2. Choose Edit->Select All, and choose Edit->Copy. 

3. Go to and choose Edit->Paste. 

This will recursively copy the files saved in the backup to your 

10.1B installation directory, thereby restoring the DLC area to its 

original state prior to installing the Service Pack. 

REPORTING A PROBLEM WITH THE SERVICE PACK INSTALLATION 

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

If you encounter problems with the installation of the Service Pack, 

or with the OpenEdge product as a result of installing the Service Pack, 

please contact Technical Support at www.progress.com. 

Page 5

READMESP.txt 

========================================================================= 

PRODUCT NOTES 

1. ABL 

Language Issues 

Object-oriented ABL 

ProDataSet 

Web Services client 

XML 

2. Adapter for Sonic ESB 

3. ADE Tools and Runtime 

ADE Common Tools 

GUI Rendering 

Tools 

4. Database 

Database Utilities 

Failover Clusters 

RDBMS 

5. DataServers 

MS-SQL 

MS-SQL/ODBC 

ORACLE 

6. Documentation 

ABL 

7. Graphical User Interface 

8. Open Client 

.NET 

Java 

Web Services Provider 

9. OpenEdge Architect 

Tools for Business Logic 

10. OpenEdge Replication 

Agent 

Replication 

11. Security 

Tools 

12. SQL 

SQL Explorer 

Tools 

13. WebSpeed 

Diagnostics 

================================================ 

ABL - 

================================================ 

Note: OE00160376 Type: Behavior Change 

XCODE-SESSION-KEY Attribute for the SECURITY-POLICY Handle 

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

When distributing encrypted code, the application provider is expected to 

distribute a compile program that compiles the application at the end-user site. 

The core of this program is one or more COMPILE statements with the XCODE 

option. With the addition of the XCODE-SESSION-KEY attribute, the encryption 

key can be specified once for all subsequent COMPILE statements and run-time 

compilations. 

XCODE-SESSION-KEY Attribute for Security-Policy 

Indicates the XCODE encryption key to be used by the COMPILE statement for 

Page 6

encrypted ABL code. 

Data type: CHARACTER 

Access: Writeable 

Applies to: SECURITY-POLICY system handle 

READMESP.txt 

Set the XCODE-SESSION-KEY attribute to indicate the encryption key for the ABL 

COMPILE statement. The key set must be the same as the key used with the XCODE 

utility. The XCODE-SESSION-KEY attribute has an eight character limit. If 

XCODE-SESSION-KEY attribute is set to a key longer than eight characters, only 

the first eight characters will be used and no warning or error message will be 

issued by the compiler. If the XCODE-SESSION-KEY attribute is queried, then the 

compiler will return an error message at run time. This attribute does not have 

a default or an initial value. Once it has been set, it can be cleared by 

setting it to the Unknown Value (?). 

If the compiler detects that the file to be compiled is an encrypted source file 

it will use the key specified in the XCODE option. If one is not provided, it 

will check if the XCODE-SESSION-KEY attribute on the SECURITY-POLICY system 

handle has been set. If this attribute has not been set, it will use the 

built-in default key. 

If the XCODE-SESSION-KEY attribute is set, if the file being compiled is 

encrypted, and if the XREF, XREF-XML, or LISTING options are used with the 

COMPILE statement, then the compiler will issue a run-time error. If the 

XCODE-SESSION-KEY attribute is set and the DEBUG-LIST option is specified on the 

COMPILE statement, then the DEBUG-LIST option will be silently ignored by the 

compiler and a debug listing file is created with no ABL code. This file 

contains the words ***Encrypted Source***. 

Once the XCODE-SESSION-KEY attribute has been set, it applies to every COMPILE 

statement encountered in all ABL code. It also applies to run-time compilations 

of encrypted source. In order to have it not apply to a specific COMPILE 

statement or a run-time compilation, the XCODE-SESSION-KEY can be cleared by 

setting it to the Unknown Value (?). 


Integer overflow message has changed 

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

When an integer overflow is detected by ABL the message: 

"Value too large to fit in INTEGER datatype. (13682)" is displayed 

usually followed by the message: 

"Unable to do run-time conversion of datatypes. (5678)". 

This second message no longer appears and is replaced with this message: 

"** Unable to update Field. (142)". 


New SESSION:TIMEZONE attribute 

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

The new TIMEZONE attribute of the SESSION system handle directs the TODAY, TIME, 

NOW, MTIME and TIMEZONE functions to return values relative to the 

SESSION:TIMEZONE value, and will initialize TODAY and NOW database and 

temp-table fields with values relative to SESSION:TIMEZONE. 

Description: Specifies the time zone offset from UTC, in minutes, to use in the 

TODAY, TIME, NOW, MTIME and TIMEZONE functions, as well as the values for DATE, 

DATETIME and DATETIME-TZ database and temp-table fields with initial values of 

TODAY or NOW. 

Data type: INTEGER 

Access: Readable/Writeable 

Applies to: SESSION system handle 

Page 7

READMESP.txt 

The default value is unknown (?) meaning use the OpenEdge session's time zone 

offset. 

If SESSION:TIME-SOURCE contains a value other than "local" or "", meaning get 

time-related data from a database server machine, SESSION:TIMEZONE is ignored. 

Valid values range from -840 to +840 (-14:00 to +14:00). 

Note: OE00168578 Type: Known Issue 

RETURN ERROR behavior change 

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

If a RETURN ERROR statement has an invalid expression for the 

, then ERROR will not be raised in the caller as of 10.1C. Prior 

to 10.1C, even though the expression was invalid, ERROR would 

still be raised in the caller. The following example illustrates the change in 

behavior. 

PROCEDURE epoo: 

RETURN ERROR SUBSTRING("abc", 1, -10). 

MESSAGE "after return error epoo". 

END PROCEDURE. 

RUN epoo. 

MESSAGE "after epoo". 

In 10.1B you will not see the message "after epoo", because ERROR was raised in 

the caller. In 10.1C you will see the message, since ERROR is not raised. 


DEFINE VARIABLE AS LONGCHAR INITIAL ? initialize to unknown value 

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

Previously, when assigning the initial Unknown Value ? to a LONGCHAR variable, 

it behaved as if it had been assigned the question mark character "?". 

DEFINE VARIABLE AS LONGCHAR INITIAL ?. 

The variable now contains the Unknown Value ?, instead of the question mark 

"?". 


TEMP-TABLE creation is slower in OpenEdge 10.x compared to 9.1 

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

See the Progress Knowledge Base, Solution P122597. 


Non-empty RETURN-VALUE from AppServer CONNECT procedure returns ERROR 

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

RETURN behaves the same as RETURN ERROR when used in an 

Application Server CONNECT procedure (srvrConnectProc property). With OpenEdge 

Release 10.1C03 this has been changed so that RETURN sets RETURN-VALUE 

to the string in the client after the server CONNECT statement. 


DECIMALS attribute for TEMP-TABLE field now returns expected value 

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

If a TEMP-TABLE DECIMAL field was defined with DECIMALS 0, the DECIMALS 

attribute used to return 30, instead of 0 as expected. It now returns the 

correct value of 0. 


GEt CURRENT [table] NO-LOCK for a TEMP-TABLE sometimes refreshes the record 

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

Prior to OpenEdge Release 10.1C, GET-CURRENT(NO-LOCK) would not refresh a record 

Page 8

READMESP.txt 

if it had been previously updated, because an update implies an EXCLUSIVE-LOCK. 

From Release 10.1C through Release 10.2A, a TEMP-TABLE record was sometimes 

refreshed incorrectly, due to a difference in certain TEMP-TABLE assignments. 

If the assignment to the TEMP-TABLE record was very simple (ttField = x), then 

the lock upgrade to EXCLUSIVE-LOCK was optimized out. This behavior has been 

changed, such that future releases will behave the same as releases prior to 

Release 10.1C. 

Note that updates to database fields, followed by GET-CURRENT(NO-LOCK), have 

always worked correctly and are unaffected by this issue. 


Errors raised on RETURN statement are not handled in a consistent manner 

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

When the RETURN statement is followed by an expression, it is possible that the 

expression could result in an ERROR condition. Using Structured Error Handling 

it should be possible to catch these errors in the block in which the RETURN 

statement appears. This works as expected for application errors (AppError). 

However, system errors (SysError) do not get handled by a CATCH in the block in 

which the RETURN statement appears, but get returned to the caller and handled 

there. 

For Release 10.2B, a CATCH block covering a RETURN statement will catch errors 

raised during the evaluation of the expression on the RETURN statement, rather 

than raising error in the caller. These errors will propagate to the caller 

automatically if the RETURN statement is covered by a ROUTINE-LEVEL ON ERROR 

UNDO, THROW statement. 

================================================ 

ABL - Language Issues 

================================================ 


CREATE BUFFER statement now gets shared schema lock 

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

Prior to 10.1C02 the CREATE BUFFER statement did not get a shared schema lock on 

the database containing the table for which the buffer was being created. If an 

application consisted entirely of programs and classes that contained only 

dynamic references to buffers for database tables, it is possible that the 

database schema could be changed even though there were running programs with 

dependencies on the existing schema. The results on running programs impacted 

by the schema change is indeterminate and could result in database corruption. 

As of 10.1C02 this potential hole in the schema lock protocol has been fixed. 

In general, no application should see any change in behavior unless it changes 

existing table definitions while the database is online and that schema change 

occurs at a time when all running programs have only dynamic references to 

tables in the database. 


Buffer change will be backed out if error on expression 

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

If a buffer operation occurs during the evaluation of a statement that has 

NO-ERROR on it and an error occurs, that operation should be backed out. This 

was not being done in the case where the statement is an "expression statement" 

-- a standalone expression that is not part of an assignment (for example a call 

to a UDF or a method, or several such calls chained together). 

This bug has been fixed, but it introduces a change in behavior that may affect 

existing ABL code. If an expression statement (as described above) caused a 

buffer change while executing, that change would persist even if the statement 

resulted in an error being raised. Now the buffer change will be rejected. 

Page 9

READMESP.txt 

Although this fix may affect existing applications, it was deemed necessary 

since the bug could cause database inconsistency. 

================================================ 

ABL - Object-oriented ABL 

================================================ 


Re-throw of error from constructor is caught in subclass 

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

If a catch block exists at the routine level of a constructor and the 

application re-throws the error (UNDO, THROW ), the error 

is thrown to a subclass constructor where it calls SUPER and raises ERROR on 

that statement. 

The re-thrown error should cause the object instantiation to abort and ERROR to 

be raised on the NEW statement. 


RETURN ERROR from a method called by a constructor aborts object instantiation 

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

RETURN ERROR from a method called by a constructor aborts object instantiation 

and raises ERROR on the NEW statement. When a constructor calls a method which 

returns ERROR, ERROR should be raised on the statement where the method is 

called. 

================================================ 

ABL - ProDataSet 

================================================ 


ATTACH-DATA-SOURCE must come before QUERY-PREPARE for recursive Dataset 

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

Prior to Release 10.2A, it was possible to run the QUERY-PREPARE method for a 

Data-Source's query for the top buffer of a recursive Dataset, and then call the 

ATTACH-DATA-SOURCE method for that buffer. For Release 10.2B, the AVM will 

raise error at compile-time. The query will not compile correctly during the 

recursion unless the ATTACH-DATA-SOURCE method is called before the 

QUERY-PREPARE method. 

================================================ 

ABL - Web Services client 

================================================ 


Analyzer crashes when wrapped document/literal is too complicated 

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

When the analyzer encounters a particular type of complex argument in a wrapped 

document/literal SOAP message definition it crashed. 

As of this release, this situation is now properly handled and documentation for 

the web service operation is generated. 


ProSOAPView forces HTTP version 1.0 in HTTP requests 

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

If a Web service client sends an HTTP 1.1 request while running ProSOAPView as a 

proxy, the HTTP version header is altered. The header displayed by ProSOAPView 

indicates that the message is an HTTP 1.0 request. In addition, the message sent 

on to the Web service provider contains that same header. 

Page 10

READMESP.txt 

If this becomes an issue during development of an ABL Web service or Web service 

client, use another utility such as TCPMon. 


Incorrect SOAP Request sent with complex input parameter 

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

When calling a Web service operation with two parameters, one input LONGCHAR and 

one output LONGCHAR, an incorrect SOAP request could be sent. 

This problem occurred when the SOAP messages used the Wrapped Document/Literal 

convention and the input parameter was a complex value. An input parameter that 

is a complex value must be sent as a text value containing XML. 

The incorrect SOAP message might look something like the following. Note the 

second, nested, occurrence of the parameter element: 

 

 

 

testing 

 

 

 

The message should look something like the following: 

 

 

testing 

 

 

This problem has been fixed. 


-SOAPEndpoint CONNECT value truncated 

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

Previously, the value for the -SOAPEndpoint parameter of the CONNECT method was 

truncated if the parameter was longer than 128 characters. The parameter length 

may now be up to 1024 characters. 

================================================ 

ABL - XML 

================================================ 


SAX-READER and X-DOCUMENT fail with basic HTTP authentication 

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

The XML processing methods in ABL cannot handle HTTP requests with basic 

authentication (username & password embedded in URL). They fail to locate the 

file. These URLs take the form of 

http://:@/ 


WRITE-XML serializes temp-table rows with all fields as attributes differently 

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

If you have a temp-table with all fields having XML-NODE-TYPE="Attribute", and 

the temp-table row is not the parent in a NESTED DATA-RELATION, the XML 

serialization for the row will be slightly different. This change provides XML 

more compatible with validation tools. 

Before this release, the resulting XML is a set of open and closed tags with no 

Page 11

content: 

 

 

Now, the result is a single empty tag: 

 

================================================ 

Adapter for Sonic ESB - 

================================================ 

READMESP.txt 


New Feature - ABL Procedure file Drag and Drop 

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

OpenEdge Release 10.1C introduced the Native Invocation Methodology for the 

OpenEdge Adapter for Sonic ESB. The Native Invocation Methodology enables ABL 

procedures and user-defined functions to be called natively from a Sonic ESB 

process, as opposed to treating them as Web services. This new feature includes 

the creation of .esboe files from OpenEdge Architect or from ProxyGen, for use 

in Sonic Workbench when developing ESB business processes (itineraries) that 

include calling ABL code. 

OpenEdge Release 10.1C01 adds the ability at development time to drag and drop 

ABL procedure files directly into a Sonic ESB itinerary. Dragging ABL procedure 

files directly into a Sonic ESB itinerary eliminates the need to create and 

import a .esboe file. If your source code is not already annotated with ESB 

annotations when you do the drag and drop, a wizard walks you through the steps 

required to add the annotations. 

To take advantage of this new feature, you must have Sonic V7.6 and you must 

have integrated OpenEdge Architect and Sonic Workbench into one Eclipse 

environment. 

The creation of an ESB itinerary based on .esboe files remains fully supported. 

================================================ 

ADE Tools and Runtime - ADE Common Tools 

================================================ 


Crash using ADE tools with UNC working directory 

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

When your working directory is a UNC pathname, some functionality in the 

AppBuilder and common ADE tools might cause a crash. The problem relates to 

providing a list of files in the working directory. The following are known to 

cause a crash: 

- Adding an image to a window in the AppBuilder 

- Building the list of files in the Widget ID Assignment Utility 

- Using adecomm/_fndfile.p to search for files 

The workaround is to map the UNC path to a drive letter. 

================================================ 

ADE Tools and Runtime - GUI Rendering 

================================================ 


IndexInformation always retrieved on the first request 

Page 12

READMESP.txt 

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

In Release 10.1A, the SDO retrieves the IndexInformation property from the 

server only when the SDO is batching. Beginning with Release 10.1C01, the SDO 

always retrieves the property from the server on the first request. This 

behavior is closer to the SDO's behavior before Release 10.1A. Also note that 

beginning with Release 10.1A, the property only applies to a single table. 

Before Release 10.1A, the property contains information on all tables joined in 

the SDO. You can override getIndexInfoTables if you want it to return info for 

more tables. 

Because of the changes to the IndexInformation property, an SDO on a client 

without batching now retrieves more context information on the first request. 

The context information for even a single table might be large and affect 

performance. 

================================================ 

ADE Tools and Runtime - Tools 

================================================ 


Appbuilder supports declarative statements like USING 

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

The Procedure Settings Dialog has additional functionality that allows the user 

to add declarative statements, like USING and ROUTINE LEVEL ERROR. A new button 

on the right hand side opens a dialog that allows you to add this code in an 

editor. 

The declarative statements added here are generated into a new section in the 

source code. This section is written before both the optional temp-table 

definitions and the optional AppServer include. This ensures that these 

statements are added before any definitional and executable statement as 

required for proper compilation. 

================================================ 

Database - Database Utilities 

================================================ 


PROUTIL IDXFIX -silent is not silent 

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

Running PROUTIL IDXFIX with the -silent parameter does not suppress the display 

of repetitive messages or prevent repetitive messages from being written to the 

log file. 


PROUTIL IDXACTIVATE errors when table-name specified in useindex qualifier 

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

The documentation for the [useindex table-name.index-name] qualifier of the 

PROUTIL IDXACTIVATE command is incorrect. The useindex qualifier should not 

include the table-name. The correct syntax is: [useindex index-name]. 

Note: OE00153473 Type: Limitation 

Negative integers are not supported by specified binary dump. 

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

Negative integers are not supported by the specified binary dump utility as 

input parameters. You can dump all negative values by specifying a value range 

as "LT 0" for the column, but specifying any negative integer, such as "LT -1", 

fails. The specified binary dump utility cannot interpret command lines with a 

"-" negative sign in the input parameter on command line. 


Page 13

READMESP.txt 

New temporary file for PROUTIL IDXCHECK and PROUTIL IDXFIX 

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

PROUTIL IDXCHECK and PROUTIL IDXFIX use a temporary file to store the list of 

indexes being checked or fixed during execution of some options. Starting with 

this release, the temporary file is named ..xb. The file is 

deleted when the process successfully completes. If the process terminates 

unsuccessfully, the file may not be deleted. 

PROUTIL IDXBUILD continues to use the temporary file .xb. The behavior 

of IDXBUILD is not changed. 

================================================ 

Database - Failover Clusters 

================================================ 


Failover clusters and multiple APWs 

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

Configurations where there are multiple APWs enabled may find that only one APW 

will restart when fail over of a database resource occurs to the same node on 

which the failure has occurred. 


Manually stopping an APW on MS Windows Server 2003 running Clusters 

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

When manually stopping a pagewriter on a Windows 2003 Server cluster (after a 

PROCLUSTER enable and PROCLUSTER start), the cluster administrator does not 

properly show the updated (failed) status of the particular pagewriter. 


Clusters -- the hour might be incorrect in the db.Appserver.log file (AIX only) 

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

The hour position time value displayed in the db.Appserver.log file might be 

incorrect for some messages. This usually occurs when database related 

processes/ancillary processes that were enabled with the database are dead or 

killed. 


Pagewriter error message on PROCLUSTER start can be ignored 

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

When executing a PROCLUSTER start, and no pagewriters were specified in your 

PROCLUSTER enable, a grep error message is displayed looking for the 

{db-name~Resources.cluster file. This file only exists if pagewriters are 

specified during the PROCLUSTER enable. This error message is harmless and can 

be ignored. 


First PROCLUSTER enable must complete 

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

The first database register, i.e. PROCLUSTER enable, must be allowed to complete 

before issuing additional PROCLUSTER enable commands. This is to allow the 

proper registration of the Progress Cluster type (PRGS.clstr). Once the 

PRGS.clstr registration is complete, PROCLUSTER commands can be entered without 

any restrictions. 


Failover Clusters node ordering 

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

The node the cluster chooses to fail over to is a default preference Clusters 

accepts from the cluster manager. If you want to tailor this, you must use your 

operating system cluster management utilities. Clusters does not alter node 

ordering. 

Page 14

READMESP.txt 


Failover Clusters excluding nodes from fail over 

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

All clustered systems provide a means for disallowing hosts from hosting a 

resource. You must use your operating system cluster management utilities to do 

this. Clusters does not provide a means to disallow a host. 


Watch Dog should be enabled for Clusters 

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

When enabling a database for clusters using the PROCLUSTER enable command, the 

Watch Dog must always be enabled. 

For example: 

procluster /usr/wrk/foo enable WDOG 


Failover clusters helper processes that do not start on another machine 

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

If any of the helper (APW, BIW, or AIW) processes or the watchdog process 

specified to start with a particular database fails, they will not be started on 

another machine during a failover. They will produce an OFFLINE status. 

Note: OE00147507 Type: Product Notice 

Clusters -- two databases using the same port (AIX only) 

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

A cluster-enabled database attempting to use a port currently in use fails to 

come ONLINE because the port is already in use. The database retries the 

attempt to come ONLINE the number of times specified by the restart count. 

During the period of time that the retries occur, querying PROCLUSTER 

isalive/looksalive or HACMP clfindres for status of resource group returns 

ALIVE/UP as the status. This is correct because there are other resources in the 

resource group that have been brought ONLINE at that time. After the database 

resource has unsuccessfully retried the specified number of times, the status of 

the resource group is updated to DOWN. 


Failover Clusters Sun Cluster uses global devices 

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

Clusters only supports databases stored on global devices. The Sun Cluster uses 

global devices to provide cluster-wide, highly available access to any device in 

a cluster, from any node, without regard to where the device is physically 

attached. In general, if a node fails while providing access to a global 

device, the Sun Cluster software automatically discovers another path to the 

device and redirects the access to that path. The local disks on each server are 

not multi-ported, and thus are not highly available devices. Multi-ported 

global devices provide more than one path to a device. In the case of multi-host 

disks, because the disks are part of a disk device group hosted by more than one 

node, the multi-host disks are made highly available. 


Clusters -- simultaneous enable of two different databases 

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

If you simultaneously execute a PROCLUSTER enable command for two databases, you 

get the following error for one of the databases: 

Unable to synchronize cluster resources, Perform synchronization manually and 

identify error cluster REGISTER command was UNSUCCESSFUL. 

Though the cluster registration reported it was unsuccessful, both databases are 

successfully registered and automatically brought online by the cluster 

manager/administration tools. To avoid this error message, disallow multiple 

Page 15

READMESP.txt 

cluster administrators from having access to the cluster administration at the 

same time, and execute PROCLUSTER commands one at a time. 

================================================ 

Database - RDBMS 

================================================ 


_Connect-IPAddress in the _Connect VST is not assigned a value 

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

The _Connect-IPAddress field of the _Connect VST is not assigned a value at this 

time. 

================================================ 

DataServers - 

================================================ 


No support for IDENTITY fields 

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

The MS SQL Server DataServer has no specific support for MS SQL Server IDENTITY 

fields outside of its own use of IDENTITY fields to provide Progress RECID 

functionality. 


hpuxia64 platform is only supported with Oracle 10g 

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

The hpuxia64 platform is only supported with Oracle 10g. It is *not* supported 

with Oracle 9i or any earlier release of Oracle. When using the Oracle 

DataServer with an Oracle 9i instance on the hpuxia64 platform, you may run into 

the following error: 

"ORACLE failed to convert a number to a 4 bytes integer." 

This error does not occur on any other supported platform, and does not occur 

when using an Oracle 10g instance. 


Compilers tested with OEBUILD 

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

The following compilers were used and tested with the OEBUILD utility in 

OpenEdge 10. While other versions and/or patch levels may work, it is 

recommended that the same compiler version be used with OEBUILD where possible. 

Solaris (32 & 64 bit): 

Compiler & version: 

Sun Forte 6 Update 2, C version 5.3 with patch 111679-10 

AIX (32 & 64 bit): 


IBM VisualAge 6 c/C++ C++ (June 2005 PTF) 

HP-UX (32 & 64 bit): 


HP C/ANSI C version 11.11.08 with patch PHSS_29484 

Compaq (HP) Tru64: 


Page 16

Compaq (HP) C V6.5-011 

Linux: 


G++ version 2.96 

Microsoft Windows: 


Visual Studio .Net 2003 

READMESP.txt 

Unixware: 


Optimizing C Compilation System (CCS) 4.2 05/11/04 (uw714.bl3af) 

HP Itanium: 


HP aC++/ANSI C B3910B A.05.55 [Dec 04 2003], with 

C++ Runtime Library patch PHSS_29659 


Change in log format for 'dataserv.lg' log file 

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

In 10.1C for all DataServers, user will notice a change in the output format of 

the dataserv.lg log file. In versions prior to 10.1C, the dataserv.lg was 

logged directly from the DataServer code layer and was essentially free 

format as follows: 

11:21:28 : Login to dataserver db as user nmanchal. (2689) 

11:21:28 : Completed connection startup; 5 secondary connections requested all 

good. 

11:21:28 : MSS version: Microsoft SQL Server 08.00.0194 (4203) 

The new output format is derived from changes in the DataServer layer 

that integrate the "Enhanced Logger" architecture which was first 

introduced in the OpenEdge product in 10.1A to standardize OpenEdge logging and 

log formats. The new format looks like the following: 

[08/01/22@11:30:38.985+2300] P-006908 T-011492 1 MSS -- Logging level set to 

= 2 

[08/01/22@11:30:38.985+2300] P-006908 T-011492 1 MSS -- Log entry types 

activated: DS.DEBUG 

[08/01/22@11:30:38.985+2300] P-006908 T-011492 1 MSS -- Login to dataserver 

db as user nmanchal. (2689) 

[08/01/22@11:30:39.048+2300] P-006908 T-011492 1 MSS -- Completed connection 

startup; 5 secondary connections requested all good. 

[08/01/22@11:30:39.048+2300] P-006908 T-011492 1 MSS -- MSS version: 

Microsoft SQL Server 08.00.0194 (4203) 

NOTE: New Enhanced Logger features are not fully implemented for 

DataServers in 10.1C. The only noticeable difference customers should 

encounter are the prefix format of written log messages as described above. 

All existing -Dsrv parameters available in earlier releases for setting log 

attributes continue to be available in 10.1C and are not affected by the new 

logging infrastructure. 


Microsoft SQL Server 2008 Certified 

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

The Dataserver for MS SQL Server has been certified for MSS 2008 using the 

following drivers. 

(1) Distributed by Microsoft Corporation 

Page 17

READMESP.txt 

(a) SQL Server (2000.85.1117.00) - SQLSRV32.DLL (32-bit) 

(b) SQL Server (2000.86.3959.00) - SQLSRV32.DLL (64-bit) (10.2A only) 

(c) SQL Native Client 9 (2005.90.1399.00) - SQLNCLI.DLL (32-bit) 

(d) SQL Native Client 9 (2005.90.1399.00) - SQLNCLI.DLL (64-bit)(10.2A only) 

((2) Distributed via OpenEdge 10.2A and OpenEdge 10.1C Service Pack 2 

Installation 

(a) Datadirect ODBC Wire Protocol driver for MS SQL Server (5.30.00.54) - 

P1MSSS23.DLL (32-bit) 

(b) Datadirect ODBC Wire Protocol driver for MS SQL Server (5.30.00.55) - 

P2MSSS23.DLL (64-bit)(10.2A only) 

This certification asserts that for all features tested, OpenEdge clients 

exhibit consistent results using the DataServer for MS SQL Server to connect MS 

SQL Server 2008 and all earlier supported database versions. 

IMPORTANT NOTE: 

SQL Native Client 10 drivers distributed by Microsoft Corporation with MS SQL 

Server 2008 are not yet certified for OpenEdge releases. You must obtain the 

SQL Native Client 9 drivers distributed by Microsoft in order to ensure full 

OpenEdge compatibility with MS SQL Server 2008. SQL Native CLient 10 drivers 

are expected to be certified in a future release and/or service pack. 

================================================ 

DataServers - MS-SQL 

================================================ 


-Dsrv switch to turn off validation in DataServer client 

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

To prevent a bad write to the database, the DataServer for MS SQL Server does 

advanced validation based on schema information. This occurs before an OpenEdge 

trigger is executed. In cases where you would prefer to explicitly turn off this 

validation, i.e. when a trigger takes care of the validation, use the new switch 

"-Dsrv PRGRS_PREVALIDATE,0". By default, validation is on; "-Dsrv 

PRGRS_PREVALIDATE,1" is the default. 


Changes as part of certifying SQL Server 2005 

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

Microsoft has made changes to the Query Optimizer in SQL Server 2005 to generate 

better and more appropriate query plans automatically when compared to earlier 

versions of SQL Server. However, a change in behavior is noticed in SQL Server 

2005 when compared to SQL Server 2000 for some lock contention scenarios when 

"read committed" isolation level is used. 

Changes have been incorporated in DataServer for MS SQL Server, as part of an 

effort to provide consistent behavior to an application when used with a newer 

version of SQL Server (SQL Server 2005). This consistency feature is leveraged 

only when used with SQL Server 2005 and above. 


SQL Server DataServers will now insert NULL value ("?") on creating new records 

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

SQL Server DataServers will now insert the NULL value if the ABL assigns the 

unknown value ("?") while creating new records. 

Previously the DataServer for MS SQL Server stored the default value from the 

schema holder into the column instead of NULL when the ABL assigned the only 

Page 18

READMESP.txt 

unknown value and all other column assignments came from default values. This 

was incorrect since the unknown value in the ABL should always be equated to a 

SQL NULL in the DataServer products when the user deliberately assigns such 

value. 

For example, 

A customer table with 3 fields - name, city and state. 

In the schema holder, the city and state columns have default values of 

'Bedford' and 'MA', respectively. 

Based on the following ABL code 

CREATE customer. 

ASSIGN name = "john". 

state = ?. 

The above would previously have created a new customer record with 

set to: 

(name,city,state) 

('john', 'Bedford', 'MA') 

where "Bedford" and "MA" are default values in the schema image for "city" and 

"state" fields, respectively.. 

Now it takes the unknown value ('?') assigned to the "state" field and properly 

translates it into a NULL column. Therefore in the example provided, the new 

record would now be created as: 

('john', 'Bedford', NULL) 


Datetime/tz support in MS SQL DataServer 

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

In OpenEdge Release 10.1C Service Pack 1 (10.1C01), the DataServer for MS SQL 

Server has been enhanced to support DATETIME data types in SQL Server (until SQL 

Server 2005) with full support for DATETIME data types and NO SUPPORT for 

DATETIME-TZ. 

1. Prior to OpenEdge 10.1C01, the MSS DATETIME datatype mapped to a OE DATE 

datatype as default. With DATETIME support in 101C01, DATETIME datatype in SQL 

Server can be directly mapped to OpenEdge DATETIME datatype. The default 

behavior will be retained for backward compatibility, i.e. MS SQL Server 

DATETIME would be pulled as an OpenEdge DATE datatype by default. However, the 

user can set 'OE_101C_DATETIME=yes' and then MSS 'Datetime' can be pulled as OE 

'Datetime' in the schema-holder by default. Note that the user can anytime 

change the mapping of MS SQL Server DATETIME to OpenEdge DATETIME, DATE, or 

CHARACTER as per his or her requirement. 

2. Please note that In MS SQL Server, subsecond accuracy is upto .333 seconds or 

1/300th of a second. Rounding at the millisecond level is granular to a third 

of a millisecond, so values will round to .000, .003, and .007 seconds. 

Users who write datetime comparison expressions in their ABL code, especially 

equality matching, should use caution when using the DataServer for MS SQL 

Server. The user must be careful about the millisecond precision of the values 

he/she is comparing due to the 1/300 millisecond rounding performed internally 

by Windows and MS SQL Server. 

One way for customers to avoid this issue is to ensure that all their datetime 

values are derived from a Windows or SQL Server source rather than obtaining 

them from the OpenEdge client or an OpenEdge database where the datetime values 

Page 19

READMESP.txt 

can be fabricated with greater precision. By setting their TIME-SOURCE 

attribute to their logical database of their MS SQL Server DataServer schema 

holder, the values derived for MTIME, NOW, TIME and TODAY will be generated from 

a Windows time source. This can avoid application conflicts with time values 

derived from other time sources with precision values of finer granularity. 

3. When using RUN STORED-PROCEDURE to execute an MS SQL Server stored procedure, 

the user must initialize the OUTPUT param with an initial value other than 

UNKNOWN (?). This initial value will be overwritten by whatever the SQL Server 

returns to the Output parameter. In case when a NULL is returned, the initial 

value will remain unchanged. 


Compatibility issues between 32-bit and 64-bit RECIDs in some versions of 10.1B 

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

As part of the effort to introduce 64-bit data addresses into the OpenEdge 

database for Release 10.1B, the default implementation of PROGRESS_RECID in the 

DataServers for MS SQL Server and ODBC were changed to a 64-bit value. In 

releases prior to 10.1B, PROGRESS_RECID was a 32-bit value. 

This produced some PROGRESS_RECID incompatibilities for schema holders created 

or maintained in OpenEdge 10.1B using the 10.1B Dictionary utilities. These 

incompatibilities also affect schema holders that were created and maintained 

prior to 10.1B but are used in a 10.1B application environment or a schema 

holder created or maintained by the 10.1B Dictionary that is now used in a 10.1C 

application environment. 

The incompatibilities are resolved in Release 10.1C and by a hot fix to patch 

level 10.1B03 by simply performing a schema pull from the Dictionary utilities. 

Therefore, if you are using or maintaining a schema holder from the OE 10.1B 

Dictionary (prior to Release 10.1C and prior to the 10.1B hot fix) you will need 

to re-pull your server definitions into that schema holder using the 10.1B03 hot 

fix patch or 10.1C Dictionary utilities to avoid application conflicts with the 

PROGRESS_RECID. 

After re-pulling definitions into your schema holder using the 10.1B hot fix or 

using 10.1C, you should encounter no further problems with PROGRESS_RECID. 


No support for IDENTITY fields 

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

The MS SQL Server DataServer does not have any specific support for MS 

SQL Server IDENTITY fields outside of its own use of IDENTITY fields to 

provide Progress RECID functionality. 


Avoid using SHARELOCK if possible 

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

The transaction isolation levels define the type of locks acquired on 

read operations. The default isolation level for MS SQL Server is Read- 

Committed. This isolation level typically puts some form of database 

dependent SHARE LOCK on records, pages, and/or tables that it reads. 

Under this isolation level, only committed changes can be read from 

existing data. For simplicity and DataServer efficiency, Progress Software 

Corporation 

recommends that you avoid using the SHARELOCK if possible. The 

DataServer for MS SQL Server can support the NO-LOCK condition in Progress with 

the 

help of -Dsrv connection parameter to set the isolation level to Read- 

Uncommitted as follows: "-Dsrv TXN_ISOLATION,1". This is a connection-level 

switch 

only. SHARE-LOCK is treated like NO-LOCK at this isolation level. Therefore if 

you set Read-Uncommitted for your session, all non-EXCLUSIVE-LOCK statements 

(statements w/SHARE-LOCK, NO-LOCK, or unspecified statements) will perform as 

NOLOCK. 

In OpenEdge DataServer for MS SQL Server 2005, Read-Uncommitted is set 

Page 20

READMESP.txt 

as default isolation level for the DataServer applications. This change would 

come into effect in the service pack 10.1B01. Currently for using SQL Server 

2005 with DataServer release 10.1B, it is required to explicitly set the 

isolation level to 1 (Read-Uncommitted) with the -Dsrv connection parameter, to 

ensure compatibility with prior releases of MS SQL Server. SQL Server 2005 

SNAPSHOT Isolation & OpenEdge 

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

The OpenEdge ABL is pessimistic and transactional (OLTP) in nature and 

for the OpenEdge DataServer technology to emulate the NO-LOCK/EXCLUSIVE-LOCK 

lock types of the OpenEdge database; it uses the READ UNCOMMITTED isolation 

level to provide the best and most efficient match. SQL Server 2005 SNAPSHOT 

ISOLATION (row versioning) provides an optimistic locking environment for 

read-intensive operations (OLAP). However, READ UNCOMMITTED isolation is still 

recommended for transaction-intensive (OLTP) applications due to the added load 

imposed on the server running update transactions with snapshot isolation. 

The OpenEdge DataServer for MSS will function against a SNAPSHOT ISOLATION 

(row versioned) enabled MSS database but any OpenEdge ABL logic that 

relies on pessimistic lock management (for instance, conditions where the 

OpenEdge 

client might issue a " is in use by USER ABC" message will be 

affected and therefore alter application behavior. Conflict resolution is also 

handled differently between pessimistic and optimistic locking models and so 

data integrity issues will also be of concern if SNAPSHOT ISOLATION is used with 

the 

OpenEdge Dataserver technology. To obtain the best concurrency control and 

inter-transactional protection in your ABL applications, progress recommends not 

using SNAPSHOT isolation. SNAPSHOT isolation, in effect, provides alternate 

implementations of SERIALIZABLE and READ COMMITTED levels of isolation that use 

optimistic locking to control concurrent access rather than pessimistic locking. 

Unless your OpenEdge ABL application requires one of these two isolation levels, 

Progress 

recommends that customers consider neither transaction-level nor statement-level 

SNAPSHOT isolation for their applications using the DataServer for MS SQL 

Server. While 

SNAPSHOT isolation can be used to emulate SERIALIZABLE and READ COMMITTED 

isolation levels, progress also recommends not using SNAPSHOT isolation to 

acheive them. 


A new -Dsrv switch for NO-WAIT functionality has been introduced 

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

A new connection-level switch PRGRS_NOWAIT_OVERRIDE has been added for the 

DataServer for MS SQL Server: 

Currently the PRGRS_NATIVE_LOCKWAIT setting permits an application to set the 

maximum time a statement waits on MS SQL Server for a blocked resource. Note 

that the ABL client is also blocked while the PRGRS_NATIVE_LOCKWAIT period is 

active on the server. This new switch may be useful to those who want the 

NO-WAIT instruction on an ABL database request to override the 

PRGRS_NATIVE_LOCKWAIT period in which the application is blocked on the server. 

The new PRGRS_NOWAIT_OVERRIDE connection-level switch will resolve the scenario 

for NO-WAIT queries. The valid values for PRGRS_NOWAIT_OVERRIDE switch are 0 

and 1. By default PRGRS_NOWAIT_OVERRIDE will be disabled (i.e. 0). Setting of 

this new switch alone will be ignored by the DataServer and would otherwise have 

no affect on the NO-WAIT conditions in your application because the default 

PRGRS_NATIVE_LOCKWAIT period is zero which means the server returns immediately 

to the client anyway when it encounters a locked resource. The override setting 

is only meaningful when specified alongside the PRGRS_NATIVE_LOCKWAIT connect 

option. Note that the PRGRS_NOWAIT_OVERRIDE switch only applies to server side 

blocking associated with the PRGRS_NATIVE_LOCKWAIT. Client side resource 

blocking, as timed by the -lkwtmo switch, is not affected by 

PRGRS_NOWAIT_OVERRIDE switch and is already designed to unblock in response to a 

NO-WAIT ABL instruction. 

Page 21

READMESP.txt 

In the following client startup example the client lock wait time out is set to 

180 seconds, the native lock wait time out is set to 50 milliseconds and the 

PRGRS_NOWAIT_OVERRIDE switch is set on: 

prowin32.exe mydb -lkwtmo 180 -Dsrv 

PRGRS_NATIVE_LOCKWAIT,50,PRGRS_NOWAIT_OVERRIDE,1 

Let us assume that a "customer" resource is already blocked on the server and 

continues to be blocked indefinitely, then using the following ABL statement: 

FIND FIRST customer NO-WAIT. 

The behavior as seen from the ABL client is the following: 

1. Because of the NO-WAIT ABL condition and the PRGRS_NOWAIT_OVERRIDE,1 setting, 

control is returned immediately to the client despite the non-zero value for 

PRGRS_NATIVE_LOCKWAIT. 

NOTE: Had the PRGRS_NOWAIT_OVERRIDE switch not been set, the server would have 

blocked a maximum of 50 milliseconds assuming the resource was not otherwise 

made available prior to the server time out period. 

2. The client's lock wait time out period of 180 seconds begins when the server 

returns to the client. In this case, the NO-WAIT instruction in the ABL and the 

switching on of the PRGRS_NOWAIT_OVERRIDE option means that the client's lock 

wait time out period begins immediately. 

NOTE: When the PRGRS_NOWAIT_OVERRIDE is off, the initial PRGRS_NATIVE_LOCKWAIT 

period (spent blocked on the server) is NOT accumulated by the client side 

"-lkwtmo" period because the '-lkwtmo' period doesn't begin until the client has 

control. This is not a concern when the PRGRS_NOWAIT_OVERRIDE switch is on and 

the ABL specifies NO-WAIT because no additional time is accumulated waiting on 

the server, i.e., the PRGRS_NATIVE_LOCKWAIT period is overridden by the NO-WAIT 

action. 

3. The ABL application takes immediate control and receives the "LOCKED" ABL 

condition indicating that the resource is unavailable. 

NOTE: If the ABL had not specified NO-WAIT and the resource continued to be 

unavailable after the PRGRS_NATIVE_LOCKWAIT period, the the client side -lkwtmo 

period would now commence and would wait 180 seconds, repeatedly cycling to the 

server in an effort to obtain the locked resource. 

Additional Notes (not related to the above test case): 

1 Had the NO-WAIT ABL condition not been specified and had the 180 second wait 

on the client expired without obtaining the resource, the ABL client would then 

fail with a "lock wait timeout exceeded" error message. 

2. Had the NO-WAIT ABL condition not been specified, and the 

PRGRS_NOWAIT_OVERRIDE switch were set to off, and the resource remained 

unavailable, the start of the client -lkwtmo period would be delayed by the 50 

milliseconds that it blocked on the server. Also, because of the difference in 

the 'seconds' granularity of the '-lkwtmo' switch as compared to the 

'milliseconds' granularity of the 'PRGRS_NATIVE_LOCKWAIT, some rounding could 

cause the actual '-lkwtmo' period on the client to be 181 seconds, versus the 

specified 180 seconds. 

3. Generally, PRGRS_NATIVE_LOCKWAIT should be set to a small number of 

milliseconds in order to allow the server a reasonable opportunity to resolve 

resource locks before returning control to the client that is expected to handle 

recovery programmatically. In such cases, the small PRGRS_NATIVE_LOCKWAIT value 

Page 22

READMESP.txt 

setting is probably negligible enough to make the PRGRS_NOWAIT_OVERRIDE switch 

unnecessary for NO-WAIT ABL requests. The PRGRS_NOWAIT_OVERRIDE switch has 

greater applicability if the PRGRS_NATIVE_LOCKWAIT value is set to a 

non-negligible period. Only then does the potential negative affect on 

application response time for ABL code that uses the NO-WAIT condition become a 

concern for which the PRGRS_NOWAIT_OVERRIDE might be applied. 

4. The DataServer for MS SQL Server uses a default server lock wait timeout of 

zero - which results in no server blocking from lock contention (and negates the 

need for the PRGRS_NOWAIT_OVERRIDE switch). The maximum value you can wait on 

the server using the PRGRS_NATIVE_LOCKWAIT switch is 32767. Any value larger 

than 32767 is the equivalent of an infinite time period whereby the server would 

block infinitely. If the server were to wait indefinitely for a resource and 

the PRGRS_NATIVE_LOCKWAIT period were infinite then meaningful use of the 

client-side '-lkwtmo' switch would be negated and the need for turning on the 

PRGRS_NOWAIT_OVERRIDE switch would be necessitated in order to ensure a client 

response could be received from the NO-WAIT ABL condition. 


Schema update required when MSS table contains 'timestamp' fileld 

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

A native "timestamp" data was not previosly allowed to be present in a database 

table pulled into a schema holder for MS SQL Server. The OpenEdge DataServer 

for MS SQL Server can now accept such columns into a schema holder as an 

non-updateable column. 

You should re-build your schema holders (or perform update schema) on MSS table 

containing 'timestamp' columns that you could not previously pull. 

================================================ 

DataServers - MS-SQL/ODBC 

================================================ 


DataServers for MSS and ODBC data type support 

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

The DataServers for MSS and ODBC do not support any of the data types that are 

new in OpenEdge Release 10 through 10.1C FCS with one exception: The OpenEdge 

DataServers began supporting the INT64 data type starting in OpenEdge Version 

10.1B. 

================================================ 

DataServers - ORACLE 

================================================ 

Note: OE00147570 Type: Workaround 

Change to ORACLE genclntsh required for ORACLE 9.0.2 on Linux 

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

The ORACLE genclntsh file must be modified for proper operation of the ORACLE 

DataServer with ORACLE 9.0.2. Change the definition of LD to use gcc shared as 

follows: 

Sample of original content: 

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

LD="ld -i -G -z text -L${ORACLE_HOME~/lib" 

shared library link command 

LD="ld -shared -L${ORACLE_HOME~/lib" 


LD_RUNTIME="-R${ORACLE_HOME~/lib" 

LD_OPT="-Map ${MAPFILE~ -h ${CLNT_LIB~" 

Page 23

name inserted into library 

LD_SELF_CONTAINED="-z defs" 

READMESP.txt 

Change to: 

---------- 

LD="gcc -shared -L${ORACLE_HOME~/lib" 


LD_RUNTIME="-Xlinker -R${ORACLE_HOME~/lib" 

LD_OPT="-Xlinker -Map -Xlinker ${MAPFILE~ -Xlinker -h -Xlinker ${CLNT_LIB~" 

name inserted into library 

LD_OUT="-o ${LIB_DIR~/${CLNT_LIB~" 

output specification 

LD_SELF_CONTAINED="-Xlinker -z -Xlinker defs" 


Building Oracle DataServer Executables 

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

For most UNIX platforms, the default client and DataServer executables are able 

to locate and load Oracle's shared library. On the platforms where this is not 

the case, you must build executables using the scripts in the 

/oebuild/make directory. 

For OpenEdge Release 10, executables must be built on AIX, and may need to be 

built on 32-bit HPUX. 


Oracle support with HP 32-bit product is dropped 

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

The last Oracle client that supports HP 32-bit is Oracle 8 which no longer works 

with OpenEdge starting with 10.1C. Any customer that needs to use Oracle on HP 

must migrate to the HP 64-bit product. The HP 64-bit product works on all 

modern HP PA-RISC hardware. Please contact your sale represntative if you need 

to make this platform version change. 


Date/Time/TZ support in DataServer for Oracle 

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

In OpenEdge Release 10.1C Service Pack 1 (10.1C01), The DataServer for Oracle 

has been enhanced to support Oracle DateTime data types and their mapping to 

OpenEdge DateTime data types. The two Oracle DateTime data types, TIMESTAMP (TS) 

and TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ), introduced in Oracle Release 9i will 

be supported in OE Release 10.1C01. Oracle 9i or later releases of the OCI 

client libraries are required for support of these new data types. 

The following datatype mapping will be supported from OpenEdge to the Oracle 

schema holder: 

1. Prior to OE 10.1C01, the Oracle DATE types mapped to a DATE column which held 

the date portion and a surrogate INTEGER column that held the time portion of an 

Oracle DATE data type to seconds precision. This default behavior will be 

retained for backward compatibility. 

2. The Data Dictionary migration utility has been upgraded to handle the mapping 

of an OpenEdge DATETIME data type to an Oracle TIMESTAMP (TS) data type. When 

the Oracle TIMESTAMP is pulled back into a schema image, the Oracle TIMESTAMP is 

then mapped to an OpenEdge DATETIME data type by default. Alternatively, users 

are allowed to change the Oracle TIMESTAMP mapping in their schema image to an 

OpenEdge CHARACTER or DATE type. 

3. The Oracle TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) data type can also be 

Page 24

READMESP.txt 

pulled from an Oracle data source into an Oracle DataServer's schema image. 

This is mapped as DATETIME data type by default. Users are also allowed to 

change the schema image mapping to OpenEdge DATE data type. The value in the 

column is translated from the database time zone into the time zone of the 

OpenEdge client when retrieved into a client application, and visa versa when 

written. 

The DataServer for Oracle has been enhanced to handle OE DATETIME,DATE and 

CHARACTER datatypes that are mapped to Oracle TIMESTAMP datatype in the WHERE 

clause of an OpenEdge client database request. 

SESSION TIME-SOURCE has been enhanced to support expansion of SYSDATE to 

SYSTIMESTAMP. This expands existing support for session:time-source for DATE 

functions to timestamps for DATETIME functions. 

NOTE 1: When a OpenEdge CHARACTER value is mapped to an Oracle TIMESTAMP, it 

must be formatted into a fixed session-level timestamp format of 

'YYYYMMDDHH24MISSFF'. The sesssion level format cannot be changed during the 

DataServer session if character data from the client application is to be 

interpreted correctly in data translation to the server. 

NOTE 2: The OpenEdge DATETIME data type supports fractional seconds up to 

millisecond accuracy and must round off values it receives from Oracle with 

greater precision. 

NOTE 3: After connecting to Oracle Database, DataServer for Oracle issues 

statement 'ALTER SESSION SET TIME_ZONE = '00:00'' . This statment sets the 

Oracle Session Time Zone to UTC. This is essentially done to optimize the 

timestamp conversions requirement for Oracle TIMESTAMP WITH LOCAL TIMEZONE 

datatype column. It is required not to override this setting. 

Not all features of DATETIME are supported in OpenEdge Release 10.1C Service 

Pack 1. 

In particular the following DATETIME features are NOT supported in 10.1C Service 

Pack 1: 

1. Support for the Oracle TIMESTAMP WITH TIME ZONE (TSTZ) datatype will be 

unavailable. 

2. Support for OpenEdge DateTime-TZ datatype will be unavailable. 

3. Support for Oracle TIMESTAMP WITH LOCAL TIME ZONE mapped to CHARACTER will be 

unavilable. 

4. Support of Datetime/Datetime-TZ as a parameter to, or in the result sets of, 

a RUN STORED-PROCEDURE statement. This includes the SEND-SQL-STATEMENT 

procedure, the PROC-TEXT-BUFFER results record and the LOAD-RESULTS-INTO phrase. 

5. On migration, Openedge DATETIME datatype will be mapped to Oracle TIMESTAMP 

datatype by default. Support for mapping OE DATETIME datatype to Oracle 

TIMESTAMP WITH LOCAL TIME ZONE datatype will be unavailable on migration. 


CLOB support in Oracle DataServers 

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

Support for Unicode for the DataServer for Oracle begins in OpenEdge Version 

10.1C. The CLOB data type is also introduced in Release 10.1C for the specific 

purpose of supporting the character widening that is possible in a Unicode 

implementation. Previously, data that exceeded the maximum size of a VARCHAR2 

data type (4000 bytes) was converted to a LONG data type when migrated to an 

Oracle server. Since only one LONG data type is allowed per Oracle table, it 

was anticipated that CLOB support would be needed in its place to handle large 

amounts of character data in a Unicode database implementation. 

The dictionary utility has been updated to migrate OpenEdge database CLOB data 

types to Oracle CLOB data types and to migrate OpenEdge CHARACTER data types 

that exceed Oracle's VARCHAR2 4000-byte maximum size into ORACLE CLOB data 

Page 25

READMESP.txt 

types. Oracle CLOBs are also pulled from the server into the Oracle 

DataServer's Schema Image as CLOB types. 

As there are code pages associated with OpenEdge CLOB data types, they will be 

set to match the code page defined to the Oracle schema holder. The 

column-level CLOB code pages in an Oracle schema image are not modifiable and 

will always be set to match the schema holder code page even if the schema 

holder code page is changed after the database is created. 

Not all features of the CLOB data type made it into the 10.1C FCS Release. 

In particular the following two CLOB features are not supported in 10.1C: 

1. Support for Oracle's Unicode CLOB data type (NCLOB) will be unavailable. 

NOTES: 

Other Oracle Unicode character data types are supported in the Unicode 

implementation for the ORACLE DataServer. 

Oracle implementations that define a Unicode database code page and define their 

Unicode data to CLOB data types are supported in the 10.1C release. 

2. Support for CLOB and LONGCHAR data types with stored procedures. This 

deficiency includes the following subcategories: 

A. Support for LONGCHAR data types as parameters to stored procedures. 

B. Support for a CLOB result set value in the "PROC-TEXT-BUFFER" record upon 

return from "SEND-SQL-STATEMENT" stored procedure execution. 

C. Support for CLOBs in result sets into a VIEW record format. 

D. Support for CLOBs in result sets using LOAD-RESULTS-INTO temp table record 

formats. 

E: Support for CLOBs in result sets using LOAD-RESULTS-INTO with indeterminate 

temp table handles and dynamic server type evaluation. 


Oracle 11g Certified 

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

The DataServer for Oracle has been certified for Oracle 11g against all OpenEdge 

DataServer client platforms. Using the same Oracle database featues, no 

differences in application behavior have been detected between OpenEdge 

connections to 11g and earlier supported Oracle versions. 


Connect from Dataserver to Oracle LDAP Server 

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

In 10.1C service pack 2 (10.1C02) and 10.2A release, the Dataserver for Oracle 

is enhanced to support external password credentials. In particular, Progress 

has tested and certified the use of LDAP directory authentication through the 

global user management capabilities of the Oracle Internet Directory (OID). 

The Oracle DataServer makes database connections through bound OCI client 

libraries that can interface with an Oracle Server using Oracle Advanced 

Security. When an Oracle database environment is configured to use external 

authentication, a centralized service can be shared by Oracle and other 

application environments to provide security and single sign on capability. For 

instance, an LDAP directory service can be configured to provide global user 

authentication and authorization using the "ldap.ora" and/or "tnsnames.ora" 

configuration files. LDAP directory services are one of several ways Oracle 

databases can be configured to use centralized enterprise-level authentication. 

Other external third party authentication mechanisms/adapters are also available 

but have not been tested, including OS authentication, Kerberos, SSL, smart 

cards, and fingerprints. 

Oracle DataServer users obtain external authentication by sending a connection 

Page 26

READMESP.txt 

request with only a user id and password delimiter, absent the actual user id 

and password, as follows: 

/@. 

Depending upon the mechanism used, external credentials may or may not be 

provided independent of the global user management features of the Oracle 

Internet Directory. For instance, public key infrastructure (PKI) digital 

certificates can be passed directly to a target Oracle Enterprise server. 

Oracle Wallets can also be provided in an external password store and may 

perform authentication in conjunction with a particular external authentication 

server. 


'session' context of time zone for OE DatServer client application 

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

In OpenEdge Release 10.1C Service Pack 2 (10.1C02), Release 10.2A and later, 

DataServer for Oracle has been enhanced to allow the use of 'session' context of 

the time zone for their OpenEdge application. Session context or session time 

refers to the time zone context of the OCI driver session to which the Oracle 

DataServer is connected. 

The use of session time zone context in this new feature is not the default 

behavior of the Oracle DataServer. Normally the time zone context of an 

OpenEdge application is the client's time zone. Under normal circumstances, 

Oracle's "session" context or session time is pre-set by the DataServer to 

Universal Time (UTC). This should not be modified in a normal OpenEdge client 

application since this fixed context allows the Oracle DataServer to properly 

convert time zone values to and from the time zone context of the OpenEdge 

client session. 

To override default behavior and turn on session context of the time zone, you 

are required to set -Dsrv switch named "native-tz-context" at the time of 

OpenEdge logical database connection to an Oracle server. Having this option 

turned on causes data transfer to and from the Oracle database to be performed 

using session context. This connect option can be provided with or without a 

comma-separated value, as follows: 

-Dsrv native-tz-context 

Or, 

-Dsrv native-tz-context 

Where is a valid character string that would be acceptable to 

the TIME_ZONE session value passed into the OCI driver, for example, local, 

-5:00, -8.00, dbtimezone, or Europe/London. 

Note: Whenever you specify the '-Dsrv native-tz-context' parameter without a 

corresponding value, the switch will omit the DataServer setting of session 

timezone which is currently set to UTC by default, the expectation is that the 

application is consciously managing the setting external to the OpenEdge 

DataServer client application, such as through the RUN STORED-PROC interface. 

The Oracle command used to set the OCI session time zone context is the 

following: 

ALTER SESSION SET time_zone = ''; 


Buffer storage optimization for NUMBER columns in Oracle DataServers 

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

The Oracle DataServer translates numeric data types from Oracle as NUMBER 

columns and then stores the character format of that NUMBER in OpenEdge record 

buffers when used in an OpenEdge application. 

Page 27

READMESP.txt 

Prior to changes for this fix, the Oracle DataServer used a fixed length buffer 

size of 41 bytes to store the native Oracle type in an OpenEdge buffer column. 

This translation expands the storage requirements of the column in the OpenEdge 

record buffer. This may lead to unexpected overflow when an OpenEdge record 

approaches the maximum record size of 30,000 bytes. 

To minimize the expansion requirements, the Oracle DataServer now optimizes 

buffer storage for NUMBER columns by considering the precision and scale of the 

NUMBER column before expanding for character translation. This means that 

NUMBER columns whose precision and scale require less than 41 bytes in character 

format will now be reduced in size. 41 bytes will still remain the maximum 

translation size for a NUMBER column. Please refer to the following examples: 

(1) NUMBER(1) -> buffer storage size is now 4 (previously it was 41) 

(2) NUMBER(3,7) -> buffer storage size is now 10 (previously it was 41) 

(3) NUMBER(10,-9) -> buffer storage size is now 22 (previously it was 41) 

(4) NUMBER(*,10) -> buffer storage size is now 41 (previously it was 41) 

(5) NUMBER -> buffer storage size is now 41 (previously it was 41) 

(6) FLOAT(5) -> buffer storage size is now 41 (previously it was 41) 

Consider NUMBER(p,s): When both 'p' and 's' are specified, buffer storage is the 

size of whichever is the maximum, either 'p' or 's', plus 3 bytes (for the sign, 

radix and NULL terminator). When 's' is negative, storage size is the sum of 

'p' and the absolute value of 's' plus three (for the sign, radix and NULL 

terminator). If neither 'p' nor 's' is specified, or if the native column is a 

floating point number, buffer storage will be 41 bytes. 

Note:- 

Stack overflow errors are most likely when dealing with very large tables. 

Please increase stack size using '-s' startup parameter on getting stack 

overflow errors. 

================================================ 

Documentation - ABL 

================================================ 


SERVER attribute incorrectly specified as Readable only 

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

The reference entry for the SERVER attribute in OpenEdge Development: ABL 

Reference indicates that the SERVER attribute is Readable. However, for the 

call object handle, the SERVER attribute is also Writable. 

================================================ 

Graphical User Interface - ABL 

================================================ 


ASSIGN on unmodified hidden editor moves data to record/variable 

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

If there is no data in the screen field, the ASSIGN statement does not move data 

into a field or variable. There is no data in the screen field unless you enter 

data in the screen field or DISPLAY data to that field. For example, using an 

ASSIGN statement on an unmodified and hidden editor should not move data into a 

target field or variable. 

However, in previous releases, the ASSIGN statement moved the Unknown value (?) 

into the target. Release 10.1C01 fixes this incorrect behavior. You should 

examine any application that might have relied on the previous behavior. 

Page 28

================================================ 

Open Client - .NET 

================================================ 

READMESP.txt 


Correct Behavior for CancelAllRequests() with .NET Open Client 

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

When calling CancelAllRequests(), an exception is now generated indicating that 

a STOP has been received from the AppServer. This behavior is the intended 

behavior and is compatable with the Java Open Client. In previous releases, this 

API call would wait until a fixed timeout occurred before returning. 


Output DataSets in .NET Send Schema Information 

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

An Output DataSet or DataTable parameter in .NET sends schema information to the 

AppServer even if the SetNoSchemaMarshal method is used and the AppServer is 

running with the -ttmarshal parameter set to 4. 

This is because the c# compiler considers an output parameter unassigned and it 

must be assigned before its value is used, therefore, the .NET proxy code is not 

able to look at the output DataSet or DataTable object to detect if 

SetNoSchemaMarshal was called. 

The .NET client programmer can now specify that they do not want the schema 

info sent from .NET to the AppServer for output DataSet or DataTable parameters 

by setting the new RunTimeProperties.NoSchemaMarshal property to true. It should 

be set before the proxy method is called. 

Note: The property will be used on all DataSet and DataTable parameters for that 

method call. Remember to reset the NoSchemaMarshal property back to false for 

subsequent proxy method calls if desired. 

The property can be used in place of the ProDataTable SetNoSchemaMarshal() 

method. This would be the case if you wanted all DataSet and DataTable 

parameters in a single proxy method to not pass schema info from .NET to the 

AppServer. 

Example code: 

RunTimeProperties.NoSchemaMarshal = true; 

appObj.getMyDSet(1, out myOutDS); 

See the existing SetNoSchemaMarshal() documentation for more details. 


OpenClient DLLs available in a strongly named but digitally unsigned version 

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

OpenEdge now ships a third version of the following OpenClient DLLs for 

applications that need strongly named DLLs that are not digitally signed: 

Progress.ssl.dll 

Progress.o4glrt.dll 

Progress.Messages.dll 

These DLLS are located in the following directory: 

/dotnet/deploy/strongnamed. 

These new DLL versions are shipped in 10.1C04, 10.2A02, and 10.2B. 

To support this choice, the ProxyGen tool was updated and made available in the 

Page 29

READMESP.txt 

10.1C04 and 10.2A02 service packs, as well as version 10.2B. 

The new version of ProxyGen replaces the "Use Strong-named Runtime" checkbox in 

the .NET tab with a combo box. The combo box provides the following three 

choices: 

Digitally Signed 

Strongnamed Signed 

Strongnamed 

The new combo box is initially be set to "Digitally Signed", which is the 

default behavior. 

================================================ 

Open Client - Java 

================================================ 


Java null integer and logical not unknown when passing dataset 

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

When passing datasets between Java and OpenEdge through the AppServer, fields 

with Java primitive data types (integer or boolean) cannot pass null values from 

Java or the unknown value from OpenEdge. On the Java side, a primitive data type 

field with no assigned value is passed or received as the default value for the 

primitive type (0 for integer fields and false for boolean fields). The ABL 

types affected are INTEGER, LOGICAL, INT64, RECID, COM-HANDLE, and 

WIDGET-HANDLE. 

To override this behavior, the RunTimeProperties class now includes the 

RunTimeProperties.setDatasetNullInitials(true) method. An OpenClient application 

calls this method to enable support for passing null or unknown values in 

datasets between OpenEdge and Java. The runtime property only takes effect 

during the definition of the ProDataObjectMetaData object. 

================================================ 

Open Client - Web Services Provider 

================================================ 


R-code header version change when XML-NODE-NAME defined 

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

The OpenEdge Web services provider now supports XML-NODE-NAME in ProDataSet 

parameter definitions. This requires a version change of the r-code header, and 

previous versions of ProxyGen are not able to parse r-code compiled in versions 

starting with 10.1C03 or 10.2A that contain XML-NODE-NAME in DATASET, 

TEMP-TABLE, or TEMP-TABLE field definitions. 


Web Service returns incorrect values for TEMP-TABLE DATE fields 

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

In previous OpenEdge releases, it was possible for values in DATE columns of a 

TEMP-TABLE to become corrupted when received by a Web Service client. 

This problem occurred when more than one Web Service client simultaneously 

requested data from TEMP-TABLE(s) through the same OpenEdge Web Service Adapter 

(WSA). If more than one of the TEMP-TABLEs contained a DATE column, it was 

possible for DATE fields in the TEMP-TABLEs to become corrupt. 

With this release of OpenEdge, the issue is now fixed. 

Page 30

READMESP.txt 

================================================ 

OpenEdge Architect - Tools for Business Logic 

================================================ 


Tools for Business Logic links now have Recursive and Not-Active properties 

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

In a Tools for Business Logic dataset diagram, links between temp tables and 

links between temp tables and buffers now have Recursive and Not-Active 

properties. Set the value of these properties to "true" to have them generated 

in the ABL code. With any other value, the NOT-ACTIVE or RECURSIVE flag for the 

dataset data relation is not set. Please note that there is no migration for 

these properties. Datasets created in a previous version of Tools for Business 

Logic do not have these properties available. To make them available, delete 

the link and then re-add it. 

Note: OE00172430 Type: Workaround 

Temp table diagrams not updated properly under Eclise 3.4 

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

If you use Eclipse 3.4, columns and indexes added to a Tools for Business Logic 

temp table diagram are not immediately visible. The newly added components 

become visible when you resize/move/rename the diagram. 

================================================ 

OpenEdge Replication - Agent 

================================================ 


Processing if OpenEdge Replication Agent Failure Occurs 

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

If an OpenEdge Replication agent failure occurs (for example, if the rpagent 

process ends abnormally), the only way to restart the agent is to restart the 

target database. Under normal circumstances, the broker or watchdog process 

dynamically backs out active transactions for a process after that process 

unexpectedly ends. The dynamic backout process cannot be performed on behalf of 

the OpenEdge Replication agent because target database updates must always be 

driven from the source database. Dynamic backout does, however, update the 

database. 

In the event of an unexpected OpenEdge Replication agent failure, dynamic 

transaction backout does not occur and the target database is left in an 

inconsistent state. This could cause ABL or SQL processes accessing the 

database to end abnormally. After the target database is restarted and 

synchronization is performed, all target database access should proceed 

normally. 


If First Agent Terminates While Two Agents Connect the Server Shuts Down 

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

In a two-agent scenario, if one Replication agent connects to the Replication 

server and then terminates while the server is connecting to the second 

Replication agent, the Replication server terminates with an error-1. 

================================================ 

OpenEdge Replication - Replication 

================================================ 


Startup Parameter -DBService is Case-Sensitive 

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

The -DBService startup parameter is case-sensitive. If you do not enter the 

Page 31

READMESP.txt 

parameter in the correct case, an error appears and indicates that the -S 

parameter is missing. 


Do Not Enable a Quiet Point before Restart of the Replication Server 

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

If the Replication server crashes and you plan to restart it using the following 

command: 

DSRUTIL sdb -C restart server 

where sdb is the name of your source database, do not enable a quiet point on 

the source database before you restart the Replication server. 

================================================ 

Security - Tools 

================================================ 


Behavior change recording auditing events during index rebuild 

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

This bug fix changes the behavior of recording audit events during an index 

rebuild. 

During index rebuild, the _index records for the indexes to be rebuilt are first 

changed to "inactive". After the rebuild is complete, they are changed to 

"active". 

Before this fix, if there was a audit policy defined to record updates on _index 

records for the indexes to be rebuilt, auditing recorded the change. 

After this fix, the events are not recorded. The reason is, if the indexes are 

in a rebuild state, the indexes used to get auditing policies might be invalid 

and we can not get the schema and policy records needed to record the event. 

================================================ 

SQL - 

================================================ 


Changed response time for query with OR predicates on index key 

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

As of OE 10.1C04, OE SQL will, at times, use a different data access strategy 

when a query WHERE clause contains OR'd predicates on an index key.This can 

occur when the index key value can be fetched directly from the index, which is 

so for numeric datatype key columns. 

For this situation, prior releases of OE SQL would at times use a table scan to 

access the data, which gives rapid response time but often poor total execution 

time. Now, OE SQL will use a strategy using index scans, which can provide much 

better total execution time, but may provide slower response time. 

Note - by response time, we mean the time between a query's execution beginning 

and the return of the first row of result set data to the application. 

================================================ 

SQL - SQL Explorer 

================================================ 

Page 32

READMESP.txt 


Enabling an sqlexp ssl connection 

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

The old sqlexp ssl parameters: ssl, nosessionreuse, nsr, nohostverify, nhv, have 

been deprecated. They have been replaced by keywords on a new sqlexp -driverUrl 

option. The basic format of this new option is as follows: 

driverurl 

"jdbc:datadirect:openedge://:;databaseName=;User=;Pass 

word=

cpinternal and cpstream (utf8.pf). 

READMESP.txt 

================================================ 

ADE Tools and Runtime Tools 

================================================ 

Issue Number: OE00182559 

Declarative statements not supported in AppBuilder 

When a .w file defines a temp table or a buffer or is Appserver aware, the 

declarative statements USING and ROUTINE LEVEL ERROR cannot be added in the 

definition section (or anywhere) through the Appbuilder without causing the 

file not to compile. 

To address this issue the Procedure Settings Dialog now has additional 

functionality that allows the user to add declarative statements like 

USING and ROUTINE LEVEL ERROR. A new button on the right hand side opens a 

dialog that allows you to add this code in an editor. 

The declarative statements added here are generated into a new section in 

the source code. This section is written before both the optional 

temp-table definitions and the optional appserver include, thus ensuring 

that these statements always are added before any definitional and 

executable statement as required for the file to compile. 

================================================ 

DATASERVER DataServer 

================================================ 


SQL Server DS crashes doing find prev if no record is available 

SQL Dataserv crashes doing find prev if there was no record available 

================================================ 

DATASERVER MSSQLSRV 

================================================ 


Client hang/crashes after REPOSITION with MSS DataServer 

The client may crash or hang after it has executed a REPOSITION on a table 

with a fields with non-default collation and when you turn off binding. 


ABL client gpf with a simple query if timestamp field is present 

ABL client gpf with a simple query syntax check if timestamp field is 

present on the MS SQL server database. The timestamp field is removed from 

schema holder for non-support. 


SYSTEM ERROR: Date in where clause with native client 10 driver 

When the given ABL is executed with SQL native client 10 driver it raises 

errors, for example: 

- SYSTEM ERROR:Assignment error.(6177) 

- 22005:[Microsoft][SQL Server Native Client 10.0][SQL Server]Operand type 

clash: datime2 is incompatible with int. 

- 37000: [Microsoft][SQL Server Native Client 10.0][SQL Server]Statement(s) 

could not be prepared. 


getting sequence number randomly writes irrelevant data 

Page 34

READMESP.txt 

when two sessions concurrently running getting sequence number randomly 

writes irrelevant data 


Preselect query with by clause with non-indexed field crashes 

Running a PRESELECT query with a BY clause that includes a field that isn't 

part of an index causes the client to crash 


Buffer-value returns 14/02/01 when Initial value is Today 

Temp-Table buffer-value always returns the initial value Today of a date 

field as 14/02/01 when connecting to the SQL Database Schema Holder 

================================================ 

DATASERVER ORACLE 

================================================ 


Buffer overflow errors when a foreign table contains many fields 

The following errors are eager to occur when querying an Oracle table that 

contains a large number of columns (array extents): 

ORACLE row may exceed 32k - can't allocate buffer for table ADMINOPALE.PRO 

(328) (6447) 

Insufficient memory to allocate buffer for ORACLE (5038) 


Oracle ORA-01841 seen in certain situations with date in where 

In certain situations error "ORA-01841: (full) year must be between -4713 

and +9999, and not be 0" is seen using bind variables and having date in 

the where clause. In the dataserver log it can be seen that the wrong 

variable type is being used for the query. 


BLOB field prevents correct display of other fields 

Oracle Dataserver: A BLOB field created before fields with other datatypes 

may prevent these other fields being displayed correctly in a FOR EACH 

...NO-LOCK query. 


High CPU usage after disconnection when using external credentia 

When executing "select * from v$session", the session was still be there. 

================================================ 

DATASERVER Other 

================================================ 


Error 11076 connecting more than 31 DataServer schemas 

Error 11076 connecting the 31st DataServer schema reported in the 

dataserv.lg file, with o.s error 0 (zero) 

================================================ 

DB bm 

================================================ 


TYPE II not reusing space after table delete 

Page 35

READMESP.txt 

Chanalys reports error 14160 after chains are rebuilt through dbrpr 

following table schema deletion, which leads to clusters being unavailable 

for re-use. 

================================================ 

DB DBTLS 

================================================ 


DBTool failure to fix SQL-WIDTH causes Query to fail 

DBTool failure to fix the SQL WIDTH of a decimal field causes SQL query to 

fail 

================================================ 

DB dbutil 

================================================ 


Prodb fails to mapped vm drive with (8265) and (4524) errors 

Prodb/procopy fail with (8265) and (4524) errors when creating a database 

without an existing void structure on a mapped vm drive. 

================================================ 

DB lat 

================================================ 


Latch performance benefit by changing select() to nanosleep(). 

Improved latch performance can be achieved by changing select() to 

nanosleep() 

================================================ 

DB Other 

================================================ 


The VST _Logging-AiJournal is not accurate 

The VST _Logging-AiJournal always shows after imaging as enabled, even if 

it is disabled. 

================================================ 

DB prolog 

================================================ 


prolog fails if lg file > 2 GB 

prolog (offline and online) fails if the lg file > 2 GB 

================================================ 

DB PROSTRCT 

================================================ 


Adding extent online doesn't allow for EGID on new extent 

Sometimes doing a prostrct addonline fails even though all clients could 

access the new extent due to the use of a script with setgid setting up an 

EGID on the users process 

================================================ 

DB proutil 

================================================ 


Page 36

READMESP.txt 

idxcompact requires more bi file space in 10.1x than 9.1E 

Using idxcompact with tables where a large number of records are deleted 

and the indexes are not freed up at record delete time (leaving blocks 

associated with them), can exhaust bi during the idxcompact operation. 

================================================ 

DB rc 

================================================ 


Error 11425 after binary load into a type II storage area 

A table residing in a type I storage area was binary dumped then the table 

definitions were loaded into a type II storage area and data was binary 

loaded back. 

RAW-TRANSFER statement fails on any records binary loaded. 

================================================ 

DB rfutil 

================================================ 


hotspare db crashes during undo phase of crash recovery 

If an OS copy is taken for a hotspare databaseline, it fails during crash 

recovery during Logical Undo Phase, with error 49 when first accessed. 

Progress Solution P141248 for details. 


Roll forward AI fails fails when sequence is larger than 65535 

When the ai sequence number is larger than 65535, rolling forward fails 

with an (8019) error. 

================================================ 

GUI 4GL 

================================================ 


Unable to display content of variable using READ-FILE and ASSIGN 

When using READ-FILE() and ASSIGN to read data into an editor, the data is 

not displayed if the editor is not enabled. 


Session hangs when setting the format of a browse column 

Setting the format of a browse column to a longer format may cause the 

session to crash or hang. 


Return error on db trigger generates wrong events on the UI 

Return error on database trigger generates wrong events on the UI 


Using browse scrollbar arrows truncates column values 

When the browse scrollbar arrows are used to scroll up and down the browse, 

some values in the browse may be truncated. Scrolling the browse by moving 

the scrollbar's thumb or paging up or down by clicking above or below the 

thumb redisplays the correct values 

================================================ 

Page 37

READMESP.txt 

GUI BROWSE 

================================================ 


Crash in Browse widget on Vista 

The session may crash when selecting the scrollbar down arrow on the BROWSE 

widget. The crash occurs when the browse widget does not contain more rows 

than are able to fit in the viewport at one time. 

================================================ 

Install NetSetup 

================================================ 


NetSetup silent install shows messages for registered filetypes 

A NetSetup Silent installation may show message boxes prompting to 

re-register file assoications with the new installation. This means the 

installation is not silent. The messages show up for any extension that we 

try to register that is registered to another application, the most common 

scenario being if multiple OpenEdge releases are installed on the same 

machine. 

================================================ 

LANG 4GL 

================================================ 


Error is not raised properly for RETURN statements 

If an error occurs during the evaluation of an expression on a RETURN 

statement it cannot be caught by a catch block covering the block 

containing the RETURN statement. Furthermore such errors do not propagate 

up the call stack properly when the routine is covered by a ROUTINE-LEVEL 

ON ERROR UNDO, THROW statement. 


Application crashes with error 51 when MEMPTR() is used 

Application crashes with SYSTEM-ERROR sizdtm - invalid type(51) when 

MEMPTR() is used. 


RETURN ERROR from AppServer = No .NET Exception 

Doing a RETURN ERROR from a 4GL program on the AppServer back to a .NET 

Open Client will no longer raise Runtime4GLErrorException. 


FILE-INFO:FULL-PATHNAME, PATHNAME sometimes incorrect 

FILE-INFO:FULL-PATHNAME and FILE-INFO:PATHNAME incorrectly return the root 

directory rather than the correct path under the following conditions: 

1. The file has a two-character name. 

2. PROPATH must be searched to find the file. 

3. PROPATH contains the directory that contains the file. 

4. The PROPATH entry is not relative to the OpenEdge working directory. 

This problem was introduced in 10.1C02 and 10.2A. 


Session crashes when adding then dropping table 

Session crashes when adding and dropping tables in two seperate 

transactions when the program or any of its callers have references to the 

Page 38

database. 

READMESP.txt 

================================================ 

LANG DATASET 

================================================ 


Inconsistent shared record lock during save-row-change 

A save-row-changes tries to put a share lock on the record when connected 

via TCP/IP to the database. This causes error 12300. 


DATA-SOURCE:QUERY before ATTACH causes incorrect FILL() 

Referencing the QUERY attribute of a DATA-SOURCE prior to attaching the 

DATA-SOURCE to a DATASET's BUFFER causes the FILL operation on the DATASET 

to behave as if REPOSITION was specified for the DATA-RELATION relative to 

the specific BUFFER. 

================================================ 

LANG I18N 

================================================ 


SET/UPDATE with "-" can fail with -cpinternal UTF-8 

If using the SET or UPDATE statements to read input from a file, and the 

input field contains the "skip" character ("-"), the ABL client might fail 

to correctly handle the data if using -cpinternal UTF-8. 

If there is a LOGICAL field in the SET or UPDATE frame, the program might 

generate the following errors: 

** Input value: should be yes/no. (87) 

** : Unable to evaluate field for assignment. (143) 

For other datatypes, if the fields in the SET frame are pre-filled (e.g. 

with a DISPLAY statement), each field that is skipped with "-" will be 

empty. 

================================================ 

LANG OO4GL 

================================================ 


WebClient doesn't support static class members or DYNAMIC-NEW 

Code which works under regular Progress will fail when run in WebClient. 


GET accessors of PRIVATE STATIC class properties do not execute 

The GET accessor of a PRIVATE STATIC class property does not execute, even 

if it has an implementation. The current value of the underlying storage is 

retrieved directly, without executing the body of the GET. 


DYNAMIC-NEW gives error 14291 with PUBLIC and STATIC constructor 

DYNAMIC-NEW gives error 14291 when instantiating a class with both a PUBLIC 

and STATIC constructor with the same signature. 


Compiling a class file with SAVE XREF hangs compilation 

Page 39

READMESP.txt 

Compiling a class file with SAVE XREF hangs the compilation: 

-- It is a NEW statement in a constructor that causes this to happen when 

an XREF file is being generated. 

-- The compilation keeps running, without stopping until the prowin32.exe 

process is killed in Task Manager 

-- The output XREF file keeps growing until the prowin32.exe process is 

killed 

-- About 50% of the CPU's resources are used during this period 

-- The problem did not occur in 10.2A FCS. 

================================================ 

LANG Other 

================================================ 


Non-English PROMSGS may be truncated 

If using a non-English PROMSGS file, long messages might be truncated if 

the AVM's -cpinternal does not match the codepage of the PROMSGS file. The 

first occurrence of the message is displayed correctly, but all subsequent 

occurrences will appear truncated. 

================================================ 

LANG Web Services Client 

================================================ 


WebService client sometimes does not time-out during Async call 

Web Service client sometimes does not time-out when performing an 

Asynchronous call after the defined time-out period has expired. The 

client waits for the response when the request should be canceled. 


Memory leak with WSO CONNECT 

Client leaks memory when connecting/disconnecting to Web Services 


LONGCHAR parameters cause memory leak with Web Services client 

The OpenEdge Web Service client has a memory leak when repeatedly calling a 

Web Service with LONGCHAR parameters. 

================================================ 

Management DBAgent 

================================================ 


Scripted database doesn't send abnormal shutdown alert 

When a scripted database has an abnormal shutdown, no alert is sent from 

Management. 

================================================ 

Management Monitors 

================================================ 


File -> Log file Monitor polling not releasing file handle 

Every poll of a log file monitor configured under File -> log file takes a 

file handle but does not release it. 

================================================ 

Open Client .NET 

Page 40

READMESP.txt 

================================================ 


AppServer connection from .NET open client takes one minute 

When there is no Internet connection on the server, the .NET open client 

takes over 60 secs to connect to the AppServer due to the validation of the 

digital signatures of the signed DLLs. 

================================================ 

Open Client Java 

================================================ 


Java null integer and logical not unknown when passing dataset 

Java null value (or the unknown value on the Progress side) integers and 

logicals come through as 0 and false, respectively, when passing datasets 

between Java and Progress via the AppServer. 


Java OpenClient ResultSet not fully JDBC compliant 

The temp-table ResultSet returned by a java OpenClient proxy does not 

provide a fully JDBC 2 compliant java.sql.ResultSet interface. JDBC clients 

expecting full JDBC compliance will fail with an exception calling the 

following methods: 

getBigDecimal(int columnIndex) 

getBigDecimal(String columnName) 

getRow() 

getType() 

getConcurrency() 

getFetchDirection() 

There is no commitment from Progress Software to make the ResultSet fully 

JDBC compliant. 


Java Open Client setNoHostVerify problem 

The setNoHostVerify option of the RuntimeProperties class in Java Open 

Client does not suppress SSL host name verification. 

================================================ 

Replication AGENT 

================================================ 


RPLA crashes when DB table has a recid over 4 billion 

Replication agent will crash when processing recid over 4 billion (2^32) 

range, producing 'RPLA (435) SYSTEM ERROR: lkrels record not locked' error 

messages. 

================================================ 

Replication Other 

================================================ 


Querying _Repl VST causes session crash 

Querying the _ReplSrv VSTs of the target, then the source and then the 

target again causes the session to crash. 

================================================ 

Server Technology Other 

================================================ 

Page 41

READMESP.txt 


Error when making Async AppServer Calls Can Cause Error (49) 

If a communication error occurs when making a call to an asynchronous 

AppServer, the client making the request might crash with error (49). 

================================================ 

SQL ESQL92 

================================================ 


"Already existing value specified" error when running SQL query 

A query that works in 10.1C and 10.1C01 fails in 10.1C02, 10.1C03, and 

10.2A with: 

[DataDirect][OpenEdge JDBC Driver][OpenEdge] Already existing value 

specified. 

================================================ 

SQL ODBC Drivers 

================================================ 


The SQLGetData ODBC API returns invalid data length 

The SQLGetData ODBC function returns invalid data length in the 

StrLen_or_IndPtr output parameter when retrieving data in multiple parts, 

for example from a CLOB field. 

================================================ 

SQL Server 

================================================ 


Performance of SQL query worse after UPDATE STATISTICS 10.1C 

Performance of a query degrades dramatically after running UPDATE 

STATISTICS in 10.1C, going from less than a second to +/- 50 minutes. 


SQL92 server dies with complex UNION queries 

The SQL92 server dies with complex UNION queries that worked in 10.1C and 

regressed in 10.1C02 and 10.2A. 


SQL Crashes on a select query 

SQL Crashes on a select query when duplicate field in the index 


SQL-92 ROUND returns wrong results with negative numbers 

ROUND function can incorrectly round negative values, generating incorrect 

results. 


Server crash is likely error with 10.1C03 

Server crash is likely error with 10.1C03 when running the attached SELECT 

statement 


Encountered internal error at 1934 in rds/xec_qfns.cxx 

The error Encountered internal error in SQL ENGINE at 1934 in 

Page 42

READMESP.txt 

Z:/vobs_sql/sql/src/rds/xec_qfns.cxx. is caused by the following 

caused by LEFT OUTER JOIN with SELECT in the ON clause 

================================================ 

SQL SQL 

================================================ 


UPDATE STATISTICS degrades query performance in 10.1C01 

SQL query runs much more slowly after UPDATE STATISTICS is executed against 

the database than it did before. 


[DataDirect][OpenEdge JDBC Driver][OpenEdge] Internal error -2 

[DataDirect][OpenEdge JDBC Driver][OpenEdge] Internal error -2 (a column 

with the specified column id does not exist in the row) in SQL from 

subsystem 


Internal error in SQL ENGINE when comparing fields with = 

Getting an internal error in sql engine when evaluating a query that 

compares fields in derived tables. If the match is anything but an 

equality match then the problem doesn't occur. 

The error that is returned follows: 

=== SQL Exception 1 === 

SQLState=HY000 

ErrorCode=-211022 

[DataDirect][OpenEdge JDBC Driver][OpenEdge] Encountered internal error in 

SQL ENGINE at 338 in Z:/vobs_sql/sql/src/rds/opt_jfn1.cxx. Contact Progress 

Technical Support 


Query that ran OK under 10.1B crashes under 10.1C03 

A query that ran error free under 10.1B03, 10.1C, 10.1C01 crashes the ODBC 

and the JDBC clients when executed under 10.1C02 and 10.1C03. 


SQL DELETE statement fails with WORD indexed ARRAY fields 

Internal error -2 error is generated by the SQL DELETE statement if the 

result set is not empty and a WORD indexed ARRAY field exists in table. 


Using delete with nested queries and derived tables causes crash 

Running a Delete or Update statement that includes 3 levels of nested 

queries involving at least one derived table may cause a server crash. 

================================================ 

SQL SQL Explorer 

================================================ 


Conv910 causes SQLWidth errors 

Converting a 9.1D database to 10.1C02 or 10.2A with proutil dbname -C 

conv910 causes sqlexp or ODBC or JDBC app no resultset contents to be 

returned but ErrorCode=-210012 

[DataDirect][OpenEdge JDBC Driver][OpenEdge] Column in table has value 

Page 43

exceedi 

ng its max length or precision. 

READMESP.txt 

================================================ 

TTY 4GL 

================================================ 


Incorrect events may be generated upon leave of a fill-in 

Incorrect events may be generated when a fill-in loses focus. This issue 

is more likely to occur when events are programmatically applied to the 

fill-in in response to the ENTRY or LEAVE events. 

================================================ 

DBNav Other 

================================================ 

Issue Number: UNUM00000442 

DB Navigator breaks on BLOB field if max size = ? 

Using Data Dictionary, it's possible to specify the maximum size for a BLOB 

(or CLOB) field to be unknown. The database engine handles this correctly 

by defaulting to the hard-coded limit of 1GB. 

The DB navigator in OE Architect trips over this. Changing the BLOB's 

properties becomes impossible and it will fail to display all fields 

correctly at all times. 

Page 44

Progress OpenEdge 10.1C04 Service Pack Readme

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?