This topic describes sample path definitions.

Communication between two network accessible units (NAUs) over a subarea connection requires a definition of at least one route connecting them. This definition includes a physical and logical path between the two. PATH definition statements are the representations of the routes VTAM® takes to communicate with other subarea nodes. Paths are defined only for hosts with subarea function.

The physical path between two subarea nodes is an explicit route (ER). The logical path between two subarea nodes is a virtual route (VR). PATH definition statements define both explicit routes and virtual routes. You can code one PATH definition statement for each destination subarea, or you can code a single PATH definition statement defining the routes to multiple destination subareas.

The first operand on a PATH definition statement is typically the DESTSA operand. DESTSA specifies the destination subarea numbers for which this PATH statement is defining routes. The numbers specified must not exceed the value specified on the MXSUBNUM start option.

On a PATH definition statement, the operands ER0-ER15 define explicit routes to adjacent subareas. Each ERx operand specifies the subarea number of the adjacent subarea and, optionally, a transmission group number for the explicit route being defined. The x in the ERx operand designates the number of the explicit route.

The operands VR0-VR7 associate a virtual route with an explicit route. explicit routes to adjacent subareas. Each VRx operand specifies the explicit route number to which the virtual route is mapped. The x in the VRx operand designates the number of the VR.

In addition, the VRPWS00-VRPWS72 operands specify the pacing window size for combinations of VRs and transmission priorities.

You do not need to define PATH definitions for APPN connections.

For more information about paths, see the z/OS Communications Server: SNA Network Implementation Guide.

The remainder of this topic shows path definitions for each of the subarea-capable nodes in the network depicted in Figure 1.