Rules for matching names by object type are listed here:

logicalLink

If the linkName attribute is network qualified, the netID must be the same as the netID of the VTAM topology agent host receiving the GET request.

logicalUnit

If the luName attribute is network qualified, the netID must be the same as the netID that VTAM display commands require for displaying the resource. The VTAM topology agent host netID will always work. For dependent LUs that are attached to a non-native PU type 2.1 node (nonnative network attachment), the netID of the physical unit will also be accepted. A non-network qualified name always has a default netID that is the same as the VTAM topology agent host netID.

For application logical units, the luName attribute can specify the name coded on the ACBNAME operand of the APPL definition statement. For this name to match, it must be either non-network-qualified or network qualified with the netID of the VTAM topology agent host. When a match occurs, the VTAM topology agent host returns data for the application program with the specified ACBNAME.

crossDomainResource

If the nonLocalResourceName attribute is specified with a network-qualified name, the name and netID must exactly equal the name and netID of the CDRSC for a match to occur. If a non-network-qualified name is given, the name will only match a CDRSC that has been added to the VTAM topology agent host SRT directory.

The nonLocalResourceName attribute can also specify the name coded on the LUALIAS operand of a CDRSC definition. For this name to match, the name must be either non-network-qualified or qualified with the netID of the VTAM topology agent host.

appnRegisteredLU

If the nonLocalResourceName attribute is specified with a network-qualified name, the name and netID must exactly match the name and netID of the registered LU. If a non-network-qualified name is given, the name will only match a registered LU with the netID of the VTAM topology agent host.

The following example shows a GET request for resource data:

 msg CMIP-1.ROIVapdu (invokeI D 196610, operation-
 value 3, argument (baseManagedObjectClass 1.3.18.
 0.0.1844, baseManagedObjectInstance (distinguishe
 dName (RelativeDistinguishedName (AttributeValueA
 ssertion (attributeType 1.3.18.0.2.4.6, attribute
 Value "NETA")), RelativeDistinguishedName (Attrib
 uteValueAssertion (attributeType 1.3.18.0.0.2032,
  attributeValue "SSCP1A")), RelativeDistinguished
 Name (AttributeValueAssertion (attributeType 1.3.
 18.0.0.2032, attributeValue "NCP3AB8")))), attrib
 uteIdList (AttributeId 2.9.3.2.7.33, AttributeId
 1.3.18.0.0.2035, AttributeId 1.3.18.0.0.2036, Att
 ributeId 1.3.18.0.0.1971, AttributeId 1.3.18.0.0.
 2080, AttributeId 2.9.3.2.7.35, AttributeId 2.9.3
 .2.7.36, AttributeId 2.9.3.2.7.39)))

Note from the example that the class specified is t4Node and that the object instance is NETA;SSCP1A;NCP3AB8. There is no scope or filter specified. The attribute list is specified and contains the following attributes:

• availabilityStatus
• subareaAddress
• subareaLimit
• gatewayNode
• nativeStatus
• operationalState
• proceduralStatus
• usageState