 |
» |
|
|
|
Once you have opened the configuration file, you are placed at the NMMGR "Main" screen.
Main Screen |
|
From this screen you can select the category of network subsystems you want to configure.
Figure 2-1 Main Screen
![[Main Screen]](img/lnkxmain.gif)
To access the NMMGR branch for configuring an SNA node and link, press [f4] (IBM).
This places you at the "HP-IBM Configuration" screen.
HP-IBM Configuration Screen |
|
From this screen you can select the item you want to configure.
Figure 2-2 HP-IBM Configuration Screen
![[HP-IBM Configuration Screen]](img/lnkxhpib.gif)
To select SNA node and link configuration, press [f2] (Go
To SNANODE).
SNA Node Configuration Screen |
|
After you have selected SNA node and link configuration, NMMGR displays the "SNA Node Configuration" screen.
(You can go directly to this screen from any screen by typing @SNANODE in
the command window and pressing [ENTER].) Here you specify information about the new SNA node you are
configuring or the existing node you are modifying.
Figure 2-3 SNA Node Configuration Screen Example
![[SNA Node Configuration Screen Example]](img/lnkxnode.gif)
- Path
For display only. The NMMGR branch you are in. - SNA Node Name
-
The name of the new SNA node you are configuring or the existing node whose configuration
you are modifying. The name can be up to eight alphanumeric characters long; the first character must
be alphabetic. Host Configuration: - New Name
The new name of an existing SNA node. The name can be up to eight
alphanumeric characters long; the first character must be alphabetic.
Host Configuration:
Once you have entered the new name, press [f4] (Rename); the node is then renamed. - Configured SNA Nodes
-
For display only. The names of the SNA nodes that have been configured. You can configure a maximum 36
nodes in a configuration file. Note that a maximum eight nodes can be active at a time; however, to
make this possible, a multi-drop line must be used.
- File
For display only. The name of the configuration file.
Once you have entered the name of the node, press [f5] (Add) if this is a new node,
or press [f6] (Modify) if you are modifying an existing node. This places you at the
"SNA Node Configuration: PU Data" screen.
PU Data Screen |
|
After you have selected a node, NMMGR displays the "SNA Node Configuration: PU Data" screen.
(You can go directly to this screen from any screen by typing @SNANODE.nodename
in the command window and pressing [ENTER].) Here you enter information that identifies
the PU to the host. If you are configuring a new node, you must enter all of the information.
Figure 2-4 PU Data Screen Example
![[PU Data Screen Example]](img/lnkxpu.gif)
- Path
For display only. The NMMGR path to this screen. It includes the name of
the SNA node you are configuring. - Link Type
Required. The type of communications link the node is being configured for.
Values: SDLC, X.25, or TOKEN.
Default: SDLC - Node Type
Required. The type of node being configured. If
you are configuring a T2.0 node, enter 2.0. If you are
configuring a T2.1 node, enter 2.1. If you are configuring a node for SNA/X.25 Link, you
must enter 2.0 in this field.
If you are configuring a node for SNA/Token Ring Link,
enter 2.1 in this field.
Values: 2.0 and 2.1 Default: 2.0
Host Configuration:
SNA/SDLC (dependent LU): The PUTYPE operand of the PU macro must be
set to 2, and the XID operand of the same PU macro must be set to
NO or not specified at all.
SNA/SDLC (independent LU): The PUTYPE operand of the PU macro
must be set to 2, and the XID operand of the same PU macro
must be set to YES. SNA/Token Ring (dependent and independent LUs): The PUTYPE
operand of the PU macro must be set to 2, and the XID operand of the same
PU macro must be set to YES. - Node 2.1 Dependent LU Support
-
If you entered 2.0 in the Node Type field, this field must be blank.
If you entered 2.1 in the Node Type field and one or more dependent LUs are configured,
enter Y. If you entered 2.1 in the Node Type field and no dependent LUs are
configured, enter N. Default: Blank (the node is T2.0)
- Physical Unit Data
Information about the Physical Unit (PU).
- MAX DATA
-
Required. The maximum size, in bytes, of the transmission buffers (frames) used to hold data for
the SDLC connection, the X.25 QLLC connection, or token ring connection.
Range: 137-2057 (integer) Default: 265
Host Configuration:
AS/400 Configuration: The MAXFRAME parameter in the line description must match this field;
see Table
2-8 “AS/400 Parameter Values for SDLC Link” and 2-10.
- ID BLK
Required. Three hexadecimal digits which, together with ID NUM (see below),
form the exchange identifier used with exchange identification (XID) requests. This composite
identifier must be unique within the SNA network.
|
|
|
|
 |
