13. Building Applications : Creating an Image of the Application : imageapp Command--Build an Image from the System Level
 
Share this page                  
imageapp Command--Build an Image from the System Level
You can build an application image from the operating system level with the imageapp command, described in this section. This command (called abfimage in earlier releases) builds an executable image, like the Image operation from the ABF menu, but uses a command line syntax instead of a forms-based interface. You can include the imageapp command in a command file.
Errors found during the image build are reported on the standard error device. The .lis file in the object code directory contains detailed descriptions of compilation errors (as described in ABF Architecture).
This command has the following syntax:
imageapp [v_node::]dbname applicationname [-uusername][-f]
    [-w][-5.0][+wopen][-oimagename][-GgroupID]
    [-Rrolename]
    [-constants_file='filename']
[v_node::]dbname
Specifies the name of the database.
If you are using a database that resides on a remote host, you must specify the v_node, followed by two colons. For example:
server1::orderdb
applicationname
Specifies the name of the application
If specified, you enter Vision at the Application Flow Diagram for that application. If not specified, you enter Vision at the Applications Catalog frame.
-uusername
Runs the application as if you were the user represented by username.
Files created under this flag are owned by the user actually running the Vision process, not by username.
To use this option, you must be a privileged user.
If you are using Enterprise Access Products (formerly Gateways), see your Enterprise Access documentation before using this parameter.
-f
Forces Vision to recompile the 4GL code for the entire application, even if no changes have been made since the last time it was compiled
-w
Causes all warnings to be turned off. See the section Disabling Warnings for more information.
-5.0
Invokes 4GL in a mode that is compatible with CA‑Ingres Release 5. See 5.0 Applications for more information.
+wopen
Generates warnings if Vision detects statements that are not compatible with OpenSQL
-oimagename
Specifies the name for the image. If the -o flag is not specified, Vision uses the default image name specified in the Applications Defaults window. If no default image name is specified, the image is given the same name as the application.
-GgroupID
VMS: Lets you run or edit the application as a member of the group specified.
Capital letter flags require double quotes in VMS, for example:"-Ggroupid"
-Rrolename
Assigns a role to an application image.
If you specify a role name, you are prompted for the role's password.
VMS: Capital letter flags require double quotes, for example:
"-Rrolename"
-constants_file='filename'
Specifies a file containing values for the application's constants. If the
-constants_file flag is specified, the values in the constants file override the values for the constants stored in the application.
The filename can be the full directory path name for the constants file.
Example--imageapp command:
To recompile all frames and create an image called "orders" for the Order_entry application in the Inventory database, enter:
imageapp inventory order_entry -oorders -f