Defining APPN cross-domain resources is optional, and it is recommended that you not define them to save time. However, there are cases where you might need to define APPN cross-domain resources. For instance, if you want APPN and LEN connectivity to a given independent LU, then both APPN and LEN adjacent link stations need to be defined in the independent LU's adjacent link station list.
In an APPN network, you can define APPN cross-domain resources at network nodes and end nodes. If you decide to define APPN cross-domain resources at an end node, the APPN directory will not be updated, but the information will be used to improve searching.
To define an APPN cross-domain resource, code the CPNAME operand on the CDRSC definition statement. When you code CPNAME, the APPN directory is updated with the location of the cross-domain resource. However, if the resource is found in the directory to have been registered or dynamically defined, the update is ignored, but no message is generated.
The CPNAME and NETSRVR operands are both valid on the CDRSC definition statement. If both operands have the same value, the resource specified by CPNAME is assumed to be the network node. If CPNAME and NETSRVR have different values, the resource specified by NETSRVR is assumed to be the network node.
If only CPNAME is defined under the CDRSC definition statement, the resource it specifies is assumed to be a network node. If the resource is not a network node, an error message indicates that the APPN information is not valid.
The CPNAME and CDRM operands can be specified on the same CDRSC definition statement to allow a path to be defined through the subarea and APPN networks to reach the resource.
The NATIVE and SUBAREA operands are valid with the CPNAME operand and will be used to update the APPN directory to improve searching. The NATIVE operand will improve searching in multiple subnetwork configurations. The SUBAREA operand will improve searching when the resource can only be reached across a CDRM session.