                         CHAPTER 3  Using NMA for NetView


This chapter describes the following procedures that you can use
after you install NMA for NetView: 

o  Start the NVCONFIG installation utility

o  Use NVCONFIG to configure or reconfigure the NMA for NetView
   software

o  Load NMA for NetView

o  Unload NMA for NetView

o  Administer NMA for NetView remotely

o  Remove the NMA for NetView software

These are independent procedures--and not subdivisions of a long
procedure. To complete any of these procedures, refer to the page
where the procedure begins.


STARTING NVCONFIG

To start NVCONFIG:

1.  If the server is not running, start the server and all    
    prerequisite NLMs and drivers.

    "Preparing the NetWare v3.1x Server" in Chapter 2  describes
    which NLMs and drivers must be running.

2.  If NMA for NetView is running on your server, unload the    
    program as described on later in this chapter under "Unloading
    NMA for NetView."

3.  Enter the following command:

    :load nvconfig

    The server loads NVCONFIG from the SYS:SYSTEM directory; then
    NVCONFIG displays the Communications Options Menu, which
    includes the following items:

    NetView Host
    NetView Collection Point

    The currently active option, either the NetView Host or
    NetView Collection Point, is marked by an asterisk.


                                                              3-1
CONFIGURING NMA FOR NETVIEW

You must configure the NMA for NetView software before loading NMA
for NetView. Later, if you want to change the configuration, you
can reconfigure NMA for NetView. This section describes how to
configure or reconfigure the NMA for NetView software. 

IMPORTANT:  Before you can configure NMA for NetView, you must have
installed the software as described in Chapter 2.

You can configure the software for

o  Direct host communications

o  Collection point server communications

IMPORTANT:  Although NMA for NetView allows you to configure the
software for either communications option, your installation may
not support both of them. Each communications option requires
specific hardware components and proper NetWare v3.1x preparation.
Configure NMA for NetView to use the option you planned to use when
you followed the installation instructions in Chapter 2. If you
want to configure NMA for NetView to use the other communications
option, review the instructions in Chapter 2 to see what changes
may be required to support the other communications option.


Configuring for Direct Host Communications
------------------------------------------

When using the direct host communications option, the NMA for
NetView server connects to the host through a token ring LAN.

To configure NMA for NetView for direct host communications, use
the following procedure:

1.  Photocopy Table 3-1; then write down the configuration       
    parameters you want to use on the photocopy.

    IMPORTANT:  If you photocopied Table 3-1 as part of the      
    procedure for requesting a PU definition, continue to use the 
    photocopy you created. 

    Table 3-1 divides the configuration parameters into host    
    communication parameters and server and LAN configuration    
    parameters.

    1a.  Ask your host systems programmer for the values for the
         host communication parameters.

         You should get this information when you request a PU   
         definition for the server. Table 2-5 provides additional
         information that can help the host systems programmer   
         locate the host communication parameters for you.

                                                              3-2
    1b.  Define the server and LAN configuration parameters.

         Some of the server and LAN configuration parameters     
         control server operation; other parameters are labels
         that identify the server and LAN in messages exchanged
         with NetView.

         Descriptions for the configuration parameters appear under
         "Communication Parameter Descriptions" later in this    
         chapter.


    Table 3-1
    Configuration Parameters for Direct Host Communications
    ---------------------------------------------------------------
    Host Communication                Status         Value
    Parameters
    ---------------------------------------------------------------
    Token Ring Destination            Required       ____________
    Node Address

    Token Destination Ring            Required       ____________
    Service Access Point (SAP)

    Block ID                          Required for   ____________
                                      937x and 37xx
                                      Attachments

    PUID for Token Ring               Required for   ____________
    Connection                        937x and 37xx
                                      Attachments

    Peripheral Node Control           Optional       ____________
    Point (PCNP) Name

    Token Ring Adapter Type           Required       ____________

    Logical Adapter Name              Required       ------------

    Token Ring Service Access         Required       ------------
    (SAP)

    Maximum Frame Size to             Required       ____________
    Transmit Inbound
    ---------------------------------------------------------------









                                                              3-3
