Startup Command Files

RTclient

An RTclient process does not have any standard startup command files. It is up to you to decide whether command files should be loaded, and to create and define those files. Startup command files can be loaded with the TutCommandParseFile function. For information on creating and using RTclient command files, see the TIBCO SmartSockets Tutorial.

This example illustrates a typical RTclient command file: 

setopt project           HST 
setopt server_names      workstation1

RTserver

An RTserver process has a standard startup command file, named rtserver.cm. The RTserver startup command files contain generic information that RTserver needs to know, such as how to locate and connect with RTclient processes, how to locate and connect with other RTserver processes, and how often to check for network failures.

This example illustrates a typical RTserver startup command file: 

setopt editor                    emacs 
setopt real_number_format        %f 
setopt server_read_timeout       10

RTserver recognizes three levels of startup command files. When first invoked, it searches for and executes the commands in each file, in this order:

  1. the system-level rtserver.cm file in the SmartSockets standard directory

    2. RTserver searches for a system-level process command file rtserver.cm in the SmartSockets directory standard, in RTHOME:

    • UNIX: $RTHOME/standard
    • OpenVMS: RTHOME:[STANDARD]
    • Windows: %RTHOME%\standard

      • The rtserver.cm file can be modified to reflect RTserver options that are meant to be system-wide. To edit this file, change the current directory to the SmartSockets standard directory and use an editor to add or change the system-wide option settings.

  1. the user-level rtserver.cm file in the user’s home directory

    2. RTserver searches for an rtserver.cm file in the user’s home directory and, if found, executes the commands in that file. This file is the ideal place to set options specific to all your projects. To create this file, use an editor to open a new file named rtserver.cm in your home directory and add the options you choose.

    The location of the home directory that RTserver searches varies by operating system:

    • UNIX: $HOME
    • OpenVMS: SYS$LOGIN
    • Windows: %HOME%
  2. the file specified by the -command argument, or the local-level rtserver.cm file in the current directory (if the -command argument is not specified)

    3. RTserver reads and executes the rtserver.cm file found in the current directory, that is, the directory from which RTserver is being run. Use this file for any application-specific option declarations. The local command file is read last, allowing you to override any values set for RTserver options in other command files.

If you have configured Basic Security features (as outlined in Security), RTserver also loads the command file sdbasic.cm. To locate this file, RTserver uses the same three discovery techniques outlined here for locating rtserver.cm.

RTmon

An RTmon process has a standard startup command file, named rtmon.cm. The RTmon startup command files contain generic information that RTmon needs to know, such as what values to use for IPC-related timeouts, what project to monitor, and what node RTserver resides on.

This example illustrates a typical RTmon startup command file: 

setopt project                 HST 
setopt server_names            cosmos 
setopt editor                  emacs

RTmon recognizes three levels of startup command files. When first invoked, it searches for and executes the commands in each file, in this order:

  1. the system-level rtmon.cm file in the SmartSockets standard directory

    2. RTmon searches for a system-level process command file rtmon.cm in the SmartSockets directory standard, in RTHOME:

    • UNIX: $RTHOME/standard
    • OpenVMS: RTHOME:[STANDARD]
    • Windows: %RTHOME%\standard

      • This file can be modified to reflect RTmon options that are meant to be system-wide. To edit this file, change to the directory and use an editor to add or change the system-wide option settings.

  1. the user-level rtmon.cm file in the user’s home directory

    2. RTmon searches for an rtmon.cm file in the user’s home directory (specified by the HOME environment variable) and, if found, executes the commands in that file. This file is the ideal place to set options specific to all your projects. To create this file, use an editor to open a new file named rtmon.cm in your home directory:

    • UNIX: $HOME
    • OpenVMS: SYS$LOGIN
    • Windows: %HOME%

      • and use the editor to add the options you choose.

  2. the file specified by the -command argument, or the local-level rtmon.cm file in the current directory (if the -command argument is not specified)

    3. RTmon reads and executes the rtmon.cm file found in the current directory, that is, the directory from which RTmon is being run. It is in this file that you place any project-specific option declarations, such as the name of the project and where to find RTserver. The local command file is read last, allowing you to override any values set for RTmon options in other command files.

TIBCO SmartSockets™ User’s Guide
Software Release 6.8, July 2006
Copyright © TIBCO Software Inc. All rights reserved
www.tibco.com