On UNIX, you can start a configured Historical Server in two ways:
Execute the histserver command from a UNIX shell prompt. If you use this method, you must type all appropriate parameters each time.
Execute a script file that contains the histserver command and all appropriate parameters. If you followed the configuration instructions in Chapter 2, “Configuring Historical Server”, you would start Historical Server using the following command:
install_dir/install/RUN_histServerName
where install_dir is the Sybase root directory and histServerName is the name of the Historical Server you want to start.
Regardless of which method you use:
Verify that the Adaptive Server to be monitored and its corresponding Monitor Server are running.
Use the same account each time you start Historical Server, if you want the new instance to have access to previously recorded sessions. See “The operating system start-up account” for more information.
Set the $SYBASE environment variable to the root directory of the Sybase installation.
The $SYBASE environment variable must contain the name of a directory that has the appropriate locales and charsets subdirectories for Historical Server. These subdirectories were created and populated by the installation procedure.
The $SYBASE environment variable also identifies the default location of the interfaces file. Use parameters to the histserver command to override the default location.
Historical Server displays the following message to indicate that start-up was successful:
Initialization is over. Ready to accept connections.
Historical Server writes messages to its log file during start-up. You can ignore these messages if start-up was successful. If start-up is not successful, examine the log file to research the problem.
The default path name for the Historical Server log file is hs.log in the current directory at the time of start-up. You can override this default path name with the -l parameter (the letter l) to the histserver command.