Loading SMAT history outside the SMAT folder

You can save SMAT history files outside the site folder by creating a link path to a specific folder/disc. You can then subdivide smatdb files within the smatHistory base on thread names.

These options are available from Options > Site Preferences > SMAT > History Options. These options are based on the site level. That is, the configuration is implemented on all processes. Processes within a site save the history database files to the link path.

  • SmatHistory Link Path

    When this is selected, specify the path to link in the field. The default value is null.

    When you specify the actual path, the engine creates this link when it starts. For example, -s ACTUAL_PATH $HCISITEDIR/exex/processes/process_name/smatHistory.

  • SmatHistory saved base on Thread Name

    When this is selected, SMAT saves the smatHistory database files based on thread names. The default value is "0."

    When this option is selected, sub-folders using the thread name are created within the SmatHistory folder. History smatdb files are saved into these sub-folders. This is the meaning of saving smatdb files based on the thread name.

Note: When the Select a location for sites outside HCIROOT (Optional) option is used on the Site Init dialog box, and multiple processes are saved to the same linked directory, do not use the Maximum options in the SMAT History panel. See Symbolic links.

Because the GUI is limited regarding SMAT searching, support is only for making the link for the smatHistory folder to a specific path. In this way, smatHistory can be subdivided base on thread names.

  1. In Options > Site Preferences > SMAT > History Options set these conditions:
    • Delete the oldest SMAT inbound/outbound history file when history file's number for a thread exceeds number files to 1.
    • Delete the oldest SMAT history file when history file's total size for a process exceeds number KB to 2.
    • Delete SMAT history file for a process when it is older than number days to 3.
  2. Clear SmatHistory saved base on Thread Name first, and then cycle. The smatdb files generate.
  3. Select the check box, restart the engine, and then cycle. The smatdb files are saved into a sub-folder.