Command Line Method to Run an Application from an Image

To run an application from an image, start the RunImage utility from the Start menu, Run command or by entering the following command at the command line:

w4glrun appfile.img [-ccomponent] [-uusername] [-ddatabase]
    [-menvironment_var] [-gfilename] [-ifilename]
    [-realfields] [-bidi]
    [-T{yes|yes,min|yes,logonly|all|all,min|all,logonly|no}] [-A]
    [-/dbmsflags dbmsflags] [-/appflags appflags]

Parameters are explained in Parameters for the RunImage Utility (see Parameters for the RunImage Utility). The following additional flags are available from the command line:

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.

Lets you use this command as if you were another user, username.

Note: You, not username, own all files created by OpenROAD.

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.

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, the -m parameter overrides any existing specification of II_LIBU3GL.

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.

For more information about creating an initialization file, see Specify Initial Values for Global Variables and Global Constants (see Specify Initial Values for Global Variables and Global Constants).

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 (see How You Can Image Included Applications).

Instructs OpenROAD to create a separate windows system control for each field on a form. By default, OpenROAD multiplexes a single control for many fields to save time and memory.

Specifies that OpenROAD application GUI components be displayed from right to left

Controls the display of the Trace window by entering one of the following values:

Specifies that the Trace window appears but suppresses all informational system messages

Specifies that the Trace window appears minimized as an icon, and all informational system messages are suppressed

Specifies that the Trace window does not appear, but all messages are saved in a log file without informational system messages

Specifies that the Trace window does appear and all messages are written

Specifies that messages are written to the Trace window, which appears minimized as an icon

Specifies that the Trace window does not appear, but all messages are saved in a log file

Specifies that the Trace window does not appear, and no log file is created

Appends the trace output of the current command to the end of the existing error log file.

Note: The error log file, w4gl.log, is located in %II_SYSTEM%\ingres\files.

For more information, see How You Can Set Metaflags for the RunDBApp and RunImage Utilities (see How You Can Set Metaflags for the RunDBApp and RunImage Utilities).

Note: If you have installed the OpenROAD Development package, you can use the w4gldev runimage command instead of w4glrun.