Run an Application from the Database Using the RunDBApp Utility
To run an application from a database, start the RunDBApp utility in one of the following ways:
• (Windows only) Access RunDBApp through the Start menu, Run command
• Enter the following command at the command line:
w4gldev rundbapp database application [-ccomponent]
[-uusername] [-menvironment_var] [-gfilename] [-ifilename]
[-nowindows] [-fakefields] [-bidi] [-vversion]
[-T{yes|yes,min|yes,logonly|all|all,min|all,logonly|no}] [-Ttitletitle] [-A]
[-Lfilename] [-/dbmsflags dbmsflags] [-/appflags appflags]
Parameters for the RunDBApp Utility
The RunDBApp utility takes the following parameters:
database
Specifies the name and location of the database in which the application resides
application
Specifies the name of the application to run
-ccomponent
Specifies a component (frame or procedure) to use as the starting point for the application. By default, the application starts with the frame or procedure specified in the application's Property Inspector.
-uusername
Lets you use this command as if you were another user, username
Note: You, not username, own all files created by OpenROAD.
-menvironment_var
Lets you specify the name of a different environment variable to contain your list of DLLs or shared libraries to be searched when resolving 3GL procedure calls. If it is present, this parameter overrides any existing specification of II_LIBU3GL.
-gfilename
Specifies a file containing initial values for the global variables and global constants in the application.
The values remain in effect for the duration of the current OpenROAD session.
-ifilename
Lets you specify a file containing overrides for the version and location of any included applications.
-nowindows
Lets the application run without the window manager running.
This option does not provide full “batch mode” execution, because some interaction with the application still may be required through the Trace window.
-fakefields
Instructs OpenROAD to multiplex a single control for many fields to save time and memory. By default, OpenROAD creates a separate Microsoft Windows system control for each field on a form.
This parameter is provided for backward compatibility. It sets the FormField.RequireRealField runtime default to FALSE.
Note: Some field types only provide all their capabilities when they are created as Windows system controls.
-bidi
Displays OpenROAD application GUI components from right to left.
-vversion
Specifies the version number of the application to run
-T
Controls the display of the Trace window by entering one of the following values:
yes
Specifies that the Trace window appears but suppresses all informational system messages
yes,min
Specifies that the Trace window appears minimized as an icon, and all informational system messages are suppressed
yes,logonly
Specifies that the Trace window does not appear, but all messages are saved in a log file without informational system messages
all
Specifies that the Trace window does appear and all messages are written
all,min
Specifies that messages are written to the Trace window, which appears minimized as an icon
all,logonly
Specifies that the Trace window does not appear, but all messages are saved in a log file
no
Specifies that the Trace window does not appear, and no log file is created
-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.
-A
Appends the trace output of the current command to the end of the existing error log file. Otherwise, that log file is replaced. This entry field can be used only if Execute in Background is enabled.
The error log file, w4gl.log, is located in %USERPROFILE%\AppData\Local\OpenROAD\Profiles\installation_ID. If the -L flag is passed, a new name and location can be provided for the OpenROAD log file.
-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
-/dbmsflags and -/appflags
An exit code of zero (0) means success; a non-zero exit code indicates an error. The exit code can be set by the application executed using the SessionObject.ExitCode attribute.