Delete an Application Using the DestroyApp Utility

To use the DestroyApp utility, enter the following command at the command line:

w4gldev destroyapp database application [-nowindows] [-uusername]
[-Lfilename] [-vversion] [-ccomponent] [-t]
[-T{yes|yes,min|yes,logonly|all|all,min|all,logonly|no}] [-A]

Note: DestroyApp is not available as a menu command in Workbench because you can simply delete an application or an application version by clicking File, Delete.

An exit code of zero (0) means success; a non-zero exit code indicates an error.

The following describes the parameters for the DestroyApp utility:

Specifies the name and location of the database in which the application resides

Specifies the name of the application to delete

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.

Note: Only the database administrator for the database, the Ingres system administrator, or a superuser can use this parameter.

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 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.

Specifies the version of the application to delete

IMPORTANT! If you do not specify a specific version, the entire application will be deleted.

Identifies a single component to be deleted from the application

Specifies that transactions are committed after each component is deleted from the database

IMPORTANT! Using this parameter decreases contention and log file use. However, if your database server terminates abnormally or the DestroyApp utility is aborted before completion, only some of the application components are deleted.

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.