	 CHAPTER 2  Installing NMA for NetView
     
     
This chapter describes how to

o  Install NMA for NetView on a NetWare v3.1x server

o  Prepare the host for communications with an NMA for NetView
   server

IMPORTANT:  NMA for NetView and NetWare for SAA provide similar
support for NetView. Do not install both NMA for NetView and
NetWare for SAA in the same server.

IMPORTANT:  Before you install this version of NMA for NetView on
a NetWare v3.11 server, read the additional instructions provided
in the NMANET.TXT text file.

OVERVIEW

Installation of the NMA for NetView consists of the following
tasks:

o  Obtain the software and manual (see this chapter)

o  Prepare the installation diskettes (see this chapter)

o  Choose an connection topology (see this chapter)

o  Set up the required server hardware and software
   (see this chapter)

o  Prepare the NetWare v3.1x server (see this chapter)

o  Install the NMA for NetView software (see this chapter)

o  Prepare the host for NMA for NetView (see this chapter)

o  Configure NMA for NetView (see Chapter 3)


OBTAINING THE SOFTWARE AND THE MANUALS

NMA for NetView v1.3 is distributed via NetWire, an online information
software delivery service from Novell available through the CompuServe*
information service. This section describes how to obtain the software 
and the manual. If you already have copies of the software and the 
manuals, you can skip this task.

NetWire subscribers can locate software updates in the NovLib
forum area. The compressed files for NMA for NetView files are 
located in the NovFiles area.  These files are listed in Table 2-1.





								 2-1
Table 2-1 
NMA for NetView Files on NetWire
-----------------------------------------------------------------
File               Function
-----------------------------------------------------------------
NMANET.TXT         Describes the contents of the NetWare
		   Express package for NMA for NetView. This file
		   also provides instructions for printing the
		   PostScript and ASCII files provided with NMA
		   for NetView. 

DISK1.EXE          Contains the NMA for NetView files for
		   installation diskette 1. Download this
		   compressed file and use it to create NMA for
		   NetView v1.3, Disk 1, as described in the next
		   section.
   
DISK2.EXE          Contains the NMA for NetView files for
		   installation diskette 2. This compressed
		   file contains installation files and code point
		   files that you may need. Download DISK2.EXE
		   and use it to create NMA for NetView v1.3,
		   Disk 2, as described in the next section.

OS.EXE             Contains files to prepare servers running 
		   NetWare v3.11 to support NMA for NetView v1.3.
		   Do not download for servers running NetWare v3.12
		   or later.

PSGUID.EXE         Contains the PostScript version of this guide.
		   The PostScript version is a complete guide
		   with all illustrations. To print this guide,
		   you must have a PostScript printer.
   
ASGUID.EXE         Contains the ASCII version of this guide. The
		   ASCII version does not contain figures. Novell
		   recommends that you use a monospaced font to
		   view or print the expanded version of this
		   file. Proportional-spaced fonts change the
		   appearance of this file and may make the guide
		   difficult to read.

PSREF.EXE          Contains the PostScript version of the NetWare
		   Reference Guide for NetView Operators. The
		   PostScript version is a complete guide with
		   all illustrations. To print this guide, you
		   must have a PostScript printer.



								 2-2
Table 2-1 (continued)
NMA for NetView Files on NetWare Express
-----------------------------------------------------------------
File               Function
-----------------------------------------------------------------
ASREF.EXE          Contains the ASCII version of the NetWare
		   Reference Guide for NetView Operators. The
		   ASCII version does not contain figures. Novell
		   recommends that you use a monospaced font to
		   view or print the expanded version of this
		   file. Proportional-spaced fonts change the 
		   appearance of this file and may make the guide
		   difficult to read.
-----------------------------------------------------------------

Before installing NMA for NetView, you must download the
DISK1.EXE and DISK2.EXE files. Before decompressing these
files, read the information in the next section, "Preparing the
Installation Diskettes."

For instructions on downloading, decompressing files, see the guide
that came with your NetWare Express software. Instructions for
printing the administration and reference guide files appear in
the NMANET.TXT file. For the latest information regarding changes
to these procedures, look for announcements on the NetWare Support
Encyclopedia.

SUGGESTION:  Consider downloading, decompressing, and printing a
version of the NetWare Reference Guide for NetView Operators.
Then give the reference guide to your NetView operator. The
information in the reference guide is designed to help the
NetView operator manage NetWare servers.


