CA Client Automation - 14.0

PDF
English

Path Definition

Path definitions relocate the files used for active management of the component.
cla140
Path definitions relocate the files used for active management of the component.
A path definition has the following statements in the order given below:
  • start path
  • name statement defining a symbolic name
    The symbolic name can be assigned a value later in the attribute definition indicating whether it should be retrieved or set by invoking the callable function.
  • number of lines equating operating system identifiers to the path of the callable program
  • end path
The operating system identifiers are DOS, MacOS, OS2, UNIX, win16, and win32. This is case-insensitive. When the code provides the component instrumentation that connects to the Service Layer (SL), use the keyword direct-interface. Contrarily, if the SL starts the code at request time, specify the path name of the callable program.
Example: Path Definition
start path
	name = "Performance Info Instrumentation Code"
	win16 = "C:\\someplace\\wincode.dll"
	os2 = direct-interface
	dos = "C:\\someplace\\doscode.com"
	unix = "/someplace/unixcode"
end path
Many path definitions may appear in the component definition; one for each callable function. The path name must be unique among all other path names in a component definition.
See the sample MIF (at the end of this chapter) for examples on the use of the symbols defined in the path definition.