Reference for Enterprise OS Software

AdjLinkSta

Syntax

: ADD !<port> -APPN AdjLinkSta <type>(NN|EN|Learn) <max_btu_size>(99-8912) [[Cmac|Ncmac] dest media addr] [Sap=<num>] [CPName=[netid.]cpname] [Nodeid=<ID>] [LinkName=<name>] [TGprof=<name>] [AutoStart=(Yes|No)] [CPSess=(Yes|No)] [HPR=(Yes|No)] [ErrorRecovery=(Yes|No)]
: DELete !<port> -APPN AdjLinkSta <LinkName>
: SHow [!<port>] -APPN AdjLinkSta [LinkName]

Default

No default

Description

The AdjLinkSta parameter defines an adjacent link station as a destination and defines the type of node being linked to, the destination address, and the node name associated with the link station. To send and receive traffic from all adjacent nodes (both network nodes and end nodes), you must configure the other nodes as adjacent link stations.

Once the adjacent link station is activated, if the APPN node is active and you want to make any configuration changes using this parameter or the LinkStaCHar parameter, you must first deactivate the link using the LinkStaCONTrol parameter. If the APPN node is not active, you do not need to deactivate the link.

You can set this parameter for virtual ports. To use virtual ports, the physical port that the virtual port is on must be configured for Frame Relay by entering the SETDefault !<port> -PORT OWNer = FrameRelay command. The DLC type configured using the SETDefault !<port> -APPN PortDef command must also be set to Frame Relay.

Values

NN|EN|Learn

Specifies whether the destination is a network node (NN) or an end node (EN). Specify Learn if you do not know the node type and you only know the node media address. If you specify Learn, do not specify a CP name.

<max_btu_size>

Enters the maximum number of bytes in a basic transmission unit (BTU) that can be sent to this destination. The acceptable range for network nodes is 99 to 8,912, while the acceptable range for end nodes is 256 to 8,912.

If you set the type to Learn, do not set the value to less than 256, because you do not know if the node is a network node or an end node. If the learned node is an end node and you set the value to less than 256, the link may not come up. If the link can support HPR (HPR=Yes), the maximum BTU size must be at least 768.

For optimal buffer utilization, the recommended maximum BTU size is 1,500 for Ethernet and for bridging LLC2 over serial lines using Source Route Transparent bridging. For token ring and all other media, including bridging over serial lines using Source Route bridging, the recommended maximum is 5,005.

<dest media addr>

Enters the destination media address. The destination media address is required if the port data link control (DLC) type is LLC2, Frame Relay, Data Link Switching (DLSw), or Synchronous Data Link Control (SDLC). The media address is not required if the port DLC type is Point-to-Point Protocol (PPP).
If the port DLC type is Frame Relay, the media address is the DLCI (data link connection identifier). When you enter the DLCI number, precede it with the word DLCI or by the at sign (@), for example:
ADD !1 -APPN AdjLinkSta NN 1033 DLCI 128
or
ADD !1 -APPN AdjLinkSta NN 1033 @ 128
You can use the DLCI to establish a permanent virtual circuit (PVC) connection or to identify a switched virtual circuit (SVC).
Your Frame Relay service provider assigns the DLCI numbers for PVCs from a range of 16 to 991. The DLCI for SVCs is actually a virtual circuit identifier (vcid) number that is mapped to a number from the range of DLCI numbers available that have not been already assigned for PVCs or SVCs. To establish SVC connections, you need to configure local and remote site addresses (telephone numbers). An SVC connection can be used as a dynamic connection or configured as a static connection, such as a PVC.

If you have specified the -SYS MacAddrFormat parameter as noncanonical, enter the address in noncanonical format. If you have not changed the -SYS MacAddrFormat, enter the address in noncanonical format but add the prefix "Ncmac." Although you can enter the address in canonical format, SNA environments normally use noncanonical format. If Ncmac or Cmac is not specified, the format specified with the -SYS MacAddrFormat parameter is used.

