Features Introduced in OpenROAD 11.2
New and Updated Features
Ingres 11.2 Support
All platforms of OpenROAD 11.2 now support Ingres 11.2.
New abf2or Frame Template
You can use the frame template abf2or to create a new OpenROAD frame containing fields according to the field definitions of an existing ABF frame. This lets you harvest the user interface. However, no 4GL code conversion is provided.
COPY TABLE...APPEND Supported
Support for the COPY TABLE...APPEND SQL syntax is supported by Ingres 11.1 or higher is added to the 4GL. For more information, see Copy Statement.
New Environment Variables
Several environment variables are added to this release of OpenROAD—three for general use, and three for memory management. For more information, see Environment Variables in the Workbench User Guide.
General Environment Variables
The following general environment variables are added:
• II_W4GL_DETAILS_ON_MOUSEWHEELCLICK
• II_W4GL_DISABLE_WINDOWS_GHOSTING
• II_W4GL_DPI_AWARENESS
II_W4GL_DETAILS_ON_MOUSEWHEELCLICK
Specifies whether to activate the On Details and On ChildDetails events by clicking the mouse wheel.
II_W4GL_DISABLE_WINDOWS_GHOSTING
Specifies whether the Windows ghosting feature for OpenROAD applications will be disabled (if set to TRUE).
“Windows ghosting” means that the Windows OS will put a ghost window in place of the application window when it considers an application as “not responding.” The ghost window looks like the application window with its title having a “(Not responding)” text appended.
For OpenROAD frames, the Windows ghosting could cause problems during processing of events, for example:
• Status bar is not updated
• Moving of ghost window of frame is possible, but OpenROAD application does not get the information of the new position
• Input buffering when using CurFrame.BlocksFrames=FALSE does not work
Default: FALSE
II_W4GL_DPI_AWARENESS
OpenROAD is DPI aware, which may make some fields smaller so the parent background becomes visible, resulting in the image of some fields with a bitmap background appearing more than once. To correct this, a new environment variable is added.
You may set this variable to these values:
DPI_UNAWARE (-1, the behavior before DPI awareness was implemented)
DPI_SYSTEM_AWARE (-2, the default)
DPI_PER_MONITOR_AWARE (-3)
DPI_PER_MONITOR_AWARE_V2 (-4)
DPI_UNAWARE_GDISCALED (-5)
Environment Variable for WebGen
The following environment variable is added:
II_W4GL_RS_ROUTES
Lets you set the path of a JSON-format file containing alternate routing information for applications running within an OpenROAD application server. It serves to convert existing applications using RemoteServer.Call4GL() statements with 'http' routing into JSON RPC requests using 'http-jsonrpc' routing. This eliminates any 4GL changes needing to be made.
Environment Variables for Memory Management
The OpenROAD memory management system is now configurable, and by default, issues fewer system memory calls, which can improve performance.
OpenROAD maintains a list of segments to store different type of buffers. When some memory is needed, OpenROAD checks its pool of segments for an available buffer. If none is available, then OpenROAD requests more memory from the operating system. When some memory is released, OpenROAD checks whether the buffer belonged to a segment that now contains only freed buffers. If this the case the, segment is returned to the OS.
These buffers and segments had static sizes that can be not big enough when running some applications on some system, hence the need to be able to modify these static values dynamically.
The following general environment variables are added:
• II_W4GL_SEGMENT_SIZES
• II_W4GL_SEGMENT_TOT_SIZE
• II_W4GL_TRACE_MEMORY
II_W4GL_SEGMENT_SIZES
Specifies a list of seven numbers, separated by commas, that define the size, in bytes, of the seven types of fixed buffers.
Default: 32, 128, 256, 512, 1024, 2048, 4096
II_W4GL_SEGMENT_TOT_SIZE
Specifies the size, in bytes, of buffer segments that OpenROAD allocates.
Default: 524160
II_W4GL_TRACE_MEMORY
Specifies whether to include the number of buffers OpenROAD has allocated and freed when printing output to the trace window. Analyzing the trace may help you decide which value to use:
TRUE
Specifies that the number of buffers should be written to the trace
FALSE
(Default) Specifies that the number of buffers not be written to the trace
Manage OpenROAD Server Configuration File with the Orserveradm.py Python Script
The Server Manager manages and monitors the OpenROAD Server. The Python script orserveradm.py provides a command line interface for managing the OpenROAD Server configuration file (orserver.json).
For more information, see Manage the Installation with orserveradm.py Script.
Command Line Utilities Get New Replacement Parameters
The following w4gl command line utilities get new filename replacement parameters:
-Lfilename
Specifies the name of a log file. If the log path specified is not a full path, the file is created in the %II_SYSTEM%\ingres\files directory. You may include the following replacement parameters in the file name.
%p
Replaced by the Process Identifier (PID)
%d
Replaced by the current date in YYYYMMDD format
%t
Replaced by the current time in HH_MM_SS format
-Ttitletitle
Replaces the title of the OpenROAD Trace window with title. If the title contains spaces, you must enclose it with single or double quotes.
For more information, see Managing and Deploying Applications in the Workbench User Guide.
New UrlConnection Class
The UrlConnection class provides methods for transferring data and files from and to URLs, supporting different transport protocols such as HTTP(s), (S)FTP, SCP, and SMTP.
It wraps calls to functions of the
libcurl library.
On a typical connection:
1. Several options are set using attributes InputFile, InputObject, OutputFile, OutputObject and methods SetOption and SetOptions.
2. A Perform() method invocation is used to actually execute the transfer to or from the URL (which must be one of the options set before).
3. The GetInfo() method invocations can be used to get information about the Perform() operation executed.
Attributes
Errortext
InputFile
InputObject
OutputFile
OutputObject
Methods
GetInfo
Perform
ResetOptions
SetOption
SetOptions
For more information, see UrlConnection Class.
XMLSchemeCache Class Gets New Attribute
This class now has the Errortext attribute, which contains the error message from the last method invocation.
Data Type: varchar(2000)
4GL Access: R
Note: This method has been deprecated on Windows. It therefore always returns ER_FAIL, and the Errortext indicates that the method is not implemented with this message: RemoveSchema failed with error 0x80004001
For more information, see Errortext Attribute in the Language Reference Guide.
WebView2 Updates
The SubForm class has a new attribute: Webpage, which enables or disables displaying a web page. It also has two new methods:
GetWebView2Version
Returns the WebView2 version, if found
Url
Displays a URL in a SubForm
For more information, see SubForm Class.
Support for the Enterprise Access ODBC Gateway
This version of OpenROAD supports the Enterprise Access ODBC Gateway.
The Query Tool now supports Enterprise Access to ODBC and can be used to access Actian Zen databases.
OpenROAD applications can now access ODBC databases through Enterprise Access to ODBC. ODBC support is only for database access and not as an OpenROAD source code database. See the Enterprise Access documentation for details (
OpenROAD and Enterprise Access to ODBC) and the II_DICTIONARY_OK setting in
Environment Variables for All Platforms.
Deprecated Features
eClient Deployment Deprecated
The term eClient has several definitions:
eClient Runtime
This uses the w4glapp.exe and orrun.dll to run 4GL image files. The normal OpenROAD Runtime uses w4gldev.exe/w4glrun.exe and or4glnt.dll.
eClient Deployment
The Internet Explorer ActiveX deployment technique was used in OpenROAD 6.2 to deploy OpenROAD image files using the eClient Runtime. Loadnrun is another technique to deploy OpenROAD image files using the eClient runtime.
OpenROAD 11.1 has deprecated the Internet Explorer ActiveX deployment of OpenROAD image files using the eClient runtime. OpenROAD 11.1 will continue to support deployment of OpenROAD image files using the eClient runtime.