The path definition is used to specify the location of the files used for active management of the component. The MIF file for a component can contain more than one path definition, as long as the name statement for each path definition is unique within the component definition.

The operating system identifiers used in the path definition include dos, macos, os2, unix, win16, win32, win9x, and winnt. These identifiers are not case sensitive.

If you specify a keyword of win32, you are indicating that the component instrumentation referenced in this definition runs on either Windows NT or Windows 95 (or greater). Use of winnt or win9x indicates that the instrumentation runs only on the platform specified by the keyword.

The syntax for the path definition is:

start path
      name  = "name identifying instrumentation code"
      win32 = "C:\\directory\\filename.dll"
      os2   = "direct interface"
      dos   = "C:\\directory\\filename.com"
      unix  = "/directory/filename"
end path

The keyword direct interface in the example indicates that the component instrumentation code is a continuously running process that is registered with the service layer.

The value of the name statement can be used as part of the attribute definition to invoke the instrumentation code indicated in the path definition. Read Value Statement for more information about how the code is invoked.