Using configuration files

If you use an extensive set of options to start your server, you may want to store them in a configuration file.

The @data option allows you to specify environment variables and configuration files on the command line. To specify a configuration file, replace data with the path and name of the configuration file:

start_iq @configuration_filename.cfg dbname.db

If both an environment variable and configuration file exist with the same name, the environment variable is used.

Configuration files can contain line breaks, and may include any set of options, including the @data option. Use a number sign (#) to designate lines as comments. Ampersand (&) characters that appear by itself at the end of a line indicates that the previous token is continued on the next line.

See Chapter 1 of the Utility Guide for a complete list of switches.

Default configuration file

%IQDIR15%\scripts directory called default.cfg. This file is also the source of parameters for the Service Manager, the params.cfg file used by Sybase Central, and multiplex configurations. You can maintain consistency by editing parameters in default.cfg.

To increase the amount of virtual memory, you can change the parameters in default.cfg to reduce the virtual memory that other programs use, add swap space to machines, or reduce IQ memory demands (cache sizes, thread count, stack size, and so on).

Security and configuration files

You can use the dbfhide (File Hiding) utility to encrypt your configuration files. See the Adaptive Server Anywhere Database Administration Guide. If you specify log file parameters (-o logfile) in encrypted files, the log is not available to the IQ Agent or start_iq, which cannot display server log information back to the database administrator. You may want to add parameters that do not require encryption on the command line or in a separate configuration file. For example:

start_iq @encrypt_params @other_params

or

start_iq @encrypt_params -n myserv -c 400 -o %IQDIR15%/logfile/myserv.log