PREPARING THE INSTALLATION DISKETTES

Before you install NMA for NetView v1.3, you must have or create 
copies of the following diskettes:

o  NMA for NetView v1.3, Disk 1

o  NMA for NetView v1.3, Disk 2

o  OS Update Disk (required for NetWare v3.11 servers only)


1.  If you have not already downloaded the software files,
    download the following files you need to your hard disk.
	
    o  DISK1.EXE

    o  DISK2.EXE

    o  OS.EXE (if you are installing on a NetWare v3.11 server)

								 2-3
2.  Format two or three high-density diskettes.

    You can use 3.5-inch or 5.25-inch high-density diskettes. If
    the target server is running NetWare v3.12, you need only
    format two high-density diskettes.
    
3.  Label the diskettes as follows:

    o  NMA for NetView v1.3, Disk 1
    
    o  NMA for NetView v1.3, Disk 2
    
    o  OS Update Disk (required for NetWare v3.11 servers only)

4.  Decompress the DISK1.EXE file and place the contents on
    the diskette labeled NMA for NetView v1.3, Disk 1.
    
    To decompress DISK1.EXE, enter a command similar to the 
    following. 
    
    disk1 -d A:
    
    In this example, DISK1 is the name of the self-decompressing
    file, and A: is the designation of the disk drive where the
    decompressed files will be placed.

IMPORTANT:  To ensure that all directories and subdirectories are 
decompressed, use the -d parameter as shown in the example above.

5.  Decompress the DISK2.EXE file onto the diskette labeled NMA for 
    NetView v1.3, Disk 2.  Use the -d parameter as shown above.

6.  If you are installing on a NetWare v3.11 server, decompress
    the OS.EXE file and onto the diskette labeled OS Update Disk.
    Use the -d parameter shown above.
    

CHOOSING A CONNECTION TOPOLOGY

Before you set up the NMA for NetView server, you must choose the
host communications option you will use. The host communications
options are

o  Direct host communications

o  Collection point server communications

The host communications options are described in Chapter 1 under
"Host Communications Options."

After you choose the host communications option, you need to
choose the topology for your connection. The topology you choose
determines the hardware and software you need to install.

There are many ways to assemble a NetWare network for NetView
management. This section describes some sample topologies that
support the NMA for NetView host communications options.
								 2-4
Topologies That Support Direct Host Communications
--------------------------------------------------

This section describes two examples of topologies that support
direct host communications.

Example 1

In topology example 1, the NMA for NetView server is connected
to two separate LANs:

o  One token ring LAN connects the NMA for NetView server, either
   directly or indirectly, to the NetView host. Indirect
   connections are supported by a variety of host communications
   equipment, such as an IBM 3174 Attachment.
   
o  The other LAN connects to both NMA for NetView and the
   workstations that use the file and print services of NetWare
   v3.1x.
   
In this example, the NMA for NetView server requires

o  An IBM 16/4 or 16/4/A Token Ring adapter for communications
   with the host LAN
   
o  Cabling from the token ring adapter to the host LAN

o  A network adapter for the workstation LAN

o  Cabling from the NMA for NetView server to the workstation LAN

Each cabling connection should provide a path (via cables,
bridges, routers, and gateways) to the respective communications
target, either the host LAN or the NetWare LAN.

Example 2

In topology example 2, the NMA for NetView server is connected
to one token ring LAN. The same token ring LAN connects to:

o  The NetView host (Indirect connections are supported by a
   variety of host communications equipment, such as an IBM 3174
   Attachment.)
   
o  The workstations that use the file and print services of
   NetWare v3.1x

When using this topology, NMA for NetView requires an IBM 16/4 or
16/4/A Token Ring adapter and cabling from the NMA for NetView
server to the host LAN. The cabling connection should provide a
path (via cables, bridges, routers, and gateways) to the host LAN
and all NetWare workstations.



								 2-5
A Topology That Supports Collection Point Communications
--------------------------------------------------------

When using the collection point communications option, NMA for
NetView indirectly connects to the host computer through a
NetWare for SAA server. In this system configuration, the NetWare
for SAA server is called a collection point server.

When operating as a collection point server, the NetWare for SAA
server uses the following connections:

o  A connection via the NetWare LAN to the NMA for NetView server

o  A token ring, SDLC, QLLC, or Ethernet connection to the host's
   communications equipment

In this topology, the NMA for NetView server connects to a single
network through one network adapter. The NMA for NetView server
uses the same adapter and network to communicate with the
collection point server and the NetWare workstations. 

This topology requires one network adapter and one network
connection. The network connection should provide paths (via
cables, bridges, routers, and gateways) to the collection point
server and the NetWare workstations.
 
SUGGESTION:  If you are adding NMA for NetView to an operating
NetWare v3.1x server and you plan to use a collection point
server topology, you can use the server's existing network
adapter--you do not need to install an additional adapter. As is
required for a new server in this topology, the network
connection must provide a path to the collection point server. 


SETTING UP THE REQUIRED SERVER HARDWARE AND SOFTWARE

NMA for NetView requires certain hardware and software.

Required Hardware
-----------------

NMA for NetView requires the following hardware:

o  A personal computer that uses an 80386 or 80486 microprocessor.

o  One or more network adapters. (See "Choosing a Connection
   Topology"  earlier in this chapter.)

o  Cabling between all network adapters and the appropriate
   network. (See "Choosing a Connection Topology" earlier in this
   chapter.)
   
o  A minimum of 6 megabytes (MB) of random access memory (RAM): 2
   MB for NMA for NetView and a minimum of 4 MB for NetWare v3.1x.
   To calculate the total memory required, determine how much   
   memory is required by NetWare v3.1x (as described in NetWare
   Version 3.11 Installation), and then add 2 MB.
								 2-6
Refer to the manuals for each hardware product for installation
instructions.

IMPORTANT:  Record the option settings of all jumpers and
switches on each network adapter. If the board has a network
address or serial number, record these items also. When using two
or more adapters for the same type of cabling system, be sure to
note which adapter is connected to which network.

SUGGESTION:  If you are adding a network adapter to an operating
server, you must bring down the server and turn off the power. To
minimize the interruption to file server users, consider waiting
until the file server is idle or is scheduled for routine
maintenance.


Required Software
-----------------

NMA for NetView requires the following software:

o  NMA for NetView v1.3 software.

o  NetWare v3.1x (any version of NetWare later than v3.1 or less
   than v4.0), which includes

   o  Clib (CLIB.NLM) to support the library of C functions.

   o  Btrieve(R) (BTRIEVE.NLM), which manages the database that
      holds your NMA for NetView configuration parameters.

o  Network drivers to support each installed network adapter.
   (Some drivers are provided with NetWare v3.1x.)

Refer to the manuals for each software product for installation 
instructions.

SUGGESTION:  Because all other software components must be loaded
before you run NMA for NetView, Novell recommends that you automate
their loading by inserting the appropriate statements in your
server's AUTOEXEC.NCF file. For additional information on
AUTOEXEC.NCF, see "Automating Server Startup" later in this
chapter.












							      2-7
PREPARING THE NETWARE V3.1x SERVER

IMPORTANT:  If you are installing NMA for NetView on a NetWare
v3.11 server, first read and carry out the instructions in the 
NMANET.TXT file in the section titled "Preparing the NetWare 
v3.11 Server."  THEN carry out the instructions in this section.

You must prepare the NetWare v3.1x server for the installation
and operation of NMA for NetView as follows:

o  Install NetWare v3.1x.

o  Start NetWare v3.1x.

o  Load all required NLMs.

o  Configure the Btrieve NLM.

o  Load and bind the appropriate LAN adapter driver.

For instructions on installing and starting NetWare v3.1x, refer
to NetWare v3.1x Installation.

For instructions on downing or restarting NetWare v3.1x, see the
Down and Server command descriptions in NetWare v3.1x
System Administration.

The rest of this section provides additional information on the
NLMs and drivers that must be loaded and configured.


Loading the Required NLMs
-------------------------

To prepare the server for NMA for NetView, you must load the
following NLMs (which are provided with NetWare v3.1x):

o  Btrieve

o  Clib

o  STREAMS

You must load Btrieve before you can install or operate NMA for
NetView. NetWare Btrieve is a database management system that
manages your NMA for NetView configuration parameters. Btrieve
requires the CLIB NLM.

Example for Direct Host Communications

The following command list is an example of the commands required
to prepare a NetWare v3.1x server for direct communications between
NMA for NetView and the host:

:LOAD CLIB
:LOAD BTRIEVE -p=4096 -f=20 -h=60 -l=20 -c
:LOAD TOKEN  NAME=<logical_adapter_name>
							      2-8
When configured for direct host communications, NMA for NetView
uses its own SNA protocol stack to communicate with the host. No
additional communication protocol NLMs are required for host
communications.

The LOAD TOKEN command loads the driver for the LAN adapter. The
NAME=<logical_adapter_name> parameter specifies the name of the
token ring LAN adapter. This procedure is described under "Loading
for Direct Host Communications" later in this chapter.

NOTE:  The NetWare v3.1x server requires additional communication
protocol NLMs for workstation communications. This section
describes only the requirements for NMA for NetView.


Example for Collection Point Communications

The following command list is an example of the commands required
to prepare a NetWare v3.1x server for IPX/SPX communications with
a collection point server:

:LOAD CLIB
:LOAD SPXS
:LOAD BTRIEVE  -p=4096 -f=20 -h=60 -l=20 -c
:LOAD <landriver>
:BIND <protocol> TO <landriver>

When configured for collection point communications, NMA for
NetView must use an SPX connection to communicate with the
collection point server. The communications path may be direct, or
it may require intermediate communications devices such as bridges
and gateways.

The LOAD landriver and BIND commands load the driver for the LAN
adapter and bind it to the communications protocol. This procedure
enables communications with the collection point server and is
described under "Loading for Direct Host Communications" later in
this chapter.

Locating NLMs

The NLMs in the previous examples are included in the NetWare
v3.1x product package and are described in NetWare Version 3.11
System Administration and in Btrieve Installation and Operation.

SUGGESTION:  If you are adding NMA for NetView to a previously
installed NetWare v3.1x server, enter the MODULES command to list
the NLMs that have already been loaded. The MODULES command is
described in NetWare v3.1x System Administration.






							      2-9
Configuring Btrieve
-------------------

If you have changed the default settings in Btrieve, you may need
to reconfigure Btrieve to support NMA for NetView. 

To configure Btrieve for operation with NetView, enter the
configuration parameters with the LOAD command at startup.

Table 2-2 lists the Btrieve configuration parameters and the
settings that NMA for NetView requires.


Table 2-2
Btrieve Configuration Settings for NMA for NetView
-----------------------------------------------------------------
Btrieve Parameter                   LOAD Command        Suggested
				    Line Option         Value
-----------------------------------------------------------------
Number of open files                    -f                20

Number of handles                       -h                60

Number of locks                         -l                20

Number of transactions                  -t

Number of files per transaction         -n

Largest compressed record size          -u

Largest record size                     -d

Largest page size                       -p              4096

Number of sessions                      -s

Create files as transactional           -i

Logging of selected files               -a
-----------------------------------------------------------------

Configuring on the Command Line

To load and configure Btrieve simultaneously, enter the following
command:

:load btrieve -p=4096 -f=20 -h=60 -l=20 -c

NOTE:  If Btrieve is already loaded, you must unload Btrieve and
then load it with the configuration parameters. To unload Btrieve,
enter the command UNLOAD BTRIEVE at the system console prompt (:).



							      2-10
Loading and Binding the LAN Adapter Driver
------------------------------------------

You must load an adapter driver for the adapter through which you
communicate with the host. If you plan to configure NMA for
NetView for collection point communications, you must bind the
adapter driver to a communications protocol.


Loading for Direct Host Communications

When NMA for NetView is configured for direct host
communications, you must use a token ring adapter and adapter
driver for host communications. Because NMA for NetView uses its
own SNA protocol stack to communicate with the host, you do not
have to bind the adapter driver to a protocol.

IMPORTANT:  If you plan to use the same adapter for host and
workstation communications, you will have to bind the adapter
driver to a communications protocol.

The TOKEN.LAN adapter driver is supplied with NetWare v3.1x. To
load the TOKEN.LAN adapter driver, enter the following command:

:load token

After you enter the LOAD TOKEN command, the server prompts you
for the configuration of the token ring adapter.

If you prefer to enter the configuration parameters with the LOAD
TOKEN command, enter a command that is similar to the following:

:load token port=a20 int=2 node=12345678 saps=4 ls=32
  name=<logical_adapter_name>

Set the adapter configuration parameters as follows:

o  PORT. Set the port parameter to A20 if it is the primary
   adapter; use A24 for the alternate adapter. (Refer to the manual
   that came with the token ring adapter for information on adapter
   switch settings.)
   
o  INT. Enter the interrupt number used by the token ring
   adapter. If you do not know what interrupt the adapter uses,  
   refer to the manual for the adapter.
   
o  NODE. Node refers to the address of the server's token ring
   adapter that communicates with the host. Enter the last eight
   digits of the adapter's locally administered address, which is
   defined by the LAN or system administrator.
   




							      2-11
o  SAPS. This parameter specifies the number of service access
   points (SAPs) that can be opened by an application using the  
   token ring adapter. The number of SAPs must be 04 or a multiple
   of 04, and depends on the number of services running on the node
   (generally one SAP per service). Consult the token ring adapter 
   manual for information on calculating the maximum number of   
   SAPs.
   
o  LS. This parameter specifies the number of link stations. This
   value should be eight times the SAPs setting.
   
o  NAME.  This parameter specifies the name for the token ring
   LAN adapter.  The logical name can be up to 16 alphanumeric
   and/or special characters.  You will use this name later to
   configure the Logical Adapter Name field in the NVCONFIG
   program.

Loading and Binding for Collection Point Server Communications

When NMA for NetView is configured for collection point server 
communications, you must load an adapter driver and bind it to a 
communication protocol. The type of adapter and communication
protocol you use depends on the network through which you will
connect to the collection point server.

The following command list is an example of the commands required
to load an NE2000 adapter driver and bind it to IPX:

:load ne2000
:bind ipx to ne2000

NetWare v3.1x provides some adapter drivers and the IPX
communications protocol. For information on using this software,
see NetWare v3.1x Installation. For additional information
on the driver required by your adapter, see the manual for your
adapter.


Automating Server Startup
-------------------------

As the previous sections illustrate, you must enter a number of
commands to prepare a NetWare v3.1x server for NMA for NetView. To
make starting a server easier, the NetWare v3.1x INSTALL utility
allows you to create a startup file, which operates in a manner
similar to the DOS AUTOEXEC.BAT file.

The startup file for NetWare v3.1x servers is named AUTOEXEC.NCF,
and it must be created with the INSTALL utility. The INSTALL
utility includes a special option that automatically enters the
names of all loaded NLMs and drivers into the AUTOEXEC.NCF file.

Novell recommends that you use the AUTOEXEC.NCF file to automate
server startup. Creating the AUTOEXEC.NCF file is generally easier
than writing down the commands you need to execute.
							      2-12
When you create the AUTOEXEC.NCF file, enter all the commands to
prepare the server for NMA for NetView; then add the command to
start NMA for NetView:

load nmanv

For instructions on creating the AUTOEXEC.NCF file, see the
server installation section of NetWare Version 3.11 Installation
or the section on the INSTALL utility in NetWare Version 3.11
System Administration.


INSTALLING THE NMA FOR NETVIEW SOFTWARE

This section describes how to install the NMA for NetView
software.

IMPORTANT:  If NetWare for SAA is installed in the NetWare v3.1x
server, do not install the NMA for NetView software. NetWare for
SAA provides NetView network management support, which is similar
to NMA for NetView.

To install the NMA for NetView software:
    
1.  If the server is not running, start the server and all
    prerequisite NLMs and drivers.
    
    "Preparing the NetWare v3.1x Server" earlier in this chpater
    describes which NLMs and drivers must be running.


2.  If NMA for NetView v1.0 or v1.2 is installed in the server,
    remove that version of the software.

    IMPORTANT:  Do not use the NetWare INSTALL utility to remove
    versions of NMA for NetView earlier than v1.3. You must remove
    earlier versions of NMA for NetView with the same version of
    NVINSTAL that was used to install that version of NMA for
    NetView.
    
    For instructions on removing previous versions of NMA for
    NetView, see the documentation for that version of NMA for
    NetView.
    
3.  Insert NMA for NetView v1.3, Disk 1 into one of the server's
    disk drives.
   
4.  Start the NetWare INSTALL utility. Enter

    :load install

5.  When the Installation Options window appears, select the
    Product Options option.


							      2-13
6.  When the Currently Installed Products window appears, press
    <Insert>.

    The "Enter drive..." dialog box appears, prompting you to
    specify the location of your NMA for NetView Installation
    files.

7.  If you inserted NMA for NetView v1.3, Disk 1 in the server's
    drive A:, press <Enter>; otherwise, type the letter of the
    drive where you inserted the diskette and press <Enter>.

8.  When the Install displayed product? window appears, select
    the option to Install on this server.

9.  Follow the prompts until all the required files are installed
    on the server.

    After installation is complete, the NMA for NetView
    Communications Options menu appears.

10. Configure NMA for NetView for connection to an SNA host or
    to a NetView collection point.  See the next chapter,
    "Configuring, Loading, and Unloading NMA for NetView" for
    details.

    o  Before operating NMA for NetView, you must configure the
       software as described in "Configuring NMA for NetView" in
       the next chapter.

    o  If you are not ready to configure the software you can
       exit the NetWare INSTALL program and restart the program
       when you are ready to configure.  To exit the program,
       press <Esc>.






















							      2-14
PREPARING THE HOST

NMA for NetView requires certain hardware and software at the
host computer. As shown in Table 2-3, these host requirements vary
according to the NMA for NetView communications option in use.

Table 2-3
Host Requirements
-----------------------------------------------------------------
Components                      Direct Host      Collection Point
				Communications   Communications
-----------------------------------------------------------------
NetView software                Required         Required
on the host

PU Type 2.0 definition          Required         Not applicable
in VTAM on the host

Token ring LAN connection       Required         Not applicable
between the host and the
NMA for NetView server

NetWare for SAA  on             Not applicable   Required
collection point server

Host communications             Not applicable   Required
link to the
collection point server

NetView code points             If needed        If needed
for NetWare on the host
-----------------------------------------------------------------

The following sections describe each of the host components that
may be required.


NetView Software
----------------

The NetView software is required to receive the NetWare alert
messages and send commands to NetWare servers. The host systems
programmer is responsible for installing NetView.


PU Type 2.0 Definition in VTAM
------------------------------

If you are configuring NMA for NetView for direct host
communications, the host must allocate a physical unit (PU) for the
NMA for NetView server. NetView messages flow over a session
between the PU and the system services control point (SSCP) host
component.


							      2-15
NOTE:  Servers that are configured for collection point
communications use the SSCP-PU session allocated to the collection
point server. When using the collection point communications
option, the NMA for NetView server does not require a PU
definition.

You are responsible for telling the host systems programmer what
type of PU definition you need. Because some NMA for NetView
configuration parameters must be set to match certain host
parameters, you must ask the host systems programmer for the host
configuration parameter settings.

To request a PU and get the host configuration parameters, you
need to do the following:

1.  Photocopy Table 3-1 in Chapter 3.

    The host communications parameters in Table 3-1 are the NMA
    for NetView parameters that must be set to match parameters at
    the host.
    
2.  Contact the host systems programmer and request a PU
    definition for your NMA for NetView server.
    
    Table 2-4 lists three types of host communication equipment
    and the PU definition required for each type. The host systems
    programmer should be able to tell you what type of    
    communication equipment is processing your connection. 
    
    
    Table 2-4
    PU Type Definitions for Host Communication Equipment 
    ---------------------------------------------------------------
    Communication Equipment              PU Definition
    ---------------------------------------------------------------
    937x attachment and 37xx             Switched token ring PU
    attachment                           Type 2.0
    
    3174 controller                      Nonswitched PU Type 2.0
    ---------------------------------------------------------------
    
    NOTE:  NMA for NetView requires no LU definitions.

    Figure 2-1 is a sample PU definition for a 937x attachment.
    This sample is provided to assist the host systems programmer
    in allocating a PU definition for NMA for NetView.









							      2-16
    Figure 2-1
    Sample PU Definition for a 937x Attachment
    _______________________________________________________________
    
    NMA4NV VBUILD TYPE=SWNET
    ***************************************************************
    * TOKEN RING PU 2.0 FOR NMA for NETVIEW
    ***************************************************************
    PT12345 PU ADDR=04,                                        X
		      IDBLK=017
		      IDNUM=12345
		      LANSW=YES
		      MAXDATA=1033
		      PUTYPE=2
		      ISTATUS=ACTIVE
    _______________________________________________________________
      
3.  Ask the host systems programmer for the host communications
    parameters for your NMA for NetView server.

    Table 2-5 lists the NMA for NetView configuration parameters
    that must match settings on the host communications equipment.
    The first column lists the parameter names as they appear in
    NVCONFIG. Columns 2 through 4 list the corresponding host
    parameters for three types of host communications equipment.
    
    
    Table 2-5
    NVCONFIG Parameters That Must Match Host Parameters
    ---------------------------------------------------------------
    NVCONFIG     937x Attachment  37xx Attachment   3174 Controller
    Parameter    Parameter        Parameter         Parameter
    Name         Location         Location          Location
    ---------------------------------------------------------------
    Peripheral   CPNAME state-    Not applicable    Not applicable
    Node Con-    ment (if any)
    trol Point   in the switched
    Name         PU definition

    Token Ring   MACADDR          Token interface   Statments 900
    Destination  definition       card (TIC)        and 940 in the 
    Node         in the PORT      address (LOCADD=  Customization 
    Address      statement        value)in the      Panels
				  Network Control 
				  Program (NCP)
				  definition
	
    Token Ring   SAPADDR          Enter 4 for       Configuration
    Destination  definition       this parameter    question 900 in
    Service      in the PORT                        the 3174
    Access       statement                          Customization
    Point                                           Panels



							      2-17
    Table 2-5 (continued)
    NVCONFIG Parameters That Must Match Host Parameters
    ---------------------------------------------------------------
    NVCONFIG     937x Attachment  37xx Attachment   3174 Controller
    Parameter    Parameter        Parameter         Parameter
    Name         Location         Location          Location
    ---------------------------------------------------------------

    Token Ring   SAPADDR          Enter 4 for       Statement 940
    Service      definition       this parameter    in the
    Access       in the PORT                        Customization
    Point        statement                          Panels

    Block ID     IDBLK statement  IDBLK statement   Not applicable;
		 in the switched  in the switched   entry required
		 PU definition    PU definition

    PU ID for    IDNUM statement  IDNUM statement   Not applicable;
    Token Ring   in the switched  in the switched   no entry
    Connection   definition       definition        required

    ---------------------------------------------------------------

    Record the host systems parameters as follows:

    3a.  Locate the column in Table 2-6 for the host
	 communications equipment your host connection will use.
    
    3b.  Ask the host systems programmer for the values of the
	 parameters in that column.
 
    3c.  Write down the host communications parameters on the
	 photocopy of Table 3-1.
     
4.  Save the photocopy of Table 3-1 so that you have the host 
    configuration information when you configure NMA for NetView.
    (Configuration instructions appear under "Configuring NMA for
    NetView" in Chapter 3.)
    
    
Connection to the Token Ring LAN
--------------------------------

When NMA for NetView is configured for direct host communications,
the host must be connected to the token ring LAN. The host systems
programmer should be responsible for this task.


NetWare for SAA
---------------

When NMA for NetView is configured for collection point
communications, you must install NetWare for SAA. To configure
NetWare for SAA for host communications, see the NetWare for SAA
v1.3 Administration Guide.
							      2-18

Host Communications Link to the Collection Point Server
-------------------------------------------------------

When NMA for NetView is configured for collection point
communications, the collection point server (NetWare for SAA)
requires a token ring, Ethernet, SDLC, or QLLC connection to the
host's communications equipment. For more information on establishing
a host communications link to the collection point server, see the
NetWare for SAA v1.3 Administration Guide.


Installation of NetView Code Points for NetWare
-----------------------------------------------

The code points allow NetView to display additional information
about alerts that are received from NMA for NetView. These code
points are provided with NMA for NetView and with NetView Version
2.1.

You may not need to install the code points for NetWare. If you
are using NetView Version 2.1, the code points are included with
NetView and do not have to be installed.

If you are using an earlier version of NetView, the code points
for NetWare must be installed once. You and the host systems
programmer must install the code points if the NetWare code points
have never been installed. Installation is not required if the code
points for NetWare have been installed for any other NMA for
NetView v1.3 server or NetWare for SAA v1.3 server. For
additional information on code points and their installation, see
Appendix A.









							      2-19