2.  If NVCONFIG is not running, start NCONFIG as described under
    "Starting NVCONFIG" at the beginning of this chapter.

    IMPORTANT:  Novell recommends that you unload NMA for NetView
    before starting NVCONFIG. Configuration changes do not take
    affect until the next time NMA for NetView is loaded.

3.  When NVCONFIG displays the Communications Options menu, use the
    arrow keys to select NetView Host; then press <Enter>.

    The Token Ring Connection to Host configuration screen
    appears, which includes the following items:

    Peripheral Node Control Point Name
    Token Ring Destination Node Address
    Token Ring Destination Service Access Point
    Token Ring Service Access Point
    Token Ring Adapter Type
    Block ID
    PUID for Token Ring Connection
    Maximum Frame Size to Transmit Inbound
    Logical Adapter Name

4.  Edit the host communication parameters.

    Use the arrow keys to select a parameter, then press <Enter>
    to edit the parameter. For some parameters, NVCONFIG displays
    a cursor; for others it displays a menu. When NVCONFIG displays
    a cursor, use the keyboard keys to edit the current value. When
    NVCONFIG displays a menu, use the arrow keys to select the new
    value; then press <Enter>.

    See "Parameter Descriptions for the Token Ring Connection to
    Host Screen," for more more information on each parameter.

5.  When all host communication parameters are set, press <Esc> to
    exit the Token Ring Connection to Host screen.

    If you changed any of the configuration options, the program
    displays a confirmation box that prompts you to save your    
    changes.

6.  In the Save Changes confirmation box, use the arrow keys to
    select Yes; then press <Enter>.

    NVCONFIG configures NMA for NetView for direct host
    communications, saves the configuration parameters, and 
    displays a message that confirms that your changes were saved.

7.  Press <Esc> to clear the confirmation message.





                                                              3-4
8.  Press <Esc> again to exit the Communications Options menu and
    NVCONFIG.

    IMPORTANT:  Exit NVCONFIG before loading NMA for NetView.

The configuration process is now complete. For instructions on
loading NMA for NetView, see "Loading NMA for NetView" later in
this chapter.


Parameter Descriptions for
the Token Ring Connection to Host Screen

The Configuration Options form lists 10 configuration parameters
that you can adjust. Some of these parameters must be set before
NMA for NetView can operate; other parameters are optional. The
rest of this section describes the configuration parameters for
direct host communications.

Block ID.  The block ID must be set to match the corresponding
value at the host. This hexadecimal number identifies the device
type of the remote communication equipment.

The number entered in this field must be three digits long.  To
specify a value less than three digits, supply leading zeros.

When the NMA for Netview server communicates with the host through
a 937x or 37xx attachment, the Block ID parameter must match the
value that follows the IDBLK= statement in the switched PU
definition. When the server communicates through a 3174 controller,
the Block ID parameter is ignored; therefore, no entry is required.

Logical Adapter Name.  Set this parameter to match the adapter
that is entered into the AUTOEXEC.NCF file.  This name must match
the AUTOEXEC.NCF file's adapter name.  The logical adapter name
can be up to 16 alphanumeric and/or special characters.

Maximum Frame Size to Transmit Inbound.  This parameter sets the
frame size for transmissions from NMA for NetView to the host. The
default frame size is 265 bytes. Press <Enter> to display a window
with the following items:

265
521
1033
2042

When configuring NMA for NetView, be sure to set the Maximum Frame
Size to Transmit Inbound parameter to 521 or larger. If this
parameter is set to a smaller size, the NetView host operator may
not receive replies to commands.




                                                              3-5
IMPORTANT:  When NMA for NetView is configured for collection point
communications and the NetView operator reports lost command
replies, check the setting of the Maximum Frame Size to Transmit
Inbound parameter on the collection point server. The collection
point server's Maximum Frame Size to Transmit Inbound parameter
controls NetView communications for the NMA for NetView server.

IMPORTANT:  When changing the maximum frame size to transmit
inbound to 2042 bytes, you must configure your system to
accommodate this setting. Do so by modifying the event control
block (ECB) size in your system's STARTUP.NCF file as follows:

Set maximum physical receive packet size = 2298

