Use the NETWORK definition statement in the NCP major
node to identify each network attached to a gateway NCP.
To define the nonnative networks, the following changes
are required:
- Add one or more NETWORK definition statements (one is required for each nonnative network).
NETWORK identifies a nonnative network that attaches to the gateway
NCP. On the NETWORK definition statement, the following operands can
be coded:
- Add one ACTPU operand (optional).
ACTPU specifies whether
SSCPs in the nonnative network can activate the gateway NCP.
- Add one COSTAB operand (optional VTAM-only operand).
COSTAB
specifies a user-written Class of Service table to be used for routes
that originate in the gateway NCP and that are within the nonnative
network being defined. No table is needed if the only COS table entries
used are ISTVTCOS and the default Class of Service.
- Add one MAXSUBA operand (optional).
This operand specifies
the MAXSUBA value for the nonnative network. It is not required if
all nodes in that network use extended network addressing.
- Add one SALIMIT operand (optional).
The SALIMIT operand specifies the maximum number of subareas that
can be used in the nonnative network.
- Add one NUMHSAS operand (required).
This operand specifies
the number of subarea nodes in the nonnative network that can communicate
concurrently with the gateway NCP.
- Add one SUBAREA operand (required).
This operand specifies
the subarea address of the gateway NCP as known in the nonnative network.
- Add one or more GWNAU definition statements (required).
Add one or more
GWNAU definition statements after the NETWORK definition statement
when defining nonnative networks.
NETWORK NETID=netb
GWNAU NETID=neta,NAME=cdrmname,ELEMENT=nn
- NETID
- Identifies the network in which the following CDRM name resides
to the nonnative network.
This value must match the value for
the NETID operand in the BUILD definition statement.
- NAME
- Identifies a CDRM to the nonnative network.
- ELEMENT
- Reserves an element address in the nonnative network to represent
that CDRM.
Some elements can be reserved in a dynamic
pool, while others can be predefined. A predefined element is one
that is associated with a particular resource name. Each resource
that has a cross-network session with a resource in this network must
have at least one address. (Some application programs require more
than one address if they have multiple sessions.)
Note: If you
plan to have session monitors communicating from one network to another,
it is strongly recommended that you code two GWNAU definition statements
for each network management session (one for the primary-to-secondary
session and one for the secondary-to-primary session) to reserve session
control blocks in the NCP for the network management session.
Optionally, you can preassign session-related control blocks
(HSCBs) to application programs (or SSCPs) that have many cross-network
sessions. The HSCBs are preassigned to the element that represents
the application program in the gateway NCP. This ensures that at least
the preassigned number of control blocks are available to represent
sessions with the application program.
- Update NCP PATH definition statements by doing the following steps:
- Add new NCP PATH definition statements to define routes that originate
in the gateway NCP subarea for the network identified by the previous
NETWORK definition statement. See Cross-network routing.
- Map virtual routes to explicit routes for these routes. For virtual
routes that terminate in a VTAM® host subarea, the forward and reverse virtual route numbers must
match. See Cross-network routing.