 |
Figure 1 shows a basic ATM configuration
enabling HPR APPN communication through native access. Figure 1. Basic ATM configuration
The major elements of an ATM configuration that must be defined
to VTAM® are:
- VTAM connection to the IBM® Open Systems Adapter
- The port on the IBM Open
Systems Adapter through which the ATM network is accessed
- The transmission groups (TGs) that route data:
- Across permanent virtual channels (PVCs)
- Across switched virtual channels (SVCs)
- To connection networks
- Defining VTAM connection
to the IBM Open Systems Adapter
-
Figure 2 illustrates a VTAM connection to the IBM Open Systems Adapter.
Figure 2. VTAM connection to the IBM Open Systems Adapter
VTAM communicates
with the IBM Open Systems Adapter
using an HPDT MPC connection. For more information about HPDT MPC connections,
see Multipath channel connections.
Define the following key characteristics of the MPC connection
in the transport resource list (TRL) major node: - Characteristics you must specify
- Name of the IBM Open Systems
Adapter
- Subchannel addresses of the WRITE and READ paths
- Name of the port associated with the IBM Open Systems Adapter to which the WRITE and READ paths are
connected
- Characteristics specified by default
- Line control (LNCTL=MPC)
LNCTL=MPC is required for ATM native
connections and is automatically defined for you when you code the
PORTNAME operand on the TRLE definition statement in the TRL major
node. The only possible value for ATM native connections is LNCTL=MPC.
- MPC level (MPCLEVEL=HPDT)
MPCLEVEL=HPDT is required for ATM
native connections and is automatically defined for you when you code
the PORTNAME operand on the TRLE definition statement in the TRL major
node. The only possible value for ATM native connections is MPCLEVEL=HPDT.
In addition to required user-specified characteristics,
optional characteristics can be defined. See the z/OS Communications Server: SNA Resource Definition
Reference for information about how to code the definition statements
and operands used to define both the key and optional characteristics.
The example shown in Figure 3 is based
on the configuration in Figure 2 and represents
definitions in the VTAMLST data set for the VTAM in HOST1. Following Figure 3 are descriptions of the major nodes,
definition statements, and operands used in Figure 3 to define VTAM connection
to the IBM Open Systems Adapter.
Figure 3. Definition of VTAM connection to the IBM Open Systems Adapter TRL1 VBUILD TYPE=TRL
OSAX TRLE WRITE=(501),
READ=(500),
PORTNAME=PORTA,
LNCTL=MPC,
MPCLEVEL=HPDT,
.
.
.
| Definition statements |
Description |
|---|
| Name of the IBM Open System Adapter |
The name field of the TRLE definition
statement indicates that the name of the IBM Open Systems Adapter is OSAX. The name specified here is
the name of the IBM Open Systems
Adapter. The name of the IBM Open Systems Adapter is defined during IBM Open Systems Adapter configuration on the ATM Native Settings
panel, which is part of the OSA Configuration pull-down option accessed
through the OSA/SF OS/2 interface.
|
| Subchannel Addresses of the WRITE and
READ Paths |
The WRITE operand on the TRLE
definition statement specifies that the subchannel address of the
WRITE path is 501. The READ operand specifies that the subchannel
address of the READ path is 500. The last two digits of the subchannel
address of the READ path must match the Even Unit Address. The Even
Unit Address and the ATM OSA-2 physical port are defined during IBM Open Systems Adapter configuration
on the ATM Native Settings panel, which is part of the OSA Configuration
pull-down option accessed through the OSA/SF OS/2 interface.
Note: Only one subchannel address is specified for the READ path and one
for the WRITE path. The address specified for the READ path must be
an even number that is one less than the address specified for the
corresponding WRITE path.
|
| Name of the Port Associated with
the IBM Open Systems Adapter
to which the WRITE and READ Paths are Connected |
The PORTNAME operand on the TRLE
definition statement specifies that the name of the port associated
with this IBM Open Systems Adapter—through
which an ATM network can be accessed—is PORTA. The name specified
here is the name of the ATM OSA-2 physical port. The Even Unit
Address and the ATM OSA-2 physical port are defined during IBM Open Systems Adapter configuration
on the ATM Native Settings panel, which is part of the OSA Configuration
pull-down option accessed through the OSA/SF OS/2 interface.
|
- Defining the port on the IBM Open Systems Adapter through which the ATM network is accessed
-
Figure 4 shows a port example.
Figure 4. Port on the IBM Open
Systems Adapter through which the ATM network is accessed
VTAM accesses the
ATM network through a port on the IBM Open Systems Adapter. Associated with the port are links
used for permanent virtual channels (PVCs) and switched virtual channels
(SVCs). These PVCs and SVCs carry data across the ATM network. Define
the following characteristics of the port in the external communication
adapter (XCA) major node:
See the z/OS Communications Server: SNA Resource Definition
Reference for information about
how to code the definition statements and operands used to define
these characteristics. No other characteristics of the port need to
be defined.
Figure 5 is based on
the configuration in Figure 4 and represents
definitions in the VTAMLST data set for the VTAM in HOST1. Following Figure 5 are descriptions of the major nodes,
definition statements, and operands used in Figure 5 to define the port on the IBM Open Systems Adapter through which the ATM network is accessed.
Figure 5. Definition of port on the IBM Open Systems Adapter through which the ATM
network is accessed OSAXCA1 VBUILD TYPE=XCA
PORT PORTNAME=PORTA,
MEDIUM=ATM
The PORTNAME operand on the PORT definition statement specifies
that the name of the port on the IBM Open Systems Adapter with which the links used for PVCs
and SVCs are associated is PORTA. The name specified here must also
be defined on the PORTNAME operand on a TRLE definition statement
in the TRL major node. Both specifications of the port name must match
the name of the ATM OSA-2 physical port.
1
- Defining the APPN transmission groups that route data across the
ATM network
-
Figure 6. TGs that route
data across the ATM network
VTAM uses transmission
groups (TGs) to route data across the ATM network. These TGs can be
over PVCs and SVCs, as shown in Figure 6. One TG is associated with each PVC or SVC.
In networks where
multiple nodes can communicate with one another across an ATM network,
you can define TGs to connection networks. This can minimize the amount
of definition required to establish routes among the multiple nodes.
Defining transmission groups over permanent virtual channels:
Permanent virtual channels (PVCs) represent permanent connections.
They are reserved by the ATM network and are available as long as
the network is active. PVCs appear to VTAM as nonswitched lines. As such, the TGs that are assigned
to them are defined in groups headed by a GROUP definition statement
that specifies DIAL=NO.
Because PVCs are associated with a
port on the IBM Open Systems
Adapter, the TGs that are assigned to them are defined in the XCA
major node that defines the port with which the PVCs are associated.
Define the following key characteristics of a TG over a PVC in
the XCA major node: - Characteristic you must specify is the name of the PVC.
- Characteristics you should specify
- Name of the remote node with which VTAM can communicate over the TG
- Route calculation characteristics
- Cost per connect time
- Cost per byte
- Security
- Propagation delay
- Effective capacity
- User-defined values
Note: IBM supplies default
TG profiles that define these characteristics for best effort and
reserved bandwidth connections across public and private ATM networks. IBM recommends that you use these
default TG profiles. For examples of the default TG profiles, see
the z/OS Communications Server: SNA Resource Definition
Reference.
- Characteristics specified by default
These characteristics
are required for ATM native connections and are automatically defined
for you when you do not code the ADAPNO and CUADDR operands on the
PORT definition statement in the XCA major node, which is the equivalent
of coding MEDIUM=ATM. The only possible values for ATM native connections
are those shown in parentheses in the following list of characteristics.
- PU type of the remote node (PUTYPE=2)
- Type of connection (CONNTYPE=APPN)
- High-performance routing (HPR) enablement (HPR=YES)
- Channel contact procedure (XID=YES)
Figure 7 shows the definition
of a TG over a PVC. Following Figure 7 are
descriptions of the major nodes and the definition statements and
operands used in Figure 7 to define a TG
over a PVC. Figure 7. Definition of
a TG over a PVC OSAXCA1 VBUILD TYPE=XCA
PORT PORTNAME=PORTA,
MEDIUM=ATM
GROUP DIAL=NO
PVCLN1 LINE PVCNAME=PVC1,
.
.
.
PVCPU1 PU CPNAME=HOST2,
TGP=ATMPVCCB,
CONNTYPE=APPN,
HPR=YES,
PUTYTPE=2,
XID=YES
.
.
.
Name of the PVC: The PVCNAME
operand on the LINE definition statement specifies that the name of
the PVC is PVC1. The name specified here is the name of the PVC associated
with the ATM OSA-2 physical port. 2 The ATM network provider must configure the ATM network
to provide the PVC connection.
Name of the remote node with which VTAM can communicate over the TG: The CPNAME operand on the PU definition statement specifies
that the name of the remote node with which VTAM can communicate over this TG is HOST2.
Route calculation characteristics: You can specify route calculation characteristics on the PU definition
statement on the following operands: - COSTTYPE
- COSTBYTE
- SECURITY
- PDELAY
- CAPACITY
- UPARM1
- UPARM2
- UPARM3
Or, they can be determined by the TGP operand on the PU
definition statement, which specifies the name of an IBM-supplied
APPN TG profile definition. In Figure 7, they are determined by the TGP operand, which specifies the name
of the IBM-supplied profile definition for ATM TGs over PVCs, campus
best effort.
Defining transmission groups over switched
virtual channels:
Figure 8 illustrates how TGs are defined over switched virtual channels.
Switched virtual channels represent temporary connections.
They are established through a dial operation and are available for
as long as the connection is required. SVCs appear to VTAM as switched lines. As such, the TGs that
are assigned to them are defined in groups headed by a GROUP definition
statement that specifies DIAL=YES.
Because SVCs are associated
with a port on the IBM Open
Systems Adapter, the TGs that are assigned to them are defined in
the XCA major node that defines the port with which the SVCs are associated.
Define the following key characteristics of a TG over an SVC
in the XCA major node: - Characteristic you must specify is the maximum number of simultaneous
connections using the port
- Characteristics you should specify
- Whether the line used for the TG can be used for calls initiated
by a remote node, VTAM or both
- Whether PUs are to be dynamically created during call-in operations
or explicitly defined in the switched major node
If a line used for a TG over an SVC is used for calls
initiated by VTAM (CALL=OUT
or CALL=INOUT), define the following key characteristics of the TG
in the switched major node: - Characteristics you must specify
- The type of APPN routes that can use the SVC
- The name of the group that contains the dial-out line definitions
for the TG
- Name of the remote node with which VTAM can communicate over the TG
- Address through which the remote node can be reached
- ATM channel characteristics
- Best effort indicator
- Cell rates
- Traffic management options
- Characteristics you should specify
- Route calculation characteristics
- Cost per connect time
- Cost per byte
- Security
- Propagation delay
- Effective capacity
- User-defined values
Note: IBM supplies default
TG profiles that define these characteristics for best effort and
reserved bandwidth connections across public and private ATM networks.
It is recommended that you use these default TG profiles. For examples
of the default TG profiles, see the z/OS Communications Server: SNA Resource Definition
Reference.
- ATM channel characteristics including the Quality of Service (QoS)
class
In addition to required characteristics, optional characteristics
can be defined. See the z/OS Communications Server: SNA Resource Definition
Reference for information
about how to code the definition statements and operands used to define
both the key and optional characteristics.
Figure 9 is based on the configuration in Figure 8 and represents definitions in the VTAMLST
data set for the VTAM in HOST1.
Following Figure 9 are descriptions of
the major nodes and the definition statements and operands used in Figure 9 to define a TG over an SVC. Figure 9. Definition of a TG over an SVC OSAXCA1 VBUILD TYPE=XCA
PORT PORTNAME=PORTA,
MEDIUM=ATM
SVCGRP1 GROUP DIAL=YES,
CALL=INOUT,
DYNPU=YES,
.
.
.
SVCLN1 LINE .
. .
SVCPU1 PU .
.
.
SVCLN2 LINE .
.
.
SVCPU2 PU .
.
.
OSASWT1 VBUILD TYPE=SWNET
SWTPU1 PU CPNAME=HOST2,
TGP=ATMSVCCR,
.
.
.
PATH GRPNM=SVCGRP1,
DLCADDR=(1,C,ATMSVC,EXCLUSIVE),
DLCADDR=(7,BCD,03,00,
00006000,00004000,
00000191,00,
00006000,00004000,
00000191,00),
DLCADDR=(8,X,03,03,03),
DLCADDR=(21,X,0002,
399999999999999999),
9998010131504553543460),
.
.
.
Maximum number of simultaneous connections: The number of sets of LINE and PU definition statements
in the XCA major node represents the maximum number of simultaneous
connections that can be established using the port. In Figure 9, the maximum number of simultaneous
connections is 2. The LINE definition statements serve as placeholders
for lines used to connect to remote nodes that are defined either
dynamically or in a switched major node, and are used when those nodes
are activated.
Who can initiate calls: The CALL operand on the GROUP definition statement in the XCA
major node specifies that the lines in this group can be used for
calls initiated by both the VTAM in HOST1 and remote nodes.
Dynamic creation of PUs: The DYNPU operand
on the GROUP definition statement in the XCA major node specifies
that PUs are to be dynamically created when remote nodes call in to VTAM. By enabling PUs to be dynamically
created, you eliminate the need to code PU and PATH definition statements
in the switched major node.
The type of APPN routes that can use the SVC: In Figure 9, EXCLUSIVE on the DLCADDR
operand with a subfield of 1 on the PATH definition statement in the
switched major node indicates that the TG can be assigned to an SVC
that is used only for this TG, and it cannot be assigned to an SVC
that is used for connection network TGs.
Meanings of the values
coded on the DLCADDR operand are directly related to ATM channel characteristics.
For additional information about what the values indicate, see the z/OS Communications Server: SNA Resource Definition
Reference.
Name of the group that contains the dial-out line definitions for the TG: The GRPNM operand on the PATH definition statement
in the switched major node specifies that the line to be used for
the TG is defined in the group named SVCGRP1 in the XCA major node.
This group follows a PORT definition statement, and identifies the
lines to be used for the TG as those associated with the port defined
on that PORT statement (PORTA in Figure 9).
Name of the remote node with which VTAM can communicate over the TG: The CPNAME operand on the PU definition statement
specifies that the name of the remote node with which VTAM can communicate over this TG is HOST2.
Address through which the remote node can be reached: The DLCADDR operand with subfield 21 on the PATH definition
statement in the switched major node specifies that the 20-byte address
through which HOST2 can be reached is identified as 3999999999999999999998010131504553543460
and that this is an International Organization for Standardization
(ISO) network service access point (NSAP) address, indicated by the
0002 preceding the address. The address through which HOST2 can be
reached was obtained through configuration of OSAY in Figure 9. OSAY is the IBM Open Systems Adapter through which HOST2
is connected to the ATM network. When the remote node is a VTAM node, configuration of the IBM Open Systems Adapter through
which the remote node is connected should be completed before definition
of the calling VTAM node is
attempted. See zEnterprise System and System z10 OSA-Express
Customer's Guide and Reference for information about how to determine the
ATM address through which the remote VTAM node can be reached.
Note: You can also determine
the ATM address through which the remote VTAM node can be reached by starting the remote VTAM, then activating the following
resources in the remote VTAM: - The TRL major node
- The XCA major node that defines the port on the IBM Open Systems Adapter through which the remote VTAM can be reached
- Any line defined in the XCA major node
After activating the remote VTAM resources, issue a DISPLAY ID command for
the XCA major node. The resulting display shows the ATM address for
the remote VTAM node.
You can follow this same procedure to obtain the ATM address for
the local VTAM as well.
Route calculation characteristics: You can specify route calculation characteristics on the PU definition
statement on the following operands: - CAPACITY
- COSTBYTE
- COSTTYPE
- PDELAY
- SECURITY
- UPARM1
- UPARM2
- UPARM3
Or, they can be determined by the TGP operand on the
PU definition statement, which specifies the name of an IBM-supplied
APPN TG profile definition. In Figure 9, they are determined by the TGP operand, which specifies the name
of the IBM-supplied profile definition for ATM TGs over SVCs (campus
reserved bandwidth).
Best effort indicator, cell rates, and traffic management options: The DLCADDR operand with a subfield of 7 specifies
the following values: - 03
- The format of the best effort indicator, cell rates, and traffic
management options is defined by the ATM network.
- 00
- Guaranteed bandwidth is required.
- 00006000
- The forward peak cell rate (cells per second), in binary coded
decimal, for cell loss priority 0+1 (CLP=0+1) is 6000.
- 00004000
- The forward sustainable cell rate (cells per second), in binary
coded decimal, for (CLP=0) is 4000.
- 00000191
- The forward maximum burst size (cells), in binary coded decimal,
for (CLP=0) is 191.
- 00
- Tagging is not requested in the forward direction.
- 00006000
- The backward peak cell rate (cells per second), in binary coded
decimal, for cell loss priority 0+1 (CLP=0+1) is 6000.
- 00004000
- The backward sustainable cell rate (cells per second), in binary
coded decimal, for (CLP=0) is 4000.
- 00000191
- The backward maximum burst size (cells), in binary coded decimal,
for (CLP=0) is 191.
- 00
- Tagging is not requested in the backward direction.
Quality of Service (QoS) class: The DLCADDR
operand with a subfield of 8 specifies the following values: - Value
- Meaning
- 03
- The format of the QoS class is defined by the ATM network.
- 03
- The QoS class is connection-oriented for outbound (forward) data
traffic.
- 03
- The QoS class is connection-oriented for inbound (backward) data
traffic.
- Defining transmission groups to connection networks
-
Figure 10 shows an ATM configuration
in which multiple nodes can communicate with one another across an
ATM network. HOST2 and HOST3 are end nodes that dial in to the network
node server, HOST1. All nodes can establish switched connections with
one another.
To enable optimal route selection among these
nodes, an extensive number of TGs needs to be defined. Specifically,
each node needs to define TGs to every other node. So, in Figure 10, HOST1 needs to define TGs to HOST2 and
HOST3, HOST2 needs to define TGs to HOST1 and HOST3, and HOST3 needs
to define TGs to HOST1 and HOST2. In a large configuration with many
nodes connected by many SVCs, the definition of TGs can become overwhelming.
Figure 10. Multiple nodes communicating across an ATM
network
APPN's connection network function reduces this extensive
TG definition for connections among multiple nodes across an ATM network.
A connection network is a representation of a shared access transport
facility, such as an ATM network, that handles the routing of data
among the nodes communicating across the shared access transport facility.
It does this by enabling the shared access transport facility to be
defined as a virtual node. As a result, end nodes need to define TGs
only to the virtual node and to the network node server. The network
node server, though it does not always need to, should also define
a TG to the virtual node.
Figure 11 shows the ATM configuration in Figure 10 with a virtual node. The virtual node represents the ATM network
to the nodes that can communicate with one another across the ATM
network.
Figure 11. ATM configuration with a connection
network
Now, HOST1 needs to define a TG only to VNODE1, as does
HOST2 and HOST3. HOST2 and HOST3 must also each define a TG to HOST1
because HOST1 is their network node server. The same routing capability
achieved by six TG definitions for the configuration in Figure 10 is now achieved by five TG definitions
using the virtual node in Figure 11. In large
networks with many nodes connected by many SVCs, the reduction in
TG definitions is much more significant. For example, without the
use of a connection network, a configuration with five end nodes that
dial into one network node server requires 30 TG definitions to enable
optimal route selection. With the use of a connection network, that
same configuration requires only 11 TG definitions to enable the same
optimal route selection.
If another network node server and
its associated end nodes wanted to communicate with HOST1, HOST2,
and HOST3 through the same connection network, each new end node would
need to define a TG to the virtual node and to the new network node
server. The new network node server would also need to define a TG
to the virtual node and to HOST1.
Multiple TGs through one
port can be to the same virtual node. In addition, TGs to multiple
virtual nodes can be through the same port.
Connections through
connection networks occur over SVCs, which appear to VTAM as switched lines. Thus, TGs to connection
networks are defined in groups headed by a GROUP definition statement
that specifies DIAL=YES.
Because SVCs are associated with a
port on the IBM Open Systems
Adapter, TGs to connection networks are defined in the XCA major node
that defines the port with which the SVCs are associated.
To
define the following key characteristics of a TG to a connection network
in the XCA major node: - Characteristics you must specify
- The type of APPN routes that can use the SVC
- Name of the virtual node that represents the ATM network
- The maximum number of simultaneous connections using the port
- ATM channel characteristics
- Best effort indicator
- Cell rates
- Traffic management options
- Characteristics you should specify
- Whether the line used for the TG can be used for calls initiated
by a remote node, VTAM, or
both
- Whether PUs are to be dynamically created during call-in operations
or explicitly defined in the switched major node
- Route calculation characteristics
- Cost per connect time
- Cost per byte
- Security
- Propagation delay
- Effective capacity
- User-defined values
Note: IBM supplies default
TG profiles that define these characteristics for best effort and
reserved connections across public and private ATM networks and recommends
use of these default TG profiles. For examples of the default TG profiles,
see the z/OS Communications Server: SNA Resource Definition
Reference.
- ATM channel characteristics
- Quality of Service (QoS) class
- Characteristics specified by default
- High-performance routing (HPR) enablement (HPR=YES)
HPR=YES
is required for ATM native connections and is automatically defined
for you when you do not code the ADAPNO and CUADDR operands on the
PORT definition statement in the XCA major node, which is the equivalent
of coding MEDIUM=ATM. The only possible value for ATM native connections
is HPR=YES.
In addition to the required characteristics, other optional
characteristics can be defined. See the z/OS Communications Server: SNA Resource Definition
Reference for information about how to code the definition statements and
operands used to define both the key and optional characteristics.
Figure 12, Figure 13, and Figure 14 are based on the
configuration in Figure 11 and represent definitions
in the VTAMLST data sets for the VTAMs in HOST1, HOST2, and HOST3.
Following Figure 14 are descriptions of
the major nodes, definition statements, and operands used in Figure 12, Figure 13, and Figure 14 to define TGs to a connection
network. Figure 12. Definitions in
VTAMLST for the VTAM in HOST1HOST1
OSAXCA1 VBUILD TYPE=XCA
PORT PORTNAME=PORTA,
MEDIUM=ATM
CNGRP1 GROUP DIAL=YES,
CALL=INOUT,
DLCADDR=(1,C,ATMSVC, &cont
VNODE1,EXCLUSIVE),
DLCADDR=(7,BCD,03,00, &cont
00006000,
00004000,00000191, &cont
00),
DLCADDR=(8,X,03,03),
DYNPU=YES,
TGP=ATMSVCCR,
HPR=YES,
.
.
.
CNLN1 LINE
CNPU1 PU
CNLN2 LINE
CNPU2 PU
CNLN3 LINE
CNPU3 PU
Figure 13. Definitions in VTAMLST
for the VTAM in HOST2HOST2
OSAXCA1 VBUILD TYPE=XCA
PORT PORTNAME=PORTA,
MEDIUM=ATM
CNGRP1 GROUP DIAL=YES,
CALL=INOUT,
DLCADDR=(1,C,ATMSVC,
VNODE1,EXCLUSIVE),
DLCADDR=(7,BCD,03,00,
00006000,
00004000,00000191,
00),
DLCADDR=(8,X,03,03),
DYNPU=YES,
TGP=ATMSVCCR,
HPR=YES,
.
.
.
CNLN1 LINE
CNPU1 PU
CNLN2 LINE
CNPU2 PU
CNLN3 LINE
CNPU3 PU
OSASWT1 VBUILD TYPE=SWNET
SWTPU1 PU CPNAME=HOST1,
TGP=ATMSVCCR,
.
.
.
PATH GRPNM=CNGRP1,
DLCADDR=(1,C,ATMSVC,EXCLUSIVE),
DLCADDR=(7,BCD,03,00,
00006000,00004000,
00000191,00,
00006000,00004000,
00000191,00),
DLCADDR=(8,X,03,03,03),
DLCADDR=(21,X,0002,
399999999999999999
9998010131504553543460),
.
.
.
Figure 14. Definitions in VTAMLST
for the VTAM in HOST3HOST3
OSAXCA1 VBUILD TYPE=XCA
PORT PORTNAME=PORTA,
MEDIUM=ATM
CNGRP1 GROUP DIAL=YES,
CALL=INOUT,
DLCADDR=(1,C,ATMSVC,
VNODE1,EXCLUSIVE),
DLCADDR=(7,BCD,03,00,
00006000,
00004000,00000191,
00),
DLCADDR=(8,X,03,03),
DYNPU=YES,
TGP=ATMSVCCR,
HPR=YES,
.
.
.
CNLN1 LINE
CNPU1 PU
CNLN2 LINE
CNPU2 PU
CNLN3 LINE
CNPU3 PU
OSASWT1 VBUILD TYPE=SWNET
SWTPU1 PU CPNAME=HOST1,
TGP=ATMSVCCR,
.
.
.
PATH GRPNM=CNGRP1,
DLCADDR=(1,C,ATMSVC,EXCLUSIVE),
DLCADDR=(7,BCD,03,00,
00006000,00004000,
00000191,00,
00006000,00004000,
00000191,00),
DLCADDR=(8,X,03,03,03),
DLCADDR=(21,X,0002,
399999999999999999
9998010131504553543460),
.
.
.
The type of APPN routes that can use the SVC: In Figure 12 through Figure 14, EXCLUSIVE on the DLCADDR operand with
a subfield of 1 on the PATH definition statement in the XCA major
node indicates that separate TGs and SVCs can be established. These
handle sessions over connection-network connections only. Sessions
through connection networks cannot be routed over an SVC already established
to the same remote node if that SVC was not established through a
connection network.
Meanings of the values coded on the DLCADDR
operand are directly related to ATM channel characteristics. For information
about what the values indicate, see the z/OS Communications Server: SNA Resource Definition
Reference.
Name of the virtual node that represents the ATM network: The DLCADDR operand, with subfield 1 on the GROUP
definition statement in the XCA major node, specifies the name of
the virtual node representing the ATM network to VTAM is VNODE1.
Maximum number of simultaneous connections: The number of sets of LINE and PU definition statements in the
XCA major node represents the maximum number of simultaneous connections
that can be established using the port. In Figure 9, the maximum number of simultaneous connections is two. The
LINE definition statements serve as placeholders for lines used to
connect to remote nodes that are defined either dynamically, or in
a switched major node, and are used when those nodes are activated.
Who can initiate calls: The CALL operand on the GROUP definition statement in the XCA
major node specifies that the lines in this group can be used for
calls initiated by both the VTAM in HOST1 and remote nodes.
Dynamic creation of PUs: The DYNPU operand
on the GROUP definition statement in the XCA major node specifies
that PUs are to be dynamically created when remote nodes call in to VTAM. By enabling PUs to be dynamically
created, you eliminate the need to code PU and PATH definition statements
in the switched major node. If you explicitly define PUs in the switched
major node, you lose the major benefit of the connection network:
reduction of resource definition.
Route calculation characteristics: Route
calculation characteristics can be specified on the GROUP definition
statement in the XCA major node on the following operands: - CAPACITY
- COSTBYTE
- COSTTYPE
- PDELAY
- SECURITY
- UPARM1
- UPARM2
- UPARM3
They can also be determined by the TGP operand on the
GROUP definition statement, which specifies the name of an IBM-supplied
APPN TG profile definition. In Figure 12 through Figure 14, the route calculation
characteristics are determined by the TGP operand, which specifies
the name of the IBM-supplied profile definition for ATM TGs over SVCs
(campus reserved bandwidth).
Best effort indicator, cell rates, and traffic management options: The DLCADDR operand with a subfield of 7 specifies
the following values: - Value
- Meaning
- 03
- The format of the best effort indicator, cell rates, and traffic
management options is defined by the ATM network.
- 00
- Guaranteed bandwidth is required.
- 00006000
- The forward peak cell rate (cells per second) for cell loss priority
0+1 (CLP=0+1) is 6000.
- 00004000
- The forward sustainable cell rate (cells per second) for (CLP=0)
is 4000.
- 00000191
- The forward maximum burst size (cells) for (CLP=0) is 191.
- 00
- Tagging is not requested in the forward direction.
Quality of Service (QoS): The DLCADDR operand with a subfield of 8 specifies
the following values: - Value
- Meaning
- 03
- The format of the QoS class is defined by the ATM network.
- 03
- The format of the QoS class is defined by the ATM network.
- 03
- The QoS class is connection-oriented for outbound (forward) data
traffic.
- Establishing a TG over a permanent virtual channel (PVC)
-
For a PVC connection to be established, both nodes must activate
the PVC. To activate the PVC from VTAM, follow these steps:
- Accept the default value or specify YES on the DYNADJCP start
option in the VTAM start list.
Or, activate the adjacent control point (ADJCP) major node that defines
the remote node with which VTAM can communicate over the TG assigned to this PVC.
ATCSTR01 DYNADJCP=YES
- Activate the transport resource list (TRL) major node that defines VTAM connection to the IBM Open Systems Adapter.
VARY ACT ID=TRL1
- Activate the external communication adapter (XCA) major node that
defines the port on the IBM Open
Systems Adapter used to access the ATM network.
VARY ACT ID=OSAXCA1
- Activate the LINE and PU definition statements in the XCA major
node that define the line to which the PVC connection can be assigned
and the remote node with which VTAM can communicate over the PVC connection.
VARY ACT ID=PVCLN1
VARY ACT ID=PVCPU1
- Establishing a TG over a switched virtual channel (SVC)
- For an SVC connection to be established, both nodes must be prepared
to call or receive calls.
To prepare VTAM to call or receive calls, follow these steps:
- Accept the default value or specify YES on the DYNADJCP start
option in the VTAM start list.
Or, activate the ADJCP major node that defines the remote node with
which VTAM can communicate
over the TG assigned to this SVC.
ATCSTR01 DYNADJCP=YES
- Activate the TRL major node that defines VTAM connection to the IBM Open Systems Adapter.
VARY ACT ID=TRL1
- Activate the XCA major node that defines the port on the IBM Open Systems Adapter used to
access the ATM network.
VARY ACT ID=OSAXCA1
- Activate the LINE definition statements in the XCA major node
that serve as placeholders for the lines used to connect to the remote
nodes with which VTAM can communicate
over the SVC connection.
VARY ACT ID=SVCLN1
VARY ACT ID=SVCLN2
The LINE definition statements in the
XCA major node serve as placeholders for lines used to connect to
remote nodes that are defined either dynamically, or in a switched
major node, and are used when those nodes are activated.
To call a remote node from VTAM, follow these steps:
- Activate the switched major node that defines the remote node
with which VTAM can communicate
over the TG assigned to the SVC.
VARY ACT ID=OSASWT1
- Activate the physical units defined in the switched major node.
VARY ACT ID=SWTPU1
- Dial the physical units defined in the switched major node.
VARY DIAL ID=SWTPU1
- Establishing a TG to a connection network
-
To establish a connection-network connection, follow these
steps:
- Accept the default value or specify YES on the DYNADJCP start
option in the VTAM start list.
Or, activate the ADJCP major node that defines the remote nodes with
which VTAM can communicate
through the connection network.
ATCSTR01 DYNADJCP=YES
- Activate the TRL major node that defines VTAM connection to the IBM Open Systems Adapter.
VARY ACT ID=TRL1
- Activate the XCA major node that defines the port on the IBM Open Systems Adapter used to
access the ATM network.
VARY ACT ID=OSAXCA1
- Activate the LINE definition statements in the XCA major node
that serve as placeholders for the SVCs to the remote nodes with which VTAM can communicate over the connection-network
connection.
VARY ACT ID=CNLN1
VARY ACT ID=CNLN2
VARY ACT ID=CNLN3
The LINE definition statements in the
XCA major node serve as placeholders for SVCs to remote nodes that
are defined either dynamically, or in a switched major node, and are
used when sessions to those nodes are established.
1 The name of the ATM
OSA-2 physical port is defined during IBM Open Systems Adapter configuration on the ATM Native Settings
panel, which is part of the OSA Configuration pull-down option accessed
through the OSA/SF OS/2 interface. 2 The name of the PVC is defined
during IBM Open Systems Adapter
configuration on the ATM Native Settings panel, which is part of the
OSA Configuration pull-down option accessed through the OSA/SF OS/2
interface.
|
z/OS Communications Server: SNA Network Implementation Guide
Copyright IBM Corporation 1990, 2014