Sap

Enters the service access point (SAP) of the remote node in the destination host. The valid range in hexadecimal of SAP values for this parameter is from 0x4 to 0xEC in multiples of 4. The default SAP value is 4. The SAP is always displayed using the hexadecimal value, but is not shown with the 0x prefix.

CPName

Enters the control point name of the adjacent link station. If the net ID is different than the net ID of the local node specified using the LocalNodeName parameter, you can specify the net ID. If you enter the net ID, you must type a period immediately following it, then type the CP name immediately following the period to create the fully qualified CP name. The CP name can be up to eight characters in length, and valid characters are A-Z, 0-9, $, @, #. The name cannot start with a number, a space or a period. This value is optional.

Nodeid

Enters the eight-digit hex identification that is used to identify the node. This value is optional. The node ID corresponds to the IDNUM of the IBM node ID format IDBLK/IDNUM.

<LinkName>

Specifies the name assigned to the link. All link names must be unique on the local network node. For example, you cannot use the same link name on more than one port, and you cannot use the same link name for two types of links (such as for adjacent link stations or DLUr link stations) at the same time. The link name is limited to eight characters, and cannot start with special characters. If no link name is specified, the system assigns a link name LINKXXXX where XXXX is a number between 0001 and 9999.

TGprof

Specifies the transmission group profile assigned to the link station. The TG profile is a set of default values that apply to the link if chosen. When a TG profile is chosen, the proper capacity and propagation delay values will be assigned to the link station based on the link speed of the media. If no profile for the link station is specified, then the profile specified for the port using the PortDef parameter is used; if no TG profile for the port is specified the system automatically picks a profile corresponding to the port's baud rate.

If the port is not active and the baud rate is unknown, then the system defaults to the Ser64 profile. Table 15 lists the TG profiles you can specify, and the corresponding link values. Once you specify a TG profile, if you then specify a different value for capacity or propagation delay using the LinkStaCHar parameter, then the TG profile value is overridden and the value assigned by the LinkStaCHar parameter is used.

NN\|EN\|Learn	Specifies whether the destination is a network node (NN) or an end node (EN). Specify Learn if you do not know the node type and you only know the node media address. If you specify Learn, do not specify a CP name.
<max_btu_size>	Enters the maximum number of bytes in a basic transmission unit (BTU) that can be sent to this destination. The acceptable range for network nodes is 99 to 8,912, while the acceptable range for end nodes is 256 to 8,912.
	If you set the type to Learn, do not set the value to less than 256, because you do not know if the node is a network node or an end node. If the learned node is an end node and you set the value to less than 256, the link may not come up. If the link can support HPR (HPR=Yes), the maximum BTU size must be at least 768.
	For optimal buffer utilization, the recommended maximum BTU size is 1,500 for Ethernet and for bridging LLC2 over serial lines using Source Route Transparent bridging. For token ring and all other media, including bridging over serial lines using Source Route bridging, the recommended maximum is 5,005.
<dest media addr>	Enters the destination media address. The destination media address is required if the port data link control (DLC) type is LLC2, Frame Relay, Data Link Switching (DLSw), or Synchronous Data Link Control (SDLC). The media address is not required if the port DLC type is Point-to-Point Protocol (PPP). If the port DLC type is Frame Relay, the media address is the DLCI (data link connection identifier). When you enter the DLCI number, precede it with the word DLCI or by the at sign (@), for example: ADD !1 -APPN AdjLinkSta NN 1033 DLCI 128 or ADD !1 -APPN AdjLinkSta NN 1033 @ 128 You can use the DLCI to establish a permanent virtual circuit (PVC) connection or to identify a switched virtual circuit (SVC). Your Frame Relay service provider assigns the DLCI numbers for PVCs from a range of 16 to 991. The DLCI for SVCs is actually a virtual circuit identifier (vcid) number that is mapped to a number from the range of DLCI numbers available that have not been already assigned for PVCs or SVCs. To establish SVC connections, you need to configure local and remote site addresses (telephone numbers). An SVC connection can be used as a dynamic connection or configured as a static connection, such as a PVC.
	If you have specified the -SYS MacAddrFormat parameter as noncanonical, enter the address in noncanonical format. If you have not changed the -SYS MacAddrFormat, enter the address in noncanonical format but add the prefix "Ncmac." Although you can enter the address in canonical format, SNA environments normally use noncanonical format. If Ncmac or Cmac is not specified, the format specified with the -SYS MacAddrFormat parameter is used.
