Read in options from the specified environment variable or configuration file. See Using configuration files.

If you want to protect passwords or other information in the configuration file, you can use the File Hiding utility to obfuscate the contents of the configuration file. See File Hiding utility (dbfhide).

Display the setting for the specified configuration option. For example, suppose you ran the following command to configure dbsupport to prompt when possible:

dbsupport -cc promptdefy

When you run the command dbsupport -ecc, the following setting is returned:

-cc "promptdefy"

Check the status of a crash report that has been submitted to iAnywhere Solutions.

For example, the following command inquires about the status of submission ID 66:

dbsupport -is 66

Check for updates to your build of SQL Anywhere.

You can also check for updates using Interactive SQL and Sybase Central. See Checking for software updates.

Generate a list of submission IDs for all reports that have been submitted to iAnywhere Solutions. For example:

dbsupport -ls

This returns information similar to the following:

Submission ID: 4
Minicore dump 20051220_133828_32116 reported: Wed Mar 15 16:31:56 2006
Submission ID: 98
Minicore dump 20051229_221211_3221 reported: Wed Mar 22 16:33:26 2006

Display information about a specific report that has been submitted to iAnywhere Solutions. For example:

dbsupport -ps 4

This returns information about submission 4:

Minicore dump 20051220_133828_32116 reported: Wed Mar 15 16:31:56 2006

Submit a crash report and diagnostic information to iAnywhere Solutions. For example:

dbsupport -sc 20051220_133828_32116

Use the -lc option to see a list of reports that have not been submitted.

Submit only diagnostic information to iAnywhere Solutions.

For more information about the diagnostic directory, see SADIAGDIR environment variable.

Change the prompting behavior of dbsupport. You can specify one of the following options:

If you specify this option, its value becomes the default used by the Support utility. The setting is stored in the dbsupport.ini file in the diagnostic directory.

The following command configures the Support utility so that it does not submit reports and never prompts the user to submit reports:

dbsupport -cc no

Specify the retry delay, in seconds, for submitting a report if the previous attempt is unsuccessful. The default delay is 30 seconds.

If you specify this option, its value becomes the default used by the Support utility. The setting is stored in the dbsupport.ini file in the diagnostic directory.

The following dbsupport command specifies that failed submissions should be retried every 3 seconds, up to a maximum of 4 times before giving up:

dbsupport -cr 4 -cd 3

Specify the address where an email is sent after a crash occurs. The email is sent using the email-server SMTP server. Optionally, you can specify the port that should be used, and the user-id and password used to authenticate with the SMTP server.

Specify a program that is called when a crash occurs.

If you specify this option, its value becomes the default used by the Support utility. The setting is stored in the dbsupport.ini file in the diagnostic directory.

The database server supports three substitution parameters that set up information that is passed to the crash-handler-program:

You can use $F, $P, and $S as alternatives to %F, %P, and %S. Because different command shells interpret the characters % and $, both are provided. For example, on 4NT, %F is substituted with the value of the environment variable F; $F can be used to avoid this substitution.

Suppose you have a crash handler program in c:\test.bat that contains the following commands:

copy %1 c:\archives
echo %2

On Windows, the following command tells dbsupport to launch c:\test.bat with two parameters when a crash occurs. If the report is being submitted, this program is called before the report is submitted.

dbsupport -ch "c:\test.bat \"%F\" parm2"

The substituted path specified by %F is sent to c:\test.bat as the first parameter. The parameter parm2 is sent to c:\test.bat as the second parameter. Note that quotation marks must be used to specify a crash handler program that takes arguments.

In the example above, additional quotes were used around the full path to the generated report file. To avoid problems accessing the report file that dbsupport is using, the crash handler program should make its own copy of the report file.

Remove the crash handler settings that are stored in the dbsupport.ini file. For example:

dbsupport -ch-

Specify a string that identifies you in the submission report. If you specify this option, its value becomes the default used by the Support utility. The configuration is stored in the dbsupport.ini file in the diagnostic directory.

The following examples specify a customer identification string for dbsupport:

dbsupport -cid myid@company.com

dbsupport -cid "MyClientApp 1.0"

Remove the customer identification string from the dbsupport.ini file. For example:

dbsupport -cid-

Configure the HTTP proxy host and port used to submit error reports.

On Windows, the syntax -cp autodetect is also supported. If you specify this option, then if a proxy server and port have been set using Internet Explorer, and they are currently enabled, dbsupport configures its proxy server and port using the system setting. You can set the proxy server and port in Internet Explorer on Windows by choosing Tools » Options » Lan Settings.

Remove HTTP proxy host and port settings from the dbsupport.ini file. For example:

dbsupport -cp-

Specify the number of times a failed submission should be retried.

If you specify this option, its value becomes the default used by the Support utility. The setting is stored in the dbsupport.ini file in the diagnostic directory.

The following dbsupport command specifies that failed operations should be retried every 3 seconds, up to a maximum of 4 times before giving up:

dbsupport -cr 4 -cd 3

Specify that dbsupport does not check the server for the status of the submission. For example, the following command submits the report, but does not check for the status of the new submission:

dbsupport -nr -sc 20051220_133828_32116

By default, dbsupport checks whether there is already a fix for the problem being submitted.