The target-resource name field contains the name of the first network component described by the embedded NS RU.

• If the flag byte (byte 4, bit 5) in the Deliver RU indicates that only one target-resource name is included, the target-resource name field contains the name of the first and only target resource. The target-resource name is derived from the resource address in the NS RU. The target resource name is the same as the name of the originator of the embedded NS RU when the RU does not contain a resource address.

  When only one target-resource name is included in the Deliver RU, the Deliver RU ends with the X'00' type byte that indicates the end of the configuration hierarchy list.

• If the flag byte in the Deliver RU indicates that multiple target-resource names are included, the target-resource name field contains the name of the first target resource, and subsequent names (1–M additional names) follow the X'00' type byte that indicates the end of the configuration hierarchy list.

  When multiple target-resource names are included in the Deliver RU, the configuration hierarchy list is provided only for the first target resource. The Deliver RU ends with the X'00' type byte that indicates the end of the additional target-resource name fields.

On all the operating systems, the configuration-hierarchy name fields provide a list of PU and link configuration information. The number of names varies. See Table 1 for standard CNM headers. The configuration-hierarchy list contained in the Deliver request is generated by using one of the following algorithms. The hierarchy contains the list of addressable nodes between the target-resource name and the PU that contains the boundary function for the resource.

• When the resource is a PU or an LU at a PU type 1 or PU type 2 node, the configuration hierarchy is an ordered list of the network names of each component in the connection, starting from the resource and including the name of the PU containing the boundary function. The resource name is not included in the list.
• When the resource is an LU, PU, or link that does not require boundary function support at a PU type 4 or PU type 5, there is no list.
• When the resource is a link station, the configuration hierarchy is an ordered list of names consisting of the link and PU type 4 or 5 node to which the line is attached (and which is the originator of the embedded RU).
• When the resource is a PU for which a load is being requested, there is no list.