#EDIR DATA#
NMA for NetView Administration GuideDisclaimerNovell®, Inc. makes no representations or warranties with respect to the contents or use of this manual, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.Further, Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of NetWare software, at any time, without any obligation to notify any person or entity of such changes.TrademarksBtrieve, DR DOS, EXOS, LANalyzer, NetWare, OnLan/PC, Novell, and the N design are registered trademarks of Novell, Inc.Advanced NetWare, Boot Support Module, BSM, ElectroText, Hardware Specific Module, Hot Fix, HSM, Internetwork Packet Exchange, LAN Service, Link Support Layer, LSL, Media Support Module, MSM, Multiple Link Interface, MLI, Multiple Link Interface Driver, MLID, Multiple Protocol Interface, MPI, NetWare Access Server, NetWare Access Services, NetWare Core Protocol, NCP, NetWare Directory Services, NDS, NetWare DOS Requester, NDR, NetWare Express, NetWare Loadable Module, NLM, NetWare Management Agent, NetWare MultiProtocol Router, NetWare NFS, NetWare Requester, NetWare RPC, NetWare Runtime, Network Support Encyclopedia, NetWare 3270 LAN Workstation, NetWare 3270 LAN Workstation for DOS, NetWare 3270 LAN Workstation for Windows, NLM, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, Novell Labs, Novell Virtual Terminal, NVT, NTR2000, Open Data-Link Interface, ODI, Packet Burst, RX-Net/2, SFT, Topology Specific Module, TSM, TSA, Transaction Tracking System, TTS, Turbo RX-Net, Virtual Loadable Module, and VLM are trademarks of Novell, Inc.NetWire is a service mark of Novell, Inc.Novell Authorized Reseller is a collective mark of Novell, Inc.3Com and 3+Share are registered trademarks of 3Com Corporation.ARCnet is a registered trademark of Datapoint Corporation.AT&T is a registered trademark of AT&T.Apple, AppleShare, AppleTalk, ImageWriter, LaserWriter, LocalTalk, and Macintosh are registered trademarks of Apple Computer, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.COMPAQ is a registered trademark of Compaq Computer Corporation.CompuServe is a registered trademark of CompuServe, Inc.DDS is a trademark of Sony Corporation.DEC is a trademark of Digital Equipment Corporation.Epson is a registered trademark of Seiko Epson Corporation.GE Information Services is a trademark of General Electric Company, USA, which is not connected with the General Electric Company p.l.c. of England.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.Hewlett-Packard, Deskjet, HP, Laserjet, PCL, and Vectra are registered trademarks of Hewlett-Packard Company.IBM, AT, Micro Channel, NetView, OS/2, ProPrinter, and PS/2 are registered trademarks of International Business Machines Corporation.IBM Operating System/2 Local Area Network Server (LAN Server), Presentation Manager, SAA, and XT are trademarks of International Business Machines Corporation.Intel is a registered trademark of Intel Corporation.LAN Manager and LAN Manager Server are trademarks of Microsoft Corporation.Lotus is a registered trademark of Lotus Development Corporation.Microsoft and MS-DOS are registered trademarks of Microsoft Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and Microline are registered trademarks of Oki Electric Industry Co., Ltd.Panasonic is a registered trademark of Panasonic Office Automation.Pinwriter, Spinwriter, and NEC are registered trademarks of NEC Corporation.PostScript is a registered trademark of Adobe Systems Incorporated.SDI is a registered trademark of Systems Data, Inc.SQL Server is a trademark of Sybase, Inc.Unicode is a registered trademark of Transoft Ltd.UNIX is a registered trademark of UNIX System Laboratories, Inc., a subsidiary of AT&T.WordPerfect is a registered trademark of WordPerfect Corporation.Xerox Diablo is a registered trademark of Xerox Corporation.Copyright Notices© Copyright 1983-1993 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.LBL="0"About This GuideID="FM66968"ID="FM66968"This guide describesNetWare Management Agent (NMA) for NetView v1.3How to install NMA for NetView v1.3How to use NMA for NetView v1.3Who Should Read This GuideRead this guide if you want toLearn about NMA for NetView and its featuresLearn about the new features in NMA for NetView v1.3Install NMA for NetView v1.3Configure or reconfigure NMA for NetViewLoad or unload NMA for NetViewRemove NMA for NetView from a NetWare v3.1x serverContent OverviewChapter 1, About NMA for NetView: Describes NMA for NetView, introduces the new features in NMA for NetView v1.3, and describes the complete set of features provided by NMA for NetView v1.3.Chapter 2, Installing NMA for NetView: Provides a procedure for setting up a NetWare v3.1x 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, and 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?" on page A-1.Appendix B, Using NetView Command Filtering: Provides the procedure for disabling or filtering out selected NetView RUNCMDs sent from the NetView operator to the server running NMA for NetView or LAN workstation.ConventionsThis guide uses a variety of typographical conventions, special terminology, and symbolic conventions.Typographic ConventionsWIDTH="96"<Words in Brackets>WIDTH="312"Bracketed words indicate names of keys that you press For  example:Press <Enter> to display the Configuration Options menu.Bold MonospaceWhen in bold, monospace font indicates commands that you  enter at a prompt or select from a menu. For example:SERVERLetters and symbols that appear in bold monospace typeface  must be entered exactly as shown.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:> servercolon (:)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 nvinstalMonospaceWhen not in bold, monospace type indicates messages that the  system displays. For example:Enter filenameItalicsWords appearing in italics represent variables that you must  replace with the appropriate values. For example:OP=useridIn the example above, you would type OP= and replace the  variableuserid with a valid NetWare user ID.UPPERCASEWords appearing in UPPERCASE are filenames, pathnames, or  NetWare utility names. For example:DISK1.ZIPTerminologyThis guide uses the following terms to summarize actions that are performed frequently or product groups referred to frequently.WIDTH="96"SelectWIDTH="312"Use the cursor keys to highlight the item and press <Enter>.EnterType the indicated text and press <Enter>. For example:Enter load nvinstal.NetWare v3.1xVersions of Netware later than v3.1 and earlier than v4.0  (for example, NetWare v3.11 and NetWare v3.12).Symbolic ConventionsA Note symbol points out an item that may be of interest but is not vital to the operation of the product or to your safety.A Suggestion symbol denotes hints, tips, or helpful information that may be useful, but not critical.An Important symbol denotes important information that you should read. It's also a visual cue to key concepts and facts.AWarning symbol carries a stronger message than an Important symbol and is used to call attention to a situation in which a critical or irreversible error can be made.A Procedure symbol calls attention to those portions of the manual that contain "action items," such as lists of step-by-step instructions.Additional ReadingThe publications described in this section provide additional information on products used with NMA for NetView.NetWare Reference Guide for NetView Operators (100-001242-003)The NetWare Reference Guide for NetView Operators describes the alert messages and NetWare command set provided by NMA for NetView v1.3 and NetWare for SAA(tm) v1.3.NetWare for SAA v1.3 Administration Guide (100-001166-002)The NetWare for SAA v1.3 Administration Guide describes the NetView support features in NetWare for SAA v1.3Btrieve Installation and Operation (100-001662-001)NetView Operations Primer (SC30-3363) from IBMLBL="1"About NMA for NetViewThis chapter describesNetWare Management Agent (NMA) for NetViewThe new features in NMA for NetView v1.3The complete NMA for NetView feature setThe NMA for NetView and NetWare for SAA products provide similar support for NetView software. Do not install NMA for NetView and NetWare for SAA in the same NetWare server.NMA for NetView and NetWare for SAA servers are designed to support the NetView network management program from IBM. These NetWare products support any other network management program that is 100 percent compatible with NetView. The NET/MASTER network management program from Systems Center 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)) product that enables idxid="w8230"book="_idx" docset="nw312" tidref="i4203"idxid="w8231"book="_idx" docset="nw312" tidref="i4203"NetWare v3.1x servers (versions of NetWare later than v3.1 and earlier than or equal to v4.0) to participate in NetView network management. The NetWare v3.1x product package includes NMA for NetView.idxid="w8232"book="_idx" docset="nw312" tidref="i4197"NetView is an IBM network management program that runs in the idxid="w8233"book="_idx" docset="nw312" tidref="i7309"Virtual Machine (VM) and idxid="w8234"book="_idx" docset="nw312" tidref="i3971"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.Figure 1-1 is a simplified illustration of how NMA for NetView communicates with NetView.LBL="1-1"Simplified Illustration of NMA for NetView CommunicationsFILE="nmaag001.pbm"idxid="w8235"book="_idx" docset="nw312" tidref="i4610"NMA for NetView runs in a NetWare v3.1x server and communicates with the NetView program, which runs in the IBM host computer. The connection between the NetWare server and the host is described later in this chapter.NMA for NetView exchanges three types of messages with NetView:AlertsCommandsCommand responsesAlerts are messages that are sent from NMA for NetView to NetView. NMA for NetView translates selected NetWare server error and status messages into alerts.idxid="w8236"book="_idx" docset="nw312" tidref="i6098"Commands, idxid="w8237"book="_idx" docset="nw312" tidref="i6098"idxid="w8238"book="_idx" docset="nw312" tidref="i4610"or 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.Command idxid="w8239"book="_idx" docset="nw312" tidref="i1049"responses are messages that are sent to NetView after a command message has been processed. Command response messages contain information about the server or about the result of a server command.The messages that travel between NMA for NetView and the NetView host relate to the operation of the NetWare v3.1x server. NMA for NetView does not monitor, report, or control the status of the NetWare local area network (LAN) or NetWare LAN workstations. NMA for NetView does not respond to maintenance statistic requests from an IBM host.NetView operators use a terminal to connect to the NetView program on the host. From the terminal, the NetView operator can view alert messages, send command messages, and view command response messages. For more information on NetView operation, see the NetView Operation Primer (SC30-3363) from IBM.Novell sells software that enables NetWare users to connect to NetView and other host programs from a NetWare LAN workstation. The NetWare 3270 LAN Workstation(tm) products allow NetWare LAN workstations to emulate IBM terminals. NetWare for SAA enables communications between NetWare 3270 LAN Workstations and the host.What Is New in Version 1.3idxid="w8240"book="_idx" docset="nw312" tidref="i4610"NMA for NetView v1.3 provides the following new features:Additional alerts for the NetWare operating system and its component services. Also, some alert messages are changed.New commands for requesting server status and controlling some server features.A command filtering feature for disabling NetView access to one or more server commands.Alert and command forwarding for applications that use the NetWare Open NetView interface.These features are described with the complete set of NMA for NetView features in the next section.NMA for NetView Featuresidxid="w8241"book="_idx" docset="nw312" tidref="i4610"The principal features of NMA for NetView areAlert generationCommand processingHost communication optionsCollection point communication optionsSupport for the Open NetView interfaceAlert Generationidxid="w8242"book="_idx" docset="nw312" tidref="i4610"idxid="w8243"book="_idx" docset="nw312" tidref="i183"idxid="w8244"book="_idx" docset="nw312" tidref="i183"NMA for NetView generates alerts for the following server processes:Token ring adapters and driversLogical link control (LLC) protocol components of token ring driversThe NetWare operating system and component servicesThe 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. 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.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 (from the reference guide) that corresponds to the alert message. (NetView messages use a format that is different from NetWare messages.) NetWare messages are described in NetWare v3.1xSystem Messages.Command Processingidxid="w8245"book="_idx" docset="nw312" tidref="i4610"idxid="w8246"book="_idx" docset="nw312" tidref="i6098"idxid="w8247"book="_idx" docset="nw312" tidref="i6098"NMA for NetView processes two types of commands:Server query commandsServer control commandsidxid="w8248"book="_idx" docset="nw312" tidref="i4610"idxid="w8249"book="_idx" docset="nw312" tidref="i6098"idxid="w8250"book="_idx" docset="nw312" tidref="i6098"idxid="w8251"book="_idx" docset="nw312" tidref="i6098"NMA for NetView allows you to control command processing with the following features:Command securityCommand filteringThis section describes the actions these commands produce and the control features you can use. For detailed information on each command and its syntax, see the NetWare Reference Guide for NetView Operators.Server Query Commandsidxid="w8252"book="_idx" docset="nw312" tidref="i6098"idxid="w8253"book="_idx" docset="nw312" tidref="i6239"Server query commands request information about server resources. These commands allow the NetView operator to query forServer information such as the number of volumes on a server, the server's login status, and the server's internetwork addressVolume information such as the space allowed for a user, and the space used by a userDirectory information such as the space allowed for a directory, and a user's rights to the directoryFile informationA user's usage of a volume and the remaining space allowed to the userThe version numbers of the Sequenced Packet Exchange (SPX) and Internetwork Packet Exchange (IPX) protocolsThe configuration of the SPX protocolThe status of the Transaction Tracking Service (TTS)Server Control Commandsidxid="w8254"book="_idx" docset="nw312" tidref="i6098"idxid="w8255"book="_idx" docset="nw312" tidref="i6236"Server control commands allow a NetView operator toEnable or disable server login, shut down a server, and broadcast a message to server usersSet the server date and timeSet the volume space allowed to a user and remove a user from a volumeSet the space allowed to a directory; add or remove a directory trustee; and set the owner, creation date, and creation time for a directoryAdd 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 timeEnable or disable the Transaction Tracking Service (TTS)Load and unload an NLMIf a NetView operator sends a idxid="w8256"book="_idx" docset="nw312" tidref="i3238"idxid="w8257"book="_idx" docset="nw312" tidref="i6098"LOAD command with an incomplete set of parameters for an NLM or a communication service, a prompt for the missing parameters appears on the server console. The NLM or communication service does not begin operating until the missing information is entered at the server console. The NetView operator is not notified about the missing parameters and may not be aware that the NLM or communication service is not operating.Also, if the NetView operator sends an idxid="w8258"book="_idx" docset="nw312" tidref="i7074"idxid="w8259"book="_idx" docset="nw312" tidref="i6098"UNLOAD command for an NLM or a communication service, the command will fail if the NLM or communication service is exporting functions and symbols to another NLM or communication service. If the UNLOAD command fails, a message appears on the system console. The NetView operator is not notified about the failure and may not be aware that the NLM or communication service is still operating.Command Securityidxid="w8260"book="_idx" docset="nw312" tidref="i6098"idxid="w8261"book="_idx" docset="nw312" tidref="i1050"NMA for NetView provides a command security feature for controlling NetView command processing. NMA for NetView checks each NetView command for a valid NetWare user ID with the appropriate status (see Table 1-1).LBL="1-1" INLINE="F"NetView Command ProcessingWIDTH="108"Server Command TypeWIDTH="192"NetWare User ID Status Required for ProcessingWIDTH="108"QueryWIDTH="192"File server console operator or SupervisorControlSupervisorWhen a command message does not include an acceptable NetWare user ID, NetWare rejects the command and sends the following message to NetWare: Invalid Operator nameWhen this message appears on the NetView console, the name variable displays the user ID that was rejected.A NetView command must include a user ID other than SUPERVISOR with either supervisor-equivalent privileges or a file server console operator status. Although the SUPERVISOR user ID has supervisor-equivalent privileges, the server rejects RUNCMDs that include the SUPERVISOR user ID.Command Filteringidxid="w8262"book="_idx" docset="nw312" tidref="i6098"idxid="w8263"book="_idx" docset="nw312" tidref="i1031"The command filtering feature allows you to disable NetWare processing of select commands that may be sent by NetView operators. You can disable any number of commands 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 command filtering, NMA for NetView returns the following message to NetView: Cannot access this NetView RuncmdID="FM49012"Host Communications Optionsidxid="w8264"book="_idx" docset="nw312" tidref="i4610"idxid="w8265"book="_idx" docset="nw312" tidref="i1088"NMA for NetView provides two options for communicating with the host computer:Direct host communications over a token ring LANCollection point communications via a NetWare for SAA serverDirect Host Communicationsidxid="w8266"book="_idx" docset="nw312" tidref="i1088"idxid="w8267"book="_idx" docset="nw312" tidref="i1429"Figure 1-2 idxid="w8268"book="_idx" docset="nw312" tidref="i4630"illustrates an example of a network topology that supports the direct host communications option.LBL="1-2"Direct Host CommunicationsFILE="nmaag002.pbm"When using the direct host communications option, you must connect to the host through a token ring LAN.Collection Point Communicationsidxid="w8269"book="_idx" docset="nw312" tidref="i1088"idxid="w8270"book="_idx" docset="nw312" tidref="i1009"Figure 1-3 illustrates an example of a network topology that supports the collection point communications option.LBL="1-3"Collection Point CommunicationsFILE="nmaag003.pbm"When using the collection point communications option, NMA for NetView indirectly connects to the host computer through a idxid="w8271"book="_idx" docset="nw312" tidref="i4297"NetWare for SAA server. In this system configuration, the NetWare for SAA server is called a collection point server.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 command to an NMA for NetView server, it sends the command to the collection point server. The collection point server forwards the command over the NetWare LAN to the idxid="w8272"book="_idx" docset="nw312" tidref="i4630"NMA for NetView server. Command response messages from NMA for NetView follow the same communications path as alert messages.idxid="w8273"book="_idx" docset="nw312" tidref="i1009"Advantages of Collection Point CommunicationsThe collection point server option 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.Support for the Open NetView Interfaceidxid="w8274"book="_idx" docset="nw312" tidref="i4610"idxid="w8275"book="_idx" docset="nw312" tidref="i4828"NMA for NetView can provide a connection between NetView and other application that conform to the NetWare Open NetView interface. When an application uses the Open NetView interface, a server running NMA for NetView canReceive alerts from the application and forward them to NetViewReceive commands from NetView and forward them to the applicationFor more information on the NetView support provided by an application, refer to the documentation supplied with the application.LBL="2"Installing NMA for NetViewThis chapter describes how to Install NMA for NetView on a NetWare v3.1x (versions of NetWare later than v3.1 and earlier than v4.0) serverPrepare the host for communications with an NMA for NetView serverThe NMA for NetView and NetWare for SAA products provide similar support for NetView software. Do not install both NMA for NetView and NetWare for SAA in the same server.idxid="w8276"book="_idx" docset="nw312" tidref="i4610"idxid="w8277"book="_idx" docset="nw312" tidref="i2842"Installation of NMA for NetView consists of the following tasks:Choose a connection topology (see IDREF="FM62490"page 2-2)Set up the required server hardware and software (see IDREF="FM92052"page 2-7)Prepare the NetWare v3.1x server (see IDREF="FM35353"page 2-9)Install the NMA for NetView software (see IDREF="FM33357"page 2-17)Prepare the host for NMA for NetView (see IDREF="FM20983"page 2-20)Configure NMA for NetView (see IDREF="FM67321"page 3-3)For instructions on completing a task, turn to the page listed after it.Give the NetWare Reference Guide for NetView Operators to your NetView operator. The information in the reference guide is designed to help the NetView operator manage NetWare servers.ID="FM62490"Choosing a Connection Topologyidxid="w8278"book="_idx" docset="nw312" tidref="i2842"Before you set up the NMA for NetView server, you must choose the host communications options you will use. The host communications options areDirect host communicationsCollections point server communicationsThe host communications options are described beginning on IDREF="FM49012"page 1-9.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.idxid="w8279"book="_idx" docset="nw312" tidref="i1429"Topologies That Support Direct Host CommunicationsFigure 2-1 illustrates an example of a connection topology that supports an NMA for NetView server configured for direct host communications.LBL="2-1"Topology Example 1, Direct Host CommunicationsFILE="nmaag004.pbm"In this topology, the NMA for NetView server communicates directly with the host's communications equipment over a token ring LAN. The workstation LAN shown in Figure 2-1 is a token ring LAN, but it does not have to be. For example, the workstation LAN could be an Ethernet LAN.When using the topology in Figure 2-1, the NMA for NetView server requiresAn IBM 16/4 or 16/4/A Token Ring adapter for communications with the host LANCabling from the token ring adapter to the host LANA network adapter for the workstation LANCabling from the NMA for NetView server to the workstation LANEach 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.Figure 2-2 illustrates another example of a topology that supports direct host communications.LBL="2-2"Topology Example 2, Direct Host CommunicationsFILE="nmaag005.pbm"In this example, the NMA for NetView server connects to a single token ring network through one adapter. The NMA for NetView server uses the same network to communicate with the host and the NetWare workstations.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. idxid="w8280"book="_idx" docset="nw312" tidref="i1429"idxid="w8281"book="_idx" docset="nw312" tidref="i1009"Topology That Supports Collection Point CommunicationsFigure 2-3 illustrates a topology that supports an NMA for NetView server configured for collection point server communications.LBL="2-3"Sample Collection Point Server TopologyFILE="nmaag006.pbm"The collection point server is a NetWare v3.1x server running NetWare for SAA. NetWare for SAA must be configured to support NetView collection point communications. (The collection point server requirements are described in the NetWare for SAA v1.3 Administration Guide.)In this example, 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.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. idxid="w8282"book="_idx" docset="nw312" tidref="i2842"idxid="w8283"book="_idx" docset="nw312" tidref="i1009"ID="FM92052"idxid="w8284"book="_idx" docset="nw312" tidref="i2842"Setting Up the Required Server Hardware and SoftwareNMA for NetView requires certain hardware and software.idxid="w8285"book="_idx" docset="nw312" tidref="i4610"idxid="w8286"book="_idx" docset="nw312" tidref="i2655"Required HardwareNMA for NetView requires the following hardware:A personal computer that uses an 80386 or 80486 microprocessor.One or more network adapters. (See "Choosing a Connection Topology" on IDREF="FM62490"page 2-2.)Cabling between all network adapters and the appropriate network. (See Choosing a Connection Topology" on IDREF="FM62490"page 2-2.)A minimum of 6 megabytes (MB) of random access memory (RAM): 2 MB for NMA for NetView and a minimum of 4 MB for NetWare v3.1x. To calculate the total memory required, determine how much memory is required by NetWare v3.1x (as described in NetWare Version 3.1xInstallation), and then add 2 MB.Refer to the manuals for each hardware product for installation instructions.Record the option settings of all jumpers and switches on each network adapter. If the board has a network address or serial number, record these items also. When using two or more adapters for the same type of cabling system, be sure to note which adapter is connected to which network.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.idxid="w8287"book="_idx" docset="nw312" tidref="i4610"idxid="w8288"book="_idx" docset="nw312" tidref="i6409"Required SoftwareNMA for NetView requires the following software:NMA for NetView v1.3 (or later) software.NetWare v3.1x, (a version of NetWare later than v3.1 and earlier than v4.0) which includes:CLIB (CLIB.NLM) to support the library of C functions.The Btrieve® product (BTRIEVE.NLM), which manages the database that holds your NMA for NetView configuration parameters.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.Because all other software components must be loaded before you run NMA for NetView, Novell recommends that you automate their loading by inserting the appropriate statements in your server's AUTOEXEC.NCF file. For additional information on AUTOEXEC.NCF, see "Automating Server Startup" on IDREF="FM84302"page 2-16. idxid="w8289"book="_idx" docset="nw312" tidref="i2842"ID="FM35353"P idxid="w8290"book="_idx" docset="nw312" tidref="i2842"idxid="w8291"book="_idx" docset="nw312" tidref="i4398"reparing the Netware v3.1x ServerYou must prepare the NetWare v3.1x server for the installation and operation of NMA for NetView as follows:Install NetWare v3.1x.Start NetWare v3.1x.Load all required NLMs.When loading the required NLMs, use LOAD command line parameters to carry out the following:Configure Btrieve to support NMA for NetView.Configure the LAN adapter driver to support NMA for NetView.For instructions on installing and starting NetWare v3.1x, refer to NetWare v3.1xInstallation.For instructions on downing or restarting NetWare v3.1x, see the DOWN and SERVER command descriptions in NetWare v3.1xSystem Administration.The rest of this section provides additional information on the NLMs and drivers that must be loaded and configured.I idxid="w8292"book="_idx" docset="nw312" tidref="i2842"idxid="w8293"book="_idx" docset="nw312" tidref="i4203"f You Are Installing on a NetWare v3.11 ServerA NetWare v3.11 server requires additional patch files available through idxid="w8294"book="_idx" docset="nw312" tidref="i4268"idxid="w8295"book="_idx" docset="nw312" tidref="i4610"NetWare Express(tm) to support NMA for NetView v1.3. NetWare Express is an online information and software delivery service from Novell. NetWare Express subscribers can locate software updates in the NSE Online(tm) Files area. The NMA for NetView v1.3 patch and software documentation package appears in the NMA for NetView Update area. To support NetWare v3.11, download this package and follow the directions in NMA4NV.DOC file and the documentation files. For more information on subscribing to NetWare Express, contact Novell.idxid="w8296"book="_idx" docset="nw312" tidref="i2842"idxid="w8297"book="_idx" docset="nw312" tidref="i4604"idxid="w8298"book="_idx" docset="nw312" tidref="i4604"Loading the Required NLMsidxid="w8299"book="_idx" docset="nw312" tidref="i794"idxid="w8300"book="_idx" docset="nw312" tidref="i981"idxid="w8301"book="_idx" docset="nw312" tidref="i1086"To prepare the server for NMA for NetView, you must load the following NLMs (which are provided with NetWare v3.1x):BtrieveCLIBCommunication protocol NLMsYou must load Btrieve before you can install or operate NMA for NetView. NetWare Btrieve is a database management system that manages your NMA for NetView configuration parameters. Btrieve requires the CLIB NLM.Example for Direct Host Communicationsidxid="w8302"book="_idx" docset="nw312" tidref="i4604"idxid="w8303"book="_idx" docset="nw312" tidref="i1429"The following command list is an example of the commands required to prepare a NetWare v3.1x server for direct communications between NMA for NetView and the host: :load clib :load btrieve -p=4096 -f=20 -h=60 -l=20 -c :load token name=logical_adapter_nameMake sure that you use the letter l when entering the parameter -l=20When 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=logical_adapter_name parameter specifies the name for the token ring LAN adapter. This procedure is described on IDREF="FM86159"page 2-14.The NetWare v3.1x server requires additional communication protocol NLMs for workstation communications. This section describes only the requirements for NMA for NetView.Example for Collection Point Communicationsidxid="w8304"book="_idx" docset="nw312" tidref="i4604"idxid="w8305"book="_idx" docset="nw312" tidref="i1009"The following command list is an example of the commands required to prepare a NetWare v3.1x server for IPX/SPX communications with a collection point server: :load clib :load spxs :load btrieve -p=4096 -f=20 -h=60 -l=20 -c :load lan_driver :bind protocol to lan_driverMake sure that you use the letter l when entering the parameter -l=20When configured for collection point communications, NMA for NetView must use an SPX connection to communicate with the collection point server. The communications path may be direct, or it may require intermediate communications devices such as bridges and gateways.The LOAD lan_driver and BIND commands load the driver for the LAN adapter and bind it to the communication protocol. This procedure, which enables communications with the collection point server, is described on IDREF="FM54096"page 2-15.Locating NLMsidxid="w8306"book="_idx" docset="nw312" tidref="i4604"The NLMs in the previous examples are included in the NetWare v3.1x product package and are described in NetWare v3.1xSystem Administration and in Btrieve Installation and Operation (100-001662-001).If you are adding NMA for NetView to a previously installed NetWare v3.1x server, enter the MODULES command to list the NLMs that have already been loaded. The MODULES command is described in NetWare v3.1xSystem Administration.Configuring idxid="w8307"book="_idx" docset="nw312" tidref="i794"idxid="w8308"book="_idx" docset="nw312" tidref="i2842"BtrieveIf you have changed the default settings in Btrieve, you may need to reconfigure Btrieve to support NMA for NetView.To configure Btrieve for operation with NMA for NetView, enter the configuration parameters with the LOAD command at startup.Table 2-1 lists the Btrieve configuration parameters and the settings that NMA for NetView requires.LBL="2-1" INLINE="F"Btrieve Configuration Settings for NMA for NetViewWIDTH="144"Btrieve ParameterWIDTH="84"LOAD Command  Line OptionWIDTH="60"SuggestedValueNumber of open files-f20Number of handles-h60Number of locks-l20Number of transactions-tNumber of files per transaction-nLargest compressed record size-uLargest record size-dLargest page size-pNumber of sessions-sCreate files as transactional-iLogging of selected files-aTo load and configure Btrieve simultaneously, enter the following command: :load btrieve -p=4096 -f=20 -h=60 -l=20 -cIf Btrieve is already loaded, you must unload Btrieve and then load it with the configuration parameters. To unload Btrieve, enter the command UNLOAD BTRIEVE at the system prompt (:).ID="FM89603"Loading and Binding the LAN AdapterYou must load an adapter driver for the adapter through which you communicate with the host. If you plan to configure NMA for NetView for collection point communications, you must bind the adapter driver to a communication protocol.ID="FM86159"Loading for Direct Host Communicationsidxid="w8309"book="_idx" docset="nw312" tidref="i3069"idxid="w8310"book="_idx" docset="nw312" tidref="i1429"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.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 v3.1x. To load the TOKEN.LAN adapter driver, enter the following command: :load tokenAfter you enter the LOAD TOKEN command, the server prompts you for the configuration of the token ring adapter.If you prefer to enter the configuration parameters with the LOAD TOKEN command, enter a command that is similar to the following: :load token port=a20 int=2 node=12345678 saps=4 ls=32 name=logical_adapter_nameSet the adapter configuration parameters as follows: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.)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.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.SAPS. This parameter specifies the number of service access points (SAPs) that can be opened by an application using the token ring adapter. The number of SAPs must be 04 or a multiple of 04, and depends on the number of services running on the node (generally one SAP per service). Consult the token ring adapter manual for information on calculating the maximum number of SAPs.LS. This parameter specifies the number of link stations. This value should be eight times the SAPS setting.NAME. This parameter specifies the name for the token ring LAN adapter. The logical name can be up to 16 alphanumeric and/or special characters. You will use this name later to configure the Logical Adapter Name field in the NVCONFIG program.ID="FM54096"Loading and Binding for Collection Point Server Communicationsidxid="w8311"book="_idx" docset="nw312" tidref="i3069"idxid="w8312"book="_idx" docset="nw312" tidref="i1009"When NMA for NetView is configured for collection point server communications, you must load an adapter driver and bind it to a communication protocol. The type of adapter and communication protocol you use depends on the network through which you will connect to the collection point server.The following command list is an example of the commands required to load an NE2000(tm) adapter driver and bind it to IPX: :load ne2000 :bind ipx to ne2000NetWare v3.1x provides some adapter drivers and the IPX communication protocol. For information on using this software, see NetWare v3.1xInstallation. For additional information on the driver required by your adapter, see the manual for your adapter.ID="FM84302"Automating Server Startupidxid="w8313"book="_idx" docset="nw312" tidref="i2842"idxid="w8314"book="_idx" docset="nw312" tidref="i617"idxid="w8315"book="_idx" docset="nw312" tidref="i4610"As the previous sections illustrate, you must enter a number of commands to prepare a NetWare v3.1x server for NMA for NetView. To make starting a server easier, the NetWare v3.1x INSTALL utility allows you to create a startup file, which operates in a manner similar to the DOS AUTOEXEC.BAT file.The startup file for NetWare v3.1x servers is named AUTOEXEC.NCF, and it must be created with the INSTALL utility. The INSTALL utility includes a special option that automatically enters the names of all loaded NLMs and drivers into the AUTOEXEC.NCF file.Novell recommends that you use the AUTOEXEC.NCF file to automate server startup. Creating the AUTOEXEC.NCF file is generally easier than writing down the commands you need to execute.When you create the AUTOEXEC.NCF file, enter all the commands to prepare the server for NMA for NetView; then add the command to start NMA for NetView: :load nmanvFor instructions on creating the AUTOEXEC.NCF file, see the server installation section of NetWare v3.1xInstallation or the section on the INSTALL utility in NetWare v3.1xAdministration. idxid="w8316"book="_idx" docset="nw312" tidref="i2842"idxid="w8317"book="_idx" docset="nw312" tidref="i4398"ID="FM33357"Installing the NMA for NetView Softwareidxid="w8318"book="_idx" docset="nw312" tidref="i2842"idxid="w8319"book="_idx" docset="nw312" tidref="i4302"This section describes how to install the NMA for NetView software.If the NetWare for SAA software is installed in the NetWare v3.1x server, do not install the NMA for NetView software. NetWare for SAA provides NetView management support, which is similar to NMA for NetView.To install the NMA for NetView software:If the server is not running, start the server and all prerequisite NLMs and drivers."Preparing the NetWare v3.1x Server" beginning on IDREF="FM35353"page 2-9 describes which NLMs and drivers must be running.If N idxid="w8320"book="_idx" docset="nw312" tidref="i4610"MA for NetView v1.0 or v1.2 is installed on the server, remove that version of the software.Do not use the NetWare INSTALL utility to remove previous versions of NMA for NetView. You must remove NMA for NetView with the 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 the software.Insert NMA for NetView v1.3, Disk 1, into one of the server's disk drives.Start the NetWare INSTALL utility by entering :load installThe INSTALL utility's option menu appears. (See Figure 2-4.)LBL="2-4"INSTALL Options MenuFILE="nmaag007.pbm"Select Product Options.The Currently Installed Products window appears.Press <Insert>.You are prompted to specify the location of your NMA for NetView installation files (Figure 2-5).LBL="2-5"Installation PromptFILE="nmaag008.pbm"If you inserted NMA for NetView v1.3, Disk 1 in the server drive A:, press <Enter>; otherwise, type the letter of the drive where you inserted the diskette and press <Enter>.The prompts shown in Figure 2-6 appear:LBL="2-6"NMA for NetView ConfirmationFILE="nmaag009.pbm"Select the option Install on this server.Follow the prompts until all the required files are installed on the server.After installation is complete, the NMA for NetView Communications Options menu appears.Configure NMA for NetView for connection to an SNA host or to a NetView collection point. See Chapter 3 for details.Before operating NMA for NetView, you must configure the software as described in "Configuring NMA for NetView" beginning on IDREF="FM67321"page 3-3.If you are not ready to configure the software, you can exit the NetWare INSTALL program and restart the program when you are ready to configure. To exit the program, press <Esc>. idxid="w8321"book="_idx" docset="nw312" tidref="i2842"idxid="w8322"book="_idx" docset="nw312" tidref="i4302"ID="FM20983"Preparing the Hostidxid="w8323"book="_idx" docset="nw312" tidref="i2842"idxid="w8324"book="_idx" docset="nw312" tidref="i2668"NMA for NetView requires certain hardware and software at the host computer (see Table 2-2). These host requirements vary according to the NMA for NetView communications option in use.LBL="2-2" INLINE="F"Connection idxid="w8325"book="_idx" docset="nw312" tidref="i2668"idxid="w8326"book="_idx" docset="nw312" tidref="i1009"RequirementsWIDTH="156"Components Supporting Direct Host ConnectionWIDTH="156"Components Supporting Collection Point Server ConnectionWIDTH="156"1. NetView software on the hostWIDTH="156"1. NetView software on the host2. PU Type 2.0 definition in the   Virtual  Telecommunications  Access Method (VTAM) system on  the host2. NetWare for SAA on the   collection point server3. Token ring LAN connection   between the host and the NMA  for NetView server3. Collection point server connection   to the host4. NetView code points for NetWare   if host version of NetView is 2.1 or  earlier4. NetView code points for NetWare   if the host version of NetView is 2.1  or earlierThe following sections describe each of the host components that may be required.NetView SoftwareNetView idxid="w8327"book="_idx" docset="nw312" tidref="i4197"software is required to receive the NetWare alert messages and send commands to NetWare servers. The host systems programmer is responsible for installing NetView.ID="FM22885"PU Type 2.0 Definition in VTAMidxid="w8328"book="_idx" docset="nw312" tidref="i1429"idxid="w8329"book="_idx" docset="nw312" tidref="i5695"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.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:Photocopy Table 3-1 on IDREF="FM29053"page 3-5.The host communications parameters in Table 3-1 are the NMA for NetView parameters that must be set to match parameters at the host.Contact the host systems programmer and request a PU definition for your NMA for NetView server.Table 2-3 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.LBL="2-3" INLINE="F"PU Type Definitions for Host Communication EquipmentWIDTH="132"Communication EquipmentWIDTH="168"PU DefinitionWIDTH="132"937x attachment WIDTH="168"Switched token ring PU Type 2.037xx attachmentSwitched token ring PU Type 2.03174 controllerNonswitched PU Type 2.0NMA for NetView requires no logical unit (LU) definitions.Figure 2-7 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.LBL=" 2-1"Sample PU  Definition for 937x  Attachment  NMA4NV VBUILD TYPE=SWNET ************************************************************************ TOKEN RING PU 2.0 FOR NMA FOR NETVIEW ************************************************************************ T12345 PU ADDR=04,                                                     X                IDBLK=017,                                              X                IDNUM=12345,                                            X                LANSW=YES,                                              X                MAXDATA=1033,                                           X                PUTYPE=2,                                               X                ISTATUS=ACTIVE                                          X Ask the host systems programmer for the host communications parameters for your NMA for NetView server.Table 2-4 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 the NVCONFIG program. Columns 2 through 4 list the corresponding host parameters for three types of host communications equipment.LBL="2-4" INLINE="F"ID="FM71351"NVCONFIG Parameters That Must Match Host ParametersWIDTH="96"NVCONFIGParameter NameWIDTH="96"937x AttachmentParameter LocationWIDTH="96"37xx AttachmentParameter LocationWIDTH="96"3174 ControllerParameter LocationWIDTH="96"Peripheral NodeControl Point  (PNCP) NameWIDTH="96"CPNAME statement  (if any) in the  switched PU  definitionWIDTH="96"Not applicableWIDTH="96"Not applicableToken RingDestination NodeAddressMACADDRdefinition in the PORT statementToken interface card  (TIC) address  (LOCADD=value) in  the Network Control  Program (NCP)  definitionStatements 900 and  940 in the  Customization  PanelsToken Ring  Destination Service  Access Point (SAP)Not applicableEnter 4 for this  parameterConfiguration  question 900 in the  Customization  PanelsToken Ring Service  Access Point (SAP)SAPADDR definition  in the PORT  statementEnter 4 for this  parameterStatement 940 in the  Customization  PanelsBlock IDIDBLK statement in  the switched PU  definitionIDBLK statement in  the switched PU  definitionNot applicable; no  entry requiredPUID for Token Ring  ConnectionIDNUM statement in  the switched PU  definitionIDNUM statement in  the switched PU  definitionNot applicable; no  entry requiredRecord the host systems parameters as follows:Locate the column in Table 2-4 for the host communications equipment your host connection will use.Ask the host systems programmer for the value of the parameters in that column.Write down the host communications parameters on the photocopy of Table 3-1.Save the photocopy of Table 3-1 so that you have the host configuration information when you configure NMA for NetView. (Configuration instructions begin on IDREF="FM37891"page 3-3.) idxid="w8330"book="_idx" docset="nw312" tidref="i1429"idxid="w8331"book="_idx" docset="nw312" tidref="i5695"Connection to the Token Ring LANidxid="w8332"book="_idx" docset="nw312" tidref="i1429"When NMA for NetView is configured for direct host communications, the host must be connected to the token ring LAN. The host systems programmer should be responsible for this task.NetWare for SAAidxid="w8333"book="_idx" docset="nw312" tidref="i1009"idxid="w8334"book="_idx" docset="nw312" tidref="i4297"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 v1.3 Administration Guide.Collection Point Server Connection to Hostidxid="w8335"book="_idx" docset="nw312" tidref="i1009"When NMA for NetView is configured for collection point communications, the collection point server (NetWare for SAA) requires either a token ring, SDLC, Ethernet, or QLLC connection to the host's communications equipment. For more information on establishing a host communications link to the collection point server, see the NetWare for SAA v1.3 Administration Guide.Installation of NetView Code Points for NetWareidxid="w8336"book="_idx" docset="nw312" tidref="i1000"idxid="w8337"book="_idx" docset="nw312" tidref="i2668"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 v2.1.You may not need to install the code points for NetWare. If you are using NetView v2.1or 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 v1.3 server or NetWare for SAA v1.3 server. For additional information on code points and their installation, see Appendix A, "Installing Code Points for NetWare." idxid="w8338"book="_idx" docset="nw312" tidref="i2842"idxid="w8339"book="_idx" docset="nw312" tidref="i2668"idxid="w8340"book="_idx" docset="nw312" tidref="i4610"idxid="w8341"book="_idx" docset="nw312" tidref="i2842"LBL="3"Configuring, Loading, and Unloading NMA for NetViewThis chapter describes procedures for managing the NMA for Netview software. You must install NMA for NetView before you can begin these procedures.Start the NVCONFIG configuration utility (IDREF="FM67803"page 3-2)Use NVCONFIG to configure or reconfigure the NMA for NetView software (IDREF="FM63338"page 3-3)Load NMA for NetView (IDREF="FM23935"page 3-13)Unload NMA for NetView (IDREF="FM71501"page 3-13)Administer NMA for NetView remotely (IDREF="FM31109"page 3-14)Remove the NMA for NetView software (IDREF="FM69684"page 3-15)These are independent procedures---not subdivisions of a long procedure. To complete any of these procedures, refer to the page where the procedure begins.ID="FM67803"Starting NVCONFIGidxid="w8342"book="_idx" docset="nw312" tidref="i4769"To start NVCONFIG:If the server is running, start the server and all prerequisite NLMs and drivers."Preparing the NetWare v3.1x Server" on page 2-9 identifies the NLMs and drivers that must be running.If NMA for NetView is running on your server, unload the program as described on IDREF="FM71501"page 3-13.Enter the following command: :load nvconfigThe server loads NVCONFIG from the SYS:SYSTEM directory; then NVCONFIG displays the Communications Options menu (see Figure 3-1).LBL="3-1"Communications Options MenuFILE="nmaag010.pbm"The currently active option, either NetView Host or NetView Collection Point, is marked by an asterisk.ID="FM67321"ID="FM63338"Configuring NMA for NetViewYou 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.Before you can configure NMA for NetView, you must have installed the software as described in Chapter 2.You can configure the software forDirect host communicationsCollection point server communicationsAlthough 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 v3.1x 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.Configuring for Direct Host Communicationsidxid="w8343"book="_idx" docset="nw312" tidref="i4610"idxid="w8344"book="_idx" docset="nw312" tidref="i4769"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:ID="FM37891"Photocopy Table 3-1; then write down the configuration parameters you want to use on the photocopy.If you photocopied Table 3-1 as part of the procedure for requesting a PU definition (see IDREF="FM22885"page 2-21), continue to use the photocopy you created.Table 3-1 on IDREF="FM29053"page 3-5 divides the configuration parameters into host communication parameters and server and LAN configuration parameters.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-4 on IDREF="FM71351"page 2-23 provides additional information that can help the host systems programmer locate the host communication parameters for you.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 of the configuration parameters begin on IDREF="FM40596"page 3-7.LBL="3-1" INLINE="F"ID="FM29053"Configuration Parameters for Direct Host CommunicationsWIDTH="192"Host Communication ParametersWIDTH="96"StatusWIDTH="108"ValueWIDTH="192"Token Ring Destination Node AddressWIDTH="96"RequiredWIDTH="108"_____________________Token Ring Destination Service Access Point  (SAP)Required_____________________Block IDRequired for 937x  and 37xx  attachments_____________________PUID for Token Ring ConnectionRequired for 937x  and 37xx  attachments_____________________WIDTH="192"Server and LAN Configuration ParametersWIDTH="96"StatusWIDTH="108"ValuePeripheral Node Control Point (PCNP) NameOptional_____________________Token Ring Adapter TypeRequired _____________________Logical Adapter NameRequired_____________________Token Ring Service Access Point (SAP)Required_____________________Maximum Frame Size to Transmit InboundRequired_____________________If NVCONFIG is not running, start NVCONFIG as described on page 3-2.Novell recommends that you unload NMA for NetView before starting NVCONFIG. Configuration changes do not take effect until the next time NMA for NetView is loaded.When NVCONFIG displays the Communications Options menu, use the arrow keys to select NetView Host; then press <Enter>.The Token Ring Connection to Host configuration screen (Figure 3-2) appears.LBL="3-2"Token Ring Connection to Host ScreenFILE="nmaag011.pbm"Edit the host communication parameters.Use the arrow keys to select a parameter, then press <Enter> to edit the parameter. For some parameters, NVCONFIG displays a cursor; for others it displays a menu. When NVCONFIG displays a cursor, use the keyboard keys to edit the current value. When NVCONFIG displays a menu, use the arrow keys to select the new value; then press <Enter>.See "Parameter Descriptions for the Token Ring Connection to Host Screen," on IDREF="FM40596"page 3-7 for more information on each parameter.When all host communication parameters are set, press <Esc> to exit the Token Ring Connection to Host screen.If you changed any of the configuration options, the program displays a configuration box that prompts you to save your changes.In the Save Changes confirmation box, use the arrow keys to select Yes; then press <Enter>.NVCONFIG configures NMA for NetView for direct host communications, saves the configuration parameters, and displays a message to confirm that your changes are saved.Press <Esc> to clear the confirmation message.Press <Esc> again to exit the Communications Options menu and NVCONFIG.You must exit NVCONFIG before loading NMA for NetView.The configuration process is now complete. For instructions on loading NMA for NetView, see IDREF="FM23935"page 3-13.Parameter Descriptions for the ID="FM40596"Token Ring Connection to Host ScreenThe Token Ring Connection to Host screen 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 how to set the configuration parameters for the direct host communications.Block IDidxid="w8345"book="_idx" docset="nw312" tidref="i4769"idxid="w8346"book="_idx" docset="nw312" tidref="i1429"idxid="w8347"book="_idx" docset="nw312" tidref="i706"Set the block ID to match the corresponding value at the host. This hexadecimal number identifies the device type of the remote communication equipment. The number entered in this field must be three digits long. To specify a value less than three digits, supply leading zeros.When the NMA for NetView server communicates with the host through a 937x or 37xx attachment, the Block ID parameter must match the value that follows the IDBLK= statement in the switched PU definition. When the server communicates through a 3174 controller, the Block ID parameter is ignored; therefore, no entry is required.Logical Adapter Nameidxid="w8348"book="_idx" docset="nw312" tidref="i4769"idxid="w8349"book="_idx" docset="nw312" tidref="i1429"idxid="w8350"book="_idx" docset="nw312" tidref="i3416"Set this parameter to match the adapter that is entered into the AUTOEXEC.NCF file. This name must match the AUTOEXEC.NCF file's adapter name. The logical adapter name can be up to 16 alphanumeric and/or special characters.Maximum Frame Size to Transmit Inboundidxid="w8351"book="_idx" docset="nw312" tidref="i4769"idxid="w8352"book="_idx" docset="nw312" tidref="i1429"idxid="w8353"book="_idx" docset="nw312" tidref="i3747"This parameter sets the frame size for transmissions from NMA for NetView to the host. The default frame size is 265 bytes. Press <Enter> to display a list of frame sizes (Figure 3-3).LBL="3-3"Frame Size Choices for Transmitting Inbound DataFILE="nmaag012.pbm"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.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 of the NMA for NetView server.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 = 2298Peripheral Node Control Point Nameidxid="w8354"book="_idx" docset="nw312" tidref="i4769"idxid="w8355"book="_idx" docset="nw312" tidref="i1429"idxid="w8356"book="_idx" docset="nw312" tidref="i5069"The peripheral node control point (PNCP) name is an optional entry. In Systems Network Architecture (SNA) terms, the NetWare server is connected to the host as a peripheral node. A peripheral node contains a software entity called a control point, which controls the resources of the SNA peripheral node.If you enter a PNCP name, NMA for NetView sends the PNCP name to NetView in each alert. If you do not enter a PNCP name, NMA for NetView sends the default value, CPNAME.PUID for Token Ring Connectionidxid="w8357"book="_idx" docset="nw312" tidref="i4769"idxid="w8358"book="_idx" docset="nw312" tidref="i1429"idxid="w8359"book="_idx" docset="nw312" tidref="i5701"Set the PUID to match the corresponding PUID at the host. The hexadecimal number entered in this field must be five digits long. To specify a value less than five digits, supply leading zeros.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.Token Ring Adapter Typeidxid="w8360"book="_idx" docset="nw312" tidref="i4769"idxid="w8361"book="_idx" docset="nw312" tidref="i1429"idxid="w8362"book="_idx" docset="nw312" tidref="i6813"In this field, specify the type of adapter your server is using for the host connection. Press <Enter> to display your two choices, Primary and Alternate (Figure 3-4).LBL="3-4"Designation Choices of AdapterFILE="nmaag013.pbm"Select Primary if the token ring adapter type switch (on the adapter) has been set to Primary; select Alternate if the adapter type switch has been set to Alternate. (Refer to the token ring adapter manual for information on switch settings.)Token Ring Destination Node Addressidxid="w8363"book="_idx" docset="nw312" tidref="i4769"idxid="w8364"book="_idx" docset="nw312" tidref="i1429"idxid="w8365"book="_idx" docset="nw312" tidref="i6814"Set this parameter 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-4 on IDREF="FM71351"page 2-23 contains additional information that the host systems programmer can use to locate the correct value for this address.Token Ring Destination Service Access Pointidxid="w8366"book="_idx" docset="nw312" tidref="i4769"idxid="w8367"book="_idx" docset="nw312" tidref="i1429"idxid="w8368"book="_idx" docset="nw312" tidref="i6815"This is the two-digit SAP number for the host.Set this parameter to match the SAP ID of the host's token ring connection. Table 3-1 lists the communication parameters that your host systems programmer should provide. Table 2-4 on IDREF="FM71351"page 2-23 provides additional information that the host systems programmer can use to locate the correct value.Token Ring Service Access Pointidxid="w8369"book="_idx" docset="nw312" tidref="i4769"idxid="w8370"book="_idx" docset="nw312" tidref="i1429"idxid="w8371"book="_idx" docset="nw312" tidref="i6818"This is the two-digit SAP number for the server.Set this parameter to match the SAP ID of the server's token ring connection. Table 3-1 lists the communication parameters that your host systems programmer should provide. Table 2-4 on IDREF="FM71351"page 2-23 provides additional information that the host systems programmer can use to locate the correct value. idxid="w8372"book="_idx" docset="nw312" tidref="i4610"Configuring for NetView Collection Point Communicationsidxid="w8373"book="_idx" docset="nw312" tidref="i4610"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.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 communications, the collection point server provides the following information in all forwarded messages:The PNCP name assigned to the collection point serverThe model number of the collection point serverThe serial number of the collection point serverFor information on setting these parameters within NetWare for SAA see the NetWare for SAA v1.3 Administration Guide.To configure NMA for NetView for NetView collection point communications, use the following procedure:If NVCONFIG is not running, start NVCONFIG as described on IDREF="FM67803"page 3-2.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.When NVCONFIG displays the Communications Options menu, use the arrow keys to select NetView Collection Point; then press <Enter>.NVCONFIG displays the Connection to Collection Point dialog box (see Figure 3-5).LBL="3-5"ID="FM63444"Connection to Collection Point Dialog BoxFILE="nmaag014.pbm"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.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.Press <Esc> to exit the Connection to Collection Point dialog box.If you changed any of the configuration options, the program displays a confirmation box that prompts you to save your changes. If you do not want to save changes to the configuration, select No, and press <Enter>.In the Save Changes confirmation box, use the arrow keys to select Yes; then press <Enter>.NVCONFIG configures NMA for NetView for collection point server communications, saves the collection point server name, and displays a message to confirm that your changes are saved.Press <Esc> to clear the confirmation message.ID="FM65480"Press <Esc> again to exit the Communications Options menu and NVCONFIG.The configuration process is now complete; NMA for NetView is ready for loading.You must exit NVCONFIG before loading NMA for NetView.For instructions on loading NMA for NetView, see IDREF="FM23935"page 3-13. Instructions for automating the startup procedure appear on IDREF="FM84302"page 2-16.ID="FM66599"idxid="w8374"book="_idx" docset="nw312" tidref="i4610"idxid="w8375"book="_idx" docset="nw312" tidref="i4769"ID="FM23935"Loading NMA for NetViewidxid="w8376"book="_idx" docset="nw312" tidref="i4610"idxid="w8377"book="_idx" docset="nw312" tidref="i3335"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 begin on IDREF="FM33357"page 2-17.Every time you load NMA for NetView, you must first execute a series of commands. These commands are identified in "Preparing the NetWare v3.1x Server," which begins on IDREF="FM35353"page 2-9.To load NMA for NetView, enter the following command: :load nmanvNovell recommends that you automate the loading process for NMA for NetView by loading the software from the AUTOEXEC.NCF file. For more information on the AUTOEXEC. NCF file, see "Automating Server Startup" on IDREF="FM84302"page 2-16.ID="FM71501"Unloading NMA for NetViewidxid="w8378"book="_idx" docset="nw312" tidref="i4610"idxid="w8379"book="_idx" docset="nw312" tidref="i7082"idxid="w8380"book="_idx" docset="nw312" tidref="i4781"Unload NMA for NetView when you want toChange the configuration of NMA for NetView Remove the NMA for NetView software (see IDREF="FM69684"page 3-15)To unload NMA for NetView from the NetWare server, enter the following command: :nvdownNetWare displays a message informing you that NMANV.NLM has been unloaded.ID="FM31109"Administering NMA for NetView Remotelyidxid="w8381"book="_idx" docset="nw312" tidref="i4610"idxid="w8382"book="_idx" docset="nw312" tidref="i5788"idxid="w8383"book="_idx" docset="nw312" tidref="i5746"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:Make sure that the REMOTE and RSPX NLMs are loaded on the server installed with NMA for NetView. From your network workstation, log in as SUPERVISOR to the directory on the local network server containing the remote network files (usually SYS:SYSTEM).Start the RCONSOLE utility, and select the server installed with NMA for NetView.When the system console prompt appears on your workstation screen, load or unload NMA for NetView or start NVCONFIG as if you were sitting at the server console.See the information on RCONSOLE in the NetWare v3.1x System Administration Guide for more information on running RCONSOLE.ID="FM69684"Removing the NMA for NetView SoftwareRemove the NMA for NetView software whenUpgrading from a previous version of NMA for NetViewPreparing to install NetWare for SAATo remove NMA for NetView v1.3, use the NetWare INSTALL utility. When removing the software, the NetWare INSTALL utility deletes the NMA for NetView files from the server's SYS:SYSTEM directory and deletes entries from the internal NetWare bindery.To remove a previous version of NMA for NetView, follow the removal directions that came with that version. Do not use the NetWare INSTALL to remove versions of NMA for NetView previous to v1.3.Start the NetWare INSTALL Utility. Type :load installSelect Product Options from the Installation Options menu.Use the arrow keys to select NMANV v1.3.0 NMA for NetView from the Currently Installed Products listing.Press <Delete>.When the Uninstall NMANV prompt appears, select Yes to confirm the removal of NMA for NetView v1.3.LBL="A"Installing Code Points for NetWareidxid="w8384"book="_idx" docset="nw312" tidref="i4203"The code points allow NetView to display additional information about alerts that are received from NMA for NetView. This appendix describesHow to determine whether you need to install NetView code pointsAn overview of the installation procedureHow to install NetView code points on a Virtual Machine (VM) systemHow to install NetView code points on a Multiple Virtual Storage (MVS) systemDo You Need to Install?idxid="w8385"book="_idx" docset="nw312" tidref="i4229"idxid="w8386"book="_idx" docset="nw312" tidref="i1000"idxid="w8387"book="_idx" docset="nw312" tidref="i4197"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 higher, 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 Overviewidxid="w8388"book="_idx" docset="nw312" tidref="i1000"idxid="w8389"book="_idx" docset="nw312" tidref="i4229"This section provides a general overview of the installation process. Detailed procedures for the VM and MVS host systems appear later in this appendix.Figure A-1 shows the equipment you might need to use for installing the code points in NetView.LBL="A-1"Installation OverviewFILE="nmaag015.pbm"To install the code point messages, you must perform the following tasks:Task 1. Prepare to transfer files to the host:Install NetWare for SAA (or a product with similar features) on a network server so that you can access the host from a workstation on the NetWare LAN.Using NetWare 3270 LAN Workstation software with file transfer capabilities (or a product with similar features) on a LAN workstation, establish a host session and access the NetView RUN disk.Task 2. Install the code point messages:Using the NetWare 3270 LAN Workstation, transfer the code point files from NMA for NetView v1.3, Disk 2 to the NetView RUN disk.Using the NetWare 3270 LAN Workstation, compile the code point files.Using a NetView console or NetView on the NetWare 3270 LAN Workstation, edit the NetView startup command file.Using a NetView console or NetView on the NetWare 3270 LAN Workstation, restart NetView and set the NetView recording and viewing filters.Detailed instructions for these tasks appear in the following sections.ID="FM12034"Preparing for File Transfer (VM and MVS Installations)idxid="w8390"book="_idx" docset="nw312" tidref="i1000"idxid="w8391"book="_idx" docset="nw312" tidref="i4229"To prepare for transferring code point files to the host, follow the procedures below:Install NetWare for SAA (or a product with similar features) on a network server so that you can access the host from a workstation on the NetWare LAN.Locate the code point files onNMA for NetView v1.3, Disk 2.The files that you need are located in the CP directory on this diskette.On a LAN workstation, start up the NetWare 3270 LAN Workstation software (or a product with similar features) that has file transfer software installed.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 and one of the following software packages:NetWare 3270 LAN Workstation for Windows(tm) softwareNetWare 3270 LAN Workstation for DOS(tm) softwareA third-party product with similar featuresFile transfer software is integrated into NetWare 3270 LAN Workstation for Windows. When using NetWare 3270 LAN Workstation for DOS, use the SEND program to transfer files to the host.For additional information on using the NetWare 3270 LAN Workstation software and on transferring files, consult the documentation for the product you are using.Installing NetView Code Points on VM Systemsidxid="w8392"book="_idx" docset="nw312" tidref="i1000"idxid="w8393"book="_idx" docset="nw312" tidref="i4229"idxid="w8394"book="_idx" docset="nw312" tidref="i7309"Before starting the procedures in this section, complete the procedures in the preceding section, "Preparing for File Transfer (VM and MVS Installations)" on IDREF="FM12034"page A-4.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:Running a host session from the NetWare 3270 LAN Workstation, log on to MAINT.If you do not know how to log on to MAINT, contact your host systems programmer.Access the NetView RUN disk by entering the following command: ACCESS 334 AUsing the file transfer software on the NetWare 3270 LAN Workstation (or a product with similar features), 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.NCCBNJ92UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ93UTB.NCC BNJ93UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ94UTB.NCC BNJ94UTB NCCFLST A (ASCII RLF RECFM F SEND BNJ95UTB.NCC BNJ95UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ96UTB.NCC BNJ96UTB NCCFLST A (ASCII CRLF RECFM FRunning a host session from the NetWare 3270 LAN Workstation, 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=NOVELLRunning a host session from the Netware 3270 LAN Workstation, open the NetView startup command file for editing by entering the following command: XEDIT NETSTRT GCSWithin 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'Log on to a NetView console and shut down NetView by entering the following NetView command: CLOSE IMMEDThis command brings down NetView. To avoid untimely interruption of NetView services, consider performing this step during a scheduled maintenance period.When NetView has completed shutdown, log on to the NetView virtual machine. Then start up NetView by entering the following VM command: CP IPL GCSWhile 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 BNJ096UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ81UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ82UTB IS AVAILABLEThe preceding messages indicate that the code point files for NetWare are available. If these messages are directed to another console, they will not appear.Disconnect from the NetView virtual machine by entering the following command: #CP DISCLog on to NetView. When the main menu appears, select NPDA (Network Problem Determination Application) by entering NPDAFrom 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 impdTo display NetWare messages, you must set the recording and viewing filters each time NetView is started. To simplify NetView startup, enter these commands in a CLIST file.Installing NetView Code Points on MVS Systemsidxid="w8395"book="_idx" docset="nw312" tidref="i1000"idxid="w8396"book="_idx" docset="nw312" tidref="i4229"idxid="w8397"book="_idx" docset="nw312" tidref="i3971"Before starting the procedures in this section, complete the procedures in "Preparing for File Transfer (VM and MVS Installations") on IDREF="FM12034"page A-4.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, follow these steps:While running a host session from the NetWare 3270 LAN Workstation (or a product with similar features), log on with a Time Sharing Option (TSO) user ID that has sufficient access rights to be able to create or update a system data set such as SYS1.xxxx.Using this NetWare 3270 LAN Workstation 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:LRECL = 80RECFM = FBDirectory blocks should be 5Primary allocation should be at least one cylinder or the equivalent in fixed-block architecture (FBA) blocksSecondary allocation should be at least one cylinder or the equivalent in FBA blocksExit ISPF by entering =xUsing the file transfer software on the NetWare 3270 LAN Workstation, transfer the INSTALL.JCL file and the code point files to the host.When transferring 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 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 CRLFFrom a host terminal or a NetWare 3270 LAN Workstation host session and the ISPF editor, open the member 'SYS2.NTVW.CODE.POINTS (INSTALL)'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 on IDREF="FM40471"page A-12 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.Submit the job.After successful completion of this job, the code points load library member should be installed correctly.Log on to a NetView console and shut down NetView by entering the following command: CLOSE IMMEDThis command brings down NetView. To avoid untimely interruption of NetView services, consider performing this step during a scheduled system maintenance period.At the primary MVS operator console, start NetView by entering the following command: S CNMPROCWhile 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 BNJ096UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ81UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ82UTB IS AVAILABLELog on to NetView. When the NetView main menu appears, select NPDA by entering NPDAFrom the 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 impdTo display NetWare messages, you must set the recording and viewing filters each time NetView is started. To simplify NetView startup, enter these commands in a CSLIST file.LBL=" A-1"ID="FM40471"Code Point  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 FORMATTED AS 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=&REG.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)) //********************************************************************* //*  ASSEMBLE STEP //********************************************************************* //ASM     EXEC PGM=IFOX00,PARM='LOAD,NODECK,OBJECT', //             REGION=&REG.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=&REG.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 LBL="B"ID="FM36115"Using NetView Command Filteringidxid="w8398"book="_idx" docset="nw312" tidref="i1041"idxid="w8399"book="_idx" docset="nw312" tidref="i6098"idxid="w8400"book="_idx" docset="nw312" tidref="i6098"The NetView command filtering feature allows you to disable NetWare processing of select commands that may be sent by NetView operators. NetView command filtering is an extension of the NetView support features described in Chapter 1.To prepare for command filtering, you need to edit the sample command filter file or create a new command filter file. To enable the command filtering feature, you need to install the command filter file and restart NMA for NetView.If a command filter file is not installed on an NMA for NetView server, or if NMA for NetView is not restarted after the command filter file is installed, NMA for NetView processes all NetView commands that conform to the command security requirements.This appendix describes how command filtering works and how toEdit the sample command filter fileCreate a new command filter fileEnable command filteringThis chapter also lists and describes the commands that NetView operators can send to NetWare servers.How Command Filtering Worksidxid="w8401"book="_idx" docset="nw312" tidref="i1031"After command filtering is enabled, NMA for NetView may apply the following two levels of security to each NetView command it receives.NMA for NetView first examines the user ID in the NetView command. If the user ID has the proper status, NMA for NetView continues to process the command.NMA for NetView checks its internal table to see if the command is disabled by command filtering. If the command is not disabled, NMA for NetView processes the command.When a NetView operator sends a command that has been disabled by command filtering, NMA for NetView responds as follows:If the command does not include an attribute parameter, or if it includes a single attribute parameter that has been disabled, NMA for NetView rejects the command and sends the following message to the NetView operator: Cannot execute this NetView RuncmdIf the command 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.ID="FM64740"Editing the Sample Command Filter File idxid="w8402"book="_idx" docset="nw312" tidref="i1031"The sample command filter file is an ASCII text file that lists all the commands NetView operators can send to NetWare servers. Initially, this file does not disable NetWare processing for any commands. You can edit this file to disable processing for any or all commands.To edit the filter file, use the following procedure:Use a text editor or a word processor to open the file named NVCMDS.DB.This file is on NMA for NetView v1.3, Disk 2 in the DATABASE directory. This file is not automatically copied to the server during the installation process.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.Example B-1 lists some of the statements from the sample command filter file.LBL=" B-1"ID="FM97498"Sample Command  Filter File Entries  rem           The NetView Run Command Filtering File .... ;QUERY        SPX          VERSION ;QUERY        SPX          CONFIG ;QUERY        SPX          VERSION  The statements in the command filter file conform to the following rules:Each line in the file is a separate statement.Command statements disable a command and must contain two or three parameters in the form: action resource attribute_parameterIn the third line of IDREF="FM97498"Example B-1,action is QUERY, resource is SPX, andattribute_parameter 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 command affects.The action and resource parameters are required. When a command has one or more attribute parameters, you must enter one attribute parameter.The parameters for all commands are listed in "IDREF="FM52999"Command Tables" on IDREF="FM52999"page B-7. Descriptions of these commands begin on IDREF="FM23179"page B-14. Each command statement can disable one attribute parameter for a command. If a command has multiple attribute parameters, you must enter a separate command statement for each attribute parameter you want to disable.The letters in each statement may be entered in uppercase or lowercase. For example, REM is equivalent to rem, Rem, and ReM.When a statement begins with REM or a semicolon (;), the statement is a comment. NMA for NetView ignores comments. Comments affect the command statements as follows:When a command statement is preceded by REM or a semicolon, the statement is ignored and the command remains enabled.When a command statement is not preceded by REM or a semicolon, the command is disabled.Command parameters may be separated by space or tab characters.Disable each command you want to disable by removing any comment characters (REM or a semicolon) at the beginning of the command statement.If you want to enable a disabled command, make the command statement a comment (using REM or a semicolon) or delete the command statement.Save the ASCII file.The ASCII file must be named NVCMDS.DB.Creating a Command Filter File idxid="w8403"book="_idx" docset="nw312" tidref="i1031"A command filter file is an ASCII text file that lists all the commands you want to disable. To create a command filter file, use the following procedure:Use a text editor or a word processor to create a new file named NVCMDS.DB.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.In the ASCII file, add command and comment statements.The command and comment statements operate as described in Step 1 of the preceding section, "IDREF="FM64740"Editing the Sample Command Filter File."Save the ASCII file.The ASCII file must be named NVCMDS.DB.Enabling Command Filtering idxid="w8404"book="_idx" docset="nw312" tidref="i1031"To enable command filtering, edit or create a command filter file, and then use the following procedure:Place a copy of the NVCMDS.DB command filter file in the server's SYS:\SYSTEM\COMMEXEC directory.Restart NMA for NetView.During initialization, NMA for NetView examines each line of the command filter file. Comment lines are ignored. Valid entries are registered in an internal table within NMA for NetView. If a command line contains an error, NMA for NetView displays the following message on the NetWare system console: Invalid NetView RunCmd entry: xxxxxxx xxxxxxx<CR><LF>Command line errors also appear in the log file if event logging is enabled.Invalid entries are ignored. Invalid entries do not disable the command you intended to disable.ID="FM52999"Command Tables idxid="w8405"book="_idx" docset="nw312" tidref="i1031"The tables in this section list commands that the NetView operator can send to NetWare. IDREF="FM42626"Table B-1 lists these commands according to the action they perform. IDREF="FM54600"Table B-2 lists commands according to the resource upon which an action is performed.The commands in the following tables include all parameters that the NetView operator can send to NetWare. When you enter a command statement in a command filter file, enter only the action, resource, and attribute parameter. When you enter an attribute parameter, do not include the equal symbol (=) or any italicized characters that appear in these tables.LBL="B-1" INLINE="F"ID="FM42626"idxid="w8406"book="_idx" docset="nw312" tidref="i1031"NetWare Commands Sorted by ActionWIDTH="72"ActionWIDTH="72"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="72"AddWIDTH="72"DirectoryWIDTH="84"TrusteeWIDTH="84"Path=pathWIDTH="84"UserName=unameRights=[ACEFMRSW]AddFileTrusteePath=pathUserName=unameRights=[ACEFMRSW]AddVolumeTrusteeVolName=vnameUserName=unameRights=[ACEFMRSW]BroadcastServerMsg="message"[UserName=uname]DisableServerLoginDisableTTSDownServer[Opts=[01]]EnableServerLoginEnableTTSLoadNLMNLMName=name[Args="argument"]QueryDirectoryPath=pathQueryDirectoryRightsPath=pathUserName=unameQueryDirectorySpaceAllowedPath=pathQueryFilePath=path[UserName=uname]QueryFileRightsPath=pathUserName=unameQueryIPXVersionQueryServerQueryServerDate   =spaceVolName=vnameUserName=unameSetVolumeNoRestriction VolName=vnameUserName=unameUnLoadNLMNLMName=nameLBL="B-2" INLINE="F"ID="FM54600"NetWare Commands Sorted by Resource idxid="w8407"book="_idx" docset="nw312" tidref="i1031"WIDTH="72"ActionWIDTH="72"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="72"AddWIDTH="72"DirectoryWIDTH="84"TrusteeWIDTH="84"Path=pathWIDTH="84"UserName=unameRights=[ACEFMRSW]QueryDirectoryPath=pathQueryDirectoryRightsPath=pathUserName=unameQueryDirectorySpaceAllowedPath=pathRemoveDirectoryTrusteePath=pathUserName=unameSetDirectoryADate=dateArDate=dateArTime=timeCDate=dateCTime=timeOwner=nameUDate=dateUTime=timePath=pathSetDirectorySpaceAllowed=spacePath=pathAddFileTrusteePath=pathUserName=unameRights=[ACEFMRSW]QueryFilePath=path[UserName=uname]QueryFileRightsPath=pathUserName=unameRemoveFileTrusteePath=pathUserName=unameSetFileADate=dateArDate=dateArTime=timeCDate=dateCTime=timeOwner=nameUDate=dateUTime=timePath=pathQueryIPXVersionLoadNLMNLMName=name[Args="argument"]UnLoadNLMNLMName=nameBroadcastServerMsg="message"[UserName=uname]DisableServerLoginDownServer[Opts=[01]]EnableServerLoginQueryServerQueryServerDate TimeQueryServerInternetAddrQueryServerLoginStatusQueryServerNumOfVolsQueryServerVolumesSetServerDate=dateTime=timeQuerySPXConfigQuerySPXVersionDisableTTSEnableTTSQueryTTSStatusQueryUserDiskSpaceLeftUserName=unameVolName=vnameQueryUserDiskUsageUserName=unameVolName=vnameAddVolumeTrusteeVolName=vnameUserName=unameRights=[ACEFMRSW]QueryVolumeVolName=vnameQueryVolumeDiskUsageVolName=vnameUserName=unameQueryVolumeUSpaceAllowedVolName=vnameUserName=unameRemoveVolumeTrusteeVolName=vnameUserName=unameSetVolumeUSpaceAllowed =spaceVolName=vnameUserName=unameSetVolumeNoRestriction VolName=vnameUserName=unameID="FM23179"Command Descriptions idxid="w8408"book="_idx" docset="nw312" tidref="i1031"for NetWare ServersThis section describes the commands NetView operators can send to NetWare.The following command descriptions include tables and examples that list all parameters that the NetView operator sends to NetWare. When you enter a command statement in a command filter file, enter only the action, resource, and attribute parameter. When you enter an attribute parameter, do not include the equal symbol (=) or any italicized characters that appear in these tables.ADD DIRECTORY, FILE, or VOLUME TRUSTEEThe idxid="w8409"book="_idx" docset="nw312" tidref="i143"ADD command allows the NetView operator to add a trustee to a directory, file, or volume on a NetWare server. IDREF="FM23455"Table B-3 shows the format of the commands that add trustees to a directory, file, or volume.LBL="B-3" INLINE="F"ID="FM23455"NetWare ADD CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"AddWIDTH="84"DirectoryWIDTH="84"TrusteeWIDTH="84"Path=pathWIDTH="84"UserName=unameRights=[ACEFMRSW]AddFileTrusteePath=pathUserName=unameRights=[ACEFMRSW]AddVolumeTrusteeVolName=vnameUserName=unameRights=[ACEFMRSW]BROADCASTThe idxid="w8410"book="_idx" docset="nw312" tidref="i765"BROADCAST command sends a message to a NetWare workstation user. The format of the command is Broadcast Server Msg="message" UserName=unameThis command does not have an attribute parameter. To disable this command in a command filter file, enter Broadcast Server.DISABLE SERVER LOGIN or TTSThe idxid="w8411"book="_idx" docset="nw312" tidref="i1534"DISABLE command can be used to disable server login by workstations or to disable the Transaction Tracking System (TTS). IDREF="FM20641"IDREF="FM50070"Table B-4 shows the format for the DISABLE SERVER LOGIN and DISABLE TTS commands.ID="FM20641"LBL="B-4" INLINE="F"ID="FM50070"NetWare DISABLE CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"DisableWIDTH="84"ServerWIDTH="84"LoginWIDTH="84"WIDTH="84"DisableTTSDOWN SERVERThe idxid="w8412"book="_idx" docset="nw312" tidref="i1721"DOWN SERVER command brings down the NetWare server. The format for this command is Down Server [Opts=[01]]This command does not have an attribute parameter; to disable this command, enter DOWNSERVER in the command filter file. Also, the server may shut down before it responds to the DOWN SERVER command. If the server shuts down, the NetView operator may receive a command timeout message.ENABLE SERVER LOGIN or TTSThe idxid="w8413"book="_idx" docset="nw312" tidref="i1814"ENABLE command can be used to enable server login by workstations or to enable the Transaction Tracking System (TTS). IDREF="FM24015"Table B-5 shows the format for the ENABLE SERVER LOGIN and ENABLE TTS commands.LBL="B-5" INLINE="F"ID="FM24015"NetWare ENABLE CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"EnableWIDTH="84"ServerWIDTH="84"LoginWIDTH="84"WIDTH="84"EnableTTSLOAD NLMThe idxid="w8414"book="_idx" docset="nw312" tidref="i3238"LOAD command loads an NLM. IDREF="FM27659"Table B-6 lists the format for the LOAD NLM command.LBL="B-6" INLINE="F"ID="FM27659"NetWare LOAD CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"LoadWIDTH="84"NLMWIDTH="84"NLMName=nameWIDTH="84"WIDTH="84"[Args="argument"]If the NetView operator sends a idxid="w8415"book="_idx" docset="nw312" tidref="i3238"LOAD command with an incomplete set of parameters for an NLM, a prompt for the missing parameters appears on the system console. The NLM does not continue execution until the missing information is entered at the system console. The NetView operator is not notified about the missing parameters, and the NLM may appear to be operating when it is not.QUERY DIRECTORYAs shown in IDREF="FM17890"Table B-7, the idxid="w8416"book="_idx" docset="nw312" tidref="i5704"QUERY DIRECTORY command has three forms.LBL="B-7" INLINE="F"ID="FM17890"NetWare QUERY DIRECTORY CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"QueryWIDTH="84"DirectoryWIDTH="84"WIDTH="84"Path=pathWIDTH="84"QueryDirectoryRightsPath=pathUserName=unameQueryDirectorySpaceAllowedPath=pathWhen the QUERY DIRECTORY command is used without an attribute parameter, the command returns the following information:Volume where the directory residesDirectory ownerInherited rights maskAccess date and timeModification date and timeCreation date and timeArchive date and timeOwner rightsThe QUERY DIRECTORY RIGHTS command returns the rights assigned to the specified NetWare user for the specified directory.The QUERY DIRECTORY SPACEALLOWED command returns the amount of available space in the specified directory and the amount of space reserved for the directory.QUERY FILEAs shown in IDREF="FM37771"Table B-8, the idxid="w8417"book="_idx" docset="nw312" tidref="i5705"QUERY FILE command has two forms.LBL="B-8" INLINE="F"ID="FM37771"NetWare QUERY FILE CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"QueryWIDTH="84"FileWIDTH="84"WIDTH="84"Path=pathWIDTH="84"[UserName=uname]QueryFileRightsPath=pathUserName=unameWhen the QUERY FILE command does not include an attribute parameter, the command returns the following information:Volume where the file residesModeAttributesSizeOwnerInherited rights maskAccess date and timeModification date and timeArchive date and timeCreation date and timeName space valuesUser rights when a user name is included (optional)When the QUERY FILE command includes the Rights attribute parameter, the command returns only the rights assigned to the specified user.QUERY IPX VERSIONThe idxid="w8418"book="_idx" docset="nw312" tidref="i5706"QUERY IPX command returns the IPX version information. The format for this command is Query IPX VersionQUERY SERVERIDREF="FM33375"Table B-9 lists the idxid="w8419"book="_idx" docset="nw312" tidref="i5707"QUERY SERVER commands.LBL="B-9" INLINE="F"ID="FM33375"NetWare QUERY SERVER CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"QueryWIDTH="84"ServerWIDTH="84"WIDTH="84"WIDTH="84"QueryServerDate TimeQueryServerInternetAddrQueryServerLoginStatusQueryServerNumOfVolsQueryServerVolumesWhen the QUERY SERVER command is used without an attribute parameter, the command returns the following information:NetWare version numberMaximum number of connections supportedNumber of connections in useSystem Fault Tolerance (SFT) levelTTS levelMaximum number of volumes supportedSecurity restriction levelWhen the QUERY SERVER command includes one or more attribute parameters, NetWare returns the information requested by each parameter (see IDREF="FM56815"Table B-10).LBL="B-10" INLINE="F"ID="FM56815"QUERY SERVER Attribute ParametersWIDTH="120"Attribute ParameterWIDTH="192"Information Sent to NetViewWIDTH="120"DateWIDTH="192"The server date.InternetAddrThe network and node addresses of the  server.LoginStatusThe server login status. The status is either  enabled or disabled.NumOfVolsThe number of server volumes.TimeThe server time.VolumesA list of the volumes mounted on the server.QUERY SPXAs shown in IDREF="FM29229"Table B-11, the idxid="w8420"book="_idx" docset="nw312" tidref="i5708"QUERY SPX command has two forms.LBL="B-11" INLINE="F"ID="FM29229"NetWare QUERY SPX CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"QueryWIDTH="84"SPXWIDTH="84"ConfigWIDTH="84"WIDTH="84"QuerySPXVersionThe QUERY SPX CONFIG command returns the maximum number of SPX connections supported and the number of available connections. The QUERY SPX VERSION command returns the SPX version number.QUERY TTSThe idxid="w8421"book="_idx" docset="nw312" tidref="i5709"QUERY TTS command returns the status of the Transaction Tracking System (TTS), which is either enabled or disabled. The format for this command is Query TTS StatusQUERY USERThe idxid="w8422"book="_idx" docset="nw312" tidref="i5710"QUERY USER command has two forms (see IDREF="FM12902"Table B-12).LBL="B-12" INLINE="F"ID="FM12902"NetWare QUERY USER CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"QueryWIDTH="84"UserWIDTH="84"DiskSpaceLeftWIDTH="84"UserName=unameWIDTH="84"VolName=vnameQueryUserDiskUsageUserName=unameVolName=vnameThe QUERY USER DISKSPACELEFT command returns the amount of remaining volume disk space allocated to the user. The QUERY USER DISKUSAGE command returns the number of directories, files, and blocks being used by a user.QUERY VOLUMEIDREF="FM40076"Table B-13 lists the three forms of the idxid="w8423"book="_idx" docset="nw312" tidref="i5711"QUERY VOLUME command.LBL="B-13" INLINE="F"ID="FM40076"NetWare QUERY VOLUME CommandsWIDTH="72"ActionWIDTH="72"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="72"QueryWIDTH="72"VolumeWIDTH="84"WIDTH="84"VolName=vnameWIDTH="84"QueryVolumeDiskUsageVolName=vnameUserName=unameQueryVolumeUSpaceAllowedVolName=vnameUserName=unameWhen used without an attribute parameter, the QUERY VOLUME command returnsVolume numberNumber of sectors per blockTotal number of blocksStarting block numberTotal available blocksTotal directory slotsAvailable directory slotsMaximum directory slots usedVolume status (for example, mounted, hashing, or removable)When the QUERY VOLUME command includes one or both attribute parameters, the command returns the information requested by the parameters. The DiskUsage parameter returns the number of directories, files, and blocks being used by a user. The USpaceAllowed parameter returns the amount of space allowed to the specified user.REMOVE DIRECTORY, FILE, or VOLUME TRUSTEEThe idxid="w8424"book="_idx" docset="nw312" tidref="i5851"REMOVE command allows the NetView operator to remove a trustee from a directory, file, or volume on a NetWare server. IDREF="FM33020"Table B-14 shows the format of the commands that remove trustees.LBL="B-14" INLINE="F"ID="FM33020"NetWare REMOVE CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"RemoveWIDTH="84"DirectoryWIDTH="84"TrusteeWIDTH="84"Path=pathWIDTH="84"UserName=unameRemoveFileTrusteePath=pathUserName=unameRemoveVolumeTrusteeVolName=vnameUserName=unameSET DIRECTORYThe idxid="w8425"book="_idx" docset="nw312" tidref="i6293"SET DIRECTORY commands allow the NetView operator to set one or more properties of a directory with a single command. IDREF="FM21598"Table B-15 shows the format of the SET DIRECTORY commands.LBL="B-15" INLINE="F"ID="FM21598"NetWare SET DIRECTORY CommandsWIDTH="72"ActionWIDTH="72"ResourceWIDTH="84"AttributeParametersWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="72"SetWIDTH="72"DirectoryWIDTH="84"ADate=dateArDate=dateArTime=timeCDate=dateCTime=timeOwner=nameUDate=dateUTime=timeWIDTH="84"Path=pathWIDTH="84"SetDirectorySpaceAllowed=spacePath=pathThe attribute parameters in IDREF="FM21598"Table B-15 define the directory properties to be set. IDREF="FM10943"Table B-16 shows the properties that each attribute parameter controls.LBL="B-16" INLINE="F"ID="FM10943"SET DIRECTORY Attribute ParametersWIDTH="120"Attribute ParameterWIDTH="192"Property DefinedWIDTH="120"ADate=dateWIDTH="192"File access date. Replace the date variable  with the new access date for the file.ArDate=dateFile archive date. Replace the date variable  with the new archive date for the file.ArTime=timeFile archive time. Replace thetime variable  with the new archive time for the file.CDate=dateDirectory creation date. Replace thedate  variable with the new creation date for the  directory.CTime=timeDirectory creation time. Replace the time variable with the new creation time for the  directory.Owner=nameDirectory owner. Replace thename variable with the user ID for the new owner  of the directory.UDate=dateFile update date. Replace thedate variable  with the new update date for the file.UTime=timeFile update time. Replace the time variable  with the new update time for the file.SpaceAllowed=spaceThe maximum space allowed for all files  and subdirectories within the directory.  Replace the space variable with a number  that represents the maximum size of the  directory. You cannot specify unlimited  space; you must specify a value.SET FILEThe idxid="w8426"book="_idx" docset="nw312" tidref="i6294"SET FILE command allows the NetView operator to set one or more properties of a file with a single command. IDREF="FM20515"Table B-17 shows the format of the SET FILE command.LBL="B-17" INLINE="F"ID="FM20515"NetWare SET FILE CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParametersWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"SetWIDTH="84"FileWIDTH="84"ADate=dateArDate=dateArTime=timeCDate=dateCTime=timeOwner=nameUDate=dateUTime=timeWIDTH="84"Path=pathWIDTH="84"The attribute parameters in IDREF="FM20515"Table B-17 define the directory properties to be set. IDREF="FM25101"Table B-18 shows the properties that each attribute parameter controls.LBL="B-18" INLINE="F"ID="FM25101"SET FILE Attribute ParametersWIDTH="120"Attribute ParameterWIDTH="192"Property DefinedWIDTH="120"ADate=dateWIDTH="192"File access date. Replace the date variable  with the new access date for the file.ArDate=dateFile archive date. Replace thedate variable  with the new archive date for the file.ArTime=timeFile archive time. Replace thetime variable  with the new archive time for the file.CDate=dateFile creation date. Replace the date variable  with the new creation date for the file.CTime=timeFile creation time. Replace the time variable  with the new creation time for the file.Owner=nameFile owner. Replace thename variable with  the user ID for the new owner of the file.UDate=dateFile update date. Replace thedate variable  with the new update date for the file.UTime=timeFile update time. Replace the time variable  with the new update time for the file.SET SERVERThe idxid="w8427"book="_idx" docset="nw312" tidref="i6300"SET SERVER commands allow you to set one or more properties of a server with a single command. IDREF="FM40513"Table B-19 shows the Set Server commands.LBL="B-19" INLINE="F"ID="FM40513"NetWare SET SERVER CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParametersWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"SetWIDTH="84"ServerWIDTH="84"Date=dateTime=timeWIDTH="84"WIDTH="84"The date and time attribute parameters allow the NetView operator to set the date and time at the server. SET VOLUMEAs shown in IDREF="FM38671"Table B-20, the idxid="w8428"book="_idx" docset="nw312" tidref="i6304"SET VOLUME command has two forms.LBL="B-20" INLINE="F"ID="FM38671"SET VOLUME Attribute ParametersWIDTH="72"ActionWIDTH="72"ResourceWIDTH="84"AttributeParametersWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="72"SetWIDTH="72"VolumeWIDTH="84"USpaceAllowed=spaceWIDTH="84"VolName=vnameWIDTH="84"UserName=unameSetVolumeNoRestriction VolName=vnameUserName=unameThe SET VOLUME USPACEALLOWED command defines the total amount of space that can be allocated to the specified user on the specified volume. The SET VOLUME NOSPACERESTRICTION command removes all restrictions on the amount of space the specified user can use on the specified volume.ID="FM10411"UNLOAD NLMidxid="w8429"book="_idx" docset="nw312" tidref="i7074"This command unloads an NLM. IDREF="FM11795"Table B-21 lists the format for the UNLOAD NLM command.LBL="B-21" INLINE="F"ID="FM11795"NetWare Unload CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"UnLoadWIDTH="84"NLMWIDTH="84"NLMName=nameWIDTH="84"WIDTH="84"idxid="w8430"book="_idx" docset="nw312" tidref="i7074"If the NetView operator sends an UNLOAD command for an NLM, the command will fail if the NLM is exporting functions and symbols to another NLM. If the UNLOAD command fails, a message appears on the system console. The NetView operator is not notified about the failure, and the NLM may appear to be unloaded when it is n idxid="w8431"book="_idx" docset="nw312" tidref="i1041"idxid="w8432"book="_idx" docset="nw312" tidref="i6098"idxid="w8433"book="_idx" docset="nw312" tidref="i6098"ot.idxid="w8434"book="_idx" docset="nw312" tidref="i1031"