You may choose to start & stop the service as root or as a designated user (e.g. sqdr) with appropriate authorities.
Using systemd:
Using systemd insures that the service will be restarted if it should terminate prematurely.
The installer creates a file /etc/systemd/user/sqdrsvc, and a directory /etc/systemd/user/sqdrsvc.d, where you can customize the environment (e.g. add directories to LD_LIBRARY_PATH) by adding a file called custom.conf.
You can use a non-privileged user such as sqdr for running the service.
- To start service
$ systemctl start sqdrsvc
- To stop service
$ systemctl stop sqdrsvc
- To restart service
$ systemctl restart sqdrsvc
- To get status of service
$ systemctl status sqdrsvc
- to enable the service to start at boot time
$ systemctl --user enable sqdrsvc
- to enable the service to run whether or not the user has an active terminal session
# loginctl enable-linger userid
e.g.
# loginctl enable-linger sqdr
Depending on what control database you are using, make sure that the Db2 or SQL Server service has started (or is running and accessible if you are using a remote control database)
using sqdrsvcd.sh
You can scripts start, stop, and status and place them in /opt/StarQuest (i.e. one level above sqdr, so they get preserved if sqdr is removed and reinstalled). start includes environment variables needed for certain ODBC drivers (bundled drivers, Salesforce bundled driver, Informix, IBM DB2 ODBC). These are explained in the ODBC documentation.