Using the HP-UX libIO Library

Hardware Path Related Routines
Each I/O node is assigned a hardware address that is unique among its siblings (no
two siblings can have the same hardware address). Concatenating a series of
hardware addresses together describes a path through the I/O Tree with an I/O
node at the end point. Each node can be uniquely identified by a hardware path.
However HP-UX 11i v3 introduces the agile naming model. So each node can be
uniquely identified by a hardware path in either the legacy or agile naming model.
The libIO routines associated with hardware path are listed in Table 7:
Table 7 – Hardware and Path Related Routines in libIO
Routines Description
io_hw_path_to_node()
Returns the token for the specified hardware
path.
io_init_hw_path()
Initializes the hardware path structure.
io_hw_path_to_str()
Converts the path specified by hw_path to
the string.
io_str_to_hw_path()
Converts a string representing the hardware
path to hw_path_t structure.
io_node_to_hw_path()
Gets the hardware path of the given node.
io_is_hwpath_legacy()
Determines whether it is a legacy hardware
path or agile hardware path.
io_legacy_to_new_hwpath()
Converts a hardware path data structure
used on pre- HP-UX 11i v3 to the hardware
path data structure used on the HP-UX 11i
v3.
io_new_to_legacy_hwpath()
Converts a hardware path data structure
used on HP-UX 11i v3 to the pre-HP-UX 11i
v3 hardware path data structure.
io_hw_compare()
Compares the contents of two pre-HP-UX 11i
v3 hardware paths.
io_hw_compare_ext()
Compares the contents of two HP-UX 11i v3
hardware paths.