NetView for z/OS, Version 5.3
The topology server can communicate with the NetView environment through an LU 6.2 conversation. To communicate with the NetView environment through an LU 6.2 conversation, define the LU name for the topology server that will be used.
To define the LU name of the topology server on the topology server workstation, use the sample ts.acg configuration file in one of the following directories:
This file is shipped with the NetView management console and represents a sample communications server configuration file for the topology server LU 6.2 communications. Use the configuration file as a guide to tailor the configuration to fit your environment. See the appropriate communications server documentation for more information about LU 6.2 connections.
Before using the NetView management console to monitor your network, define your workstation network configuration. This section outlines how to configure SNA on your topology server workstation.
To configure SNA LU 6.2 support for your workstation network, use the information in this section.
NCP can be channel-attached to the host, with token-ring connections between the NCP and server.
The topology communications server provides communications between the server workstation and the host. In a multi-workstation configuration, the topology server also handles communications between the server workstation and the client workstations.
The topology server uses a topology communications server to establish and communicate through LU 6.2 sessions. The topology communication server supports LU 6.2 sessions through any medium that supports LU 6.2 communication. The server workstation is directly connected to a status focal point host through an LU 6.2 session.
This type of workstation serves the client workstation by storing views and status and by distributing this data to the client workstations. The client workstation acts as a graphic operator console that retrieves data from the server workstation. An example of this is a topology server workstation communicating with topology console workstations over a LAN.
SNA requires an IBM® SNA communications product to be properly configured. Although there are numerous products that support the NetView management console requirements for communications over SNA, they share certain parameters that must be configured. Before you configure your workstation for SNA, define the following:
To define the LU name of the topology server on the topology server workstation, use the sample ts.acg configuration file in one of the following directories:
This file is shipped with the NetView management console and represents a sample communications server configuration file for the topology server LU 6.2 communications. Use the configuration file as a guide to tailor the configuration to fit your environment. See the appropriate communications server documentation for more information about LU 6.2 connections.
The tables in this section provide examples of how to define the LU 6.2 sessions between the host and the server workstation.
The fields provided in the tables are fields that, typically, are in the configuration panel for each area. Because each SNA communications program is slightly different, the fields in the tables might not be available in all products or they might be labeled slightly differently.
Table 7 shows an example of the topology server workstation configuration for the data link control profile for SDLC.
| Communications Server Field Name | Example Field Value | Explanation |
|---|---|---|
| Adapter | 0 | The SLDC adapter used for this communication. |
| Line Type | Nonswitched | This will be nonswitched unless you are using a modem that must be dialed. |
| Link Station Role | Secondary | A link station role of secondary is required when connecting to a host through a boundary function. |
| Maximum I-Field Size | 2048 | The maximum RU size must be coordinated with the MAXDATA parameter in the NCP definition for the nonswitched line. |
| Free Unused Links | No | This box cannot be selected for nonswitched communications. |
| Local Station Address | C1 | The SDLC station address of this node. It must match the ADDR parameter in the NCP definition for this node. |
| Line Mode | Full-duplex | This parameter must be coordinated with the DUPLEX parameter in the NCP definition for the nonswitched line. |
| Modem Speed | Full speed | Set the modem rate at full speed unless line noise is a problem. Half speed provides more reliable operation if line noise is a problem. |
| Use NRZI Data Encoding | No | This parameter must match the NRZI parameter in the NCP definition for the nonswitched line. If you select NRZI, the communication hardware between the workstation and the host must support NRZI. |
| Send Window Count | 7 | The send window count must match the MAXOUT parameter in the NCP definition for the nonswitched line. |
| Receive Window Count | 7 | The receive window count must match the MAXOUT parameter in the NCP definition for the nonswitched line. |
Table 8 shows an example of the topology server workstation configuration for the data link control profile for LAN.
| Communications Server Field Name | Example Field Value | Explanation |
|---|---|---|
| Adapter | 0 | The LAN adapter used for this communication. |
| Free Unused Link | No | No indicates that the host connection must not be dropped when the last application is logged off. |
| Local Node Name | A19SRVCP | The 8-character name of the local control point. The name must match the CP name parameter in the host definition for this workstation. |
| Maximum I-field Size | 2048 | Specifies the maximum I-field size that the station can receive. This number must be greater than, or equal to, the maximum I-field size in the transmission service mode profile. For the host connection only, this number must coordinate with the MAXDATA value on the PU definition statement. |
| Maximum Number of Link Stations | 16 | One link is used to allocate sessions to another workstation. This parameter sets the maximum number of link stations that LU 6.2 communication uses. |
| Network ID | NETA | The 8-character name for the network containing this PU. |
| Receive Window Count | 1 | The receive window count specifies the number of frames that the station can receive before sending an acknowledgment. |
| Send Window Count | 7 | The send window count specifies the number of frames that the station can send before receiving an acknowledgment. For the host connection, this number must match the MAXOUT parameter on the PU definition statement. |
Table 9 shows an example of a topology server workstation configuration for the local node characteristics. Modify this profile for either an SDLC or LAN configuration.
| Communications Server Field Name | Example Field Value | Explanation |
|---|---|---|
| Network ID | NETA | The 8-character name of the network containing this PU. |
| Local Node Name (CP name) | A19SRVCP | The 8-character name of the local control point. The name must match the CP name parameter in the host definition for this workstation. |
| Local Node Type | Network node | The topology server can work with any node type. This example, however, assumes that the node type of the server is network node. |
| Local Node ID (in hexadecimal) | (05D) 00001 | Used to determine which link station is primary for negotiable link stations. The node with the higher value becomes the primary link station. For a LAN connection, the first 3 hexadecimal digits are typically '05D'; the last 5 hexadecimal digits must match the IDNUM parameter in the switched major node PU definition. |
Table 10 shows an example of the topology server workstation configuration for the logical unit profile you have specified.
| Communications Server Field Name | Example Field Value | Explanation |
|---|---|---|
| LU Name | A19SRVLO | Specifies the name of the LU as it is known externally to the SNA network. The value must match the host definition for this workstation. This value is unique for each workstation. |
| LU Alias | EGVPC | The name of the local LU profile. Create a local LU profile with the name EGVPC. The topology server requires the value EGVPC. The topology server also requires the LU alias to be specified in uppercase. |
| NAU Address | Independent LU | The topology server requires that an independent LU be selected. |
Table 11 is an example of the topology server workstation configuration for the transmission service mode profile.
| Communications Server Field Name | Example Field Value | Explanation |
|---|---|---|
| Mode Name | DSIL6MOD | Specifies the mode name profile. Create a mode name profile with the name DSIL6MOD. The topology server requires this value. |
| Class of Service | #CONNECT | Specifies the class of service name. Use the system default for this value. |
| Mode Session Limit | 3 | Specifies the mode session limit. The topology server requires a minimum of 3. The sum of the mode session limits for a partner LU must be equal to or less than the partner LU session limit in the partner LU profile. |
| Minimum Contention Winners | 1 | The topology server requires 1 contention winner source session. |
| Receive Pacing Window | 1 | Must be coordinated with the PACING parameter in the NCP definition for this LU and the SSNDPAC and ARCVPAC parameter in the VTAM® logmode entry table for DSIL6MOD. Pacing prevents a session from flooding a node with data and using all the available buffers. |
| RU Size | Default RU | Enables Communications Server to select the most appropriate maximum RU size. If Maximum RU size is selected, the maximum RU size must be smaller than or equal to the maximum RU size in the appropriate DLC profile. |
Table 12 shows an example of the topology server workstation configuration for the transaction program profile.
| Communications Server Field Name | Example Field Value | Explanation |
|---|---|---|
| Service TP | No | The topology server transaction program is not a service TP. |
| Transaction Program (TP) Name | 30F0F4F4 | The required name of the topology server transaction program. This value is case-sensitive and the topology server requires the TP name to be specified in upper case. |
| Transaction Program (TP) File Name | ihsctp.exe | The TP executable file which enables the host and server to communicate. |
| Conversation Security | No | The topology server does not support conversation security. |
| Program Parameter String | The topology server does not require this field. |
If you have an SDLC or LAN connection, configure a connection to the host.
Then configure a connection by performing the following steps:
| Communications Server Field Name | Example Field Value | Explanation |
|---|---|---|
| Link name | LINK0001 | Specifies the user default. |
| Adjacent Node ID | Blank | Specifies the XID used by the partner node. Leave this value blank for the topology server. |
| Partner Network ID | NETID | Use the NETID in the VTAM ATCSTRxx member. |
| Partner Node Name | SSCPNAME | Use SSCPNAME in the VTAMATCSTRxx member. This field and the Partner Network ID can be left blank. |
| LAN Destination Address (LAN only) | The 12-character, hexadecimal LAN address of the computer to which you are defining the connection. | |
| Address Format | Token-ring | This value must match the type of LAN connection you are using: token-ring or ethernet. |
| Remote SAP | 04 | Defines the address of the service access point (SAP) of the host with which you are communicating. |
[ Top of Page | Previous Page | Next Page | Contents | Index ]