Sap	Enters the service access point (SAP) of the remote node in the destination host. The valid range in hexadecimal of SAP values for this parameter is from 0x4 to 0xEC in multiples of 4. The default SAP value is 4. The SAP is always displayed using the hexadecimal value, but is not shown with the 0x prefix.
CPName	Enters the control point name of the adjacent link station. If the net ID is different than the net ID of the local node specified using the LocalNodeName parameter, you can specify the net ID. If you enter the net ID, you must type a period immediately following it, then type the CP name immediately following the period to create the fully qualified CP name. The CP name can be up to eight characters in length, and valid characters are A-Z, 0-9, $, @, #. The name cannot start with a number, a space or a period. This value is optional.
Nodeid	Enters the eight-digit hex identification that is used to identify the node. This value is optional. The node ID corresponds to the IDNUM of the IBM node ID format IDBLK/IDNUM.
<LinkName>	Specifies the name assigned to the link. All link names must be unique on the local network node. For example, you cannot use the same link name on more than one port, and you cannot use the same link name for two types of links (such as for adjacent link stations or DLUr link stations) at the same time. The link name is limited to eight characters, and cannot start with special characters. If no link name is specified, the system assigns a link name LINKXXXX where XXXX is a number between 0001 and 9999.
TGprof	Specifies the transmission group profile assigned to the link station. The TG profile is a set of default values that apply to the link if chosen. When a TG profile is chosen, the proper capacity and propagation delay values will be assigned to the link station based on the link speed of the media. If no profile for the link station is specified, then the profile specified for the port using the PortDef parameter is used; if no TG profile for the port is specified the system automatically picks a profile corresponding to the port's baud rate.
	If the port is not active and the baud rate is unknown, then the system defaults to the Ser64 profile. Table 15 lists the TG profiles you can specify, and the corresponding link values. Once you specify a TG profile, if you then specify a different value for capacity or propagation delay using the LinkStaCHar parameter, then the TG profile value is overridden and the value assigned by the LinkStaCHar parameter is used.

Table 15 TG Profile Values

TG Profile

Link Type

Effective Capacity

Propagation Delay

TR4

LAN

4M (0x76)

LAN (0x4C)

TR16

LAN

16M (0x85)

LAN

Eth10

LAN

10M (0x80)

LAN

Eth100

LAN

100M (0x9A)

LAN

FDDI

LAN

100M (0x9A)

LAN

Ser9.6

WAN

9600 (0x30)

Telephone (0x71)

Ser19.2

WAN

19200 (0x38)

Telephone

Ser56

WAN

56000 (0x44)

Telephone

Ser64

WAN

64000 (0x45)

Telephone

Ser256

WAN

256000 (0x55)

Telephone

SerT1

WAN

T1 (0x69)

Telephone

**Table 15** TG Profile Values
TG Profile	Link Type	Effective Capacity	Propagation Delay
TR4	LAN	4M (0x76)	LAN (0x4C)
TR16	LAN	16M (0x85)	LAN
Eth10	LAN	10M (0x80)	LAN
Eth100	LAN	100M (0x9A)	LAN
FDDI	LAN	100M (0x9A)	LAN
Ser9.6	WAN	9600 (0x30)	Telephone (0x71)
Ser19.2	WAN	19200 (0x38)	Telephone
Ser56	WAN	56000 (0x44)	Telephone
Ser64	WAN	64000 (0x45)	Telephone
Ser256	WAN	256000 (0x55)	Telephone
SerT1	WAN	T1 (0x69)	Telephone

