w4glapp loadnrun Command--Run a Loadnrun Application
To run an application from an image using w4glapp loadnrun, start the Loadnrun utility by entering the following command at the command line:
w4glapp loadnrun file [-ccomponent]
[-uusername]
[-ddatabase]
[-menvironment_var]
[-gfilename]
[-ifilename]
[-fakefields]
[-bidi]
[-T{yes|yes,min|all|all,min|no}]
[-A]
[-Lw4gl_log_file]
[-/dbmsflags dbmsflags]
[-/appflags appflags]
Note: w4glapp.exe is dynamically bound to orrun.dll and is available only on Microsoft Windows.
This command takes the following parameters:
file
(Required) Specifies the name of the image file 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.
-ddatabase
Specifies the name and location (host machine) of the database that contains the data to be used in the application. This database need not be the same database that was specified when the application was created.
-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 present, the -m parameter overrides any existing specification of II_LIBU3GL.
-gfilename
Specifies a file containing initial values for the global variables and constants in the application
-ifilename
Lets you specify a file containing overrides for the version and location of any included applications.
For more information about specifying an override file, see How You Can Image Included Applications in the Workbench User Guide.
The values remain in effect for the duration of the current OpenROAD session.
-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
Specifies that OpenROAD application GUI components be displayed from right to left
-A(ppend to log)
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.
Note: 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.
-T(race)
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
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
no
Specifies that the Trace window does not appear, and no log file is created
-Lw4gl_log_file
Specifies the name of the 4GL log file. If a file name is not specified, then the default value of w4gl.log, located in the %II_SYSTEM%\ingres\files directory, is used. The OpenROAD server process has authority to write to this directory. If a different path and file name are specified, such as -L"%II_LOG%\vosa.log", the specified location and file name are used.
The file name can be a fully qualified file name. If there are embedded blanks in the file name, enclose the name in double quotes (").
For the Loadnrun module, you can set metaflags that provide more advanced features.
You can specify a metaflag only on the Loadnrun command line. Metaflags begin with "-/" and must appear after all other command line parameters because their value is terminated by either the next metaflag or by the end of the command.
The available metaflags for Loadnrun and their possible values are:
-/dbmsflags dbmsflags
Specifies initial DBMS connection flags for the applications. The string of flags following this metaflag overrides the string of DBMS flags that was specified in the application's Property Inspector.
-/appflags appflags
Passes parameters to your application. These parameters are placed in the AppFlags attribute of the SessionObject of the running application.
Note: Appflags contains an array of appflag objects. Each appflag object consists of a name, and an array of values.
Application parameters may be of the following kinds:
Positional parameters
A parameter is positional if there is no equal sign (=) in its first 32 characters. All other parameters are keyword parameters.
Keyword parameters
A keyword parameter is assigned the values that come after the equal sign (possibly separated by commas if an array of values is used).
Appflags are subject to the following restrictions:
• Values and names must not contain a space, tab, newline, carriage return, quote, apostrophe, comma, or the equal sign.
• Names must not exceed 32 characters.
Note: If these rules are violated, the behavior is undefined.