NOTE: For communication with an IBM host, this parameter (ID BLK) is ignored
for nonswitched lines. For communication with an IBM AS/400, this parameter is required for both
switched and nonswitched lines. |
|
|
|
|
Range: 001-FFE (hexadecimal) Default: 023 (ID BLK sent by the IBM 8100)
Host Configuration:
AS/400 Configuration: The EXCHID parameter in the controller description is required,
and must match the entire exchange identifier (this field combined with ID NUM);
see Table 2-8 “AS/400
Parameter Values for SDLC Link” and
Table 2-10 “AS/400
Parameter Values for Token Ring Link”. - ID NUM
Five hexadecimal digits that are appended to ID BLK (see above) to form the exchange
identifier used with exchange identification (XID) requests. This composite identifier must be unique
within the SNA network.
|
|
|
|
|
NOTE: For communication with an IBM host, this parameter (ID
NUM) is ignored for nonswitched lines. For communication with
an IBM AS/400, this parameter is required for both switched
and nonswitched lines. |
|
|
|
| Range: 00001-FFFFF (hexadecimal) Default: FFFFF Host Configuration:
AS/400 Configuration: The EXCHID parameter
in the controller description is required, and must match the
entire exchange identifier (this field combined with ID BLK);
see Table 2-8 “AS/400
Parameter Values for SDLC Link” and
Table 2-10 “AS/400
Parameter Values for Token Ring Link”. - Local Control Point Name
(Token ring only) Required for APPC over token ring link. The name by which the HP 3000
node is known to the remote system.
Host Configuration: HP recommends that you use the PU name (the SNA Node Name field
in the SNA Node Configuration screen) in this field.
AS/400 Configuration: For APPN, the RMTCPNAME in the APPC display controller
description must match this field; see
Table 2-10 “AS/400
Parameter Values for Token Ring Link”. Otherwise, HP recommends that you use
the PU name (the SNA Node Name field in the SNA Node Configuration screen) in this field. - File
For display only. The name of the configuration file.
Once you have entered all of the PU information, press [f6] (Save Data).
After the information is saved, if you need to configure LU information, press
[f2] (Go To LUDATA); this places you at the "SNA Node Configuration: LU Data" screen
(described next in this chapter).
If you need to configure link information, press [f1] (Go To LINKDATA).
If you specified SDLC for the Link Type field on the "SNA Node Configuration:
PU Data" screen, you are placed at the "SNA Node Configuration: SDLC Link Data" screen.
If you specified X.25 for the Link Type field, you are placed at the
"SNA Node Configuration: X.25 Link Data" screen. If you specified TOKEN for the
Link Type field, you are placed at the "SNA Node Configuration: Token Ring Link Data" screen.
Each of the screens is described later in this chapter.
If you do not need to configure LU information or link information, press [f8] (Prior Screen)
until you get to the screen you need next.
LU Data Screen |
|
Once you have specified the PU information, you are ready to specify LU information. You do this
on the "SNA Node Configuration: LU Data" screen. Select this screen by pressing [f2] (Go To LUDATA)
on the "SNA Node Configuration: PU Data" screen. (You can go directly to this screen from any screen by typing
@SNANODE.nodename.LUDATA in the command window and pressing [ENTER].)
Figure 2-5 LU Data Screen Example
![[LU Data Screen Example]](img/lnkxlu.gif)
- Path
For display only. The NMMGR path to this screen. It includes the name
of the SNA node you are configuring.
- Logical Unit Data
Information about the LUs to be configured
for this node. You can configure a maximum 256 LUs for each node.
- LU Name
The remote system name (not the Network Addressable
Unit [NAU] number) of the LU. The name can be up to eight alphanumeric
characters long; the first character must be alphabetic. Note that
at least one LU Name must be specified. Host Configuration:
-
-
SNA/Token Ring: For troubleshooting purposes, we recommend that the luname operand
of the LU macro in the VTAM switched major node match this field; see table 2-7.
- LU#
The LU (NAU) number. Note that for an independent LU this field must be blank.
Range: 1-255 (integer) Default: Blank Host Configuration:
SNA/SDLC: The LOCADDR operand of the LU macro must match this field; see table 2-1. Note that for
an independent LU the LOCADDR operand must be set to 0.
SNA/X.25 (PVC): The LOCADDR operand of the X25.LU macro must match this field; see table
2-2.
SNA/X.25 (SVC): The LOCADDR operand of the LU macro in the VTAM switched major
node must match this field; see table 2-3. -
SNA/Token Ring: The LOCADDR operand of the LU macro
in the VTAM switched major node must match this field; see table 2-7.
- File
-
For display only. The name of the configuration file.
Note that you can enter LU information on up to eight pages of this
screen. Each page contains 32 LU Name and LU #
fields You do not have to fill all of the fields on a page before
pressing [f1] (Next Page), [f2] (Prev
Page), [f3] (First Page), or [f4] (Last Page) to display another page of the screen
for entering information. That is, partially filled pages are allowed.
Once you have entered information for all of the LUs, do one of these two things:
Press [f5] (Sort & Condense) to sort
the information from all pages of this screen by LU Name. The sorted information
is condensed into full pages. Note that this
takes approximately as much time as validation of the configuration file. After the information is processed,
press [f6] (Save Data). -
Press [f6] (Save Data). The information remains in the order it was entered on the pages of the screen,
and any partially filled pages remain partially filled.
After the information is saved, if you need to configure link information, press [f8]
(Prior Screen) until you get to the "SNA Node Configuration: PU Data" screen.
Then, press [f1] (Go To LINKDATA). If you specified SDLC for the Link Type field
on the "SNA Node Configuration: PU Data" screen, you are placed at the "SNA Node Configuration: SDLC Link Data"
screen (described next in this chapter). If you specified X.25 for the Link Type field,
you are placed at the "SNA Node Configuration: X.25 Link Data" screen (described later in this chapter).
If you specified TOKEN for the Link Type field, you are placed at the "SNA Node Configuration:
Token Ring Link Data" screen (described later in this chapter).
If you do not need to configure link information, press [f8] (Prior Screen) until
you get to the screen you need next.
SDLC Link Data Screen |
|
Once you have specified the PU and LU information, you are ready to configure the communications link
parameters and the phone data for the SDLC link. You do this on the "SNA Node Configuration: SDLC Link Data" screen.
Select this screen by pressing [f1] (Go To LINKDATA) on the "SNA Node Configuration: PU Data" screen.
(You can go directly to this screen from any screen by typing @SNANODE.nodename.LINKDATA
in the command window and pressing [ENTER]).
Figure 2-6 SDLC Link Data Screen Example
![[SDLC Link Data Screen Example]](img/lnkxsdlc.gif)
- Path
For display only. The NMMGR path to this screen. It includes the name of the SNA node you are configuring.
- Physical Path
-
Required. The address of the PSI. At system start-up time, this address is assigned according to
the slot the PSI is in. The value you enter here is determined by one of these
formulas:
If only one card cage is present: 4 X SlotNumber
where (a) X is the multiplication sign (not the character "X"), and (b) SlotNumber is the number of the slot the PSI is in. Example: If the PSI is in slot 6, the Physical Path
is 24 (4 multiplied by 6). If two card cages are present: PathNumber/(4 X SlotNumber) where (a) PathNumber is a number corresponding
to the card cage the PSI is in: Card cage 0: PathNumber = 2 Card cage 1: PathNumber = 6 (b) / is the slash character (not the division sign), (c) the parentheses are used to set off the arithmetic formula (they are not entered as part of the Physical Path value), (d) X is the multiplication sign (not
the character "X"), and (e) SlotNumber is the number of the slot, within the card cage, the PSI is in. Examples: If the PSI is in card cage 0, slot number 4, the Physical
Path is 2/16 (PathNumber, slash character, 4 multiplied
by 4). If the PSI is in card cage 1, slot number 3, the Physical
Path is 6/12 (PathNumber, slash character, 4 multiplied
by 3).
- Receive Timeout
Required. The number of seconds the SDLC link driver will wait for the remote system poll before closing the line. If 0 is specified, no timeout occurs. Range: 0, 30-1800 (integer) Recommended value: 180 (30 in Europe) Default: 180 - Local Timeout
Required. The number of seconds the SDLC link driver waits for PSI card activity, before informing SNA Transport that the PSI is down and the link driver is going down. Note that the PSI card waits 20 seconds longer (than the value specified here) for SDLC link driver activity before bringing down the link and reporting a failure. This avoids unnecessary use of dial-up lines, which avoids excessive phone charges. (Note that since no driver activity is taking place, the driver probably will not receive the failure notice.) If 0 is specified, no timeout occurs. Range: 0, 30-900 (integer) Recommended value: 30 Default: 30 - Connect Timeout
Required. The number of seconds the SDLC link driver will wait for a link Set Normal Response Mode (SNRM) command after telling the PSI to enable the Data Terminal Ready (DTR) signal, before closing the line. This includes time waiting for either the autodialer or the operator to dial the remote phone number. If 0 is specified, no timeout occurs. If you are using a manual-dial modem, we recommend that you specify either 0
(no timeout) or 900 (the maximum wait). You can begin
to dial after this logging message is displayed on the console after
issuing SNACONTROL START:
Node NodeName ready for activation by host Note that if you are using a manual-dial modem, console
logging must be enabled for SNA Transport logging class CLAS0013,
so that the above message can be displayed (see chapter 3). Range: 0, 30-900 (integer) Default: 900 - Number of Error Retries
Required. The maximum number of times the SDLC link
manager will retry after errors or timeouts before setting the line
to idle. Range: 1-999 (integer) Default: 7 - Transmission Speed
Required. The line transmission speed (bits per second). This value is overridden by the modem, if one is used. For direct-connect, the speed must be supported by the cable. Values: 1200 2400 4800 9600 19200 38400 56000 64000 (integer) Default: 9600 Host Configuration: The SPEED operand of the LINE
macro must match this field; see table 2-1. AS/400 Configuration: The LINESPEED parameter
in the line description must match this field; see table 2-7. - NRZI
Required. Enter Y to enable the Non-Return to Zero Inverted
(NRZI) feature; N to disable it (and enable Non-Return
to Zero [NRZ]). Default: N Host Configuration: The NRZI operand of the LINE macro must match this field; see table
2-1. - Station ID
Required. This defines the HP 3000's link station identifier to the remote system's
communications controller. Range: 01-FE (hexadecimal) Host Configuration: The ADDR operand of the PU macro must match this field; see table
2-1. AS/400 Configuration: The STNADR parameter
in the controller description must match this field; see table 2-7. - Auto Dial
Required. Enter Y only if you are using an auto-dial modem and you want the modem to dial at link startup time; N if a leased line, a manual-dial modem, or no modem is used, or if you are using an auto-dial modem but you want to defer dialing until the SNACONTROL AUTODIAL command is issued (see chapter 6). Default: N - Phone Number
The number you want the link to dial into. Note that you specify this field only if you are using an auto-dial modem. Allowable Characters:
Any of the 12 phone characters: 0 1 2 3 4 5 6 7
8 9 * # - = A spacing character, used for readability
purposes.
D = Pause for three seconds.
E = The end of the phone number. This character
might be required by the modem; check your modem manual for details. Do
not use this unless you know the modem/auto-call unit (ACU) requires
it. / = Wait for a second dial tone. When the
modem encounters this character, it waits for another dial tone. This
can be used when an outside line must be accessed before the actual
phone number is dialed.
| | | | | NOTE: Only 34 characters can be entered. So, if you have more than one access number to dial, you might not be able to use the dash (-) spacing character.
| | | | |
Example: Suppose this is typed in the Phone Number field: 9-DD-415-555-3216
9 is an access number to an outside line.
DD means to pause six seconds before dialing
the next set of numbers.
4155553216 is the number you want to dial,
where 415 is the area code 5553216 is the specific number The dashes are used for readability.
- File
For display only. The name of the configuration file. Once you have entered the SDLC link information, press [f6]
(Save Data). After the information is saved, press [f8] (Prior Screen) until you get to the screen you need next. X.25 Link Data Screen | |
Once you have specified the PU and LU information, you are ready to configure the communications link parameters and virtual circuit data for the X.25 link. You do this on the "SNA Node Configuration: X.25 Link Data" screen. Select this screen by pressing [f1] (Go To LINKDATA) on the "SNA Node Configuration: PU Data" screen. (You can go directly to this screen from any screen by typing @SNANODE.nodename.X25LINK in the command window and pressing [ENTER].) Before You Use This ScreenThe PVC or SVC that SNA/X.25 Link is going to use must have already been defined in the X.25 System Access configuration and the DTC Manager configuration or the DTS configuration. So, before you configure the X.25 link parameters and virtual circuit data on the "SNA Node Configuration: X.25 Link Data" screen, you must have done the tasks described below. For an SNA/X.25 PVC: Configured a logical channel identifier (LCI) range in the DTC Manager configuration or the DTS configuration. The PVC Number you specify on the "SNA Node Configuration: X.25 Link Data" screen must be within the LCI range you configured. Configured a network interface (NI) for the SNA/X.25 PVC in the X.25 System Access configuration. The value you specify for NS Network Interface Name on the "SNA Node Configuration: X.25 Link Data" screen must match the NI name you configured. Configured an address key for the SNA/X.25 PVC in the X.25 System Access network interface configuration, if you want to reserve the PVC for only SNA/X.25's use.
For an SNA/X.25 SVC: Configured a network interface (NI) for the SNA/X.25 SVC in the X.25 System Access configuration. The value you specify for NS Network Interface Name on the "SNA Node Configuration: X.25 Link Data" screen matches the NI name you configured. Configured a facility set in the network interface with the same parameters as the facility set on the host. The HP 3000 facility set can be configured for the SNA/X.25's SVC use only, or for use by any SVC. We recommend that you configure the facility for only SNA/X.25's use, because that ensures that SNA/X.25 receives only incoming calls intended for it.
Data Required from the NS ConfigurationsCertain items from the X.25 System Access configuration and the DTC Manager configuration or the DTS configuration must match or be compatible with items in the SNA/X.25 configuration. Listed below are the X.25 System Access configuration screens and DTC Manager configuration or DTS configuration screens that contain those items. For an SNA/X.25 PVC: "DTC Manager DTCX25 Board # Level 3" screen or "DTS DTC X.25 Card Config - Level 3 & Miscellaneous" screen: The PVC LCI Range must include the PVC number specified for PVC Number on the "SNA Node Configuration: X.25 Link Data" screen. "Network Interface Configuration" screen: The Configured Network Interfaces list must include the NI name specified for NS Network Interface Name on the "SNA Node Configuration: X.25 Link Data" screen. "X.25 PVC Address Key Paths" screen: If you want to reserve an X.25 address key for the SNA/X.25 PVC's use only, the PVC Number must match the PVC Number specified on the "SNA Node Configuration: X.25 Link Data" screen.
Figure 2-7 shows the configuration dependencies for an SNA/X.25 PVC. Figure 2-7 PVC Configuration Dependencies
![[PVC Configuration Dependencies]](img/lnkxpvc.gif)
For an SNA/X.25 SVC: "Network Interface Configuration" screen: The Configured Network Interfaces list must include the NI name specified for NS Network Interface Name on the "SNA Node Configuration: X.25 Link Data" screen. "X.25 SVC Address Key Paths" screen: The name of the facility set configured for the SVC must be found on this screen, even though it is not actually used in the SNA/X.25 configuration. If you follow our recommendation and reserve the facility set for the SNA/X.25 SVC's use only, the X.25 Address you specify for the facility set on this screen must match the address you specify for Remote's X.25 Network Address on the "SNA Node Configuration: X.25 Link Data" screen. Note that this address is the remote system's address. Also, the security specification in the "X.25 SVC Address Key Paths" screen must be compatible with the Call Direction specified on the "SNA Node Configuration: X.25 Link Data" screen. If you do not reserve the facility set for SNA/X.25's use, by associating it with the remote system's address, you must configure it as the POOL facility set. You do this by specifying the facility set as the default facility set for the POOL X.25 address key. Also, the security specification in the "X.25 SVC Address Key Paths" screen must be compatible with the Call Direction specified on the "SNA Node Configuration: X.25 Link Data" screen.
Figure 2-8 shows the configuration dependencies for an SNA/X.25 SVC. Figure 2-8 SVC Configuration Dependencies
![[SVC Configuration Dependencies]](img/lnkxsvc.gif)
Figure 2-9 X.25 Link Data Screen Example
![[X.25 Link Data Screen Example]](img/lnkxx25.gif)
- Path
For display only. The NMMGR pat to this screen. It includes the name of the SNA node you are configuring.
- NS Network Interface Name
Required. The NS network interface that the X.25 link will use. The name can be up to eight alphanumeric characters long; the first character must be alphabetic. See the appropriate NS documentation for more information. X.25 System Access Configuration: An NI name in the Configured Network Interfaces field of the "Network Interface Configuration" screen must match this field.
- Inactivity Timeout
Required. The number of minutes that the QLLC module will wait between incoming packets. The timer is reset each time a packet is received. If the specified number of minutes elapses before the next packet arrives, the virtual circuit is cleared and then released. For an incoming SVC, this results in a recoverable link failure. If 0 is specified, the timer is disabled. This can result in an indefinite period of inactivity; however, note that it might be desirable to disable the timer for permanent virtual circuits (PVCs). Range: 0-32767 (integer) Default: 0
- Virtual Circuit Type
Required. The type of virtual circuit to be used to connect to the
host: permanent virtual circuit (PVC) or switched
virtual circuit (SVC). The X.25 network subscription
information and the host NPSI configuration should be used to determine
the type of virtual circuits that are available for this connection. If you specify PVC, you must also specify
the PVC Number
field (see below). If you specify SVC, you must also specify
the Remote's X.25 Network Address and Call
Direction fields (both fields are described later in this chapter). Values: PVC and SVC Host Configuration: PVC: The TYPE operand of the X25.LINE macro for the PVC must
be set to PERMANENT; see table 2-2.
SVC: The TYPE operand of at least one X25.LINE macro must be set to
SWITCHED; see table 2-3.
- PVC DATA
Information about the permanent virtual circuit (PVC).
- PVC Number
Conditionally required. The number identifying the permanent
virtual circuit that will connect the HP 3000 node to the remote
system. This is found in the X.25 network subscription information,
and is equivalent to the Logical Channel Number (LCN). This field is required only if PVC is entered for the Virtual Circuit Type field. Range: 0-4095 (integer) X.25 System Access Configuration: If you followed
our recommendation and configured a specific address key for the SNA/X.25
PVC (in the PVC Number field of the "X.25 PVC Address Key Paths" screen), that address key must match the value specified in this field. See figure
2-7 for an example. DTC Manager Configuration: The range specified for the LCI Range field (for PVCs) of the "DTC Manager DTCX25 Board # Level 3" screen must contain the value specified in this field. DTS Configuration: The range specified for the LCI Range field (for PVCs) of the "DTS X.25 Card Config - Level 3 & Miscellaneous"
screen must contain the value specified in this field.
- SVC DATA
Information about the switched virtual circuit (SVC).
- Remote's X.25 Network Address
Conditionally required. The X.25 network address of the remote system. This is found in the X.25 network subscription information. This field is required only if SVC is entered for the Virtual Circuit Type field. Host Configuration: If the host is configured to make outgoing calls, the DIALNO operand value of the PATH macro that defines the dial-out path to the HP 3000 node must contain the value specified in this field; see table 2-3. For security purposes, SNA/X.25 Link compares the remote X.25 address contained in incoming calls with the value specified in this field. See the HP SNA Products Remote System Configuration Guide [J2220-61025] for more information about host configuration. Also, the features and names of the facility sets are found in the X.25 network subscription information. Note that the facility set (the set of virtual circuit features and security attributes associated with the SVC) configured on the remote system must also be configured for the NS X.25 system link (see below). AS/400 Configuration: The NETADDR parameter in the line description must match this field; see table 2-8. X.25 System Access Configuration: The facility set that the SNA/X.25 SVC will use must be configured for the NS X.25 system link. If you followed our recommendation and reserved the facility set for the SNA/X.25 SVC, the X.25 Address you specified in the "X.25 SVC Address Key Paths" screen must be the same as the address you specify in this field. See figure 2-8 for an example.
- Call Direction
Conditionally required. Enter IN if the HP 3000 will wait for the remote system to request a connection (incoming direction); OUT if the HP 3000 will initiate the connection (outgoing
direction). If you specify OUT, you might need to specify the Maximum Call Retries and Call Retry Delay fields. These fields are described below. This field is required only if SVC is entered for the Virtual Circuit Type field. | | | | | NOTE: Only one incoming SVC is supported per system.
| | | | |
Values: IN and OUT Recommended value: OUT Default: OUT Host Configuration:
If you are configuring an outgoing SVC, at least one X25.LINE host macro must
specify CALL=IN and you must enter OUT in this field.
If you are configuring an incoming SVC, at least one X25.LINE host macro must
specify CALL=OUT and you must enter IN in this field.
If CALL=INOUT is specified in at least one X25.LINE host macro, either
IN or OUT can be specified in this field.
- Maximum Call Retries
Conditionally required. The maximum number of times the QLLC module will try to connect to the remote system without success. If 0 is specified, the QLLC module will not retry if the first attempt to connect fails. This field is required only if SVC is entered for the Virtual Circuit Type field. If you specify a value greater than 0, you must also specify the Call Retry Delay field (see below). Note that this field is valid only when OUT is specified for the Call Direction field (described below). Range: 0-999 (integer) Default: 3
- Call Retry Delay
Conditionally required. The number of seconds the QLLC module waits between attempts to connect to the remote system. This field is required only if a value greater
than 0 is specified for the Maximum Call Retries
field (see above). Note that this field is valid only when OUT
is specified for the Call Direction field (described earlier in this chapter). Range: 60-999 (integer) Default: 60
- File
For display only. The name of the configuration file. Once you have entered the X.25 link information, press [f6] (Save Data). After the information is saved, press [f8] (Prior Screen) until you get to the screen you need next.
Token Ring Link Data Screen | |
Once you have specified the PU and LU information, you are ready to configure the communications link parameters for the token ring link. You do this on the "SNA Node Configuration: Token Ring Link Data" screen. Select this screen by pressing [f1] (Go To LINKDATA) on the "SNA Node Configuration: PU Data" screen. (You can go directly to this screen from any screen by typing @SNANODE.nodename.LINKDATA in the command window and pressing [ENTER]). | | | |  | CAUTION: If the Token Ring 3000/iX Network Link product is already configured for the Network Services (NS) subsystem, the values that initially appear in the Token Ring Link Data screen fields reflect the NS configuration. If the same token ring card is being used for both NS and SNA communications, certain fields in the Token Ring Link Data screen must match the values of the NS token ring link configuration. (See the following field descriptions.)
If the Link Name configured for an SNA token ring link is the same as the name of an NS token ring link, make sure that the values of these fields in the SNA token ring link configuration match the NS token ring link configuration; otherwise, the SNA token ring link configuration will change the NS token ring link configuration. If more than one token ring link is configured for NS, the values of the first configured token ring link appear. | | | | |
Figure 2-10 Token Ring Link Data Screen Example
![[Token Ring Link Data Screen Example]](img/lnkxtokn.gif)
- Path
For display only. The NMMGR path to this screen. It includes the name
of the SNA node you are configuring.
- Link Name
Required. The symbolic name of the token ring card. The name must start with an alphabetical character. | | | | | NOTE: If the same token ring card is being used for both NS
and SNA communications, you must use the same name in this field as
is configured for the NS link.
| | | | |
- Physical Path of Device Adapter
Required. The address of the Token Ring Card. At system start-up time, this address is assigned according to the slot in which the Token Ring Card resides. | | | | | NOTE: If the same token ring card is being used for both NS and SNA communications, you must use the same value for this field as is configured for the NS link.
| | | | |
- Remote DSAP
Required. The service access point (SAP) for the remote system. This is a two-digit
hexadecimal number that is a multiple of 4. Host Configuration: For a 3745 remote system,
the IDNUM and IDBLK values in the PU
macro must also match the ID NUM and ID BLK fields in the SNA Node Configuration: PU data screen on the HP 3000. For
a 3174 or 3745 remote system, HP recommends that the value of this
field be 04. While other values may work, a value of 04
has been verified to work. AS/400 Configuration: The SSAP in the controller description for the AS/400 must match this field; see table 2-10. - Local SSAP
Required. The SAP for the HP 3000 node. This is a two-digit hexadecimal number that is a multiple of 4. Each active node on an HP 3000 system must have a unique SAP. AS/400 Configuration: The DSAP in the controller description for the HP 3000 must match this field; see table 2-10. | | | | | NOTE: A service access point (SAP) pair identifies a MAC type 2 connection. This pair consists of two SAPs: the destination SAP (DSAP) and the local SAP (LSAP). DSAP is the SAP of the remote computer and LSAP is the SAP of the local computer. The SAP pair, along with the remote and local station address, uniquely identifies a logical connection in the token ring network.
| | | | |
- Unacknowledged Send Limit
Required. The maximum number of frames that a MAC type 2 connection expects to receive
before sending an acknowledgement. Range: 1-127 (integer) Default: 2
- Retry Limit
Required. The maximum number of times a MAC type 2 connection retransmits a frame before dropping the connection. Range: 1-254 (integer) Default: 10
- Acknowledgement Timer
Required. The maximum time, in tenths of a second, that the MAC type 2 connection waits before determining that a frame has been dropped and retransmitting. Range: 1-254 (integer) Default: 10 (1 second)
- Error Timer
Required. The amount of time, in tenths of a second, that the MAC type 2 connection waits before initiating a Poll/Find (P/F) cycle. Range: 1-600 (integer) Default: 100 (10 seconds)
- Remote Station Address
Required. Host Configuration: The LOCADD parameter
in the LINE macro must match this field; see table 2-7. AS/400 Configuration: The ADPTADR in
the line description for the AS/400 must match this field; see table
2-10.
- Use Factory-Configured Local Station Address
Enter Y to use the factory-configured local
station address. Enter N to use the address to be entered
in the Local Station Address field. In most IBM environments,
the local station address is assigned by the IBM system manager. This
is necessary since connection establishment requires knowledge of
remote addresses. | | | | | NOTE: If the same token ring card is being used for both NS and SNA communications, you must specify the local station address that is configured for the NS token ring link.
| | | | |
- Local Station Address
Required (if N is specified in the Use Factory-Configured Local Station Address field.) For non-AS/400 communications, HP recommends that you use either the factory-configured address (enter Y in the Use Factory-Configured Local Station Address field) or use local station address for the NS token ring link, if it is configured. AS/400 Configuration: The ADPTADR in the controller description for the HP 3000 must match this field; see table 2-10. | | | | | NOTE: If the same token ring card is being used for both NS and SNA communications, you must use the local station address that is configured for the NS token ring link.
| | | | |
- File
For display only. The name of the configuration file.
|