Peripheral Node Control Point Name.  The peripheral node control
point (PCNP) name is an optional entry.  In System's Network
Architecture (SNA) terms, the NetWare server is connected to
the host as a peripheral node.  A peripheral node contains a
software entity called a control point, which controls the
resources of the SNA peripheral node.

If you enter a PNCP name, NMA for NetView sends the PNCP name
to NetView in each alert.  If you you do not enter a PNCP name,
NMA for NetView sends the default value, CPNAME.

Peripheral Node Control Point Name.  The Peripheral Node Control
Point (PNCP) name is an optional entry. In Systems Network
Architecture (SNA) terms, the NetWare server is connected to the
host as a peripheral node. A peripheral node contains a software
entity called a control point, which controls the resources of the
SNA peripheral node.

If you enter a PNCP name, NMA for NetView sends the PNCP name to
NetView in each alert. If you do not enter a PNCP name, NMA for
NetView sends the default value, CPNAME.

PUID for Token Ring Connection.  The PU ID must be set to match the
corresponding PU ID at the host.

When the NMA for Netview server communicates with the host through
a 937x or 37xx attachment, the PU ID parameter must match the value
that follows the IDNUM= statement in the switched PU definition.
When the server communicates through a 3174 controller, the PU ID
parameter is ignored; therefore, no entry is required.











                                                              3-6
Token Ring Adapter Type.  In this field, specify the type of
adapter your server is using for the host connection.  Press
<Enter> to display your two choices:

Primary
Alternate

Select Primary if the token ring adapter type switch (on the
adapter) has been set to Primary; select Alternate if the
adapter type switch has been set to Alternate. (Refer to the
token ring adapter manual for information on switch settings.)


Token Ring Destination Node Address.  The token ring address must
be set to match the address of the host's token ring connection.
Table 3-1 lists the host communication parameters that your host
systems programmer should provide. Table 2-5 on page 2-22 provides
additional information that the host systems programmer can use to
locate the correct values.


Token Ring Destination Service Access Point.  This is the
two-digit SAP number for the host.

Set this parameter to match the SAP ID of the host's token ring
connection.  Table 3-1 lists the communication parameters that
your host systems programmer should provide.  Table 2-4 on page
2-23 provides additional information that the host systems
programmer can use to locate the correct value.


Token Ring Service Access Point.  This is the two-digit SAP
number for the server.

Set this parameter to match the SAP ID of the host's token ring
connection. Table 3-1 lists the communication parameters that your
host systems programmer should provide. Table 2-5 in Chapter 2
provides additional information that the host systems programmer
can use to locate the correct values.


Configuring for NetView Collection Point Communications
-------------------------------------------------------

When configured for collection point communications, 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.

IMPORTANT:  When NMA for NetView is configured for collection point
communications and the NetView operator reports lost command
replies, check the setting of the Maximum Frame Size to Transmit
Inbound parameter on the collection point server. The collection
point server's Maximum Frame Size to Transmit Inbound parameter
controls NetView communications for the NMA for NetView server.

                                                              3-7
When NMA for NetView is configured for collection point server
communications, the collection point server provides the
following information in all forwarded messages:

o  The PCNP name assigned to the collection point server

o  The model number of the collection point server

o  The serial number of the collection point server

For information on setting these parameters within NetWare for SAA,
see the NetWare for SAA v1.3 Administration Guide.

To configure NMA for NetView for NetView collection point
communications, use the following procedure:

1.  If NVCONFIG is not running, start NVCONFIG as described in
    "Starting NVCONFIG" at the beginning of this chapter.

    IMPORTANT:  Novell recommends that you unload NMA for NetView
    before starting NVCONFIG. Configuration changes do not take
    affect until the next time NMA for NetView is loaded.

2.  When NVCONFIG displays the Communications Options menu, use the
    arrow keys to select NetView Collection Point; then press
    <Enter>.

    NVCONFIG displays the Connection to Collection Point dialog
    box, which prompts you to enter the collection point server
    name.

3.  Enter the collection point server name.

    The value you enter must match the server name that was
    entered when the collection point server was started. The
    collection point server you name must be running NetWare for
    SAA v1.3 or later must be configured to support NetView
    collection point communications.

    IMPORTANT:  When changing the configuration from direct host
    communications to collection point server communications, you
    must edit the collection point server name. If you do not edit
    the name, NVCONFIG does not prompt you to save the
    configuration and NMA remains configured for direct host
    communications.

