NETWARE MANAGEMENT AGENT FOR NETVIEW ADMINISTRATION GUIDE Table of Contents Who Should Read This Guide Content Overview Conventions Typographic Conventions Terminology Additional Reading CHAPTER 1 About NMA for NetView What Is NMA for NetView?. . . . . . . . . . . . . . 1-1 What Is New in Version 1.3B . . . . . . . . . . . 1-2 NMA for NetView Features. . . . . . . . . . . . . 1-3 Alert Generation. . . . . . . . . . . . . . . . . 1-3 RUNCMD Processing . . . . . . . . . . . . . . . . 1-4 Server Query RUNCMDs. . . . . . . . . . . . . . . . . 1-4 Server Control RUNCMDs. . . . . . . . . . . . . . . . 1-5 RUNCMD Security . . . . . . . . . . . . . . . . . . 1-6 RUNCMD Filtering. . . . . . . . . . . . . . . . . 1-6 Host Communications Options . . . . . . . . . . . . 1-7 Direct Host Communications. . . . . . . . . . . . 1-7 Collection Point Communications . . . . . . . . . 1-7 Advantages of Collection Point Communications . . 1-8 Alert Flow Control. . . . . . . . . . . . . . . . 1-8 Support for the Open NetView Interface. . . . . . . . . 1-8 CHAPTER 2 Installing and Upgrading NMA for NetView Overview Preparing NMA for NetView Installation Directories Choosing a Connection Topology Topologies That Support Direct Host Communications Example 1 Example 2 A Topology That Supports Collection Point Communications Setting Up the Required Server Hardware and Software Required Hardware Required Software Preparing the NetWare Server Enabling Bindery Emulation Loading and Configuring Btrieve Loading and Binding the LAN Adapter Loading for Direct Host Communications Loading and Binding for Collection Point Server Communications AUTOEXEC.NCF Examples Installing or Upgrading the NMA for NetView Software Preparing the Host PU Type 2.0 Definition in VTAM NetWare for SAA Connection to the Token Ring LAN Host Communications Link to the Collection Point Server Installation of NetView Code Points for NetWare CHAPTER 3 Configuring, Loading and Unloading NMA for NetView Starting NVCONFIG . . . . . . . . . . . . . . . . . . . . . . 3-1 Configuring NMA for NetView . . . . . . . . . . . . . . . . . 3-2 Configuring for Direct Host Communications. . . . . . . . 3-3 Parameter Descriptions for the Token Ring to Host Form . . . . . . . . . . . . . . 3-6 Configuring for NetView Collection Point Communications . 3-8 Enabling and Disabling Features . . . . . . . . . . . . . . . 3-10 Loading NMA for NetView . . . . . . . . . . . . . . . . . . . 3-11 Unloading NMA for NetView . . . . . . . . . . . . . . . . . . 3-11 Administering NMA for NetView Remotely. . . . . . . . . . . . 3-12 Configuring Alert Flow Control. . . . . . . . . . . . . . . . 3-12 How Alert Flow Control Works. . . . . . . . . . . . . . . 3-12 Editing the NVCMDS.DB File for Alert Flow Control . . . . 3-13 Checking for Failed LOAD or UNLOAD RUNCMDs. . . . . . . . . . 3-14 Removing the NMA for NetView Software . . . . . . . . . . . . 3-15 APPENDIX A Installing Code Points for NetWare Do You Need to Install? . . . . . . . . . . . . . . . . . . . A-1 Installation Overview . . . . . . . . . . . . . . . . . . . . A-1 Preparing for File Transfer (VM and MVS Installations). . . . A-2 Installing NetView Code Points in VM Systems. . . . . . . . . A-3 Installing NetView Code Points in MVS Systems . . . . . . . . A-5 APPENDIX B Using NetView RUNCMD Filtering How RUNCMD Filtering Works. . . . . . . . . . . . . . . . . . B-1 Editing the Sample RUNCMD Filter File . . . . . . . . . . . . B-2 Creating a RUNCMD Filter File . . . . . . . . . . . . . . . . B-3 Enabling RUNCMD Filtering . . . . . . . . . . . . . . . . . . B-4 RUNCMD Tables . . . . . . . . . . . . . . . . . . . . . . . . B-4 TRADEMARKS Novell, the N Design, NetWare, and Btrieve are registered trademarks and Internetwork Packet Exchange, IPX, NE2000, NetWare 3270 LAN Workstation, NetWare Directory Services, NetWare Loadable Module, NLM, ODI, and Transaction Tracking System are trademarks of Novell, Inc. Attachmate is a registered trademark of Attachmate Corporation. CompuServe is a registered trademark of CompuServe Incorporated. PostScript is a registered trademark of Adobe Systems Incorporated. 80386 and 80486 are trademarks of Intel Corporation. IBM, NetView, and PS/2 are registered trademarks and SAA and VTAM are trademarks of International Business Machines Corporation. NET/MASTER is a registered trademark of Systems Center. This guide describes o NetWare(R) Management Agent for NetView* 1.3B o How to install NMA for NetView 1.3B o How to use NMA for NetView 1.3B WHO SHOULD READ THIS GUIDE Read this guide if you want to: o Learn about NMA for NetView and its features o Learn about the new features in NMA for NetView 1.3B o Install NMA for NetView 1.3B o Configure or reconfigure NMA for NetView o Load or unload NMA for NetView o Remove NMA for NetView from a NetWare server CONTENT OVERVIEW Chapter 1, "About NMA for NetView," describes NMA for NetView, introduces the new features in NMA for NetView 1.3B, and describes the complete set of features provided by NMA for NetView 1.3B. Chapter 2, "Installing and Updating NMA for NetView," provides a procedure for setting up a NetWare server to run NMA for NetView. This chapter includes instructions for preparing the host for communications with NMA for NetView. Chapter 3, "Configuring, Loading, and Unloading NMA for NetView," provides separate procedures for tasks you may want to perform after you complete the installation procedure in Chapter 2. This chapter includes instructions for configuring, loading, or unloading NMA for NetView. Appendix A, "Installing NetView Code Points for NetWare," provides the procedure for installing NetView code points for NetWare. This procedure may not be required for your installation. Be sure to read the section entitled "Do You Need to Install?" in Appendix A. Appendix B, "Using NetWare RUNCMD Filtering," provides the procedure for disabling or filtering out selected RUNCMDs sent from the NetView operator to the server running NMA for NetView. CONVENTIONS This guide uses a variety of typographical conventions and special terminology. Typographic Conventions ----------------------- This document uses the following conventions. Angle bracketed words indicate names of variables. For example: o Press to display the menu. o The format is LOAD NLM NLMNAME= ARGS="" [Words in square brackets] Square bracketed words indicate optional characters or variables. For example: QUERY FILE RIGHTS [Username=] greater than (>) When the greater than symbol precedes a command,the symbol indicates that you must enter the command from the DOS prompt. For example: >server colon (:) When a colon precedes a command, the colon indicates that you must enter the command from the system console prompt, which is a colon. For example: :load install UPPERCASE Words appearing in UPPERCASE are file or path names. For example: DISK1.ZIP Terminology ----------- This guide uses the following terms: Select: Use the cursor keys to highlight the item and press . Enter: Type the indicated text and press . For example: Enter load nvinstal NOTE: When this term precedes a paragraph, the paragraph points out an item that may be of interest but is not vital to the operation of the product or to your safety. SUGGESTION: When this term precedes a paragraph, the paragraph provides hints, tips, or helpful information that may be useful, but not critical. IMPORTANT: When this term precedes a paragraph, the paragraph provides important information that you should read. This term is also used to highlight key concepts and facts. WARNING: When this term precedes a paragraph, the paragraph calls attention to a situation in which a critical or irreversible error can be made. NetWare v3.1x: This term refers to versions of NetWare later than NetWare v3.10 or earlier than NetWare 4.0, For example, NetWare v3.11 or v3.12. NetWare 4.x: This term refers to NetWare 4.0 or later. ADDITIONAL READING The publications described in this section provide additional information on products used with NMA for NetView. o NetWare Reference Guide for NetView Operators The NetWare Reference Guide for NetView Operators describes the alert messages and NetWare command set provided by NMA for NetView 1.3B and NetWare for SAA* 1.3B. This guide is provided in electronic form with NMA for NetView on NetWire(TM). A printed version of this guide (part number 100-001242-004) ships with NMA for NetView 1.3B. o NetWare for SAA v1.3 Rev. B Administration Guide The NetWare for SAA 1.3 Rev. B Administration Guide (part number 100-001166-003) describes the NetView support features in NetWare for SAA v1.3 Rev. B. o NetView Operation Primer (SC30-3363) from IBM o The Btrieve(R) Installation and Operation manual for your version of NetWare CHAPTER 1 About NMA for NetView This chapter describes o NetWare Management Agent (NMA) for NetView o The new features in NMA for NetView v1.3B o The complete NMA for NetView feature set IMPORTANT: NMA for NetView and NetWare for SAA provide similar support for NetView. Do not install NMA for NetView and NetWare for SAA in the same NetWare server. NOTE: NMA for NetView and NetWare for SAA servers are designed to support the NetView network management program from IBM*. These NetWare products will support any other network management program that is 100 percent compatible with NetView. The NET/MASTER* network management program from Sterling Software is an example of a program that is designed to be compatible with NetView. WHAT IS NMA FOR NETVIEW? NMA for NetView is a NetWare Loadable Module(TM)(NLM(TM)) that enables NetWare v3.1x and 4.x servers to participate in NetView network management. NetView is an IBM network management program that runs in the Virtual Machine (VM) and Multiple Virtual Storage (MVS) host environments. NetView is designed to be an enterprise-wide network management tool. IBM publishes specifications that describe how network product vendors can design products to communicate with NetView. Throughout this guide, a NetWare server that is running NMA for NetView is called an NMA for NetView server. The NMA for NetView server uses the following connections: o A connection to a NetWare local area network (LAN), which connects to workstations that use the file and print services provided by NetWare. o A connection that leads to a host computer that is running NetView The connection and communications between the workstations and the NetWare server. NMA for NetView provides for two types of connections between NMA for NetView and the NetView host computer. The physical connection between NMA for NetView and the NetView host is described later in this chapter. 1-1 NMA for NetView exchanges three types of messages with NetView: o Alerts o RUNCMDs o RUNCMD responses Alerts are messages that are sent from NMA for NetView to NetView. NMA for NetView translates selected NetWare server error and status messages into alerts. RUNCMDs are messages that are sent from NetView to the NMA for NetView server. NMA for NetView enables NetView to send commands that request NetWare server information or control some NetWare server features. RUNCMD responses are messages that are sent to NetView after a RUNCMD message has been processed. RUNCMD response messages contain information about the server or about the result of a server command. IMPORTANT: The messages that travel between NMA for NetView and the NetView host relate to the operation of the NetWare server. NMA for NetView does not monitor, report, or control the status of the NetWare LAN or NetWare LAN workstations. NMA for NetView does not respond to maintenance statistic requests from an IBM host. NetView operators use a terminal, or NetView console, to connect to the NetView program on the host. From the terminal, the NetView operator can view alert messages, send RUNCMD messages, and view RUNCMD response messages. For more information on NetView operation, see the NetView Operation Primer (SC30-3363) from IBM. NOTE: Third-party 3270 terminal emulation products, such as the NetWare 3270 LAN Workstation(TM) by Attachmate*, enable NetWare LAN workstations to emulate IBM terminals. NMA for NetView enables NetView communications between LAN workstations and the host. WHAT IS NEW IN VERSION 1.3B? NMA for NetView 1.3B provides the following new features: o Support for NetWare 4.0-or-later servers and support for additional RUNCMDs that apply to the NetWare 4.0-or-later server. o Security enabling and disabling. o RUNCMD and alert enabling and disabling. o Alert flow control in servers with direct host connections. These features are described with the complete set of NMA for NetView features in the next section. 1-2 NMA FOR NETVIEW FEATURES The principal features of NMA for NetView are o Alert generation o RUNCMD processing o RUNCMD security o RUNCMD filtering o Host communication options - Direct host communications - Collection point communications o Alert flow control o Support for the Open NetView Interface Alert Generation ---------------- NMA for NetView generate alerts for the following server processes: o Token ring adapters and drivers o Logical link control (LLC) protocol components of token ring drivers o The NetWare operating system and component services NOTE: The alerts for token ring adapters, drivers, and protocol components apply to the token ring components in the NMA for NetView server. NMA for NetView does not generate alerts for similar conditions in NetWare LAN workstations. These NetView alert messages are listed in the NetWare Reference Guide for NetView Operators. (For information on how to get this guide, see "Obtaining the Software and the Manuals" in Chapter 2.) Each message description in the NetWare Reference Guide for NetView Operators includes the NetView alert, a description of the alert cause, a suggested action, and the NetWare message (if one exists) that would appear on the server console. 1-3 SUGGESTION: If the NetView operator contacts you for help with an alert message, ask the operator to look it up in the NetWare Reference Guide for NetView Operators. If the operator still needs help, ask the operator to tell you the NetWare message that corresponds to the alert message. Because of differences between NetView and NetWare, the NetWare message is always different from the corresponding NetView message. (NetWare messages are described in the System Messages manuals for your version of NetWare.) RUNCMD Processing ----------------- If the RUNCMD processing feature is enabled, NMA for NetView processes two types of RUNCMDs: o Server query commands o Server control commands NMA for NetView allows you to control command processing with the following features: o RUNCMD security o RUNCMD filtering This section describes the actions these commands produce and the control features you can use. For detailed information on each RUNCMD and its syntax, see the NetWare Reference Guide for NetView Operators. Server Query RUNCMDs Server query RUNCMDs request information about server resources. These commands allow the NetView operator to query for o Server information such as the number of volumes on a server, the server's login status, and the server's internetwork address o Volume information such as the space allowed for a user, and the space used by a user o Directory information such as the space allowed for a directory, and a user's rights to the directory o File information o A user's usage of a volume and the remaining space allowed to the user o The version numbers of the Sequenced Packet Exchange (SPX) and Internetwork Packet Exchange(TM) (IPX(TM)) protocols 1-4 o The configuration of the SPX protocol o The status of the Transaction Tracking System(TM) (TTS) o Information on most (not all) server settings that can be set with NetWare SET command parameters Server Control Commands Server control commands allow a NetView operator to o Enable or disable server login, shut down a server, and broadcast a message to server users o Set server date and time o Set the volume space allowed to a user and remove a user from a volume o Set the space allowed to a directory; add or remove a directory trustee; and set the owner, creation date, and creation time for a directory o Add and remove file trustees and set the file owner, the creation date and time, the update date and time, the access date, and the archive date and time o Enable or disable the Transaction Tracking System (TTS) o Load and unload an NLM o Set most (not all) server control parameters that can also be set at the server console with the NetWare SET command 1-5 RUNCMD Security --------------- NMA for NetView provides an optional RUNCMD security feature for controlling NetView RUNCMD processing. If security is enabled, NMA for NetView checks each RUNCMD for a valid NetWare user ID with the appropriate status (see Table 1-1). Table 1-1 NetView RUNCMD Processing --------------------------------------------------------------- Server Command Type NetWare User ID Status Required for Processing -------------------------------------------------------------- Query File server console operator or supervisor on target NetWare v3.1x servers. Console operator status or security equivalence to the file server object on target NetWare 4.x servers. Control Supervisor rights on target NetWare v3.1x servers. Security equivalence to the file server object on target NetWare 4.x servers. ----------------------------------------------------------------- When a command message does not include an acceptable NetWare user ID, NetWare rejects the command and sends the following message to NetWare: Invalid operator When this message appears on the NetView console the variable displays the user ID that was rejected. NOTE: When RUNCMD security is enabled, the SUPERVISOR user ID is not an acceptable user ID for issuing RUNCMDs. NMA for NetView rejects RUNCMDs issued by the SUPERVISOR ID. RUNCMD Filtering ---------------- The RUNCMD filtering feature allows you to disable NetWare processing of select commands that may be sent by NetView operators. You can disable any number of RUNCMDs by listing them in a file that NMA for NetView reads when loading. When a NetView operator sends a command that has been disabled by RUNCMD filtering, NMA for NetView returns the following message to NetView: Cannot access this NetView Runcmd For more information, see Appendix B, "Using NetView RUNCMD Filtering." 1-6 Host Communications Options --------------------------- NMA for NetView provides two options for communicating with the host computer: o Direct host communications over a token ring LAN o Collection point communications via a NetWare for SAA server Direct Host Communications When using the direct host communications option, the NMA for NetView server must connect to a token ring LAN. The host computer must also connect, either directly or indirectly, to the same token ring LAN. Indirect connections are supported by a variety of host communications equipment, such as an IBM 3174 Attachment. Alerts and RUNCMD responses from the NMA for NetView server travel over the token ring LAN to the host. RUNCMDs from NetView travel over the token ring LAN to the NMA for NetView server. 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, Synchronous Data Link Control (SDLC), Qualified Logical Link Control (QLLC), or Ethernet connection to the host computer running NetView When NMA for NetView is ready to send an alert, it sends the alert over the NetWare LAN to the collection point server. The collection point server forwards the alert to NetView. When NetView is ready to send a RUNCMD to an NMA for NetView server, it sends the RUNCMD to the collection point server. The collection point server forwards the RUNCMD over the NetWare LAN to the NMA for NetView server. RUNCMD response messages from NMA for NetView follow the same communications path as do alert messages. 1-7 Advantages of Collection Point Communications The collection point server option on the NetWare for SAA server and the collection point communications option on any downstream NMA for NetView server can reduce the cost of NetView management in NetWare LANs with multiple servers. If your NetWare LAN does not use token ring cabling, for example, the collection point server option can eliminate the cost of a token ring adapter for each NMA for NetView server. The collection point server option also reduces the number of host connections required by NetWare servers. The host must allocate a physical unit (PU) for each NMA for NetView or NetWare for SAA server that is configured for direct host communications. NetView messages flow over a session between the PU and the system services control point (SSCP) host component. Servers that are configured for collection point communications use the SSCP-PU session allocated to the collection point server; they do not require an additional PU assignment. Alert Flow Control ------------------ You can insert parameters into the NVCMDS.DB file to configure NMA for NetView to monitor and control the flow of NetView alerts to the NetView console. If the rate exceeds a high-water mark over a given time interval, alerts are discarded until the rate slows to the low-water mark. You can define the high and low water marks and the time interval in the NVCMDS.DB file. See "Configuring Alert Flow Control" in Chapter 3. Support for the Open NetView Interface -------------------------------------- NMA for NetView can provide a connection between NetView and other applications that conform to the NetWare Open NetView interface. When an application uses the Open NetView interface, a server running NMA for NetView can o Receive alerts from the application and forward them to NetView o Receive commands from NetView and forward them to the application For more information on the NetView support provided by an application, refer to the documentation supplied with the application. 1-8 CHAPTER 2 Installing or Upgrading NMA for NetView OVERVIEW Installation of NMA for NetView consists of the following tasks: o Choose a connection topology (see this chapter) o Set up the required server hardware and software (see this chapter) o Prepare the NetWare 3.1x or 4.x 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) 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. Topologies That Support Direct Host Communications -------------------------------------------------- This section describes two examples of topologies that support direct host communications. Example 1 In this example, 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. 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 this example, 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. 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. 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 a 386 or 486 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 Sufficient random access memory (RAM) to support your version of NetWare and NMA for NetView. - For NetWare v3.1x a minimum of 6 MB RAM is required: 2 MB for NMA for NetView and a minimum of 4 MB for NetWare v3.1x. - For NetWare 4.x a minimum 10 MB of RAM is required: 2 MB for NMA for NetView and a minimum 8 MB for NetWare 4.x. 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 the adapter connected to each 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 1.3B. (this software) o NetWare v3.1x or NetWare 4.x, which includes: - Clib (CLIB.NLM) to support the library of C functions. - Btrieve v6.0 or later (BTRIEVE.NLM). This product manages the database that holds your NMA for NetView configuration parameters. NOTE: If Btrieve v6.10 or later is absent from your server, or if you have an earlier version installed, NMA for NetView automatically installs the correct version during the installation procedure. 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. 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 the adapter connected to each 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 scheduled for routine maintenance. PREPARING THE NETWARE SERVER Because all other software components must be loaded before you can run NMA for NetView, Novell recommends that you automate their loading by inserting the appropriate statements in your server's AUTOEXEC.NCF file. Prepare the NetWare v3.1x or 4.x server for the installation and operation of NMA for NetView as follows: 1. If you have not already done so, install NetWare. For instructions on installing and starting NetWare, refer to the installation and upgrade manual for your version of NetWare. 2. Start the server. For instructions on downing or restarting NetWare, see the NetWare DOWN and SERVER command descriptions in the system administration or supervising manual for your version of NetWare. 3. Start the NetWare INSTALL utility and select the option to edit the AUTOEXEC.NCF file. For instructions on editing the AUTOEXEC.NCF file, see the instructions on the INSTALL utility in the system administration or supervising manual for your version of NetWare. 4. If you are using NetWare 4.0 or later, edit the AUTOEXEC.NCF file to enable bindery emulation. Insert the line: set bindery context=[ou=.] o= For more information on setting the bindery context, see "Enabling Bindery Emulation" in this chapter. IMPORTANT: Insert this line only if you are using NetWare 4.0 or later! 5. Edit the AUTOEXEC.NCF file to load the CLIB.NLM and load and configure Btrieve. Insert the following lines: load clib load btrieve -P=4096 -F=20 -H=60 -L=20 -C -U=1 For more information on Btrieve and its parameters, see "Loading and Configuring Btrieve" in this chapter. 6. Edit the AUTOEXEC.NCF file to load and configure the communication protocol NLMs. o If setting up a server for direct host communications, insert a line similar to the following to load the token ring adapter: load token port=a20 int=2 node=12345678 name= For more information, see "Loading for Direct Host Communications" in this chapter. o If setting up a server for "collection point communications," insert lines similar to the following to load and bind the server's LAN adapter: load bind ipx to For more information, see "Loading and Binding for Collection Point Server Communications" in this chapter. SUGGESTION: See "AUTOEXEC.NCF Examples," later in this chapter, for examples of AUTOEXEC.NCF edits that support NMA for NetView. 7. (Optional) If you want to, edit the AUTOEXEC.NCF file to load NMA for NetView automatically when you start the server. Insert the following line in a location after the command lines described in Steps 4, 5, and 6: load NMANV 8. Restart the server. After completing the above edits, but before installing NMA for NetView, restart the server with the settings you specified in this procedure. Then see "Preparing the Host," later in this chapter. The rest of this section provides additional information on the steps to prepare the server. Enabling Bindery Emulation -------------------------- If you are running NetWare 4.0 or later, you must make sure bindery emulation is enabled for the server on which you have NMA for NetView installed. Enter the following command or make sure it exists in the server's AUTOEXEC.NCF file: set bindery context=[ou=.] o= Replace with the organizational unit (if any) to which this server is assigned in NetWare Directory Services(TM). You can specify several levels of organizational units. Replace with whatever organization name has been assigned in NetWare Directory Services. The following example sets the bindery context for a server in SNAGROUP container object. set bindery context=ou=snagroup.ou=sunnyvale.o=megabrite For more information on setting bindery emulation on NetWare 4.x servers, see the NetWare 4.x manual, "Supervising the Network." Loading and Configuring Btrieve ------------------------------- You must edit the AUTOEXEC.NCF file to load and configure Btrieve before you can install or operate NMA for NetView. NetWare Btrieve is a database management system that manages you NMA for NetView configuration parameters. First, insert the command to load the CLIB.NLM. Btrieve requires this NLM to be loaded. Next, enter the command to load Btrieve along with required configuration parameters. Table 2-2 lists the Btrieve configuration parameters and the settings that NMA for NetView requires. If you have changed the default settings in Btrieve, you may need to reconfigure Btrieve to support NMA for NetView. 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 1 Largest record size -D Largest page size -P 4096 Number of sessions -S Create files as transactional -I Logging of selected files -A ----------------------------------------------------------------- The following two commands entered in the AUTOEXEC.NCF file support, load, and configure Btrieve to support NMA for NetView: load clib load btrieve -P=4096 -F=20 -H=60 -L=20 -C -U=1 Loading and Binding the LAN Adapter ----------------------------------- If you plan to configure NMA for NetView for direct host communications, edit AUTOEXEC.NCF to 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, edit AUTOEXEC.NCF to load the LAN adapter driver and bind the driver to a communication 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 must bind the adapter driver to a communication protocol. The TOKEN.LAN adapter driver is supplied with NetWare. To load and configure the TOKEN.LAN adapter driver, enter a command in your AUTOEXEC.NCF file that is similar to the following: load token port=a20 int=2 node=12345678 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. 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 NVCONFIG. Loading and Binding for Collection Point Server Communications -------------------------------------------------------------- When NMA for NetView is configured for collection point server communications, you must load a LAN 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(TM) adapter driver and bind it to IPX: load ne2000 bind ipx to ne2000 For information on binding a LAN adapter driver to IPX, see NetWare Version 3.11 Installation, NetWare 3.12 Installation and Upgrade, or the NetWare 4.x manual Installation and Upgrade. NOTE: If you are installing NMA for NetView onto a NetWare v3.11 server, the INSTALL program automatically upgrades your LAN adapter drivers if it detects that your current drivers are too old to support NMA for NetView. AUTOEXEC.NCF Examples --------------------- This section contains examples of commands entered in AUTOEXEC.NCF files to prepare the NetWare server to support NMA for NetView. Example for Direct Host Communications -------------------------------------- The following command list is an example of the commands required to prepare a NetWare server for direct communications between NMA for NetView and the host: bindery context=ou=hostsrv.ou=legal.o=megabrite load clib load btrieve -P=4096 -F=20 -H=60 -L=20 -C -U=1 load token port=a20 int=2 node=12345678 name= When configured for direct host communications, NMA for NetView uses its own Systems Network Architecture (SNA) protocol stack to communicate with the host. No additional communication protocol NLMs are required for host communications. The LOAD TOKEN command loads the token ring driver for the LAN adapter. The NAME= parameter specifies the name for the token ring LAN adapter. The procedure for loading for direct host communications is described in "Loading for Direct Host Communications" earlier in this chapter. NOTE: The NetWare 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 server for communications with a collection point server: bindery context=ou=hostsrv.ou=legal.o=megabrite load clib load btrieve -P=4096 -F=20 -H=60 -L=20 -C -U=1 load bind to When configured for collection point communications, NMA for NetView uses 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 or routers. The LOAD and BIND commands load the driver for the LAN adapter and bind it to the communication protocol. The procedure to load and bind collection point communications is described in "Loading and Binding for Collection Point Server Communications" earlier in this chapter. INSTALLING OR UPGRADING THE NMA FOR NETVIEW SOFTWARE This section describes how to install the NMA for NetView software or upgrade it from version 1.3 to 1.3B. Upgrading from NMA for NetView v1.3 to 1.3B is the same as installing. The installation procedure automatically upgrades your software also. In addition, if you have upgraded from NetWare v3.1x to NetWare 4.x, the installation procedure automatically installs the files to make NMA for NetView compatible. IMPORTANT: If NetWare for SAA is installed in the NetWare 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 Server" earlier in this chapter describes which NLMs and drivers must be running. 2. If a version of NMA for NetView earler than 1.3 is installed, 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. Start the NetWare INSTALL utility. Enter :load install o If you are running NetWare v3.1x, the INSTALL utility displays the Installation Options menu. o If you are running NetWare 4.0 or later, the INSTALL utility displays the Select an Installation Method menu. Select "Maintenance/Selective Install" from the Select an Installation Method menu. The INSTALL utility then displays the Installation Options menu. 5. Select Product Options from the Installation Options menu. 6. When the Currently Installed Products window appears, press . The "Enter drive..." dialog box appears, prompting you to specify the location of your NMA for NetView Installation files. 7. Specify where the installation files are located. o If you inserted the "NMA for NetView 1.3B, Disk 1" in the server's drive A:, press ; otherwise, type the letter of the drive where you inserted the diskette and press . o If you copied the installation files to an installation directory in the DOS partition of your server's hard disk or in a network drive, enter the path to that directory. For example: >c:\disk1 IMPORTANT: You must specify DISK1 at the end of the above directory path to continue the installation. 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 item appears highlighted in the Currently Installed Products window. 10. Run NVCONFIG to configure NMA for NetView before running NMA for NetView. o If you want to run NVCONFIG immediately, highlight the NMA for NetView option in the Currently Installed Products and press . The NMA for NetView Communications Options menu appears. Configure the software as described in "Configuring NMA for NetView" in Chapter 3. 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 . 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 Connection 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 installed If installed for NetWare on the host NetView is 2.1 NetView is 2.1 or earlier or earlier ------------------------------------------------------------- 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. 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. Example 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. Example 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 )in the Panels Network Control Program (NCP) definition -------------------------------------------------------- Token Ring Not applicable Enter 4 for Configuration Destination this parameter. question 900 in Service the 3174 Access Customization Point (SAP) Panels Token Ring SAPADDR Enter 4 for Statement 940 Service definition this parameter. in the Access in the PORT Customization Point (SAP) statement Panels Block ID IDBLK statement IDBLK statement Not applicable; in the switched in the switched entry required PU definition PU definition PUID for IDNUM statement IDNUM statement Not applicable; Token Ring in the switched in the switched no entry Connection PU definition PU definition required ------------------------------------------------------- Record the host systems parameters as follows: 3a. Locate the column in Table 2-5 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.) NetWare for SAA --------------- When NMA for NetView is configured for collection point communications, you must install NetWare for SAA in the collection point server. To configure NetWare for SAA for host communications, see the NetWare for SAA 1.3B Administration Guide. 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. 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 1.3 Rev. B 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, or later, 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 1.3 or later server or NetWare for SAA 1.3 or later server. For additional information on code points and their installation, see Appendix A. CHAPTER 3 Configuring, Loading, and Unloading 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 Use NVCONFIG to enable or disable NetView alarm generation, RUNCMD processing, or RUNCMD security o Load NMA for NetView o Unload NMA for NetView o Administer NMA for NetView remotely o Configure alert flow control in servers with direct host connections o Check for failed LOAD or UNLOAD RUNCMDs o Remove the NMA for NetView software These are independent procedures--not subdivisions of a long procedure. STARTING NVCONFIG To start NVCONFIG: 1. If the server is not running, start the server and all prerequisite NLMs and drivers. "Preparing the NetWare Server" in Chapter 2 identifies the NLMs and drivers that must be running. 2. If NMA for NetView is running on your server, unload the program as described 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 Available Topics Menu, which includes the following options: Communications Options NetView Management 3-1 4. Do one of the following: o Select Communications Options to configure NMA for NetView for direct host or collection point server connections. If you select this option, NVCONFIG displays the Communications Options menu. See "Configuring NMA for NetView" later in this chapter. o Select NetView Management to enable or disable forwarding alerts to the NetView console, processing NetView RUNCMDs, and enforcing RUNCMD security. If you select this option, NVCONFIG displays the NetView Management menu. See "Enabling and Disabling Features," later in this chapter. 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 options. Each communications option requires specific hardware components and proper NetWare preparation. Configure NMA for NetView to use the option you planned to use when you followed the 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. 1. After starting NVCONFIG, select Communications Options in the Available Topics menu. 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-2 2. Select the type of communications you want to configure. o To configure for direct host communications, select NetView Host. NVCONFIG displays the Token Ring Connection to Host menu. See the following section, "Configuring for Direct Host Communications" later in this chapter for more information on configuring direct host connections. o To configure for collection point server communications, select NetView Collection Point. NVCONFIG displays the Connection to Collection Point box. See "Configuring for NetView Collection Point Communications" later in this chapter for more information on configuring collection point server connections. 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. 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 "Parameter Descriptions for the Token Ring to Host Form" later in this chapter. 3-3 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 --------------------------------------------------------------- Server and LAN Status Value Communication Parameters --------------------------------------------------------------- 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 --------------------------------------------------------------- 2. If NVCONFIG is not running, start NVCONFIG as described under "Starting NVCONFIG" at the beginning of this chapter and select Communications Options. 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 . The Token Ring Connection to Host configuration form appears, which includes the following items: 3-4 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 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 . See "Parameter Descriptions for the Token Ring Connection to Host Form," for more more information on each parameter. 5. When all host communication parameters are set, press to exit the Token Ring Connection to Host form. 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 . 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 to clear the confirmation message. 8. Press 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. 3-5 Parameter Descriptions for the Token Ring Connection to Host Form The Token Ring Connections to Host form lists nine 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. o 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. o 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. o Maximum Frame Size to Transmit Inbound. This parameter sets the frame size for transmissions from NMA for NetView to the host. Press to display a window with the following items: 265 521 1033 2042 4015 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. 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-6 IMPORTANT: If you change 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 o Peripheral Node Control Point Name. The peripheral node control point (PCNP) 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 you do not enter a PNCP name, NMA for NetView sends the default value, CPNAME. o 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 PUID parameter must match the value that follows the IDNUM= statement in the switched PU definition. - When the server communicates through a 3174 controller, the PUID parameter is ignored; therefore, no entry is required. o Token Ring Adapter Type. In this field, specify the type of adapter your server is using for the host connection. Press 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.) 3-7 o 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 in Chapter 2 provides additional information that the host systems programmer can use to locate the correct values. o 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-5 in Chapter 2 provides additional information that the host systems programmer can use to locate the correct value. o 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 value. 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. 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 3-8 For information on setting these parameters within NetWare for SAA, see the NetWare for SAA 1.3 Rev. B 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 and select Communications Options. 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 . 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 and 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 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 . 5. In the Save Changes confirmation box, use the arrow keys to select Yes; then press . 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 to clear the confirmation message. 3-9 7. Press again to exit the Configuration Options menu and NVCONFIG. The configuration process is now complete; NMA for NetView is ready for loading. IMPORTANT: You must 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 "Preparing the NetWare Server" in Chapter 2. ENABLING AND DISABLING FEATURES You can use the NetView Management menu to enable or disable the NMA for NetView Alert forwarding, RUNCMD processing, or RUNCMD Security features. 1. Select the NetView Management option in the Available Topics menu. NVCONFIG displays the NetView Management menu, which includes the following items: Generate Alerts Yes/No Process RunCmds Yes/No NetView Security Yes/No 2. Select an option (Generate Alerts, Process Rumds, or NetView Security); then type Y to enable the option or N to disable the option. Use these options as follows: o Generate Alerts: Use this option to enable or disable the generation of NetView alerts by this server. o Process RunCmds: Use this option to enable or disable processing of NetView RUNCMDs addressed to this server. o NetView Security: Use this option to control RUNCMD processing by the server when the Process RunCmds option is enabled. If the NetView Security option is enabled, all NetView RUNCMDs must contain a valid NetWare server user ID with appropriate privileges: - Supervisor-equivalent privileges or server console operator status on a NetWare v3.1x server - Security equivalence to the file server object or server console operator status on a NetWare 4.x server 3-10 The SUPERVISOR user ID is not valid. If a command does not contain a valid server user ID, the command is not processed and a message is returned to NetView. If the NetView Security option is disabled, the server processes all NetView RUNCMDs addressed to the server and ignores any user ID included within RUNCMDs. 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 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 "Preparing the NetWare Server" in Chapter 2. 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. 3-11 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 or the NetWare 4.x manual, Supervising the Network for more information on running RCONSOLE. CONFIGURING ALERT FLOW CONTROL On NMA for NetView servers configured for direct host connections, you can configure NMA for NetView to limit the number of alerts that it and downstream workstations forward to the NetView host over a specified period of time. How Alert Flow Control Works ---------------------------- If the number of NetView alerts generated by or forwarded to the NMA for NetView server over a specified number of minutes exceeds its high-water mark, NMA for NetView stops forwarding alerts to the NetView host. NMA for NetView then sends one of the following alerts to the NetView host: File Server Error Limit Reached: Server Configuration or Configurable Capacity Limit Reached: Server configuration Once the number of alerts reaches or drops below a low-water mark during the specified number of minutes, NMA for NetView resumes alert forwarding to the NetView host. IMPORTANT: NMA for NetView supports alert flow control only from NMA for NetView servers with direct host connections. It does not support alert flow control from end point servers. 3-12 Editing the NVCMDS.DB File for Alert Flow Control ------------------------------------------------- To implement alert flow control, locate and edit the NVCMDS.DB ASCII file on the NMA for NetView server. Insert configuration parameters that control the flow of alerts to the NetView host from an NMA for NetView server configured for direct host communications. 1. Locate the NVCMDS.DB file. If you have not already copied NVCMDS.DB to the SYS:\SYSTEM\COMMEXEC directory on the server running NMA for NetView, you will find it on the NMA for NetView 1.3B, Disk 3 diskette in the DATABASE directory. 2. Using a text editor, open the NVCMDS.DB file on the NMA for NetView server. Make sure the text editor is configured not to insert formatting or other non-ASCII characters. 3. Insert the following lines: @CONFIG ALERT THRESHOLDINTERVAL @CONFIG ALERT HIGHWATERMARK @CONFIG ALERT LOWWATERMARK Replace with a specified period of time, in minutes, that you want the number of NetView alerts to be measured over. The default value is 100. Replace with the maximum number of NetView alerts allowed in the THRESHOLDINTERVAL time period. If this number is exceeded, NMA for NetView stops forwarding alerts to the NetView host. The default value is 1000. Replace with the number of alerts at which to resume alert forwarding to the NetView console. NMA for NetView will resume forwarding alerts once the number of alerts in the period of time specified by THRESHOLDINTERVAL drops to or below this number. The default value is 100. NOTE: The NVCMDS.DB file may contain both RUNCMD-filtering statements (described in Appendix B, "Using NetView RUNCMD Filtering") and NetView support configuration parameters. The RUNCMD-filtering statements and configuration parameters need not appear in any special order. 4. Copy NVCMDS.DB to the SYS:\SYSTEM\COMMEXEC directory. After you finish your edit, make sure your edited NVCMDS.DB file is located in the SYS:\SYSTEM\COMMEXEC directory of the NMA for NetView server you want to configure. 5. Restart NMA for NetView. 3-13 Example The following lines were inserted into NVCMDS.DB on an NMA for NetView server configured for direct host communications to stop forwarding alerts to the NetView host if it generates or receives more than 500 alerts per five-minute interval. NMA for NetView will not resume forwarding alerts to the NetView host until the rate of incoming and generated alerts drops to or below 50 per five-minute interval. @CONFIG ALERT THRESHOLDINTERVAL 5 @CONFIG ALERT HIGHWATERMARK 500 @CONFIG ALERT LOWWATERMARK 50 NOTE: This solution limits the flow of NetView alerts from any specific NetWare server with direct host connection, and from all end point servers. However, this solution does not limit the collective flow of NetView alerts from all NetWare servers, since each server independently detects and reports LAN errors (such as token ring beaconing). You can use other methods to limit the collective flow. For example, in the case of token ring beaconing, you can use Novell's token ring drivers to minimize problems because these drivers do not report duplicate alerts to network management modules. CHECKING FOR FAILED LOAD OR UNLOAD RUNCMDS If you send a LOAD NLM or UNLOAD NLM RUNCMD from the NetView console, and the RUNCMD fails, NMA for NetView does not return a failure message to NetView. Instead, NMA for NetView generates an NMA Load Module screen at the NMA for NetView server and displays either an error message or a prompt for missing parameters. o If, for example, you issue a LOAD NLM RUNCMD with an incomplete set of parameters from the NetView console, NMA for NetView does not execute your LOAD command. Instead it generates the NMA Load Module screen at the NMA for NetView server with a prompt for the missing parameters. o If you issue an UNLOAD NLM RUNCMD that fails because other NLMs may have to be unloaded before it, NMA for NetView generates the NMA Load Module screen with an error message. If you suspect a LOAD NLM or UNLOAD NLM RUNCMD failed, do the following: 1. Go the the NMA for NetView server and press to list the available control screens. If a LOAD or UNLOAD NLM RUNCMD issued from the NetView console has failed, you will see an option for the NMA Load Module screen. 3-14 2. Select the NMA Load Module option to see the error message or prompt. NOTE: The NMA Load Module screen is present on the server only if the LOAD or UNLOAD RUNCMD has failed. REMOVING THE NMA FOR NETVIEW SOFTWARE To remove NMA for NetView v1.3 or later, 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. 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. By entering :load install 2. Select Product Options from the Installation Options menu. 3. Use the arrow keys to select NMA for NetView from the Currently Installed Products listing. 4. Press . 5. When the Uninstall NMANV prompt appears, select Yes to confirm the removal of NMA for NetView. 3-15 APPENDIX A Installing Code Points for NetWare The code points allow NetView to display additional information about alerts that are received from NMA for NetView. This appendix describes o How to determine whether you need to install NetView code points o An overview of the installation procedure o How to install NetView code points on a Virtual Machine (VM) system o How to install NetView code points on an Multiple Virtual Storage (MVS) system DO YOU NEED TO INSTALL? Beginning with NetView v2.1, all versions of NetView contain all the code points required to display NetWare alerts. Contact a NetView operator or your systems programmer and ask for the version number of NetView. If the host is running NetView v2.1 or later, you do not need to install code points. If the host is running an older version of NetView (before v2.1), you might need to install additional code points as described later in this appendix. You do not need to install the code points if the code points for NMA for NetView v1.2 or NetWare for SAA v1.2 are already installed on the NetView host. Once the code points are installed for one NetWare for SAA v1.2-and-later server, the installed code points support all NetWare for SAA v1.2-and-later servers. INSTALLATION OVERVIEW This section provides a general overview of the installation process. Detailed procedures for the VM and MVS host systems appear later in this appendix. The installation procedure in this chapter requires the following hardware and software components: o NetView software installed at the NetView host. o NetWare for SAA or an equivalent product that enables communications and file transfers between a LAN workstation PC and the host computer installed and loaded on the server. o 3270 terminal emulation software with file transfer capabilities installed on a LAN workstation (such as, the NetWare 3270 LAN Workstation for DOS by Attachmate). A-1 o A cabling connection between NetWare for SAA and the NetView host. o A cabling connection between NetWare for SAA and the PC that is running the 3270 terminal emulation software. To install the code point messages, you must perform the following tasks: o Task 1. Prepare to transfer files to the host: - Install NetWare for SAA (or a product with similar features) so that you can access the host from a workstation on the NetWare LAN. - Using 3270 terminal emulation software with file transfer capabilities, establish a host session from the LAN workstation and access the NetView RUN disk. o Task 2. Install the code point messages: - Using the 3270 terminal emulation software on the LAN Workstation, transfer the code point files from the NMA for NetView 1.3B, Disk 3 diskette to the NetView RUN disk. - Using the NetWare 3270 emulation software on a LAN workstation, compile the code point files. - Using a NetView console or NetView on the LAN workstation running the 3270 emulation software, edit the NetView startup command file. - Using a NetView console or NetView on the LAN workstation running the 3270 emulation software, restart NetView and set the NetView recording and viewing filters. Detailed instructions for these tasks appear in the following sections. PREPARING FOR FILE TRANSFER (VM AND MVS INSTALLATIONS) To prepare for transferring code point files to the host, follow these steps: 1. Install NetWare for SAA (or a product with similar features) in a NetWare server so that you can access the host from a workstation on the NetWare LAN. 2. Locate the code point files on NMA for NetView 1.3B, Disk 3. The files that you need are located in the CP directory on this diskette. Instructions for creating this diskette appear under "Preparing the Installation Diskettes" in Chapter 2. A-2 3. On a LAN workstation, start up a 3270 emulation package with file transfer software capabilities. 4. Establish a host session on the workstation. You must use a workstation with a 3.5-inch floppy diskette drive. To establish the host session, you can use NetWare for SAA on the server and 3270 terminal emulation software with file transfer capability on the workstation For additional information on using your 3270 terminal emulation software and on transferring files, consult the documentation for the products you are using. INSTALLING NETVIEW CODE POINTS IN VM SYSTEMS Before starting the procedures in this section, complete the procedures in the preceding section, "Preparing for File Transfer (VM and MVS Installations)." IMPORTANT: The following procedure is based on recommendations in the NetView Customization Guide (IBM publication SC31-6016). Novell recommends that you review the information on creating user-defined generic code points before attempting to install the code points. To continue installing the NetView code points, complete the following steps: 1. While running a host session from a LAN workstation running 3270 terminal emulation software, log on to MAINT. If you do not know how to log on to MAINT, contact your host systems programmer. 2. Access the NetView RUN disk by entering the following command: ACCESS 334 A 3. Using file transfer software on the workstation, transfer the code point files to the NetView RUN disk. When transferring the files, use the ASCII, CRLF, and fixed record format options. If you are using the SEND.EXE program, for example, enter the following at the DOS prompt (>): SEND BNJ81UTB.NCC BNJ81UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ82UTB.NCC BNJ82UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ92UTB.NCC BNJ92UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ93UTB.NCC BNJ93UTB NCCFLST A (ASCII CRLF RECFM F A-3 SEND BNJ94UTB.NCC BNJ94UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ95UTB.NCC BNJ95UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ96UTB.NCC BNJ96UTB NCCFLST A (ASCII CRLF RECFM F 4. While running a host session from the workstation under 3270 emulation, compile the transferred files on the host by entering CNMSVM07 NUMBER=81 NETLNK=NOVELL CNMSVM07 NUMBER=82 NETLNK=NOVELL CNMSVM07 NUMBER=92 NETLNK=NOVELL CNMSVM07 NUMBER=93 NETLNK=NOVELL CNMSVM07 NUMBER=94 NETLNK=NOVELL CNMSVM07 NUMBER=95 NETLNK=NOVELL CNMSVM07 NUMBER=96 NETLNK=NOVELL 5. While running a host session from the workstation under 3270 emulation, open the NetView startup command file for editing by entering the following command: XEDIT NETSTRT GCS 6. Within the NetView startup file, locate the GLOBAL command and insert the word NOVELL immediately after the word LOADLIB. This step includes the Novell library in the list of NetView libraries that are loaded at startup. The modified GLOBAL command will look like the following: `GLOBAL LOADLIB NOVELL PROPMX USER NCCF STATMON NLDM NPDA' 7. Log on to a NetView console and shut down NetView by entering the following NetView command: CLOSE IMMED WARNING: This command brings down NetView. To avoid untimely interruption of NetView services, consider performing this step during a scheduled maintenance period. 8. When NetView has completed shutdown, log on to the NetView virtual machine. Then start up NetView by entering the following VM command: CP IPL GCS A-4 9. While NetView is starting up, check the startup messages to make sure that they include BNJ090I NETVIEW USER CODE POINT TABLE BNJ92UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ93UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ94UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ95UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ96UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ81UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ82UTB IS AVAILABLE The preceding messages indicate that the code point files for NetWare are available. If these messages are directed to another console, they will not appear. 10. Disconnect from the NetView virtual machine by entering the following command: #CP DISC 11. Log on to NetView. When NetView main menu appears, select NPDA (Network Problem Determination Application) by entering NPDA 12. From the NetView NPDA prompt, set the NetView recording and viewing filters by entering the following NetView commands: srf arec pass e paff srf arec pass e temp srf arec pass e impd svf pass e paff svf pass e temp svf pass e impd NOTE: To display NetWare messages, the recording and viewing filters must be set each time NetView is started. To simplify NetView startup, enter these commands in a CLIST file. INSTALLING NETVIEW CODE POINTS IN MVS SYSTEMS Before starting the procedures in this section, complete the procedures in "Preparing for File Transfer (VM and MVS Installations)" earlier in this appendix. IMPORTANT: The following procedure is based on recommendations in the NetView Customization Guide (IBM publication SC31-6016). Novell recommends that you review the information on creating user-defined generic code points before attempting to install the code points. A-5 To continue installing the NetView code points, follow these steps: 1. While running a host session from the workstation running 3270 terminal emulation software, log on with a Time Sharing Option (TSO) user ID that has sufficient access rights to create or update a system data set such as SYS1.xxxx. 2. Using this 3270 terminal emulation host session and the Interactive System Productivity Facility (ISPF), allocate a partitioned data set (PDS) to contain the code point files. Give the data set a name like SYS2.NTVW.CODE.POINTS. Make sure to set the allocation parameters to the following values: o LRECL = 80 o RECFM = FB o Directory blocks should be 5 o Primary allocation should be at least one cylinder--or the equivalent in fixed-block architecture (FBA) blocks o Secondary allocation should be at least one cylinder or the equivalent in FBA blocks 3. Exit ISPF by entering =X 4. Using the file transfer software on the workstation running 3270 terminal emulation software, transfer the INSTALL.JCL file and the code point files to the host. When transferring the files, use the ASCII and CRLF options. If you are using the SEND.EXE program, for example, enter the following at the DOS prompt (>): SEND BNJ92UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ92UTB)' ASCII CRLF SEND BNJ93UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ93UTB)' ASCII CRLF SEND BNJ94UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ94UTB)' ASCII CRLF SEND BNJ95UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ95UTB)' ASCII CRLF SEND BNJ96UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ96UTB)' ASCII CRLF A-6 SEND BNJ81UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ81UTB)' ASCII CRLF SEND BNJ82UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ82UTB)' ASCII CRLF SEND INSTALL.JCL 'SYS2.NTVW.CODE.POINTS(INSTALL)' ASCII CRLF 5. From a host terminal or a NetWare 3270 LAN Workstation host session and the ISPF editor, open the member 'SYS2.NTVW.CODE.POINTS(INSTALL)' 6. Follow the directions inside the job control language (JCL) listing. These instructions appear under the label TO EXECUTE THIS JCL: Refer to Example A-1 at the end of this appendix for a sample JCL listing for a code point installation. For additional information on using listings similar to this sample, refer to the Network Program Products Samples book (SC30-3352) from IBM. 7. Submit the job. After successful completion of this job, the code points load library member should be installed correctly. 8. Log on to a NetView console and shut down NetView by entering the following NetView command: CLOSE IMMED WARNING: This command brings down NetView. To avoid untimely interruption of NetView services, consider performing this step during a scheduled system maintenance period. 9. At the primary MVS operator console, start NetView by entering the following command: S CNMPROC 10. While NetView is starting up, check the startup messages to make sure that they include BNJ090I NETVIEW USER CODE POINT TABLE BNJ92UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ93UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ94UTB IS AVAILABLE A-7 BNJ090I NETVIEW USER CODE POINT TABLE BNJ95UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ96UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ81UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ82UTB IS AVAILABLE The preceding messages indicate that the code point files for NetWare are available. If these messages are directed to another console, they will not appear. 11. Log on to NetView. When the NetView main menu appears, select NPDA (Network Problem Determination Application) by entering NPDA 12. From NPDA prompt, set the NetView recording and viewing filters by entering the following NetView commands: srf arec pass e paff srf arec pass e temp srf arec pass e impd svf pass e paff svf pass e temp svf pass e impd NOTE: To display NetWare messages, the recording and viewing filters must be set each time NetView is started. To simplify NetView startup, enter these commands in a CLIST file. A-8 Example A-1 Code Points Installation JCL _________________________________________________________________ // JOB // ***************************************************************** //* * //*DESCRIPTION: PARSE, ASSEMBLE, AND LINKEDIT USER DEFINED CODE * //* POINT TABLES. * //* * //* NOTE ===> THIS JCL ASSUMES: * //* * //* 1) THE CODE POINT SOURCE IS CONTAINED IN A * //* SINGLE LIBRARY * //* 2) THE MEMBER NAMES ARE FORMATED ASD AAABBCCC * //* WHERE AAA = BNJ * //* BB = CODE POINT TABLE NUMBER * //* CCC = UTB (MODIFIABLE BY SYMBOLIC * //* VARIABLE "NAME") * //* * //* TO EXECUTE THIS JCL: * //* 1.) PUT YOUR OWN JOB CARD ON THE JOB * //* 2.) MODIFY SYMBOLIC VARIABLE "NETLNK" TO POINT TO THE * //* NETVIEW LOAD LIBRARY YOU WANT THE CODE POINTS * //* LINKED INTO * //* 3.) MODIFY SYMBOLIC VARIABLE "USERLIB" TO POINT TO THE * //* SOURCE LIBRARY NAME CONTAINING THE CODE POINTS. * //* * //*************************************************************** //CNMUSER PROC NUMBER=, // NAME=UTB, // NETLNK='CNM.USERLNK', ** USER CODE POINT LIBRARY // REG=1, ** REGION SIZE IN MEG // SOUTA='*', ** DEFAULT PRINTED OUTPUT CLASS // UNIT=SYSDA, ** DEVICE TYPE FOR DASD // USERLIB='SYS2.NTVW.CODE.POINTS', ** CODE POINTS SOURCE // PS=3, ** PRIMARY CYLINDER ALLOCATION // SS=1 ** SECONDARY CYLINDER ALLOCATION // ***************************************************************** //* VERIFY USER TABLE INPUT // //*************************************************************** //PARSE EXEC PGM=BNJUSTBL,REGION=®.M, // PARM='&NUMBER' //STEPLIB DD DSN=SYS1.NPDALIB,DISP=SHR //INTABLE DD DSN=&USERLIB(BNJ&NUMBER&NAME),DISP=SHR //OUTTABLE DD DSN=&&OUTDCB,DISP=(NEW,PASS),UNIT=&UNIT, // SPACE=(CYL,(&PS,&SS)), // DCB=(DSORG=PS,LRECL=80,BLKSIZE=3120,RECFM=FB) //SYSPRINT DD SYSOUT=&SOUTA //SYSUDUMP DD DUMMY //SYSUT1 DD UNIT=&UNIT,SPACE=(CYL,(&PS,&SS)) ***************************************************************** A-9 Example A-1 (continued) Code Points Installation JCL _________________________________________________________________ // //* ASSEMBLE STEP // ***************************************************************** //ASM EXEC PGM=IFOX00,PARM='LOAD,NODECK,OBJECT', // REGION=®.M,COND=(4,LT) //SYSPRINT DD SYSOUT=&SOUTA //SYSLIB DD DSNAME=SYS1.MACLIB,DISP=SHR //SYSUT1 DD UNIT=&UNIT,SPACE=(CYL,(1,1)) //SYSUT2 DD UNIT=&UNIT,SPACE=(CYL,(1,1)) //SYSUT3 DD UNIT=&UNIT,SPACE=(CYL,(1,1)) //SYSGO DD DSNAME=&&SYSGO,DISP=(NEW,PASS),UNIT=&UNIT, // SPACE=(CYL,(&PS,&SS)), // DCB=(DSORG=PS,LRECL=80,BLKSIZE=3120,RECFM=FB) //SYSIN DD DSN=*.PARSE.OUTTABLE, // DISP=(OLD,DELETE) // ***************************************************************** //* LINKEDIT STEP // ***************************************************************** //LINK EXEC PGM=IEWL, // PARM='XREF,LET,LIST,SIZE=(512K,128K),NCAL,REUS', // REGION=®.M,COND=(4,LT) //SYSPRINT DD SYSOUT=&SOUTA //SYSUT1 DD SPACE=(CYL,(1,1)),DISP=(NEW,PASS),UNIT=&UNIT //SYSLMOD DD DSN=&NETLNK(BNJ&NUMBER&NAME), // DISP=SHR //SYSLIN DD DSNAME=&&SYSGO,DISP=(OLD,DELETE) // PEND //STEP1 EXEC PROC=CNMUSER,NUMBER=92 //STEP2 EXEC PROC=CNMUSER,NUMBER=93 //STEP3 EXEC PROC=CNMUSER,NUMBER=94 //STEP4 EXEC PROC=CNMUSER,NUMBER=95 //STEP5 EXEC PROC=CNMUSER,NUMBER=96 //STEP6 EXEC PROC=CNMUSER,NUMBER=81 //STEP7 EXEC PROC=CNMUSER,NUMBER=82 _________________________________________________________________ A-10 APPENDIX B: Using NetView RUNCMD Filtering The NetView RUNCMD filtering feature allows you to disable NetWare processing of select RUNCMDs that may be sent by NetView operators. NetView RUNCMD filtering is an extension of the NetView support features described in Chapter 1. To prepare for RUNCMD filtering, you need to edit the sample RUNCMD filter file or create a new RUNCMD filter file. To enable the RUNCMD filtering feature, you need to install the RUNCMD filter file and restart NMA for NetView. IMPORTANT: If a RUNCMD filter file is not installed on an NMA for NetView server, or if NMA for NetView is not restarted after the RUNCMD filter file is installed, NMA for NetView processes all NetView RUNCMDs that conform to the RUNCMD security requirements. This appendix describes how RUNCMD filtering works and how to o Edit the sample RUNCMD filter file o Create a new RUNCMD filter file o Enable RUNCMD filtering This appendix also lists the RUNCMDs that NetView operators can send to NetWare servers. HOW RUNCMD FILTERING WORKS After RUNCMD filtering is enabled, NMA for NetView may apply the following two levels of security to each NetView RUNCMD it receives. o NMA for NetView first examines the user ID in the NetView RUNCMD. If the user ID has the proper status, NMA for NetView continues to process the RUNCMD. o NMA for NetView checks its internal table to see if the RUNCMD is disabled by RUNCMD filtering. If the RUNCMD is not disabled, NMA for NetView processes the RUNCMD. When a NetView operator sends a RUNCMD that has been disabled by RUNCMD filtering, NMA for NetView responds as follows: o If the RUNCMD does not include an attribute parameter, or if it includes a single attribute parameter that has been disabled, NMA for NetView rejects the RUNCMD and sends the following message to the NetView operator: Cannot execute this NetView Runcmd o If the RUNCMD includes multiple attribute parameters of which some are enabled and some are disabled, NMA for NetView processes all enabled parameters and ignores all disabled parameters. B-1 EDITING THE SAMPLE RUNCMD FILTER FILE The sample RUNCMD filter file is an ASCII text file that lists all the RUNCMDs NetView operators can send to NetWare servers. Initially, this file does not disable NetWare processing for any RUNCMDs. You can edit this file to disable processing for any or all RUNCMDs. To edit the filter file, use the following procedure: 1. Use a text editor or a word processor to open the file named NVCMDS.DB. This file is on NMA for NetView 1.3B, Disk 3 in the DATABASE directory. This file is not automatically copied to the server during the installation process. IMPORTANT: The text editor for word processor must be capable of editing an ASCII text file. Do not use programs that embed control characters into saved files for special effects such as bold and underline. Example B-1 lists some of the statements from the sample RUNCMD filter file. Example B-1 Sample RUNCMD Filter File Entries ----------------------------------------------------------------- rem The NetView Run Command Filtering File ... ;QUERY SPX VERSION ;QUERY SPX CONFIG ;QUERY SPX VERSION ----------------------------------------------------------------- The statements in the RUNCMD filter file conform to the following rules: o Each line in the file is a separate statement. o RUNCMD statements disable a RUNCMD and must contain two or three parameters in the form: In the third line of Example B-1, is QUERY, is SPX, and is VERSION. The action parameter defines the function to be performed, and the resource parameter defines the resource affected by the action. The attribute parameter defines the resource attribute the RUNCMD affects. The action and resource parameters are required. When a RUNCMD has one or more attribute parameters, you must enter one attribute parameter. B-2 The parameters for all RUNCMDs are listed in "RUNCMD Tables" later in this appendix. o Each RUNCMD statement can disable one attribute parameter for a RUNCMD. If a RUNCMD has multiple attribute parameters, you must enter a separate RUNCMD statement for each attribute parameter you want to disable. o The letters in each statement may be entered in uppercase or lowercase. For example, REM is equivalent to rem, Rem, and ReM. o When a statement begins with REM or a semicolon (;), the statement is a comment. NMA for NetView ignores comments. Comments affect the RUNCMD statements as follows: When a RUNCMD statement is preceded by REM or a semicolon, the statement is ignored and the RUNCMD remains enabled. When a RUNCMD statement is not preceded by REM or a semicolon, the RUNCMD is disabled. o RUNCMD parameters may be separated by space or tab characters. 2. Disable each RUNCMD you want to disable by removing any comment characters (REM or semicolon) at the beginning of the RUNCMD statement. 3. If you want to enable a disabled RUNCMD, make the RUNCMD statement a comment (using REM or a semicolon) or delete the RUNCMD statement. 4. Save the ASCII file. IMPORTANT: The ASCII file must be named NVCMDS.DB. CREATING A RUNCMD FILTER FILE A RUNCMD filter file is an ASCII text file that lists all the RUNCMDs you want to disable. To create a RUNCMD filter file, use the following procedure: 1. Use a text editor or a word processor to create a new file named NVCMDS.DB. IMPORTANT: The text editor or word processor must be capable of editing an ASCII text file. Do not use programs that embed control characters into saved files for special effects such as bold and underline. B-3 2. In the ASCII file, add RUNCMD and comment statements. The RUNCMD and comment statements operate as described in Step 1 of the preceding section, "Editing the Sample RUNCMD Filter File." 3. Save the ASCII file. IMPORTANT: The ASCII file must be named NVCMDS.DB. ENABLING RUNCMD FILTERING To enable RUNCMD filtering, edit or create a RUNCMD filter file, and then use the following procedure: 1. Place a copy of the NVCMDS.DB RUNCMD filter file in the server's SYS:\SYSTEM\COMMEXEC directory. 2. Restart NMA for NetView. During initialization, NMA for NetView examines each line of the RUNCMD filter file. Comment lines are ignored. Valid entries are registered in an internal table within NMA for NetView. If a RUNCMD line contains an error, NMA for NetView displays the following message on the NetWare system console: Invalid NetView RunCmd entry: xxxxxxxxxxxxxx IMPORTANT: Invalid entries are ignored. Invalid entries do not disable the RUNCMD you intend to disable. RUNCMD TABLES The tables in this section list RUNCMDs that the NetView operator can send to NetWare. Table B-1 lists these RUNCMDs according to the action they perform. Table B-2 lists RUNCMDs according to the resource upon which an action is performed. For more information on the listed RUNCMDs, see Chapter 3 of the NetWare Reference Guide for NetView Operators. IMPORTANT: The RUNCMDs in the following tables include all parameters that the NetView operator can send to NetWare. When you enter a RUNCMD statement in a RUNCMD filter file, enter only the action, resource, and attribute parameter. When you enter an attribute parameter, do not include the equal symbol (=) or any characters enclosed in brackets (< >) that appear in these tables. WARNING: The UserName parameter in the following RUNCMDs does not support group names. When the phrase (NetWare 4.x) appears in the Action column, the command and all its parameters can be used only with servers that run NetWare 4.0 and later. These commands do not work with NetWare 3.1x servers. B-4 Table B-1 NetWare RUNCMDs Sorted by Action ------------------------------------------------------------------ Action Resource Attribute Resource Command Parameter Qualifier Qualifier ------------------------------------------------------------------ Add Directory Trustee Path= UserName= Rights= [A][C][E][F] [M][R][S][W] Add File Trustee Path= UserName= Rights= [A][C][E][F] [M][R][S][W] Add Volume Trustee VolName= UserName= Rights= [A][C][E][F] [M][R][S][W] Broadcast Server Msg= "" UserName= Disable Server Login Disable TTS Down Server [Opts= [0][1]] Enable Server Login Enable TTS Get Server Parm= (NetWare "" 4.x) Load NLM NLMName= [Args= ""] Query Directory Path= Query Directory Rights Path= UserName= Query Directory SpaceAllowed Path= B-5 Table B-1 (continued) NetWare RUNCMDs Sorted by Action ------------------------------------------------------------------ Action Resource Attribute Resource Command Parameter Qualifier Qualifier ------------------------------------------------------------------ Query File Path= [UserName= ] Query File Rights Path= UserName= Query IPX Version Query Server Query Server Date Time Query Server InternetAddr Query Server LoginStatus Query Server NumOfVols Query Server Volumes Query SPX Config Query SPX Version Query TTS Status Query User DiskSpaceLeft UserName= VolName= Query User DiskUsage UserName= VolName= Query Volume VolName= Query Volume DiskUsage VolName= UserName= Query Volume USpaceAllowed VolName= UserName= Remove Directory Trustee Path= UserName= Remove File Trustee Path= UserName= B-6 Table B-1 (continued) NetWare RUNCMDs Sorted by Action ------------------------------------------------------------------ Action Resource Attribute Resource Command Parameter Qualifier Qualifier ------------------------------------------------------------------ Remove Volume Trustee VolName= UserName= Set Directory CDate= Path= CTime=