#EDIR DATA#
NetWare Reference for NetViewDisclaimerNovell®, 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 GuideThis guide describesThe NetWare products that support NetView network managementThe alert messages NetWare products send to NetViewThe commands NetWare accepts from NetViewHow to install NetWare code point messages for NetViewWho Should Read This GuideThis guide is written for the NetView operator. Read this guide if you want toLearn about NetWare products that support NetView network managementLearn more about the alert messages NetWare sends to NetViewSend commands to a NetWare serverInstall NetView code pointsContent OverviewChapter 1, About NetWare Support for NetView: Describes the NetWare products that support NetView, introduces the new features in version 1.3 of these products, and describes the complete set of NetView support features provided by all versions of these products.Chapter 2, Alert Message Descriptions: Lists the alert messages that NetWare servers can send to NetView. Each message appears with a description of the alert's cause, a suggested action to take, and the corresponding NetWare message that appears at the NetWare server console.Chapter 3, Sending NetWare Commands: Describes how to send commands to NetWare servers. This chapter lists commands alphabetically by command action and by server component and provides a description of each command.Appendix A, Installing NetWare Code Point Messages for NetView: Provides the procedure for installing NetWare code points for NetView. This procedure may not be required for your installation.ConventionsThis guide uses a variety of typographical and symbolic conventions.Typographic ConventionsThis book uses the following typographic conventions. The bold monospace convention used in Chapter 2, as explained below, however, varies from that used in the rest of the book.WIDTH="108"Bold monospaceWIDTH="300"When in bold, monospace font indicates commands that you  enter at a prompt or select from a menu. For example:RUNCMDThe letters and symbols that appear in the bold monospace  typeface must be entered exactly as shown.In Chapter 2, bold monospace type is used to show text that  appears in the NetView Recommended Action for Selected  Event panel.MonospaceWhen 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 variable userid with a valid NetWare user ID.[ ]Square brackets enclose optional values. Do not enter the brackets.  When an option appears in bold monospace, enter the option as  described in the command description. For example:Rights=[ACEFMRSW]In this example, you can enter any or all of the letters that appear  between the brackets. Do not enter the brackets.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.An Important symbol denotes important information that you should read. It's also a visual cue to key concepts and facts.A Warning 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 NetWare products that you can manage with NetView.The NetWare for SAA v1.3 Administration Guide (100-001166-002) describes the NetView support features in NetWare for SAA` v1.3.The NetWare for SAA v1.2 Administration Guide (100-001166-001) describes the NetView support features in NetWare for SAA v1.2.The NetWare Management Agent for NetView Administration Guide (100-001479-002) describes the NetView support features in NMA for NetView v1.3.An ASCII version of the NetWare Management Agent for NetView Administration Guide is provided with a patch version of NMA for NetView v1.3 that supports NetWare v3.11. This version is distributed on the NetWare Express` online software subscription service.The first edition of this manual is supplied with NetWare v3.11 and describes NMA for NetView v1.0.NetWare Version 3.11 ConceptsNetWare Version 3.11 InstallationNetWare Version 3.11 System AdministrationNetWare Version 3.11 Utilities ReferenceBundled with NetWare v3.11 and v3.12, these books provide information on managing a NetWare local area network (LAN) and on NetWare LAN concepts.NetWare v3.12 ConceptsNetWare v3.12 InstallationNetWare v3.12 System AdministrationNetWare v3.12 Utilities ReferenceBundled with NetWare v3.12, these books provide information on managing a NetWare local area network (LAN) and on NetWare LAN concepts.NetWare 4.0 Utilities ReferenceNetWare 4.0 ConceptsBundled with NetWare v4.0, these books provide information on managing a NetWare LAN and on NetWare LAN concepts.LBL="1"About NetWare Support for NetViewThis chapter introducesThe NetWare products that support NetView network managementThe new features in version 1.3 for NetWare support of NetViewThe complete set of features for NetWare support of NetViewNetWare Products That Support NetViewThe following NetWare products support NetView network management:NetWare for SAA` communication serviceNetWare Management Agent (NMA) for NetViewNetWare for SAA must run in a NetWare server (v3.1x or v4.0). NMA for NetView runs on a NetWare v3.1x server. The following subsections describe NetWare servers, NetWare for SAA, and NMA for NetView.NetWare v3.1x is any version of NetWare later than v3.1 and earlier than v4.0 (for example, NetWare v3.11 or NetWare v3.12).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 idxid="w4102"book="_idx" docset="nw312" tidref="i4159"idxid="w4103"book="_idx" docset="nw312" tidref="i4201"NET/MASTER network management program from Systems Center is an example of a program that is designed to be compatible with NetView.NetWare ServersNetWare servers are software products that provide local area network (LAN) communications for personal computers. NetWare v3.11 was the first version that participated in NetView network management. NetWare v4.0 also participates in NetView network management. Throughout this guide, the term NetWare server refers to a server running NetWare v3.11 or later.NetWare servers do not independently support NetView. To support NetView, the NetWare server must be operating with either NetWare for SAA or NMA for NetView.Each NetWare server package provides software forOne NetWare serverMultiple NetWare workstationsThe server provides the following services to workstations:File services. Workstation users can use disk space on the server as if the space were a hard disk mounted on the workstation. Because many users can use the same disk space, the file services feature allows workstation users to share files. Security features on the server allow the NetWare administrator to control how users access the server disk space.Print services. Workstation users can send print jobs to a printer attached to the server. The server receives all print jobs, places the jobs in a queue, and prints the jobs in order.Additional services. The NetWare server software is an operating system that supports LAN communications for additional network services such as NetWare for SAA and NMA for NetView.The NetWare v3.12 package includes NMA for NetView v1.3, which is described later in this chapter.NetWare for SAANetWare for SAA is a software product that runs as an additional service in a NetWare server.NetWare for SAA v1.3 or later is required in servers that run NetWare v4.0. NetWare v4.0 is not compatible with earlier versions of NetWare for SAA.NetWare for SAA providesCommunications between workstations and other computers using IBM's Systems Application Architecture (SAA) softwareNetView support services, which are described later in this chapterNovell's implementation of SAA allows NetWare workstations to communicate with 3270 host computers and AS/400 host computers. NetWare for SAA also supports LU6.2 communications between NetWare workstations and other computers.Throughout this guide, the term NetWare for SAA server refers to a NetWare server that is running both NetWare server software and NetWare for SAA.NMA for NetViewNMA for NetView is a software product that runs as an additional service in a NetWare server. NMA for NetView provides NetView support services, which are described later in this chapter.Throughout this guide, the term NMA for NetView server refers to a NetWare server that is running both NetWare server software and NMA for NetView.NMA for NetView v1.0 is bundled with NetWare v3.11; NMA for NetView v1.2 is distributed via the NetWare Express online software subscription service. NMA for NetView v1.3 is bundled with NetWare v3.12. A patch release of NMA for NetView v1.3 that runs with NetWare v3.11 is distributed via NetWare Express.What Is New in Version 1.3?NetWare for SAA v1.3 and NMA for NetView v1.3 provide the following new NetView support features:Support for NetWare v4.0 (NetWare for SAA only).Additional alerts for the NetWare operating system and its component services. Also, some alert messages are changed.Additional commands for requesting server status and controlling some server features.A command filtering feature for disabling NetView access to one or more server commands.Support for NetWare for SAA v1.2 end point servers (NetWare for SAA only).Alert and command forwarding for applications that use the NetWare Open NetView interface.These features are described with the complete set of NetView support features in the next section.NetView Support FeaturesThe NetView support features in NetWare for SAA and NMA for NetView allow you, the NetView operator, to manage NetWare servers from your NetView console. IDREF="FM39432"Figure 1-1 on the next page shows how a NetWare server participates in NetView network management.LBL="1-1"ID="FM39432"NetView Support in a NetWare ServerFILE="nvorg001.pbm"The NetWare server in IDREF="FM39432"Figure 1-1 can be a NetWare for SAA server or an NMA for NetView server. The options for connecting a NetWare server to NetView are described later in this chapter in "IDREF="FM22261"Host Connectivity Options."NetWare for SAA and NMA for NetView provide the following features for NetView support:Alert generationCommand processingHost connectivity optionsFeature controlSupport for the Open NetView interfaceAlert GenerationAlerts are messages that are sent from NetWare servers to NetView. NetWare alerts appear in the following NetView Network Problem Determination Application (NPDA) panels:Alerts-DynamicAlerts-StaticAlerts-HistoryNetWare for SAA and NMA for NetView translate selected NetWare error and status messages into alerts for the following server processes:The TOKEN.LAN driver supplied with NetWare serversLogical link control (LLC) protocol components of token ring driversLLC protocol components of Synchronous Data Link Control (SDLC) drivers and Qualified Logical Link Control (QLLC) drivers (NetWare for SAA servers only)The NetWare operating system and file servicesNetWare alerts describe the operation of the NetWare server. The NetView support feature does not monitor, report, or control the status of NetWare LAN workstations. However, the server may forward alerts and commands for other applications that perform these functions (see "IDREF="FM70522"Support for the Open NetView Interface," later in this chapter).The NetWare alerts are listed in Chapter IDREF="FM37278"2, "IDREF="FM37278"Alert Message Descriptions." Each message description in Chapter IDREF="FM37278"2 includes the alert, an explanation of the alert's cause, a suggested action, and the corresponding NetWare message that appears on the server console.Command ProcessingCommands are messages that you send from NetView to a NetWare server via the NetView Network Communications Control Facility (NCCF). NetWare for SAA and NMA for NetView translate each NetView command into a NetWare command. After translation, the NetWare command is forwarded to the server component that normally executes the command.The command processing feature is provided in NetWare for SAA v1.2 and later and in NMA for NetView v1.2 and later. Earlier versions of these products cannot process commands.Command response messages contain information about the server or about the result of a server command. After a server processes a command from NetView, NetWare for SAA or NMA for NetView builds a command response, embeds it in a NetView message, and sends it to NetView.NetWare servers process two types of commands:Server query commandsServer control commandsThis section describes the actions these commands produce. For detailed information on sending commands, see Chapter IDREF="FM36115"3.All the commands described in the following sections may be executed with NetWare for SAA v1.3 when the destination server is running NetWare v4.0. If the destination server is running NetWare for SAA v1.2, NMA for NetView v1.2, NMA for NetView v1.3, or NetWare v3.1x, some commands are not supported. The command tables and command descriptions in Chapter 3, "Sending NetWare Commands," identify which commands can be used with which servers.Server Query CommandsServer query commands request command responses that contain information about server resources. These commands allow you to query forServer information such as the server date, server time, number of volumes on a server, the server's login status, and the server's internetwork addressVolume information such as the volume number and configuration, 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 number of a communication service, the Sequenced Packet Exchange (SPX) protocol, or the Internetwork Packet Exchange (IPX) protocolSome server configuration parametersThe configuration of the SPX protocolThe status of the Transaction Tracking Service (TTS)Server Control CommandsServer control commands allow you toEnable or disable server login, shut down a server, and broadcast a message to server usersSet the server date, server time, and a variety of server control parametersSet the volume space allowed to a user and add or remove a trustee 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 TTSLoad and unload a NetWare Loadable Module` (NLM`) productLoad or unload a communication serviceCommand SecurityBoth NetWare for SAA and NMA for NetView provide a command security feature. The command security feature checks each command you send for a valid NetWare user ID. If the command contains a valid user ID, the server executes the command. If the user ID is missing or invalid, the command is ignored.The command security feature is provided in NetWare for SAA v1.2 and later and in NMA for NetView v1.2 and later. Earlier versions of these products cannot process commands.NetWare for SAA allows the server administrator to enable or disable command security. When the command security feature is disabled, NetWare for SAA ignores the user ID and processes all commands.The command security feature in NMA for NetView is always enabled.IDREF="FM14388"Table 1-1 shows the NetWare user ID status required for command processing when the command security feature is enabled.LBL="1-1" INLINE="F"ID="FM14388"NetWare User ID Status for Command ProcessingWIDTH="120"Server Command TypeWIDTH="192"NetWare User ID Status Required for ProcessingWIDTH="120"QueryWIDTH="192"File server console operator or supervisorControlSupervisorWhen the command security feature is enabled, a command must include a user ID (other than SUPERVISOR) with either supervisor-equivalent privileges or file server console operator status. Although the SUPERVISOR user ID has supervisor-equivalent privileges, the server rejects commands that include the SUPERVISOR user ID.ID="FM27394"Command FilteringThe command-filtering feature allows the NetWare administrator to disable processing of select commands that you send to NetWare. The NetWare administrator can disable any number of commands by listing them in a file that the NetWare server reads when loading.The command-filtering feature is new in NetWare for SAA v1.3 and NMA for NetView v1.3. Earlier versions of these products do not support command filtering.When you send a command with attribute parameters that have been disabled by command filtering, NetWare for SAA responds as follows:If the command includes a single attribute parameter that has been disabled, NetWare for SAA returns the following message: Cannot execute this NetView RuncmdIf the command includes some attribute parameters that are enabled and some that are disabled, NetWare for SAA processes all enabled parameters and ignores all disabled parameters.The command-filtering feature is controlled by the NetWare administrator. Instructions for controlling this feature appear in the NetWare for SAA v1.3 Administration Guide and the NetWare Management Agent for NetView Administration Guide (for NMA for NetView v1.3).ID="FM22261"Host Connectivity OptionsTo connect to the NetView host, NetWare servers use one of the following options:Collection pointEnd pointStandaloneCollection Point ServersIDREF="FM31354"Figure 1-2 shows a NetWare server that is configured as a collection point server.LBL="1-2"ID="FM31354"Collection Point and End Point ServersFILE="nvorg002.pbm"NetWare for SAA servers---version 1.2 or later---are the only servers that can be configured as collection point servers. A collection point server connects to the host via one of the following types of connections:Token ringSDLCEthernetQLLCCustom data linkThe collection point server does not depend on any intermediate servers for the NetView connection. The collection point server may, however, forward alerts and commands for end point servers.End Point ServersIDREF="FM31354"Figure 1-2 shows a NetWare server that is configured as an end point server.End point servers communicate with NetView via a collection point server. NetWare for SAA and NMA for NetView servers---version 1.2 and later--- may be configured as end point servers. The connection between the end point server and the collection point server is the NetWare LAN.When an end point server 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 you send a command from the NetView console to an end point server, NetView passes the command to the collection point server, which forwards the command over the NetWare LAN to the end point server. Command response messages from the end point server follow the same communications path as alert messages.Version 1.3 end point servers cannot communicate with version 1.2 collection point servers.End point servers can reduce the cost of NetView management in NetWare LANs with multiple servers. Because end point servers can use the existing NetWare LAN connection to communicate with NetView (via a collection point server), end point servers do not require additional hardware for a direct host connection.End point servers also can reduce the number of host connections required by NetWare servers. Each collection point server requires the allocation of a host physical unit (PU) Type 2.0 through which it communicates with NetView. End point servers communicate with NetView over the PU used by the collection point server. Therefore, end point servers do not require the allocation of additional host PUs.Messages that travel between NetWare and NetView flow over a session between the PU Type 2.0 and the system services control point (SSCP) host component. If a server is not configured to use a PU Type 2.0 session, configure the server as an end point server.Standalone ServersIDREF="FM85132"Figure 1-3 on the next page shows a NetWare server that is configured as a standalone server.LBL="1-3"ID="FM85132"NetView Support in a Standalone NetWare ServerFILE="nvorg003.pbm"All versions of NMA for NetView may be configured as standalone servers. The connection between the standalone server and NetView must be a token ring LAN.Standalone servers cannot communicate with collection point servers.Configure your NMA for NetView server as a standalone server only when your LAN does not have a collection point server. If your LAN has a collection point server, you should configure the NMA for NetView server as an end point server.Feature ControlThe NetWare support features for NetView are controlled on a server-by-server basis. The NetWare administrator determines which features are enabled in each server. The rest of this section describes the features that may be enabled or disabled in NetWare for SAA and NMA for NetView servers.NetWare for SAABeginning with NetWare for SAA v1.2, the NetWare administrator can control the NetView support features as follows:Enable or disable all NetView support featuresEnable or disable the sending of alerts to NetViewEnable or disable NetView command processingEnable or disable the command security optionConfigure NetWare for SAA for collection point or end point communicationsUse command filtering to enable or disable processing of select commands (only in NetWare for SAA v1.3 and later)The NetWare administrator uses a configuration utility program (CSCON) and a command-filter file to control these features.Except for enabling or disabling of all NetView support, all the feature controls listed above apply only to the server that is being configured; these controls do not regulate communications with end point servers. For example, disabling command processing in a collection point server does not prevent command forwarding to end point servers.NMA for NetViewIn each NMA for NetView server, the NetWare administrator can control the NetView support features as follows:Configure NMA for NetView for standalone or end point communications (only in NMA for NetView v1.2 and above)Use command filtering to enable or disable processing of select commands (only in NMA for NetView v1.3 and above)The NetWare administrator uses a utility program to select the communications option for the NMA for NetView server.To enable all NetView support, the NetWare administrator must install NMA for NetView and start the program. When NMA for NetView starts, the following features are automatically enabled:Alert generation Command processingThe command security optionID="FM70522"Support for the Open NetView InterfaceNetWare for SAA v1.3 and NMA for NetView v1.3 can provide a connection between NetView and other applications that conform to the NetWare Open NetView interface. When an application uses the Open NetView interface, a NetWare for SAA or NMA for NetView server 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 provided with the application.Summary of NetWare Software Support for NetViewTable 1-2 summarizes the versions of NetWare software that provide support for NetView functions.LBL="1-2" INLINE="F"Summary of NetWare Support Software for NetViewWIDTH="96"NetWare SupportSoftware for NetViewWIDTH="96"Supported Version(s) of NetWareWIDTH="96"Supported FeaturesWIDTH="96"Supported Configurations  and ConnectionsWIDTH="96"NetWare for SAA v1.0WIDTH="96"NetWare v3.11WIDTH="96"Alert generationWIDTH="96"Standalone---token  ring connection to  hostNetWare for SAA v1.2NetWare v3.11Alert generationServer query  commandsServer control  commandsCommand securityCollection point---  token ring, SDLC,  Ethernet, QLLC, &  custom data link  connections to hostEnd Point---token  Ring connection to  collection pointStandalone---token  ring connection to  hostNetWare for SAA v1.3NetWare v3.1x(Patch procedure  required before  installing on a  NetWare v3.11  server)NetWare v4.0Alert generationServer query  commandsServer control  commandsCommand securityCommand filteringFeature controlOpen NetView  interface supportCollection point---  token ring, SDLC,  Ethernet, QLLC, &  custom data link  connections to hostEnd point---token  ring connection to  collection pointStandalone---token  ring connection to  hostNMA for NetView v1.0(Supplied with  NetWare v3.11)NetWare v3.11Alert generationStandalone---token  ring LAN connection  to hostNMA for NetView v1.2(Distributed via  NetWare Express)NetWare v3.11Alert generationServer query  commandsServer control  commandsCommand securityEnd Point---token  ring connection to  collection pointStandalone---token  ring LAN connection  to hostNMA for NetView v1.3(Supplied with  NetWare v3.12.  Patch release  distributed via  NetWare Express)NetWare v3.1x(NetWare Express  patch release  required for  installation on  NetWare v3.11  server)Alert generationServer query  commandsServer control  commandsCommand securityCommand filteringOpen NetView  interface supportEnd Point---token  ring connection to  collection pointStandalone---token  ring LAN connection  to hostLBL="2"ID="FM37278"Alert Message DescriptionsThis chapter lists the NetWare alert messages that may appear in NetView display panels. These alerts appear in the following NetView NPDA panels:Alerts-DynamicAlerts-StaticAlerts-HistoryThe messages in this chapter are generated by NetWare servers. To learn more about an alert from an application that uses the Open NetView interface, refer to the manual for that application.The Sender Hardware Product ID panel in NetView displays the following two values that represent parameters defined in NetWare servers:The Machine Type= value in the NetView user interface is the same as the Model Number of Server Machine parameter in NetWare.The Serial Number:Sequence Number= value in NetView is the same as the Serial Number of Server parameter in NetWare.These parameters describe the NetWare server to which a PU is assigned. When these values appear in alerts from end point servers, they describe the collection point server, not the end point server.Alert Description FormatThe alert message descriptions in this chapter use bold text to represent text that appears on NetView display panels. Italicized text within a description indicates variable data received from the server. The message descriptions are listed in alphabetical order using the following format.Alert Description: Probable CauseUserThis text appears after the User Caused label in the NetView Recommended Action for Selected Event panel. This text describes a problem that may be corrected by a user action.InstallThis text appears after the Install Caused label in the NetView Recommended Action for Selected Event panel. This text describes a problem that may have been caused by an installation error.FailureThis text appears after the Failure Caused label in the NetView Recommended Action for Selected Event panel. This text describes a problem that may have been caused by a component failure.Explanation: Additional information on what the alert means.Action: Recommendation for corrective action.NetWare message: This is the NetWare message that appears on a server console.Alert MessagesThis chapter lists all the alerts that might be generated by NetWare for SAA v1.3 and NMA for NetView v1.3 servers. When managing NetWare servers, remember the following:Earlier versions of NetWare for SAA and NMA for NetView produce reduced sets of alerts. For example, NMA for NetView v1.0 does not produce alerts for NetWare system messages.The NetWare message for each alert is from the software that generates that alert. Some messages are produced by the server's SERVER.EXE program, and others are produced by drivers and protocol stacks installed at the server. Different versions of software may produce different messages on the NetWare console.The NetWare message for each alert is from the latest version of software that generates that alert. For example, if NetWare v3.12 was the last version to generate the alert, the NetWare message listed is the message from NetWare v3.12. If NetWare v4.0 and NetWare v3.12 produce different messages for the same alert, the version 4.0 message is listed.Auto removal: Token-ring lobeFailureLocal token-ring adapterLocal access unitLocal lobe cablesExplanation: Adapter left the ring as part of the beacon automatic recovery process.Action: Ask the LAN administrator to review the link data.NetWare message: TOKEN-NW-237-Adapter number-board number: The adapter is beaconing.Ring status = code.Capacity exceeded: Logged in usersUserThe Maximum Number of Users Supportable by the Server has been ExceededProblem detected by serverExplanation: When the system tried to allocate a connection number for a workstation, the maximum number of connections (250) was exceeded.Action: Depends on frequency. A connection will become available when other users log out from the system. If this message appears frequently, consider adding another server to the network.NetWare message: Out of server connections. User connect request failed.Capacity exceeded: MemoryUserInsufficient MemoryProblem Detected by serverFailureLoadable Software ModuleServer Software Component may have Excessive Memory RequirementsExplanation: The cache buffer limit is set to 0 (zero). All cache memory has been used.Action: Add more memory to the file server.NetWare message: Cache memory allocator out of available memory.Capacity exceeded: Storage subsystemUserInsufficient Storage Media SpaceInsufficient Storage Media Space forvolumesize K of Storage is in Use by Deleted Files that Cannot be Purged YetProblem Detected byserverExplanation: When the volume is out of disk space, the NetWare message (listed below) is broadcast to all users on the system. All attempts to write to files will fail because of insufficient disk space. The second line of the message indicates that deleted files have not been purged.Action: If the server is running NetWare v3.1x, ask the NetWare administrator to complete one or more of the following actions:Run the NetWare PURGE command to free up space occupied by deleted files that have not been automatically purged.Use the NetWare SET command to change the Minimum File Delete Wait Time parameter so that files can be purged at shorter intervals.Delete unnecessary files from the volume.Add more disks to the volume.NetWare message: Volume server/volume out of disk space.number K of disk space is in use by deleted files.Capacity exceeded: Storage subsystemUserInsufficient Storage Media SpaceInsufficient Storage Media Space forvolumeThere are no Deleted Files Using Storage SpaceProblem Detected by serverExplanation: When the volume is out of disk space, the NetWare message (listed below) will be broadcast to all users on the system. All attempts to write to files will fail because of insufficient disk space.Action: Delete unnecessary files from the volume, or add more disk space to the volume.NetWare message: Volume server/volume out of disk space.There are no deleted files using disk space.Capacity exceeded: Transmit/receive buffersInstallSystem Transmit/Receive Buffer Threshold Set Too LowProblem Detected by serverFailureSoftware Device DriverCommunications/LAN Device DriverCommunications ProgramTransmit/Receive Buffer Limit Reached -- Buffers Are Not Being ReleasedExplanation: A SET command parameter limits the number of Packet Receive Buffers that the operating system can allocate for itself. This parameter is set too low.Action: If the server is a NetWare v3.1x server, ask the NetWare administrator to use the NetWare SET command to correct the problem.If the server is a NetWare v4.0 server, use the GET SERVER command (see IDREF="FM30134"page 3-22) to display the Maximum Packet Receive Buffers parameter. Use the SET SERVER command (see IDREF="FM54338"page 3-35) to change the Maximum Packet Receive Buffers parameter.NetWare message: LAN receive buffer limit reached. All buffers are in use.Directory search threshold reached: Application programInstallConcurrent Directory Search Threshold for Workstations Set too LowProblem Detected by serverFailureApplication ProgramWorkstation Concurrent Directory Search Threshold ReachedExplanation: The directory search threshold has been reached.Action: Contact the NetWare server administrator.NetWare message: Connection number USER name exceeded outstanding NCP directory search limit.File directory entry limit exceeded: File directory structureUserFile Directory Table Full on volumeProblem Detected by serverInstallDirectory Size Limit too Low on volumeExplanation: When a new directory is created, NetWare allocates a directory block for that directory. The file server limits the amount of directory blocks to 1/32 of the total disk space. If that amount of space is exceeded, the attempt to expand the directory table will fail.Action: Delete unused or unnecessary directories.NetWare message: Error expanding server/volume directory because directory size limit was exceeded.File directory may be corrupted: Storage subsystemFailureStorage SubsystemDisk Write Errors on volumeProblem Detected by serverExplanation: A write error occurred on the system. This error may have been caused by a hard disk or channel failure.Action: Check the disk drives and channel to see if a failure has occurred. NetWare message: Error expanding server/volume directory due to disk write errors.File directory may be corrupted: Storage subsystemFailureStorage SubsystemError Writing Newly Allocated Directory Block on volumeProblem Detected by serverExplanation: A write error occurred while a directory on the named server was being written to. This error may have been caused by a hard disk or channel failure.Action: Check the disk drives and channel to see if a failure has occurred.NetWare message: Error writing to a newly allocated directory block on server/volume.File directory may be corrupted: Storage subsystemFailureStorage SubsystemError Writing to Directory on volumeProblem Detected byserverExplanation: A write error occurred on the system that Hot Fix(tm) could not correct (For more information on Hot Fix, see NetWare v3.11 Concepts, NetWare v3.12 Concepts, or NetWare 4.0 Concepts.) This error may have been caused by a hard disk or channel failure.Action: Check the disk drives and channel to see if a failure has occurred. NetWare message: Error writing to the directory on server/volume.File lock threshold reached: Application programInstallFile Lock Threshold for Workstations Set too LowProblem Detected byserverFailureApplication ProgramWorkstation File Lock Threshold Reachednumber Lock Requests FailedExplanation: The number of open files and file locks on the server has exceeded the maximum specified by the Maximum File Locks Per Connection parameter. The default value is 20000. The number variable indicates the number of open file and file lock requests that failed because the limit was exceeded. Action: If the server is a NetWare v3.1x server, ask the NetWare administrator to use the NetWare SET command to correct the problem.If the server is a NetWare v4.0 server, use the GET SERVER command (see IDREF="FM30134"page 3-22) to display the Maximum File Locks Per Connection parameter. Use the SET SERVER command (see IDREF="FM54338"page 3-35) to change the Maximum File Locks Per Connection parameter.NetWare message: Station number file lock threshold exceeded.Total violations number.File lock threshold reached: Application programInstallSystem File Lock Threshold Set too LowProblem Detected by serverFailureApplication ProgramSystem File Lock Threshold Reachednumber Lock Requests FailedExplanation: The number of open files and file locks on the server has exceeded the maximum specified by the Maximum File Locks parameter. The default value is 10000. The number variable indicates the number of open file and file lock requests that failed because the limit was exceeded.Action: If the server is a NetWare v3.1x server, ask the NetWare administrator to use the NetWare SET command to correct the problem.If the server is a NetWare v4.0 server, use the GET SERVER command (see IDREF="FM30134"page 3-22) to display the Maximum File Locks parameter. Use the SET SERVER command (see IDREF="FM54338"page 3-35) to change the Maximum File Locks parameter.NetWare message: System file lock threshold exceeded.number file open or lock requests failed.LAN communications lost: Local LAN adapterFailureLocal LAN Adapternetwork Inaccessible Due to LAN Adapter FailureProblem Detected by serverExplanation: You received this message for one of the following reasons:The LAN board failed. The driver detected an error and removed the board.A user unloaded the LAN driver with the NetWare UNLOAD command.Action: If the LAN board failed, replace the board. If the driver was unloaded with the NetWare UNLOAD command, you do not need to take any action.NetWare message: IPX local network number removed because LAN board is unreachable.Link error: LAN LLC communicationsFailureLAN LLC communicationsDM receivedExplanation: Link disconnected: a disconnect mode (DM) request was sent by the server's partner station. The partner station issued a DM, which severed the logical connection between the partner station and the server.Action: Reactivate the partner station. If the problem persists, contact the Systems Network Architecture (SNA) network administrator.NetWare message: Link lost: remote sent a DM.SAddr: number, SSAP: number, DAddr: number, DSAP: numberLink error: LAN LLC communications/remote nodeFailureLAN LLC communications/remote nodePoll count exhaustedExplanation: Link disconnected: inactive remote station. The server's partner station does not respond to polling either because it is down or because there is a problem with the connection.Action: Verify whether the partner station is active. If it is active, check the physical connection between the stations.NetWare message: Link lost: remote is not responding.SAddr: number, SSAP: number, DAddr: number, DSAP: numberLink error: SDLC communicationsFailureSDLC communications errorDM receivedExplanation: Link disconnected: a disconnect mode (DM) request was sent by the server's partner station. The partner station issued a DM, which severed the logical connection between the partner station and the server.Action: Reactivate the partner station. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: remote sent a DM.Local DLC address: number, Remote DLC address: numberLink error: SDLC communications/remote nodeUserRemote device power offFailureSDLC communication/remote nodeLineInactivity timer expiredExplanation: Link disconnected: the inactivity timer of the local station expired. The server has not received anything for the amount of time specified by the server's inactivity timer.Action: Verify whether there is an active partner station. If there is, check the physical connections.NetWare message: Link lost: local station's inactivity timer has expired.Local DLC address: number, Remote DLC address: numberLink error: SDLC communications/remote nodeUserRemote device power offFailureSDLC communications/remote nodeLinePoll count exhaustedExplanation: Link disconnected: inactive remote station. The server's partner station does not respond to polling either because it is down or because there is a problem with the connection.Action: Verify whether the partner station is active. If it is active, check the physical connection between the stations.NetWare message: Link lost: remote is not responding.Local DLC address: number, Remote DLC address: numberLink error: SDLC communications/remote nodeUserRemote device power offFailureSDLC communication/remote nodeLineXID poll count exhaustedExplanation: Link disconnected: the exchange station ID (XID) retry limit was exceeded on the local station. The server sent an XID, which the partner station either did not receive or ignored.Action: Verify whether the partner station is active. If it is active, check the physical connection.NetWare message: Link lost: local station's XID retry limit has been exceeded.Local DLC address: number, Remote DLC address: numberMemory threshold reached: Server configurationInstallMemory Threshold Set too Lownumber Memory Allocation Requests FailedProblem Detected by serverExplanation: The request for short-term memory failed because the system limit was exceeded.Action: Ask the NetWare administrator to use the NetWare SET command to increase the setting for the Maximum Alloc Short Term Memory parameter. (Note that only NetWare v3.1x servers produce this alert.)NetWare message: Alloc Short Term Memory allocator requests exceeded the configuration limit.number short-term memory allocation requests failed.Memory usage threshold reached: Loadable software moduleUserInsufficient MemoryProblem detected by serverInstallMemory Lower Limit Set too HighFailureLoadable Software ModuleServer Software Component may have Excessive Memory RequirementsExplanation: The server is running out of memory.Action: Ask the NetWare server administrator to determine how memory is being used in the server. If memory is being used properly, add more memory. If a software component is using excessive memory or the Memory Lower Limit value is set too high, correct the problem.NetWare message: Cache memory allocator exceeded minimum cache buffer left limit. <or>Number of cache buffers is getting too low.Network addressing conflict: Server configurationInstallFile Server Assigned Duplicate LAN Logical Addressserver Duplicates LAN Logical Address of Alert OriginatorProblem Detected by serverExplanation: Another server on the network is claiming to be at the same address as this server. This claim is occurring because two NetWare servers have been given the same IPX internal network number.Action: Assign each NetWare server a unique network address.NetWare message: Router configuration error detected.name is claiming my same internet address.Network addressing conflict: Server configurationInstallFile Server Assigned Duplicate LAN Logical Network AddressIdentity of Offending Server is UnknownProblem Detected byserverExplanation: Another server claims to have the same network and node addresses as this server.Action: Find out which server has the incorrect network and node addresses; then change the configuration accordingly.NetWare message: Router configuration error detected.Another router is claiming the same internet address.Network addressing conflict: Server configurationInstallFile Server Assigned Incorrect LAN LogicalIdentifierFile Server at node Assigned network_name_a -- Alert Originator Assignment on Same Network is network_name_bProblem Detected by serverExplanation: The NetWare BIND command that was issued to bind IPX to a LAN driver specified an incorrect network number. Other routers or servers on the network list a different network number for the cabling system.Action: Ask the NetWare administrator to unbind the LAN driver; then bind the LAN driver with the correct network number. The correct number is specified by the network_name_b variable.NetWare message: Router configuration error detected.Router at node number1 claims network number2 should be number3.Open failure: Token-ring duplicate station addressInstallToken-ring duplicate station address assignedExplanation: Adapter detected another station with the same address during the insertion process.Action: Ask the LAN administrator to review the link data.NetWare message: TOKEN-NW-233-Adapter number-Board number: The adapter detected a duplicate station during the insertion process.Error code = code.Open failure: Token-ring fault domainFailureToken-ring fault domainExplanation: Adapter detected a beaconing condition on the ring during the insertion process.Action: Ask the LAN administrator to reopen the adapter (reload the token ring driver). After this message appears, the administrator should wait 30 seconds before attempting to reopen the adapter.NetWare message: TOKEN-NW-236-Adapter number-Board number: The ring was beaconing during the insertion process.Error code = code.Open failure: Token-ring lobeFailureLocal token-ring adapterLocal access unitLocal lobe cablesExplanation: Adapter detected a problem on its lobe during the insertion process.Action: Ask the LAN administrator to reopen the adapter (reload the token ring driver). After this message appears, the administrator should wait 30 seconds before attempting to reopen the adapter.NetWare message: TOKEN-NW-235-Adapter number-Board number: The adapter cable was disconnected during the insertion process.Error code = code.Open failure: Token-ring lobeFailureLocal token-ring lobeToken-ring LAN componentInterferenceExplanation: An unknown error was detected during the insertion process resulting in an incomplete insertion.Action: Ask the LAN administrator to review the link data.NetWare message: None.Open failure: Token-ring remove command receivedUserToken-ring remove adapter command receivedExplanation: The adapter received a Remove Ring Station MAC frame during the insertion process.Action: Ask the LAN administrator to review the link data.NetWare message: TOKEN-NW-234-Adapter number-board number: The adapter received a Remove MAC Frame during the insertion process.Error code = code.Password encryption error: Application programInstallClient Application Program Sent an Unencrypted Password to a Server Configured for Encrypted Passwords OnlyRequest Originated fromnode onnetworkProblem Detected by serverExplanation: An application, utility, or NetWare shell tried to log in, verify a password, or change a password without first encrypting the password. The NetWare server is configured to accept only encrypted passwords.Action: Either replace the application, utility, or NetWare shell, or reconfigure the server to accept unencrypted passwords. You can ask the NetWare administrator to replace the utility with one that encrypts passwords. If the utility is a NetWare 2.x utility or shell, it should be replaced with a 3.x utility or shell.To reconfigure the server, do one of the following:If the server uses NetWare v4.0, set the server to accept unencrypted passwords by using the SET SERVER command (see IDREF="FM54338"page 3-33) with the Allow Unencrypted Passwords parameter.If the server uses NetWare v3.1x, ask the NetWare administrator to use the NetWare SET command to configure the NetWare server so that it accepts unencrypted passwords.NetWare message: Station number attempted to use an unencrypted password call.Possible file allocation table corruption: Storage subsystemFailureStorage SubsystemError Writing File Allocation Table for volumeProblem Detected by serverExplanation: A write error occurred on the system. This error may have been caused by a hard disk or channel failure.Action: Check the disk drives and channel to see if a failure has occurred. Correct the failure if possible. Ask the NetWare administrator to run VREPAIR.NetWare message: Error writing FAT table for volume server/volume.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Read ErrorServer Requested OperationDetailed Data Contains Path Information for the File - Path Shown may be IncompleteProblem detected by serverExplanation: The operating system was unable to read the specified file. The file is corrupted or the disk has failed.Action: Complete one of the following:If the file is corrupted, restore the file from a backup copy.If the disk has failed, check for faulty hardware components (cable, power supply, controller, or hard disk).NetWare message: Error reading file filename.Offset number data stream number.Read was requested by the SERVER.File path volume:path.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Read ErrorServer Requested OperationFile Name InaccessibleProblem Detected by serverExplanation: A read error occurred on the system. This error may have been caused by a hard disk or channel failure. The data stream number is listed in the Actions area of the Recommended Action for Selected Event display and indicates the name space stream.Action: Check the disk drives and channel to see if a failure has occurred.NetWare message: File read error at offset number data stream number.Error getting file name.Read was requested by the SERVER.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Read Erroruser on station_number Requested OperationFile Name InaccessibleProblem Detected by serverExplanation: A read error occurred on the system. This error may have been caused by a hard disk or channel failure. Some data was lost that would cause the user's applications to fail when reading data from files. The data stream number is listed in the Actions area of the Recommended Action for Selected Event display and indicates the name space stream.Action: Check the disk drives and channel to see if a failure has occurred.NetWare message: File read error at offset number data stream number.Error getting file name.Read was requested by user name on station number.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Read Erroruser on station_number Requested OperationDetailed Data Contains Path Information for the File - Path Shown may be IncompleteProblem Detected by serverExplanation: A read error occurred on the system. This error may have been caused by a hard disk or channel failure. Some data was lost that would cause the user's applications to fail when reading data from files. The data stream number is listed in the Actions area of the Recommended Action for Selected Event display and indicates the name space stream.Action: Check the disk drives and channel to see if a failure has occurred.NetWare message: Error reading file filename.Offset number data stream number.Read was requested by user name on station number.File path volume:path.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Write ErrorServer Requested OperationDetailed Data Contains Path Information for the File - Path Shown may be IncompleteProblem Detected byserverExplanation: An error occurred while the file named in the Event Detail display was being written to. This error may have been caused by a hard disk or channel failure.Action: Check the disk drives and channel to see if a failure has occurred.NetWare message: Error writing to file filename data stream number.Write was requested by the SERVER.File path volume:path.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Write ErrorServer Requested OperationFile Name InaccessibleProblem Detected by serverExplanation: A write error occurred while data was being written to disk. A file has been lost or corrupted. The write error may be due to a hard disk or channel failure. The disk may have other problems with data integrity. The data stream number is listed in the Actions area of the Recommended Action for Selected Event display and indicates the name space stream.Action: Ask the NetWare administrator to do the following:Check the system console and the history base for messages concerning disk and disk partition problems.Run the disk manufacturer's diagnostic programs to determine the exact disk problem.Run VREPAIR to correct minor problems.Repair or replace the disk and disk controller if necessary.Notify users that they may have lost data.If an adequate backup was done, restore damaged files.NetWare message: Error writing to file (file name not accessible) data stream number. Write was requested by the server.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Write Erroruser on station_number Requested OperationDetailed Data Contains Path Information for the File - Path Shown may be IncompleteProblem Detected by serverExplanation: An error occurred while the file named in the Event Detail display was being written to. The data stream number is listed in the Actions area of the Recommended Action for Selected Event display and indicates the name space stream.Action: Check the disk drives and channel to see if a failure has occurred.NetWare message: Error writing to file filename data stream number.Write was requested by user name on station number.File path volume:path.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Write Erroruser on station_number Requested OperationFile Name InaccessibleProblem Detected by serverExplanation: A write error occurred while data was being written to disk. A file has been lost or corrupted. The write error may be due to a hard disk or channel failure. The disk may have other problems with data integrity. The data stream number is listed in the Actions area of the Recommended Action for Selected Event display and indicates the name space stream.Action: Ask the NetWare administrator to do the following:Check the system console and the history base for messages concerning disk and disk partition problems.Run the disk manufacturer's diagnostic programs to determine the exact disk problem.Run VREPAIR to correct minor problems.Repair or replace the disk and disk controller if necessary.Notify users that they may have lost data.If an adequate backup was done, restore damaged files.NetWare message: Error writing to file (file name not accessible) data stream number. Write was requested by user name on station number.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Write Pre-Read ErrorServer Requested OperationDetailed Data Contains Path Information for the File -Path Shown may be IncompleteProblem Detected by serverExplanation: A disk failure occurred. A write preread operation occurs when NetWare writes a partial block and subsequently needs to write the rest of the block. NetWare must first read the partial block and then write the entire block. If the read fails, a write preread error occurs.Action: Check for faulty hardware components in the disk channel (cable, power supply, controller, or hard disk).NetWare message: File filename write pre-read error.Offset number data stream number.Read was requested by the SERVER.File path volume:path.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Write Pre-Read ErrorServer Requested OperationFile Name InaccessibleProblem Detected by serverExplanation: A disk failure occurred. A write preread operation occurs when NetWare writes a partial block and subsequently needs to write the rest of the block. NetWare must first read the partial block and then write the entire block. If the read fails, a write preread error occurs.Action: Check for faulty hardware components in the disk channel (cable, power supply, controller, or hard disk).NetWare message: File write pre-read error.Offset number data stream number.Error getting file name.Read was requested by the SERVER.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Write Pre-Read Erroruser on station_number Requested OperationDetailed Data Contains Path Information for the File -Path Shown may be IncompleteProblem Detected by serverExplanation: A disk failure occurred. A write preread operation occurs when NetWare writes a partial block and subsequently needs to write the rest of the block. NetWare must first read the partial block and then write the entire block. If the read fails, a write preread error occurs.Action: Check for faulty hardware components in the disk channel (cable, power supply, controller, or hard disk).NetWare message: File filename write pre-read error.Offset number data stream number.Read was requested by user name on station number.File path volume:path.Possible file corruption: Storage subsystemFailureStorage SubsystemFile Write Pre-Read Erroruser on station_number Requested OperationFile Name InaccessibleProblem Detected by serverExplanation: A disk failure occurred. A write preread operation occurs when NetWare writes a partial block and subsequently needs to write the rest of the block. NetWare must first read the partial block and then write the entire block. If the read fails, a write preread error occurs.Action: Check for faulty hardware components in the disk channel (cable, power supply, controller, or hard disk).NetWare message: File write pre-read error.Offset number data stream number.Error getting file name.Read was requested by user name on station number.Record lock threshold reached: Application programInstallRecord Lock Threshold for Workstations Set too LowProblem Detected byserverFailureApplication ProgramWorkstation Record Lock Threshold Reachednumber Lock Requests FailedExplanation: The number of record locks on the server has exceeded the Maximum Record Locks Per Connection system parameter. The default value is 20000. Applications that request record locks do not function properly until record locks are released by other applications.Action: If the server is a NetWare v3.1x server, ask the NetWare administrator to increase the setting for the Maximum Record Locks Per Connection parameter.If the server is a NetWare v4.0 server, use the GET SERVER command (see IDREF="FM30134"page 3-22) to display the Maximum Record Locks Per Connection parameter. Use the SET SERVER command (see IDREF="FM54338"page 3-35) to change the Maximum Record Locks Per Connection parameter.NetWare message: Station number record lock threshold exceeded.Total violations number.Record lock threshold reached: Application programInstallSystem Record Lock Threshold Set too LowProblem Detected by serverFailureApplication ProgramSystem Record Lock Threshold Reachednumber Lock Requests FailedExplanation: The number of record locks on the server has exceeded the Maximum Record Locks parameter. The default value is 20000. Applications that lock records will not function properly.Action: If the server is a NetWare v3.1x server, ask the NetWare administrator to increase the setting for the Maximum Record Locks parameter.If the server is a NetWare v4.0 server, use the GET SERVER command (see IDREF="FM30134"page 3-22) to display the Maximum Record Locks parameter. Use the SET SERVER command (see IDREF="FM54338"page 3-35) to change the Maximum Record Locks parameter.NetWare message: System record lock threshold exceeded.number record lock requests failed.Remove adapter command received: LAN manager operatorUserToken-ring remove adapter command receivedExplanation: The reporting station's adapter received a Remove Adapter command from a LAN manager and, as a result, left the LAN.Action: Contact the LAN administrator and report the adapter number and error code, which appear in the Actions area of the Recommended Action for Selected Event display.NetWare message: TOKEN-NW-242-Adapter number-board number: The Remove MAC Frame process shut down the adapter.Ring status = code.Required software attempted termination: Application programFailureApplication ProgramProblem Detected by serverExplanation: An error occurred while a module was being unloaded. The module is still loaded. The error may occur when another module references public symbols exported by this module.Action: Unload the module that is using the public symbols; then unload this module.NetWare message: Error unloading killed loadable moduleResource nearing capacity: Storage subsystemUserInsufficient Storage Media SpaceInsufficient Storage Media Space Available for volumeProblem Detected byserverExplanation: The volume is almost out of disk space.Action: Ask the NetWare administrator to delete unnecessary files from the volume or add more disk space to the volume.When the server is running NetWare v4.0, you can manage disk space usage and reporting with the following SET SERVER command parameters:Immediate Purge of Deleted FilesVolume Low Warn All UsersVolume Low Warning ThresholdNetWare message: Volume server/volume almost out of disk space.Software program error: LAN LLC communicationsFailureCommunications program in remote nodeI-field receive when not permittedExplanation: Link disconnected: an information field was sent at the wrong time by a remote station. A partner station sent an information field when it was not permitted to do so. The server sent a frame reject.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: remote station sent an Information field at the wrong time.SAddr: number, SSAP: number, DAddr: number, DSAP: numberSoftware program error: LAN LLC communicationsFailureCommunications program in remote nodeInvalid N(r) receivedExplanation: Link disconnected: the number of frames received (Nr) from the remote station does not match the number of frames sent (Ns). There is a discrepancy between the number of frames the server received and the number of frames the partner station sent.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: remote station sent an invalid N(r).SAddr: number, SSAP: number, DAddr: number, DSAP: numberSoftware program error: LAN LLC communicationsFailureCommunications program in remote nodeInvalid/unsupported command or response receivedExplanation: Link disconnected: an invalid command or response was sent by remote station. A partner station sent a command or response that is not supported by the server. The server sent a frame reject.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: remote station sent an invalid or unsupported frame.SAddr: number, SSAP: number, DAddr: number, DSAP: numberSoftware program error: LAN LLC communicationsFailureCommunications program in remote nodeReceived I-field exceeded maximum lengthExplanation: Link disconnected: too long an information field was sent by a remote station. A partner station sent an information field that was larger than the frame size specified for NetWare for SAA.Action: Ensure that Netware for SAA's frame size matches the frame size specified on the partner station.NetWare message: None.Software program error: LAN LLC communicationsFailureCommunications program in remote nodeSABME received while in ABMEExplanation: Link disconnected: link was in Data Transfer mode when a SABME request was sent by a remote station. The server's partner station requested set asynchronous balanced mode extended (SABME) while data was already being sent in that mode.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: remote sent SABME while in Data Transfer Mode.SAddr: number, SSAP: number, DAddr: number, DSAP: numberSoftware program error: LAN LLC communicationsFailureSoftware programFrame reject received: I-field sent when not permittedExplanation: Link disconnected: an information field was sent at the wrong time by the local station. The server sent an information field when it was not permitted to do so. The server's partner station sent a frame reject.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: local station sent an Information field at the wrong time.SAddr: number, SSAP: number, DAddr: number, DSAP: numberSoftware program error: LAN LLC communicationsFailureSoftware programFrame reject received: invalid N(r) sentExplanation: Link disconnected: the number of frames received (Nr) from the local station does not match the number of frames sent (Ns). There is a discrepancy between the number of frames the server's partner station received and the number of frames the server sent.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: local station sent an invalid N(r).SAddr: number, SSAP: number, DAddr: number, DSAP: numberSoftware program error: LAN LLC communicationsFailureSoftware programFrame reject received: Invalid/unsupported command or response sentExplanation: Link disconnected: an invalid command or response was sent by the local station. The server sent a command or response that is not supported by the server's partner station. The partner station sent a frame reject.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: local station sent an invalid or unsupported frame.SAddr: number, SSAP: number, DAddr: number, DSAP: numberSoftware program error: LAN LLC communicationsFailureSoftware programFrame reject received: maximum I-field length exceededExplanation: Link disconnected: too long an information field was sent by the local station. The server sent an information field that was larger than the frame size specified on the server's partner station.Action: Ensure that the NetWare for SAA frame size matches the frame size specified on the partner station.NetWare message: Link lost: local station sent too long an I frame.SAddr: number, SSAP: number, DAddr: number, DSAP: numberSoftware program error: SDLC communicationsFailureCommunications program in remote nodeI-field received when not permittedExplanation: Link disconnected: an information field was sent at the wrong time by the local station. The server sent an information field when it was not permitted to do so. The server's partner station sent a frame reject.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: local station sent an Information field at the wrong time.Local DLC address: number, Remote DLC address: numberSoftware program error: SDLC communicationsFailureCommunications program in remote nodeInvalid N(r) receivedExplanation: Link disconnected: the number of frames received (Nr) from remote station does not match the number of frames sent (Ns). There is a discrepancy between the number of frames the server received and the number of frames the server's partner station sent.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: local station sent an invalid N(r).Local DLC address: number, Remote DLC address: numberSoftware program error: SDLC communicationsFailureCommunications program in remote nodeInvalid/unsupported command or response receivedExplanation: Link disconnected: an invalid command or response was sent by the local station. The server sent a command or response that is not supported by the server's partner station. The partner station sent a frame reject.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: remote station sent an invalid or unsupported frame.Local DLC address: number, Remote DLC address: numberSoftware program error: SDLC communicationsFailureCommunications program in remote nodeReceive window size exceededExplanation: Link disconnected: the receive window size was exceeded because a remote station sent too many information (I) frames. A server's partner station sent more information (I) frames than specified by the receive window size.Action: Check the remote station's window size. Reconfigure the receive window size as discussed in the remote station's documentation.NetWare message: Link lost: local station receive window size is exceeded.Local DLC address: number, Remote DLC address: numberSoftware program error: SDLC communicationsFailureCommunications program in remote nodeSNRM received while in NRMExplanation: Link disconnected: an SNRM request was sent by a remote station while the station was already in use. The server's partner station requested set normal response mode (SNRM) while data was already being sent in normal response mode.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: remote sent an unexpected SNRM frame.Local DLC address: number, Remote DLC address: numberSoftware program error: SDLC communicationsFailureSoftware programFrame reject received: I-field sent when not permittedExplanation: Link disconnected: an information field was sent at the wrong time by a remote station. The server's partner station sent an information field when it was not permitted to do so. The server sent a frame reject.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: remote station sent an Information field at the wrong time.Local DLC address: number, Remote DLC address: numberSoftware program error: SDLC communicationsFailureSoftware programFrame reject received:invalid N(r) sentExplanation: Link disconnected: the number of frames received (Nr) from the local station does not match the number of frames sent (Ns). There is a discrepancy between the number of frames the server's partner station received and the number of frames the server sent.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: remote station sent an invalid N(r).Local DLC address: number, Remote DLC address: numberSoftware program error: SDLC communicationsFailureSoftware programFrame reject received: invalid/unsupported command or response sentExplanation: Link disconnected: an invalid command or response was sent by a remote station. The server's partner station sent a command or response that is not supported by the server. The server sent a frame reject.Action: Wait for the communication service to reestablish the link. If the problem persists, contact the SNA network administrator.NetWare message: Link lost: local station sent an invalid or unsupported frame.Local DLC address: number, Remote DLC address: numberSoftware program error: SDLC communicationsFailureSoftware programFrame reject received: maximum I-field length exceededExplanation: Link disconnected: too long an information field was sent by a remote station. The server's partner station sent an information field that was larger than the frame size specified for NetWare for SAA.Action: Ensure that the NetWare for SAA frame size matches the frame size specified on the partner station.NetWare message: Link lost: remote station sent too long an I frame.Local DLC address: number, Remote DLC address: numberSoftware program error: SDLC communicationsFailureSoftware programFrame reject received: no reason specifiedExplanation: Link disconnected: a remote station rejected a frame without including information about why it rejected the frame. The remote station is the server's partner station.Action: Contact the SNA network administrator.NetWare message: Link lost: A Frame Reject packet was received with no reason specified.Local DLC address: number, Remote DLC.address: numberSystem file unusable: Storage subsystemFailureStorage SubsystemUnable to Open/Create VOL$LOG.ERR on volumeProblem Detected by serverExplanation: The volume's error file, VOL$LOG.ERR, could not be created because either the volume was out of room or a disk error occurred.Action: Make sure the volume has enough available space. Add more disk space and delete unused and unnecessary files.NetWare message: Unable to create VOL$LOG.ERR on volume.System file unusable: Storage subsystemFailureStorage SubsystemUnable to Write to VOL$LOG.ERR on volumeProblem Detected by serverExplanation: The system was unable to write to the volume's error file because of a disk failure.Action: Contact the NetWare server administrator. Additional messages indicating what went wrong should appear on the system console. Correct the problem as suggested by those messages. Check for disk integrity and fix any disk problems you find.NetWare message: Unable to write to VOL$LOG.ERR on volume.Token-ring inoperative: Token-ring fault domainFailureToken-ring fault domainExplanation: Ring has been beaconing and is inoperative.Action: Ask the LAN administrator to review the link data.NetWare message: None.Unauthorized access attempted: File server userUserUnauthorized Access Attempted on accountRequest Originated from node on networkProblem Detected by serverExplanation: This notice appears on the NetWare server console and in the error log that can be viewed in SYSCON (a NetWare server utility). A user repeatedly entered an invalid password in an attempt to log in to the NetWare server. The number of invalid passwords exceeded the Incorrect Login Attempt limit allowed for the period of time specified in the NetWare Bad Login Count Retention Time parameter. The user's account has been disabled for the time specified by the NetWare Length of Account Lockout parameter.Action: The NetWare administrator must run SYSCON to clear the lockout, or the user must wait the specified lockout time.NetWare message: Intruder lock-out on account username [number:number].Wire fault: Token-ring lobeFailureLocal access unitLocal lobe cablesLocal token-ring adapterExplanation: Wire-fault condition detected on the ring.Action: Ask the LAN administrator to check the cable connections.NetWare message: TOKEN-NW-240-Adapter number-board number: Cable is disconnected at the MAU. Board is resetting.Ring status = code.<or>TOKEN-NW-239-Adapter number-board number:Cable is disconnected at the board. Board is resetting.Ring status = code.X.25 Error: Logical Link ControlInstallConfiguration errorFailureReceived I-field exceeded maximum lengthExplanation: The local station sent an frame reject (FRMR) response after it received a protocol data unit (PDU) with an information (I) field that was too long.Action: If the problem occurs repeatedly, contact the X.25 network information service.NetWare message: Link lost: remote station sent too long an I frame.SAddr: number; DAddr: numberLCN: numberX.25 Error: Logical Link ControlFailureX.25 Communications ErrorFrame reject received: invalid/unsupported command or response sentExplanation: The local station sent an frame reject (FRMR) response after it received a protocol data unit (PDU) with an invalid or unknown control field.Action: If the problem occurs repeatedly, contact the X.25 network information service.NetWare message: Link lost: local station sent an invalid or unknown Control field.SAddr: number; DAddr: numberLCN: numberX.25 Error: Logical Link ControlFailureX.25 Communications ErrorFrame reject received: I-field sent when not permittedExplanation: The local station sent an frame reject (FRMR) response after it received a protocol data unit (PDU) with an invalid information (I) field.Action: If the problem occurs repeatedly, contact the X.25 network information service.NetWare message: Link lost: local station sent an invalid I frame.SAddr: number; DAddr: numberLCN: numberX.25 Error: Logical Link ControlInstallConfiguration ErrorFailureX.25 Communications ErrorFrame reject received: Maximum I-Field Length ExceededExplanation: The local station sent an frame reject (FRMR) response after it received a protocol data unit (PDU) with an information (I) field that was too long.Action: If the problem occurs repeatedly, contact the X.25 network information service.NetWare message: Link lost: local station sent too long an I frame.SAddr: number; DAddr: numberLCN: numberX.25 Error: Logical Link ControlFailureX.25 Communications ErrorFrame reject received: Invalid N(r) sentExplanation: The local station sent an frame reject (FRMR) response after it received a protocol data unit (PDU) with an invalid number of frames received (Nr) value.Action: If the problem occurs repeatedly, contact the X.25 network information service.NetWare message: Link lost: local station sent an invalid N(r).SAddr: number; DAddr: numberLCN: numberX.25 Error: Logical Link ControlFailureX.25 Communications ErrorInvalid/Unsupported command or response receivedExplanation: The local station sent an frame reject (FRMR) response after it received a protocol data unit (PDU) with an invalid or unknown control field.Action: If the problem occurs repeatedly, contact the X.25 network information service.NetWare message: Link lost: remote station sent an invalid or unknown Control field.SAddr: number; DAddr: numberLCN: numberX.25 Error: Logical Link ControlFailureX.25 Communications ErrorI-Field received when not permittedExplanation: The local station sent an frame reject (FRMR) response after it received a protocol data unit (PDU) with an invalid information (I) field.Action: If the problem occurs repeatedly, contact the X.25 network information service.NetWare message: Link lost: remote station sent an invalid I frame.SAddr: number; DAddr: numberLCN: numberLBL="3"ID="FM36115"Sending NetWare CommandsThis chapter describes how to send commands from the NetView Network Communications Control Facility (NCCF) to the following types of NetWare servers:NetWare for SAA v1.2 and later NMA for NetView v1.2 and laterThese versions of NetWare for SAA and NMA for NetView support commands for the operating system and file services features of NetWare v3.11 and later servers.This chapter does not describe how to send commands to an application that has been designed to use the Netware Open NetView interface. For information on sending commands to this type of application, refer to the manual for that application.How to Send CommandsNetWare servers support the RUNCMD feature in NetView NCCF. The format for a RUNCMD for a NetWare server is RUNCMD SP=service_point_name, APPL=NETWARE, SName=server_name [OP=userid] actionresourceattribute_parameter resource_qualifier command_qualifierIDREF="FM39245"Table 3-1 divides the NetWare RUNCMD into three components.LBL="3-1" INLINE="F"NetWare RUNCMD ComponentsID="FM39245"WIDTH="180"Command ComponentsWIDTH="228"Command ParametersWIDTH="180"Command routingWIDTH="228"RUNCMD SP=service_point_name, APPL=NETWARE, SName=server_nameCommand securityOP=useridServer command parameters for  NetWare v3.1x and NetWare v4.0 serversactionresourceattribute_parameter resource_qualifiercommand_qualifierThe following sections describe how to route commands to the destination server, comply with NetWare security, and assemble server command parameters for NetWare v3.1x and NetWare v4.0 servers.The NetWare RUNCMD format is a combination of NetView RUNCMD parameters and parameters for NetWare. For additional information on NetView RUNCMD parameters and options, see the NetView Operation (SC31-6019) manual from IBM.When NCCF displays the message "No NetView Response received," the message indicates that an end point server did not respond to your command. This message is generated by the collection point server.Command RoutingThe format for the command routing portion of a NetWare RUNCMD is RUNCMD SP=service_point_name, APPL=NETWARE, SName=server_nameIDREF="FM20675"Table 3-2 shows how to address the NetWare RUNCMD routing parameters for different types of NetWare servers.LBL="3-2" INLINE="F"ID="FM20675"Command Routing Parameter SettingsWIDTH="84"DestinationServer TypeWIDTH="108"Parameter Setting for  SP=service_point_nameWIDTH="96"Parameter Setting for  SName=server_nameWIDTH="84"End point serverWIDTH="108"Enter the PU name of a  collection point server.WIDTH="96"Enter the name of the  end point server.Collection point  server or stand- alone serverEnter the PU name of the  collection point server or  the standalone server.Enter the name of the  collection point server or  the standalone server.Command SecurityThe format for the command security portion of a NetWare RUNCMD is [OP=userid]This command parameter is optional when the NetView security option is disabled on the destination server.When the security feature is enabled on the destination NetWare server, you must include this parameter and replace the userid variable with a valid NetWare user ID. If your NetWare user ID has been designated as a file server console operator, you are restricted to sending NetWare QUERY commands, which request information from the file server. If your NetWare user ID has supervisor-equivalent privileges, you can use all the commands supported by the server.When NetView security is enabled at the NetWare server, a RUNCMD must include a user ID (other than SUPERVISOR) with either supervisor-equivalent privileges or file server console operator status. Although the SUPERVISOR user ID has supervisor-equivalent privileges, the server rejects RUNCMDs that include the SUPERVISOR user ID.The command security feature is always enabled on NMA for NetView servers. (You must provide a user ID.) On NetWare for SAA servers, the NetWare administrator can enable or disable this feature.Server Command ParametersThe format of the server command parameters portion of a NetWare RUNCMD is actionresourceattribute_parameter resource_qualifier command_qualifierIDREF="FM88280"Table 3-3 lists and describes each of the server command parameters for NetWare for SAA and NMA for NetView servers.LBL="3-3" INLINE="F"ID="FM88280"Server Command ParametersWIDTH="108"ParameterWIDTH="312"DescriptionWIDTH="108"actionWIDTH="312"The action parameter specifies what action is to be executed on the  NetWare server. Valid actions includeAddBroadcastDisableDownEnableGetLoadQueryRemoveSetUnloadThe first table under "Command Tables," beginning on IDREF="FM90523"page 3-7,  alphabetically lists the server command parameters according to the  action parameter. "NetWare Command Descriptions," beginning on IDREF="FM75148"page  3-16, describes the function and format of each group of server command  parameters.resourceTheresource parameter specifies the server component that the command  action affects. Valid command resources includeCommunication service (CS)DirectoryFileIPXNLMServerSPXTTSUserVolumeThe second table under "Command Tables" alphabetically lists the server  command parameters according to the resource parameter. "NetWare  Command Descriptions" describes the function and format of each group  of server command parameters.attribute_parameterThis parameter identifies the resource attribute the command affects. In  the QUERY SPX VERSION command, for example, the VERSION  attribute_parameter identifies the SPX parameter (Version) to be returned.  Some commands do not use this parameter.The tables under "Command Tables" and "NetWare Command  Descriptions" list the commands you can send to NetView. If a table lists  one or more attribute parameters for a single command, you must enter  at least one attribute parameter before sending the command. You may  include multiple attribute parameters in the same command.resource_qualifierThis parameter usually names the resource to receive the action. Some  commands do not use this parameter.The tables under "Command Tables" and "NetWare Command  Descriptions" list the commands you can send to NetView. If the resource  qualifier for a command is not enclosed in brackets ([]), you must enter  the resource qualifier. command_qualifierThis parameter further defines the action to be taken on the resource.  Some commands do not use this parameter.The tables under "Command Tables" and "NetWare Command  Descriptions" list the commands you can send to NetView. If the  command qualifier for a command is not enclosed in brackets ([]), you  must enter the command qualifier. Command ExamplesThe following is a sample RUNCMD for a NetWare server: RUNCMD SP=NWSAA1, APPL=NetWare, SName=Sales OP=JSmith Query User DiskSpaceLeft UserName=jbowman VolName=pubsThe command routing parameters define the PU name of a NetWare for SAA server (NWSAA1), the application name (NetWare) of the service, and the destination server name (Sales).The JSmith variable represents the NetWare ID of the NetView operator.The server command parameters in the RUNCMD operate as follows:The QUERY keyword represents the action.The USER keyword indicates the resource to be queried.The DISKSPACELEFT (disk space left) attribute parameter defines what user information the query will return.Thejbowman variable in the USERNAME resource qualifier names the user for which the command will retrieve information.Thepubs variable in the VOLNAME command qualifier identifies the volume for which the command will retrieve information.The following command is an example of a command with multiple attribute parameters. RUNCMD SP=NWSAA1, APPL=NetWare, SName=Sales OP=JSmith Query Server Date TimeIn this example, both DATE and TIME are attribute parameters for the QUERY SERVER command. When this command is sent, NetWare returns the date and time for the specified server.ID="FM90523"Command TablesThis section lists the server command parameters for NetWare v3.1x and NetWare v4.0 servers. IDREF="FM26029"Table 3-4 lists the server command parameters according to the action being performed. IDREF="FM15606"Table 3-5 lists the server command parameters according to the resource on which the action is being performed (for example, a file or directory).The command tables use the following conventions:When the phrase (v1.3 & later) appears in the Action column, the command and all its parameters can be used only with NetWare for SAA v1.3 and later and NMA for NetView v1.3 and later.When the phrase (v1.3 & later) appears adjacent to a single attribute parameter or qualifier, the phrase indicates that parameter or qualifier can be used only with v1.3-and-later servers. Unmarked parameters and qualifiers may be used with v-1.2-and-later servers.When the phrase (NetWare v4.0 & later) appears in the Action column, the command and all its parameters can be used only with NetWare for SAA servers that use NetWare v4.0 and later. These commands do not work with servers that use NetWare v3.1x.These tables list the server command parameters for each command you can send to NetWare. These commands should always be preceded with the following command routing and command security parameters: RUNCMD SP=service_point_name, APPL=NETWARE SName=server_name OP=useridLBL="3-4" INLINE="F"ID="FM26029"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]Add(v1.3 & later)VolumeTrusteeVolName=vnameUserName=unameRights=[ACEFMRSW]BroadcastServerMsg="message"[UserName=uname]DisableServerLoginDisableTTSDownServer[Opts=[01]]EnableServerLoginEnableTTSGet (v1.3 & later  NetWare v4.0  & later)ServerParm="parameter"LoadCSCSName=name[Args="argument"]LoadNLMNLMName=nameQueryCSVersionQueryDirectoryPath=pathQueryDirectoryRightsPath=path[UserName=uname]QueryDirectorySpaceAllowedPath=pathQueryFilePath=path[UserName=uname](v1.3 & later)QueryFileRightsPath=path[UserName=uname]QueryIPXVersionQueryServerQuery(v1.3 & later)ServerDate TimeQueryServerInternetAddrQueryServerLoginStatusQueryServerNumOfVolsQuery(v1.3 & later) (v1.3 & later)ServerDate=dateTime=timeSet(v1.3 & later,  NetWare v4.0  & later)ServerParm="parameter"Value=valueSetVolumeUSpaceAllowed =spaceVolName=vnameUserName=unameSet(v1.3 & later)VolumeNoRestriction VolName=vnameUserName=unameUnLoadCSCSName=nameUnLoadNLMNLMName=nameLBL="3-5" INLINE="F"ID="FM15606"NetWare Commands Sorted by ResourceWIDTH="72"ActionWIDTH="72"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="72"LoadWIDTH="72"CSWIDTH="84"CSName=nameWIDTH="84"WIDTH="84"Query(v1.3 & later)CSVersionUnLoadCSCSName=nameAddDirectoryTrusteePath=pathUserName=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](v1.3 & later)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]]EnableServerLoginGet(v1.3 & later,  NetWare v4.0  & later)ServerParm="parameter"QueryServerQuery(v1.3 & later)ServerDateTimeQueryServerInternet_AddrQueryServerLoginStatusQueryServerNumberOfVolsQuery(v1.3 & later)ServerVolumesSetServerDate=dateTime=timeSet(v1.3 & later,  NetWare v4.0  & later)ServerParm="parameter"Value=valueQuerySPXConfigQuerySPXVersionDisableTTSEnableTTSQueryTTSStatusQueryUserDiskSpaceLeftUserName=unameVolName=vnameQueryUserDiskUsageUserName=unameVolName=vnameAdd(v1.3 & later)VolumeTrusteeVolName=vnameUserName=unameRights=[ACEFMRSW]QueryVolumeVolName=vnameQueryVolumeDiskUsageVolName=vnameUserName=unameQueryVolumeUSpaceAllowedVolName=vnameUserName=unameRemoveVolumeTrusteeVolName=vnameUserName=unameSetVolumeUSpaceAllowed =spaceVolName=vnameUserName=unameSet(v1.3 & later)VolumeNoRestriction VolName=vnameUserName=unameID="FM75148"NetWare Command DescriptionsThis section describes the function and the server command parameters for each command you can send to NetWare. The server command parameters in each command should always be preceded with the following command routing and command security parameters: RUNCMD SP=service_point_name, APPL=NETWARE SName=server_name [OP=userid]Many command descriptions include tables that use the following conventions:When the phrase (v1.3 & later) appears in the action column, the command and all its parameters can be used only with NetWare for SAA v1.3 and later and NMA for NetView v1.3 and later.When the phrase (v1.3 & later) appears adjacent to a single attribute parameter or qualifier, the phrase indicates that the parameter or qualifier can be used only with v1.3-and-later servers. Unmarked parameters and qualifiers may be used with v1.2-and-later servers.When the phrase (NetWare v4.0 & later) appears in the action column, the command and all its parameters can be used only with NetWare for SAA servers that use NetWare v4.0 and later. These commands do not work with servers that use NetWare v3.1x.ADD VOLUME, DIRECTORY, or FILE TRUSTEEThe ADD commands allow you to add a trustee to a volume, directory, or file on a NetWare server. A trustee is a NetWare user that is entitled to use the volume, directory, or file. IDREF="FM23455"Table 3-6 shows the server command parameters for each ADD command.LBL="3-6" 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]Add(v1.3 & later)VolumeTrusteeVolName=vnameUserName=unameRights=[ACEFMRSW]The path variable specifies the NetWare directory path to the volume, directory, or file. The path may include the volume, directory, subdirectory, and filename. For example: Volume:MyDir\MySubDir\MyFile.txtTheuname variable specifies the name of the user that will be allowed access to the volume, directory, or file.The Rights command qualifier specifies how the user will be able to use the directory, file, or volume. The Rights command qualifier must be followed by one or more of the letters shown in IDREF="FM42469"Table 3-7.LBL="3-7" INLINE="F"ID="FM42469"NetWare RightsWIDTH="60"LetterWIDTH="108"RightWIDTH="240"DescriptionWIDTH="60"AWIDTH="108"Access ControlWIDTH="240"Allows users to modify trustee assignments and Inherited  Rights Masks.CCreateAllows users to create files and subdirectories.EEraseAllows users to delete files and subdirectories.FFile ScanAllows users to see files.MModifyAllows users to change directory and file attributes and  to rename subdirectories and files.RReadAllows users to open and read files.SSupervisoryGrants all rights to the directory or file.WWriteAllows users to write to files.When you enter the rights letters, enter them according to the following rules:The letters may be entered in any sequence.The letters you type may be uppercase or lowercase letters.Do not enter spaces before, between, or after the letters.To assign all rights, enter ALL after the Rights= command qualifier. You can enter ALL in any combination of uppercase and lowercase letters.The Rights command qualifier simultaneously defines all new rights for the directory, file, or volume. To add rights to a directory, file, or volume, you must include the letters for the new rights and the letters for all existing rights that are to be retained. To review the rights assigned to a directory or file, use the QUERY DIRECTORY RIGHTS or QUERY FILE RIGHTS command. For more information on path or NetWare rights, see NetWare v3.1x Concepts or NetWare 4.0 Concepts.BROADCASTThe BROADCAST command sends a message to workstation users that are connected to the destination NetWare server. You can broadcast a message to one user or to all users. Consider using this command to warn users before shutting down a server.The BROADCAST command requires the following parameters: Broadcast Server Msg="message" [UserName=uname]When sending commands, replace themessage variable with the message you want to send (the quotation marks are required). To send a message to all workstation users that are currently logged in, do one of the following:Send the command without the UserName=uname command qualifier.Send the command with the UserName=uname command qualifier and replace the uname variable with ALL (UserName=ALL).To send a message to one or more users, send the command with a UserName=uname command qualifier for each user. For example: Broadcast Server Msg="Server is going down in 5 minutes." [UserName=jbowman] [UserName=vjang]Theuname variable specifies the NetWare user ID of the user that will receive the message.DISABLE SERVER LOGIN or TTSThe DISABLE commands can be used to disable server login by workstations or to disable the TTS.Consider disabling server login when you have performance problems with the server. Disabling server login prevents additional workstations from logging in. Workstations that are already logged in remain logged in.Novell recommends that you do not disable TTS. TTS protects database applications from corruption caused when a server, workstation, or network failure interrupts a database transaction. TTS protects the database by backing out incomplete transactions that result from a failure in a network component. IDREF="FM20641"Table 3-8 shows the parameters required by the DISABLE SERVER LOGIN and DISABLE TTS commands.LBL="3-8" INLINE="F"ID="FM20641"NetWare DISABLE CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"DisableWIDTH="84"ServerWIDTH="84"LoginWIDTH="84"WIDTH="84"DisableTTSDOWN SERVERThe DOWN SERVER command brings down the NetWare server. This command uses the following parameters: Down Server [Opts=[01]]When the DOWN SERVER command is entered without the [Opts=[01]] command qualifier, the server shuts down immediately, regardless of the current state of server files. If files are open, changes made to those files may be lost.The server may shut down before it responds to the DOWN SERVER command. When this happens, NCCF may display a command timeout message.When the DOWN SERVER command is entered with the [Opts=[10]] command qualifier, you must choose option 1 or option 0 (zero). Option 1 (Opts=1) shuts down the server immediately, regardless of the current state of server files. Option 0 (Opts=0) shuts down the server only when no server files are open; if any server files are open, the server is not shut down.When you bring down a server, the server is instantly unavailable to all users and to the NetWare administrator. Before bringing down a server, consider using the Broadcast command to warn all users. Also, you should warn the NetWare administrator before bringing down a server.ENABLE SERVER LOGIN or TTSThe ENABLE commands can be used to enable server login by workstations or to enable TTS.TTS protects database applications from corruption caused when a server, workstation, or network failure interrupts a database transaction. TTS protects the database by backing out incomplete transactions that result from a failure in a network component.IDREF="FM24015"Table 3-9 shows the parameters required for the ENABLE commands.LBL="3-9" 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"EnableTTSID="FM30134"GET SERVERThe GET SERVER command allows you to display the value of select server parameters. IDREF="FM76932"Table 3-10 shows the syntax of the GET SERVER command.LBL="3-10" INLINE="F"ID="FM76932"NetWare GET SERVER CommandWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParametersWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"Get(v1.3 & later,  NetWare v4.0 &  later)WIDTH="84"ServerWIDTH="84"Parm="parameter"WIDTH="84"WIDTH="84"The GET SERVER command operates only on NetWare v4.0 servers. To view one of the server parameters, enter the command and replace theparameter variable with one of the following parameters: Allow Unencrypted Passwords Immediate Purge of Deleted Files Maximum Directory Cache Buffers Maximum File Locks Maximum File Locks Per Connection Maximum Outstanding NCP Searches Maximum Packet Receive Buffers Maximum Record Locks Maximum Record Locks Per Connection Minimum Directory Cache Buffers Minimum File Cache Buffers Volume Low Warn All Users Volume Low Warning ThresholdYou can enter a parameter name in uppercase or lowercase letters. You must enter a single space character between each pair of words in the parameter name, and you must enclose the parameter name in quotation marks. Do not enter additional space characters before or after the parameter name.The NetWare administrator can use the NetWare GET command to view the settings of all these parameters on NetWare v3.1x and NetWare v4.0 servers.Descriptions of these attribute parameters begin on IDREF="FM55556"page 3-37.LOAD CS or NLMThe LOAD commands load a communication service or NLM. IDREF="FM27659"Table 3-11 lists the parameters used by the LOAD commands.LBL="3-11" INLINE="F"ID="FM27659"NetWare LOAD CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"LoadWIDTH="84"CSWIDTH="84"CSName=nameWIDTH="84"WIDTH="84"LoadNLMNLMName=name[Args="argument"]Thename variable must be replaced with the name of the communication service or NLM. When loading an NLM, you may use the optional [Args="argument"] command qualifier to include any arguments or parameters that are required when you are loading the command from the NetWare console. These arguments or parameters must replace the argument variable and be enclosed in quotation marks. For more information on LOAD NLM parameters, refer to the NetWare documentation for the NLM.If you send a LOAD command with an incomplete set of parameters for an NLM or communication service, a prompt for the missing parameters may appear on the server console. The NLM or communication service does not continue execution until the missing information is entered at the server console. You are not notified about the missing parameters, and the NLM or communication service may appear to be operating when it is not.When loading an NLM that has arguments, separate the arguments with space characters.QUERY CS VERSIONThe QUERY CS VERSION command returns the version level of the communication executive. This command uses the following parameters: Query CS VersionThe QUERY CS VERSION command operates only with NetWare for SAA v1.3 or later.QUERY DIRECTORYAs shown in IDREF="FM17890"Table 3-12, the QUERY DIRECTORY command has three forms.LBL="3-12" 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 rights are listed in IDREF="FM42469"Table 3-7.The QUERY DIRECTORY SPACEALLOWED command returns the amount of available space in the specified directory and the amount of space reserved for the directory.Use the path variable to specify the directory for which you want information. When using the QUERY DIRECTORY RIGHTS command, use the uname variable to specify the user for which you want information.QUERY FILEAs shown in IDREF="FM37771"Table 3-13, the QUERY FILE command has two forms.LBL="3-13" 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](v1.3 & later)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 if a user name is included. The user name is optional.When the QUERY FILE command includes the Rights attribute parameter, the command returns only the rights assigned to the specified user.Use thepath variable to specify the file for which you want information. The uname variable specifies the user whose file rights you want to view. The USERNAME command qualifier is optional when the QUERY FILE command is entered without the Rights attribute parameter. To display the file information and the rights for a specific user, include the USERNAME command qualifier and replace the uname variable with the user's NetWare ID.QUERY IPX VERSIONThe QUERY IPX command returns the IPX version information. This command uses the following parameters: Query IPX VersionQUERY SERVERIDREF="FM33375"Table 3-14 lists the parameters used by each of the QUERY SERVER commands.LBL="3-14" 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"Query(v1.3 & later)ServerDate TimeQueryServerInternetAddrQueryServerLoginStatusQueryServerNumOfVolsQuery(v1.3 & later)ServerVolumesWhen 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 an attribute parameter, NetWare returns the information requested by the parameter (see IDREF="FM41512"Table 3-15).LBL="3-15" INLINE="F"ID="FM41512"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 3-16, the QUERY SPX command has two forms.LBL="3-16" 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 QUERY TTS command returns the status of the TTS, which is either enabled or disabled. TTS protects database applications from corruption caused when a server, workstation, or network failure interrupts a database transaction. TTS protects the database by backing out incomplete transactions that result from a failure in a network component.The format for this command is Query TTS StatusQUERY USERThe QUERY USER command has forms, which are listed in IDREF="FM12902"Table 3-17.LBL="3-17" 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.Theuname variable specifies the user for which you want information. The vname variable specifies the volume for which you want the information.QUERY VOLUMEIDREF="FM40076"Table 3-18 lists the three forms of the QUERY VOLUME command.LBL="3-18" 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 (mounted,hashing, or removable)The QUERY VOLUME DISKUSAGE command returns the number of directories, files, and blocks being used by a user. The QUERY VOLUME USPACEALLOWED command returns the amount of space allowed to the specified user.The vname variable specifies the volume for which you want information; the uname variable specifies the user for which you want information.REMOVE VOLUME, DIRECTORY, or FILE TRUSTEEThe REMOVE commands allow you to remove a trustee from a volume, directory, or file on a NetWare server. A trustee is a NetWare user that is entitled to use the volume, directory, or file.IDREF="FM33020"Table 3-19 shows the parameters used by the REMOVE commands.LBL="3-19" 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=unameWhen using the REMOVE DIRECTORY TRUSTEE and REMOVE FILE TRUSTEE commands, the path variable specifies the NetWare directory path to the volume, directory, or file from which the trustee will be removed. The path may include the volume, directory, subdirectory, and filename. For example: Volume:MyDir\MySubDir\MyFile.txtFor more information on specifying a directory or file path, seeNetWare v3.1x Concepts orNetWare 4.0 Concepts.Theuname variable specifies the name of the user that will be denied access to the file or directory.When using the REMOVE VOLUME TRUSTEE command, the vname variable specifies the volume from which the trustee will be removed.SET DIRECTORYThe SET DIRECTORY commands allow you to set one or more properties of a directory with a single command. IDREF="FM21598"Table 3-20 shows the parameters used by the SET DIRECTORY commands.LBL="3-20" INLINE="F"ID="FM21598"NetWare SET DIRECTORY CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParametersWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"SetWIDTH="84"DirectoryWIDTH="84"ADate=dateArDate=dateArTime=timeCDate=dateCTime=timeOwner=nameUDate=dateUTime=timeWIDTH="84"Path=pathWIDTH="84"SetDirectorySpaceAllowed =spacePath=pathThe attribute parameters in IDREF="FM21598"Table 3-20 define the directory properties to be set. IDREF="FM10943"Table 3-21 shows the properties that each attribute parameter controls.LBL="3-21" 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 the time 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 thetime 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 thetime 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.Thepath variable identifies the directory to be modified.SET FILEThe SET FILE command allows you to set one or more properties of a file with a single command. IDREF="FM34003"Table 3-22 shows the parameters used by the SET FILE command.LBL="3-22" INLINE="F"ID="FM34003"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="FM34003"Table 3-22 defines the directory properties to be set. IDREF="FM16023"Table 3-23 shows the properties that each attribute parameter controls.LBL="3-23" INLINE="F"ID="FM16023"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 thedate variable  with the new creation date for the file.CTime=timeFile creation time. Replace thetime 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.Thepath variable identifies the directory path to the file you are modifying. Thepath variable must include the name of the file.ID="FM54338"SET SERVERThe SET SERVER commands allow you to set one or more properties of a server with a single command. IDREF="FM32888"Table 3-24 shows the parameters used by the SET SERVER commands.LBL="3-24" INLINE="F"ID="FM32888"NetWare Set Server CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParametersWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"Set(v1.3 & later)WIDTH="84"ServerWIDTH="84"Date=dateTime=timeWIDTH="84"WIDTH="84"Set(v1.3 & later,  NetWare v4.0 &  later)ServerParm="parameter"Value=valueTo set the server date, use the Date attribute parameter and replace thedate variable with the new date. To set the server time, use the Time attribute parameter and replace the time variable with the new server time. To set one of the server parameters, use the Parm attribute parameter and replace the parameter variable with one of the following parameters: Allow Unencrypted Passwords Immediate Purge of Deleted Files Maximum Directory Cache Buffers Maximum File Locks Maximum File Locks Per Connection Maximum Outstanding NCP Searches Maximum Packet Receive Buffers Maximum Record Locks Maximum Record Locks Per Connection Minimum Directory Cache Buffers Minimum File Cache Buffers Volume Low Warn All Users Volume Low Warning ThresholdThe SET SERVER PARM command operates only with NetWare v4.0 servers. If you need to adjust one of these parameters in a NetWare v3.1x server, contact the NetWare administrator. The NetWare administrator can use the NetWare SET command to set all these parameters on NetWare v3.1x and NetWare v4.0 servers.You can enter a parameter name in uppercase or lowercase letters. You must enter a single space character between each pair of words in the parameter name, and you must enclose the parameter name in quotation marks. Do not enter additional space characters before or after the parameter name.The following subsections provide additional information on each of these attribute parameters. For more information on a parameter, see the NetWare 4.0 Utilities Reference.ID="FM55556"Allow Unencrypted PasswordsThis parameter controls the use of unencrypted passwords. An ON setting allows users to use both unencrypted and encrypted passwords. An OFF setting allows users to use only encrypted passwords.Supported values: ON and OFFDefault: OFFImmediate Purge of Deleted FilesThis parameter controls the salvageable file feature.Supported values: ON and OFFDefault: OFFIf this parameter is set to OFF, files can be salvaged with a utility program. See SALVAGE in the NetWare Version 3.1x Utilities Reference or FILER in the NetWare 4.0 Utilities Reference.If this parameter is set to ON, all files are immediately purged when they are deleted. The ON setting disables all NetWare salvage features.Maximum Directory Cache BuffersThis parameter sets the maximum cache buffers used for directory cache buffers. When the operating system allocates a directory cache buffer, the allocation is permanent until the file server reboots; the buffers do not return to file caching when the need for directory cache buffers decreases.This parameter keeps the operating system from allocating too many directory cache buffers so that memory is available for other server processes.Supported values: 20 to 4000Default: 500Maximum File LocksThis parameter controls how many opened and locked files the operating system can handle.Supported values: 100 to 100000Default: 10000Maximum File Locks Per ConnectionThis parameter controls how many opened and locked files a station can use at one time.Supported values: 10 to 1000Default: 250Maximum Outstanding NCP SearchesThis advanced parameter determines the maximum number of NetWare Core Protocol (NCP) directory searches that can be processed at the same time.Supported values: 10 to 1000Default: 51Maximum Packet Receive BuffersThis parameter determines the maximum number of packet receive buffers that the operating system can allocate.Supported values: 50 to 200Default: 100Maximum Record LocksThis parameter controls how many record locks the operating system can handle.Supported values: 100 to 200000Default: 20000Maximum Record Locks Per ConnectionThis parameter controls how many record locks a station can use at one time.Supported values: 100 to 10000Default 500Minimum Directory Cache BuffersThis parameter reserves memory for directory cache buffers.Supported values: 10 to 2000Default: 20If directory searches take too long, increase this parameter in small increments until directory searches can be done quickly. Do not increase this parameter beyond the value that provides satisfactory performance. Once memory is assigned to directory cache buffers, it cannot be used for any other server process.Minimum File Cache BuffersThis parameter sets the minimum number of cache buffers that the operating system can allow for file caching. All memory not allocated for other processes is given to file caching. As memory is requested for other uses, the file server gives up cache buffers. This limit specifies when the file server should stop giving file cache buffers to other processes.Supported values: 20 to 1000Default: 20If you set the minimum too high, other server processes may not be able to allocate necessary memory resources. For example, a loadable module could fail to load because the server has run out of available memory.Volume Low Warn All UsersThis parameter controls whether the operating system warns users when a volume is almost full.Supported values: ON and OFFDefault: ONIf you choose not to warn your users, check the volume usage daily with the QUERY VOLUME command.Volume Low Warning ThresholdThis parameter defines the volume usage level that triggers a "volume low" warning message to volume users. When the unused volume space decreases to below the value set by this parameter, a warning is issued if the Volume Low Warn All Users parameter is set to ON.Supported values: 0 to 1000000 blocksDefault: 256 blocksIf your volumes have been assigned different block sizes, each volume will have a different amount of free space when the warning is issued.SET VOLUMEAs shown in IDREF="FM38671"Table 3-25, the SET VOLUME command has two forms.LBL="3-25" 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=unameSet(v1.3 & later)VolumeNoRestriction 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 NORESTRICTION command removes all restrictions on the amount of space the specified user can use on the specified volume. This command operates only with NetWare for SAA v1.3 or later and NMA for NetView v1.3 or later.Thespace variable defines the allocated space in kilobytes, while the vname anduname variables define the volume and user to which the command applies.ID="FM10411"UNLOAD CS or NLMThis command unloads a communication service or NLM. IDREF="FM11795"Table 3-26 lists the parameters used by the UNLOAD CS and UNLOAD NLM commands.LBL="3-26" INLINE="F"ID="FM11795"NetWare UNLOAD CommandsWIDTH="84"ActionWIDTH="84"ResourceWIDTH="84"AttributeParameterWIDTH="84"ResourceQualifierWIDTH="84"CommandQualifierWIDTH="84"UnLoadWIDTH="84"CSWIDTH="84"CSName=nameWIDTH="84"WIDTH="84"UnLoadNLMNLMName=nameThename variable must be replaced with the name of the communication service or NLM to be unloaded.If you send an UNLOAD command for an NLM or 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. You are not notified about the failure, and the NLM or communication service may appear to be unloaded when it is not.LBL="A"ID="FM84495"Installing NetWare Code Point Messages for NetViewThis 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) systemID="FM15068"Do You Need to Install?Beginning with NetView v2.1, all versions of NetView contain all the code point messages required to display NetWare alerts. To find out the version of NetView you are using, contact a NetView operator or your systems programmer. If the host is running NetView v2.1 or higher, you do not need to install code point messages.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 NetWare for SAA v1.2 or later are already installed on the NetView host. Once the code points are installed for one v1.2 server, the installed code points support all v1.2-and-later servers.Installation OverviewThis section provides a general overview of the installation process. Detailed procedures for the VM and MVS host systems appear later in this appendix.IDREF="FM24747"Figure A-1 shows the equipment you may need for installing the code points in NetView.LBL="A-1"ID="FM24747"Installation OverviewFILE="nvorg004.pbm"To install the code point messages, you must perform the following tasks:Task 1. Prepare to transfer files to the host.The NetWare administrator should install NetWare for SAA (or a product with similar features). The NetWare administrator must be able to access the host from a workstation on the NetWare LAN.Using a workstation configured with NetWare 3270 LAN Workstation` software with file transfer capabilities (or a product with similar features), the NetWare administrator establishes a host session and accesses the NetView RUN disk.Task 2. Install the code point messages.Using the NetWare 3270 LAN Workstation (or a product with similar features), the NetWare administrator transfers the code point files from the NetView Support Files disk to the NetView RUN disk.Using a host terminal or 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="FM95680"Preparing for File Transfer (VM and MVS Installations)To prepare for transferring code point files to the host, follow the procedures below.Complete the NetWare for SAA installation so that the NetWare administrator can access the host from a workstation on the NetWare LAN.Locate the disk with the code point files.The code point files are located on the diskette labeled NetView Support Files in the NetWare for SAA package.The code point files are located in the CP directory on NMA for NetView v1.3, Disk 2.Start up a NetWare 3270 LAN Workstation that has file transfer software installed; then establish a host session.You must use a workstation with a 3.5-inch floppy disk drive. To establish the host session, you can useNetWare 3270 LAN Workstation for Windows(tm) softwareNetWare 3270 LAN Workstation for DOS(tm) softwareFile 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, refer to the publications for the products you are using.ID="FM15239"Installing NetView Code Points in VM SystemsBefore starting the procedures in this section, complete the procedures in the preceding section. IDREF="FM95680"See "Preparing for File Transfer (VM and MVS Installations)" on 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, use the following procedure.Using a host session in the NetWare 3270 LAN Workstation, log on to MAINT; then access the NetView RUN disk by entering ACCESS 334 AIf you do not know how to log on to MAINT, contact your host systems programmer.Using the file transfer software on the NetWare 3270 LAN Workstation, transfer the code point files to the NetView RUN disk.When transferring the files, use the ASCII, CRLF, and fixed record format options. If you are using the SEND.EXE program, for example, enter the following at the DOS prompt (>): SEND BNJ81UTB.NCC BNJ81UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ82UTB.NCC BNJ82UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ92UTB.NCC BNJ92UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ93UTB.NCC BNJ93UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ94UTB.NCC BNJ94UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ95UTB.NCC BNJ95UTB NCCFLST A (ASCII CRLF RECFM F SEND BNJ96UTB.NCC BNJ96UTB NCCFLST A (ASCII CRLF RECFM FUsing a host terminal or a host session in 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=NOVELLUsing a host terminal or host session in the NetWare 3270 LAN Workstation, open the NetView startup command file for editing by typing XEDIT NETSTRT GCSWithin the NetView startup file, locate the GLOBAL command; insert the word NOVELL immediately after the word LOADLIB; save the change; and close the file.This step includes the Novell library in the list of NetView libraries that are loaded at startup. The modified GLOBAL command will appear similar to `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 system maintenance period.When NetView has completed shutting down, log on to the NetView virtual machine; then start up NetView by entering the following VM command: CP IPL GCSWhile NetView is starting up, the startup messages may include BNJ090I NETVIEW USER CODE POINT TABLE BNJ92UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ93UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ94UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ95UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ96UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ81UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ82UTB IS 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 command #CP DISCLog on to NetView. When the NetView main menu appears, select NPDA 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 impdIn order for NetWare messages to be displayed, the recording and viewing filters must be set each time NetView is started. To simplify NetView startup, enter these commands in a CLIST.Installing NetView Code Points in MVS SystemsBefore starting the procedures in this section, complete the procedures in "Preparing for File Transfer (VM and MVS Installations)" on IDREF="FM95680"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:Using a host session in the NetWare 3270 LAN Workstation, 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 a NetWare 3270 LAN Workstation host session and the Interactive System Productivity Facility (ISPF), allocate a partitioned data set (PDS) that is 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 the files, use the ASCII and CRLF options. If you are using the SEND.EXE program, for example, enter the following at the DOS prompt (>): SEND BNJ92UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ92UTB)' ASCII CRLF SEND BNJ93UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ93UTB)' ASCII CRLF SEND BNJ94UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ94UTB)' ASCII CRLF SEND BNJ95UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ95UTB)' ASCII CRLF SEND BNJ96UTB.NCC 'SYS2.NTVW.CODE.POINTS(BNJ96UTB)' ASCII CRLF 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, use the ISPF editor to open the member 'SYS2.NTVW.CODE.POINTS(INSTALL)'Follow the directions inside the job control language (JCL) listing.These instructions appear under the labelIDREF="FM46559"See "Code Point Installation JCL" on page A-13 for a sample JCL listing for code points installation.For additional information on using listings similar to this one, refer to theNetwork 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 bring 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 system maintenance period.At the primary MVS operator console, start NetView by entering the following command: S CNMPROCWhile NetView is starting up, the startup messages should include BNJ090I NETVIEW USER CODE POINT TABLE BNJ92UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ93UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ94UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ95UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ96UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ81UTB IS AVAILABLE BNJ090I NETVIEW USER CODE POINT TABLE BNJ82UTB IS 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.Log on to NetView. When the NetView main menu appears, select NPDA 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, the recording and viewing filters must be set each time NetView is started. To simplify NetView startup, enter these commands in a CLIST.LBL=" A-1"ID="FM46559"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 