4.  Press <Esc> to exit the Connection to Collection Point
    dialog box.

    If you changed any of the configuration options, the program
    displays a confirmation box that prompts you to save your
    changes.  If you do not want to save changes to the
    configuration, select No, and press <Enter>.


                                                              3-8
5.  In the Save Changes confirmation box, use the arrow keys to
    select Yes; then press <Enter>.

    NVCONFIG configures NMA for NetView for collection point server
    communications, saves the collection point server name, and  
    displays a message that confirms that your changes are saved.

6.  Press <Esc> to clear the confirmation message.

7.  Press <Esc> again to exit the Configuration Options menu and
    NVCONFIG.

The configuration process is now complete; NMA for NetView is ready
for loading.

IMPORTANT:  Exit NVCONFIG before loading NMA for NetView.

For instructions on loading NMA for NetView, see "Loading NMA for
NetView" later in this chapter. Instructions for automating the
startup procedure appear under "Automating Server Startup" in
Chapter 2.


LOADING NMA FOR NETVIEW

The process of starting the NMA for NetView software is called
loading. Before loading NMA for NetView, you must install and
configure NMA for NetView. Chapter 2 describes how to install NMA
for NetView; configuration instructions appear under "Configuring
NMA for NetView" earlier in this chapter.

IMPORTANT:  Every time you load NMA for NetView, you must first
execute a series of commands. These commands are identified in
"Preparing the NetWare v3.1x Server," in Chapter 2.

To load NMA for NetView, enter the following command:

:load nmanv

IMPORTANT:  Novell recommends that you automate the loading process
for NMA for NetView by loading the software from the AUTOEXEC.NCF
file. For more information on the AUTOEXEC.NCF file, see
"Automating Server Startup" in Chapter 2.












                                                              3-9
UNLOADING NMA FOR NETVIEW

Unload NMA for NetView when you want to

o  Change the configuration of NMA for NetView 

o  Remove the NMA for NetView software

To unload NMA for NetView from the NetWare server, enter the
following command:

:nvdown

NetWare displays a message informing you that NMANV.NLM has been
unloaded.


ADMINISTERING NMA FOR NETVIEW REMOTELY

You can set up the server with NMA for NetView installed to
support the NetWare RCONSOLE utility.  With RCONSOLE you can
load, unload, and configure NMA for NetView remotely from a
workstation as follows:

1.  Make sure that the REMOTE and RSPX NLMs are loaded on the
    server installed with NMA for NetView.

2.  From your network workstation, log in as SUPERVISOR to the
    directory on the local network server containing the remote
    network files (usually SYS:SYSTEM).

3.  Start the RCONSOLE utility, and select the server installed
    with NMA for NetView.

4.  When the system console prompt appears on your workstation
    screen, load or unload NMA for NetView or start NVCONFIG as
    if you were sitting at the server console.

See the information on RCONSOLE in the NetWare v3.1x System
Administration Guide for more information on running RCONSOLE.


REMOVING THE NMA FOR NETVIEW SOFTWARE

Remove the NMA for NetView software when

o  Upgrading from a previous version of NMA for NetView

o  Preparing to install NetWare for SAA

To remove NMA for NetView v1.3, use the NetWare INSTALL utility.
When removing the software, the NetWare INSTALL utility deletes
the NMA for NetView files from the server's SYS:SYSTEM directory
and deletes entries from the internal NetWare bindery.

                                                              3-10
IMPORTANT:  To remove a previous version of NMA for NetView,
follow the removal directions that came with that version.  Do
not use the NetWare INSTALL utility to remove versions of NMA for
NetView previous to v1.3.


1.  Start the NetWare INSTALL utility. Type

    :load install

2.  Select Product Options from the Installation Options menu.

3.  Use the arrow keys to select NMANV v1.3.0 NMA for NetView
    from the Currently Installed Products listing.

4.  Press <Delete>.

5.  When the Uninstall NMANV prompt appears, select Yes to confirm
    the removal of NMA for NetView v1.3.
































                                                              3-11

