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

Creates a new service, or overwrites one if one of the same name exists. If you supply -y, the existing service is overwritten without confirmation. You cannot delete a service while it is running.

You must supply the full path to the executable that you want to use as a service, as the account under which the service is running may not have the appropriate SQL Anywhere installation directory in its path.

You must supply parameters appropriate for the service you are creating.

See:

Names the Microsoft Windows account. All services run under a Microsoft Windows account. If you run under an account you have created, you must name the account with the -a option and supply a password with the -p option.

The Login as a Service privilege is required for all accounts other than the LocalSystem account. If an account does not have the Login as a Service privilege enabled, you are prompted to enable it. If the -y option is also specified, dbsvc attempts to grant the Login as a Service privilege without prompting you. If the -q option is specified without the -y option, you are not prompted to grant the Login as a Service privilege and dbsvc fails.

Specifies that all the services in the list must have started before the service being created is allowed to start.

You can specify the display name or the service name. Service names are verified to see if they already exist. If the specified service name cannot be found, the Service utility (dbsvc) checks to see if there is a service with a matching display name.

It is recommended that you create a dependency on the Transport Data Interface (TDI) for TCP/IP to ensure that the connection starts correctly. For more information about the TDI, see  http://msdn.microsoft.com/en-us/library/ms797340.aspx.

Provides a name for the service. This name appears in the Windows Service Manager. If you do not specify the -sn option, the default service name is SQL Anywhere - svc. For example, the following service is named SQL Anywhere - myserv by default.

dbsvc -as -w myserv
"C:\Program Files\SQL Anywhere 12\Bin32\dbeng12.exe"

To have the service name myserv appear in the Windows Service Manager, you need to execute the following (entered all on one line):

dbsvc -as -sn myserv -w myserv
"C:\Program Files\SQL Anywhere 12\Bin32\dbeng12.exe"

Specifies the type for this service. You can choose from the following types:

Displays the command used to create the service. This option can be used to output the creation command to a file, which can then be used to add the service on another computer or restore a service to its original state if changes have been made to it. You must specify the -g option or -l option with -cm or the command fails. Specifying -g displays the creation command for the specified service, while specifying -l displays the creation command for all services.

If the specified service does not exist, the command to delete the service is generated. For example, if service_1 does not exist on the computer, dbsvc -cm -g service_1 would return the following command to delete the service_1 service:

dbsvc -y -d "service_1"

If the service does not use the LocalSystem account, there is no way to retrieve the password, so it is not included in the command that is generated. If you created the service with -a user -p password, only -a user is included in the output.

Writes output from the Service utility (dbsvc) to the specified file. The -o option must be specified before the -d, -g, -l, -u, and -x options. When you specify the -o option for both dbsvc and for the executable that you are running as a service (for example, the database server), log files are created for both. For example:

dbsvc -o out1.txt -y -as -w mydsn install-dir\bin32\dbsrv12 
-n mysrv -o c:\out2.txt

In this case, the output from dbsvc is logged to out1.txt, while the output from the database server is logged to c:\out2.txt.