Utility Switches List
This file contains alphabetical list of the valid Utility switches. An overview of switches can be found in Programming with Apex.
Include switch aliases.
Use all options valid for the command.
Compute architecture on which Apex is running.
Note: Set at installation. Do not change.
When not empty, the value of this switch overrides the use of
$USER as the replacement of the Author
attribute during keyword replacement.
The value of this switch will be whitespace stripped.
Only check for problems, do not make any repairs.
Perform any maintenance on any state involving compilation. This includes the state associated with importing and exporting.
Include Context switches.
Location of the dialog boxes.
Note: Set by installation. Do not change.
Adjusts the default setting for the delete dialog box.
Specifies the maximum number of symbolic links displayed by the verification query.
To have an effect, this switch must be set prior to starting apex.
Location of the online documentation.
Xterm command to use to create the xterm used when executing a program
Adjusts the default setting for the delete dialog box.
When false, the default setting is "Create Deleted Version".
When true, the default setting is "Delete from view only".
To have an effect, this switch must be set prior to starting apex.
Startup command for the Rational Apex online help browser.
Netscape is provided with Apex.
To use a different browser, change this value.
Unix command to cause the browser to open the online help documents.
Two keyword replacements are supported:
<browsername> first token in APEX_HELP_BROWSER
<helpfilename> the name of the file to be opened
If a value is not specified and
the simple name of the APEX_HELP_BROWSER command is
"netscape" (note that if you specified a full pathname,
like /usr/apps/bin/netscape, the default will still apply),
this switch will use the following to open the help file:
<browsername> openURL(<helpfilename>)
Version histories to check.
Home directory for Rational Apex release.
Note: Set by installation. Do not change.
Check for abandoned locks and aborted updates. When repair is requested, abandoned locks are recovered and aborted updates are reverted or completed.
Directory containing the files that define the GUI menus.
Note: Set by installation. Do not change.
Path to the message server.
Note: Set by installation. Do not change.
Identifies the path on which to search for message catalogs and switch registration files.
Note: Set by installation. Do not change.
Check the UNIX permissions.
Replace an existing name with a new name. Otherwise, objects that have an existing permanent name are not affected.
Keep shell windows (those created by the Tools > Shell command) when Apex is exited.
Directory containing the rules files..
Note: Set by installation. Do not change.
Include Session switches.
Command used to create an xterm when a Tools > Shell command is requested.
You can use this switch to change the default shell window type (xterm) launched by the Tools > Shell command:
For example,
However, use of "unmanaged" results in the xterms not appearing in the window directory, not being able to pass command-line options to the command, and the created xterms are not closed automatically when Apex exits.
An alternate method of changing the default shell window type which does not have the restrictions associated with "unmanaged" can be found in the description of the Tools > Shell command.
The directory containing the source objects.
When set, Rational compiler-specific menu items are not enabled. Is set when invoking apexinit -summit
Note: Rational Summit/TM is separately licensed from Apex.
Shell windows not to be managed by Apex. These windows will not appear in the Windows window and will not be closed when Apex exits.
Xterm command to use when creating xterms from Apex.
You can use this switch to change the default shell window type (xterm) launched by the Tools > Shell command:
For example,
However, use of "unmanaged" results in the xterms not appearing in the window directory, not being able to pass command-line options to the command, and the created xterms are not closed automatically when Apex exits.
An alternate method of changing the default shell window type which does not have the restrictions associated with "unmanaged" can be found in the description of the Tools > Shell command.