Feedback
Did this article resolve your question/issue?

   

Article

What is the -IOEverywhere client startup parameter?

« Go Back

Information

 
TitleWhat is the -IOEverywhere client startup parameter?
URL Name000042839
Article Number000166167
EnvironmentProduct: OpenEdge
Version: 10.2B02 and higher, 11.x
OS: All supported platforms
Question/Problem Description
What is the -IOEverywhere client startup parameter?
Summary of the undocumented client startup parameter -IOEverywhere
What is the default for -IOEverywhere?
Are there any particular cases where the default setting for -IOEverywhere should not be used?
Why is -IOEverywhere undocumented? 
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement NumberEnhancement OE00193613
Cause
Resolution
Until OpenEdge 10.2B02, ABL had restrictions on where an input-blocking statement ( UPDATE, SET, PROMPT-FOR, CHOOSE, INSERT, WAIT-FOR, READKEY, or PROCESS EVENTS) could be used. Input-blocking statements could not be used in a user-defined function, a non-void method, class destructors and some database trigger blocks.

In OE 10.2B02 new startup parameter was introduced: -IOEverywhere <n>, where <n> is either 0 or 1. For service packs of Release 10.2B, the default is 0, which means the new feature is off and everything works as before. However, when "-IOEverywhere 1" is specified, input-blocking statements may be used in almost every context. There is only one remaining restriction. This occurs if the application.
  1. Uses .NET and is in a WAIT-FOR Application:Run() statement.
  2. Does a stacked input blocking statement for an ABL non-modal window in one of the places that has always been restricted from doing input-blocking.
In these cases, the restriction remains in place.

In OpenEdge11, the default became "-IOEverywhere 1", thus removing the restriction (except for the special cases above) without the need to use the startup parameter.

The default value for -IOEverywhere is normally appropriate. It can be changed if the pre-OE11 behavior is needed for compatibility, or possibly to work around a bug.  For this reason, -IOEverywhere is currently undocumented except in the release notes.  There are no plans to document -IOEverywhere in our existing documentation.

The parameter is intended for use under the direction of Technical Support as a workaround due to a defect.  If this parameter needs to be used, please contact Technical Support for assistance in duplication and logging of a defect for the issue being encountered.
Workaround

 
Notes
Last Modified Date12/9/2016 10:49 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.