DLCADDR

Read syntax diagramSkip visual syntax diagram
>>-+---------------------------------------------------+-------><
   '-DLCADDR--=--(--subfield_id--,--type--,--string--)-'   

Specifies the signaling information used to establish a switched connection with a remote node through an ATM native connection network.

Multiple DLCADDR operands can be coded on a single GROUP definition statement. For example, the following information can be coded on a single GROUP statement.
    GROUP  DLCADDR=(1,TYPE1,STRING1),
           DLCADDR=(2,TYPE2,STRING2)
subfield_id
Indicates the subfield. A value between 1–96 can be specified.
The first DLCADDR operand must have a subfield_id of 1. Also, each operand must have a unique subfield_id. If two DLCADDR operands—after a DLCADDR operand with a subfield of 1—have the same subfield_id, VTAM® treats the two operands as duplicates. VTAM ignores the second operand and issues an error message.
Note: If you receive an error message referring to the first DLCADDR operand coded on a GROUP statement, limited syntax checking is done on the subsequent DLCADDR operands coded.
type
Indicates the data format of the signaling information and is one of the following formats:
Type
Data Format
A
Compressed alphanumeric
BCD
Binary coded decimal
C
EBCDIC
D
Decimal
X
Hexadecimal
Type C (EBCDIC) is the default.
string
Defines the signaling information in the data format defined by type. Multiple string values can be coded for a subfield_id type pair. For example:
DLCADDR=(1,TYPE1,STRING1,STRING2,STRING3)

You can specify up to 250 bytes of signaling information on a single DLCADDR operand. If coding multiple strings on a single operand, the total number of bytes available for signaling information is reduced by 2 for each additional DLCADDR string.

The first DLCADDR operand defined for each GROUP definition statement identifies the DLC type, which for ATM native connection-network connections is ATMSVC. The remaining DLCADDR operands define the DLC signaling information for the ATM native connection-network connection. You can code only one set of DLCADDR operands on the GROUP definition statement for an ATM native connection-network connection.

Code the following DLCADDR operands for an ATM native connection-network connection. Fields in italics are user-defined fields.
DLCADDR=(1,C,ATMSVC,vnname,tg_use)
DLCADDR=(7,BCD,format,best_effort_indicator,a,b,c,
        forward_traffic_management_options)
DLCADDR=(8,X,format,outbound_QOS_class)
DLCADDR=(9,BCD,tns_identifier)
DLCADDR=(21,BCD,type,ATM_address)
DLCADDR=(51,X,format,a,b,c,d,e)
DLCADDR=(61,BCD,format,05,a,b)
The following list explains the information provided by each subfield:
Subfield
Contents
1
C indicates EBCDIC format. ATMSVC indicates that the connection provides native access to an ATM network.

Code vnname to specify a 1–17 character network-qualified CP name for the connection network. vnname is reported to the network topology as a virtual node and is treated as an adjacent CP to this node. If the name is not network-qualified, the network ID of the SSCP that owns the connection network (network ID of the host) is used. For sessions that are routed through the connection network, a dynamic PU is created to represent the destination node. In effect, DYNPU=YES is enforced automatically when a session is established through the connection network.

Code tg_use to specify one of the following items:
EXCLUSIVE
Indicates that SVCs and TGs can be established that will handle sessions only over connection network connections. Sessions through a connection network cannot be routed over an SVC already established to the same remote node if that SVC was not established through a connection network. Shared sessions can be shared between connection network connections and non-connection networks over an SVC.
SHARE
Indicates that HPR sessions routed through connection networks can use an SVC that is already established to the same remote node, even if that SVC was not established through a connection network.
7
BCD indicates binary coded decimal format.
Code format to specify one of the following items:
00
Indicates ITU-T defined
03
Indicates ATM network defined
Code best_effort_indicator to specify one of the following items:
00
Indicates that guaranteed bandwidth is wantd
01
Indicates that best effort is acceptable
Code a, b, and c as 4-byte decimal values to specify the following items:
a
Forward peak cell rate (cells per second) for cell loss priority=0+1 (CLP=0+1)
b
Forward sustainable cell rate (cells per second) for (CLP=0)
c
Forward maximum burst size (cells) for (CLP=0)
Code forward_traffic_management_options to specify one of the following items:
00
Indicates that tagging is not requested in the forward direction
01
Indicates that tagging is requested in the forward direction
Note: If best_effort_indicator is 00, code format, a, b, c, and forward_traffic_management_options.

If best_effort_indicator is 01, code format and a.

8
X indicates hexadecimal format.
Code format to specify one of the following items:
00
Indicates ITU-T defined
03
Indicates ATM network defined

Code outbound_QOS_class to specify the QOS class for outbound (forward) data traffic.

9
BCD indicates binary coded decimal format.

Code tns_identifier to specify the carrier identification code for the carrier that will be used for this connection.

21
BCD indicates binary coded decimal format.
Code type to specify the following items:
0101
Indicates public E164 address, which means the address is in a public ATM network. The address is variable in length.

Code ATM_address only if remote nodes that use the same connection network are attached directly to public networks. Code ATM_address to specify the public gateway E164 address through which this port can be reached.

51
X indicates hexadecimal format.
Code format to specify the following items:
00
Indicates ITU-T defined
Code a, b, c, d, and e to specify the following bearer capabilities:
a
Bearer class.
a can be one of the following items:
01
Indicates class A
03
Indicates class C
10
Indicates class X
b
Susceptibility to clipping.
b can be one of the following items:
00
Not susceptible
01
Susceptible
c
User plane connection configuration.
c must be:
00
Point-to-point
d
If bearer class is 10, indicates the traffic type.
d can be one of the following items:
00
No indication
02
Variable bit rate
e
If bearer class is 10, indicates timing requirements.
e can be one of the following items:
00
No indication
01
End-to-end timing required
61
BCD indicates binary coded decimal format.
Code format to specify the following:
00
Indicates ITU-T defined

Code 05 to indicate ATM adaptation layer (AAL) type 5.

Code a and b as 4-byte decimal values to specify the following AAL parameters:
a
Forward CPCS-SDU maximum size
b
Backward CPCS-SDU maximum size
Note: If an application using an ATM reserved bandwidth SVC connection sends RUs smaller than the forward CPCS-SDU size, the throughput for the session may be reduced. For example, if the forward CPCS-SDU size was defined or allowed to default to 8448 (Maximum RU size 8K + 256), and the data being transmitted over this ATM connection is in 1K RUs, the throughput (as defined by the connection's forward cell rate) is greatly reduced. If this ATM SVC connection is used for 1K RU data transmission, the forward CPCS-SDU size should be set to 1280 bytes (Maximum RU size of 1K + 256).