OS/2 Example Files displays a list of OS/2 example files provided with SystemView
Agent. The paths listed here indicate the default drive and subdirectory
used during installation. If you installed SystemView Agent in a different
drive or directory, adjust the file location accordingly. ┌──────────────────────────────────────────────────────────────────────────────┐
│ Table 54. OS/2 Example Files │
├────────────────┬──────────────────────────┬──────────────────────────────────┤
│ FILE NAME │ LOCATION │ DESCRIPTION │
├────────────────┼──────────────────────────┼──────────────────────────────────┤
│ MIEXAMP.C │ [boot │ The source code used by the DMI │
│ │ drive]:\DMISL\EXAMPLES\MI│ MIF browser to interact with the
│
│ │ │ Management Interface. │
├────────────────┼──────────────────────────┼──────────────────────────────────┤
│ NAMES.C │ [boot │ The source file for the overlay │
│ │ drive]:\DMISL\EXAMPLES\CI│ instrumentation for the sample │
│ │ │ component. │
├────────────────┼──────────────────────────┼──────────────────────────────────┤
│ NAMES.DEF │ [boot │ The module definition file for │
│ │ drive]:\DMISL\EXAMPLES\CI│ use in building the DLL file for
│
│ │ │ the overlay instrumentation. │
│ │ │ The NAMES.DEF file defines the │
│ │ │ entry points and other charac- │
│ │ │ teristics of the DLL. │
├────────────────┼──────────────────────────┼──────────────────────────────────┤
│ NAMES.DEP │ [boot │ The dependency file for use in │
│ │ drive]:\DMISL\EXAMPLES\CI│ compiling the NAMES.C file. You
│
│ │ │ might need to modify this file │
│ │ │ to accommodate path differences │
│ │ │ in your system. │
├────────────────┼──────────────────────────┼──────────────────────────────────┤
│ NAMES.MAK │ [boot │ The make file for use in com- │
│ │ drive]:\DMISL\EXAMPLES\CI│ piling and linking the sample │
│ │ │ component instrumentation │
│ │ │ (NAMES.C). You can use this │
│ │ │ make file with the NMAKE utility │
│ │ │ provided by version 2 of the IBM │
│ │ │ C/C++ Tools product. You might │
│ │ │ need to modify this file to │
│ │ │ accommodate path differences in │
│ │ │ your system. │
├────────────────┼──────────────────────────┼──────────────────────────────────┤
│ NAMES.MIF │ [boot │ The sample MIF file that defines │
│ │ drive]:\DMISL\EXAMPLES\CI│ the NAMES component. You might │
│ │ │ need to modify the path defi- │
│ │ │ nition in the file to accommo- │
│ │ │ date path differences in your │
│ │ │ system. │
├────────────────┼──────────────────────────┼──────────────────────────────────┤
│ NAMEDIR.C │ [boot │ The source file for the direct- │
│ │ drive]:\DMISL\EXAMPLES\CI│ interface instrumentation for │
│ │ │ the sample component. │
├────────────────┼──────────────────────────┼──────────────────────────────────┤
│ NAMEDIR.DEP │ [boot │ The dependency file for use in │
│ │ drive]:\DMISL\EXAMPLES\CI│ compiling the NAMEDIR.C file. │
│ │ │ You might need to modify this │
│ │ │ file to accommodate path differ- │
│ │ │ ences in your system. │
├────────────────┼──────────────────────────┼──────────────────────────────────┤
│ NAMEDIR.MAK │ [boot │ The make file for use in com- │
│ │ drive]:\DMISL\EXAMPLES\CI│ piling and linking the sample │
│ │ │ component instrumentation │
│ │ │ (NAMEDIR.C). You can use this │
│ │ │ make file with the NMAKE utility │
│ │ │ provided by version 2 of the IBM │
│ │ │ C/C++ Tools product. You might │
│ │ │ need to modify this file to │
│ │ │ accommodate path differences in │
│ │ │ your system. │
├────────────────┼──────────────────────────┼──────────────────────────────────┤
│ NAMEDIR.MIF │ [boot │ The sample MIF file that defines │
│ │ drive]:\DMISL\EXAMPLES\CI│ the NAMEDIR component. │
└────────────────┴──────────────────────────┴──────────────────────────────────┘