Considerations for implementing dynamic network identifier

You need to consider the following when implementing dynamic network identifier:

All dynamically created networks have the same subarea, but have different NETIDs.
The model network must have paths defined to at least the first adjacent subarea that is contacted when the NETID is initially established. After this, you can use dynamic path update to dynamically define paths. See Dynamic path update. Paths require careful planning, especially when the paths go to the same subarea number in several different networks.
Note: When a dynamic network is cleared, any paths created by dynamic path update for that network are also cleared and lost.
Because the model network represents other networks, the model network must contain all necessary GWNAU definition statements for any NETID of any network that the model represents. GWNAU definition statements cannot be dynamically added, modified, or deleted.
For a link station and its line to support dynamic NETID, the GROUP definition statement for the INN link must have NETID=(name,ANY) coded as a parameter. For leased and switched links, this is coded on the respective GROUP definition statements. For NTRI links, this is coded on the LOGICAL GROUP(s). To establish dynamic NETID capability, code NETID=ANY on the GROUP definition statement. All INN links defined under the dynamic GROUP have the ability to use it.
Note: When coding NETID=(name,ANY) on the GROUP, name must be either the default or predefined network within the gateway NCP. If name is omitted and NETID=(,ANY) is coded, the default network is assumed.
Ensure that the necessary GWPATH definition statements are coded for the cross-domain resource managers that you are contacting.
To display static and dynamic networks, use the command
```
D NET,COS,ID=ncp_name,NETID=*
```
This displays the COS table associated with a NETID. The model network is displayed as *NETWORK. Any static networks appear above the model network, and any dynamic networks are displayed below it. Remember, the results are with respect to the VTAM® where you issue the command. When displaying a remote NCP, a dynamic network might appear as static because it is a predefined network in the local NCP or because it is in the network that issued the VTAM network identifier.
To display the network identifier of active link stations, use the command
```
D NET,STATIONS,A
```
A leased line can change its network identifier to a predefined network identifier. To do this, code NETID=(name,ANY) on the GROUP definition statement for the leased line. A model network is not needed.
You need to ensure that the value specified on the HSBPOOL operand on the BUILD definition statement is large enough to accommodate the number of addresses needed to represent all SSCPs and logical units that participate in cross-network sessions (specified on the NUMADDR operand on the GWNAU definition statement) for all predefined and dynamic networks.