AutoStart

Specifies whether AutoStart will be supported. If you specify yes, the link is automatically activated when the local network node is enabled and is restarted automatically if the link stops. If you specify no, the link is not automatically started and you must activate the link by entering the SET -APPN LinkStaCONTrol command. The default value is yes. In the SHow -APPN AdjLinkSta display, AutoStart support is shown in the "AS" column.

CPSess

Specifies whether CP-CP sessions are activated with the adjacent node. If you specify yes, CP-CP sessions will be activated with the node, and if you specify no, they will not. The default value is no if the adjacent node type is a network node, and yes if the adjacent node type is an end node or the node type is set to LEARN. In the SHow -APPN AdjLinkSta display, CP-CP session support is shown in the "CP" column.

HPR

Specifies if the link station supports High Performance Routing (HPR) on this link. If you specify "Yes," then HPR will be supported on the link between the local node and the adjacent link station. If you specify "No," HPR is not supported and the link uses Intermediate Session Routing (ISR). The default is Yes, meaning HPR is supported by default. If you want the adjacent link station to support only ISR, you must specify No.

ErrorRecovery

For HPR links only, specifies if link level error recovery is used for an outgoing connection on the link. If you specify "Yes," error recovery is preferred, but can be negotiated down. If you specify "No," error recovery for HPR does not take place. If you want link level error recovery for the incoming connection, then you must set the ErrorRecovery value for the PortDef parameter (see "PortDef" later in this chapter). The default is the ErrorRecovery value defined using the PortDef parameter (the port that the adjacent link station belongs to). If you use link level error recovery, additional overhead is created on your links. This value is only valid if the HPR value is set to "Yes."

AutoStart	Specifies whether AutoStart will be supported. If you specify yes, the link is automatically activated when the local network node is enabled and is restarted automatically if the link stops. If you specify no, the link is not automatically started and you must activate the link by entering the SET -APPN LinkStaCONTrol command. The default value is yes. In the SHow -APPN AdjLinkSta display, AutoStart support is shown in the "AS" column.
CPSess	Specifies whether CP-CP sessions are activated with the adjacent node. If you specify yes, CP-CP sessions will be activated with the node, and if you specify no, they will not. The default value is no if the adjacent node type is a network node, and yes if the adjacent node type is an end node or the node type is set to LEARN. In the SHow -APPN AdjLinkSta display, CP-CP session support is shown in the "CP" column.
HPR	Specifies if the link station supports High Performance Routing (HPR) on this link. If you specify "Yes," then HPR will be supported on the link between the local node and the adjacent link station. If you specify "No," HPR is not supported and the link uses Intermediate Session Routing (ISR). The default is Yes, meaning HPR is supported by default. If you want the adjacent link station to support only ISR, you must specify No.
ErrorRecovery	For HPR links only, specifies if link level error recovery is used for an outgoing connection on the link. If you specify "Yes," error recovery is preferred, but can be negotiated down. If you specify "No," error recovery for HPR does not take place. If you want link level error recovery for the incoming connection, then you must set the ErrorRecovery value for the PortDef parameter (see "PortDef" later in this chapter). The default is the ErrorRecovery value defined using the PortDef parameter (the port that the adjacent link station belongs to). If you use link level error recovery, additional overhead is created on your links. This value is only valid if the HPR value is set to "Yes."

Example

To add an adjacent link station on port 1 that is a network node using a maximum BTU size of 1033, with a noncanonical MAC address of 100040C08ACE, a fully qualified control point name of "HQ.SnJose," enter:

: ADD !1 -APPN AdjLinkSta NN 1033 N100040C08ACE CPName=HQSnJose