#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'ConceptsConceptsNovell, Inc.DisclaimerNovell, 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.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 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.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=15 ID="BP1"ID="FM87016"How to Use This ManualRENDERAS="SECT1"IntroductionConcepts is an extended glossary of terms related to the NetWare® network operating system. Use this manual as a reference if you have questions during the installation and operation of your network.Concepts are arranged alphabetically. Some entries contain "See" or "See also" references to other entries where concepts are explained in detail. Some entries refer you to related information in other manuals.RENDERAS="SECT1"Documentation ConventionsThis manual uses the following Novell® conventions:RENDERAS="SECT2"Asterisk ( * )An asterisk denotes a trademarked name belonging to a third-party company. Novell trademarks are denoted with specific trademark symbols (®, TM, etc.).An ownership listing of all (Novell and third-party) trademarks cited in a manual can be found either on the disclaimer page in the front or in a "Trademarks" section at the back of printed manuals. A trademarks list is also available in the DynaText* online documentation.RENDERAS="SECT2"CommandsBoldface characters indicate items that you type, such as IDXID="w1654"BOOK="_idx" COLLECTION="nw41" TIDREF="i683"
commands and options. You can use any combination of uppercase and lowercase letters.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\A INSTALL
PAGENUM=16 ID="BP2"RENDERAS="SECT2"Delimiter Bar ( | )In syntax examples, a delimiter bar separating two command options indicates that you can choose one of the options.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"-S | -RDo not type the bar.RENDERAS="SECT2"DOS CommandsIDXID="w1655"BOOK="_idx" COLLECTION="nw41" TIDREF="i683"IDXID="w1656"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"IDXID="w1657"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"IDXID="w1658"BOOK="_idx" COLLECTION="nw41" TIDREF="i683"
DOS commands and command option letters are shown in uppercase letters. For example: FTPD.Because DOS is not case-sensitive, you can type DOS commands in uppercase or lowercase letters.RENDERAS="SECT2"DOS Filenames, Directory Names, and PathnamesDOS filenames, directory names, and pathnames are shown in uppercase letters. For example, AUTOEXEC.BAT.Because DOS is not case-sensitive, you can type these names in uppercase or lowercase letters.RENDERAS="SECT2"EllipsesEllipses in syntax examples indicate that parameters, options, or settings can be repeated.For example, in the commandFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN SERVER1/SUPERVISOR /option...you could replace option with any number of available options.PAGENUM=17 ID="BP3"RENDERAS="SECT2"EmphasisItalic type indicates emphasized text. For example:Remember to load the driver before you install the application.RENDERAS="SECT2"IconsChecklists, which often contain prerequisites, are marked with the "Checklist" icon to the left of this text.Procedures to follow in order to accomplish a specified task are marked with the "Procedure" icon to the left of this text.Additional or "nonessential" but noteworthy information is marked with the "Note" icon to the left of this text.Vital information about system or software requirements, etc., that deserves particular attention is marked with the "Important" icon to the left of this text.Guidelines or tips about fine-tuning, optimizing, etc., which might be applicable to your site or situation but maybe not to all, are emphasized with the "Suggestion" icon to the left of this text.Warnings about potential danger to data, hardware, or person are emphasized with the "Warning" icon to the left of this text. RENDERAS="SECT2"Key NamesIDXID="w1659"BOOK="_idx" COLLECTION="nw41" TIDREF="i2021"
Angle brackets surround the name of a key. For example, MOREINFO="NONE"<Enter> corresponds to the MOREINFO="NONE"Enter key on your keyboard. MOREINFO="NONE"<Ctrl>+<c> means hold down the MOREINFO="NONE"Ctrl key and simultaneously type the letter MOREINFO="NONE"c (in lowercase, in this case).RENDERAS="SECT2"NET.CFG File Section Headings and Parameter SettingsIDXID="w1660"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"IDXID="w1661"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"IDXID="w1662"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"IDXID="w1663"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"
NET.CFG section headings and parameter settings are shown in uppercase when used as a reference item and lower case when used in syntax or working examples.For example:PAGENUM=18 ID="BP4"NETBIOS VERIFY TIMEOUT specifies how often in (ticks) NetBIOS sends a keep-alive packet to the other side of a session to preserve the session.If no packets are being exchanged on the NetBIOS session by the software that established the session, NetBIOS sends packets at regular intervals to make sure that the session is still valid.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios verify timeout numberReplace number with a number of ticks. COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"54 (approximately 3 seconds)COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 65,535COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To make NetBIOS wait longer before sending a request- for-acknowledgment packet, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios verify timeout 1350Because interpretation of this file is not case-sensitive, you can type its contents in uppercase or lowercase letters.RENDERAS="SECT2"OptionsIn syntax examples, braces indicate that you are required to choose one of the enclosed options. For example, the following notation means that you must include a 0 or a 1 in the command:FORMAT="LINESPECIFIC"MOREINFO="NONE"{0, 1}RENDERAS="SECT2"Square BracketsIn syntax examples, boldface type enclosed in square brackets indicates command options that you can type as needed. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"FTP [ -D ] [ -F ]
PAGENUM=19 ID="BP5"RENDERAS="SECT2"System ResponseMonospace type shows system-generated responses that appear on your workstation screen. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"TNVT220>RENDERAS="SECT2"VariablesItalic type indicates variables---descriptive item names, such as command parameters---that you replace with appropriate values.For example, in the command:FORMAT="LINESPECIFIC"MOREINFO="NONE"FTP -F remote_hostyou type the name of a computer on your network in place of remote_host.RENDERAS="SECT2"UNIX CommandsIDXID="w1664"BOOK="_idx" COLLECTION="nw41" TIDREF="i4652"IDXID="w1665"BOOK="_idx" COLLECTION="nw41" TIDREF="i683"
UNIX® commands are shown in boldface letters. For example, MOREINFO="NONE"vi. Because UNIX is case-sensitive, these commands are usually lowercase. Type UNIX commands exactly as shown.RENDERAS="SECT2"UNIX Filenames, Directory Names, and PathnamesIDXID="w1666"BOOK="_idx" COLLECTION="nw41" TIDREF="i4652"IDXID="w1667"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"
UNIX filenames, directory names, and pathnames are shown in italics. For example, /etc/hosts.Because UNIX is case-sensitive, these names usually are in lowercase letters. Type UNIX filenames exactly as shown.RENDERAS="SECT1"Online HelpMARK=BULLETContext-sensitive help. If you are using a NetWare menu utility and want more information about how to complete a task, press <MOREINFO="NONE"F1>.If you are unsure how to use a command, type the command name and add the /? option for help. For example, for help with the RIGHTS command, type "RIGHTS /?".PAGENUM=20 ID="BP6"Online MS Windows help. The Microsoft* (MS) Windows help viewer allows you to read NetWare help developed for the MS Windows environment. To access the NetWare help screens within MS Windows, press <MOREINFO="NONE"F1> or the "?" button.DynaText* online documentation. The DynaText viewer allows you to read NetWare documentation from your DOS, MS Windows, Macintosh*, UNIX, or OS/2* workstation.All NetWare 4TM and 3.12 documentation except the Quick Access Guide are available on the CLASS=DISKNetWare Online Documentation CD-ROM.RENDERAS="SECT1"Additional Help ResourcesMARK=BULLETNovell Authorized Service CenterSM (NASC) locations. NASCSM facilities are local support providers authorized and supported by Novell. They provide both telephone and on-site assistance, and should be your first source for technical support.For the Novell Authorized Service Center nearest you, in the U.S. and Canada call 1-800-338-NASC.Hardware documentation. Many network problems occur because of malfunctioning hardware.If you can isolate a problem to a certain computer component or cable segment, check the manuals that came with the hardware involved.NetWare Management SystemTM (NMS) services. NMSTM services help you manage the cabling system, computers, software, and other components of the network.For more information about using NMS on your network, contact your Novell Authorized ResellerCLM representative.Other Novell publications. NetWare Applications Notes and Research Reports cover technical aspects of NetWare based system design, implementation, and management.Application Notes is a collection of technical articles published monthly. Research Reports is published as the research becomes available.To purchase subscriptions and back issues of these publications from within the United States or Canada, call the Novell Research Order Desk at 1-800-UPDATE1. From other locations, call 801-429-5380.PAGENUM=21 ID="BP7"Third-party books and periodicals. A number of books on NetWare, including books published by Novell PressTM publishing, are available at most bookstores.In addition, numerous networking periodicals give advice on configuring, managing, and troubleshooting your network.NetWire® forum on the CompuServe bulletin board. A fairly inexpensive way to get up-to-date advice and patches is through NetWire on the CompuServe bulletin board.To open a CompuServe account, call one of the following numbers and ask for "Representative 200"MARK=BULLETIn the United States or Canada: 1-800-524-3388In the United Kingdom: 0800-289-378In Germany: 0130-37-32In other European countries: 44-272-255-111In locations other than the United States, Canada, or Europe, use the appropriate country code for the U.S. and call 614-457-0802. Ask for "Representative 200." This phrase identifies you as a Novell customer.Technical Support Database and NetWire forum on the Internet. The Novell FTP sites support access through FTP, Gopher, and World Wide Web (WWW) systems. Over 9,000 documents exist on the WWW system for providing technical hints and information.To access the Novell Internet sites, log in as ANONYMOUS and use your E-mail address as your password.   Contact one of the following site addresses:TYPE="VERT"In the United States: ftp.novell.comIn Germany: ftp.novell.deIn the United Kingdom: ftp.salford.ac.ukIn Canada: novell.nrc.caSee public areas in these sites for possible listings of other sites' addresses.FaxBack Service. Novell provides a FaxBack Service for obtaining additional product information to help with support needs.To access the Novell FaxBack Service, complete the following steps:PAGENUM=22 ID="BP8"MARK=BULLETWithin the continental United StatesTYPE="VERT"1. Dial 1-800-NETWARE (1-800-638-9273).TYPE="VERT"2. Press #1 (the "Presale Product Information and Upgrade Information" option).TYPE="VERT"3. Again press #1 (the "Receive Product Information via Fax" option).Outside the continental United StatesTYPE="VERT"Dial 1-801-429-2772. You are connected directly to the FaxBack Service.Follow the directions provided on the phone. You are prompted to enter a document number and then a fax number to send the document to.Network Support Encyclopedia Professional VolumeSM package. This encyclopedia gives customers access to regularly updated information on products and services---plus patches, fixes, and more---from Novell and other vendors.The package is distributed on CD-ROM on a subscription basis. Updates are sent out several times each year. More information is available on NetWire or from your Novell Authorized Reseller.Troubleshooting hardware and software. Specialized hardware and software packages, such as the Novell LANalyzer® software, are available to help you isolate network problems.Customer service. You can contact your Novell Authorized Reseller for technical assistance.Most Novell Authorized Resellers have Certified NetWare EngineerSM representatives on their staffs ready to assist users with their networking problems.RENDERAS="SECT1"User CommentsWe are continually looking for ways to make our products and our manuals as easy to use as possible.You can help us by sharing your comments and suggestions about how our documentation could be made more useful to you and about inaccuracies or information gaps it might contain.PAGENUM=23 ID="BP9"Submit your comments either by filling out the "User Comments" form at the end of this document or by writing to us directly at the following address:TYPE="VERT"Novell, Inc.Technical Publications MS C-23-1122 East 1700 South Provo, UT 84606 USAWe appreciate your comments.PAGENUM=1 ID="BP10"ARENDERAS="SECT1"IDXID="w1668"BOOK="_idx" COLLECTION="nw41" TIDREF="i42"
Abend(Abnormal end) A message issued by the operating system when it detects a serious problem, such as a hardware or software failure. The abend stops the NetWare® server.Abend messages are explained in BOOK="sysmsenu" COLLECTION="nw41"System Messages.RENDERAS="SECT1"ID="FM53605"Access Control List (ACL)IDXID="w1669"BOOK="_idx" COLLECTION="nw41" TIDREF="i49"IDXID="w1670"BOOK="_idx" COLLECTION="nw41" TIDREF="i3575" An object property that stores information about who or what can access that object.An ACL contains trustee assignments that include object and property rights. The ACL also contains the Inherited Rights Filter. When you view an object's trustees or its Inherited Rights Filter, you are seeing the values of that object's ACL.An ACL for an object is like the list of trustees for a file or directory.To change an ACL (and therefore a trustee's rights to an object), you must have a property right that allows you to modify the ACL for that object.See also IDREF="FM13600""Object"; IDREF="FM52521""Security."RENDERAS="SECT1"IDXID="w1671"BOOK="_idx" COLLECTION="nw41" TIDREF="i50"
Access Control rightA file system right that grants the right to change the trustee assignments and Inherited Rights Filter of a directory or file.See also IDREF="FM74455""Rights."PAGENUM=2 ID="BP11"RENDERAS="SECT1"ID="FM43837"AccountingIDXID="w1672"BOOK="_idx" COLLECTION="nw41" TIDREF="i72"The process of tracking resources used on a network.The network supervisor can charge for network services and resources by assigning users account balances that they draw from as they use the services and resources.RENDERAS="SECT2"Charging for Network Services and ResourcesThe network supervisor can assign different charge rates for services at different times of the day, in half-hour increments.The network supervisor can set up charges forMARK=BULLETBlocks read. The charge amount is for each block of data read from the server.Blocks written. The charge amount is for each block of data written to the server.Connect time. The charge amount is for each minute a user is logged in. User logins and logouts are tracked automatically.Disk storage. The charge amount is for each block of data stored on the server's disk for one day.Service requests. The charge amount is for each request to the server.To calculate the charge rate for services, the supervisor shouldMARK=BULLETDetermine network costs and the amount to charge over a given period of time.Decide which services to charge for (based on network costs) and determine the amount needed to cover the costs of each service.For example, if server disk storage capacity is a concern, then charge for disk storage. If network use is high, charge for service requests. To encourage users to log out when they aren't working, charge for connect time.PAGENUM=3 ID="BP12"Estimate how much each service is being used by monitoring the server for two or three weeks.For example, if 30% of the server's charges are from service requests, the supervisor would want to recuperate 30% of network costs by charging for service requests.At the end of the monitoring period, use ATOTAL to determine total use of each service. (ATOTAL is located in SYS:SYSTEM and requires supervisor rights.) See "BOOK="utlrfenu" COLLECTION="nw41"ATOTAL" in Utilities Reference.After establishing how much each service is used and the amount needed to cover the cost of each service, the supervisor can calculate a charge rate.The charge rate is the charge per unit of the specified service. This rate converts the amount of service used to a monetary figure. The unit is arbitrary, but consider beginning with one charge unit equaling one cent.Use the following formula to calculate a charge rate:FILEREF="n40co87a.tif"For example, a network supervisor needs to charge $100 per month for blocks read. There are 250,000 blocks read each month. Therefore, the charge rate is $100 (or 10,000 cents) divided by 250,000 blocks, or $.01 (1 cent) per 25 blocks:FILEREF="n40co88a.tif"PAGENUM=4 ID="BP13"RENDERAS="SECT2"Assigning Account BalancesThe network supervisor canMARK=BULLETAssign each user a balance to limit the amount of services a user can useAssign a credit limit (or allow unlimited credit)Assign a default account balance for all usersIncrease a user's account balanceThe user must log out and log in again before changes take effect.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.RENDERAS="SECT1"ID="FM71916"ACL(Access Control List) An object property that stores information about who or what can access that object.See also IDREF="FM53605""Access Control List."RENDERAS="SECT1"IDXID="w1673"BOOK="_idx" COLLECTION="nw41" TIDREF="i83"
Active hubA device that amplifies transmission signals in network topologies.See also IDREF="FM27825""Hub."RENDERAS="SECT1"IDXID="w1674"BOOK="_idx" COLLECTION="nw41" TIDREF="i92"
Add or Delete Self rightIDXID="w1675"BOOK="_idx" COLLECTION="nw41" TIDREF="i983"A property right that grants a trustee the right to add or remove itself as a value of the property.See also IDREF="FM74455""Rights."RENDERAS="SECT1"Add-on boardIDXID="w1676"BOOK="_idx" COLLECTION="nw41" TIDREF="i113"A circuit board that modifies or enhances a personal computer's capabilities. Examples includePAGENUM=5 ID="BP14"MARK=BULLETMemory board. Increases the amount of RAM within a personal computer.Network board. Allows workstations to communicate with each other and with the NetWare server. (Network boards are sometimes referred to as NIC cards.)Network boards are connected together with cabling.RENDERAS="SECT1"AddressA number that identifies a location in memory or disk storage or that identifies the location of a device on the network.See IDREF="FM63963""Controller address"; IDREF="FM24770""IP address"; IDREF="FM97740""Network numbering"; IDREF="FM75975""SCSI."RENDERAS="SECT1"ID="FM81485"Address Resolution ProtocolIDXID="w1677"BOOK="_idx" COLLECTION="nw41" TIDREF="i102"(ARP) A process in Internet Protocol (IP) and AppleTalk* networks that allows a host to find the Media Access Control (MAC) address of a target host on the same physical network when it only knows the target's IP address.With ARP, a network board contains a table that maps IP addresses to the hardware addresses of the objects on the network.To create entries, the ARP broadcasts a request with the target's IP address. The target responds with its physical address. The network board adds the physical address to its ARP table and can then send packets to the target.RENDERAS="SECT1"Addressing (disk channelIDXID="w1678"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"
)The method of assigning numbers to identify hardware resources on disk channels.Each controller must have a unique address on the disk channel. You can find the physical address settings in the documentation shipped with the controller.Depending on where you place the controller in your system, you might need to change the default setting (usually controller 0). Within one channel, the addresses can range from 0 to 7.PAGENUM=6 ID="BP15"For reference purposes, set the controller nearest to the host bus adapter as controller 0.RENDERAS="SECT1"Addressing spaceIDXID="w1679"BOOK="_idx" COLLECTION="nw41" TIDREF="i110"The total amount of RAM available to the operating system in a NetWare 4TM server. This amount can be divided into domains.In the NetWare 4 operating system, the maximum addressing space is 4 gigabytes (GB), although practical hardware limits are much lower.See also IDREF="FM45002""Paging."RENDERAS="SECT1"AFPAn AppleTalk protocol that provides communication and data transmission between file servers and clients in an AppleShare network. See IDREF="FM75635""AppleTalk Filing Protocol."RENDERAS="SECT1"ID="FM83400"AFP Server objectIDXID="w1680"BOOK="_idx" COLLECTION="nw41" TIDREF="i136"A leaf object that represents an AppleTalk Filing Protocol server that is operating as a node on your NetWare network. The AFP server is probably also acting as a NetWare router to, and the AppleTalk server for, several Apple* Macintosh* computers.See also IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Creating Leaf Objects" in Chapter 1 of Supervising the Network.RENDERAS="SECT1"ID="FM28929"Alias objectIDXID="w1681"BOOK="_idx" COLLECTION="nw41" TIDREF="i153"A leaf object that points to the original location of an object in the Directory. Aliases can make NetWare Directory ServicesTM (NDS) easier to use.Any Directory object located in one place in the Directory can also appear to be in another place in the Directory by using aliases.PAGENUM=7 ID="BP16"For example, an administrator could create aliases pointing to all the modems on the network. The aliases could be created in one container. A user would then need to search only one area of the Directory to find all modems on the network.However, when you move or rename a container object in a Directory tree, you have the option of creating an alias in place of the moved or renamed object. If you select this option, NDSTM features automatically create the alias for you and assign it the same name as the original object.Creating an alias in place of a moved or renamed container object allows users who are unaware of the object's new location to see the object in its original Directory location.When you add aliases to a list (for example, adding an alias of a user to a group) the name of the object appears in the list, not the name of the alias that points to the object.To access the alias and the properties of the object it refers to, you need the Read right to the alias name and the Read right to the properties of the object it refers to.See also IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Creating Leaf Objects" and "BOOK="superenu" COLLECTION="nw41"Cautions When Deleting Alias Objects" in Chapter 1 of Supervising the Network.RENDERAS="SECT1"ID="FM40660"AppleShare softwareIDXID="w1682"BOOK="_idx" COLLECTION="nw41" TIDREF="i186"Networking software from Apple Computer, Inc., that enables a Macintosh computer to function as a file server in an AppleTalk network.Also, AppleShare* workstation software that allows a Macintosh computer to access an AppleShare server.RENDERAS="SECT1"ID="FM75635"AppleTalk Filing ProtocolIDXID="w1683"BOOK="_idx" COLLECTION="nw41" TIDREF="i204"(AFP) An AppleTalk protocol that provides communication and data transmission between file servers and clients in an AppleShare network. When AFP.NLM is loaded on a NetWare server running NetWare for Macintosh, AFP allows Macintosh users to share files by interacting directly with the NetWare file system on the same level as NetWare Core ProtocolTM (NCP).PAGENUM=8 ID="BP17"RENDERAS="SECT1"ID="FM62114"IDXID="w1684"BOOK="_idx" COLLECTION="nw41" TIDREF="i222"
AppleTalk Phase 2The latest version of the AppleTalk protocols. AppleTalk Phase 2 implements more efficient routing techniques that improve performance in multiprotocol environments.Apple introduced AppleTalk Phase 2 in 1989 to provide support for AppleTalk networks with thousands of nodes, for multiple AppleTalk zones on a network, and for token ring networks.RENDERAS="SECT1"ID="FM88684"AppleTalk Print Services moduleIDXID="w1685"BOOK="_idx" COLLECTION="nw41" TIDREF="i227"IDXID="w1686"BOOK="_idx" COLLECTION="nw41" TIDREF="i3538"IDXID="w1687"BOOK="_idx" COLLECTION="nw41" TIDREF="i2258"A NetWare Loadable ModuleTM (NLM) program that enables Macintosh users to print to NetWare queues and enables non-Macintosh users to print to AppleTalk printers.AppleTalk Print Services module (ATPS.NLM) spools print jobs sent from Macintosh workstations to the NetWare queue. Print jobs can then be sent to the printer through PSERVER.NLM (for an AppleTalk or non-AppleTalk printer), or through ATXRP.NLM or ATPS.NLM (for an AppleTalk printer).For a non-Macintosh user printing to an AppleTalk printer, ATPS.NLM transfers the print job from the NetWare queue to the printer.RENDERAS="SECT1"ID="FM41940"AppleTalk protocolsIDXID="w1688"BOOK="_idx" COLLECTION="nw41" TIDREF="i233"IDXID="w1689"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"The underlying forms and rules that determine communication between nodes on an AppleTalk network.These protocols control the AppleTalk network, from the network board to the application software.One protocol defines electrical characteristics that send out a data bit. Another protocol defines how many characters are in a data packet and what address information follows the packet on the network.RENDERAS="SECT2"Link Access Protocol (LAP)IDXID="w1690"BOOK="_idx" COLLECTION="nw41" TIDREF="i2107"LAP works at the Data Link Layer (the bottom layer of the network), receiving packets of information and converting them into the proper signals for your network board.PAGENUM=9 ID="BP18"Three LAPs areMARK=BULLETLLAP (LocalTalk* LAP). Allows the LocalTalk hardware built into Macintosh computers to communicate on LocalTalk networks.ELAP (Ethernet LAP). Allows a Macintosh computer with an installed Ethernet board to communicate with devices on AppleTalk networks.TLAP (Token Ring LAP). Allows devices using IBM* token ring technology to communicate with devices on AppleTalk networks.ELAP and TLAP use AppleTalk Address Resolution Protocol (AARP) to translate AppleTalk node addresses into addresses that can be used on Ethernet or token ring devices.RENDERAS="SECT2"IDXID="w1691"BOOK="_idx" COLLECTION="nw41" TIDREF="i932"
Datagram Delivery Protocol (DDP)DDP works at the Network Layer and prepares packets of data to send on network cables.These packets, called datagrams, include network address information and data formatting. They are delivered to one of the Link Access Protocols (LLAP, ELAP, or TLAP), according to the hardware in the computer.DDP provides only a best-effort delivery system, with no guarantee that data has arrived at another node. A more reliable method of delivery is to use AppleTalk Transaction Protocol (ATP) with DDP.AppleTalk Session Protocol (ASP) extends ATP, allowing two processes (like a user and a server) to exchange transactions and commands reliably.AppleTalk Data Stream Protocol (ADSP) allows the two processes to open a virtual "data pipe" to read and write information for the other. The strict organization and commands of transaction protocols aren't used.AppleTalk provides stream protocols for those more familiar with them, but makes more frequent use of the transactional protocols ATP and ASP.PAGENUM=10 ID="BP19"RENDERAS="SECT2"IDXID="w1692"BOOK="_idx" COLLECTION="nw41" TIDREF="i3913"
Routing Table Maintenance Protocol (RTMP)RTMP is the routing protocol used by AppleTalk. It is very similar to RIP. When many small networks are connected, a router connects them together in an internetwork. The router maintains the addresses of all networks connected to the internetwork.Information about other networks is stored in routing tables. Routers update routing tables by using the RTMP to communicate with each other.RENDERAS="SECT2"IDXID="w1693"BOOK="_idx" COLLECTION="nw41" TIDREF="i250"
AppleTalk Update-Based Routing Protocol (AURP)AURP operates like RTMP, but sends updates only when a change occurs on the network.The principal features of AURP areMARK=BULLETAppleTalk tunneling in TCP/IP. Enables two AppleTalk networks to be connected through a TCP/IP network.Update-based routing through tunnels. Reduces the amount of bandwidth by sending updates to peer routers only when network routing information changes, rather than sending periodic broadcasts of the routing table.RENDERAS="SECT2"IDXID="w1694"BOOK="_idx" COLLECTION="nw41" TIDREF="i2574"
Name Binding Protocol (NBP)Each network process or device has a name that corresponds to network and node addresses. AppleTalk uses an NBP to conceal those addresses from users.The NBP converts the name of a network object provided by a user (like a printer) into a network address that the Link Access Protocol can locate.RENDERAS="SECT2"IDXID="w1695"BOOK="_idx" COLLECTION="nw41" TIDREF="i3498"
Printer Access Protocol (PAP)When a network node prints to a network printer, the PAP uses NBP to prepare a path to the requested printer.PAGENUM=11 ID="BP20"RENDERAS="SECT2"IDXID="w1696"BOOK="_idx" COLLECTION="nw41" TIDREF="i4874"
Zone Information Protocol (ZIP)In a large internetwork, all AppleTalk nodes are divided into groups, called zones, for ease of locating an object.The NBP uses ZIP to assist in finding the correct network and node addresses from a Zone List.See also IDREF="FM75635""AppleTalk Filing Protocol"; IDREF="FM62114""AppleTalk Phase 2"; IDREF="FM40660""AppleShare software"; IDREF="FM76792""Zones."RENDERAS="SECT1"ApplicationIDXID="w1697"BOOK="_idx" COLLECTION="nw41" TIDREF="i266"A software program that makes calls to the operating system and manipulates data files, allowing a user to perform a specific job (such as accounting or word processing).MARK=BULLETStandalone application. An application that runs from the hard disk or floppy disk in a self-contained, independent computer. Only one user can access the application.Network application. An application that runs on networked computers and can be shared by users.Network applications use network resources such as printers. Advanced network applications (such as electronic mail) allow communication among network users.RENDERAS="SECT1"ArchiveIDXID="w1698"BOOK="_idx" COLLECTION="nw41" TIDREF="i279"A transfer of files to long-term storage media, such as optical discs or magnetic tape.See also IDREF="FM85330""Attributes"; IDREF="FM24312""Backup"; IDREF="FM55003""Data migration"; IDREF="FM40870""High Capacity Storage System"; IDREF="FM66936""Storage Management Services."RENDERAS="SECT1"Archive Needed (A) attributeIDXID="w1699"BOOK="_idx" COLLECTION="nw41" TIDREF="i276"A file attribute, set by the NetWare operating system, indicating that the file has been changed since the last time it was backed up.See also IDREF="FM85330""Attributes."PAGENUM=12 ID="BP21"RENDERAS="SECT1"ID="FM82152"ARP(Address Resolution Protocol) A process in IP and AppleTalk networks that allows a host to find the MACTM address of a target host on the same physical network when it only knows the target's IP address.See IDREF="FM81485""Address Resolution Protocol."RENDERAS="SECT1"ATPS(AppleTalk Print Services) Enables a Macintosh client to print to a NetWare queue and a non-Macintosh client to print to an AppleTalk printer.See IDREF="FM88684""AppleTalk Print Services module."RENDERAS="SECT1"AttachIDXID="w1700"BOOK="_idx" COLLECTION="nw41" TIDREF="i331"Establishes a connection between a workstation and a NetWare server. In networks running NetWare 3TM or earlier versions, users connected to multiple file servers using the ATTACH command. In NetWare 4, with NetWare Directory Services, users no longer need to attach separately to multiple servers. When users log in to the Directory tree, they automatically have access to any resources in the Directory tree to which they have rights. Rights to resources are verified through authentication.In NetWare 4, the ATTACH command can still be used in login scripts to establish connections with bindery-based servers.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"LOGIN," "BOOK="utlrfenu" COLLECTION="nw41"LOGOUT," and "BOOK="utlrfenu" COLLECTION="nw41"MAP" in Utilities Reference.See also, IDREF="FM59413""Authentication"; IDREF="FM83674""NetWare Directory Services."RENDERAS="SECT1"ID="FM85330"AttributesIDXID="w1701"BOOK="_idx" COLLECTION="nw41" TIDREF="i336"The characteristics of a IDXID="w1702"BOOK="_idx" COLLECTION="nw41" TIDREF="i1044"
directory or IDXID="w1703"BOOK="_idx" COLLECTION="nw41" TIDREF="i1452"
file. In NetWare, these characteristics are called flags.NDS objects do not have attributes.PAGENUM=13 ID="BP22"Attributes dictate what can be done with a file or directory. For example, you can set a file to be a Read Only (Ro) file.While the term "attributes" is used predominately for DOS and OS/2* files, NetWare offers additional attributes, and then applies them to both files and directories.LABEL="1" PGWIDE=1 TOCENTRY="1" Directory AttributesCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="23*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"AttributeCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Delete Inhibit (Di)COLNAME=2 ROTATE="0" MOREROWS="0"Prevents any user from erasing the directory.COLNAME=1 ROTATE="0" MOREROWS="0"Don't Compress (Dc)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the directory so that files in it are never compressed.COLNAME=1 ROTATE="0" MOREROWS="0"Don't Migrate (Dm)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the directory so that files in it are never migrated to a secondary storage device (such as a tape drive or optical disc).COLNAME=1 ROTATE="0" MOREROWS="0"Hidden (H)COLNAME=2 ROTATE="0" MOREROWS="0"A DOS and OS/2 attribute. Hides the directory from the DOS or OS/ 2 DIR command and prevents it from being deleted or copied. However, the NetWare NDIR command shows the directory if the user has the File Scan right. (See IDREF="FM74455""Rights.")COLNAME=1 ROTATE="0" MOREROWS="0"Immediate Compress (Ic)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the directory so that all files in it are compressed on disk as soon as the operating system can do so, without waiting for a specific event to initiate compression (such as a time delay).COLNAME=1 ROTATE="0" MOREROWS="0"Normal (N)COLNAME=2 ROTATE="0" MOREROWS="0"No directory attributes are set.COLNAME=1 ROTATE="0" MOREROWS="0"Purge (P)COLNAME=2 ROTATE="0" MOREROWS="0"Tells NetWare to purge the directory and any file in the directory when deleted, even if the purge attribute isn't set on an individual file. The directory and files can't be salvaged with the FILER utility.COLNAME=1 ROTATE="0" MOREROWS="0"Rename Inhibit (Ri)COLNAME=2 ROTATE="0" MOREROWS="0"Prevents any user from renaming the directory.COLNAME=1 ROTATE="0" MOREROWS="0"System (Sy)COLNAME=2 ROTATE="0" MOREROWS="0"A DOS and OS/2 attribute. Marks directories used only by the operating system. The directory is hidden from the DOS or OS/2 DIR command and can't be deleted or copied. However, the NetWare NDIR command shows the directory if the user has the File Scan right. (See IDREF="FM74455""Rights.")LABEL="2" PGWIDE=1 TOCENTRY="1" File AttributesCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="23*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"AttributeCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Archive Needed (A)COLNAME=2 ROTATE="0" MOREROWS="0"A status flag set by NetWare.Indicates that the file has been changed since the last time it was backed up. NetWare sets this attribute when a file is modified. Backup programs usually clear this attribute after backing up the file.COLNAME=1 ROTATE="0" MOREROWS="0"Can't Compress (Cc)COLNAME=2 ROTATE="0" MOREROWS="0"A status flag set by NetWare. Indicates that the file can't be compressed because of insignificant space savings. This attribute is shown on attribute lists, but can't be set by the user.COLNAME=1 ROTATE="0" MOREROWS="0"Compressed (Co)COLNAME=2 ROTATE="0" MOREROWS="0"A status flag set by NetWare. Indicates that the file is compressed. This attribute is shown on attribute lists, but can't be set by the user.COLNAME=1 ROTATE="0" MOREROWS="0"Copy Inhibit (Ci)COLNAME=2 ROTATE="0" MOREROWS="0"Only valid on Macintosh workstations. Prevents users from copying the file.COLNAME=1 ROTATE="0" MOREROWS="0"Delete Inhibit (Di)COLNAME=2 ROTATE="0" MOREROWS="0"Prevents any user from erasing the file.COLNAME=1 ROTATE="0" MOREROWS="0"Don't Compress (Dc)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the file so that it is never compressed.COLNAME=1 ROTATE="0" MOREROWS="0"Don't Migrate (Dm)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the file so that it is never migrated to a secondary storage device (such as a tape drive or optical disc).COLNAME=1 ROTATE="0" MOREROWS="0"Don't Suballocate (Ds)COLNAME=2 ROTATE="0" MOREROWS="0"Prevents an individual file from being suballocated, even if suballocation is enabled for the system.Use for files that are enlarged or appended frequently, such as certain data base files.COLNAME=1 ROTATE="0" MOREROWS="0"Execute Only (X)COLNAME=2 ROTATE="0" MOREROWS="0"Prevents a file from being copied. Only the Supervisor can set this file attribute; it cannot be cleared. It should be set only if you have a second copy of the file.Backup utilities don't back up a file marked Execute Only, and some program files with this attribute set don't execute properly.COLNAME=1 ROTATE="0" MOREROWS="0"Hidden (H)COLNAME=2 ROTATE="0" MOREROWS="0"Hides the file from the DOS or OS/2 DIR command and prevents it from being deleted or copied. However, the NetWare NDIR command shows the file if the user has the File Scan right. (See IDREF="FM74455""Rights.")COLNAME=1 ROTATE="0" MOREROWS="0"Immediate Compress (Ic)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the file so that it is compressed on disk as soon as the operating system can do so, without waiting for a specific event to initiate compression (such as a time delay).COLNAME=1 ROTATE="0" MOREROWS="0"Migrated (M)COLNAME=2 ROTATE="0" MOREROWS="0"A status flag set by NetWare. Indicates that the file is migrated. This attribute is shown on attribute lists, but can't be set by the user.COLNAME=1 ROTATE="0" MOREROWS="0"Normal (N)COLNAME=2 ROTATE="0" MOREROWS="0"No file attributes are set.COLNAME=1 ROTATE="0" MOREROWS="0"Purge (P)COLNAME=2 ROTATE="0" MOREROWS="0"Tells NetWare to purge the file when it is deleted. The file can't be salvaged with the FILER utility.COLNAME=1 ROTATE="0" MOREROWS="0"Read Only (Ro)COLNAME=2 ROTATE="0" MOREROWS="0"Indicates that no one can write to this file. When Read Only is set or cleared, NetWare also sets or clears the Delete Inhibit and Rename Inhibit attributes. Consequently, a user can't write to, erase, or rename a file when Read Only is set.A user with the Modify right can remove the Delete Inhibit and Rename Inhibit attributes without removing Read Only. Then the file can be deleted or renamed, but not written to. (See IDREF="FM74455""Rights.")NetWare shows Read Write (Rw) if Read Only isn't set.COLNAME=1 ROTATE="0" MOREROWS="0"Read Write (Rw)COLNAME=2 ROTATE="0" MOREROWS="0"Allows users to change the content of the file. Assigned by default when Read Only is not set.COLNAME=1 ROTATE="0" MOREROWS="0"Rename Inhibit (R)COLNAME=2 ROTATE="0" MOREROWS="0"Prevents a user from renaming a file.COLNAME=1 ROTATE="0" MOREROWS="0"Shareable (Sh)COLNAME=2 ROTATE="0" MOREROWS="0"Allows the file to be accessed by more than one user at a time. Usually used in combination with the Read Only attribute.COLNAME=1 ROTATE="0" MOREROWS="0"System (Sy)COLNAME=2 ROTATE="0" MOREROWS="0"A DOS and OS/2 attribute. Marks a file used only by an operating system. The file is hidden from the DOS or OS/2 DIR command and can't be deleted, renamed, or copied.However, the NetWare NDIR command shows the file if the user has the File Scan right. (See IDREF="FM74455""Rights.")COLNAME=1 ROTATE="0" MOREROWS="0"Transactional (T)COLNAME=2 ROTATE="0" MOREROWS="0"Indicates that the file is protected by Transaction Tracking System® (TTS). TTSTM prevents data corruption by ensuring that either all changes are made or no changes are made when a file is being modified.Set this attribute for all database files you want protected by TTS. (See IDREF="FM67355""Transaction Tracking System.")PAGENUM=16 ID="BP23"Set or clear attributes with the FLAG command line utility, the FILER menu utility, or the NetWare Administrator graphical utility. Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"FILER," "BOOK="utlrfenu" COLLECTION="nw41"FLAG," "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN," and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.RENDERAS="SECT1"AuditingIDXID="w1704"BOOK="_idx" COLLECTION="nw41" TIDREF="i346"The process of examining network transactions to ensure that network records are accurate and secure.In general, auditing means examining records to make sure that transactions are accurate and that confidential information is secure.NetWare auditing allows individuals, acting independently of network supervisors and other users, to audit network transactions.Auditors can audit NDS events as well as those events specific to a volume or a server. Some events you can audit are shown in the following figure.PAGENUM=17 ID="BP24"LABEL="1" FLOAT="0"Audited EventsFILEREF="n41co90a.tif"Auditors can track events and activities on the network, but they don't have rights to open or modify network files (other than the audit data and audit history files), unless they are granted rights by the network supervisor.Auditing is enabled at the volume level for file system auditing. It is enabled at the container level when auditing NDS events.The Audit program files are installed automatically when you install or upgrade to NetWare 4.1.Audit data and history files are automatically created for volumes and containers that have auditing enabled. The files keep records much like a system or error log file. All activity tracked by the auditing utility is recorded.The audit files continue to accept records until auditing is disabled or the file becomes full.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"AUDITCON" in Utilities Reference.PAGENUM=18 ID="BP25"RENDERAS="SECT1"ID="FM59413"AuthenticationIDXID="w1705"BOOK="_idx" COLLECTION="nw41" TIDREF="i351"A means of verifying that an object sending messages or requests to NDS is authorized to do so.Authentication guarantees that only the purported sender could have sent a message or request, and that it originated from the workstation where the authentication data was created.Authentication works with login restrictions and access control rights to provide a secure network.All a network user sees of authentication is a request for a password during network login. Every subsequent network operation is transparently authenticated using identification information created when the password was entered.NetWare 4 authentication uses a Public Key Encryption system that is virtually unbreakable. It consists of a private key and a public key. The keys are strings of numbers used in complex mathematical functions.The workstation uses a private key to encode messages sent to the NetWare server. The server then uses a public key to decode the messages. The server knows that the workstation sent it because the workstation's private key is required to encode the message.Neither the two keys nor the user's password are ever sent across the network.Authentication is illustrated in the following figure:PAGENUM=19 ID="BP26"LABEL="2" FLOAT="0"IDXID="w1706"BOOK="_idx" COLLECTION="nw41" TIDREF="i351"AuthenticationFILEREF="n40co84a.tif"Because the keys aren't changed during a login session, you might encourage users to log out periodically to update the authentication keys. That way, if someone on the server or workstation got one of the keys, only the current login session would be compromised.You can force periodic logouts by setting login time restrictions.RENDERAS="SECT1"IDXID="w1707"BOOK="_idx" COLLECTION="nw41" TIDREF="i360"
AUTOEXEC.BATA batch file that executes automatically when DOS or OS/2 is booted on a computer.A workstation's AUTOEXEC.BAT file, located on the bootable floppy or hard disk, can contain commands thatMARK=BULLETLoad NetWare client filesLoad other files required by the hardwareSet the DOS or OS/2 promptPAGENUM=20 ID="BP27"Change the default drive to the first network driveLog in the userThe workstation AUTOEXEC.BAT file can also load user-specific programs such as NETBIOS.COM or call other batch files.A NetWare server's AUTOEXEC.BAT file located on the hard disk's DOS or OS/2 partition can contain the command that loads the NetWare operating system (SERVER.EXE).RENDERAS="SECT1"ID="FM78770"AUTOEXEC.NCFIDXID="w1708"BOOK="_idx" COLLECTION="nw41" TIDREF="i363"A NetWare server executable batch file, located on the NetWare partition of the server's hard disk.AUTOEXEC.NCF is used to MARK=BULLETLoad modulesSet the NetWare operating system configurationSet bindery contextsStore the IPXTM internal network numberStore the file server nameMake time zone settingsThe network supervisor can also add executable server commands (such as LOAD INSTALL or LOAD MONITOR) to AUTOEXEC.NCF.If you choose only the IPX protocol during installation, the AUTOEXEC.NCF contains all LOAD and BIND commands for the LAN drivers, network boards, and for the IPX protocol. In addition, if you enable your server for non-routing TCP/IP or AppleTalk, the LOAD and BIND commands are placed in the AUTOEXEC.NCF file.PAGENUM=21 ID="BP28"See also: IDREF="FM11121""NETINFO.CFG"; and IDREF="FM86375""Router". 
Related utility:"BOOK=utlrfenu COLLECTION="nw41"INETCFG" in Utilities Reference. RENDERAS="SECT1"Automatic rollbackIDXID="w1709"BOOK="_idx" COLLECTION="nw41" TIDREF="i372"A feature of TTS that returns a database to its original state.When a network running under TTS fails during a transaction, the database returns, or rolls back, to its most recent complete state, preventing corruption from an incomplete transaction.See also IDREF="FM67355""Transaction Tracking System."RENDERAS="SECT1"ID="FM27700"Autonomous systemA collection of routers and networks under a single administrative control.See also IDREF="FM64249""Exterior Gateway Protocol."PAGENUM=22 ID="BP29"BRENDERAS="SECT1"ID="FM24312"BackupIDXID="w1710"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"A duplicate of data (file, directory, volume), copied to a storage device (floppy diskette, cartridge tape, hard disk). A backup can be retrieved and restored if the original is corrupted or destroyed.The type of backup you perform and the storage media rotation method you use are dictated byMARK=BULLETThe number of backup sessions you are willing to restore in the event of data lossThe number of duplicate copies of data you want and are willing to storeThe maximum age you want the oldest data copy to bePerform backups when the fewest files are likely to be open. (Files in use at the time of the backup aren't backed up.)RENDERAS="SECT2"How Often to Back Up FilesFiles that don't change often, such as applications or archived files, don't need to be backed up as frequently as files that change often.In deciding which files to back up and how often to back them up, imagine a worst case scenario: Determine how long it would take and what it would cost to re-create critical information if an unexpected failure caused data loss at the worst possible time.RENDERAS="SECT2"How File Restoration Decisions Determine Backup MethodsBackup methods have different implications for the process of restoring files. Before you decide which backup method works best, make sure you understand the implications.PAGENUM=23 ID="BP30"RENDERAS="SECT2"Amount of Media RequiredAfter you decide what kind of backups you want to perform, determine how many sets of storage media you need, and how you plan to rotate them.RENDERAS="SECT2"Rotation MethodsRotation distributes both current and older data across several storage media, thereby reducing the risk of all data being lost if one of the media becomes corrupted.RENDERAS="SECT2"IDXID="w1711"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
Example: The Grandfather Rotation MethodTo use the Grandfather rotation method, you need 20 sets of storage media.Label four as daily sets Monday, Tuesday, Wednesday, and Thursday. Label four as weekly sets Friday1, Friday2, Friday3, and Friday4. Label the other twelve as monthly sets January, February, etc.You may want to add another set of weekly tapes, labeled Friday5, for months in which there are five Fridays.The Grandfather method of rotation is illustrated in the following table:COLS=6 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="4*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="4*"COLNAME=4 COLWIDTH="4*"COLNAME=5 COLWIDTH="4*"COLNAME=6 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"DailyCOLNAME=2 ROTATE="0" MOREROWS="0"DailyCOLNAME=3 ROTATE="0" MOREROWS="0"DailyCOLNAME=4 ROTATE="0" MOREROWS="0"DailyCOLNAME=5 ROTATE="0" MOREROWS="0"WeeklyCOLNAME=6 ROTATE="0" MOREROWS="0"MonthlyVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Mon.COLNAME=2 ROTATE="0" MOREROWS="0"Tue.COLNAME=3 ROTATE="0" MOREROWS="0"Wed.COLNAME=4 ROTATE="0" MOREROWS="0"Thu.COLNAME=5 ROTATE="0" MOREROWS="0"Fri. 1COLNAME=6 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Mon.COLNAME=2 ROTATE="0" MOREROWS="0"Tue.COLNAME=3 ROTATE="0" MOREROWS="0"Wed.COLNAME=4 ROTATE="0" MOREROWS="0"Thu.COLNAME=5 ROTATE="0" MOREROWS="0"Fri. 2COLNAME=6 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Mon.COLNAME=2 ROTATE="0" MOREROWS="0"Tue.COLNAME=3 ROTATE="0" MOREROWS="0"Wed.COLNAME=4 ROTATE="0" MOREROWS="0"Thu.COLNAME=5 ROTATE="0" MOREROWS="0"Fri. 3COLNAME=6 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Mon.COLNAME=2 ROTATE="0" MOREROWS="0"Tue.COLNAME=3 ROTATE="0" MOREROWS="0"Wed.COLNAME=4 ROTATE="0" MOREROWS="0"Thu.COLNAME=5 ROTATE="0" MOREROWS="0"Fri. 4COLNAME=6 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"COLNAME=6 ROTATE="0" MOREROWS="0"Jan.COLNAME=1 ROTATE="0" MOREROWS="0"Mon.COLNAME=2 ROTATE="0" MOREROWS="0"Tue.COLNAME=3 ROTATE="0" MOREROWS="0"Wed.COLNAME=4 ROTATE="0" MOREROWS="0"Thu.COLNAME=5 ROTATE="0" MOREROWS="0"Fri. 1COLNAME=6 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Mon.COLNAME=2 ROTATE="0" MOREROWS="0"Tue.COLNAME=3 ROTATE="0" MOREROWS="0"Wed.COLNAME=4 ROTATE="0" MOREROWS="0"Thu.COLNAME=5 ROTATE="0" MOREROWS="0"Fri. 2COLNAME=6 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Mon.COLNAME=2 ROTATE="0" MOREROWS="0"Tue.COLNAME=3 ROTATE="0" MOREROWS="0"Wed.COLNAME=4 ROTATE="0" MOREROWS="0"Thu.COLNAME=5 ROTATE="0" MOREROWS="0"Fri. 3COLNAME=6 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Mon.COLNAME=2 ROTATE="0" MOREROWS="0"Tue.COLNAME=3 ROTATE="0" MOREROWS="0"Wed.COLNAME=4 ROTATE="0" MOREROWS="0"Thu.COLNAME=5 ROTATE="0" MOREROWS="0"Fri. 4COLNAME=6 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"COLNAME=6 ROTATE="0" MOREROWS="0"Feb.PAGENUM=24 ID="BP31"RENDERAS="SECT2"IDXID="w1712"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
Example: The 10-Tape Rotation MethodTo use the 10-tape rotation method, you need ten tape sets, each set labeled with a number from one through ten.In this method, a 40-week period is divided into 10 four-week cycles, and each tape set is used an equal number of times during the 40 weeks.You always have a 12-week-old copy of your data on at least one tape set.For the first four weeks, use the same tape sets for the Monday (set 1), Tuesday (set 2), Wednesday (set 3), and Thursday (set 4) backups.On the first four Fridays, use the next sequence of four tapes (sets 5 through 8).During the second four week cycle, increment the daily tape set numbers by one, for example, Monday (set 2), Tuesday (set 3), Wednesday (set 4), and Thursday (set 5).During the second four weeks, increment the Friday tape set number by one also (sets 6 through 9).The 10-tape rotation method (showing the tape set numbers) is illustrated in the following table.COLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="6*"COLNAME=3 COLWIDTH="6*"COLNAME=4 COLWIDTH="6*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Week 1M, T, W, Th, FCOLNAME=2 ROTATE="0" MOREROWS="0"Week 2M, T, W, Th, FCOLNAME=3 ROTATE="0" MOREROWS="0"Week 3M, T, W, Th, FCOLNAME=4 ROTATE="0" MOREROWS="0"Week 4M, T, W, Th, FVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"1, 2, 3, 4, 5COLNAME=2 ROTATE="0" MOREROWS="0"1, 2, 3, 4, 6COLNAME=3 ROTATE="0" MOREROWS="0"1, 2, 3, 4, 7COLNAME=4 ROTATE="0" MOREROWS="0"1, 2, 3, 4, 8COLNAME=1 ROTATE="0" MOREROWS="0"2, 3, 4, 5, 6COLNAME=2 ROTATE="0" MOREROWS="0"2, 3, 4, 5, 7COLNAME=3 ROTATE="0" MOREROWS="0"2, 3, 4, 5, 8COLNAME=4 ROTATE="0" MOREROWS="0"2, 3, 4, 5, 9COLNAME=1 ROTATE="0" MOREROWS="0"3, 4, 5, 6, 7COLNAME=2 ROTATE="0" MOREROWS="0"3, 4, 5, 6, 8COLNAME=3 ROTATE="0" MOREROWS="0"3, 4, 5, 6, 9COLNAME=4 ROTATE="0" MOREROWS="0"3, 4, 5, 6, 10COLNAME=1 ROTATE="0" MOREROWS="0"4, 5, 6, 7, 8COLNAME=2 ROTATE="0" MOREROWS="0"4, 5, 6, 7, 9COLNAME=3 ROTATE="0" MOREROWS="0"4, 5, 6, 7, 10COLNAME=4 ROTATE="0" MOREROWS="0"4, 5, 6, 7, 1COLNAME=1 ROTATE="0" MOREROWS="0"5, 6, 7, 8, 9COLNAME=2 ROTATE="0" MOREROWS="0"5, 6, 7, 8, 10COLNAME=3 ROTATE="0" MOREROWS="0"5, 6, 7, 8, 1COLNAME=4 ROTATE="0" MOREROWS="0"5, 6, 7, 8, 2COLNAME=1 ROTATE="0" MOREROWS="0"6, 7, 8, 9, 10COLNAME=2 ROTATE="0" MOREROWS="0"6, 7, 8, 9, 1COLNAME=3 ROTATE="0" MOREROWS="0"6, 7, 8, 9, 2COLNAME=4 ROTATE="0" MOREROWS="0"6, 7, 8, 9, 3COLNAME=1 ROTATE="0" MOREROWS="0"7, 8, 9, 10, 1COLNAME=2 ROTATE="0" MOREROWS="0"7, 8, 9, 10, 2COLNAME=3 ROTATE="0" MOREROWS="0"7, 8, 9, 10, 3COLNAME=4 ROTATE="0" MOREROWS="0"7, 8, 9, 10, 4COLNAME=1 ROTATE="0" MOREROWS="0"8, 9, 10, 1, 2COLNAME=2 ROTATE="0" MOREROWS="0"8, 9, 10, 1, 3COLNAME=3 ROTATE="0" MOREROWS="0"8, 9, 10, 1, 4COLNAME=4 ROTATE="0" MOREROWS="0"8, 9, 10, 1, 5COLNAME=1 ROTATE="0" MOREROWS="0"9, 10, 1, 2, 3COLNAME=2 ROTATE="0" MOREROWS="0"9, 10, 1, 2, 4COLNAME=3 ROTATE="0" MOREROWS="0"9, 10, 1, 2, 5COLNAME=4 ROTATE="0" MOREROWS="0"9, 10, 1, 2, 6COLNAME=1 ROTATE="0" MOREROWS="0"10, 1, 2, 3, 4COLNAME=2 ROTATE="0" MOREROWS="0"10, 1, 2, 3, 5COLNAME=3 ROTATE="0" MOREROWS="0"10, 1, 2, 3, 6COLNAME=4 ROTATE="0" MOREROWS="0"10, 1, 2, 3, 7PAGENUM=25 ID="BP32"To make sure that you have a four-week-old copy of data at the end of the first four-week cycle, back up to tape set 10 as well as to tape set 1 on Monday of the first week.RENDERAS="SECT2"Backup LogKeep a written log of all backups performed. The log serves as a record in case the electronic log and error files are destroyed.Record the date, backup type, what was backed up, the media set identification name or number, session log path, data path, and the initials of the person performing the backup.Recording the data path in a log makes it easier to provide this information if you want to restore the session to a different location than it was backed up from.See also IDREF="FM76561""Data set."RENDERAS="SECT1"ID="FM52079"IDXID="w1713"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
Backup hosts and targetsIDXID="w1714"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"A backup host is a NetWare server that has a storage device and a storage device controller attached.A target is the server, workstation, or database from which you back up data or to which you restore data.PAGENUM=26 ID="BP33"Any server, workstation, or service (such as NDS) on the network can be a target, including the backup host. The target server must contain Target Service Agent files.See also IDREF="FM24312""Backup"; IDREF="FM66936""Storage Management Services"; IDREF="FM82095""Target Service Agent."RENDERAS="SECT1"Baud rateIDXID="w1715"BOOK="_idx" COLLECTION="nw41" TIDREF="i424"In serial communication, the signal modulation rate, or the speed at which a signal changes.See also IDREF="FM44412""Serial communication."RENDERAS="SECT1"BinderyIDXID="w1716"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"A network database, in NetWare versions earlier than NetWare 4, that contains definitions for entities such as users, groups, and workgroups.In NetWare 4, the bindery has been replaced by the NetWare Directory database, under NDS.Bindery services provides NetWare 4 networks with backward compatibility to NetWare versions that used the bindery. (See IDREF="FM26082""Bindery services.")The following table compares features of bindery- and Directory-based versions of NetWare.COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="9*"COLNAME=3 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"FeatureCOLNAME=2 ROTATE="0" MOREROWS="0"BinderyCOLNAME=3 ROTATE="0" MOREROWS="0"DirectoryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Logical StructureCOLNAME=2 ROTATE="0" MOREROWS="0"Flat structureCOLNAME=3 ROTATE="0" MOREROWS="0"Hierarchical treeCOLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=3 ROTATE="0" MOREROWS="0"Distributed databaseCOLNAME=1 ROTATE="0" MOREROWS="0"ReplicationCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=3 ROTATE="0" MOREROWS="0"Partitions replicatedCOLNAME=1 ROTATE="0" MOREROWS="0"SynchronizationCOLNAME=2 ROTATE="0" MOREROWS="0"No replicasCOLNAME=3 ROTATE="0" MOREROWS="0"Replicas synchronizedCOLNAME=1 ROTATE="0" MOREROWS="0"UsersCOLNAME=2 ROTATE="0" MOREROWS="0"Separate account on each serverCOLNAME=3 ROTATE="0" MOREROWS="0"Global account for networkCOLNAME=1 ROTATE="0" MOREROWS="0"GroupsCOLNAME=2 ROTATE="0" MOREROWS="0"Server-by-serverCOLNAME=3 ROTATE="0" MOREROWS="0"Network-wideCOLNAME=1 ROTATE="0" MOREROWS="0"LoginCOLNAME=2 ROTATE="0" MOREROWS="0"Password per serverCOLNAME=3 ROTATE="0" MOREROWS="0"Network-wide with authenticationCOLNAME=1 ROTATE="0" MOREROWS="0"PrintingCOLNAME=2 ROTATE="0" MOREROWS="0"No friendly mapCOLNAME=3 ROTATE="0" MOREROWS="0"User-friendly accessCOLNAME=1 ROTATE="0" MOREROWS="0"VolumesCOLNAME=2 ROTATE="0" MOREROWS="0"Server-specificCOLNAME=3 ROTATE="0" MOREROWS="0"Global objectsCOLNAME=1 ROTATE="0" MOREROWS="0"QueuesCOLNAME=2 ROTATE="0" MOREROWS="0"Local objects onlyCOLNAME=3 ROTATE="0" MOREROWS="0"System-wide objectsCOLNAME=1 ROTATE="0" MOREROWS="0"TrusteesCOLNAME=2 ROTATE="0" MOREROWS="0"Server-specificCOLNAME=3 ROTATE="0" MOREROWS="0"Global objectsPAGENUM=27 ID="BP34"RENDERAS="SECT1"Bindery contextIDXID="w1717"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"IDXID="w1718"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"The container object in which bindery services is set.See also IDREF="FM26082""Bindery services."RENDERAS="SECT1"Bindery context pathIDXID="w1719"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"A path statement that allows bindery context to be set in as many as 16 containers. Use the Bindery Context SET parameter to set bindery contexts. Multiple contexts are separated by semicolons. For example:SET BINDERY CONTEXT = OU=Legal.O=Novell; OU=Sales.O=Novell; OU=Mktg.O=NovellFor more information, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.In previous versions of NetWare 4, you could only set the bindery context in one container (Organization or Organizational Unit) within the Directory tree. All bindery objects had to be located in that container.In NetWare 4.1, a bindery context path allowsMARK=BULLETBindery objects on a NetWare 4.1 server to be located in multiple containersNetWare 3 NLM programs that rely on bindery services to access objects in more than one containerPAGENUM=28 ID="BP35"All containers in the bindery context path must be in a read/write replica present on the server. However, using a bindery context path can create a potential problem: Although you cannot have more than one object of the same name in the same container, you can have objects with the same names in the different containers of a bindery context path. But, you can still have only one object with the same name in a bindery. So, only the object in the first container of a path shows up to users, overriding other objects with the same name in other containers.It does not matter whether these objects are of the same type (for example, printer Joe and user Joe). The following illustration shows part of a tree that is included in this bindery context path: OU=Legal.O=Novell; OU=Sales.O=Novell; OU=Mktg.O=NovellFILEREF="n41co71a.tif"If the context is specified as shown above, only user Joe in Legal shows up to a user logging in. On the other hand, only user Joe in Sales shows if the user logging in specifies the context as follows: OU=Sales.O=Novell;OU=Legal.O=Novell;OU=Marketing.O=NovellPAGENUM=29 ID="BP36"Consequently, you should avoid having objects with duplicate names in different containers if these containers are in the same bindery context path.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.See also IDREF="FM26082""Bindery services."RENDERAS="SECT1"ID="FM96444"Bindery objectIDXID="w1720"BOOK="_idx" COLLECTION="nw41" TIDREF="i449"A leaf object that represents an object placed in the Directory tree by an upgrade or migration utility, but that NDS can't identify.This object is for backward compatibility with bindery-oriented utilities.See also IDREF="FM13600""Object."RENDERAS="SECT1"Bindery Queue objectIDXID="w1721"BOOK="_idx" COLLECTION="nw41" TIDREF="i451"A leaf object that represents a queue placed in the Directory tree by an upgrade or migration utility, but that NDS can't identify.This object is for backward compatibility with bindery-oriented utilities.See also IDREF="FM13600""Object."RENDERAS="SECT1"ID="FM26082"Bindery servicesIDXID="w1722"BOOK="_idx" COLLECTION="nw41" TIDREF="i455"A feature of NetWare 4 that allows bindery utilities and clients to co-exist with NDS on the network.Objects in a bindery exist in a flat database instead of a hierarchical database like a Directory tree.Bindery services creates a flat structure for the objects within an Organization object or within an Organizational Unit object.All objects within that container object can then be accessed both by NDS objects and by bindery clients and servers. Bindery services applies only to the leaf objects in that Organizational Unit.The container object where bindery services is set is called the bindery contextPAGENUM=30 ID="BP37". You can change the bindery context by using the SET command. You can also set multiple bindery contexts. You can have up to 16 bindery contexts for each server. (See Chapter 3, "BOOK="getstenu" COLLECTION="nw41"Understanding Bindery Services," in Introduction to NetWare Directory Services.)When you install any NetWare 4 server into the Directory tree, a NetWare Server object is created in the container object. By default, bindery services is activated and the bindery context is set for that container object.A read/write replica of the Directory partition that the bindery context is located in must be stored on each server you want bindery services enabled on. This is done by default when you install a server into a new context.If you don't create a new context when installing NetWare 4 on a server (that is, if you place the server object into an existing context), then the installation program places on the server a read/write replica of the Directory partition containing that context.Although bindery services is enabled during installation of NetWare 4, you can disable it with the SET command.The following figure illustrates bindery services when a bindery context is set for an Organizational Unit object. PAGENUM=31 ID="BP38"LABEL="3" FLOAT="0"Bindery Services in a Directory TreeFILEREF="n41co64a.tif"If you use Partition Manager to change the default Directory partitions, you must also change the Directory replicas stored on the servers in the bindery context.The objects in the container object set as the bindery context must have bindery-compatible names. For example, the complete name for a User object might beMRICHARD.ACCOUNTING.NOVELL USHowever, only the common name of the User object can be seen by bindery clients and servers using bindery services. Therefore, the object's common name must match bindery naming rules.See also IDREF="FM60364""Context"; IDREF="FM69136""Directory tree"; IDREF="FM13600""Object"; Chapter 5, "BOOK="getstenu" COLLECTION="nw41"Planning NetWare Directory Services Implementation," of Introduction to NetWare Directory Services.PAGENUM=32 ID="BP39"RENDERAS="SECT1"ID="FM34556"IDXID="w1723"BOOK="_idx" COLLECTION="nw41" TIDREF="i470"
Binding and unbindingIDXID="w1724"BOOK="_idx" COLLECTION="nw41" TIDREF="i4635"The process of assigning a communication protocol to network boards and LAN drivers and the process of removing it.Each board must have at least one communication protocol bound to the LAN driver for that board. Without a communication protocol, the LAN driver can't process packets.You can bind more than one protocol to the same LAN driver and board. You can also bind the same protocol stack to multiple LAN drivers on the server.You can also cable workstations with different protocols to the same cabling scheme.RENDERAS="SECT2"Binding communication protocols to boards and driversTo bind communication protocols to boards and drivers, use the INETCFG program or the BIND console command. Use BIND for each board in the server.Until a protocol is bound to a board, users attached to the cabling scheme from the board can't log in.When you bind a protocol to a board, you specify the cabling scheme's IPX external network number.This hexadecimal number must be the same for all boards cabled together that use the same frame type. The IPX external number must be different from the number used by boards of other frame types and must be different from the addresses of other cabling systems on the network.The cabling scheme's IPX external network number must also be different from the internal network address for any node on the network. Related utility: "BOOK="utlrfenu" COLLECTION="nw41"BIND" in Utilities Reference.See also IDREF="FM35125""IPX external network number." PAGENUM=33 ID="BP40"RENDERAS="SECT2"Unbinding Communication Protocols from Boards and DriversTo remove a communication protocol from a board and driver, you can use the UNBIND console command or delete the binding in INETCFG. If you have loaded the driver more than once, select the specific board you want to unbind.Use UNBIND to unbind each board. When the protocol is unbound, users attached to the cabling scheme of the board can't log in.If users are already logged in, they receive a message when they attempt to access the server.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"UNBIND" in Utilities Reference.See also IDREF="FM34819""Communication protocols"; IDREF="FM35125""IPX external network number."RENDERAS="SECT1"BIOSIDXID="w1725"BOOK="_idx" COLLECTION="nw41" TIDREF="i471"(Basic Input/Output System) A set of programs, usually in firmware, that enables each computer's central processing unit to communicate with printers, disks, keyboards, consoles, and other attached input and output devices.RENDERAS="SECT1"ID="FM84883"BlockIDXID="w1726"BOOK="_idx" COLLECTION="nw41" TIDREF="i474"The smallest amount of disk space that can be allocated at one time on a NetWare volume.To minimize RAM requirements in NetWare 4.1, the block size depends on the size of the volume, as shown in the following table:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w1727"BOOK="_idx" COLLECTION="nw41" TIDREF="i474"IDXID="w1728"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"
Volume sizeCOLNAME=2 ROTATE="0" MOREROWS="0"Block sizeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0 to 32 MBCOLNAME=2 ROTATE="0" MOREROWS="0"4 KBCOLNAME=1 ROTATE="0" MOREROWS="0"32 to 150 MBCOLNAME=2 ROTATE="0" MOREROWS="0"8 KBCOLNAME=1 ROTATE="0" MOREROWS="0"150 to 500 MBCOLNAME=2 ROTATE="0" MOREROWS="0"16 KBCOLNAME=1 ROTATE="0" MOREROWS="0"500 to 2,000 MBCOLNAME=2 ROTATE="0" MOREROWS="0"32 KBCOLNAME=1 ROTATE="0" MOREROWS="0"2,000+ MBCOLNAME=2 ROTATE="0" MOREROWS="0"64 KBPAGENUM=34 ID="BP41"The block size is set automatically during installation; we recommend that you don't change the default block size.Block suballocation can subdivide a disk block among several files to make better use of disk space when a large block size is used.See also IDREF="FM89382""Block suballocation."RENDERAS="SECT1"ID="FM89382"Block suballocationIDXID="w1729"BOOK="_idx" COLLECTION="nw41" TIDREF="i476"Allows parts of several files to share one disk block, better utilizing disk space.Block suballocation divides any partially used disk block into 512-byte suballocation blocks. These suballocation blocks are used to share the remainder on the block with leftover fragments of other files.Example: Your default block size is 64 KB, and you create a 65KB file.MARK=BULLETWithout block suballocation, the 65KB file requires two disk blocks, or 128 KB.With block suballocation, you use one disk block (64 KB) plus two 512-byte suballocation blocks. The remaining 63 KB of the second block can still be used by other files.Block suballocation is set by default when NetWare 4 is installed.See also IDREF="FM84883""Block"; IDREF="FM96914""Volume."RENDERAS="SECT1"ID="FM50252"Boot filesIDXID="w1730"BOOK="_idx" COLLECTION="nw41" TIDREF="i489"Files, like AUTOEXEC.BAT and CONFIG.SYS, thatMARK=BULLETStart the operating system and its driversSet environment variablesLoad NetWareNetWare server boot files includePAGENUM=35 ID="BP42"MARK=BULLETAUTOEXEC.NCF loads modules and sets the NetWare operating system configuration. (See IDREF="FM78770""AUTOEXEC.NCF.")STARTUP.NCF loads the servers' disk driver and some SET parameters.Workstation boot files depend on the client type (DOS, MS Windows, OS/2, Macintosh, UNIX®). See your client manual.RENDERAS="SECT1"BOOTCONF.SYSIDXID="w1731"BOOK="_idx" COLLECTION="nw41" TIDREF="i497"A file used by a workstation using Remote Reset to determine which remote boot image file to use.See IDREF="FM88007""Remote printer mode." RENDERAS="SECT1"ID="FM19375"BOOTPIDXID="w1732"BOOK="_idx" COLLECTION="nw41" TIDREF="i505"A protocol used by some hosts to obtain their IP address. The host broadcasts a BOOTP request on the local network. If the server is attached to the same network as the host, it receives the request and replies with a packet that contains the host's address.If the server is on a different network, a BOOTP forwarder must direct the broadcast to a BOOTP server and forward the reply to the host. The TCP/IP software provides BOOTPFWD.NLM, which enables your machine to forward BOOTP request and reply packets between the BOOTP server and BOOTP clients. BOOTP forwarding with NetWare can be configured for use with up to four different BOOTP servers.RENDERAS="SECT1"BridgeIDXID="w1733"BOOK="_idx" COLLECTION="nw41" TIDREF="i515"IDXID="w1734"BOOK="_idx" COLLECTION="nw41" TIDREF="i3885"A device that retransmits packets from one segment of the network to another segment.A router, on the other hand, is a device that receives instructions for forwarding packets between topologies and determines the most efficient path.See also IDREF="FM86375""Router."PAGENUM=36 ID="BP43"RENDERAS="SECT1"Browse rightIDXID="w1735"BOOK="_idx" COLLECTION="nw41" TIDREF="i533"An object right that grants the right to see an object in the Directory tree.See also IDREF="FM74455""Rights."RENDERAS="SECT1"ID="FM14193"BrowsingIDXID="w1736"BOOK="_idx" COLLECTION="nw41" TIDREF="i536"A way of finding objects in the Directory.Objects in the Directory are in hierarchical order. Since the Directory can be very large, you can browse the tree structure to find the object you need.FILEREF="n41co56a.tif"IDXID="w1737"BOOK="_idx" COLLECTION="nw41" TIDREF="i536"Example: To find object PRINTER3 when you aren't sure where it is, look at objects in your current context.If PRINTER3 isn't in your current context, search up or down the Directory tree until you find it, or use the browser's search feature.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.RENDERAS="SECT1"BtrieveIDXID="w1738"BOOK="_idx" COLLECTION="nw41" TIDREF="i542"IDXID="w1739"BOOK="_idx" COLLECTION="nw41" TIDREF="i542"IDXID="w1740"BOOK="_idx" COLLECTION="nw41" TIDREF="i924"A complete key-indexed record management system designed for high-performance data handling.PAGENUM=37 ID="BP44"The Btrieve* program stores information in Btrieve data files. Numerous existing database programs recognize the Btrieve data file format, and you can use Btrieve with any of these database programs.Btrieve supports concurrent access; more than one user or application can access a Btrieve data file at the same time.Btrieve maintains the data file's integrity during concurrent access. That is, Btrieve ensures that the information in the data file isn't corrupted.The Btrieve Record Manager can run on a NetWare server, called server-based Btrieve, or on a workstation, called client-based Btrieve.RENDERAS="SECT2"IDXID="w1741"BOOK="_idx" COLLECTION="nw41" TIDREF="i542"IDXID="w1742"BOOK="_idx" COLLECTION="nw41" TIDREF="i4064"
Server-Based BtrieveThis product is packaged with the NetWare operating system and comes as a series of NLM files for the NetWare server.Server-based Btrieve also includes a collection of other executable files for workstations that need access to Btrieve data files on that server (or on any other NetWare server running server-based Btrieve).Using these NLM files and executable files, you can run both Btrieve applications that reside on the NetWare server and those that reside on a workstation.RENDERAS="SECT2"IDXID="w1743"BOOK="_idx" COLLECTION="nw41" TIDREF="i542"IDXID="w1744"BOOK="_idx" COLLECTION="nw41" TIDREF="i658"
Client-Based BtrieveThis product is available only as part of the Btrieve Developer's Kit (purchased separately from the NetWare operating system). The kit provides developers with a set of tools to create new Btrieve applications.IDXID="w1745"BOOK="_idx" COLLECTION="nw41" TIDREF="i542"
The Btrieve Developer's Kit consists of the client-based Btrieve Record Manager, an application programming interface (API) to give your application access to the information in Btrieve data files and to documentation for the API.Client-based Btrieve can run under several operating systems, including DOS, OS/2, and MS Windows.PAGENUM=38 ID="BP45"Client-based Btrieve allows you to run Btrieve applications that reside on your local workstation and to access Btrieve data files that reside on a NetWare server.See BOOK="btrv_enu" COLLECTION="nw41"Btrieve Installation and Operation.RENDERAS="SECT1"BufferAn area in server or workstation memory set aside to temporarily hold data, such as packets received from the network.See IDREF="FM67808""Cache buffer"; IDREF="FM51228""Packet receive buffer."PAGENUM=39 ID="BP46"CRENDERAS="SECT1"Cabling systemIDXID="w1746"BOOK="_idx" COLLECTION="nw41" TIDREF="i565"Part of a network's physical layout.See IDREF="FM64932""Topology."RENDERAS="SECT1"ID="FM67808"Cache bufferIDXID="w1747"BOOK="_idx" COLLECTION="nw41" TIDREF="i568"A block of NetWare server memory (RAM) in which files are temporarily stored. Cache buffers greatly increase NetWare server performance.The cache buffer size depends on the default block size, which depends on the size of the volume. (See IDREF="FM84883"See also "Block.")Cache buffers allow workstations to access data more quickly because reading from and writing to memory is much faster than reading from or writing to disk.See also IDREF="FM97832""Cache buffer pool."RENDERAS="SECT1"ID="FM97832"Cache buffer poolIDXID="w1748"BOOK="_idx" COLLECTION="nw41" TIDREF="i568"The amount of memory available for use by the operating system after the SERVER.EXE file has been loaded into memory.The operating system uses cache buffers in a variety of ways:MARK=BULLETTo cache a volume's File Allocation Table (FAT) and suballocation tables in memoryTo cache parts of a volume's Directory Entry Table (DET)To cache parts of files for users to accessTo build a hash table for directory namesPAGENUM=40 ID="BP47"To build Turbo FAT indexes for open files that are randomly accessed and have 64 or more regular FAT entriesTo use with NLM programs such as LAN drivers, disk drivers, INSTALL (used to create and modify NetWare partitions and volumes), VREPAIR (used to repair NetWare server tables), database servers, communications servers, and print serversWhen an NLM is removed from server memory, the NLM returns the borrowed memory to the cache buffer pool.RENDERAS="SECT1"ID="FM22916"Cache memoryIDXID="w1749"BOOK="_idx" COLLECTION="nw41" TIDREF="i575"Available RAM that NetWare uses to improve NetWare server access time.Cache memory allocates memory for the hash table, the FAT, the Turbo FAT, suballocation tables, the directory cache, a temporary data storage area for files and NLM files, and available memory for other functions.FILEREF="n41co03a.tif"IDXID="w1750"BOOK="_idx" COLLECTION="nw41" TIDREF="i575"
PAGENUM=41 ID="BP48"If the cache memory uses the default block size and a file takes more than one block, the file is placed in a second noncontiguous block both in cache memory and on the volume (on the hard disks). (See IDREF="FM84883""Block.")RENDERAS="SECT2"Directory CachingA method of decreasing the time it takes to determine a file's location on a disk.The FAT and DET are written into the server's memory. The area holding directory entries is called the directory cache.The server can find a file's address from the directory cache much faster than retrieving the information from disk.LABEL="4" FLOAT="0"Directory CachingFILEREF="n40co04a.tif"RENDERAS="SECT2"IDXID="w1751"BOOK="_idx" COLLECTION="nw41" TIDREF="i1454"
File CachingA server can service requests from workstations up to 100 times faster when it reads from and writes to the server's cache memory, rather than reading from or writing to the server's hard disks.PAGENUM=42 ID="BP49"The following figure illustrates how a workstation makes a read request from the server and how the server executes a hash algorithm to calculate the file's address from a hash table.LABEL="5" FLOAT="0"File CachingFILEREF="n40co09a.tif"Hashing is a quick way of predicting the file's address in the directory table.For example, the address on the hash table contains pointers to the first and second probable locations of the DB.DAT file's directory entry in the directory cache.If the first search isn't successful, the server uses the second pointer to find the directory entry, as illustrated in the following figure:PAGENUM=43 ID="BP50"LABEL="6" FLOAT="0"Locating the Directory EntryFILEREF="n40co05a.tif"When the directory entry is located, the server first checks its cache memory to see if it has a copy of DB.DAT.LABEL="7" FLOAT="0"Locating the File in the Cache MemoryFILEREF="n40co06a.tif"If the file is there, the server sends the file to the station from memory. If the file isn't there, the server retrieves the file from disk and sends it to the station.RENDERAS="SECT2"IDXID="w1752"BOOK="_idx" COLLECTION="nw41" TIDREF="i4856"IDXID="w1753"BOOK="_idx" COLLECTION="nw41" TIDREF="i1454"
Writing Files to CacheWhen a workstation writes a file to the server, the server performs the hash algorithm to find the file's cache buffer.PAGENUM=44 ID="BP51"It writes the file to the designated location (writing over the old file, if the file was already in cache) and updates the directory table in the directory cache.Since the file has changed, its cache buffer is different from the file on disk. The buffer is then referred to as a dirty cache buffer.Since writes to disk take longer to perform than writes to cache, the server keeps the dirty buffer designation on the file in cache until the disk has received the file.Writing a file to cache is illustrated in the following figure:LABEL="8" FLOAT="0"Writing a File to CacheFILEREF="n40co07a.tif"PAGENUM=45 ID="BP52"The server then sends a message to the station that the server has received the file, and the station is free to complete other processes.Once the file is written to disk, the server checks the data in memory against the data on disk. If there is a match, the buffer is no longer dirty, as illustrated in the following figure:LABEL="9" FLOAT="0"Cache Memory Write and VerifyFILEREF="n40co08a.tif"As the cache memory fills up, buffers containing the least-used files and directories are eliminated.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" and "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.See also IDREF="FM91856""Directory hashing."PAGENUM=46 ID="BP53"RENDERAS="SECT1"Can't Compress (Cc) attributeIDXID="w1754"BOOK="_idx" COLLECTION="nw41" TIDREF="i583"A status flag indicating that a file can't be compressed because of insignificant space savings.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"CDM(Custom Device Module) The driver component in the NetWare Peripheral ArchitectureTM (NPA) used to drive specific storage devices attached to the host adapter.See IDREF="FM87820""NetWare Peripheral Architecture."RENDERAS="SECT1"ChannelIDXID="w1755"BOOK="_idx" COLLECTION="nw41" TIDREF="i614"The path that data flows on to get from the computer to the device. This path can include a host bus adapter, cables, and storage devices.RENDERAS="SECT1"Character lengthIDXID="w1756"BOOK="_idx" COLLECTION="nw41" TIDREF="i615"In serial communication, the number of bits used to form a character.See IDREF="FM44412""Serial communication."RENDERAS="SECT1"ID="FM82431"Child VLMIDXID="w1757"BOOK="_idx" COLLECTION="nw41" TIDREF="i628"IDXID="w1758"BOOK="_idx" COLLECTION="nw41" TIDREF="i4770"IDXID="w1759"BOOK="_idx" COLLECTION="nw41" TIDREF="i4770"
A Virtual Loadable ModuleTM (VLM) that handles a particular implementation of a logical grouping of functionality. For example, each of the NetWare server types has its own child VLMTM:MARK=BULLETBIND.VLM for NetWare 2 and 3 bindery serversNDS.VLM for NetWare 4 NDS serversPNW.VLM for Personal NetWareTM (NetWare desktop) serversAlso, various implementations of transport protocols each have an individual child VLM. For example, IPXNCP.VLM handles IPX protocol services. Other transport protocols may be defined in the future.PAGENUM=47 ID="BP54"RENDERAS="SECT1"ID="FM99174"ClientIDXID="w1760"BOOK="_idx" COLLECTION="nw41" TIDREF="i657"A workstation that uses NetWare software to gain access to the network.In NetWare, client types include DOS, Macintosh, OS/2, UNIX, and MS Windows.With the respective client software, users can perform networking tasks. These tasks include mapping drives, capturing printer ports, sending messages, accessing files, and changing contexts.See also IDREF="FM97421""DOS client"; IDREF="FM74418""Macintosh client"; IDREF="FM68243""OS/2 client"; IDREF="FM70532""Workstation."RENDERAS="SECT1"CMOS RAMIDXID="w1761"BOOK="_idx" COLLECTION="nw41" TIDREF="i665"Memory used to store system configuration data (such as number of drives, types of drives, and amount of memory).CMOS RAM is battery powered to retain the date, time, and other information that needs to be maintained when the computer is turned off.RENDERAS="SECT1"ID="FM75667"Code pageIDXID="w1762"BOOK="_idx" COLLECTION="nw41" TIDREF="i667"IDXID="w1763"BOOK="_idx" COLLECTION="nw41" TIDREF="i2046"A table storing a character set supporting one or more language scripts. Many personal computers use operating systems that support multiple code pages and allow you to switch between them. When you press a key on a keyboard (a letter, symbol, or number), the computer receives a numeric code that represents that keystroke. Code pages store these numeric codes.In a single-byte code page, up to 256 codes are available to represent lower and upper case letters, numbers, punctuation marks, and all the mathematical symbols on your keyboard. IDXID="w1764"BOOK="_idx" COLLECTION="nw41" TIDREF="i2046"
However, 256 codes are not sufficient to represent all the letters and characters used in every language. Some Roman character-based languages, for instance, have a larger alphabet than others and include many accented characters. PAGENUM=48 ID="BP55"For example, a common code page (known as 437) can be used for several Roman character-based languages, including English, French, and German. Portuguese, however, requires a different character set. Code page 860 (Portuguese) removes the symbol for f (franc) and inserts an Ó (O acute).Other languages such as Chinese, Japanese, and Korean use different characters altogether. The character sets for these languages contain thousands of characters and require a double-byte code page. The differences between any two single-byte code pages may cause display and readability problems. Differences between single-byte and double-byte code pages usually cause display and readability problems. Two steps have been taken to help resolve these problems:MARK=BULLETA common code page (850) has been established that handles most character sets of the Roman script.This set doesn't include some line drawing characters, and other characters appear in a new location within the table.IDXID="w1765"BOOK="_idx" COLLECTION="nw41" TIDREF="i4644"
A new convention, called Unicode*, that supports 64,000 characters has been established.Unicode provides enough codes to support Roman, Chinese, and other character bases.Nonetheless, whether you use a common code page or Unicode, any unrecognizable character is substituted in your display. Unrecognizable characters in DOS are displayed as a heart, and in MS Windows as a box.Substituted characters can prevent NDS from recognizing an object. For example, you create an Organizational Unit object to represent Finance in western Europe and use code page 852 to make the generic currency symbol a part of its name (OU=¤W-Euro). When this object is accessed using code page 437, the unsupported currency symbol (¤) is replaced and a new name is sent to NDS. NDS, however, doesn't recognize the new name, and the object can't be opened or accessed---a potentially serious problem. PAGENUM=49 ID="BP56"The only solution is to determine which code page was used to create the object, then view the object using that code page. Determining which code page was used can be time consuming.See also IDREF="FM17174""Unicode."RENDERAS="SECT1"COM portsIDXID="w1766"BOOK="_idx" COLLECTION="nw41" TIDREF="i678"Asynchronous serial ports on IBM PC-compatible computers.See IDREF="FM18990""Serial port."RENDERAS="SECT1"Command formatIDXID="w1767"BOOK="_idx" COLLECTION="nw41" TIDREF="i685"Instructions that show how to type a command at the keyboard, also called syntax.In NetWare manuals, a command format may include constants, variables, and symbols.RENDERAS="SECT1"CommunicationIDXID="w1768"BOOK="_idx" COLLECTION="nw41" TIDREF="i697"The process of transferring data from one device to another in a computer system.See also IDREF="FM29539""Network communication"; IDREF="FM44412""Serial communication."RENDERAS="SECT1"Communication bufferIDXID="w1769"BOOK="_idx" COLLECTION="nw41" TIDREF="i697"(Formerly used for a packet receive buffer) An area in the NetWare server's memory set aside to temporarily hold data packets arriving from workstations.See IDREF="FM51228""Packet receive buffer."RENDERAS="SECT1"ID="FM34819"Communication protocolsIDXID="w1770"BOOK="_idx" COLLECTION="nw41" TIDREF="i697"IDXID="w1771"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"Conventions or rules used by a program or operating system to communicate between two or more endpoints.Although many communication protocols are used, they all allow information to be packaged, sent from a source, and delivered to a destination system.PAGENUM=50 ID="BP57"RENDERAS="SECT2"IDXID="w1772"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"IDXID="w1773"BOOK="_idx" COLLECTION="nw41" TIDREF="i4837"
Workstation ProtocolsNetWare workstations may use protocols such as IPXTM, SPXTM, TCP/IP, NetBIOS, OSI, and AppleTalk (for Macintosh).See also IDREF="FM61173""File Transfer Protocol"; IDREF="FM16854""IPX"; IDREF="FM43851""SPX."RENDERAS="SECT2"IDXID="w1774"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"IDXID="w1775"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
Server ProtocolsNetWare 4 has six layers of communication between an application and the hardware in the computer. These layers are based on the OSI model. The six communication layers areMARK=BULLETApplication LayerService Protocol LayerCommunication Protocol LayerLink Support LayerDriver LayerHardware LayerIn the server, communication protocols allow the Service Protocol Layer to communicate with the Link Support LayerTM (LSL). IPX, part of the operating system, is the default communication protocol.You can use more than one protocol on the same cabling scheme because the LSLTM, part of the Open Data-Link InterfaceTM (ODI), allows the LAN driver for a network board to service more than one protocol.Use the following console commands to view, add, and configure communication protocols:MARK=BULLETPROTOCOL. Displays the protocols registered with your server and can register others. (See "BOOK="utlrfenu" COLLECTION="nw41"PROTOCOL" in Utilities Reference.)PAGENUM=51 ID="BP58"BIND. Binds a protocol to a network board installed in the server. (See "BOOK="utlrfenu" COLLECTION="nw41"BIND" in Utilities Reference.)UNBIND. Removes protocols from network boards installed in the server. (See "BOOK="utlrfenu" COLLECTION="nw41"UNBIND" in Utilities Reference.)The INETCFG utility can also be used to view, add, and configure communication protocols.See also IDREF="FM34556""Binding and unbinding"; IDREF="FM33588""Open Data-Link Interface."RENDERAS="SECT1"Compare rightIDXID="w1776"BOOK="_idx" COLLECTION="nw41" TIDREF="i714"A property right that grants the right to compare any other value to a value of that property.See IDREF="FM74455""Rights."RENDERAS="SECT1"Compressed (Co) attributeIDXID="w1777"BOOK="_idx" COLLECTION="nw41" TIDREF="i722"A status flag indicating that a file is compressed.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"ID="FM72100"Computer objectIDXID="w1778"BOOK="_idx" COLLECTION="nw41" TIDREF="i732"A leaf object that represents a computer on the network.In the Computer object's properties, you can store information such as the computer's serial number or the person the computer is assigned to.See also IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Creating Leaf Objects" in Chapter 1 of Supervising the Network.RENDERAS="SECT1"Configuration (hardware)IDXID="w1779"BOOK="_idx" COLLECTION="nw41" TIDREF="i1638"IDXID="w1780"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"The equipment used on a network (such as servers, workstations, printers, cables, network boards, and routers) and the way the equipment is connected---the network's physical layout.Hardware configuration includesPAGENUM=52 ID="BP59"MARK=BULLETThe specific hardware installed in or attached to the computer (such as disk subsystems, network boards, memory boards, and printer boards)The set of parameters selected for a boardFor many boards, these settings are made with jumper and switch settings; for other boards, settings are made using configuration software.RENDERAS="SECT1"Configuration (server)IDXID="w1781"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"IDXID="w1782"BOOK="_idx" COLLECTION="nw41" TIDREF="i4045"The settings and parameters chosen through INSTALL.NLM while either installing a new NetWare 4 server, or performing maintenance work on an existing NetWare 4 server.Server configuration includesMARK=BULLETLoading and binding disk, CD-ROM, and LAN driversAssigning an IPX external network numberPartitioning the server hard disk as NetWare partitionsCreating NetWare volumesMounting volumesAssigning an IPX internal network numberModifying volume segments, names, and block sizeEnabling or disabling file compression, block suballocation, data migrationBinding the IPX protocolInstalling NetWare Directory ServicesOptional configuration parameters includeMARK=BULLETMirroring or duplexing NetWare disk partitionsIncreasing the number of licensed connectionsPAGENUM=53 ID="BP60"Binding additional protocols such as TCP/IP and AppleTalkDisabling NetWare Directory ServicesInstalling additional NetWare productsCreating client diskettesAdding or changing a server languageInstalling online documentationModifying the STARTUP.NCF and AUTOEXEC.NCF filesRENDERAS="SECT1"Configuration (router)IDXID="w1783"BOOK="_idx" COLLECTION="nw41" TIDREF="i3885"IDXID="w1784"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"The settings and parameters chosen through internetwork utilities to configure a NetWare 4 server as a router.Use INETCFG to MARK=BULLETConfigure AppleTalk and TCP/IP packet routing across network segmentsConfigure IPX/SPX parameters such as network number and frame typeLoad and bind protocols to the server's network boardsEnable the NLSP protocol Display the most recent console messagesUse FILTCFG to configure RIP/SAP packet filtering.See also BOOK="ipxrtenu" COLLECTION="nw41"NetWare IPX Protocol Reference, BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference, and BOOK="atrefenu" COLLECTION="nw41" NetWare AppleTalk Reference.RENDERAS="SECT1"Configuration (software)IDXID="w1785"BOOK="_idx" COLLECTION="nw41" TIDREF="i4199"IDXID="w1786"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"The software used on a network for servers, clients, protocols, services, drivers, utilities, etc., provides the means to communicate and operate on network hardware.PAGENUM=54 ID="BP61"Software configuration includesMARK=BULLETThe specific software installed or copied to the computer storage mediaConfiguration utilities and preference optionsThe default setting established in each software moduleThe set of .NCF, .CFG, .INI, and system configuration files used as reference files for non-default settingsRENDERAS="SECT1"Connection numberIDXID="w1787"BOOK="_idx" COLLECTION="nw41" TIDREF="i780"A number assigned to any workstation that attaches to a NetWare server; it may be a different number each time a station attaches.Connection numbers are also assigned to processes, print servers, and applications that use server connections.The server's operating system uses connection numbers to control each station's communication with other stations.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"NLIST" in Utilities Reference.RENDERAS="SECT1"ConnectivityIDXID="w1788"BOOK="_idx" COLLECTION="nw41" TIDREF="i798"The ability to link computer systems (Macintoshes, PCs, minicomputers, and mainframes) into a network in order to share resources such as applications and printers.See also IDREF="FM24537""Internetwork."RENDERAS="SECT1"ConsoleIDXID="w1789"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"The monitor and keyboard where you view and control NetWare server activity.See IDREF="FM65589""Server console."RENDERAS="SECT1"Console operatorIDXID="w1790"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"A user or member of a group who has been delegated rights to manage the NetWare server.PAGENUM=55 ID="BP62"RENDERAS="SECT1"ID="FM56194"Container login scriptIDXID="w1791"BOOK="_idx" COLLECTION="nw41" TIDREF="i805"IDXID="w1792"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"Sets a general environment for all users in a container (such as an Organizational Unit). These login scripts execute first.Maintaining many user login scripts can be time consuming. You want to include as much customizing information as possible in the container login script.For example, if all users need access to NetWare utilities in the same volume, put the search drive mapping to that volume in a container login script.See also IDREF="FM23712""Login scripts."RENDERAS="SECT1"ID="FM37599"Container objectAn object that can hold, or contain, other objects. For example, an Organizational Unit is a container object because it can contain other objects; it doesn't have to. Container objects are used as a way to logically organize all other objects in the Directory tree.See also IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Creating Container Objects" in Chapter 1 of Supervising the Network; Chapter 5, "BOOK="getstenu" COLLECTION="nw41"Planning NetWare Directory Services Implementation," in Introduction to NetWare Directory Services.RENDERAS="SECT1"ID="FM60364"ContextIDXID="w1793"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"The position of an object within its container in the Directory tree.NDS allows you to refer to objects according to their positions within a tree. When you add an object (such as a server or user) to the network, you place that object in a container object in the Directory tree.For example, in the following figure, the context for the User object ESAYERS is SALES PV.SALES.NOVELL US. The context for the User object RJONES is ACCOUNTING.NOVELL US.PAGENUM=56 ID="BP63"LABEL="10" FLOAT="0"IDXID="w1794"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"Context in a Directory TreeFILEREF="n41co70a.tif"When you move from one container object to another, you change contexts. Whenever you change contexts, indicate the complete name of the object you are changing the context to.If you are referring to an object that is in the same container object as your User object, you need only refer to that object by its common name, instead of by its complete name.For example, in the previous figure, if the User object ESAYERS located in SALES PV.SALES.NOVELL US wants information on User object ESMITH located in the same context, then ESAYERS need only refer to the User object as ESMITH.See also IDREF="FM83674""NetWare Directory Services"; IDREF="FM13600""Object"; IDREF="FM37599""Container object."PAGENUM=57 ID="BP64"RENDERAS="SECT1"ID="FM63963"Controller addressIDXID="w1795"BOOK="_idx" COLLECTION="nw41" TIDREF="i826"The number the operating system uses to locate the controller on a disk channel. The number is physically set (usually with jumpers) on a disk controller board.RENDERAS="SECT1"Controller boardIDXID="w1796"BOOK="_idx" COLLECTION="nw41" TIDREF="i826"A device that enables a computer to communicate with another device, such as a hard disk or tape drive.The controller board manages input/output and regulates the operation of its associated device.Controller circuitry is incorporated in most new hard disks and tape drives; a separate controller board isn't used.See also IDREF="FM75975""SCSI."RENDERAS="SECT1"Copy Inhibit (Ci) attributeIDXID="w1797"BOOK="_idx" COLLECTION="nw41" TIDREF="i840"A file attribute valid only on Macintosh workstations that prevents users from copying the file.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"ID="FM81199"Country objectIDXID="w1798"BOOK="_idx" COLLECTION="nw41" TIDREF="i861"A container object that represents a country where your network resides and organizes other Directory objects with the country.For example, you could use a Country object for the country where your organization headquarters reside or, if you have a multinational network, for each country that is a part of your network.The Country object isn't part of the default NetWare 4.1 server installation. To use a Country object, create it at installation. Using a Country object in NDS isn't a requirement for interoperability with other X.500-compliant directory services.See also IDREF="FM13600""Object"; IDREF="FM37599""Container object"; "BOOK="superenu" COLLECTION="nw41"Creating Container Objects" in Chapter 1 of Supervising the Network;  see Chapter 5, "BOOK="getstenu" COLLECTION="nw41"Planning NetWare Directory Services Implementation," of Introduction to NetWare Directory Services.PAGENUM=58 ID="BP65"RENDERAS="SECT1"Create rightIDXID="w1799"BOOK="_idx" COLLECTION="nw41" TIDREF="i871"A file system right that grants the right to create new files or subdirectories, or to salvage a file after it has been deleted.Also, an object right that grants the right to create a new object in the Directory tree.See also IDREF="FM74455""Rights."RENDERAS="SECT1"Custom Device Module(CDM) The driver component in NPATM used to drive specific storage devices attached to the host adapter.See IDREF="FM87820""NetWare Peripheral Architecture."RENDERAS="SECT1"CylinderIDXID="w1800"BOOK="_idx" COLLECTION="nw41" TIDREF="i909"IDXID="w1801"BOOK="_idx" COLLECTION="nw41" TIDREF="i1634"Used to organize data on a hard disk. Some hard disks have multiple platters with a read/write head for each side of each platter. The group of read/write heads moves in unison to the same track number on each platter side.This group of tracks is called a cylinder and is numbered according to the tracks it references. For example, the 0 cylinder is a group of 0 tracks.PAGENUM=59 ID="BP66"DRENDERAS="SECT1"IDXID="w1802"BOOK="_idx" COLLECTION="nw41" TIDREF="i911"
DaemonA process running in the background that can spawn (initialize) other processes with little or no user input.Daemons provide services for clients such as printing, remote printing, and server advertising.Some daemon processes, such as the NetWare daemon, perform administrative functions and access the host file system.RENDERAS="SECT1"ID="FM57339"IDXID="w1803"BOOK="_idx" COLLECTION="nw41" TIDREF="i914"IDXID="w1804"BOOK="_idx" COLLECTION="nw41" TIDREF="i1542"
Data forkThe part of the Macintosh file containing the series of bytes which makes up the actual file data. For example, the data fork of an application file contains the instructions that make the application work.See also IDREF="FM86837""Macintosh files."RENDERAS="SECT1"ID="FM55003"Data migrationIDXID="w1805"BOOK="_idx" COLLECTION="nw41" TIDREF="i914"IDXID="w1806"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"IDXID="w1807"BOOK="_idx" COLLECTION="nw41" TIDREF="i2460"The transfer of inactive data from a NetWare volume to an optical disc storage device.Data migration lets you move data to an optical disc storage device, called a jukebox, while NetWare still sees the data as residing on the volume.This frees valuable hard disk space for often-used files while still allowing slower access to infrequently used files.For example, a law firm might store case reports on a 500-megabyte (MB) volume with data migration. The firm doesn't want to archive these files because it might need any of them at any time. Any single file, however, has only a small chance of being used.PAGENUM=60 ID="BP67"Data migration allows this firm to transfer all these files from its 500MB hard disk to another storage media. These files no longer reside on the NetWare volume (thus freeing disk space), but take only a few extra seconds to call up.Data migration is enabled and disabled at the volume level using INSTALL.NLM. You can use file system attributes to mark files as eligible or ineligible for migration.See also IDREF="FM85330""Attributes"; IDREF="FM40870""High Capacity Storage System."RENDERAS="SECT1"ID="FM20059"Data protectionIDXID="w1808"BOOK="_idx" COLLECTION="nw41" TIDREF="i914"A means of ensuring that data on the network is safe.NetWare protects data primarily by maintaining duplicate file directories and by redirecting data from bad blocks to reliable blocks on the NetWare server's hard disk.RENDERAS="SECT2"Protecting Data Location InformationA hard disk's DET and FAT contain address information that tells the operating system where data can be stored or retrieved.If the blocks containing these tables are damaged, some or all of the data may be irretrievable.NetWare greatly reduces the possibility of losing this information by maintaining duplicate copies of the DET and FAT on separate areas of the hard disk.If one of the blocks in the original tables is damaged, the operating system switches to the duplicate tables to get the location data it needs.The faulty sector is then listed in the disk's bad block table, and the data it contained is stored elsewhere on the disk.Every time the server is turned on, the operating system performs a consistency check on both sets of DETs and FATs to verify that the two copies are identical.If both sets don't match, a warning is sent, and the network supervisor should run VREPAIR.PAGENUM=61 ID="BP68"RENDERAS="SECT2"Protecting Data against Surface DefectsNetWare hard disks store data in 4, 8, 16, 32, or 64KB blocks. These blocks are specific data storage locations on the disk's magnetic surface. (Block size is the same on all segments of a volume. See IDREF="FM84883""Block.") Due to the constant reading and writing of data to disk, some storage blocks lose their capacity to store data.NetWare prevents data from being written to unreliable blocks by employing two complementary features known as read-after-write verification and Hot FixTM.These features, illustrated in the next two figures, enable a hard disk to maintain the same data integrity it had when it was first tested and installed.Read-after-write verification. When data is written to disk, the data is immediately read back from the disk and compared to the original data still in memory.LABEL="11" FLOAT="0"Read-after-Write VerificationFILEREF="n40co35a.tif"If the data on the disk matches the data in memory, the write operation is considered successful, the data in memory is released, and the next disk I/O operation takes place.PAGENUM=62 ID="BP69"If the data on the disk doesn't match the data in memory, the operating system determines (after making appropriate retries) that the disk storage block is defective.The Hot Fix feature redirects the original block of data (still in memory) to the Hot Fix Redirection Area, where the data can be stored correctly.IDXID="w1809"BOOK="_idx" COLLECTION="nw41" TIDREF="i1700"Hot Fix Redirection Area. A small portion of the disk's storage space is set aside as the Hot Fix Redirection Area. This area holds data blocks that are redirected there from faulty blocks on the disk.Hot Fix is always active unless the disk fails and is inoperative, or the redirection area is full.Once the operating system records the address of the defective block in a section of the Hot Fix area reserved for that purpose, the server won't attempt to store data in the defective block.LABEL="12" FLOAT="0"Hot FixFILEREF="n40co36a.tif"Read-after-write verification and Hot Fix are transparent. The network supervisor or a console operator can view Hot Fix activity in SERVMAN or MONITOR.PAGENUM=63 ID="BP70"Disk mirroring or duplexing. You can also protect your data with disk mirroring or duplexing.Mirroring stores the same data on separate disks on the same controller channel; duplexing stores the same data on separate disks on separate controller channels.Duplexing is the preferred method since two channels rarely fail simultaneously.See also IDREF="FM71720""Directory Entry Table"; IDREF="FM66029""Disk mirroring"; IDREF="FM60634""Disk duplexing"; IDREF="FM93344""System Fault Tolerance."RENDERAS="SECT1"ID="FM76561"Data setIDXID="w1810"BOOK="_idx" COLLECTION="nw41" TIDREF="i914"IDXID="w1811"BOOK="_idx" COLLECTION="nw41" TIDREF="i3953"A set of data that can be manipulated by SBACKUP.Data sets can contain different items depending on which Target Service Agent they are related to. The following figure shows typical NetWare data sets.LABEL="13" FLOAT="0"Types of Informational Items Data Sets ContainFILEREF="n40co92a.tif"See also IDREF="FM84298""Restore."PAGENUM=64 ID="BP71"RENDERAS="SECT1"DCDBAn IBM file that is associated with LAN Manager* and LAN Server*.See IBM documentation.RENDERAS="SECT1"Default driveIDXID="w1812"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"IDXID="w1813"BOOK="_idx" COLLECTION="nw41" TIDREF="i1218"IDXID="w1814"BOOK="_idx" COLLECTION="nw41" TIDREF="i4837"The drive a workstation is currently using. The drive prompt, such as A:> or F:>, identifies the drive.RENDERAS="SECT1"Default serverIDXID="w1815"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"IDXID="w1816"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"The server you attach to when you load the NetWare RequesterTM. The default server is the preferred server specified in your NET.CFG file.RENDERAS="SECT1"Delete Inhibit (Di) attributeIDXID="w1817"BOOK="_idx" COLLECTION="nw41" TIDREF="i976"A file system attribute that prevents any user from erasing the directory or file.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"Delete rightIDXID="w1818"BOOK="_idx" COLLECTION="nw41" TIDREF="i980"An object right that grants the right to delete an object from the Directory tree.See also IDREF="FM74455""Rights."RENDERAS="SECT1"DelimiterIDXID="w1819"BOOK="_idx" COLLECTION="nw41" TIDREF="i992"A symbol or character that signals the beginning or end of a command or of a parameter within a command.For example, in the command MOREINFO="NONE"NCOPY F:*.* G:, the blank space between F:*.* and G: is a delimiter that marks two distinct parameters.Other delimiters used in NetWare include the comma (,), the period (.), the slash (/), the backslash (\), the hyphen (-), and the colon (:).PAGENUM=65 ID="BP72"RENDERAS="SECT1"ID="FM91450"Destination serverIDXID="w1820"BOOK="_idx" COLLECTION="nw41" TIDREF="i1015"IDXID="w1821"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"The NetWare 4 server to which you migrate data files, bindery files, and other information from a previous NetWare version or another network operating system when upgrading to NetWare 4.See also IDREF="FM24361""Source server."RENDERAS="SECT1"DET(Directory Entry Table) A table that contains basic information about files, directories, directory trustees, or other entities on the volume.See IDREF="FM71720""Directory Entry Table."RENDERAS="SECT1"ID="FM41988"Device driverIDXID="w1822"BOOK="_idx" COLLECTION="nw41" TIDREF="i1022"IDXID="w1823"BOOK="_idx" COLLECTION="nw41" TIDREF="i1226"A program (usually an NLM) that controls devices attached to the computer, such as a printer, network board, diskette drive, hard disk, or monitor. Device drivers expand an operating system's ability to work with peripherals because they control the software routines that make peripherals work.Device drivers that enable communication between peripherals and the NetWare operating system are NLM programs. Two types of device drivers are disk drivers and NPA drivers.RENDERAS="SECT2"Disk DriversThe disk driver talks to an adapter that is connected by an internal cable to the disk drives.Depending on the type of disk controller or adapter, one or more disk drives can be connected. Drivers can be loaded into the operating system during installation or at the command line.Disk drivers includeMARK=BULLETISADISK.DSK. For Industry Standard Architecture hard disks such as MFM, and ESDI (if the ESDI controller isn't IBM PS/2-style).IDE.DSK. For ATA Drives (also known as Integrated Drive Electronics) hard disks.PAGENUM=66 ID="BP73""SCSI.DSK." (The name of the SCSI disk driver is vendor-specific.) For hard disks connected to SCSI controllers in the ISA, EISA architecture computers.PS2ESDI.DSK. For hard disks connected to ESDI controllers in IBM Micro Channel* architecture PS/2* computers.PS2SCSI.DSK. For hard disks connected to SCSI controllers in IBM Micro Channel architecture PS/2 computers.Other disk drivers are available from third-party vendors.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"LOAD" in Utilities Reference.RENDERAS="SECT2"NPA DriversThe NPA drivers are called Host Adapter Modules (HAMs) and CDMs, which together help the Media Manager in NetWare keep track of and communicate with a variety of storage devices and media.Just as disk drivers support adapters and the hard disk devices attached to them, HAMs and CDMs support host adapters and the storage devices attached to them. (HAMs drive the host adapter and CDMs drive the storage devices attached to the host adapter.)The NPA drivers includeMARK=BULLETSCSIPS2.HAM---A host adapter module for PS2 SCSI adapters.SCSI154X.HAM---A host adapter module designed for Adaptec 154X host adapters.SCSIHD.CDM---A custom device module for hard disks. Can be used with any SCSI host adapter module.SCSICD.CDM---A custom device module which provides generic support for some compact disc drives. Can be used with any SCSI host adapter module.PAGENUM=67 ID="BP74"SCSI2TP.CDM---A custom device module which provides generic support for some tape devices.SCSIMO.CDM---A custom device module which provides generic support for some removable magneto-optical drives.IDEATA.HAM---A host adapter module for IDE host adapters.IDEHD.CDM---A custom device module for hard disks. Can be used with any IDE host adapter module.See also IDREF="FM41878""LAN driver"; IDREF="FM87820""NetWare Peripheral Architecture."RENDERAS="SECT1"ID="FM29049"Device numberingIDXID="w1824"BOOK="_idx" COLLECTION="nw41" TIDREF="i3021"IDXID="w1825"BOOK="_idx" COLLECTION="nw41" TIDREF="i1022"A method of identifying a device, such as a hard disk, to allow the device to work on the network.Devices are identified by three sets of numbers:MARK=BULLETPhysical addressDevice codeLogical device number.The following figure shows how physical addresses correspond to logical numbers and device codes (based on the physical order in which the devices are loaded). Each box in the second column describes the physical address and device code. Device # indicates the logical number of the disk.PAGENUM=68 ID="BP75"LABEL="14" FLOAT="0"IDXID="w1826"BOOK="_idx" COLLECTION="nw41" TIDREF="i3021"IDXID="w1827"BOOK="_idx" COLLECTION="nw41" TIDREF="i1022"Physical and Logical Device NumberingFILEREF="n41co37a.tif"PAGENUM=69 ID="BP76"MARK=BULLETPhysical address. Established when the driver reads the address as it was set by jumpers or by software configuration programs.Device code. Determined by the driver ID, driver load instance, disk number, and controller number, as illustrated in the following figure:FILEREF="n41co02a.tif"Logical device number. Determined by the order in which the disk drivers are loaded. Both the device code and the logical device number are assigned when the disk driver is loaded. Thus, you must load disk drivers in the same order to maintain the same identification numbers.If a disk driver is unloaded and then reloaded, the third and forth digits in the identification number change.Consider making a chart of your setup. List the order that the disk drivers are loaded in the STARTUP.NCF file.Then, if you receive a message stating that device 1 (20000100) has been deactivated due to disk failure, you know which disk has failed.After device numbers are assigned, NetWare also assigns physical and logical partition numbers to the partitions created on the hard disks.The following figure displays the relationship between logical devices and physical partition numbers. Each logical device is assigned a partition number for each type of partition.PAGENUM=70 ID="BP77"LABEL="15" FLOAT="0"Logical Devices and Partition NumbersFILEREF="n41co38a.tif"NetWare 4 recognizes DOS and NetWare partitions. All other partition types, such as UNIX and OS/2 partitions, are listed as non-NetWare partitions.Hot Fix messages use the physical partition number when recording which hard disks have blocks of data that need to be redirected.All physical partitions are assigned logical partition numbers. These numbers are assigned to both the mirrored disks and the DOS and non-NetWare partitions.The following figure displays the relationship between physical partitions and logical partitions. The chart assumes that partition 1 is mirrored to partition 4 and that partition 2 is mirrored to partition 5.PAGENUM=71 ID="BP78"LABEL="16" FLOAT="0"Partition Numbers and Logical Partition NumbersFILEREF="n41co39a.tif"Mirroring messages use the logical partition number to record which hard disks are being remirrored or unmirrored. (See also IDREF="FM60634""Disk duplexing"; IDREF="FM66029""Disk mirroring.")Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"SET" and "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities Reference.RENDERAS="SECT1"Device sharingIDXID="w1828"BOOK="_idx" COLLECTION="nw41" TIDREF="i1022"The shared use of centrally located devices (such as printers, modems, and disk storage space) by users or software programs.By attaching a device to a network that several workstations are logged in to, you can use resources more efficiently.An example of device sharing is when two clients share disk storage space where Netware volume data is stored. Another example of device sharing is when two network clients have access to a shared printer, as is illustrated in the following figure. PAGENUM=72 ID="BP79"FILEREF="n41co99a.tif"RENDERAS="SECT1"ID="FM45928"DirectoryIDXID="w1829"BOOK="_idx" COLLECTION="nw41" TIDREF="i1097"IDXID="w1830"BOOK="_idx" COLLECTION="nw41" TIDREF="i1097"Directory: A common name for the NetWare Directory database, which organizes NDS objects in a hierarchical tree structure called the Directory tree. (See IDREF="FM83674""NetWare Directory Services.")IDXID="w1831"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"directory: A component in the NetWare file system, used to contain files and subdirectories. (See IDREF="FM22177""File system.")RENDERAS="SECT1"Directory and file rightsRights that control what a trustee can do with a directory or file.See IDREF="FM74455""Rights."RENDERAS="SECT1"Directory cachingIDXID="w1832"BOOK="_idx" COLLECTION="nw41" TIDREF="i1048"A method of decreasing the time it takes to determine a file's location on a disk.See IDREF="FM22916""Cache memory."RENDERAS="SECT1"Directory databaseA common name for the NetWare Directory database.See IDREF="FM40161""NetWare Directory database."PAGENUM=73 ID="BP80"RENDERAS="SECT1"ID="FM77162"Directory entryIDXID="w1833"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"Basic information for NetWare server directories and files, such asMARK=BULLETFile or directory nameOwnerDate and time of the last update (for files)Location of the first block of data on the network hard diskDirectory entries are located in a directory table on a network hard disk and contain information about all files on the volume.The server uses directory entries to track file location, changes made to the file, and other related file properties.See also IDREF="FM71720""Directory Entry Table."RENDERAS="SECT1"ID="FM71720"Directory Entry TableIDXID="w1834"BOOK="_idx" COLLECTION="nw41" TIDREF="i1053"(DET) A table that contains basic information about files, directories, directory trustees, or other entities on the volume.The DET occupies one or more directory blocks on the volume. Each block has 4 KB (4,096 bytes) of data. A directory entry is 128 bytes long, so each block can hold 32 directory entries.Volume SYS: starts out with seven blocks for its directory table. When a volume needs to add another block to its directory table, the server allocates another block.The maximum directory blocks per volume is 65,536. Since each block can accommodate 32 entries, the maximum directory table entries per volume is 2,097,152.The server doesn't cache entire directory tables; it only caches directory blocks in use.PAGENUM=74 ID="BP81"In NetWare 4, a volume can span multiple drives, so each drive can have more than one directory table.See also IDREF="FM77162""Directory entry."RENDERAS="SECT1"ID="FM91856"Directory hashingIDXID="w1835"BOOK="_idx" COLLECTION="nw41" TIDREF="i1057"A process that facilitates access to a file in a large volume by calculating the file's address both in cache memory and on the hard disk.When a workstation wants to read a file from the NetWare server, the server performs a hash algorithm which predicts an address on a hash table.In NetWare 4, it is common to find the file 95% of the time on the first try. This method is much more efficient than searching for a file sequentially.See also IDREF="FM22916""Cache memory."RENDERAS="SECT1"ID="FM48764"IDXID="w1836"BOOK="_idx" COLLECTION="nw41" TIDREF="i1062"
Directory Map objectA leaf object that refers to a directory on a volume.You can't look at the file structure on the volume from the Directory Map object, but login scripts can use the MAP command with a Directory Map object to record the location of frequently used applications.If the application moves, you need to change only the directory map; all login scripts remain unchanged.See also IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Creating and Using Directory Map Objects" in Chapter 2 of Supervising the Network.RENDERAS="SECT1"Directory pathIDXID="w1837"BOOK="_idx" COLLECTION="nw41" TIDREF="i1068"The full specification that includes server name, volume name, and name of each directory leading to the file system directory you need to access.See also IDREF="FM39775""Drive mapping"; IDREF="FM22177""File system."PAGENUM=75 ID="BP82"RENDERAS="SECT1"Directory partitionA common name used for NetWare Directory partitions.See IDREF="FM61672""NetWare Directory partition."RENDERAS="SECT1"Directory replicaA common name used for NetWare Directory replicas.See IDREF="FM27324""NetWare Directory replica."RENDERAS="SECT1"Directory rightsRights that control what a trustee can do with a directory.See IDREF="FM74455""Rights."RENDERAS="SECT1"Directory servicesA database built into NetWare 4 that maintains information about every resource on the network.See IDREF="FM83674""NetWare Directory Services."RENDERAS="SECT1"Directory structureIDXID="w1838"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"A hierarchical structure that represents how Directory partitions are related to each other in the Directory database. (See IDREF="FM69136""Directory tree.")Also, formerly used to describe the filing system of volumes, directories, and files that the NetWare server uses to organize data on its hard disks. (See IDREF="FM22177""File system.")RENDERAS="SECT1"ID="FM69136"Directory treeIDXID="w1839"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"A hierarchical structure of objects in the Directory database. The Directory tree includes container objects that are used to organize the network.The structure of the Directory tree can be based on a logical organization of objects, and not necessarily on their physical location.The following figure shows an example of a Directory tree:PAGENUM=76 ID="BP83"LABEL="17" FLOAT="0"IDXID="w1840"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"Directory TreeFILEREF="n41co10a.tif"See also IDREF="FM14193""Browsing"; IDREF="FM13600""Object"; IDREF="FM61672""NetWare Directory partition"; IDREF="FM27324""NetWare Directory replica";  see Chapter 5, "BOOK="getstenu" COLLECTION="nw41"Planning NetWare Directory Services Implementation," of Introduction to NetWare Directory Services.RENDERAS="SECT1"DiskIDXID="w1841"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"A magnetically encoded storage medium in the form of a plate (also called a platter). The following types of disks are used with personal computers:MARK=BULLETHard disk. Uses a metallic base and is usually installed within a computer or disk subsystem. (In some cases, they are removable.)IDXID="w1842"BOOK="_idx" COLLECTION="nw41" TIDREF="i1525"IDXID="w1843"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"Floppy disk (Also called a diskette). Uses a mylar base and is removable.PAGENUM=77 ID="BP84"IDXID="w1844"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"CD-ROM (Compact Disc Read Only Memory). A small plastic optical disc that cannot be written to or erased.IDXID="w1845"BOOK="_idx" COLLECTION="nw41" TIDREF="i3099"Optical disc. Either erasable and writable, or WORM (Write Once, Read Many).See also IDREF="FM20059""Data protection"; IDREF="FM76186""Disk partition"; IDREF="FM19745" "Hard disk."RENDERAS="SECT1"Disk controllerIDXID="w1846"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"This can be an adapter, board, or a chip set on the mother board. This device controls how data is written to and retrieved from the disk drive.The disk controller sends signals to the disk drive's logic board to regulate the movement of the head as it reads data from or writes data to the disk.See also IDREF="FM26878""Host Bus Adapter."RENDERAS="SECT1"ID="FM58921"Disk driverIDXID="w1847"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"IDXID="w1848"BOOK="_idx" COLLECTION="nw41" TIDREF="i1226"IDXID="w1849"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"
An NLM that forms the interface between the NetWare operating system and the hard disks. The disk driver talks to an adapter that is connected by an internal cable to the disk drives.Depending on the type of disk controller or adapter, one or more disk drives can be connected. Drivers can be loaded into the operating system during installation or at the command line.For specific Novell® driver names and descriptions, see IDREF="FM41988""Device driver." Other disk drivers are available from third-party vendors.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"LOAD" in Utilities Reference.RENDERAS="SECT1"ID="FM60634"Disk duplexingIDXID="w1850"BOOK="_idx" COLLECTION="nw41" TIDREF="i1117"A means of duplicating data to provide data protection. Disk duplexing consists of copying data onto two hard disks, each on a separate disk channel.This protects data against the failure of a hard disk, or of the hard disk channel between the disk and the NetWare server. (The hard disk channel includes the disk controller and interface cable.)PAGENUM=78 ID="BP85"If any component on one channel fails, the other disk can continue to operate without data loss or interruption because it is on a different channel.The operating system sends a warning message to the console when a drive has failed. Restore the duplexing protection as soon after a failure as possible.Because the warning message can scroll off the console screen before you see it, we recommend that you check the status of disk mirroring periodically to ensure that the channels are synchronized.LABEL="18" FLOAT="0"IDXID="w1851"BOOK="_idx" COLLECTION="nw41" TIDREF="i1117"Disk DuplexingFILEREF="n40co11a.tif"Duplexing alone doesn't guarantee data protection. If both disk channels fail at the same time, or if the computer itself fails, you still lose your data. Therefore, back up your data regularly. Use SBACKUP or another backup utility.Disk duplexing allows the same data to be written to all disks simultaneously.Since the disks are on different channels, data transfer is faster than with disk mirroring, where data is written to the disks sequentially over the same channel.PAGENUM=79 ID="BP86"Disk duplexing also allows split seeks. This sends read requests to whichever disk can respond first. Multiple read requests are also split between the duplexed disks for simultaneous processing.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"INSTALL" in Utilities Reference.See also IDREF="FM29049""Device numbering"; IDREF="FM66029""Disk mirroring."RENDERAS="SECT1"Disk formatIDXID="w1852"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"IDXID="w1853"BOOK="_idx" COLLECTION="nw41" TIDREF="i1548"The way in which a hard disk is prepared or structured so that it can receive data from the computer's operating system. Disk formatting is a function of the operating system.Hard disk formats include a FAT for DOS and NetWare, High Performance File System (HPFS) for OS/2, Hierarchical File System (HFS) for Macintosh, and Berkeley Fast File System (FFS) for UNIX.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"INSTALL" in Utilities Reference.For specific information on formatting your hard disk, see your computer's operating system manual.See also "BOOK="superenu" COLLECTION="nw41"Testing for Bad Disk Blocks," in Chapter 7 of Supervising the Network.RENDERAS="SECT1"ID="FM66029"Disk mirroringIDXID="w1854"BOOK="_idx" COLLECTION="nw41" TIDREF="i1122"IDXID="w1855"BOOK="_idx" COLLECTION="nw41" TIDREF="i2479"The duplication of data from the NetWare partition on one hard disk to the NetWare partition on another hard disk.When you mirror disks, two or more hard disks on the same channel are paired. Blocks of data written to the original (primary) disk are also written to the duplicate (secondary) disk.The disks operate in tandem, constantly storing and updating the same files. Should one of the disks fail, the other disk can continue to operate without data loss or interruption.PAGENUM=80 ID="BP87"FILEREF="n40co12a.tif"Mirroring alone doesn't guarantee data protection. If both hard disks fail at the same time, or if the computer itself fails, you still lose your data. Therefore, back up your data regularly. Use SBACKUP or another backup utility.If one of the disks fails, the operating system sends a warning to the console to indicate the failure so that the mirroring protection can be restored as soon as possible.Because the warning message can scroll off the console screen before you see it, we recommend that you check the status of disk mirroring periodically to ensure that the channels are synchronized.Because disk mirroring duplicates disks on the same channel, it doesn't protect against failures that may occur along the channel between the disks and the NetWare server.A problem in the channel would cause a failure in both disks.See also IDREF="FM29049""Device numbering"; IDREF="FM60634""Disk duplexing."PAGENUM=81 ID="BP88"RENDERAS="SECT1"ID="FM76186"Disk partition IDXID="w1856"BOOK="_idx" COLLECTION="nw41" TIDREF="i1125"A logical unit that NetWare server hard disks can be divided into.In NetWare 4, a NetWare partition is created on each hard disk.NetWare disk partitions are not related to NDS partitions. Disk partitions are subdivisions of a hard disk. An NDS partition is a subtree within the NDS directory tree. (See IDREF="FM23688""Partition (disk).")Volumes are created from the pool of NetWare partitions. A volume consists of one or more volume segments.One of the server's internal hard disks can contain both an active, primary DOS partition, and a NetWare partition.When the server boot files are copied to the DOS partition and included in the AUTOEXEC.BAT file, the NetWare operating system boots automatically.You need only one DOS partition; the other hard disks need to contain only a NetWare partition.A NetWare partition consists of a Hot Fix Redirection Area plus a large data area. The logical sector 0 of a NetWare partition is the first sector of the data area.The following figures illustrate how hard disks can be partitioned:LABEL="19" FLOAT="0"Disk Partition: Single VolumeFILEREF="n40co30a.tif"PAGENUM=82 ID="BP89"LABEL="20" FLOAT="0"Disk Partition: Volume Spanning Multiple DisksFILEREF="n40co31a.tif"A data area contains four copies of the Volume Definition Table (VDT). Each table contains a list of all volume segments in that NetWare partition.Four copies are maintained for fault tolerance. If a disk error occurs and one table is corrupted, the error can be detected and corrected.The rest of the data area can contain one to eight volume segments. Each IDXID="w1857"BOOK="_idx" COLLECTION="nw41" TIDREF="i1125"
segment can belong to the same volume or to a different volume.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"INSTALL" in Utilities Reference.See also IDREF="FM20059""Data protection"; IDREF="FM95725""Hot Fix"; IDREF="FM96914" "Volume."RENDERAS="SECT1"Disk subsystemIDXID="w1858"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"An external unit that attaches to the NetWare server and contains hard disk drives, a tape drive, optical drives, or any combination of these.The disk subsystem gives the server more storage capacity.PAGENUM=83 ID="BP90"RENDERAS="SECT1"Distance vectorIDXID="w1859"BOOK="_idx" COLLECTION="nw41" TIDREF="i1154"An algorithm that disseminates routing information to routers on a network.A router using the distance vector algorithm maintains only enough information to know how to reach the next router destination (hop) on the network. Distance vector routers periodically forward this information to each other, even if it has not changed since the last update. Such broadcasts create unnecessary traffic on the network and consume router CPU time.RENDERAS="SECT1"ID="FM74578"Distribution List objectIDXID="w1860"BOOK="_idx" COLLECTION="nw41" TIDREF="i1161"A leaf object that represents a list of mail recipients.For example, you can create a Distribution List object called Recreation Committee. When anyone wants to send a message to all the members in the Recreation Committee, they can simply address their mail to Recreation Committee.The member of a Distribution List can be a user, another Distribution List object, a Group object, or an Organizational Role object.Although you can send mail to all the members of a Group, there are some differences between a Distribution List and a Group:MARK=BULLETMembers of a group are security equal to the Group object, but the members of a Distribution List are not security equal to the Distribution List.A Group is used mainly to simplify assigning trustee assignments and creating login scripts, whereas a Distribution List is used for simplifying sending mail to a list of recipients.A Distribution List can have another Distribution List as a member, but a Group cannot have another Group as a member.PAGENUM=84 ID="BP91"RENDERAS="SECT1"ID="FM37708"DomainsIDXID="w1861"BOOK="_idx" COLLECTION="nw41" TIDREF="i3126"IDXID="w1862"BOOK="_idx" COLLECTION="nw41" TIDREF="i3144"Memory segments in NetWare that allow you to separate NLM files from the operating system. NetWare 4.1 has two domains, OS domain and OS_PROTECTED domain. By loading an NLM in the OS_PROTECTED domain, you prevent a misbehaved NLM from writing to memory it should not have access to. This keeps a misbehaved NLM from bringing down the server.The NetWare operating system assigns memory segments to one or two memory domains, depending on how you configure the server. By loading DOMAIN.NLM before any other NLM programs are loaded, you establish the OS_PROTECTED domain.To determine the recommended domain for third-party NLM programs such as database and backup modules, check the documentation that came with the NLM.If you have an NLM running in one domain, and it is accessed by an NLM that is running in a separate domain, make sure your NLM provides the necessary cross-domain calls. See also IDREF="FM72408""Memory protection"; IDREF="FM45002""Paging"; Appendix C, "BOOK="utlrfenu" COLLECTION="nw41"Memory Domains for NLMs and Autoloaded NLMs" in Utilities Reference. RENDERAS="SECT1"Don't Compress (Dc) attributeIDXID="w1863"BOOK="_idx" COLLECTION="nw41" TIDREF="i1178"A file system attribute that prevents files from being compressed.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"Don't Migrate (Dm) attributeIDXID="w1864"BOOK="_idx" COLLECTION="nw41" TIDREF="i1179"A file system attribute that prevents files from being migrated to a secondary storage device (such as a tape drive or optical disc).See also IDREF="FM85330""Attributes."PAGENUM=85 ID="BP92"RENDERAS="SECT1"Don't Suballocate (Ds) attributeIDXID="w1865"BOOK="_idx" COLLECTION="nw41" TIDREF="i1180"A file system attribute that prevents an individual file from being suballocated, even if suballocation is enabled for the system.Use for files that are often enlarged or appended, such as certain database files.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"DOS boot recordIDXID="w1866"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"A record containing information that ROM-BIOS uses to determine which device to boot from. The boot record can be on either a floppy diskette, a local hard disk, or a remote boot chip.ROM-BIOS then runs a short program from the boot record to determine disk format and location of system files and directories.Using this information, ROM-BIOS loads the system files (including two hidden files, IBMBIO.COM and IBMDOS.COM) and the command processor (COMMAND.COM).RENDERAS="SECT1"ID="FM97421"DOS clientIDXID="w1867"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"A workstation that boots with DOS and gains access to the network through eitherMARK=BULLETThe NetWare DOS RequesterTM software (for NetWare 4).A NetWare shell (for NetWare 2 and NetWare 3).With DOS client software, users can perform networking tasks. These tasks include mapping drives, capturing printer ports, and sending messages. Using the NetWare Requester in NetWare 4, users can change contexts.See also IDREF="FM99174""Client."RENDERAS="SECT1"DOS deviceIDXID="w1868"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"IDXID="w1869"BOOK="_idx" COLLECTION="nw41" TIDREF="i1022"A storage unit compatible with the DOS disk format---usually a disk drive or tape backup unit.PAGENUM=86 ID="BP93"The UPGRADE and SBACKUP utilities both write to a DOS device. The DOS device should be a read/write device.Because the utilities both read and write data, the media the DOS device uses must allow the data to be updated or changed.The following devices can be used. If the device runs out of storage space on the media, you are prompted to insert another one.MARK=BULLETWorkstation floppy disk drives (can't be used with SBACKUP)Tape drives with a DOS device driverOptical drives that are read/write devices and have a DOS device driverThe following devices can also be used as DOS devices:MARK=BULLETWorkstation hard disk drivesNetwork drivesAn optical drive or a WORM drive that has a DOS device driverRENDERAS="SECT1"DOS RequesterThe DOS client software portion of NetWare 4.See IDREF="FM21900""NetWare DOS Requester."RENDERAS="SECT1"DOS setup routineIDXID="w1870"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"IDXID="w1871"BOOK="_idx" COLLECTION="nw41" TIDREF="i4112"The routine that sets up the system configuration of your DOS client or NetWare server.The setup routine records the system's built-in features (add-on boards, hard drives, disk drives, ports, math-coprocessor) and available system memory. It also lets you set date and time, password, and keyboard speed.The system configuration is accessed from the reference diskette (for IBM PS/2 systems) or from the setup or user diagnostics diskette (for most other systems).PAGENUM=87 ID="BP94"Instructions for running the DOS setup routine are usually contained in the introduction to your PC's operations guide.RENDERAS="SECT1"ID="FM39874"DOS versionIDXID="w1872"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"The version number and name of the DOS you are using (Novell DOS 7TM, MS DOS* 3.3, etc.).Different machines use different versions of DOS, which are generally not compatible.Since all DOS versions have identically named utilities and command interpreters, you can't place the files of different DOS versions in the same directory.You must create a DOS directory for each workstation type or DOS version you use and load the DOS files into it.See also IDREF="FM22177""File system"; IDREF="FM23712""Login scripts."RENDERAS="SECT1"ID="FM87366"DriveIDXID="w1873"BOOK="_idx" COLLECTION="nw41" TIDREF="i1218"IDXID="w1874"BOOK="_idx" COLLECTION="nw41" TIDREF="i3305"IDXID="w1875"BOOK="_idx" COLLECTION="nw41" TIDREF="i1218"Physical drive. A storage device that data is written to and read from, such as a disk drive or tape drive. A drive that is physically contained in or attached to a workstation is called a local drive.IDXID="w1876"BOOK="_idx" COLLECTION="nw41" TIDREF="i2202"IDXID="w1877"BOOK="_idx" COLLECTION="nw41" TIDREF="i1218"Logical drive. An identification for a specific directory located on a disk drive. For example, network drives point to a directory on the network, rather than to a local disk.RENDERAS="SECT1"ID="FM39775"Drive mappingIDXID="w1878"BOOK="_idx" COLLECTION="nw41" TIDREF="i1224"A pointer to a location in the file system, represented as a letter assigned to a directory path on a volume.To locate a file, you follow a path that includes the volume, directory, and any subdirectories leading to the file.You create drive mappings to follow these paths for you. You assign a letter to the path, and then use the letter in place of the complete path name.Drive mappings can be temporary or permanent:PAGENUM=88 ID="BP95"MARK=BULLETIDXID="w1879"BOOK="_idx" COLLECTION="nw41" TIDREF="i4465"Temporary mappings. To map a drive so you can use it during your current session, use the NetWare MAP utility (from a DOS or OS/2 workstation). The mapping is only valid until you log out.IDXID="w1880"BOOK="_idx" COLLECTION="nw41" TIDREF="i3299"Permanent mappings. To make drive mappings so you can use them every time you log in, place MAP commands in your login script. (See IDREF="FM23712""Login scripts.")NetWare recognizes four types of drive mappings: local drive mappings, network drive mappings, network search drive mappings, and Directory Map objects.RENDERAS="SECT2"IDXID="w1881"BOOK="_idx" COLLECTION="nw41" TIDREF="i2164"
Local Drive MappingsLocal drive mappings are paths to local media such as hard disk drives and floppy disk drives.In DOS 3.0 and later versions, drives A: through E: are reserved for local mappings. To change this default (for example, if you are using the NetWare DOS Requester, you need all of your drives mapped as DOS drives), use the DOS LASTDRIVE command in your workstation CONFIG.SYS file.RENDERAS="SECT2"IDXID="w1882"BOOK="_idx" COLLECTION="nw41" TIDREF="i2857"
Network Drive MappingsNetwork drive mappings point to volumes and directories on the network. Normally, drives F: through Z: are used for network mappings. Each user can map drive letters to different directories.To create a network drive mapping, use the MAP command, the NETUSER text utility, or the NetWare User Tools graphical utilityRENDERAS="SECT2"IDXID="w1883"BOOK="_idx" COLLECTION="nw41" TIDREF="i2882"IDXID="w1884"BOOK="_idx" COLLECTION="nw41" TIDREF="i3974"
Network Search Drive MappingsNetwork search drive mappings point to directories containing files such as applications or DOS files. Search drive mappings enable the system to locate a program even if it isn't located in the directory you're working in.PAGENUM=89 ID="BP96"Search drive mappings are numbered, although they also have drive letters. For example, search drive 1 (or S1) may also be known as network drive Z:.You can map up to 16 network search drives (letters K: through Z:, starting with Z:). You can't map a search drive and a regular network drive to the same letter.When you request a file and the system can't find it in your current directory, the system looks in every directory a search drive is mapped to.The system searches, following the numerical order of the search drives, until either the program file is found or can't be located.Search drive mappings aren't supported on OS/2 workstations. The search functionality is provided with the OS/2 PATH, LIBPATH, and DPATH commands.RENDERAS="SECT2"IDXID="w1885"BOOK="_idx" COLLECTION="nw41" TIDREF="i1062"
Directory Map ObjectsDirectory Map objects can point to directories that contain frequently-used files such as applications.If you create a Directory Map object to point to an application, users can access the application by clicking on the Directory Map icon from the browser.If the application's location in the directory structure changes, you can update the object instead of having to change all users' drive mappings.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"MAP" and "BOOK="utlrfenu" COLLECTION="nw41"NETUSER" in Utilities Reference.RENDERAS="SECT1"DriverIDXID="w1886"BOOK="_idx" COLLECTION="nw41" TIDREF="i1226"IDXID="w1887"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"Software that forms the interface between the NetWare operating system and devices such as hard disks or network boards.See IDREF="FM41988""Device driver" and IDREF="FM41878""LAN driver."RENDERAS="SECT1"IDXID="w1888"BOOK="_idx" COLLECTION="nw41" TIDREF="i1265"
Dual processingA NetWare® SFT IIITM configuration that assigns parts of the operating system to separate processors.PAGENUM=90 ID="BP97"Because SFT III is split into two 
engines (the IOEngine and the MSEngine), it is possible to run each engine on a separate CPU, creating a dual processing system. However, unless such a system is extremely busy, the extra CPU does not help network performance. Dual processing improves performance only when the servers are being utilized at near maximum capacity. The following figure shows how a dual processing system is configured:LABEL="21" FLOAT="0"Dual ProcessingFILEREF="n41co01a.tif"RENDERAS="SECT1"DuplexingA means of duplicating data to provide data protection. Disk duplexing consists of copying data onto two hard disks, each on a separate disk channel.See IDREF="FM60634""Disk duplexing."RENDERAS="SECT1"Dynamic configurationIDXID="w1889"BOOK="_idx" COLLECTION="nw41" TIDREF="i1275"IDXID="w1890"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"A means of allowing the NetWare server to allocate resources according to need and availability.When the server boots, all free memory is assigned to file caching. As demand increases for other resources (directory cache buffers, for example), the number of available file cache buffers decreases.PAGENUM=91 ID="BP98"The operating system doesn't immediately allocate new resources when a request is received. It waits a specified amount of time to see if existing resources become available to service the demand.If resources become available, no new resources are allocated. If they don't become available within the time limit, new resources are allocated.The time limit ensures that sudden, infrequent peaks of server activity don't permanently allocate unneeded resources.The following parameters are dynamically configured by the operating system:MARK=BULLETDirectory cache buffersFile locksKernel processesKernel semaphoresMaximum number of open filesMemory for NLM programsRouter/server advertisingRouting buffersService processesTTS transactionsTurbo FAT index tablesRelated utilities: "BOOK="utlrfenu" COLLECTION="nw41"MONITOR," "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN," and "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.RENDERAS="SECT1"Dynamic memoryIDXID="w1891"BOOK="_idx" COLLECTION="nw41" TIDREF="i1275"IDXID="w1892"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"The most common form of memory, used for RAM. Dynamic memory requires a continual rewriting of all stored information to preserve data.PAGENUM=92 ID="BP99"If dynamic memory is too slow for a computer's microprocessor, overall performance suffers while the CPU waits for requested information to arrive from memory.A continuous electrical current is necessary to maintain dynamic memory. All data is lost from dynamic memory when the power is turned off.PAGENUM=93 ID="BP100"ERENDERAS="SECT1"ID="FM57690"Effective rightsIDXID="w1893"BOOK="_idx" COLLECTION="nw41" TIDREF="i1294"IDXID="w1894"BOOK="_idx" COLLECTION="nw41" TIDREF="i3851"The rights that an object can actually exercise to see or modify a particular directory, file, or object.An object's effective rights to a directory, file, or object are calculated by NetWare each time that object attempts an action.Effective rights to a file or directory are determined byMARK=BULLETAn object's trustee assignments to the directory, file, or other objectInherited rights from an object's trustee assignments to parent directoriesTrustee assignments of Group objects that a User object belongs toTrustee assignments of objects listed in a User object's "Security Equal To" listIf a user has a trustee assignment to a directory on a given level in the directory structure and one on a higher level, the current trustee assignment overrides the one at the higher level.Trustee assignments to a group, however, are added to individual user trustee assignments.Effective rights to an object are shown in the following figure:PAGENUM=94 ID="BP101"LABEL="22" FLOAT="0"Effective RightsFILEREF="n41co57a.tif"In the figure, MWILKENS' effective rights to access the MANAGERS profile can come fromMARK=BULLETTrustee assignments to MANAGERS that list MWILKENS (rights are explicitly granted)Trustee assignments to MANAGERS that list SALES PV (rights are inherited from the trustee's container)Trustee assignments to SALES LA that list MWILKENS (rights are inherited from the object's container)Rights must pass through MANAGERS' Inherited Rights Filter before becoming effective.Trustee assignments to SALES LA that list SALES PV (inherited from object's container and trustee's container)Rights must pass through MANAGERS' Inherited Rights Filter before becoming effective.Trustee assignments to any Group object that MWILKENS is a member of (rights are only valid when the object requesting rights is a User object)Trustee assignments to any object listed in MWILKENS' "Security Equal To" list (only valid when the object requesting rights is a User object)PAGENUM=95 ID="BP102"If MWILKENS has a trustee assignment to SALES LA and to MANAGERS, the trustee assignment on MANAGERS overrides the trustee assignment on SALES LA.No rights are granted by default. They must be granted by a trustee assignment at some point.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"FILER," "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN," and "BOOK="utlrfenu" COLLECTION="nw41"RIGHTS" in Utilities Reference.See also IDREF="FM13738""Inherited Rights Filter"; IDREF="FM52521""Security"; IDREF="FM26134""Trustee."RENDERAS="SECT1"ID="FM48923"
EGP(Exterior Gateway Protocol) A protocol that exchanges network reachability information between autonomous systems.EGP is part of the TCP/IP protocol suite.See IDREF="FM64249""Exterior Gateway Protocol."RENDERAS="SECT1"Elevator seekingIDXID="w1895"BOOK="_idx" COLLECTION="nw41" TIDREF="i1305"Organizes the way data is read from hard disk storage devices. A shared network disk drive and its related channel can quickly become clogged with disk I/O requests. Elevator seeking logically organizes disk operations as they arrive at the server for processing.A queue is maintained for each disk driver operation within the server. As disk read and write requests are queued for a specific drive, the operation system prioritizes incoming requests based on the drive's head position.As the disk driver services the queue, subsequent requests are located either in the vicinity of the last request or in the opposite direction. Drive heads operate in a sweeping fashion, from the outside to the inside of the disk.Thus, elevator seeking improves disk channel performance by significantly reducing disk head thrashing (rapid back-and-forth movements) and by minimizing head seek times.PAGENUM=96 ID="BP103"RENDERAS="SECT1"Embedded SCSIIDXID="w1896"BOOK="_idx" COLLECTION="nw41" TIDREF="i1306"IDXID="w1897"BOOK="_idx" COLLECTION="nw41" TIDREF="i3969"A hard disk that has a SCSI and a hard disk controller built into the hard disk unit.See also IDREF="FM75975""SCSI."RENDERAS="SECT1"Erase rightIDXID="w1898"BOOK="_idx" COLLECTION="nw41" TIDREF="i1336"A file system right that grants the right to delete directories, subdirectories, or files.See also IDREF="FM74455""Rights."RENDERAS="SECT1"ID="FM81286"Ethernet configurationIDXID="w1899"BOOK="_idx" COLLECTION="nw41" TIDREF="i1351"The setup that allows communication using an Ethernet environment.In an Ethernet environment, stations communicate with each other by sending data in frames along an Ethernet cabling system.Different Ethernet standards use different frame formats. NetWare 4 uses the IEEE 802.2 standard by default. The following figure illustrates the Ethernet 802.2 frame:LABEL="23" FLOAT="0"Ethernet 802.2 FrameFILEREF="n40co93a.tif"To configure stations for Ethernet standards other than 802.2, use a frame statement. For servers and routers, add the frame statement to the LOAD command. For workstations, add the frame statement to the NET.CFG file.PAGENUM=97 ID="BP104"In addition to 802.2, you can use one of the following frame types:MARK=BULLETEthernet 802.3. Used as the default in NetWare 3.11 and earlier versions. This frame type is also referred to as the raw frame. Don't use this frame on a network that uses protocols other than IPX. The following figure illustrates the Ethernet 802.3 raw frame:LABEL="24" FLOAT="0"Ethernet 802.3 Raw FrameFILEREF="n40co94a.tif"Ethernet II. Used on networks that communicate with DEC* minicomputers, and on computers that use TCP/IP or AppleTalk Phase I. The following figure illustrates the Ethernet II frame:LABEL="25" FLOAT="0"Ethernet II FrameFILEREF="n40co95a.tif"Ethernet SNAP (the IEEE standard 802.2 frame type with an extension (SNAP) added to the header). Used on networks that communicate with workstations using protocols such as AppleTalk Phase II. The following figure illustrates the Ethernet SNAP frame:PAGENUM=98 ID="BP105"LABEL="26" FLOAT="0"Ethernet SNAP FrameFILEREF="n40co96a.tif"On Ethernet 802.2, Ethernet II, and Ethernet SNAP cabling systems, stations using different protocol numbers can coexist, but they cannot communicate directly with each other. The 802.3 raw frames are able to communicate with other frames using an internal IPX router in the server.Using Novell ODITM technology, NetWare 4 allows stations with different Ethernet frame types to coexist on the same Ethernet cabling system, as in the following figure:LABEL="27" FLOAT="0"Coexisting Frame TypesFILEREF="n40co98a.tif"Because of the ODI Multiple Link Interface DriverTM (MLID) and Link Support LayerTM (LSL), a single workstation with one network board can communicate with other devices using different types of Ethernet frames.PAGENUM=99 ID="BP106"Even though there may be only one physical network board in the computer, the MLIDTM gives the effect of having multiple network boards and multiple LAN drivers.Unlike traditional dedicated LAN drivers, the MLID is responsible for removing the media-specific (frame-specific) information from the data packets it receives.The packets are then passed on to the LSLTM, which functions much like a switchboard operator, sending the packet to the assigned protocol stack (such as IPX).The following figure illustrates the ODI architecture in a multiple Ethernet frame configuration using IPX protocol.LABEL="28" FLOAT="0"ODI Architecture Using Multiple Ethernet FramesFILEREF="n40co97a.tif"See also IDREF="FM33588""Open Data-Link Interface"; IDREF="FM33398""Multiple Link Interface Driver"; IDREF="FM12535""Link Support Layer"; IDREF="FM21658""Packet."PAGENUM=100 ID="BP107"RENDERAS="SECT1"Execute Only (X) attributeIDXID="w1900"BOOK="_idx" COLLECTION="nw41" TIDREF="i1377"A file system attribute that prevents a file from being copied.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"Extended AppleTalk networkIDXID="w1901"BOOK="_idx" COLLECTION="nw41" TIDREF="i200"An AppleTalk network that is capable of supporting the AppleTalk Phase 2 extensions, such as zone lists and network ranges.See also IDREF="FM62114""AppleTalk Phase 2."RENDERAS="SECT1"ID="FM64249"Exterior Gateway ProtocolIDXID="w1902"BOOK="_idx" COLLECTION="nw41" TIDREF="i1405"(EGP) A protocol that exchanges network reachability information between autonomous systems. EGP is part of the TCP/IP protocol suite.Routers within each autonomous system are chosen to use EGP to talk to the outside world, usually over the Internet. These EGP routers are called exterior routers.The exterior routers become EGP neighbors. The EGP neighbors exchange information about the networks that can be reached within the neighbors' respective autonomous systems.See also IDREF="FM27700""Autonomous system."RENDERAS="SECT1"ID="FM67952"Expansion busIDXID="w1903"BOOK="_idx" COLLECTION="nw41" TIDREF="i1385"IDXID="w1904"BOOK="_idx" COLLECTION="nw41" TIDREF="i554"A common pathway between hardware devices. A bus connects the CPU to its main memory and the memory that resides on the control units of the peripheral devices. A bus allows you to transfer data from the motherboard to plug-in peripherals. An expansion bus allows you to expand your PC system using adapter cards by providing a data path from the adapter to the CPU.PAGENUM=101 ID="BP108"Expansion bus types includeMARK=BULLETIndustry Standard Architecture (ISA). An 8- and 16-bit bus that reaches speeds of 6 MHz and 8 MHz. The ISA design includes a buffering chip between the CPU bus and the ISA slot. This chip adds wait states to I/O to allow faster CPUs to accommodate ISA bus speeds. Extended Industry Standard Architecture (EISA). A 32-bit bus that is compatible with 8- and 16-bit products. The EISA slot speed is 8 MHz to maintain compatibility with ISA, but, because of its wider bus, EISA has faster data transfer rates.Another reason for EISA bus speed is the EISA bus design allows add-in boards to process independently of the CPU. That is, they have bus-mastering capabilities and can access the computer's memory and peripherals on their own without intervention from the CPU. Micro Channel. IBM's 32-bit bus for the PS/2 machines. Like ISA and EISA, the MCA bus is limited to 8- or 10-MHz speed.The MCA bus supports bus-mastering (direct communication with the computer's memory and peripherals without CPU involvement) and allows multiple processors and devices to share the single data bus.Peripheral Component Interconnect (PCI). A 32- or 64-bit bus based on local bus architecture. Local bus architecture design gives the PCI bus a direct data path to the CPU. This direct connection between the CPU and the local bus slots allows data transfers at the speed of the system clock, which can currently reach speeds of 66 MHz and sometimes 90 MHz.The PCI bus supports bus-mastering and allows ten peripherals such as video, LAN and SCSI devices to be integrated directly onto the local bus.PCI bus provides a throughput rate of 132Mbps, 16 times faster than ISA bus, and four times faster than the EISA bus. It is designed for high bandwidth applications such as multimedia.To provide compatibility with slower CPUs, the PCI bus slot also functions with ISA and EISA adapter cards. PAGENUM=102 ID="BP109"Video Electronics Standards Association (VESA). The VL-bus is VESA's standard 32-bit bus (upgradable to 64-bit). Based on the local bus architecture, the VL-bus provides a direct path from the CPU to peripherals such as video, disk, and network devices. The VL-bus supports bus-mastering and works with ISA and EISA buses. Personal Computer Memory Card International Association (PCMCIA). PCMCIA standardized credit-card sized modules for laptop and palm-top computers. THE PCMCIA I/O bus uses the local bus architecture.See also IDREF="FM30185""Local bus."RENDERAS="SECT1"ID="FM75406"External Entity objectIDXID="w1905"BOOK="_idx" COLLECTION="nw41" TIDREF="i1408"A leaf object that represents a non-native NDS object that has been imported into NDS or registered in NDS.NetWare Message Handling ServiceTM (NetWare MHS) uses External Entity objects to represent users from non-NDS environments and provides an integrated address book for sending mail.For example, if your messaging environment contains non-NetWare MHSTM messaging servers, such as SMTP hosts, SNADS nodes, or X.400 Message Transfer Agents, you might choose to add users and lists at these servers to your Directory database. You would add them as External Entity objects.Adding these objects to the Directory database as External Entity objects adds them to the address books of your messaging applications. So, when addressing messages, NetWare MHS users can choose non-NetWare MHS users and lists from a directory list.An External Entity object has an External Name property that specifies the native name that the External Entity is known by in its native messaging environment.An External Entity also has a Foreign E-mail Address property that specifies the user's mailbox in a foreign messaging system.See also IDREF="FM10590""NetWare MHS Services."PAGENUM=103 ID="BP110"FRENDERAS="SECT1"ID="FM77617"IDXID="w1906"BOOK="_idx" COLLECTION="nw41" TIDREF="i1427"
Failure handlingThe SFT III process that prevents system downtime caused by a single IDXID="w1907"BOOK="_idx" COLLECTION="nw41" TIDREF="i1638"
hardware failure in a NetWare server.With SFT III, if one NetWare server fails, its mirrored partner automatically takes over. This failure handling process is instantaneous, automatic, and transparent to NetWare workstations. NetWare users view a server failure as a simple routing change, although they might detect a slight pause when SFT III switches from the primary to the secondary server.Failure handling allows server operations to continue. For example, open files stay open during the switch from one server to the other.The following diagram and scenarios describe how SFT III failure handling works.LABEL="29" FLOAT="0"SFT III Failure-Handling ScenariosFILEREF="n41co50a.tif"PAGENUM=104 ID="BP111"RENDERAS="SECT2"Scenario 1: Hardware Fails in the Primary ServerMARK=BULLETThe secondary server displays a console message similar to the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"Primary server failed...this server is becoming the primary server.The secondary server notifies each workstation that the secondary server is now the primary server.Workstation packets are rerouted to the new primary (formerly the secondary) server.SFT III tracks disk blocks that change following the server's failure.After you resolve the problem and restart the server that failed, SFT III recognizes that the two servers are out of synchronization.The new primary server sends the changes over the mirrored server link to update the repaired server and to resynchronize the two servers.RENDERAS="SECT2"Scenario 2. Hardware Fails in the Secondary ServerMARK=BULLETThe primary server displays a console message similar to the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"Secondary server failed...this server is remaining the primary server.SFT III tracks disk blocks that change following the secondary server's failure.After you repair and bring up the secondary server, SFT III recognizes that the two servers are out of synchronization.The primary server sends the changes over the mirrored server link to update the secondary server and to resynchronize the two servers.PAGENUM=105 ID="BP112"RENDERAS="SECT2"Scenario 3: The Mirrored Server Link FailsMARK=BULLETThe secondary server notifies the primary server over the internet that the mirrored server link is down. If it does not get a response, it becomes the primary server. If the secondary server gets a response, it restarts itself, trying the active mirrored server link for up to one minute. If the active mirrored server link fails, the secondary server switches to an alternate mirrored server link, if one is installed.Certain SET parameters cause the secondary MSL to restart without first trying the active MSL. They include Secondary Server MSL Hardware Failure Recovery Option; Primary Server MSL Hardware Failure Recovery Option; Secondary Server MSL Consistency Error Recovery Option; and Primary Server MSL Consistency Error Recovery Option. These parameters should be changed only if you are running SFT III in a testing environment.SFT III tracks disk blocks that change following the failure.The primary server sends the changes over the mirrored server link in order to update the secondary server and resynchronize the two servers.Unless both servers have alternate MSL boards, there is no alternate mirrored server link, and a failure of the active mirrored server link leaves the secondary server in an unmirrored state.RENDERAS="SECT2"Scenario 4: Disk Failure with No SwitchoverMARK=BULLETIf either disk fails, the system may continue to run by routing all disk requests to the good disk. The user or group specified in the Server Failure Notification Name SET parameter is notified of the disk failure. The failed disk must be repaired or replaced.Notification that a disk has failed means the system is no longer fully redundant. If the remaining disk should fail before the first disk is repaired or replaced, system failure and loss of data will result.PAGENUM=106 ID="BP113"RENDERAS="SECT1"ID="FM97295"Fake rootIDXID="w1908"BOOK="_idx" COLLECTION="nw41" TIDREF="i1430"IDXID="w1909"BOOK="_idx" COLLECTION="nw41" TIDREF="i3875"A subdirectory that functions as a root directory, allowing you to assign users rights at the subdirectory level.Fake roots work with the NetWare DOS Requester, as well as with NetWare shells included with NetWare 2.2 and NetWare 3. Fake roots do not work for OS/2 clients. (Under OS/2, all mapped drives are roots, and search drives don't exist.)Some applications can't be run from subdirectories; they read files from and write files to the root directory. However, for security, you should not assign users rights at the root or volume directory level.NetWare allows you to map a drive to a fake root (a directory where rights can be assigned to users).Thus, to use an application that must be installed at the root, load the files in a subdirectory and designate it as a fake root directory in the login script using MAP ROOT.You can't use the DOS CD (change directory) command at the fake root to return to the original root. To change the fake root back to the original root, remap the drive.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"MAP" in Utilities Reference.See also IDREF="FM52521""Security."RENDERAS="SECT1"ID="FM38827"FAT(File Allocation Table) An index table that points to the disk areas where a file is located.See IDREF="FM79681""File Allocation Table."PAGENUM=107 ID="BP114"RENDERAS="SECT1"Fault toleranceIDXID="w1910"BOOK="_idx" COLLECTION="nw41" TIDREF="i1435"A means of protecting data by reconciling bad disk blocks or by providing data duplication. (See IDREF="FM93344""System Fault Tolerance.")Also, distributing the Directory database among several servers to provide continued authentication and access to object information should a server go down. (See IDREF="FM27324""NetWare Directory replica.")RENDERAS="SECT1"ID="FM79681"IDXID="w1911"BOOK="_idx" COLLECTION="nw41" TIDREF="i1449"
File Allocation Table(FAT) An index table that points to the disk areas where a file is located. Because one file may be in any number of blocks spread over the disk, the FAT links the file together.Each volume contains a FAT. The NetWare operating system divides each volume into disk allocation blocks that can be configured to 4, 8, 16, 32, or 64 KB. (All blocks on one volume are the same size.)NetWare stores files on the volume in these blocks. If a file consists of one or more blocks, the file may be stored in blocks that aren't adjacent.Entries in the FAT correspond to the blocks for that volume. The first entry in the FAT corresponds to the first block on that volume, the second entry corresponds to the second block, etc.The FAT is accessed from the DET. It is cached in server memory, allowing the server to quickly access the data.Turbo FAT index. When a file exceeds 64 blocks (and the corresponding number of FAT entries), NetWare creates a turbo FAT index to group together all FAT entries for that file.See also IDREF="FM24560""Turbo FAT index."RENDERAS="SECT1"File cachingIDXID="w1912"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"The use of NetWare server RAM to improve file access time.See IDREF="FM22916""Cache memory."PAGENUM=108 ID="BP115"RENDERAS="SECT1"File compressionIDXID="w1913"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"IDXID="w1914"BOOK="_idx" COLLECTION="nw41" TIDREF="i730"A means of allowing more data to be stored on server hard disks by compressing (packing) files that aren't being used.By enabling NetWare volumes to be compressed, you can effectively increase disk space up to 63%. For example, 600 MB of files on a volume can be compressed to as little as 222 MB.File compression is managed internally by the NetWare operating system. Users can flag their files or directories so they are compressed after being used, or flag them so they are never compressed.After compression is enabled, files flagged Immediate Compress (Ic) are compressed immediately; other files are automatically compressed when they haven't been accessed for a specific amount of time. Files are decompressed when a user accesses them again.In simplified terms, file compression works like this:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The file to be compressed is read and analyzed.A temporary file is built describing the original file.The system determines if any disk sectors are saved by compressing the file.The creation of the compressed file begins.After an error-free compressed version of the file is built, the original and compressed files are swapped.If a disk error or a power failure occurs during compression, the original file is retained.File compression is a background process that only minimally impacts server performance. However, we recommend running compression when the server is relatively idle.You can enable file compression during or after installing NetWare 4PAGENUM=109 ID="BP116". Once enabled, you cannot disable file compression without re-creating the volume. You can, however, temporarily suspend file compression using a SET command. If you suspend file compression, you may have many files to be compressed once you enable file compression. If so, to avoid server performance degradation, set parameters to compress files during hours that don't affect production. See also IDREF="FM85330""Attributes."RENDERAS="SECT1"File handleIDXID="w1915"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"A number used to refer to or identify a file.RENDERAS="SECT1"File indexingIDXID="w1916"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"The method of indexing FAT entries for faster access to large files.For example, if you want to go to block 128 of a file, file indexing allows you to go right to the block instead of scanning through the 127 previous blocks.NetWare 4 supports automatic file indexing after 64 blocks. The two levels of file indexing in NetWare 4 refer to the size of the table it uses to index the FAT.The first level indexes 64 to 1,023 blocks; the second level, 1,024 or more blocks.See also IDREF="FM79681""File Allocation Table."RENDERAS="SECT1"ID="FM51849"File lockingIDXID="w1917"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"The means of ensuring that a file is updated correctly before another user, application, or process can access the file.For example, without file locking, if two users attempt to update the same word processing file simultaneously, one user could overwrite the file update of the other user.See also IDREF="FM29327""Record locking"; IDREF="FM30179""Semaphore."PAGENUM=110 ID="BP117"RENDERAS="SECT1"File rightsRights that control what a trustee can do with a file.See IDREF="FM74455""Rights."RENDERAS="SECT1"File Scan rightIDXID="w1918"BOOK="_idx" COLLECTION="nw41" TIDREF="i1470"A file system right that grants the right to see the directory and file with the DIR or NDIR directory command.See also IDREF="FM74455""Rights."RENDERAS="SECT1"File serverA name used in previous NetWare versions for the computer that runs NetWare operating system software; now referred to as the NetWare server.See IDREF="FM34874""NetWare server."RENDERAS="SECT1"File sharingIDXID="w1919"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"A feature of networking that allows more than one user to access the same file at the same time.See also IDREF="FM52521""Security."RENDERAS="SECT1"ID="FM22177"File systemIDXID="w1920"BOOK="_idx" COLLECTION="nw41" TIDREF="i1477"(Formerly directory structure) The system the NetWare server uses to organize data on its hard disks. Each file is given a filename and stored at a specific location in a hierarchical filing system so that files can be located quickly.In previous NetWare versions, this concept was referred to as directory structure. The concept is now called file system to distinguish it from the Directory that is part of NDS.The NetWare server is divided into one or more volumes. Volumes are divided into directories containing files or subdirectories.The file system is analogous to an office filing system, as illustrated in the following figure.PAGENUM=111 ID="BP118"LABEL="30" FLOAT="0"Volumes, Directories, and FilesFILEREF="n40co76a.tif"IDXID="w1921"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"Volume. The highest level in the NetWare file system, created from logical partitions using INSTALL. A volume can reside on one hard disk, or it can span multiple hard disks.To a user, a volume appears much like a hard disk in a standalone system.You can store directories at the volume level. Storing files at this level is possible but, for security reasons, isn't recommended.IDXID="w1922"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"Directory. A place within a volume where you can store files or other directories. Directories within directories are called subdirectories.A directory can contain any number of files and subdirectories.IDXID="w1923"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"Files. Individual records that can be created in or copied to any level of the directory structure (except, in practice, the volume level).PAGENUM=112 ID="BP119"RENDERAS="SECT2"IDXID="w1924"BOOK="_idx" COLLECTION="nw41" TIDREF="i1068"IDXID="w1925"BOOK="_idx" COLLECTION="nw41" TIDREF="i3255"
Directory PathA file or directory is located by its path, which states where the directory or file is on a volume. The following figure shows how to specify a path. (Listing the server is optional.)LABEL="31" FLOAT="0"Directory Path ConventionsFILEREF="n40co77a.tif"Under DOS and OS/2, directory names and filenames contain one to eight characters, followed with an optional filename extension (See IDREF="FM42995""Filename extension.")If your network uses more than one client operating system, keep in mind the conventions of the different systems. For example, NetWare allows 255 characters in a directory path (counting the drive letter and delimiters), but DOS permits only 127 characters.Also, some applications restrict the number of characters in the directory path. For more information, check the application's documentation.RENDERAS="SECT2"Basic Netware Server DirectoriesWhen volume SYS: is created, it contains seven predefined directories:MARK=BULLETSYS:DELETED.SAV holds files that have been deleted until they are purged.SYS:ETC contains sample files to assist the network supervisor in configuring the server.SYS:LOGIN contains programs necessary for users to log in. A subdirectory, SYS:LOGIN/OS2, contains OS/2 login programs.PAGENUM=113 ID="BP120"SYS:MAIL is used by mail programs compatible with NetWare. (NetWare creates a subdirectory in SYS:MAIL for User object ADMIN.)If you upgrade from an earlier NetWare version, existing users still have subdirectories here, but their login script becomes a property of their User objects.If you create new users after upgrading, the new users do not have directories in SYS:MAIL.SYS:SYSTEM contains NetWare operating system files as well as NLM programs and NetWare utilities used for managing the network.SYS:PUBLIC allows general access to the network and contains NetWare utilities and programs for network users. A subdirectory, SYS:PUBLIC/OS2, contains NetWare utilities and programs for OS/2.SYS:DOC contains electronic versions of the NetWare manuals.RENDERAS="SECT2"Directory StructuresAll directories are organized in tree structures, but a directory structure can be flat with many directories coming off the volume, or it can be deep with several levels of directories.The following figure illustrates possible directory structures:PAGENUM=114 ID="BP121"LABEL="32" FLOAT="0"Flat and Deep Directory StructuresFILEREF="n40co78a.tif"The general principle is to keep directory structure clean and logical. Keeping the structure relatively flat (no more than five levels deep) generally increases usability.RENDERAS="SECT2"Directory TypesYou can create directories for both executable files and data files, depending on what types of directories best fit the needs of your network.Operating system directories. These store workstation operating system files.The number of DOS or other operating system directories you need depends on the number of different operating systems, versions, and workstation types on the network.Application directories. Although applications can be accessed from local drives, installing them on the network provides convenient access.Several structures are possible for application directories:MARK=BULLETCreate a separate volume for applications, with a separate directory for each application off the root. Make trustee assignments for each application. Then go into the system or profile login script and map a search drive to each application. PAGENUM=115 ID="BP122"The following figure shows this type of directory structure:LABEL="33" FLOAT="0"Application VolumeFILEREF="n40co79a.tif"Create a separate directory off volume SYS: for each application. Make trustee assignments for each application. Then go into the system or profile login script and map a search drive to each application. The following figure shows this type of directory structure.LABEL="34" FLOAT="0"Application Directory off Volume SYS:FILEREF="n40co80a.tif"Create a parent directory for applications, with subdirectories for each application. Make trustee assignments for each application. Then go into the system or profile login script and map a search drive to each application. The following figure shows this type of directory structure.LABEL="35" FLOAT="0"Parent Directory for ApplicationsFILEREF="n40co81a.tif"PAGENUM=116 ID="BP123"Create a parent directory for applications in SYS:PUBLIC.Because users generally have Read and File Scan rights in SYS:PUBLIC, you don't need to make trustee assignments or map a search drive. However, users can see and use all applications.Use this directory structure only if you want all users to have access to all applications. The following figure shows this type of directory structure.LABEL="36" FLOAT="0"Application Directory in SYS:PUBLICFILEREF="n40co82a.tif"Installing applications in SYS:PUBLIC isn't recommended (unless a subdirectory is created for each application).Upgrading a network is made more complicated by mixing NetWare utilities with application program files.An application file might have the same filename as a NetWare utility file or another application's program file. If so, one file overwrites the other because two files with the same filename can't coexist in a directory.Some applications write files to the root. For security reasons you don't want users working at the root level. Therefore, use MAP ROOT to map a drive to a fake root---a directory or subdirectory in which the user can be assigned rights (See IDREF="FM97295""Fake root.")IDXID="w1926"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"IDXID="w1927"BOOK="_idx" COLLECTION="nw41" TIDREF="i914"Data directories. These are work directories for groups and users to keep work files in. You can also create a directory to transfer files between directories on the network.Although data can be created and stored in a home or user directory, when data is stored in a user's directory, no other user (except network supervisors or managers assigned file rights) can access it.PAGENUM=117 ID="BP124"So, to allow users to share data, create work directories and make trustee assignments for groups or users who need access to these directories.IDXID="w1928"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"IDXID="w1929"BOOK="_idx" COLLECTION="nw41" TIDREF="i1681"IDXID="w1930"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"Home or 
username directories. To provide personal workspace for users, create home or username directories.You can create a parent directory in volume SYS: called HOME or USERS. Or, you can create a separate HOME or USERS volume. Then you can create a subdirectory for each user.The name of each subdirectory should be the username. Usernames can be up to 47 characters, but DOS displays only 8 characters in a one-level directory name. The following figure shows this type of directory structure.LABEL="37" FLOAT="0"Home or Username DirectoriesFILEREF="n40co83a.tif"Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"FILER," "BOOK="utlrfenu" COLLECTION="nw41"MAP," "BOOK="utlrfenu" COLLECTION="nw41"NLIST," "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN," and "BOOK="utlrfenu" COLLECTION="nw41"RENDIR" in Utilities Reference.Related DOS utilities: CD (Change Directory); DIR; MD (Make Directory); RD (Remove Directory). See your DOS manual.See also IDREF="FM45928""Directory"; IDREF="FM71720""Directory Entry Table"; IDREF="FM39775""Drive mapping"; IDREF="FM52521""Security."PAGENUM=118 ID="BP125"RENDERAS="SECT1"ID="FM61173"File Transfer ProtocolIDXID="w1931"BOOK="_idx" COLLECTION="nw41" TIDREF="i1478"(FTP) A set of control procedures to prevent errors in information transmitted between network stations. FTP is part of the TCP/IP protocol suite.The data is sent from one station to another in packets. Each packet includes a discrete number that is derived from the data that makes up the packet, according to a mathematical algorithm.The algorithm is applied to each data packet a second time when it arrives on the receiving end.If the number on the receiving end doesn't match the number included in the packet, the receiving station sends a signal to the transmitting station requesting that the packet be resent.RENDERAS="SECT1"ID="FM42995"Filename extensionIDXID="w1932"BOOK="_idx" COLLECTION="nw41" TIDREF="i1480"IDXID="w1933"BOOK="_idx" COLLECTION="nw41" TIDREF="i1403"The extension used after the period in filenames.Under the FAT system used by DOS and OS/2, filename extensions can be up to three characters in length. Under the High Performance File System (HPFS) used by OS/2, filename extensions aren't restricted to three characters. (See your OS/2 user guide.)Some extensions are reserved for special purposes or circumstances:MARK=BULLETThe .COM, .CMD, .EXE, or .BAT extensions enable a file to execute a command, program, or batch file (for example, AUTOEXEC.BAT).The .ERR, .DAT, or .NLM extensions indicate the file has a specific function. For example, an .ERR file contains an error log and an .NLM file contains an NLM.The .ASC, .BIN, .GIF, .DFX, or .RFT extensions identify a specific file format.The .C, .ASM, or .BAS extensions indicate specific programming languages.PAGENUM=119 ID="BP126"NetWare uses the following DOS filename extensions:MARK=BULLET.BAT---Executable batch file.COM---Executable command file.DAT---ASCII text file (usually).ERR---Error log file.EXE---Executable file.HLP---Help screens (F1 help) in a menu or graphical utility.MSG---Message file.OVL---Overlay file used with NetWare menu utilities.SYS---Operating system or driver fileNetWare also uses its own specific extensions:MARK=BULLET.001---Unicode table.DSK---NetWare server disk driver.LAN---NetWare server LAN driver.MSG---Text messages (for international NetWare versions).NCF---NetWare server executable batch file used to load modules and set the NetWare operating system configuration.NDS---NetWare Directory Services file.NLM---NetWare Loadable Module program.PDF---NetWare printer definition filePAGENUM=120 ID="BP127".Q---NetWare print job file.QDR---NetWare print queue definition directoryRENDERAS="SECT1"Foreign E-mail addressIDXID="w1934"BOOK="_idx" COLLECTION="nw41" TIDREF="i1425"IDXID="w1935"BOOK="_idx" COLLECTION="nw41" TIDREF="i1536"Specifies an object's mailbox that resides in a foreign E-mail system.For example, an NDS user can choose to have E-mail delivered to a UNIX machine that supports the SMTP messaging protocol. This user's SMTP address in the UNIX machine (the SMTP native name) is also the user's foreign E-mail address.An object can have only one foreign E-mail address.RENDERAS="SECT1"Foreign E-mail aliasIDXID="w1936"BOOK="_idx" COLLECTION="nw41" TIDREF="i1425"IDXID="w1937"BOOK="_idx" COLLECTION="nw41" TIDREF="i1538"Specifies an object's aliases as known in a foreign messaging system.A foreign E-mail alias is the return address value used when the NetWare MHS user sends E-mail to an X.400 user.For example, a NetWare MHS user (a user whose mailbox is located on an MHS Messaging Server) can have an X.400 alias---with an X.400 native name---so that X.400 users can use this alias to send mail to the MHS user.An object can have several foreign E-mail aliases, one for each type of foreign E-mail system.RENDERAS="SECT1"FormIn a NetWare printer command, the name and size of the paper used for a print job.See IDREF="FM14172""Printer form."PAGENUM=121 ID="BP128"RENDERAS="SECT1"FrameIDXID="w1938"BOOK="_idx" COLLECTION="nw41" TIDREF="i1573"A packet data format for a given media.Some media support multiple packet formats (frames), such as Ethernet 802.2, Ethernet 802.3, Ethernet II, Ethernet SNAP, token ring, or token ring SNAP.For NetWare 4, the default Ethernet frame type is 802.2.See also IDREF="FM81286""Ethernet configuration."RENDERAS="SECT1"ID="FM80125"FTP(File Transfer Protocol) A set of control procedures to prevent errors in information transmitted between workstations. FTP is part of the TCP/IP protocol suite.See IDREF="FM61173""File Transfer Protocol."PAGENUM=122 ID="BP129"GRENDERAS="SECT1"GatewayIDXID="w1939"BOOK="_idx" COLLECTION="nw41" TIDREF="i1592"A link between two networks.A gateway allows communication between dissimilar protocols (for example, NetWare and non-NetWare networks) using industry standard protocols such as TCP/IP, X.25, or SNA.RENDERAS="SECT1"ID="FM36715"Group objectIDXID="w1940"BOOK="_idx" COLLECTION="nw41" TIDREF="i1620"A leaf object that represents a grouping of several User objects, used to provide collective, rather than individual, network administration.For example, whenever electronic mail is sent to a Group object, or whenever a trustee assignment names a Group object, each user in the list is part of that action.You can create Group objects based on who uses the same applications, printers, or print queues; who performs similar tasks; or who has similar needs for information.You can use Group objects to simplify trustee assignments. For example, instead of repeating a trustee assignment for each user, you can create a Group object that lists the users and then grant the trustee assignment to the Group.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"FILER," "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN," and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.See also IDREF="FM57690""Effective rights"; IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Managing Group Objects" in Chapter 1 of Supervising the NetworkPAGENUM=123 ID="BP130"HRENDERAS="SECT1"ID="FM32530"HAM(Host Adapter Module) A driver component used to drive specific host adapter hardware in NPA.The HAM adapter drivers have a .HAM file extension.See IDREF="FM87820""NetWare Peripheral Architecture."RENDERAS="SECT1"HandleIDXID="w1941"BOOK="_idx" COLLECTION="nw41" TIDREF="i1631"A pointer used by a computer to identify a resource or feature.For example, a directory handle identifies a volume and a directory, such as SYS:PUBLIC.Other types of handles used to access NetWare 4 include file handles, video handles, request handles, device handles, and volume handles.RENDERAS="SECT1"ID="FM98858"HandshakingIDXID="w1942"BOOK="_idx" COLLECTION="nw41" TIDREF="i1633"The initial exchange between two data communication systems prior to and during data transmission to ensure proper data transmission.A handshake method (such as XON/XOFF) is part of the complete transmission protocol.A serial (asynchronous) transmission protocol might include the handshake method (XON/XOFF), baud rate, parity setting, number of data bits, and number of stop bits.See also IDREF="FM44412""Serial communication."PAGENUM=124 ID="BP131"RENDERAS="SECT1"ID="FM19745"Hard diskIDXID="w1943"BOOK="_idx" COLLECTION="nw41" TIDREF="i1634"A high-capacity magnetic storage device that allows a user to write and read data. Hard disks can be network or local workstation disks.Internal disks use channel 0 and external hard disks use channels 1 through 4.See also IDREF="FM20059""Data protection"; IDREF="FM58921""Disk driver"; IDREF="FM26878""Host Bus Adapter"; IDREF="FM23688""Partition (disk)."RENDERAS="SECT1"ID="FM19734"HashingA process that facilitates access to a file in a large volume by calculating the file's address both in cache memory and on the hard disk.See IDREF="FM91856" "Directory hashing."See also IDREF="FM22916""Cache memory."RENDERAS="SECT1"ID="FM52404"HBA(Host Bus Adapter) A board that acts as an interface between the host microprocessor and the disk controller.See IDREF="FM87820""NetWare Peripheral Architecture."RENDERAS="SECT1"HCSS(High Capacity Storage System) A system that increases data storage capacity by integrating an optical disc library into the NetWare file system.See IDREF="FM40870""High Capacity Storage System."RENDERAS="SECT1"HexadecimalIDXID="w1944"BOOK="_idx" COLLECTION="nw41" TIDREF="i1657"A base-16 numeric notation system used to specify addresses in computer memory.In hexadecimal notation, the decimal numbers 0 through 15 are represented by the decimal digits 0 through 9 and the alphabetic characters A through F (A = decimal 10, B = decimal 11, etc.).PAGENUM=125 ID="BP132"RENDERAS="SECT1"Hidden (H) attributeIDXID="w1945"BOOK="_idx" COLLECTION="nw41" TIDREF="i1664"A DOS and OS/2 attribute that hides a directory or file from the DOS or OS/2 DIR command and prevents the directory or file from being deleted or copied.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"ID="FM40870"High Capacity Storage SystemIDXID="w1946"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"(HCSS) A data storage system that extends the storage capacity of a NetWare server by integrating an optical disc library, or jukebox, into the NetWare file system.HCSS moves files between faster low-capacity storage devices (the server's hard disk) and slower high-capacity storage devices (optical discs in a jukebox).This process is transparent to the user; the file still appears to be stored on the file server.Users and programs can access files and directories on a jukebox using the same NetWare commands and function calls used to access them from the hard disk.HCSS uses rewritable optical discs. By using rewritable disks, data can be repeatedly written and erased. An optical disc can be one-sided or two-sided.RENDERAS="SECT2"Data MigrationIDXID="w1947"BOOK="_idx" COLLECTION="nw41" TIDREF="i2460"IDXID="w1948"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"
 and DemigrationIDXID="w1949"BOOK="_idx" COLLECTION="nw41" TIDREF="i995"IDXID="w1950"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"HCSS uses free space on the server's hard disk to temporarily cache the jukebox's most active files.When space on the hard disk reaches a preconfigured capacity, the cache's least active files are moved to optical discs. This process is known as data migration.When a user requests a file and that file was migrated to an optical disc, HCSS copies the file from the jukebox onto the server's hard disk. This process, known as demigration, allows users to access their least active files in the same manner as their most active files, with only a slight delay in response time.PAGENUM=126 ID="BP133"The path name of a file remains the same whether the file resides on the hard disk or on optical disc.The following figure demonstrates the processes of migration and demigration.LABEL="38" FLOAT="0"Migration and Demigration of the Requested FileFILEREF="n41co29a.tif"Data migration and demigration allow HCSS to optimize the use of the server's storage devices. Migration is performed on a file-by-file basis, according to the amount of hard disk space used (capacity threshold) and the last time a file was accessed (least recently used).MARK=BULLETCapacity threshold is the percentage of the server's hard disk that can be used before HCSS starts migrating files from the hard disk to the jukebox.Least recently used is the rule that determines which files are moved from the server's hard disk to the jukebox. The least active files are the first moved.RENDERAS="SECT2"IDXID="w1951"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"IDXID="w1952"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"
HCSS Directory ManagementAn HCSS directory is a file system directory that logically groups one or more optical discs and its associated files. An HCSS directory resides on the NetWare volume that is associated with the directory's jukebox.The network supervisor can create one or more HCSS directories for each jukebox.The network supervisor assigns unique labels to each side of each optical disc, and then assigns each optical disc to an HCSS domain PAGENUM=127 ID="BP134"directory. Once assigned, each label appears as a media-label directory within the HCSS directory.The following figure shows the association between labeled media (magneto-optical media) and the media-label directories.LABEL="39" FLOAT="0"Media Grouped into HCSS DirectoriesFILEREF="n41co48a.tif"An HCSS directory's contents can be viewed using any directory listing command (such as the DOS DIR or NetWare NDIR commands).Users can access and manipulate HCSS first-level subdirectories the same way they access any other NetWare directory, except that users can't create or delete an HCSS first-level subdirectory.Access control rights are assigned to HCSS directories in the same way they are for other NetWare directories.See also IDREF="FM55003""Data migration."PAGENUM=128 ID="BP135"RENDERAS="SECT1"Home directoryIDXID="w1953"BOOK="_idx" COLLECTION="nw41" TIDREF="i1681"IDXID="w1954"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"A private network directory that the network supervisor can create for a user. Users' login scripts should contain a drive mapping to their home directories.RENDERAS="SECT1"Hop countIDXID="w1955"BOOK="_idx" COLLECTION="nw41" TIDREF="i1688"The number of cable segments a message packet passes through on the way to its destination on a network or internetwork.The destination network can be no more than 16 hops from the source.The server utilities DISPLAY NETWORKS, DISPLAY SERVERS, and TRACK ON show how many hops other recognized networks are from the server router.They also show the number of ticks (1/18 of a second) it takes for the message packet to reach its destination network.See also IDREF="FM23688""Partition (disk)."RENDERAS="SECT1"ID="FM71612"HostIDXID="w1956"BOOK="_idx" COLLECTION="nw41" TIDREF="i1696"IDXID="w1957"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"A NetWare server from which you run SBACKUP. A storage device and a storage device controller are attached to it.See also IDREF="FM24312""Backup"; IDREF="FM46936""Target."RENDERAS="SECT1"ID="FM32299"Host Adapter Module(HAM) The driver component used to drive specific host adapter hardware in NPA.See IDREF="FM87820""NetWare Peripheral Architecture."PAGENUM=129 ID="BP136"RENDERAS="SECT1"ID="FM26878"Host Bus AdapterIDXID="w1958"BOOK="_idx" COLLECTION="nw41" TIDREF="i1693"(HBA) A SCSI adapter board or disk controller that adds a bus through which peripheral devices (such as hard disks, tape drives, and CD-ROM drives) are connected to the computer.These devices typically have embedded controllers.See also IDREF="FM19745""Hard disk"; IDREF="FM83109""SCSI bus."RENDERAS="SECT1"ID="FM95725"Hot FixIDXID="w1959"BOOK="_idx" COLLECTION="nw41" TIDREF="i1700"A method NetWare uses to ensure that data is stored safely. Data blocks are redirected from faulty blocks on the server's disk to a small portion of disk space set aside as the Hot FixTM Redirection Area.Once the operating system records the address of the defective block in a section of the Hot Fix area reserved for that purpose, the server doesn't attempt to store data in defective blocks.By default, 2% of a disk partition's space is set aside as the Hot Fix Redirection Area.Hot Fix is always active unless the disk fails and is inoperative, or unless the redirection area is full. Hot Fix, together with read-after-write verification, enables a hard disk to maintain data integrity.See also IDREF="FM20059""Data protection."RENDERAS="SECT1"ID="FM27825"HubIDXID="w1960"BOOK="_idx" COLLECTION="nw41" TIDREF="i1734"A device that modifies transmission signals, allowing the network to be lengthened or expanded with additional workstations.Two kinds of hubs exist:MARK=BULLETActive hubs. Amplify transmission signals in network topologies. Use active hubs to add workstations to a network or to extend the cable distance between stations and the server.Passive hubs. PAGENUM=130 ID="BP137"Used in certain network topologies to split a transmission signal, allowing additional workstations to be added. Passive hubs can't amplify the signal, so it must be cabled directly to a station or to an active hub.PAGENUM=131 ID="BP138"IRENDERAS="SECT1"ICMP(Internet Control Message Protocol) A protocol in the TCP/IP suite that sends packets containing information about network failures, such as inoperative nodes and gateways, or congestion at a gateway.See IDREF="FM97442""Internet Control Message Protocol."RENDERAS="SECT1"IDEA hard disk drive standard interface.IDREF="FM99005""Integrated Drive Electronics."RENDERAS="SECT1"Identifier variablesIDXID="w1961"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"IDXID="w1962"BOOK="_idx" COLLECTION="nw41" TIDREF="i4751"Variables used in login scripts that allow you to enter a variable (such as LOGIN_NAME) in a login script command, rather than specific information (such as RICHARD).See IDREF="FM23712""Login scripts."RENDERAS="SECT1""IDXID="w1963"BOOK="_idx" COLLECTION="nw41" TIDREF="i1982"
I'm Alive" packetDiagnostic packets SFT III servers send back and forth over the internetwork connection to check each other's status.Each SFT III server sends an "I'm alive" packet to the other SFT III server over the IPX cable at a rate of 18 times per second. These packets act as a backup communications check for the mirrored server link. A network analyzer attached to the LAN segment between the two SFT III servers detects many "I'm alive" packets per minute. However, the extra traffic generated by these diagnostic packets should not affect network performance.PAGENUM=132 ID="BP139"RENDERAS="SECT1"Immediate Compress (Ic) attributeIDXID="w1964"BOOK="_idx" COLLECTION="nw41" TIDREF="i1764"A file system attribute that causes files to be compressed as soon as the operating system can do so. The operating system doesn't wait for a specific event (such as a time delay) before compressing the file.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"Indexed (I) attributeIDXID="w1965"BOOK="_idx" COLLECTION="nw41" TIDREF="i1786"A status flag set automatically when a file exceeds a set size, indicating that the file is indexed for fast access.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"ID="FM13738"Inherited Rights FilterIDXID="w1966"BOOK="_idx" COLLECTION="nw41" TIDREF="i1804"(IRF) A list of rights created for every file, directory, and object. The IRF controls the rights that a trustee can inherit from parent directories and container objects. By default, the IRF allows every right to be inherited from the parent directory or container object. The IRF cannot grant rights, it can only allow or revoke rights.To allow a right, the right must exist in the parent directory or container object and the IRF.To revoke a right, the right must exist in the parent directory or container object and then be removed from the IRF.The IRF is ignored whenever a trustee has an explicit trustee assignment to that file, directory, or object.PAGENUM=133 ID="BP140"FILEREF="n41co13a.tif"Use this figure as a reference for IDREF="FM41221"Figure 40 and IDREF="FM65188"Figure 41. Together, they show how a trustee assignment flows through the IRF to determine which rights the trustee can exercise within a file, directory, or object.IDXID="w1967"BOOK="_idx" COLLECTION="nw41" TIDREF="i1802"IDREF="FM41221"Figure 40 illustrates the effective rights of user Nick, who is assigned object and property rights to the SALES object. Nick is also granted trustee rights to the PROJECTS directory. Nick's trustee assignment to Organizational Unit SALES grants him BCDR (Browse, Create, Delete, Rename) object rights.Because Nick doesn't have a trustee assignment to any of the three objects within the SALES container, Nick's effective rights to those objects are inherited from SALES and must pass through the IRF of each object.PAGENUM=134 ID="BP141"LABEL="40" FLOAT="0"IDXID="w1968"BOOK="_idx" COLLECTION="nw41" TIDREF="i1804"ID="FM41221"Inherited Rights FilterFILEREF="n41co75a.tif"Because Nick has an explicit trustee assignment to SALES, the IRF for SALES has no affect on his rights.The IRF for MANAGERS allows all rights to pass through, so Nick's rights to MANAGERS are the same as his rights to SALES. However, the IRFs for SPREADSHEET and ACCOUNTING block rights from SALES, so Nick doesn't have the same rights for those objects.If Nick is granted an explicit trustee assignment to any objects below SALES, the IRF for those objects is ignored and his new assignment determines his effective rights.IDREF="FM65188"Figure 41 lists the results of these rights flowing through the IRFs.PAGENUM=135 ID="BP142"LABEL="41" FLOAT="0"ID="FM65188"Effective Rights ChartFILEREF="n41co91a.tif"Only rights assigned for all properties can be inherited. Rights assigned to selected properties can't be inherited. (See IDREF="FM74455""Rights.")RENDERAS="SECT2"Blocking the Supervisor Object RightThe IRF of an object and its properties can block the Supervisor object right. This allows distributed management of the Directory tree.However, NetWare utilities don't allow you to block the Supervisor object right unless an object, including itself, is already granted the Supervisor right to that object. This helps to prevent cutting off Supervisor-level access to a part of the Directory tree.Any object can be assigned as a trustee to an object, including to itself. But unless the trustee assignment is a User object, blocking the Supervisor object right with the IRF still cuts off that object from future control because you can only log in as a User object.Because the Supervisor right to objects and properties can be blocked, you should also grant a trustee all other rights.PAGENUM=136 ID="BP143"For example, don't grant only the Supervisor right. Even though that right allows or implies all rights to an object, if the Supervisor right is blocked, the trustee is left with no rights.Instead, grant all rights to the trustees, so that if Supervisor is blocked by an IRF, the trustee still has Browse, Rename, Create, and Delete rights.To change the IRF of an object, you must have at least the Write property right to the ACL property of that object.As with previous versions of NetWare, the Supervisor right cannot be blocked in the file system. A trustee who has the Supervisor right in the root directory of a volume has the Supervisor right to the entire volume, and it cannot be blocked with an IRF.RENDERAS="SECT2"Changing the IRFThe IRF for any file, directory, or object is part of the access control list (ACL) for that file, directory, or object.To change the IRF of an object, you must have at least the Write property right to the ACL property of that object.To change the IRF of a file or directory, you must have the Access Control right to that file or directory.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"FILER," "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN," "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator," and "BOOK="utlrfenu" COLLECTION="nw41"RIGHTS" in Utilities Reference.See also IDREF="FM57690""Effective rights"; IDREF="FM52521""Security."RENDERAS="SECT1"Input/Output EngineThe part of the SFT III operating system that handles physical processes, such as network and disk I/O, hardware interrupts, device drivers, timing, and routingSee IDREF="FM76680""IOEngine."PAGENUM=137 ID="BP144"RENDERAS="SECT1"ID="FM99005"IDXID="w1969"BOOK="_idx" COLLECTION="nw41" TIDREF="i42"
Integrated Drive ElectronicsIDXID="w1970"BOOK="_idx" COLLECTION="nw41" TIDREF="i1843"IDXID="w1971"BOOK="_idx" COLLECTION="nw41" TIDREF="i1634"(IDE) A hard disk drive standard interface. The IDE integrates controller electronics onto the drive. The controller connects to a paddleboard that may be external to, or on, the motherboard. The paddleboard then interfaces with the bus to the CPU.Unlike the IDE drive, the SCSI drive has a separate host bus adapter (HBA) instead of the paddleboard. The HBA interfaces with the bus to the CPU.You can identify an IDE bus by its 40-pin connector, as opposed to a SCSI bus, which has a 50-pin connector. See also IDREF="FM19745""Hard disk"RENDERAS="SECT1"Internal network numberIDXID="w1972"BOOK="_idx" COLLECTION="nw41" TIDREF="i1857"IDXID="w1973"BOOK="_idx" COLLECTION="nw41" TIDREF="i3015"A logical network number that identifies an individual NetWare 3 or NetWare 4 server.On IPX networks the internal network number must also be different from the IPX external network number.See also IDREF="FM16357""IPX internal network number"; IDREF="FM35125""IPX external network number."RENDERAS="SECT1"International use of NetWare 4.1IDXID="w1974"BOOK="_idx" COLLECTION="nw41" TIDREF="i1862"IDXID="w1975"BOOK="_idx" COLLECTION="nw41" TIDREF="i2046"The adaptation of NetWare 4 for use with multiple languages.The NetWare 4 operating system, NLM programs, and utilities use English as the default language but can be set to several other languages.You can have NLM programs running in different languages at the same time.The formats for expressing dates, times, and numbers also change across languages, and sometimes change across locales within a given language area.In NetWare 4PAGENUM=138 ID="BP145", you can configure certain local formats through INSTALL.NLM. You specify the formats when installing the NetWare server, but you can reconfigure these formats with INSTALL.NLM while the server is running.You can configure the following information:MARK=BULLETDateTimeCurrencySorting tablesUpper case tablesSupported filename charactersThe following are some formats for various locales:COLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="6*"COLNAME=3 COLWIDTH="6*"COLNAME=4 COLWIDTH="6*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"LocationCOLNAME=2 ROTATE="0" MOREROWS="0"DateCOLNAME=3 ROTATE="0" MOREROWS="0"TimeCOLNAME=4 ROTATE="0" MOREROWS="0"NumberVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"USACOLNAME=2 ROTATE="0" MOREROWS="0"06/19/94COLNAME=3 ROTATE="0" MOREROWS="0"8:37:00 PMCOLNAME=4 ROTATE="0" MOREROWS="0"12,345.67COLNAME=1 ROTATE="0" MOREROWS="0"UKCOLNAME=2 ROTATE="0" MOREROWS="0"19/06/94COLNAME=3 ROTATE="0" MOREROWS="0"20:37:00COLNAME=4 ROTATE="0" MOREROWS="0"12,345.67COLNAME=1 ROTATE="0" MOREROWS="0"FranceCOLNAME=2 ROTATE="0" MOREROWS="0"19.06.94COLNAME=3 ROTATE="0" MOREROWS="0"20:37:00COLNAME=4 ROTATE="0" MOREROWS="0"12 345,67COLNAME=1 ROTATE="0" MOREROWS="0"GermanyCOLNAME=2 ROTATE="0" MOREROWS="0"19.06.94COLNAME=3 ROTATE="0" MOREROWS="0"20:37:00COLNAME=4 ROTATE="0" MOREROWS="0"12.345,67RENDERAS="SECT2"Languages SupportedNetWare 4 supports the following languages:MARK=BULLETGermanFrenchItalianSpanishPAGENUM=139 ID="BP146"You can set the language for the following:MARK=BULLETServerMessage filesConsole keyboardRENDERAS="SECT2"Setting the Language of the ServerYou must set the server language when loading SERVER.EXE. Setting the language later requires you to reboot the NetWare server. The server language is determined by the SERVER.MSG file. See "BOOK="superenu" COLLECTION="nw41"Setting a Server's Language" in Chapter 7 of Supervising the Network. RENDERAS="SECT2"IDXID="w1976"BOOK="_idx" COLLECTION="nw41" TIDREF="i2046"
Setting the Language of the Message FilesYou must specify the language you want NLM messages to be displayed in. To set the language for the message file, use the LANGUAGE.NLM.You can change the language for NLM messages anytime. It is not necessary to reboot the server. See "BOOK="superenu" COLLECTION="nw41"Specifying a Language for an NLM" in Chapter 7 of Supervising the Network.RENDERAS="SECT2"IDXID="w1977"BOOK="_idx" COLLECTION="nw41" TIDREF="i2046"
Setting the Language of the Console KeyboardSet the server keyboard type by loading KEYB.NLM and executing theMOREINFO="NONE" KEYB console command. You can change the keyboard type anytime. It is not necessary to reboot the server. See "BOOK="superenu" COLLECTION="nw41"Changing the Server Keyboard Type" in Chapter 7 of Supervising the Network.PAGENUM=140 ID="BP147"RENDERAS="SECT1"ID="FM97442"IDXID="w1978"BOOK="_idx" COLLECTION="nw41" TIDREF="i1865"
Internet Control Message Protocol(ICMP) A protocol in the TCP/IP suite that sends packets containing information about failures on the network such as inoperative nodes and gateways, and congestion at a gateway.IP software interprets and acts on an ICMP message. Because an ICMP message might need to travel across several networks to reach its destination, it is encapsulated in the data portion of an IP datagram.See also IDREF="FM32350""Internet Protocol"; IDREF="FM82397""TCP/IP."RENDERAS="SECT1"ID="FM32350"Internet ProtocolIDXID="w1979"BOOK="_idx" COLLECTION="nw41" TIDREF="i1869"(IP) The network layer protocol of the TCP/IP suite of protocols. IP enables dissimilar nodes in a heterogenous environment to communicate with one another.See also IDREF="FM82397""TCP/IP."RENDERAS="SECT1"ID="FM24537"InternetworkIDXID="w1980"BOOK="_idx" COLLECTION="nw41" TIDREF="i1877"Two or more networks connected by a router. Each network has a unique network number.Users on an internetwork can use the resources (files, printers, hard disks) of all connected networks, provided they have security clearance.See also IDREF="FM86375""Router"; IDREF="FM35125""IPX external network number."RENDERAS="SECT1"InteroperabilityIDXID="w1981"BOOK="_idx" COLLECTION="nw41" TIDREF="i1879"The ability to use products from different vendors within the same system.For example, Novell ODINSUP interface allows LAN Manager, LAN Server, or other NDS protocols to co-exist with ODI on a network.Communication protocols, such as IP or AFP, can be used in ODI to process information from the network without the user having to know each protocol's required method of packet transmission.PAGENUM=141 ID="BP148"Interoperability also means that an application running on different platforms (such as Macintosh or UNIX) can share files.See also IDREF="FM33588""Open Data-Link Interface"; IDREF="FM19164""ODINSUP."RENDERAS="SECT1"Interrupt modeIDXID="w1982"BOOK="_idx" COLLECTION="nw41" TIDREF="i1881"IDXID="w1983"BOOK="_idx" COLLECTION="nw41" TIDREF="i3496"A printer configuration option through which the data port sends a signal, or interrupt, to the port driver (NPRINTER) when it is ready to accept another character to be transmitted to the printer. The interrupt instructs the CPU to suspend its other processing activities to service the needs of the port in question.In past releases of NetWare, using interrupt mode was faster than the alternative polled mode. However, the enhanced performance of NPRINTER for NetWare 4 makes polled mode considerably faster than before. In most instances, users see little difference in performance. Also, using interrupt mode has the disadvantage of possible interrupt conflicts among different devices attempting to access the same processor. See also IDREF="FM52438""Polled mode."RENDERAS="SECT1"ID="FM76680"IDXID="w1984"BOOK="_idx" COLLECTION="nw41" TIDREF="i1902"
IOEngine(Input/Output Engine) The part of the SFT III operating system that handles physical processes, such as network and disk I/O, hardware interrupts, device drivers, timing, and routing.SFT III is split into two parts: the IOEngine and the MSEngine (Mirrored Server Engine). The IOEngine routes packets between the network and the MSEngine. To network workstations, the IOEngine appears as a standard NetWare router or bridge (making the SFT III server at least two hops away from any other router or workstation). The primary server and the secondary server each have an IOEngine, but they share the same MSEngine.PAGENUM=142 ID="BP149"Because the IOEngines are not mirrored, NLM programs and applications that directly interface with hardware, such as NPRINTER.NLM, are not mirrored. Hardware-related applications and NLM programs must be installed in the IOEngines on both the primary and secondary server.LABEL="42" FLOAT="0"ID="FM60796"IOEngine and MSEngineFILEREF="n41co51a.tif"RENDERAS="SECT1"ID="FM24770"IP addressIdentifies the network to which the host server is attached. The address is normally in four segments, each separated by a period (for example, 87.34.53.12). Individual numbers must be between 0 and 255.RENDERAS="SECT1"IP tunnelingIDXID="w1985"BOOK="_idx" COLLECTION="nw41" TIDREF="i1918"A method by which two or more IPX or AppleTalk networks exchange packets through an IP internetwork.The tunnel sends each IPX or AppleTalk packet across the IP internetwork by encapsulating it in a User Datagram Protocol (UDP) datagram.The tunnel driver at the destination removes the UDP header from each incoming packet and passes it through the ODI to IPX or AppleTalk.PAGENUM=143 ID="BP150"RENDERAS="SECT1"ID="FM16854"IPXIDXID="w1986"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"(Internetwork Packet Exchange) A Novell communication protocol that sends data packets to requested destinations (such as workstations or servers).IPX allows packet addressing within a single network, or in an internetwork environment. (That is, two or more networks connected by a router, where each network has a unique IPX external network number.)Through IPX, incoming data packets are directed to the proper area within the operating system of the workstation or NetWare server.IPX provides services to help other network-aware programs in their network data-transmission process.The NetWare DOS Requester prepares data packets in a form understandable to the intended destination before handing them to IPX.The IPXODI.COM file then uses the services of a LAN driver routine to control the station's network board for data delivery.Thus, IPX allows data packets to be sent and received through physically different networks and workstations.See also IDREF="FM34819""Communication protocols"; IDREF="FM24537""Internetwork"; IDREF="FM65595""IPXODI"; IDREF="FM41878""LAN driver"; IDREF="FM70203""NETX"; IDREF="FM33588""Open Data-Link Interface."RENDERAS="SECT1"ID="FM35125"IPX external network numberIDXID="w1987"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1988"BOOK="_idx" COLLECTION="nw41" TIDREF="i3015"IDXID="w1989"BOOK="_idx" COLLECTION="nw41" TIDREF="i1412"A network number that uniquely identifies a network cable segment.An IPX external network number is a hexadecimal number, one to eight digits (1 to FFFFFFFE). The number is arbitrary, and is assigned when the IPX protocol is bound to a network board in the server.You can bind IPX with multiple frame types to the same network board. For example, the NetWare 4 installation utility can install both Ethernet Raw 802.3 and IEEE 802.2 frame types as defaults and bind the IPX protocol stack to each. PAGENUM=144 ID="BP151"Both frame types are represented as logical IPX networks, and the IPX router, which is internal to the operating system, routes packets between the two logical networks. This means that each frame type requires its own unique logical IPX external network number, even though both frame types are bound to the same network board and physical cable segment.The terms network number and network address are sometimes used to refer to the IPX external network number.See also IDREF="FM16357""IPX internal network number"; IDREF="FM70179""IPX internetwork address"; IDREF="FM97740""Network numbering."RENDERAS="SECT1"ID="FM16357"IPX internal network numberIDXID="w1990"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1991"BOOK="_idx" COLLECTION="nw41" TIDREF="i3015"A logical network number that identifies an individual NetWare server. The IPX internal network number is a hexadecimal number, one to eight digits (1 to FFFFFFFE), and is assigned to the server during installation.Each server on a network must have a unique IPX internal network number. The IPX internal network number of any node must also be different from any IPX external network number on the internetwork.In earlier versions of NetWare, the IPX internal network number was referred to as the internal network number.An internal network (used in NetWare 3 and NetWare 4) is a logical network that routes packets to the physical networks that a NetWare server is attached to.See also IDREF="FM78770""AUTOEXEC.NCF"; IDREF="FM35125""IPX external network number."RENDERAS="SECT1"ID="FM70179"IPX internetwork addressIDXID="w1992"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"A 12-byte number (represented by 24 hexadecimal characters) divided into three parts, illustrated in the following figure:PAGENUM=145 ID="BP152"LABEL="43" FLOAT="0"IPX Internetwork AddressFILEREF="n40co86a.tif"The first part is the 4-byte (8-character) IPX external network number. The second part is the 6-byte (12-character) node number. The third part is the 2-byte (4-character) socket number. Typically, the example address is written: AAAAAAAA: 00001B1EA1A1; 0451.(The leading zeros in the node number can be eliminated.) See also IDREF="FM35125""IPX external network number"; IDREF="FM74415""Node number"; IDREF="FM10425""Socket."RENDERAS="SECT1"ID="FM65595"IPXODI(Internetwork Packet Exchange Open Data-Link Interface) A module that takes the workstation requests the DOS Requester has determined are for the network, packages them with transmission information (such as their destination), and transfers them to the LSL.IPXODI requires that each packet has an initialized header. The header specifies information that targets network delivery, announcing where the packet came from, where it's going, and what happens after delivery.Because IPXODI transmits data packets as datagrams (self-contained packages that move independently from source to destination), it can only deliver the packets on a best-effort basis. To guarantee delivery of packets, use SPX.See also IDREF="FM16854""IPX"; IDREF="FM12535""Link Support Layer"; IDREF="FM21900""NetWare DOS Requester"; IDREF="FM43851""SPX."JRENDERAS="SECT1"PAGENUM=146 ID="BP153"JukeboxIDXID="w1993"BOOK="_idx" COLLECTION="nw41" TIDREF="i2003"A high-capacity storage device, sometimes called an optical disc library, that uses an autochanger mechanism to mount and dismount optical discs as they are needed.A jukebox typically contains one to four optical disc drives. A picker rotates, flips, and transports disks to and from the storage slots, drives, and the mail slot. The mail slot is the location in the jukebox used to insert and remove the optical disc cartridge.See also IDREF="FM40870""High Capacity Storage System."RENDERAS="SECT1"Jumper blockIDXID="w1994"BOOK="_idx" COLLECTION="nw41" TIDREF="i2004"A group of jumper pins that can be connected (jumpered) or left unconnected to make hardware configuration settings on a circuit board.LRENDERAS="SECT1"PAGENUM=147 ID="BP154"ID="FM18846"LAN(LAN) A network located within a small area or common environment, such as in a building or a building complex.See also IDREF="FM30129""Wide area network."RENDERAS="SECT1"ID="FM41878"LAN driverIDXID="w1995"BOOK="_idx" COLLECTION="nw41" TIDREF="i2036"IDXID="w1996"BOOK="_idx" COLLECTION="nw41" TIDREF="i1226"IDXID="w1997"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"An NLM that interfaces with a network board. A LAN driver serves as a link between a station's operating system and the physical network parts.NetWare 4 is designed for LAN drivers written to the Open Data-Link Interface (ODI) specification. Under this specification, the LAN driver is more specifically referred to as the a Multiple Link Interface Driver (MLID).ODI drivers connect directly to the ODI model's LSL, which serves as an intermediary between the drivers and the communication protocols.NetWare LAN drivers have a .LAN filename extension. See also IDREF="FM12535""Link Support Layer"; IDREF="FM33398""Multiple Link Interface Driver"; IDREF="FM68484""NetWare Loadable Module"; IDREF="FM33588""Open Data-Link Interface."RENDERAS="SECT1"ID="FM31073"Large Internet PacketIDXID="w1998"BOOK="_idx" COLLECTION="nw41" TIDREF="i2067"(LIP) A functionality that allows the maximum size of internetwork packets to be increased. (Formerly, the maximum size was 576 bytes.)In NetWare versions earlier than NetWare 4, the workstation initiated a negotiation with the NetWare server to determine an acceptable packet size.If, during this negotiation, the server detected a router between it and the station, the server limited the maximum packet size to 576 bytes.PAGENUM=148 ID="BP155"However, some network architecture, such as Ethernet and token ring, support packets larger than 576 bytes.Thus, in NetWare 4, LIP allows the workstation to determine the packet size based on the maximum size supported by the router. LIP functionality is implemented for DOS clients through the station's NET.CFG file.See also "BOOK="ws_d2enu" COLLECTION="nw41"Configuring for Large Internet Packet" in NetWare Client for DOS and MS Windows Technical Reference.RENDERAS="SECT1"Leaf objectsIDXID="w1999"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"IDXID="w2000"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"Objects that don't contain any other objects, located at the end of a branch in the Directory tree.See also IDREF="FM13600""Object"; "BOOK="getstenu" COLLECTION="nw41"Organizing Objects into a Logical Hierarchy" in Chapter 5 of Introduction to NetWare Directory Services.RENDERAS="SECT1"ID="FM63052"Link stateIDXID="w2001"BOOK="_idx" COLLECTION="nw41" TIDREF="i2114"IDXID="w2002"BOOK="_idx" COLLECTION="nw41" TIDREF="i3885"A routing algorithm that builds and maintains a logical map of the entire network.A link state router accomplishes this by sending a packet containing information about all its links---connections to networks and other routers---to all other link state routers on the network. This process is known as flooding. Each router uses this information to build the network map.When each link state router has the same view (map) of the network, the network is said to have converged. Link state routers multicast their link information only when a change occurs in a route or service.See also IDREF="FM64684""NetWare Link Services Protocol"; IDREF="FM28062""Open Shortest Path First."RENDERAS="SECT1"ID="FM12535"Link Support Layer(LSL) An implementation of theODI specification that serves as an intermediary between the NetWare server's LAN drivers and the communication protocols, such as IPX, AFP, or TCP/IP.PAGENUM=149 ID="BP156"The LSL allows one network board to service several communications protocol stacks. It also allows several network boards to service the same protocol stack.See also IDREF="FM33588""Open Data-Link Interface."RENDERAS="SECT1"LIP(Large Internet Packet) A functionality that allows the maximum size of internetwork packets to be increased.See IDREF="FM31073""Large Internet Packet."RENDERAS="SECT1"Loadable moduleA program you can load and unload from a server or a workstation while the attendant operating system is running. Two common types are NLM programs and Virtual Loadable ModuleTM (VLM) programs.See IDREF="FM68484""NetWare Loadable Module"; IDREF="FM28012""Virtual Loadable Module."RENDERAS="SECT1"ID="FM72737"Loading and unloadingIDXID="w2003"BOOK="_idx" COLLECTION="nw41" TIDREF="i4670"IDXID="w2004"BOOK="_idx" COLLECTION="nw41" TIDREF="i2157"IDXID="w2005"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"IDXID="w2006"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"
 The process of linking and unlinking NLM programs to the NetWare operating system.NLM programs can be loaded and unloaded while NetWare is running. For precautions to take before unloading a disk or LAN driver, see "BOOK="utlrfenu" COLLECTION="nw41"UNLOAD" in Utilities Reference.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"LOAD" and "BOOK="utlrfenu" COLLECTION="nw41"UNLOAD" in Utilities Reference.See also IDREF="FM68484""NetWare Loadable Module."RENDERAS="SECT1"ID="FM88066"Local area networkIDXID="w2007"BOOK="_idx" COLLECTION="nw41" TIDREF="i2161"(LAN) A network located within a small area or common environment, such as in a building or a building complex.See also IDREF="FM30129""Wide area network."PAGENUM=150 ID="BP157"RENDERAS="SECT1"ID="FM30185"Local busIDXID="w2008"BOOK="_idx" COLLECTION="nw41" TIDREF="i2162"IDXID="w2009"BOOK="_idx" COLLECTION="nw41" TIDREF="i554"A 32-bit internal path that connects the CPU directly to memory, video, and disk controllers.The local bus allows data transfer to and from the CPU to memory and peripherals at CPU speeds (such as 33, 66, and 90 MHz). Prior to local-bus architecture, the microprocessor speeds outpaced the internal bus speeds, which created a narrow data stream in and out of the CPU and slowed the computer. Local bus architecture significantly improves data transfer rates and greatly reduces the I/O bottleneck because peripheral devices are bound only by the clock speed of the CPU.Local bus architecture is utilized by Peripheral Component Interconnect (PCI) and Video Electronics Standards Association (VESA) buses. See also IDREF="FM67952""Expansion bus"RENDERAS="SECT1"Local driveA common name for a physical drive attached to a workstation.See IDREF="FM87366""Drive"RENDERAS="SECT1"ID="FM84055"Logical memoryIDXID="w2010"BOOK="_idx" COLLECTION="nw41" TIDREF="i2203"IDXID="w2011"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"Memory that may not have contiguous addresses, but which appears contiguous to NetWare 4 processes.See also IDREF="FM45002""Paging."RENDERAS="SECT1"ID="FM12564"LoginIDXID="w2012"BOOK="_idx" COLLECTION="nw41" TIDREF="i2206"IDXID="w2013"BOOK="_idx" COLLECTION="nw41" TIDREF="i2222"The procedure that provides access to the network by using the LOGIN command.When a user initiates a login request, the operating system looks for security rights; the user is then asked for a password.PAGENUM=151 ID="BP158"All security information is placed into the NetWare server's connection list and the user is said to be logged in.At this point, LOGIN executes one or more login scripts (which initialize environment variables, map network drives, etc.).Related utility: "BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities Reference.See also IDREF="FM52477""LOGIN directory"; IDREF="FM22722""Login restrictions"; IDREF="FM88191""Logout"; IDREF="FM23712""Login scripts."RENDERAS="SECT1"ID="FM52477"LOGIN directoryIDXID="w2014"BOOK="_idx" COLLECTION="nw41" TIDREF="i2207"The SYS:LOGIN directory, created during network installation that contains the LOGIN and NLIST utilities. Users can use these utilities to log in and view a list of available NetWare servers.For NetWare users running OS/2, the corresponding LOGIN directory is SYS:LOGIN/OS2.Don't delete the LOGIN directory.See also IDREF="FM22177""File system"; IDREF="FM38021""MAIL directory"; IDREF="FM82664""PUBLIC directory"; IDREF="FM79008""SYSTEM directory."RENDERAS="SECT1"ID="FM22722"Login restrictionsIDXID="w2015"BOOK="_idx" COLLECTION="nw41" TIDREF="i2206"Limitations on user accounts that control access to the network, such asMARK=BULLETRequiring a password. If you require a password, you can specify its minimum length, whether it must be changed (and how often), whether it must be unique, and whether the user can change it.You can also specify the number of times a user can log in using an expired password and the number of incorrect login attempts allowed.Setting account limits. If you install Accounting, you can assign account limits, like an account balance or expiration date.Limiting disk space. You can limit the amount of disk space for each user by specifying the maximum blocks available for each user on a volume.PAGENUM=152 ID="BP159"Specifying the number of connections. You can limit the number of times a user can log in simultaneously. You can also specify, by node address, which workstations users can log in on.Setting time restrictions. You can restrict the hours during which users can log in. You can assign all users the same hours, or you can restrict users individually.When a user violates login restrictions, NetWare disables the account and no one can log in using that username. This prevents unauthorized users from logging in.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.RENDERAS="SECT1"ID="FM23712"Login scriptsIDXID="w2016"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"Files containing commands that set up users' workstation environments whenever they log in. Login scripts are similar to batch files and are executed by the LOGIN utility.You can use login scripts toMARK=BULLETMap drives and search drives to directoriesDisplay messagesSet environment variablesExecute programs or menusLogin scripts work the same way for DOS, MS Windows, and OS/2 workstations, although some commands that apply to DOS and MS Windows workstations may not apply to OS/2 workstations.RENDERAS="SECT2"Three Types of Login ScriptsWhen a user logs in, the LOGIN utility executes the appropriate login scripts. Three types of login scripts can be used together to specify a custom environment for your users. All three types of login scripts are optional.PAGENUM=153 ID="BP160"MARK=BULLETContainer login scripts set general environments for all users in a container (such as an Organizational Unit). These login scripts execute first.Profile login scripts set environments for multiple users. These login scripts execute after a container login script.User login scripts set environments specific to a single user, such as menu options or a username for electronic mail. These login scripts execute after container and profile login scripts.The LOGIN utility contains a default login script. This login script executes the first time you log in as User object ADMIN. It contains only essential commands, such as a drive mapping to NetWare utilities.This default login script also executes for any user who doesn't have an individual user login script. If you don't want to create a user login script and you want to prevent the default login script from executing, you can disable the default script by including the NO_DEFAULT command in the container or profile login scripts.RENDERAS="SECT2"Which Types of Login Scripts to CreateMaintaining many user login scripts can be time consuming. Therefore, include as much customizing information as possible in the container and profile login scripts, which are fewer in number and easier to maintain.For example, if all users need access to NetWare utilities in the same volume, put the search drive mapping to that volume in a single container login script rather than in every user login script.Create profile login scripts if there are multiple users with identical login script needs. These are sometimes thought of as group login scripts.Finally, in user login scripts, include only those individual items that can't be included in profile or container login scripts.PAGENUM=154 ID="BP161"Since up to three login scripts can execute whenever a user logs in, conflicts can occur. If this happens, the last login script to execute (usually the user login script) overrides any conflicting commands in a previous login script.Login scripts are properties of objects. The following table shows which objects can contain login scriptsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectCOLNAME=2 ROTATE="0" MOREROWS="0"Type of login scriptVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"OrganizationCOLNAME=2 ROTATE="0" MOREROWS="0"ContainerCOLNAME=1 ROTATE="0" MOREROWS="0"Organizational UnitCOLNAME=2 ROTATE="0" MOREROWS="0"ContainerCOLNAME=1 ROTATE="0" MOREROWS="0"ProfileCOLNAME=2 ROTATE="0" MOREROWS="0"ProfileCOLNAME=1 ROTATE="0" MOREROWS="0"UserCOLNAME=2 ROTATE="0" MOREROWS="0"UserThe following figure shows how the different types of login scripts can reside in a Directory tree and how they affect users.PAGENUM=155 ID="BP162"LABEL="44" FLOAT="0"IDXID="w2017"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"Where Login Scripts Are LocatedFILEREF="n41co28a.tif"In the previous figure, there are three users, ESAYERS, SWILLIAMS, and MRICHARD. The following table shows which login scripts execute when each user logs in.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="12*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w2018"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"
When this users logs inCOLNAME=2 ROTATE="0" MOREROWS="0"Login scripts execute in this orderVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ESAYERSCOLNAME=2 ROTATE="0" MOREROWS="0"1. SALES PV's container login script2. ESAYERS's user login scriptCOLNAME=1 ROTATE="0" MOREROWS="0"SWILLIAMSCOLNAME=2 ROTATE="0" MOREROWS="0"1. SALES PV's container login script2. Default user login scriptCOLNAME=1 ROTATE="0" MOREROWS="0"MRICHARDCOLNAME=2 ROTATE="0" MOREROWS="0"1. ACCOUNTING's container login script2. CLERKS' profile login script3. MRICHARD's user login scriptPAGENUM=156 ID="BP163"Container login scripts only affect users immediately below the Organization or Organizational Unit that contains the login script.For example, in the figure, although there are two levels of container objects above users ESAYERS and SWILLIAMS, only the container login script immediately above them (at OU=SALES PV) executes when they log in.If SALES PV had no container login script defined, no container login script would execute for ESAYERS and SWILLIAMS, even though a container login script exists at a higher level.Since SWILLIAMS has no user login script defined, the default login script executes after the container login script.Since MRICHARD belongs to the profile CLERKS, the CLERKS' profile login script executes before MRICHARD's user login script. Users can belong to only one Profile, so only one profile login script can execute for any user.RENDERAS="SECT2"Creating, Modifying, and Copying Login ScriptsYou can use either the NETADMIN utility or the NetWare Administrator utility to create or modify login scripts.The main difference in creating container, profile, and user login scripts is the object you select to contain the scripts.MARK=BULLETContainer login scripts are assigned to container objects (Organization or Organizational Unit objects).PAGENUM=157 ID="BP164"Profile login scripts are assigned to Profile objects. For a User object to use a profile login script, you must select that User object and assign it to the Profile object.User login scripts are assigned to User objects.A user can have login scripts in both the Directory tree and the bindery. However, if a change is made in one, that change is not automatically made in the other. You must manually edit both login scripts if you want them to be identical.All three scripts use the same conventions, commands, and variables.RENDERAS="SECT2"Login Script CommandsSome of the commands you can use in login scripts are listed in the following table. (For a list of all login script commands and a complete description of each, see "BOOK="superenu" COLLECTION="nw41"Login Script Commands and Variables" in Chapter 3 of Supervising the Network.)LABEL="4" PGWIDE=1 TOCENTRY="1" Selected Login Script CommandsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Login script commandCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ATTACHCOLNAME=2 ROTATE="0" MOREROWS="0"Connects to bindery-based NetWare servers (NetWare 2 or NetWare 3) or to NetWare 4 servers using bindery services.COLNAME=1 ROTATE="0" MOREROWS="0"COMSPECCOLNAME=2 ROTATE="0" MOREROWS="0"If users run DOS from the network, this specifies the directory where the DOS command processor (COMMAND.COM) is loaded.Users running OS/2 shouldn't use this command in the login script.COLNAME=1 ROTATE="0" MOREROWS="0"EXITCOLNAME=2 ROTATE="0" MOREROWS="0"Terminates execution of the LOGIN utility and executes an external program (doesn't apply to OS/2 workstations).COLNAME=1 ROTATE="0" MOREROWS="0"FIRE PHASERSCOLNAME=2 ROTATE="0" MOREROWS="0"Emits a phaser sound when certain conditions exist.COLNAME=1 ROTATE="0" MOREROWS="0"IF...THENCOLNAME=2 ROTATE="0" MOREROWS="0"Performs an action only under certain conditions.COLNAME=1 ROTATE="0" MOREROWS="0"MAPCOLNAME=2 ROTATE="0" MOREROWS="0"Maps drives and search drives to network directories and NDS objects.COLNAME=1 ROTATE="0" MOREROWS="0"PAUSECOLNAME=2 ROTATE="0" MOREROWS="0"Creates a pause in the execution of the login script.COLNAME=1 ROTATE="0" MOREROWS="0"SETCOLNAME=2 ROTATE="0" MOREROWS="0"Sets a DOS or OS/2 environment variable.For OS/2 workstations, SET commands affect the environment only while the login script is running; the settings disappear when LOGIN terminates.COLNAME=1 ROTATE="0" MOREROWS="0"WRITECOLNAME=2 ROTATE="0" MOREROWS="0"Displays messages on the workstation screen when a user logs in.PAGENUM=158 ID="BP165"RENDERAS="SECT2"Identifier VariablesWith many login script commands, you can take advantage of identifier variables to make your login script more efficient and flexible.Identifier variables allow you to enter a variable (such as LOGIN_NAME) in a login script command, rather than a specific name (such as RICHARD). By using the variable, you can make the login script command applicable to many users.When the login script executes, it substitutes real values for the identifier variables. Therefore, when Richard logs in, the commandFORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "Hello,";LOGIN_NAMEdisplays the following message on Richard's workstation screen:FORMAT="LINESPECIFIC"MOREINFO="NONE"Hello, RichardIn the above example, when Richard logged in, the name he entered was substituted for the LOGIN_NAME variable.PAGENUM=159 ID="BP166"The following table lists identifier variables you can use in login scripts.  IDXID="w2019"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"IDXID="w2020"BOOK="_idx" COLLECTION="nw41" TIDREF="i4751"LABEL="5" PGWIDE=1 TOCENTRY="1"Identifier VariablesCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"CategoryCOLNAME=2 ROTATE="0" MOREROWS="0"Identifier variableCOLNAME=3 ROTATE="0" MOREROWS="0"FunctionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DateCOLNAME=2 ROTATE="0" MOREROWS="0"DAYCOLNAME=3 ROTATE="0" MOREROWS="0"Day number (01 through 31).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"DAY_OF_WEEKCOLNAME=3 ROTATE="0" MOREROWS="0"Day of week (Monday, Tuesday, etc.).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"MONTHCOLNAME=3 ROTATE="0" MOREROWS="0"Month number (01 through 12).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"MONTH_NAMECOLNAME=3 ROTATE="0" MOREROWS="0"Month name (January, February, etc.).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NDAY_OF_WEEKCOLNAME=3 ROTATE="0" MOREROWS="0"Weekday number (1 through 7, with 1=Sunday).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"SHORT_YEARCOLNAME=3 ROTATE="0" MOREROWS="0"Last two digits of year (93, 94, 95, etc.).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"YEARCOLNAME=3 ROTATE="0" MOREROWS="0"All four digits of year (1993, 1994, 1995, etc.).COLNAME=1 ROTATE="0" MOREROWS="0"TimeCOLNAME=2 ROTATE="0" MOREROWS="0"AM_PMCOLNAME=3 ROTATE="0" MOREROWS="0"Day or night (am or pm).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"GREETING_TIMECOLNAME=3 ROTATE="0" MOREROWS="0"Time of day (morning, afternoon, or evening).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"HOURCOLNAME=3 ROTATE="0" MOREROWS="0"Hour (12-hour scale; 1 through 12).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"HOUR24COLNAME=3 ROTATE="0" MOREROWS="0"Hour (24-hour scale; 00 through 23, 00=midnight). COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"MINUTECOLNAME=3 ROTATE="0" MOREROWS="0"Minute (00 through 59).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"SECONDCOLNAME=3 ROTATE="0" MOREROWS="0"Second (00 through 59).COLNAME=1 ROTATE="0" MOREROWS="0"DOS EnvironmentCOLNAME=2 ROTATE="0" MOREROWS="0"<variable>COLNAME=3 ROTATE="0" MOREROWS="0"Any DOS environment variable can be used in angle brackets (<path>, etc.). To use a DOS environment variable in a MAP command, add a percent sign (%) in front of the variable, such as MAP S16:=%<path>.COLNAME=1 ROTATE="0" MOREROWS="0"NetworkCOLNAME=2 ROTATE="0" MOREROWS="0"FILE_SERVERCOLNAME=3 ROTATE="0" MOREROWS="0"NetWare server name.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NETWORK_ADDRESSCOLNAME=3 ROTATE="0" MOREROWS="0"Network number of the cabling system (8- digit hexadecimal number).COLNAME=1 ROTATE="0" MOREROWS="0"UserCOLNAME=2 ROTATE="0" MOREROWS="0"FULL_NAMECOLNAME=3 ROTATE="0" MOREROWS="0"User's complete name in the Directory context, or full name in bindery-based NetWare.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"LAST_NAMECOLNAME=3 ROTATE="0" MOREROWS="0"User's last name (surname) in NDS, or full name in bindery-based NetWare.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"LOGIN_NAMECOLNAME=3 ROTATE="0" MOREROWS="0"User's unique login name. (Long names are truncated to eight characters.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"MEMBER OF "group"COLNAME=3 ROTATE="0" MOREROWS="0"Group object that the user is assigned to.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NOT MEMBER OF "group"COLNAME=3 ROTATE="0" MOREROWS="0"Group object that the user isn't assigned to.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"PASSWORD_EXPIRESCOLNAME=3 ROTATE="0" MOREROWS="0"Number of days before password expires.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"USER_IDCOLNAME=3 ROTATE="0" MOREROWS="0"Number assigned to each user.COLNAME=1 ROTATE="0" MOREROWS="0"WorkstationCOLNAME=2 ROTATE="0" MOREROWS="0"MACHINECOLNAME=3 ROTATE="0" MOREROWS="0"Type of computer (IBM_PC, etc.). See your DOS manual for more information. (Not available under OS/2.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NETWARE_REQUESTERCOLNAME=3 ROTATE="0" MOREROWS="0"Version of the NetWare Requester for OS/2 (2.01, etc.).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"OSCOLNAME=3 ROTATE="0" MOREROWS="0"Type of DOS on the workstation (DRDOS, MSDOS, etc.).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"OS_VERSIONCOLNAME=3 ROTATE="0" MOREROWS="0"Version of DOS on the workstation (3.30, etc.).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"P_STATIONCOLNAME=3 ROTATE="0" MOREROWS="0"Workstation's node address (12-digit hex).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"SHELL_TYPECOLNAME=3 ROTATE="0" MOREROWS="0"Version of the workstation's DOS shell (1.02, etc.). Supports NetWare 2 and NetWare 3 shells and NetWare 4 Requester for DOS.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"SMACHINECOLNAME=3 ROTATE="0" MOREROWS="0"Short machine name (IBM, etc.). (Not available under OS/2.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"STATIONCOLNAME=3 ROTATE="0" MOREROWS="0"Workstation's connection number.COLNAME=1 ROTATE="0" MOREROWS="0"MiscellaneousCOLNAME=2 ROTATE="0" MOREROWS="0"ACCESS_SERVERCOLNAME=3 ROTATE="0" MOREROWS="0"Shows whether the access server is functional (TRUE=functional, FALSE=not functional).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"ERROR_LEVELCOLNAME=3 ROTATE="0" MOREROWS="0"An error number (0=No errors).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"%nCOLNAME=3 ROTATE="0" MOREROWS="0"Replaced by parameters the user enters at the command line with the LOGIN utility.COLNAME=1 ROTATE="0" MOREROWS="0"Object propertiesCOLNAME=2 ROTATE="0" MOREROWS="0"property nameCOLNAME=3 ROTATE="0" MOREROWS="0"You can use any property of NDS objects as a variable. Use the property's name just as you do any other identifier variable. If the property name includes a space, enclose the name in quotation marks.PAGENUM=161 ID="BP167"RENDERAS="SECT2"PAGENUM=162 ID="BP168"Sample Login ScriptsThe following sample login scripts may help you plan your own container, profile, and user login scripts. Each example script is shown in a table. The left column shows the commands in the script. The right column explains the command.Container login script. The container login script should contain any information that applies to all users.LABEL="6" PGWIDE=1 TOCENTRY="1"IDXID="w2021"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"IDXID="w2022"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"Sample Container Login ScriptCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="21*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Login script commandsCOLNAME=2 ROTATE="0" MOREROWS="0"PurposeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"MAP DISPLAY OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Prevents map commands from displaying on the screen.COLNAME=1 ROTATE="0" MOREROWS="0"MAP ERRORS OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Prevents mapping errors from displaying on the screen.COLNAME=1 ROTATE="0" MOREROWS="0"MAP *1:=SYS:COLNAME=2 ROTATE="0" MOREROWS="0"Maps the first drive to volume SYS:.COLNAME=1 ROTATE="0" MOREROWS="0"MAP *1:=SYS:%LOGIN_NAMECOLNAME=2 ROTATE="0" MOREROWS="0"Maps the first drive to the user's home directory. If the user has no home directory, the first drive is still mapped to SYS:.COLNAME=1 ROTATE="0" MOREROWS="0"IF "%1"= "ADMIN"THEN MAP *1:=SYS:SYSTEMCOLNAME=2 ROTATE="0" MOREROWS="0"If the login name is ADMIN, it maps the first drive to SYS:SYSTEM instead of to the user's home directory.COLNAME=1 ROTATE="0" MOREROWS="0"IF OS2 THENMAP P:=SYS:PUBLICELSE MAP INS S1:=SYS:PUBLICMAP INS S2:=SYS:PUBLIC\%MACHINE\%OS\ %OS_VERSIONENDCOLNAME=2 ROTATE="0" MOREROWS="0"If the user logs in from an OS/2 station, drive P: maps to PUBLIC. (See "BOOK="ws_osenu" COLLECTION="nw41"NetWare 2 and 3 Users Upgrading to NetWare 4," in NetWare Client for OS/2 User Guide.)If the user isn't using an OS/2 station, the first search drive is mapped to SYS:PUBLIC, where DOS-based NetWare utilities are stored. The second search drive is mapped to the directory where DOS is stored.For example, if all stations use DOS, use the following two commands instead of the IF...THEN command:MAP INS S1:=SYS:PUBLIC  MAP INS S2:=SYS:PUBLIC\ %MACHINE\%OS\%OS_VERSIONCOLNAME=1 ROTATE="0" MOREROWS="0"IF MEMBER OF "WIN31" THENMAP INS *2:=SYS:USERS\%LOGIN_NAME\WIN31MAP INS S16:=SYS:APPS\WINAPPS\WIN31SET TEMP = "P:\USERS\%LOGIN_NAME\WIN31\TEMP"ENDCOLNAME=2 ROTATE="0" MOREROWS="0"If the user who logs in is a member of Group object WIN31, the next available drive is mapped to that user's MS Windows directory. Then the next available search drive is mapped to the MS Windows directory for the WIN31 group. Finally, the MS Windows TEMP directory is set to a subdirectory of the user's MS Windows directory.COLNAME=1 ROTATE="0" MOREROWS="0"MAP INS S16:=VOL1:APPL\WPCOLNAME=2 ROTATE="0" MOREROWS="0"Maps the next available search drive to the directory that contains WordPerfect®.COLNAME=1 ROTATE="0" MOREROWS="0"MAP INS S16:=VOL1:APPL\LOTUSCOLNAME=2 ROTATE="0" MOREROWS="0"Maps the next available search drive to the directory that contains Lotus*.COLNAME=1 ROTATE="0" MOREROWS="0"MAP INS S16:=SYS:EMAILCOLNAME=2 ROTATE="0" MOREROWS="0"Maps the next available search drive to the E-mail directory.COLNAME=1 ROTATE="0" MOREROWS="0"MAP O:=SYS:DOCCOLNAME=2 ROTATE="0" MOREROWS="0"Maps drive O: to a directory necessary for running the electronic NetWare documentation.COLNAME=1 ROTATE="0" MOREROWS="0"IF MEMBER OF "MANAGERS" THENMAP *3:=VOL1:PROJECTS\REPORTSENDCOLNAME=2 ROTATE="0" MOREROWS="0"If the user belongs to the MANAGERS Group object, the script maps the third network drive to the REPORTS directory.COLNAME=1 ROTATE="0" MOREROWS="0"IF MEMBER OF "TESTERS" THENMAP *4:=INPUT:STATUS\UPDATESENDCOLNAME=2 ROTATE="0" MOREROWS="0"If the user belongs to the TESTERS Group object, the script maps the fourth network drive to the UPDATES directory.COLNAME=1 ROTATE="0" MOREROWS="0"COMSPEC = S2:COMMAND.COMCOLNAME=2 ROTATE="0" MOREROWS="0"Sets COMSPEC to the DOS command processor, located in the DOS directory (in the second search drive).COLNAME=1 ROTATE="0" MOREROWS="0"SET PROMPT = "$P$G"COLNAME=2 ROTATE="0" MOREROWS="0"Sets the prompt to display the user's current directory path, followed by the > symbol.COLNAME=1 ROTATE="0" MOREROWS="0"MAP DISPLAY ONCOLNAME=2 ROTATE="0" MOREROWS="0"Allows map commands to display.COLNAME=1 ROTATE="0" MOREROWS="0"MAPCOLNAME=2 ROTATE="0" MOREROWS="0"Displays a list of all drive mappings.COLNAME=1 ROTATE="0" MOREROWS="0"WRITECOLNAME=2 ROTATE="0" MOREROWS="0"Displays a blank line between the list of mappings and following lines.COLNAME=1 ROTATE="0" MOREROWS="0"WRITE "Good %GREETING_TIME, %FULL_NAME."COLNAME=2 ROTATE="0" MOREROWS="0"Displays a greeting to the user. Example: "Good morning, MARY.SALES.NOVELL."COLNAME=1 ROTATE="0" MOREROWS="0"WRITE "Your password expires in %PASSWORD_EXPIRES days."COLNAME=2 ROTATE="0" MOREROWS="0"Displays a message indicating the number of days before the user's password expires.COLNAME=1 ROTATE="0" MOREROWS="0"FIRE PHASERS 3 TIMESCOLNAME=2 ROTATE="0" MOREROWS="0"Makes the phaser sound occur three times, to tell the user that the login process is complete.PAGENUM=165 ID="BP169"IDXID="w2023"BOOK="_idx" COLLECTION="nw41" TIDREF="i3565"IDXID="w2024"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"Profile login script. If you have groups of users with identical login script needs, you can create a Profile object and create a login script for the Profile object. Then, you can assign each user a member of that Profile object.The following is an example of a profile login script you might create for users in the ACCOUNTING Profile object. The ACCOUNTING profile login script would execute after the container login script.  IDXID="w2025"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"IDXID="w2026"BOOK="_idx" COLLECTION="nw41" TIDREF="i3565"LABEL="7" PGWIDE=1 TOCENTRY="1"Sample Profile Login ScriptCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="21*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Login script commandsCOLNAME=2 ROTATE="0" MOREROWS="0"PurposeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"MAP DISPLAY OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Prevents map commands from displaying on the screen as they are assigned.COLNAME=1 ROTATE="0" MOREROWS="0"MAP ERRORS OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Prevents mapping errors from displaying on the screen.COLNAME=1 ROTATE="0" MOREROWS="0"MAP INS S16:=VOL1:APPL\DBCOLNAME=2 ROTATE="0" MOREROWS="0"Maps the first available search drive (after those assigned in the container login script) to the directory that contains the database program.COLNAME=1 ROTATE="0" MOREROWS="0"MAP *5:=VOL1:ACCOUNTS\NEWCOLNAME=2 ROTATE="0" MOREROWS="0"Maps the fifth network drive (after those assigned in the container login script) to the NEW subdirectory.COLNAME=1 ROTATE="0" MOREROWS="0"MAP *6:=VOL1:ACCOUNTS\RECORDSCOLNAME=2 ROTATE="0" MOREROWS="0"Maps the sixth network drive (after those assigned in the container login script) to the RECORDS subdirectory.COLNAME=1 ROTATE="0" MOREROWS="0"#WSUPDATE S1:IPXODI.COM /LOCALCOLNAME=2 ROTATE="0" MOREROWS="0"Executes WSUPDATE, which updates the IPXODI.COM file on the user's workstation with a new version of the file located in the first search drive.COLNAME=1 ROTATE="0" MOREROWS="0"MAP DISPLAY ONCOLNAME=2 ROTATE="0" MOREROWS="0"Allows map commands to display.COLNAME=1 ROTATE="0" MOREROWS="0"MAPCOLNAME=2 ROTATE="0" MOREROWS="0"Displays a list of all drive mappings.COLNAME=1 ROTATE="0" MOREROWS="0"WRITECOLNAME=2 ROTATE="0" MOREROWS="0"Displays a blank line between the list of mappings and following lines.COLNAME=1 ROTATE="0" MOREROWS="0"IF DAY_OF_WEEK = "FRIDAY" THENWRITE "Weekly progress report is due today."FIRE 2ENDCOLNAME=2 ROTATE="0" MOREROWS="0"On Fridays, the phaser sound occurs twice to alert the user while the message "Weekly progress report is due today" displays on the screen.COLNAME=1 ROTATE="0" MOREROWS="0"PCCOMPATIBLEEXIT "NMENU WORK"COLNAME=2 ROTATE="0" MOREROWS="0"Stops the profile login script and sends the user into a menu program called WORK.EXIT also prevents user login scripts from executing. If you want a user login script to execute after the profile script, put these lines at the end of the user login script instead.DOS workstations with the machine name IBM_PC don't need the PCCOMPATIBLE line.EXIT doesn't work on OS/2 workstations.PAGENUM=168 ID="BP170"IDXID="w2027"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"User login script. The following is an example of a user login script for MARY. The user login script executes after container and profile login scripts.  IDXID="w2028"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"IDXID="w2029"BOOK="_idx" COLLECTION="nw41" TIDREF="i4709"LABEL="8" PGWIDE=1 TOCENTRY="1"Sample User Login ScriptCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="21*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Login script commandsCOLNAME=2 ROTATE="0" MOREROWS="0"PurposeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"MAP DISPLAY OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Prevents map commands from displaying on the screen as they are assigned.COLNAME=1 ROTATE="0" MOREROWS="0"MAP ERRORS OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Prevents mapping errors from displaying on the screen.COLNAME=1 ROTATE="0" MOREROWS="0"MAP *7:=VOL1:MARY\PROJECTS\RESEARCHCOLNAME=2 ROTATE="0" MOREROWS="0"Maps Mary's seventh network drive (after those assigned in the container and profile scripts) to the RESEARCH subdirectory in her home directory.COLNAME=1 ROTATE="0" MOREROWS="0"MAP *8:=VOL1:FORMSCOLNAME=2 ROTATE="0" MOREROWS="0"Maps Mary's eighth network drive (after those assigned in the container and profile scripts) to the FORMS directory.COLNAME=1 ROTATE="0" MOREROWS="0"REM Mary needs access to FORMS while she's on theREM troubleshooting team. Remove this drive mappingREM when she's reassigned.COLNAME=2 ROTATE="0" MOREROWS="0"This remark is a reminder to the person who created the login script. It doesn't display on the user's screen.(Because the remark is several lines long, each line starts with the keyword REM.)COLNAME=1 ROTATE="0" MOREROWS="0"SET WP="/u-mjr/b-5"COLNAME=2 ROTATE="0" MOREROWS="0"Sets Mary's environment variables for WordPerfect.COLNAME=1 ROTATE="0" MOREROWS="0"SET USR="mrichard"COLNAME=2 ROTATE="0" MOREROWS="0"Sets Mary's user name (mrichard) for the electronic mail program.COLNAME=1 ROTATE="0" MOREROWS="0"#CAPTURE Q=FAST_Q NB TI=10 NFFCOLNAME=2 ROTATE="0" MOREROWS="0"Executes the CAPTURE utility so Mary can print from non-network applications.COLNAME=1 ROTATE="0" MOREROWS="0"PCCOMPATIBLEEXIT "NMENU TRAINING"COLNAME=2 ROTATE="0" MOREROWS="0"Stops the user login script and sends the user into a menu program called TRAINING.DOS workstations with the machine name IBM_PC don't need the PCCOMPATIBLE line.The EXIT command doesn't work on OS/2 workstations.PAGENUM=169 ID="BP171"If you did not exist as a user on a server before it was upgraded to NetWare 4 and you now need to log in via bindery services, use SYSCON (a NetWare 3 utility) to create the login script.For information about creating, modifying, and copying login scripts, see "BOOK="superenu" COLLECTION="nw41"Creating, Modifying, Copying, and Printing Login Scripts" in Chapter 3 of Supervising the Network.See also IDREF="FM39775""Drive mapping."RENDERAS="SECT1"ID="FM88191"LogoutIDXID="w2030"BOOK="_idx" COLLECTION="nw41" TIDREF="i2227"A procedure that breaks the network connection and deletes drives mapped to the network.If you log out without specifying a NetWare server name in the LOGOUT command, the station connections and drives mapped to all servers are terminated.To log out from one server and remain attached to the other servers, specify the server name in the LOGOUT command.PAGENUM=170 ID="BP172"Make sure at least one of the remaining drives is mapped to the PUBLIC directory of a NetWare server that you are still attached to. Otherwise, you can't access NetWare utilities.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"LOGOUT," "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN," and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.RENDERAS="SECT1"ID="FM83726"Long machine typeIDXID="w2031"BOOK="_idx" COLLECTION="nw41" TIDREF="i2235"IDXID="w2032"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"IDXID="w2033"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
A six-letter name representing a DOS workstation brand. (This doesn't apply to OS/2 workstations.)Use the long machine type in container login scripts (using the MACHINE identifier variable) to automatically map a drive to the correct version of DOS assigned to the station.IBM computers use the long machine type IBM_PC. If the station is not an IBM computer, create a long machine type for the station in a NET.CFG file.Use the six-letter name for the long machine type as the subdirectory name when you use more than one brand of workstation. For example, if you use COMPAQ* workstations, use COMPAQ as the long machine type.Use the same six-letter name for DOS directories that you use for the long machine type.If you use more than one version of DOS, you must have separate subdirectories for each DOS version used on each machine type.See also IDREF="FM39874""DOS version"; IDREF="FM23712""Login scripts"; IDREF="FM97289""Short machine type."RENDERAS="SECT1"ID="FM25427"LPT portsIDXID="w2034"BOOK="_idx" COLLECTION="nw41" TIDREF="i2243"The parallel printer ports of a personal computer.See IDREF="FM31531""Parallel port." See also "BOOK="printenu" COLLECTION="nw41"Selecting the Best Type of Printer for Your Setup" in Appendix A of Print Services.PAGENUM=171 ID="BP173"RENDERAS="SECT1"ID="FM97359"LSL(Link Support Layer) An intermediary between the NetWare server's LAN drivers and communication protocols, such as IPX, AFP, or TCP/IP.See IDREF="FM12535""Link Support Layer."PAGENUM=172 ID="BP174"MRENDERAS="SECT1"ID="FM74418"Macintosh clientIDXID="w2035"BOOK="_idx" COLLECTION="nw41" TIDREF="i2258"A Macintosh computer that attaches to the network.The Macintosh client can store data on, and retrieve data from, a NetWare server running NetWare for Macintosh name space support modules. The Macintosh client can also run executable Macintosh network files, share files with other clients (DOS, MS Windows, OS/2, and UNIX), and monitor queues.See also IDREF="FM99174""Client."RENDERAS="SECT1"ID="FM86837"Macintosh filesIDXID="w2036"BOOK="_idx" COLLECTION="nw41" TIDREF="i2258"Files used on Macintosh computers.A Macintosh file contains two parts: the data fork and the resource fork.MARK=BULLETData fork. Contains information (data) specified by the user.Resource fork. Contains file resources, including Macintosh-specific information such as the windows and icons used with the file.To store Macintosh files on a NetWare server, the Macintosh name space module must be linked with the NetWare operating container.When a Macintosh client accesses the file stored on the server, it accesses both the data and resource forks; both of these are required for the Macintosh to use the file.When a non-Macintosh client accesses the file stored on the server, only the data fork is used.PAGENUM=173 ID="BP175"When you use a non-Macintosh client to copy Macintosh files from one location to another on a NetWare server, use NCOPY rather than COPY so that both forks are copied.When you use a Macintosh client to drag-copy Macintosh files from one location to another on a NetWare server, both the data and resource forks are copied.If you use the NetWare Administrator to copy a Macintosh file between volumes, you lose extended attribute information on the file unless the two volumes have identical sets of name spaces loaded.For example, if volume 1 has Macintosh and DOS name spaces loaded and volume 2 has Macintosh, DOS, and OS/2 name spaces loaded, and you copy a Macintosh file from one volume to another, you lose extended attributes, even though both volumes have the Macintosh name space. See also IDREF="FM32610""Name space support."RENDERAS="SECT1"Mailbox IDIDXID="w2037"BOOK="_idx" COLLECTION="nw41" TIDREF="i2303"A unique name that specifies the directory in which all of the object's inbound mail is placed.The utility you use to administer mailbox information (NetWare Administrator or NETADMIN) automatically assigns an object a Mailbox ID by using up to eight characters of the object's name.However, if the object's name has spaces in it, or if it uses non-DOS characters, the utility assigns the object a Mailbox ID, but eliminates the spaces and other illegal characters to form a legal DOS name.RENDERAS="SECT1"Mailbox locationIDXID="w2038"BOOK="_idx" COLLECTION="nw41" TIDREF="i2303"The name of the messaging server where an object's mailbox resides.RENDERAS="SECT1"ID="FM38021"MAIL directoryIDXID="w2039"BOOK="_idx" COLLECTION="nw41" TIDREF="i2301"The SYS:MAIL directory, created during network installation, used by mail programs that are compatible with NetWare.In previous versions of NetWare, the MAIL directory held user login scripts. When you upgrade to NetWare 4PAGENUM=174 ID="BP176", existing users still have subdirectories in the MAIL directory, but their login scripts become a property of the new User object.New users that you create under NetWare 4 won't have subdirectories in the MAIL directory.See also IDREF="FM22177""File system"; IDREF="FM52477""LOGIN directory"; IDREF="FM82664""PUBLIC directory"; IDREF="FM79008""SYSTEM directory."RENDERAS="SECT1"IDXID="w2040"BOOK="_idx" COLLECTION="nw41" TIDREF="i4425"IDXID="w2041"BOOK="_idx" COLLECTION="nw41" TIDREF="i3821"ID="FM34549"Major resourceIDXID="w2042"BOOK="_idx" COLLECTION="nw41" TIDREF="i2310"A category of data defined by the Target Service Agent, and recognized by SBACKUP.A major resource contains data that can be backed up as a group, such as a the data on a server or volume.See also IDREF="FM24312""Backup"; IDREF="FM51647""Minor resource"; IDREF="FM82095""Target Service Agent"; IDREF="FM67355""Transaction Tracking System."RENDERAS="SECT1"ID="FM79303"Management Information Base(MIB) The entire set of objects that any service or protocol uses in Simple Network Management Protocol (SNMP). Because different network-management services are used for different types of devices or for different network-management protocols, each service has its own set of objects.RENDERAS="SECT1"MapIDXID="w2043"BOOK="_idx" COLLECTION="nw41" TIDREF="i2338"For DOS and OS/2 clients, to assign a drive letter to a directory path on a volume.For example, if you map drive F: to the directory SYS:ACCTS/RECEIVE, you access that directory every time you change to drive F:.See also IDREF="FM39775""Drive mapping."RENDERAS="SECT1"PAGENUM=175 ID="BP177"Master replicaThe Directory replica used to create a new Directory partition in the Directory database or to read and update Directory information.Although many Directory replicas can exist in the Directory, only one can be the master replica. The master replica is always considered to be the most accurate Directory replica.See also IDREF="FM27324""NetWare Directory replica."RENDERAS="SECT1"ID="FM74176"Media ManagerIDXID="w2044"BOOK="_idx" COLLECTION="nw41" TIDREF="i2364"A database built in NetWare that keeps track of all peripheral storage devices and media attached to NetWare servers, and allows applications to gain access and get information.See alsoIDREF="FM87820""NetWare Peripheral Architecture."RENDERAS="SECT1"ID="FM11327"MemoryIDXID="w2045"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"The internal dynamic storage of a computer that can be addressed by the computer's operating system, referred to frequently as RAM (random access memory).Memory accepts and holds binary data. To be effective, a computer must store the data that is operated on, as well as the program that directs the operations to be performed.Memory stores information and rapidly accesses any part of the information upon request.The following figure, and the text that follows, illustrate how memory is addressed in personal computers running DOS.PAGENUM=176 ID="BP178"LABEL="45" FLOAT="0"IDXID="w2046"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"MemoryFILEREF="n40co16a.tif"RENDERAS="SECT2"IDXID="w2047"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
Conventional MemoryRAM located below 640 KB that is devoted to running programs and applications. Also called low DOS memory or base memory.RENDERAS="SECT2"IDXID="w2048"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
Expanded MemoryMemory that lies outside DOS's normal address space but that can be made addressable in 16KB units, called pages, through an area called a page frame.PAGENUM=177 ID="BP179"Expanded memory is available for 8086, 8088, and 80286 systems through expanded memory specification (EMS) compliant memory boards, or for 80386 and 80486 systems through EMS emulators.Expanded memory is mainly designed to store data and certain numbers.Most program code, most add-ins, and integers between -32,767 and 32,767 generally must be stored in memory that is directly addressed by DOS.Collectively, these requirements reduce the usefulness of expanded memory.RENDERAS="SECT2"IDXID="w2049"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
Extended MemoryRAM above the 1,024KB address limit of DOS.Up to 16 MB of extended memory can be addressed on 80286 systems; up to 4 GB on 80386 and 80486 systems.Extended memory from 1,024 KB to 1,088 KB is defined as the high memory area (HMA) and can be directly addressed by DOS using drivers.Even though extended memory above 1,088 KB can't be directly addressed by DOS or applications, DOS extenders that comply with the extended memory specification (XMS) provide access to extended memory.Extended memory is often used for RAM disks and disk caching routines.RENDERAS="SECT2"IDXID="w2050"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
Upper MemoryA somewhat generic term that excludes conventional memory.Upper memory can mean system memory (RAM between 640 KB and 1,024 KB), high memory area (RAM between 1,024 KB and 1,088 KB), extended memory (RAM above 1,024 KB) or expanded memory (also area above 1,024 KB).PAGENUM=178 ID="BP180"RENDERAS="SECT2"IDXID="w2051"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"IDXID="w2052"BOOK="_idx" COLLECTION="nw41" TIDREF="i1671"
High Memory Area (HMA)The first 64 KB of extended memory from 1,024 KB to 1,088 KB. It can be directly addressed by DOS in real mode with the use of device drivers (such as HIMEM.SYS).The high memory area provides additional memory directly addressed by DOS and functions like conventional memory.HMA is defined in the extended memory specification (XMS), and is only available on 80286, 80386, or 80486 CPUs with more than 1,024 KB of RAM.RENDERAS="SECT2"IDXID="w2053"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
System MemoryThe RAM between 640 KB and 1,024 KB that provides space for system use (including video adapters and other devices).System memory isn't normally addressed by DOS or applications, but 80386 and 80486 systems can use special control programs to make upper memory blocks (UMB) in system memory that are directly addressed by DOS.System memory is sometimes called high DOS memory, high memory, high memory area (HMA), or upper memory.RENDERAS="SECT2"IDXID="w2054"BOOK="_idx" COLLECTION="nw41" TIDREF="i4692"
Upper Memory Block (UMB)A block of system memory (between 640 KB and 1,024 KB) that is directly addressed by DOS and applications.UMBs are defined by the extended memory specification (XMS) and are created by a driver such as EMM386.EXE in DOS.The driver converts unused address spaces in the system memory to upper memory blocks.The upper memory blocks are then directly addressed by DOS and applications and can be loaded with applications, drivers, and terminate-and-stay-resident (TSR) programs.PAGENUM=179 ID="BP181"RENDERAS="SECT1"Memory allocationIDXID="w2055"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"The process of reserving specific memory locations in RAM for processes, instructions, and data.When a computer system is installed, the installer may allocate memory for items such as disk caches, RAM disks, extended memory, and expanded memory.Operating systems and application programs allocate memory to meet their requirements, but they can use only that memory actually available to them.Memory can be reallocated between resources to optimize performance. The proper memory allocation mix depends on the applications that are run.For example, a large disk cache that speeds up one application may slow down others because there is less conventional memory available.NetWare 4 has only one memory allocation pool, compared to NetWare 3, which has at least five allocation pools.After continuous operation of a NetWare 3 server, applications can run out of memory because some management routines don't release memory back to the operating system.Using one allocation pool, NetWare 4 alleviates these conditions.Memory management routines and third-party NLM programs operate more efficiently in NetWare 4 because management operations are reduced.NetWare 4 memory allocation routines raise the level of performance by eliminating certain conditions that often lead to inefficiencies.RENDERAS="SECT1"Memory boardIDXID="w2056"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"An add-on board that increases the amount of RAM within a personal computer.See also IDREF="FM11327""Memory"; IDREF="FM21738""RAM."PAGENUM=180 ID="BP182"RENDERAS="SECT1"ID="FM72408"Memory protectionIDXID="w2057"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"The structuring of memory resources in NetWare 4 that guards NetWare server memory from corruption by NLM programs.In NetWare 4, memory can be divided up into two domains: OS domain and OS_PROTECTED domain. By default, the operating system and NLM programs run in the OS domain. You can load the DOMAIN.NLM to create the OS_PROTECTED domain. Some NLM programs can be loaded in the OS_PROTECTED domain. NLM programs running in the OS_Protected domain have limited entry points to the OS domain, thus preventing unauthorized memory access. The OS_PROTECTED domain allows you to test your NLM programs without risking server memory corruption. Once you load an NLM in the OS_PROTECTED domain and find it safe, you can load it into the OS domain, where it can run most efficiently.To determine the recommended domain for third-party NLM programs, such as database and backup modules, check the documentation that came with the NLM.Another form of memory protection in NetWare 4 is paging.See also IDREF="FM37708""Domains"; IDREF="FM45002""Paging."RENDERAS="SECT1"Message packetIDXID="w2058"BOOK="_idx" COLLECTION="nw41" TIDREF="i2410"IDXID="w2059"BOOK="_idx" COLLECTION="nw41" TIDREF="i3169"A unit of information used in network communication.See IDREF="FM21658""Packet."RENDERAS="SECT1"ID="FM45790"Message Routing Group objectA leaf object that represents a group of messaging servers that can send and receive messages among themselves.See also IDREF="FM48140""Messaging Server object."PAGENUM=181 ID="BP183"RENDERAS="SECT1"Message systemIDXID="w2060"BOOK="_idx" COLLECTION="nw41" TIDREF="i2410"A communications protocol that runs on top of IPX. It provides an engine that allows a node on the network to send messages to other nodes.A set of APIs (application program interfaces) gives programs access to the message system.See also IDREF="FM16854""IPX."RENDERAS="SECT1"ID="FM48140"Messaging Server objectIDXID="w2061"BOOK="_idx" COLLECTION="nw41" TIDREF="i2428"A leaf object that represents a messaging server that resides on a NetWare server. A Messaging Server object is automatically created in the Directory tree when you install NetWare MHS on a NetWare server. The Messaging Server object is automatically placed in the same context as the NetWare Server object.The messaging server bundled with NetWare 4 is a NetWare Basic MHS server. It is an NLM that provides message delivery between users on a NetWare 4 LAN.Other types of messaging servers provide different types of connectivity, or operate in different environments. For example, a Global MHSTM messaging server supports communication across asynchronous links and with non-MHS environments, such as SMTP, SNADS, and X.400.A NetWare MHS messaging server picks up messages, which are either submitted by messaging applications (such as E-mail) or transferred from another messaging server, and delivers them to the recipients.For recipients whose mailboxes are local on the messaging server, the message is delivered to their mailboxes. Otherwise the messaging server transfers the message to another messaging server for eventual delivery to the recipient's mailbox.A messaging server can service an unlimited number of mailboxes. The amount of disk space available for mailboxes is the only limiting factor.RENDERAS="SECT1"PAGENUM=182 ID="BP184"MIB(Management Information Base) The entire set of objects that any service or protocol uses in SNMP.See IDREF="FM79303""Management Information Base."RENDERAS="SECT1"Migrated (M) attributeIDXID="w2062"BOOK="_idx" COLLECTION="nw41" TIDREF="i2448"A status flag, set automatically, that indicates a file is migrated.See also IDREF="FM85330""Attributes"; IDREF="FM55003""Data migration."RENDERAS="SECT1"Migration (operating system)IDXID="w2063"BOOK="_idx" COLLECTION="nw41" TIDREF="i2461"The conversion of servers from NetWare 2 or NetWare 3, or from another network operating system, to NetWare 4. (Do not confuse migration from one version of NetWare to another with data migration, which refers to moving files to near-line or offline storage devices. See IDREF="FM55003""Data migration.")See also IDREF="FM21704""Upgrade."RENDERAS="SECT1"Migration (protocol)IDXID="w2064"BOOK="_idx" COLLECTION="nw41" TIDREF="i2462"The conversion of a server, router, or network from IPX to NetWare Link Services ProtocolTM (NLSP), or from TCP/IP to Open Shortest Path First (OSPF) protocol.See also IDREF="FM16854""IPX"; IDREF="FM64684""NetWare Link Services Protocol"; IDREF="FM28062""Open Shortest Path First."RENDERAS="SECT1"ID="FM51647"MinorIDXID="w2065"BOOK="_idx" COLLECTION="nw41" TIDREF="i4425"IDXID="w2066"BOOK="_idx" COLLECTION="nw41" TIDREF="i3821"
 resourceIDXID="w2067"BOOK="_idx" COLLECTION="nw41" TIDREF="i2468"A category of data defined by the Target Service Agent and recognized by SBACKUP.A minor resource might be located in the directory structure below the selected major resource (for example, directories, subdirectories, or files).See also IDREF="FM24312""Backup"; IDREF="FM34549""Major resource"; IDREF="FM82095""Target Service Agent"; IDREF="FM67355""Transaction Tracking System."PAGENUM=183 ID="BP185"RENDERAS="SECT1"Mirrored Server Engine(MSEngine) The part of the SFT III operating system that handles nonphysical processes, such as the NetWare file system and theDirectory.See IDREF="FM96050""MSEngine."RENDERAS="SECT1"ID="FM95166"Mirrored server link IDXID="w2068"BOOK="_idx" COLLECTION="nw41" TIDREF="i2473"(MSL) A dedicated, 
high-speed connection between SFT III primary and secondary servers. The MSL manages server synchronization.The MSL is essentially a bus extension from the primary IOEngine to the secondary IOEngine. It requires similar boards in each server, directly connected by fiber-optic or other cables.LABEL="46" FLOAT="0"Mirrored Server LinkFILEREF="n41co52a.tif"To provide the fastest possible throughput, the mirrored server link should be a 32-bit, low latency, low CPU-utilizing board such as the NMSL board. Because of their slower speed, network boards such as the NE2000TM or the NE/2-32TM are recommended for use only as alternate MSL boards.PAGENUM=184 ID="BP186"For system redundancy, additional MSL boards and cabling may be installed in each server. This alternate MSL connection automatically takes over (without user intervention) if the active MSL connection fails.RENDERAS="SECT1"MirroringThe duplication of data from the NetWare partition on one hard disk to the NetWare partition on another hard disk.See IDREF="FM66029""Disk mirroring."RENDERAS="SECT1"MLID(Multiple Link Interface Driver) A device driver written to the ODI specification that handles the sending and receiving of packets to and from a physical or logical LAN medium.See IDREF="FM33398""Multiple Link Interface Driver."See also IDREF="FM33588""Open Data-Link Interface."RENDERAS="SECT1"ID="FM34781"Modify bitIDXID="w2069"BOOK="_idx" COLLECTION="nw41" TIDREF="i2494"A file attribute set by the operating system, when a file is changed, to indicate that data has been modified.The NetWare modify bit, called Archive Needed Attribute, appears as an "A" wherever file attributes are listed.When a backup is performed, SBACKUP checks to see whether modify bits are set, and backs up only those files that have their modify bit set.The following table shows how different types of backups handle the modify bit and process the files that aren't marked with the modify bit.COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="9*"COLNAME=3 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Type of backupCOLNAME=2 ROTATE="0" MOREROWS="0"Modify bit settingCOLNAME=3 ROTATE="0" MOREROWS="0"Treatment of non-modified files at time of next backup of this typeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"FullCOLNAME=2 ROTATE="0" MOREROWS="0"Clear after backupCOLNAME=3 ROTATE="0" MOREROWS="0"IncludeCOLNAME=1 ROTATE="0" MOREROWS="0"IncrementalCOLNAME=2 ROTATE="0" MOREROWS="0"Clear after backupCOLNAME=3 ROTATE="0" MOREROWS="0"ExcludeCOLNAME=1 ROTATE="0" MOREROWS="0"DifferentialCOLNAME=2 ROTATE="0" MOREROWS="0"Don't clear after backupCOLNAME=3 ROTATE="0" MOREROWS="0"ExcludeCOLNAME=1 ROTATE="0" MOREROWS="0"CustomCOLNAME=2 ROTATE="0" MOREROWS="0"As desiredCOLNAME=3 ROTATE="0" MOREROWS="0"As desiredPAGENUM=185 ID="BP187"See also IDREF="FM24312""Backup."RENDERAS="SECT1"Modify rightIDXID="w2070"BOOK="_idx" COLLECTION="nw41" TIDREF="i2495"A directory or file right that grants the right to change the attributes or name of a directory or file.See also IDREF="FM74455""Rights."RENDERAS="SECT1"MS Windows clientA workstation that boots with DOS and gains access to the network through eitherMARK=BULLETThe NetWare DOS Requester and its VLM programs (for NetWare 4)A NetWare shell (for NetWare versions earlier than NetWare 4)The computer also runs MS Windows and, with the client software, can perform networking tasks in the MS Windows environment. These tasks include mapping drives, capturing printer ports, sending messages, and changing contexts.See also IDREF="FM99174""Client."RENDERAS="SECT1"ID="FM96050"MSEngineIDXID="w2071"BOOK="_idx" COLLECTION="nw41" TIDREF="i2544"(Mirrored Server Engine) The part of the SFT III operating system that handles nonphysical processes, such as the NetWare file system, queue management, and the Directory.SFT III is split into two parts: the IOEngine (Input/Output Engine) and the MSEngine. The primary server and the secondary server each have a separate IOEngine, but they share the same MSEngine. PAGENUM=186 ID="BP188"The file system, receive buffers, and queue management system all reside in the MSEngine. Applications and NLM programs that do not address hardware directly can be mirrored by loading them in the MSEngine. If one server fails, applications and NLM programs in the MSEngine continue to run.The MSEngine keeps track of active network processes; it provides uninterrupted network service when the primary server fails and the secondary server takes over. During server switchoverMARK=BULLETOpen files stay openWorkstation requests that have reached the receive buffers are processed without delay Requests that have not reached the receive buffers are retried.Print requests that have reached the print queue remain in the queue until they can be servicedRequests that have not reached the queue are retried. If the print queue is assigned to a printer that is attached only to the failed server, print requests remain in the queue until the failed server is restored.RENDERAS="SECT1"MSL(Mirrored server link) A dedicated, high-speed connection between SFT III primary and secondary servers.See IDREF="FM95166""Mirrored server link."RENDERAS="SECT1"Multiple-byte characterIDXID="w2072"BOOK="_idx" COLLECTION="nw41" TIDREF="i2567"A single character made up of more than one byte.One byte allows 256 different characters. Since the number of ASCII characters equals 256, a computer can handle each ASCII character with one byte.Asian character sets, however, include more than 256 characters; in this case, a computer must use two bytes for each character.PAGENUM=187 ID="BP189"RENDERAS="SECT1"ID="FM33398"Multiple Link Interface Driver(MLID) A device driver written to the ODI specification that handles the sending and receiving of packets to and from a physical or logical LAN medium.See IDREF="FM33588""Open Data-Link Interface."RENDERAS="SECT1"ID="FM19052"Multiple name space support IDXID="w2073"BOOK="_idx" COLLECTION="nw41" TIDREF="i2565"IDXID="w2074"BOOK="_idx" COLLECTION="nw41" TIDREF="i2586"Allows various workstations running different operating systems to create their own familiar naming conventions.Different operating systems (DOS, OS/2, Macintosh, MS Windows, and UNIX) have different conventions for naming files. These conventions include name length, allowable characters, case-sensitivity, data and resource forks, length of extensions, multiple extensions, etc.With multiple name space support, each file stored on a given volume has a name that any workstation (running off of any operating system) can recognize. This name is stored in a file entry in the volume's DET.Volumes that support multiple name spaces use one file and directory entry for each name space supported. The same applies to directory names.For example, a NetWare server configured to support DOS and Macintosh filenames would generate two 128-byte file entries for every file.The name spaces supported on a volume are configurable. See also IDREF="FM32610""Name space support."RENDERAS="SECT1"Multiserver networkIDXID="w2075"BOOK="_idx" COLLECTION="nw41" TIDREF="i2570"IDXID="w2076"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"A single network that has two or more NetWare servers operating.On a multiserver network, users can access files from any NetWare server they have access rights to.A multiserver network isn't the same as an internetwork, where two or more networks are linked through a router.PAGENUM=188 ID="BP190"See also IDREF="FM24537""Internetwork"; IDREF="FM97740""Network numbering."PAGENUM=189 ID="BP191"NRENDERAS="SECT1"Name contextIDXID="w2077"BOOK="_idx" COLLECTION="nw41" TIDREF="i2581"IDXID="w2078"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"IDXID="w2079"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"The position of an object in the Directory tree.See IDREF="FM60364""Context."RENDERAS="SECT1"ID="FM32610"Name space supportIDXID="w2080"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"Name space support is provided by NLM files that allow you to store non-DOS filenames on a NetWare 3 or 4 server. Files appear in native mode to users at different types of workstations.Name space NLM files have a .NAM extension. (For example, MAC.NAM and OS2.NAM.)To provide name spaces for MARK=BULLETMacintosh. Load MAC.NAM.OS/2. Load OS2.NAM.FTAM. Load FTAM.NAM---an add-on module you purchase separately.NFS. Load NFS.NAM---an add-on module you purchase separately.To store any non-DOS file types on a NetWare volume, you must first load the name space NLM and then add the name space to the volume. Once the name space NLM is loaded, you must use the ADD NAME IDXID="w2081"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"IDXID="w2082"BOOK="_idx" COLLECTION="nw41" TIDREF="i2586"
SPACE console command to configure the volumes so you can store other types of file names.You only add a name space to a volume once by using the ADD NAME SPACE command. PAGENUM=190 ID="BP192"You don't need to add a name space to a volume each time the server comes up, so the ADD NAME SPACE command does not need to be placed in your AUTOEXEC.NCF file. Each time you mount a volume that you configured for additional name space support, (for example, each time you bring up the server), the corresponding name space module autoloads.When name space support is added to a volume, another entry is created in the directory table for the directory and file naming conventions of that name space (file system).For example, a volume that supports Macintosh files has the following for each Macintosh file:MARK=BULLETA DOS filename in the DOS name spaceA Macintosh filename in the Macintosh name spaceThese are illustrated in the following figure.LABEL="47" FLOAT="0"Macintosh Name Space SupportFILEREF="n40co18a.tif"Each volume assigned to support an additional name space type requires about twice as much memory as a volume without additional name space types because the server must cache the additional directory entries.PAGENUM=191 ID="BP193"Once a name space is added to a volume, the name space can be removed from the volume only by deleting the volume and re-creating it, or by using "BOOK="utlrfenu" COLLECTION="nw41"VREPAIR." (See Utilities Reference.) Name space modules (files with the *.NAM extension) should be stored with the NetWare server boot files so that you can add the additional name space to any volume, including the SYS volume.The NetWare installation procedure places the MAC.NAM and the OS.NAM files in the SYS:SYSTEM directory. If you purchase additional name spaces such as FTAM or NFS, consult that documentation to determine where the name space modules are placed.Related procedure: "BOOK="superenu" COLLECTION="nw41"Setting Up a Volume to Store Non-DOS Files" in Chapter 7 of Supervising the Network.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"ADD NAME SPACE," "BOOK="utlrfenu" COLLECTION="nw41"INSTALL," "BOOK="utlrfenu" COLLECTION="nw41"LOAD," and "BOOK="utlrfenu" COLLECTION="nw41"VREPAIR" in Utilities Reference.See also IDREF="FM19052""Multiple name space support"; IDREF="FM68484""NetWare Loadable Module."RENDERAS="SECT1"Named pipesIDXID="w2083"BOOK="_idx" COLLECTION="nw41" TIDREF="i2597"IDXID="w2084"BOOK="_idx" COLLECTION="nw41" TIDREF="i659"The basis for communication between a client and advanced client-server applications such as Microsoft* SQL Server* and Microsoft Comm Server* software. Client-server computing allows more effective use of computing resources, higher performance, greater flexibility, simpler upgrades, and, for some applications, greater reliability and data integrity.For NetWare ClientTM workstations, communication between client-server applications is implemented most frequently using the named pipes interprocess communication (IPC) protocol. RENDERAS="SECT1"NCP(NetWare Core Protocol) Procedures that a server's NetWare operating system follows to accept and respond to workstation requests.See IDREF="FM62017""NetWare Core Protocol."PAGENUM=192 ID="BP194"RENDERAS="SECT1"NCP Packet SignatureIDXID="w2085"BOOK="_idx" COLLECTION="nw41" TIDREF="i2622"IDXID="w2086"BOOK="_idx" COLLECTION="nw41" TIDREF="i3169"IDXID="w2087"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
An enhanced security feature that protects servers and workstations using NCPTM by preventing packet forgery.Without NCP Packet Signature installed, a user can pose as a more privileged user and send a forged NCP request to a NetWare server.By forging the proper NCP request packet, an intruder could gain the Supervisor object right and access to all network resources.NCP Packet Signature prevents packet forgery by requiring the server and the user's workstation to "sign" each NCP packet. The packet signature changes with every packet.NCP packets with incorrect signatures are discarded without breaking the workstation's connection to the server.However, an alert message about the invalid packet goes out to the error log, the affected workstation, and the server console. The alert message contains the login name and the station address of the affected workstation.If NCP Packet Signature is installed on the server and all of its workstations, it is virtually impossible to forge a valid NCP packet.RENDERAS="SECT1"NDS(NetWare Directory Services) A relational database that is distributed across your entire network.See IDREF="FM83674""NetWare Directory Services."RENDERAS="SECT1"ID="FM94818"NetBIOSIDXID="w2088"BOOK="_idx" COLLECTION="nw41" TIDREF="i2667"IBM's standard protocol for applications developed to run peer-to-peer communications on the IBM PC network and the token ring network. NetBIOS has become widely accepted as a standard for network interfacing.PAGENUM=193 ID="BP195"The NetWare ClientTM for DOS and MS Windows provides a NetBIOS driver that emulates the NetBIOS protocol. This emulator allows NetWare IPX to interface with the NetBIOS Interrupt 5Ch and an alternate interface, Interrupt 2Ah. The NetBIOS provided by Novell is an emulator because it does not transmit NetBIOS packets. Instead, NetBIOS packets are encapsulated in IPX packets, and the IPX packets are transmitted.The NetBIOS protocol was designed for small scale networks. While Novell has added functionality to the original specification, Novell NetBIOS emulation still works most effectively with small scale networks.If your network contains several thousand workstations and your LAN segments are interconnected with more than one router, use SPXTM instead of NetBIOS if your applications support SPX.RENDERAS="SECT1"NET.CFGA workstation boot file, similar to CONFIG.SYS in DOS, that contains configuration values that are read and interpreted when your workstation starts up.NET.CFG is created with an ASCII text editor and needs to be included on the workstation boot diskette with other boot files. NET.CFG replaces SHELL.CFG, used in earlier NetWare versions.The configuration values in NET.CFG adjust the operating parameters of the NetWare DOS Requester, IPX, and other workstation software.Applications such as database, multitasking, or NetBIOS (involved in peer-to-peer communications or distributed processing) may require parameter values different from the default values to function properly on the network.To learn which parameters you might need to modify, consult the setup reference for each application used on your network. Some network problems such as printing and file retrieval might also be solved by adjusting workstation parameters.RENDERAS="SECT1"PAGENUM=194 ID="BP196"
ID="FM11121"NETINFO.CFGIDXID="w2089"BOOK="_idx" COLLECTION="nw41" TIDREF="i2672"A NetWare server executable batch file, located on the NetWare partition of the server's hard disk.NETINFO.CFG is used to store LOAD and BIND commands associated with protocol configuration if you used the INETCFG utility to configure the protocols. If you have not used the INETCFG utility to configure the protocols, then the LOAD and BIND commands are placed in the AUTOEXEC.NCF file. Some of the configuration commands are written by the INETCFG utility.Never edit this file with a text editor. Improper maintenance causes your server to malfunction.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.See also IDREF="FM86375""Router."RENDERAS="SECT1"NetSync clusterIncludes one NetWare 4.1 server running NETSYNC4 and up to twelve NetWare 3.1x servers attached to it. See 
BOOK="ntsncenu" COLLECTION="nw41"Installing and Using NetSync. RENDERAS="SECT1"NetWare Client for DOS and MS WindowsIDXID="w2090"BOOK="_idx" COLLECTION="nw41" TIDREF="i2712"IDXID="w2091"BOOK="_idx" COLLECTION="nw41" TIDREF="i2712"Software that connects DOS and MS Windows workstations to NetWare networks and allows DOS and MS Windows users to share network resources. PAGENUM=195 ID="BP197"The core components of the NetWare DOS and MS Windows environment are four terminate-and stay-resident (TSR) programs, described in the following table:LABEL="9" PGWIDE=1 TOCENTRY="1" Key Components of the NetWare Client for DOS and MS WindowsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="24*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TSR programsCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Link Support LayerTM  (LSL.COM)COLNAME=2 ROTATE="0" MOREROWS="0"Puts the packaged requests from the IPXODI driver into the proper format for transmission on the particular physical network that the client workstations are running on.Also takes replies for the various client workstations from the network (using the network LAN driver), removes the network- specific information it has added, and passes the reply to IPXODI.COLNAME=1 ROTATE="0" MOREROWS="0"NetWare DOS Requester  (VLM.EXE)COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w2092"BOOK="_idx" COLLECTION="nw41" TIDREF="i2733"
A DOS-based client software that provides the interface between DOS and the network. It consists of individual modules that provide various network services and is loaded when you run the file STARTNET.BAT. This file also loads drivers that the NetWare DOS Requester needs in order to communicate with the network hardware.COLNAME=1 ROTATE="0" MOREROWS="0"ODI LAN driver  (NE2000.COM)COLNAME=2 ROTATE="0" MOREROWS="0"Takes requests from the LSL and sends them to the network. It also receives replies from the network and passes them to the LSL software. This LAN driver is specific to the network board installed in your client workstations.COLNAME=1 ROTATE="0" MOREROWS="0"Transport Protocol(IPXODI.COM)  (Internetwork Packet ExchangeTM Open Data- Link InterfaceTM)  SPX (Sequenced Packet Exchange. Included in IPXODI.COM)(TCPIP.COM)  (Transmission Control Protocol/Internet Protocol)COLNAME=2 ROTATE="0" MOREROWS="0"Delivers requests and replies between client workstations and the network.Also handles packet sequencing and acknowledgment for the client- server connection.Takes requests that the NetWare DOS Requester has determined are for the network, packages them with transmission information (such as their destination), and hands them to the LSL.RENDERAS="SECT1"PAGENUM=196 ID="BP198"ID="FM93979"NetWare Client for OS/2IDXID="w2093"BOOK="_idx" COLLECTION="nw41" TIDREF="i2710"IDXID="w2094"BOOK="_idx" COLLECTION="nw41" TIDREF="i2712"Software that connects OS/2 workstations to NetWare networks and allows OS/2 users to share network resources. NetWare ClientTM for OS/2MARK=BULLETDirects network requests from the workstation to the network.Allows application servers (such as SQL Server) and their workstations to communicate on the network without using a NetWare server.Users can run advanced distributed applications or back-end server engines on their OS/2 workstations.DOS and OS/2 users can access data on those application servers without using a NetWare server.A standalone computer running OS/2 is converted into an OS/2 client by adding a network board and installing the NetWare Client for OS/2 software.The NetWare Client installation program copies the NetWare Client program files, DLL files, network board drivers, and several utilities to a specified directory on your OS/2 machine.The installation program also modifies your CONFIG.SYS file so that the next time you reboot your machine, the NetWare Requester for OS/2 software is loaded automatically.See BOOK="ws_osenu" COLLECTION="nw41" NetWare Client for OS/2 User Guide.RENDERAS="SECT1"ID="FM62017"IDXID="w2095"BOOK="_idx" COLLECTION="nw41" TIDREF="i2715"
NetWare Core ProtocolIDXID="w2096"BOOK="_idx" COLLECTION="nw41" TIDREF="i2624"IDXID="w2097"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"
(NCP) Procedures that a server's NetWare operating system follows to accept and respond to workstation requests.The process of requesting service from a NetWare server begins in the workstation's RAM where the NetWare DOS Requester or NetWare Requester for OS/2 forms requests according to the definitions of the server's NCP.PAGENUM=197 ID="BP199"The NetWare Requester then hands the requests to the station's IPX communication protocol. IPX transmits the request to the server after attaching a header designating the source and destination.Upon receiving the request, the server removes the IPX header and reads the request.Because the NetWare Requester formed the request using the exact guidelines of a specific service protocol, the server handles the request according to the protocol rules, resulting in a proper response.NetWare Core Protocols exist for every service a station might request from a server.Common requests handled by NCP include creating or destroying a service connection, manipulating directories and files, opening semaphores, altering the Directory, and printing.See also IDREF="FM34819""Communication protocols"; IDREF="FM16854""IPX."RENDERAS="SECT1"ID="FM40161"NetWare Directory databaseIDXID="w2098"BOOK="_idx" COLLECTION="nw41" TIDREF="i2727"IDXID="w2099"BOOK="_idx" COLLECTION="nw41" TIDREF="i2716"
The database (commonly referred to as the Directory) that organizes NetWare Directory Services objects in a hierarchical tree structure called the Directory tree.See IDREF="FM83674""NetWare Directory Services."RENDERAS="SECT1"ID="FM61672"NetWare Directory partitionIDXID="w2100"BOOK="_idx" COLLECTION="nw41" TIDREF="i2718"A logical division of the NetWare Directory database. A Directory partition forms a distinct unit of data in the Directory tree that you use to store and replicate Directory information.Each Directory partition consists of a container object, all objects contained in it, and data about those objects. Directory partitions don't include any information about the file system or the directories and files contained there.The following figure shows the default Directory partition created for the first server installed and for all the new Organizational Units in which NetWare 4 servers were installed.PAGENUM=198 ID="BP200"LABEL="48" FLOAT="0"Example of Default Directory PartitionsFILEREF="n41co67a.tif"Under NDS, an object resides in only one Directory partition, but through distributed operations, the object can be accessed from any point on the network.To optimize access to different areas of the Directory, each Directory partition can be replicated and stored at many locations.Directory partition replication improves access to Directory information and provides the Directory with fault tolerance. Since a Directory partition can be replicated at several locations, damage to one of the Directory replicas doesn't need to interrupt access to partition information.Furthermore, the Directory allows Directory replicas to be designated as read/write or read-only, thus controlling the introduction of updates into the system.The tree of Directory partitions is transparent to Directory users (unless they are running Partition Manager); users usually see only a global tree of Directory objects.PAGENUM=199 ID="BP201"Replicas of Directory partitions are stored on NetWare servers. Multiple replicas of different Directory partitions can be stored on the same NetWare server; none of the Directory partitions need to be contiguous to each other.See also IDREF="FM83674""NetWare Directory Services"; IDREF="FM27324""NetWare Directory replica"; Chapter 5, "BOOK="superenu" COLLECTION="nw41"Managing the NetWare Directory Tree," of Supervising the Network.RENDERAS="SECT1"ID="FM27324"NetWare Directory replicaIDXID="w2101"BOOK="_idx" COLLECTION="nw41" TIDREF="i2719"IDXID="w2102"BOOK="_idx" COLLECTION="nw41" TIDREF="i2718"A copy of a NetWare Directory partition.For the Directory database to be distributed across a network, it must be stored on many servers. Rather than storing a copy of the whole Directory database on each server, Directory replicas of each Directory partition are stored on many servers throughout the network.You can create an unlimited number of Directory replicas for each Directory partition and store them on any server.RENDERAS="SECT2"Purpose of Directory ReplicasDirectory replicas serve two purposes:MARK=BULLETTo eliminate any single point of failureFor example, if a disk crashes or a server goes down, a Directory replica on another server can still authenticate users to use the network and can provide information on objects in that Directory partition.With the same information distributed on several servers, you aren't dependent on any single server to authenticate who can use the network.You can store a Directory replica of one Directory partition with a Directory replica of another Directory partition on the same server.Replication of the Directory doesn't provide fault tolerance for your file system. Only Directory information about objects is replicated. To provide fault tolerance for your files, you must mirror or duplex your hard disks and be sure TTS is enabled. (See IDREF="FM60634""Disk duplexing"; IDREF="FM66029""Disk mirroring"; IDREF="FM67355""Transaction Tracking System.")To provide faster access to information for users across a WAN linkPAGENUM=200 ID="BP202"For example, if a WAN link is used to access information, you can decrease access time and network traffic by placing a Directory replica containing the needed information on a server that users can access locally.Distributing Directory replicas among servers lets you access information more quickly and reliably because the information comes from the nearest available server.RENDERAS="SECT2"Types of Directory replicasMARK=BULLETMaster replica. Although many Directory replicas can exist in the Directory, only one is the master replica. Use it to create a new Directory partition in the Directory database, or to read and update Directory information, such as adding or deleting objects.Read/write replica. Use to read or update Directory information (such as adding or deleting objects).Read-only replica. Use to view, but not to modify, Directory information.Subordinate replica. You cannot modify this type of Directory replica. NDS automatically places a subordinate replica on the server if the parent Directory partition has either a master, read/write, or read-only replica on the server and the child Directory partition does not.If you add a read/write or read-only replica of the child Directory partition to the server, the subordinate replica disappears.RENDERAS="SECT2"IDXID="w2103"BOOK="_idx" COLLECTION="nw41" TIDREF="i2719"IDXID="w2104"BOOK="_idx" COLLECTION="nw41" TIDREF="i4355"
Synchronization of Directory replicasTo maintain its fault tolerance, the replicas of a Directory partition are periodically (and automatically) updated, or synchronized.When changes are made in one Directory replica, synchronization ensures that those changes are made in all other Directory replicas of that partition, so that each Directory partition's replica contains the same data as the other Directory replicas.PAGENUM=201 ID="BP203"Network supervisors cannot control how often Directory replica synchronization occurs; NDS handles Directory replica synchronization automatically. But, supervisors can manually synchronize Directory replicas using the Partition Manager graphical utility, which is launched from NetWare Administrator, or using PARTMGR.Related Utilities: "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" and "BOOK="utlrfenu" COLLECTION="nw41"PARTMGR"See also IDREF="FM61672""NetWare Directory partition"; Chapter 5, "BOOK="superenu" COLLECTION="nw41"Managing the NetWare Directory Tree," of Supervising the NetworkRENDERAS="SECT1"ID="FM83674"
NetWare Directory ServicesIDXID="w2105"BOOK="_idx" COLLECTION="nw41" TIDREF="i2727"(NDS) A relational database that is distributed across your entire network. NDS provides you with global access to all network resources to which you have been given rights, regardless of where they are physically located.NDS treats all network resources as objects in a distributed database known as the NetWare Directory database, also referred to as the Directory.All users log in to a multiserver network and view the entire network as a single information system. This single view provides for increased productivity and reduced administrative costs.NDS helps you manage Directory resources such as NetWare servers and volumes, but it doesn't provide control over the file system (files and file directories). Graphical and text utilities are available that help you control the file system.RENDERAS="SECT2"AuthenticationWhen a user accesses resources on the network, background authentication processes verify that the user has rights to use those resources.Authentication allows users (who have logged in) to access any server, volume, or printer to which they have rights. User trustee rights restrict the user's access within the network. (See also IDREF="FM59413""Authentication"; IDREF="FM23712""Login scripts"; IDREF="FM74455""Rights"; IDREF="FM26134""Trustee.")PAGENUM=202 ID="BP204"RENDERAS="SECT2"IDXID="w2106"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"IDXID="w2107"BOOK="_idx" COLLECTION="nw41" TIDREF="i2727"
ObjectsIDXID="w2108"BOOK="_idx" COLLECTION="nw41" TIDREF="i2727"
Within NDS, objects represent network resources. An object consists of categories of information, called properties, and the data in those properties. The information is stored in the NetWare Directory database.Some objects represent physical entities. For example, a User object represents a user and a Printer object represents a printer.Some objects represent logical entities, such as groups and print queues.Other objects, such as the Organizational Unit object, help you organize and manage objects. (See IDREF="FM13600""Object.")RENDERAS="SECT2"IDXID="w2109"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"
The Directory TreeNDS operates in a logical organization called the Directory tree. It is called a Directory tree because objects are stored in a hierarchical tree structure, starting with a root object and branching out. (See IDREF="FM69136""Directory tree.")RENDERAS="SECT2"IDXID="w2110"BOOK="_idx" COLLECTION="nw41" TIDREF="i2718"
Directory PartitionsTo make it more manageable, the NetWare Directory database is divided into smaller portions called Directory partitions. Directory partitions are created by default when you install NetWare 4 on a server in a new context in the Directory tree. (See IDREF="FM61672""NetWare Directory partition.")RENDERAS="SECT2"IDXID="w2111"BOOK="_idx" COLLECTION="nw41" TIDREF="i2719"
Directory ReplicasFor NDS to be distributed across a network, the Directory database must be stored on many servers. Rather than have a copy of the whole Directory database on each server, Directory replicas of each Directory partition are stored on many servers throughout the network.Directory partition replication improves access and provides the Directory with fault tolerance. Since a Directory partition can be replicated at several locations, damage to one of the Directory replicas doesn't need to interrupt access to the Directory partition information. (See IDREF="FM27324""NetWare Directory replica.")RENDERAS="SECT2"PAGENUM=203 ID="BP205"Time SynchronizationTime synchronization establishes the order of events in NDS. Whenever an event occurs in the Directory, such as a password changed or an object renamed, NDS requests a time stamp so that the Directory replicas are updated in the correct order. (See IDREF="FM65772""Time synchronization.")RENDERAS="SECT2"IDXID="w2112"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
Bindery CompatibilityNDS replaces the bindery, which served as the system database in earlier versions of NetWare. To provide compatibility with earlier, bindery-based versions of NetWare that may co-exist with NDS on the network, NetWare 4 features bindery services. (See IDREF="FM26082""Bindery services.")RENDERAS="SECT1"NetWare Directory Services management requestIDXID="w2113"BOOK="_idx" COLLECTION="nw41" TIDREF="i1097"IDXID="w2114"BOOK="_idx" COLLECTION="nw41" TIDREF="i2727"A request that controls the physical distribution of the Directory database. Through these requests, system administrators can create new Directory partitions and manage their Directory replicas.The following requests are supported:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"RequestCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Add replicaCOLNAME=2 ROTATE="0" MOREROWS="0"Adds a Directory replica of an existing Directory partition to a server.COLNAME=1 ROTATE="0" MOREROWS="0"Delete replicaCOLNAME=2 ROTATE="0" MOREROWS="0"Deletes a Directory replica from a server.COLNAME=1 ROTATE="0" MOREROWS="0"List replicasCOLNAME=2 ROTATE="0" MOREROWS="0"Lists the Directory replicas stored by a server.COLNAME=1 ROTATE="0" MOREROWS="0"Change replica typeCOLNAME=2 ROTATE="0" MOREROWS="0"Changes Directory replica type to master, read/write, or read-only.COLNAME=1 ROTATE="0" MOREROWS="0"Send updates to other replicasCOLNAME=2 ROTATE="0" MOREROWS="0"Sends updated information from the current master replica to all replicas of the Directory partition.COLNAME=1 ROTATE="0" MOREROWS="0"Receive updates from other replicasCOLNAME=2 ROTATE="0" MOREROWS="0"Updates the current master replica with information from all the replicas of the Directory partition. COLNAME=1 ROTATE="0" MOREROWS="0"Create a new partitionCOLNAME=2 ROTATE="0" MOREROWS="0"Splits a Directory partition into two at a specified object.COLNAME=1 ROTATE="0" MOREROWS="0"Merge partitionCOLNAME=2 ROTATE="0" MOREROWS="0"Joins the Directory partition at the specified objects.COLNAME=1 ROTATE="0" MOREROWS="0"Abort partition operationCOLNAME=2 ROTATE="0" MOREROWS="0"Aborts the creating of a new Directory partition or the merging of a Directory partition.PAGENUM=204 ID="BP206"See also IDREF="FM61672""NetWare Directory partition"; IDREF="FM27324""NetWare Directory replica."RENDERAS="SECT1"NetWare Directory Services requestA request made to the Directory database by users or network supervisors. NDS requests can be divided into three types:MARK=BULLETDirectory access requests. Requests submitted by users who are accessing or network supervisors who are managing the Directory database's contents.These requests support the Directory database's interface and allow objects to be created, modified, and retrieved.Directory access control requests. Requests that set access rights to Directory objects. In this respect, directory access rights resemble file access rights.Directory management requests. Requests submitted by network supervisors who manage the Directory database's physical distribution, such as partitioning.RENDERAS="SECT1"ID="FM21900"NetWare DOS Requester IDXID="w2115"BOOK="_idx" COLLECTION="nw41" TIDREF="i2733"A group of files that provide NetWare support for DOS and MS Windows client workstations. These files consist of a number of VLMTM programs and a single executable file (VLM.EXE) which manages operation of the .VLM files.PAGENUM=205 ID="BP207"RENDERAS="SECT2"Three Layer StructureIDXID="w2116"BOOK="_idx" COLLECTION="nw41" TIDREF="i2733"
The .VLM files have been grouped into the following three layers:MARK=BULLETDOS Redirection LayerService Protocol LayerTransport Protocol LayerThe following figure shows how these layers and modules fit together:LABEL="49" FLOAT="0"IDXID="w2117"BOOK="_idx" COLLECTION="nw41" TIDREF="i2733"NetWare DOS Requester Layers and ModulesFILEREF="n40co22a.tif"PAGENUM=206 ID="BP208"RENDERAS="SECT2"IDXID="w2118"BOOK="_idx" COLLECTION="nw41" TIDREF="i2733"
DOS Redirection Layer This layer provides DOS file services through the DOS redirector; its VLM program is REDIR.VLM, which performs all the DOS-specific callouts.Previously, NETX provided its own file services. The NetWare DOS Requester architecture uses the DOS redirector for most file services.RENDERAS="SECT2"Service IDXID="w2119"BOOK="_idx" COLLECTION="nw41" TIDREF="i2733"
Protocol 
LayerThis layer consists of the following parallel services:LABEL="10" PGWIDE=1 TOCENTRY="1" Key Components of the NetWare DOS and MS Windows ClientCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="24*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Protocol layer service and moduleCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare Services  NWP.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"NWP, the NetWare protocol multiplexor, handles each particular network implementation through these child VLM programs:MARK=BULLETBIND.VLM for NetWare 2 and 3 bindery serversNDS.VLM for NetWare 4 NDS serversPNW.VLM for Personal NetWare (NetWare desktop) serversThe NWP services also include logins and logouts, broadcast messages, and establishing and destroying connections.COLNAME=1 ROTATE="0" MOREROWS="0"Security Services  RSA.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"RSA (Rivest, Shamir, and Adleman, developers of this particular public key encryption system) provides system-level background authentication for the workstation.NetWare uses this encryption system to strengthen user authentication and access control functions.COLNAME=1 ROTATE="0" MOREROWS="0"File Services  FIO.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"FIO, the file input/output module, is a separate-but-parallel piece that implements a basic file-transfer protocol. This includes cached or noncached read/write functionality, burst mode-based read/write, and large internet packet read/write functionality.The Packet BurstTM protocol in FIO.VLM is based on ODI interconnectivity strategy and is referred to as PBODI. This functionality allows users to choose performance over memory use and vice versa.COLNAME=1 ROTATE="0" MOREROWS="0"Print Services  PRINT.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"PRINT provides printing services using the FIO module for its file writes. Print redirection is handled in the following ways, depending on entries in the NET.CFG file:MARK=BULLETNoncachedCachedRedirected to the server through Packet Burst protocolPrinter redirection using FIOPAGENUM=207 ID="BP209"RENDERAS="SECT2"Transport Protocol LayerThis layer is responsible for maintaining connections, providing packet transmissions between connections, and performing other transport-specific functions.The IPXNCP module uses the IPX protocol as a transport mechanism.The AUTO.VLM module reconnects a client workstation to a server and rebuilds the workstation's environment (excluding file-specific items) to its original state.RENDERAS="SECT2"VLM ManagerPAGENUM=208 ID="BP210"The VLM Manager (VLM.EXE) controls communication and memory issues between the individual VLM software. It is responsible for loading the required modules and for disbursing requests to individual modules. Thus, instead of loading NETX, EMSNETX, XMSNETX, or BNETX, the user loads only the VLM.EXE program.IDXID="w2120"BOOK="_idx" COLLECTION="nw41" TIDREF="i4770"
The VLM Manager decides whether a given VLM program uses expanded memory, extended memory, conventional memory, or any other memory type supported, without affecting the individual VLM programs.RENDERAS="SECT2"Connection Table IDXID="w2121"BOOK="_idx" COLLECTION="nw41" TIDREF="i788"
ManagerThe Connection Table Manager (CONN.VLM) spans all the layers of the NetWare DOS Requester architecture.CONN allows client workstations running the NetWare DOS Requester to establish a configurable number of connections with multiple NetWare servers.RENDERAS="SECT2"Backward Compatibility with NETX ApplicationsIDXID="w2122"BOOK="_idx" COLLECTION="nw41" TIDREF="i2733"
The NETX.VLM program provides backwards compatibility with NETX and other older versions of the shell. Therefore, you do not need to run NETX or other versions of the shell with the NetWare DOS Requester.The following figure shows a comparison of the NETX and the NetWare DOS Requester architectures:PAGENUM=209 ID="BP211"LABEL="50" FLOAT="0"Comparison of NETX and NetWare DOS RequesterFILEREF="n41co15a.tif"The NetWare DOS Requester offers several improvements over NETX:MARK=BULLETProvides a modular architecture that has advantages for current and future applicationsTakes advantage of memory-swapping technology and DOS redirection capabilityIncludes the Packet Burst protocol and LIPSupports the installed base of NetWare users by providing backward compatibility with NETXSupports NDS architecture in NetWare 4 softwarePAGENUM=210 ID="BP212"RENDERAS="SECT2"File and Print ServicesIDXID="w2123"BOOK="_idx" COLLECTION="nw41" TIDREF="i2895"
Previously, the NetWare shell for DOS intercepted requests for DOS services. At the client workstations, the NetWare shell (NETX) software hooked interrupts in front of DOS and provided network services for files and printing.The NetWare DOS Requester takes advantage of DOS redirection to provide file and print services. It also uses NetWare shell technology to add features to DOS and provide compatibility with applications that run on the NetWare shell software.RENDERAS="SECT2"Memory UsageIDXID="w2124"BOOK="_idx" COLLECTION="nw41" TIDREF="i2733"IDXID="w2125"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
The NetWare DOS Requester works with extended memory, expanded memory, and conventional memory.The following figure illustrates how memory is addressed in personal computers running DOS.PAGENUM=211 ID="BP213"LABEL="51" FLOAT="0"IDXID="w2126"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"MemoryFILEREF="n40co16a.tif"The VLM.EXE program automatically selects the best possible memory use: extended memory first, expanded memory second, and conventional memory only in the absence of enhanced memory options. See also BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User Guide.PAGENUM=212 ID="BP214"RENDERAS="SECT1"ID="FM64684"NetWare Link Services Protocol(NLSP) A link state routing protocol designed by Novell for IPX internetworks.NLSPTM is derived from IS-IS (Intermediate System-to-Intermediate System), the link state routing protocol developed by the International Standards Organization (ISO). Like IS-IS, NLSP transfers routing information between routers and makes routing decisions based on that information.NLSP routers exchange link information such as network connectivity, path costs, IPX network numbers, media types, etc. By exchanging this information with its peer routers, each router builds and maintains a complete logical map of the network.IDXID="w2127"BOOK="_idx" COLLECTION="nw41" TIDREF="i2754"
Unlike RIP and SAP, which periodically broadcast routing and service information, NLSP multicasts routing information only when a change occurs in a route or service on the network.To communicate with NetWare clients, NLSP routers use RIP.See also IDREF="FM63052""Link state."RENDERAS="SECT1"ID="FM68484"NetWare Loadable ModuleIDXID="w2128"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"(NLM) A program you can load and unload from server memory while the server is running. (Some NLM programs are loaded automatically because other NLM programs can't run without them.)When loaded, an NLM program is dynamically linked to the operating system, and the NetWare server allocates a portion of memory to it.The amount of memory an NLM program uses depends on the task. Some tasks make calls that cause the operating system to allocate more memory.The NLM uses the memory to perform a task, and then returns control of the memory to the operating system when the NLM is unloaded.When an NLM is unloaded, all allocated resources are returned to the operating system.NetWare 4 has four types of NLM programs:PAGENUM=213 ID="BP215"MARK=BULLETDisk drivers (.DSK extension) control communication between the operating system and hard disks.You can load and unload disk drivers while the server is running.LAN drivers (.LAN extension) control communication between the operating system and the network boards.You can load and unload LAN drivers while the server is running and users are logged in.Management utilities and server applications modules (.NLM extension) allow you to monitor and change configuration options.For example, you can run VREPAIR on a dismounted volume, add disk space to a mounted volume, or surface test a disk drive while the NetWare server is running.Once you finish your tasks, you can unload the utility and free memory for other server functions.Name space support (.NAM extension) allows non-DOS naming conventions to be stored in the directory and file naming system.Some NLM programs, such as utilities, can be loaded, used, and then unloaded. Other NLM programs, such as LAN driver and disk driver NLM programs, must be loaded every time the server is booted.NCF files (STARTUP.NCF and AUTOEXEC.NCF) allow you to store NLM commands that you want loaded every time the NetWare server is booted.Most NLM programs released with NetWare 4 are copied to SYS:SYSTEM during installation. As you acquire additional NLM programs, decide where you want to copy them. The operating system must be able to find the NLM programs when a LOAD command is issued.NLM programs can be copied to any of the following areas:MARK=BULLETThe SYS:SYSTEM directoryAny network directory on the NetWare serverPAGENUM=214 ID="BP216"A DOS drive of the NetWare serverRelated utilities: "BOOK="utlrfenu" COLLECTION="nw41"LOAD," "BOOK="utlrfenu" COLLECTION="nw41"UNLOAD," and "BOOK="utlrfenu" COLLECTION="nw41"SEARCH" in Utilities Reference.See also IDREF="FM72737""Loading and unloading"; IDREF="FM72408""Memory protection."RENDERAS="SECT1"IDXID="w2129"BOOK="_idx" COLLECTION="nw41" TIDREF="i2312"IDXID="w2130"BOOK="_idx" COLLECTION="nw41" TIDREF="i2945"
NetWare managed nodeIDXID="w2131"BOOK="_idx" COLLECTION="nw41" TIDREF="i2689"A NetWare 4 server that has the NetWare Management AgentTM software enabled, making more information available to management console software than is available with IPX/SPX function calls.RENDERAS="SECT1"NetWare Management AgentIDXID="w2132"BOOK="_idx" COLLECTION="nw41" TIDREF="i2761"IDXID="w2133"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"A group of NLM programs that provide server statistics and notify the NetWare Management SystemTM (NMS) console of alarm conditions.When installed on each server in the network, NetWare Management Agent allows you to monitor, manage, and maintain all servers from a central console.For example, with NetWare Management Agent software, you canMARK=BULLETView the configuration of a server, including NLM programs installed, printers and print queues, hard disks and disk controllers, and LAN driversMonitor server traffic and server memory useSpecify alarm settings for server errors and eventsNetWare Management Agent provides a graphical representation of all managed objects and their attributes, including a server's hardware, software, or data components.RENDERAS="SECT1"ID="FM10590"
NetWare MHS ServicesIDXID="w2134"BOOK="_idx" COLLECTION="nw41" TIDREF="i2765"Services that allow users to communicate electronically across a network. Using messaging services, users can exchange electronic mail, share calendars, schedule facilities, etc.PAGENUM=215 ID="BP217"To provide messaging services, NetWare uses a messaging server, a Distribution List object, a Message Routing Group object, an External Entity object, and a Postmaster.RENDERAS="SECT1"ID="FM38207"IDXID="w2135"BOOK="_idx" COLLECTION="nw41" TIDREF="i2769"
NetWare Name Service(NNS) A naming service designed to provide more transparent access to resources in NetWare installations.NNS was a predecessor to NDS, and consisted of a set of specialized utilities designed to work with existing NetWare 2 and NetWare 3 networks.Using NNS, users could more easily log in to multiple file servers and print to specific print queues, and network administrators could more easily manage users and groups on multiserver networks.NNS is no longer available or supported.See also IDREF="FM83674""NetWare Directory Services."RENDERAS="SECT1"ID="FM73509"NetWare Networked File System(NetWare NFS) Software that transparently integrates UNIX systems with NetWare 4 file systems and resources to give UNIX users access to the NetWare environment from their native operating system.RENDERAS="SECT1"NetWare NFSSoftware that transparently integrates UNIX systems with NetWare 4 file systems.See IDREF="FM73509""NetWare Networked File System."RENDERAS="SECT1"ID="FM49817"NetWare operating systemIDXID="w2136"BOOK="_idx" COLLECTION="nw41" TIDREF="i2689"The network operating system developed by Novell, Inc. NetWare runs on the server and provides several functions to the network and the applications running on it, includingMARK=BULLETFile and record lockingSecurityPAGENUM=216 ID="BP218"Print spoolingInterprocess communicationsThe NetWare operating system also determines performance, multivendor support, and reliability of the network.RENDERAS="SECT1"NetWare partition (disk)A partition created on each network hard disk, from which NetWare volumes are created.NetWare disk partitions are not related to NetWare Directory partitions. Disk partitions are subdivisions of a hard disk. A Directory partition is a subtree within the Directory tree. (See IDREF="FM61672""NetWare Directory partition.")See IDREF="FM76186""Disk partition."RENDERAS="SECT1"ID="FM87820"NetWare Peripheral ArchitectureIDXID="w2137"BOOK="_idx" COLLECTION="nw41" TIDREF="i2776"(NPA) An extension of the NetWare 4 Media Manager (a database built into NetWare for managing storage devices and media). NPA provides broader and more flexible driver support for host adapters and storage devices.NPA separates NetWare driver support into two components: a HAM and a CDM. The HAM drives the host adapter hardware. The CDM drives storage devices or autochangers attached to a host adapter bus.Instead of .DSK files, you can load .HAM and .CDM files when available for your adapter and devices. The integrated architecture of HAMs and CDMs may provide better performance, especially for CD-ROM drives and magneto-optical disk drives.Loading HAMs and CDMs is much like loading other device drivers, but instead of loading one .DSK file for both the adapter and device, you load one .HAM file for the adapter and one .CDM file for each device attached to the adapter. PAGENUM=217 ID="BP219"When you want to connect a new hardware device to the host bus adapter, you need to load only the appropriate CDM for that hardware device (in addition to the HAMs and CDMs already loaded and assuming a compatible adapter is installed).A brief description of some NPA components follows:RENDERAS="SECT2"Media ManagerIDXID="w2138"BOOK="_idx" COLLECTION="nw41" TIDREF="i2364"A database built into NetWare that keeps track of all peripheral storage devices and media attached to NetWare servers, and allows applications to gain access and get information.The Media Manager receives application I/O requests and converts them to messages compatible with the NPA architecture.RENDERAS="SECT2"IDXID="w2139"BOOK="_idx" COLLECTION="nw41" TIDREF="i2776"
Host Adapter Module (HAM)The driver component associated with the host adapter hardware. HAMs are adapter-specific. For example, if a third-party adapter is installed in the server, a HAM developed specifically for that adapter must be installed during installation of NetWare 4 custom installation (not a simplified installation). HAMs provide the functionality to route requests to the bus where a specified device is attached.RENDERAS="SECT2"IDXID="w2140"BOOK="_idx" COLLECTION="nw41" TIDREF="i2776"
Host Adapter Interface (HAI)A set of APIs within the NPA that provide an interface for HAMs to communicate with the Media Manager.RENDERAS="SECT2"IDXID="w2141"BOOK="_idx" COLLECTION="nw41" TIDREF="i2776"
Custom Device Module (CDM)The driver component associated with storage devices attached to the host adapter. CDMs are device-specific. For example, if there are three storage devices attached to the host adapter, a specific CDM for each device must be installed with NetWare 4 during a custom installation (not a simplified installation). RENDERAS="SECT2"IDXID="w2142"BOOK="_idx" COLLECTION="nw41" TIDREF="i2776"
Custom Device Interface (CDI)A set of APIs within the NPA that provides an interface for CDMs to communicate with the Media Manager.RENDERAS="SECT1"PAGENUM=218 ID="BP220"ID="FM46616"NetWare protocols and transportsIDXID="w2143"BOOK="_idx" COLLECTION="nw41" TIDREF="i4567"IDXID="w2144"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"The components of NetWare software that allow client workstations to communicate and be understood on the network.A protocol manages data and a transport manages application messages. A protocol and transport can be provided by one piece of software or by many.In order for client workstations to communicate on the network, they must use a protocol identical to the one used on the network. However, workstations can be configured to use multiple protocols.The NetWare Client software provides the following standard protocols:MARK=BULLETAddress Resolution Protocol (ARP)BOOTP (Provides TCP/IP configuration information)Internet Control Message Protocol (ICMP)Internet Protocol (IP)IPX/SPX Management Information Base (MIB)NetBIOSReverse Address Resolution Protocol (RARP)Remote Program Load (RPL)System Network Architecture (SNA)Simple Network Management Protocol (SNMP)Transmission Control Protocol (TCP)User Datagram Protocol (UDP)Xerox Network System (XNS)PAGENUM=219 ID="BP221"See also IDREF="FM81485""Address Resolution Protocol"; IDREF="FM19375""BOOTP"; IDREF="FM97442""Internet Control Message Protocol"; IDREF="FM32350""Internet Protocol"; IDREF="FM16854""IPX"; IDREF="FM79303""Management Information Base"; IDREF="FM94818""NetBIOS"; IDREF="FM24801""Reverse Address Resolution Protocol"; IDREF="FM88537""Remote Program Load."; IDREF="FM94361""Simple Network Management Protocol";IDREF="FM60628""System Network Architecture"; IDREF="FM32342""Transmission Control Protocol"; IDREF="FM12693""User Datagram Protocol"; IDREF="FM89838""Utilities." RENDERAS="SECT1"NetWare IDXID="w2145"BOOK="_idx" COLLECTION="nw41" TIDREF="i2788"
RuntimeIDXID="w2146"BOOK="_idx" COLLECTION="nw41" TIDREF="i4164"IDXID="w2147"BOOK="_idx" COLLECTION="nw41" TIDREF="i4165"IDXID="w2148"BOOK="_idx" COLLECTION="nw41" TIDREF="i2689"
A single-user version of the NetWare 4 operating system that provides NetWare services to clients of NLM programs.RENDERAS="SECT2"Benefits of a Runtime ServerNetWare RuntimeTM is a network server platform supporting front-end or back-end applications as well as basic NLM services such as communication services, database servers, electronic mail, and other third-party applications.NLM application developers have the flexibility to determine which client services are available in their product.NLM programs, loaded on a NetWare Runtime server, provide client connection services (using IPX, SPX, AppleTalk, or TCP/IP).RENDERAS="SECT2"How Runtime WorksNetwork clients attach to the NLM that runs on top of NetWare Runtime. The NLM provides all services required by the client using NetWare application program interfaces (APIs).Specific NetWare services are available to clients only through the NLM applications which serve those clients. The NLM program implements and manages any required client services.The following figure shows how NetWare Runtime functions:PAGENUM=220 ID="BP222"LABEL="52" FLOAT="0"NetWare RuntimeFILEREF="n40co49a.tif"For example, a database NLM application may provide a client with login connections (including authentication), file services, data access, and disconnect services.Other NetWare services can be built into NLM applications to provide additional functionality.RENDERAS="SECT2"Limitations of a Runtime ServerOnly one user can log in to the NetWare Runtime server at a time. Normally, the network supervisor logs in for administrative purposes using the single allowed NetWare Core Protocol (NCP) connection.RENDERAS="SECT2"Utilities That Don't Apply to a Runtime ServerThough all NetWare 4 utilities and commands are available on a Runtime server, some don't apply or wouldn't be used because of the server's single-user environment.PAGENUM=221 ID="BP223"You aren't likely to use the following utilities:TYPE="VERT"CAPTUREDCONFIGNMENUNPRINTPCONSOLEPRINTCONPRINTDEFPSCSENDSETTTSSYSTIMEWSUPDATEIn addition to utilities, you don't need several network supervisor commands, such as commands associated with creating or modifying login scripts or menus, as well as those related to workstation management.RENDERAS="SECT2"Netware Runtime InstallationThe procedures for installing a NetWare 4 Runtime server are the same as for any NetWare 4 server.For information on how to install a Runtime server, see BOOK="instlenu" COLLECTION="nw41"Installation. For information on how to upgrade a Runtime server, see BOOK="upmigenu" COLLECTION="nw41"Upgrade.RENDERAS="SECT1"ID="FM34874"NetWare serverIDXID="w2149"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"A computer that runs NetWare operating system software.A NetWare server regulates communications among personal computers attached to it and to shared resources, such as printers.A NetWare 4.1 server must have at least one hard disk, either internal or external, and a recommended minimum 8 MB of RAM. The server must also contain at least one network board.PAGENUM=222 ID="BP224"NetWare servers running NetWare 4.1 can be used only as dedicated servers, except NetWare 4.1 for OS/2 servers, which are nondedicated only.RENDERAS="SECT2"IDXID="w2150"BOOK="_idx" COLLECTION="nw41" TIDREF="i501"IDXID="w2151"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"IDXID="w2152"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
Booting a NetWare ServerYou can set up a NetWare server to automatically boot by placing an AUTOEXEC.BAT file on the server's boot diskette or by placing it on a DOS partition on the NetWare server's DOS-addressable internal hard disk.The AUTOEXEC.BAT file executes the SERVER.EXE command, in most cases.To complete the boot process, NETINFO.SYS loads the LAN drivers (.LAN files) for the network topology attached to the server and one disk driver (.DSK) for the architecture handling the server's hard disks (AT* or compatible, PS/2 or compatible, or HBA).Depending on the functions of the server, you might need to use AUTOEXEC.NCF to load one or more additional NLM programs.You must also include STARTUP.NCF and AUTOEXEC.NCF (NetWare boot files created during NetWare installation) on the server's boot diskette or DOS partition:MARK=BULLETSTARTUP.NCF loads the server's disk driver, loads name spaces and other NLM programs (such as DOMAIN), and sets some parameters.AUTOEXEC.NCF stores the server's name, time, time server type, and IPX internal network number. This file loads settings for network boards and binds the IPX communication protocol to the installed drivers.NETINFO.SYS loads settings for network boards and binds the communication protocol other than IPX (such as IP and AppleTalk) to the installed drivers.You can also add executable NetWare server commands (such as TRACK ON, LOAD, or MONITOR) to the AUTOEXEC.NCF file.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"INSTALL" in Utilities Reference.PAGENUM=223 ID="BP225"RENDERAS="SECT2"Bringing Down the NetWare ServerSome maintenance procedures require that you bring down the NetWare server. To do so, use the DOWN command.Because changes made to data files are often held in the server's cache buffers until the server processor has idle time, that data is lost if you shut the server's power off without first using the DOWN command to bring the server down.When you use the DOWN command, the server writes data held in its cache buffers to disk.Users on the server should be notified that you are bringing down the server so that they can save and exit their files.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"SEND" in Utilities Reference and "BOOK="utlrfenu" COLLECTION="nw41"DOWN" in Utilities Reference.RENDERAS="SECT1"NetWare Server for OS/2IDXID="w2153"BOOK="_idx" COLLECTION="nw41" TIDREF="i2792"Device drivers that allow the NetWare 4 operating system to run as a non-dedicated server on an OS/2 computer. NetWare Server for OS/2MARK=BULLETRuns as an independent operating system on an OS/2 computer It is not a process controlled by OS/2.Shares processing time with OS/2The amount of processing time given to NetWare and OS/2 is controlled by a setting in the NET.CFG file.Works with NetWare Client for OS/2The client and server software can be loaded on the same computer making the computer a NetWare client and server.IDXID="w2154"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
Can be configured to share one network board between the client and server (on the same computer) PAGENUM=224 ID="BP226"This is done using one of three options: IDXID="w2155"BOOK="_idx" COLLECTION="nw41" TIDREF="i2054"
LANSHARE, IDXID="w2156"BOOK="_idx" COLLECTION="nw41" TIDREF="i4520"
TOKENSHR, or IDXID="w2157"BOOK="_idx" COLLECTION="nw41" TIDREF="i4518"
TOKENLNK. Each option provides drivers that communicate between NetWare Client for OS/2 and NetWare Server for OS/2.MARK=BULLETLANSHARE is used on Ethernet networks that use only the NetWare IPX/SPX protocols.TOKENSHR is used on token-ring or Ethernet networks using protocols in addition to IPX/SPX (TCP/IP, AppleTalk, etc.).TOKENLNK is used exclusively on token-ring networks using IBM communication products that use IBM protocols.IDXID="w2158"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"IDXID="w2159"BOOK="_idx" COLLECTION="nw41" TIDREF="i1634"
Shares the hard disk with OS/2The disk driver, IDXID="w2160"BOOK="_idx" COLLECTION="nw41" TIDREF="i1248"
DSKSHARE.DSK, allows OS/2 and NetWare to use separate partitions on the same hard disk. DSKSHARE.DSK is the interface from NetWare to OS/2 and OS/2 is the interface to the hard disk.IDXID="w2161"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
Shares memory with OS/2. NetWare Server for OS/2 allocates blocks of memory from OS/2. If the NetWare operating system needs more memory than OS/2 needs during a process, it automatically allocates the memory it needs from OS/2. If OS/2 needs the memory, NetWare passes it back for OS/2 to use.IDXID="w2162"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"
Shares a CD-ROM drive with OS/2The disk driver, IDXID="w2163"BOOK="_idx" COLLECTION="nw41" TIDREF="i601"
CDROMSHR.DSK, allows NetWare to access CD-ROM devices operating under OS/2. CDROMSHR.DSK is the interface from NetWare to OS/2 and OS/2 is the interface to the CD-ROM drive.See also Chapter 4, "BOOK="instlenu" COLLECTION="nw41"Install NetWare Server for OS/2," of Installation; "BOOK="superenu" COLLECTION="nw41"NetWare Server for OS/2 and NetWare 4" in Chapter 9 of Supervising the Network.RENDERAS="SECT1"ID="FM70205"NetWare Server objectIDXID="w2164"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"A leaf object that represents a server running NetWare on your network.A NetWare Server object can represent a server running any version of NetWare.PAGENUM=225 ID="BP227"Certain objects, such as Volume objects, reference a NetWare Server object to help identify their locations.Use caution when removing the Supervisor right from the Inherited Rights Filter of a NetWare Server object. You could cut off access to part of the Directory tree. (See IDREF="FM13738""Inherited Rights Filter.")See also IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Creating Leaf Objects" and "BOOK="superenu" COLLECTION="nw41"Cautions When Deleting NetWare Server Objects" in Chapter 1 of Supervising the NetWork.RENDERAS="SECT1"ID="FM50073"NetWare user toolsIDXID="w2165"BOOK="_idx" COLLECTION="nw41" TIDREF="i2816"Software that provides you with a graphical means of accessing network resources, such as volumes, directories, printers, and users.NetWare user tools allow you to perform tasks such as managing drive mappings, managing printer connections and setup, managing server connections, displaying network users, and sending messages.NetWare user tools are available for DOS, MS Windows, OS/2, Macintosh, and UNIX. For more information on NetWare user tools for DOS and MS Windows workstations, see Chapter 3, "BOOK="ws_d1enu" COLLECTION="nw41"Understanding Client Tools" in NetWare Client for DOS and MS Windows User Guide. For OS/2 workstations, see "BOOK="ws_osenu" COLLECTION="nw41"Using NetWare Tools" in Chapter 7 of NetWare Client for OS/2. For Macintosh workstations, see "BOOK="macclenu" COLLECTION="nw41"Using MacNDS Client for NetWare 4."RENDERAS="SECT1"NetWare volumeA physical amount of hard disk storage space, fixed in size. A NetWare volume is the highest level in the NetWare directory structure (on the same level as a DOS root directory).See IDREF="FM96914""Volume"PAGENUM=226 ID="BP228"RENDERAS="SECT1"NetWireIDXID="w2166"BOOK="_idx" COLLECTION="nw41" TIDREF="i2837"An online information service, which provides access to Novell product information, Novell services information, and time-sensitive technical information for NetWare users.NetWire® allows you toMARK=BULLETAccess information remotely 24 hours a daySubmit questions to a Novell Technician or System OperatorDownload files and technical information dealing with product updates and modificationsNetWire is accessed through the CompuServe* Information Service. It requires a PC or compatible workstation, a modem, and a communications program.Contact CompuServe for more information on NetWire subscriptions and a free introductory subscription.MARK=BULLETIn the USA or Canada, call 1-800-524-3388.In all other locations, call 1-614-457-0802.Ask for representative 200.RENDERAS="SECT1"NetworkIDXID="w2167"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"IDXID="w2168"BOOK="_idx" COLLECTION="nw41" TIDREF="i2689"A group of computers that can communicate with each other, share peripherals (such as hard disks and printers), and access remote hosts or other networks.A NetWare network consists of workstations, peripherals, and one or more NetWare servers.NetWare network users can share the same files (both data and program files), send messages directly between workstations, and protect files with an extensive security system.PAGENUM=227 ID="BP229"RENDERAS="SECT1"Network addressIDXID="w2169"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"A network number that uniquely identifies a network cable segment; usually referred to as the IPX external network number.See IDREF="FM35125""IPX external network number."RENDERAS="SECT1"Network 
backboneIDXID="w2170"BOOK="_idx" COLLECTION="nw41" TIDREF="i2845"IDXID="w2171"BOOK="_idx" COLLECTION="nw41" TIDREF="i565"A cabling system that NetWare servers and routers are attached to. The central cable handles all network traffic, decreasing packet transmission time and traffic on the network.LABEL="53" FLOAT="0"IDXID="w2172"BOOK="_idx" COLLECTION="nw41" TIDREF="i2845"Network BackboneFILEREF="n40co21a.tif"RENDERAS="SECT1"Network boardIDXID="w2173"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"A circuit board installed in each workstation to allow stations to communicate with each other and with the NetWare server.PAGENUM=228 ID="BP230"Some printers contain their own network board to allow them to attach directly to the network cabling.NetWare documentation uses the term network board. Documentation from other companies might use the terms NIC or network card instead of network board.RENDERAS="SECT1"ID="FM29539"Network communicationIDXID="w2174"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"Data transmission between workstations. Requests for services and data pass from one workstation to another through a communication medium such as cabling.RENDERAS="SECT1"Network direct printerIDXID="w2175"BOOK="_idx" COLLECTION="nw41" TIDREF="i3496"Printers and third-party print queue servers that connect directly into the network.In many cases, these devices (direct-connect printers and queue servers) offer an effective printing solution in NetWare printing environments. Typically, these print devices are shipped with their own installation utilities. The manufacturer's utilities configure the device to recognize network print components and to communicate with the network. Many network-direct print devices and their installation programs are designed to search the NetWare 3 bindery for network printing information. In order for these devices to work on a NetWare 4 network, you should use the bindery services mode when installing them.See also "BOOK="printenu" COLLECTION="nw41"Using Third-Party Network-Direct Print Devices with NetWare 4" in Chapter 6 of Print Services.RENDERAS="SECT1"Network driveA common name for a logical drive.See IDREF="FM87366""Drive"PAGENUM=229 ID="BP231"RENDERAS="SECT1"Network nodeIDXID="w2176"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"A personal computer or other device connected to a network by a network board and a LAN driver.A network node can be a server, workstation, router, printer, or fax machine.RENDERAS="SECT1"Network numberIDXID="w2177"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"A number that uniquely identifies a network cable segment, usually referred to as the IPX external network number.See IDREF="FM35125""IPX external network number."RENDERAS="SECT1"ID="FM97740"Network numberingIDXID="w2178"BOOK="_idx" COLLECTION="nw41" TIDREF="i2871"The system of numbers that identifies servers, network boards, and cable segments. These network numbers include the following:MARK=BULLETIDXID="w2179"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w2180"BOOK="_idx" COLLECTION="nw41" TIDREF="i1412"IPX external network number. A number that identifies a network cable segment.Servers that use the same frame type must use the same external network number to identify a specific cable segment. For example, all servers using frame type 802.2 could identify a particular cable segment as AAAAAAAA. If a new server using the same frame type is added to the network, it must also refer to this cable segment as AAAAAAAA. On the other hand, if a server with a different frame type is added to the network, it must use a different external network number for the same cable segment. It must use the same external network number as other servers of its frame type.IPX internal network number. A number that identifies an individual NetWare 4 server. This number must be unique for each server.Node number. A number that identifies a network board (in a server, workstation, or router). This number must be unique for each board.The relationship of these numbers is illustrated in the following figure.PAGENUM=230 ID="BP232"LABEL="54" FLOAT="0"NetWork NumberingFILEREF="n40co85a.tif"See also IDREF="FM35125""IPX external network number"; IDREF="FM16357""IPX internal network number"; IDREF="FM74415""Node number."RENDERAS="SECT1"Network printerIDXID="w2181"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"A printer shared in a network environment.See also IDREF="FM10765""Printer"; Chapter 7, "BOOK="printenu" COLLECTION="nw41"Setting Up Printers Attached to Workstations or Servers," in Print Services.RENDERAS="SECT1"Network supervisorIDXID="w2182"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"IDXID="w2183"BOOK="_idx" COLLECTION="nw41" TIDREF="i4330"A generic term in NetWare 4 for the person responsible for configuring the NetWare server, workstations, user access (security), printing, etc.RENDERAS="SECT1"ID="FM97312"Network Support Encyclopedia Professional VolumeIDXID="w2184"BOOK="_idx" COLLECTION="nw41" TIDREF="i2884"(NSE Pro) An electronic information database containing comprehensive information about network technology.The Network Support Encyclopedia Professional VolumeSM includes Novell technical bulletins and manuals, as well as downloadable NetWare patches, fixes, drivers, and utilities.NSE ProSM contains NetWare Application NotesTM (with graphics), the NetWare Buyer's Guide, Novell press releases, and additional product information.PAGENUM=231 ID="BP233"The NSE Pro also includes Novell LabsTM hardware and software compatibility test results.Using the text-retrieval software included with the NSE, you can search through custom menus, browse through manuals and technical bulletins, and do string searches using Boolean logic.The NSE Pro is available on CD-ROM in one year subscription which includes updates.For more information on subscribing to the NSE Pro, contact your Novell Authorized ResellerCLM.RENDERAS="SECT1"ID="FM70203"NETXIDXID="w2185"BOOK="_idx" COLLECTION="nw41" TIDREF="i2895"A VLM (NETX.VLM) in the NetWare DOS Requester that provides backwards compatibility with NETX and other older versions of the shell.See also IDREF="FM21900""NetWare DOS Requester"; IDREF="FM28012""Virtual Loadable Module."RENDERAS="SECT1"NFSNetworked file system. NetWare® NFS* allows UNIX systems to integrate with NetWare 4 file systems.See IDREF="FM73509""NetWare Networked File System."RENDERAS="SECT1"NIC(Network interface card) A circuit board installed in each workstation to allow stations to communicate with each other and with the NetWare server.NetWare documentation uses the term network board instead of NIC.RENDERAS="SECT1"ID="FM25202"NLM(NetWare Loadable Module) A program you can load and unload from server memory while the server is running.See IDREF="FM68484""NetWare Loadable Module."PAGENUM=232 ID="BP234"RENDERAS="SECT1"ID="FM91162"NLSP(NetWare Link Services Protocol) A link-state routing protocol designed by Novell for IPX internetworks.See IDREF="FM64684""NetWare Link Services Protocol."RENDERAS="SECT1"NNS(NetWare Name Service) A naming service designed to provide more transparent access to resources in NetWare installations. NNS was a predecessor to NDS.See IDREF="FM38207""NetWare Name Service."See also IDREF="FM83674""NetWare Directory Services."RENDERAS="SECT1"Node addressIDXID="w2186"BOOK="_idx" COLLECTION="nw41" TIDREF="i2945"A number that uniquely identifies a network board; usually referred to as the node number.See IDREF="FM74415""Node number."RENDERAS="SECT1"ID="FM74415"Node numberIDXID="w2187"BOOK="_idx" COLLECTION="nw41" TIDREF="i2945"IDXID="w2188"BOOK="_idx" COLLECTION="nw41" TIDREF="i3015"A number that uniquely identifies a network board, also known as station address, physical node address, and node address.Every node must have at least one network board, by which the node is connected to the network. Each network board must have a unique node number to distinguish it from all other network boards on that network.Node numbers are assigned in several ways, depending on the network board type:MARK=BULLETEthernet and token ring boards are factory-set (with no two Ethernet boards having the same number).ARCnet* board numbers are set with jumpers or switches.See also IDREF="FM70179""IPX internetwork address."PAGENUM=233 ID="BP235"RENDERAS="SECT1"Node schematicIDXID="w2189"BOOK="_idx" COLLECTION="nw41" TIDREF="i2945"A graphical representation of a node (NetWare server) and its managed objects.A node schematic is the main graphical display available in the NMS software.The node schematic is the focal point of the node with other graphical displays being launched from it.The node schematic can display network boards, server disks, volumes, queues, users, memory, NLM programs, and event and alert messages.RENDERAS="SECT1"Nonextended AppleTalk networkAn AppleTalk network that does not support Phase 2 extensions, such as zone lists and network ranges.See also IDREF="FM62114""AppleTalk Phase 2."RENDERAS="SECT1"Normal (N) attributeIDXID="w2190"BOOK="_idx" COLLECTION="nw41" TIDREF="i2977"A file system attribute that indicates that no NetWare attributes are set.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"NPA(NetWare Peripheral Architecture) An extension of the NetWare 4 Media Manager that separates NetWare driver support into two components; a HAM for the host adapter hardware, and a CDM for devices attached to the host adapter.See IDREF="FM87820""NetWare Peripheral Architecture."RENDERAS="SECT1"NSE Pro(NetWare Support Encyclopedia Professional Volume) A Novell database that contains comprehensive information about network technology.See IDREF="FM97312""Network Support Encyclopedia Professional Volume."PAGENUM=234 ID="BP236"ORENDERAS="SECT1"ID="FM13600"ObjectIDXID="w2191"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"IDXID="w2192"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"An NDS structure that stores information about a network resource (such as a user, group, printer, or volume).An object consists of categories of information, called properties, and the data in those properties. The information is stored in the NetWare Directory database.Some objects represent physical entities. For example, a User object represents a user and a Printer object represents a printer.Some objects represent logical entities, such as groups and print queues. Other objects, such as the Organizational Unit object, help you organize and manage objects.Remember that an object is a structure where information about the entity is stored; it isn't the actual entity.For example, a Printer object stores information about a printer and helps manage how the printer is used, but it isn't the printer itself.Types of ObjectsTwo types of objects make up the Directory tree: container objects and leaf objects.A subtree, or branch, of the Directory tree consists of a container object and all the objects it holds, which can include other container objects.Leaf objects are at the ends of branches and don't contain other objects.The following figure shows how container objects and leaf objects make up the Directory tree.PAGENUM=235 ID="BP237"LABEL="55" FLOAT="0"Objects in a Directory TreeFILEREF="n41co68a.tif"IDXID="w2193"BOOK="_idx" COLLECTION="nw41" TIDREF="i811"Container objects hold, or contain, other objects. Container objects are used as a way to logically organize all other objects in the Directory tree.The [Root] object is also considered a container object, but it is the very first object in the Directory tree, and it cannot be deleted or modified. All other objects, including Organization objects, are contained within the [Root] object. Container objects are like directories in a file system in that they group related information together. If a container object has objects in it, it is called a IDXID="w2194"BOOK="_idx" COLLECTION="nw41" TIDREF="i3218"parent object.Types of container objects. There are three types of container objects, described in the following table:LABEL="11" PGWIDE=1 TOCENTRY="1" Types of Container ObjectsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="6*"COLNAME=3 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Container objectCOLNAME=2 ROTATE="0" MOREROWS="0"AbbreviationCOLNAME=3 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CountryCOLNAME=2 ROTATE="0" MOREROWS="0"CCOLNAME=3 ROTATE="0" MOREROWS="0"Designates the countries where your network resides and organizes other Directory objects within the country. (See IDREF="FM81199""Country object.")COLNAME=1 ROTATE="0" MOREROWS="0"OrganizationCOLNAME=2 ROTATE="0" MOREROWS="0"OCOLNAME=3 ROTATE="0" MOREROWS="0"A level below the Country object (unless you don't use the Country object), the Organization object helps you organize other objects in the Directory and allows you to set template information for users created in this container. (See IDREF="FM72322""Organization object.")COLNAME=1 ROTATE="0" MOREROWS="0"Organizational UnitCOLNAME=2 ROTATE="0" MOREROWS="0"OUCOLNAME=3 ROTATE="0" MOREROWS="0"A level below the Organization object, the Organizational Unit object helps you to further organize other objects in the Directory and also allows you to set template information for users created in this container. (SeeIDREF="FM12169""Organizational Unit object.").PAGENUM=236 ID="BP238"Country objects can contain Organization objects or Alias objects (a leaf object, described in the next section).Organization and Organizational Unit objects can contain Organizational Unit objects or leaf objects.IDXID="w2195"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"Types of leaf objects. Leaf objects don't contain other objects. They represent network resources, such as users, computers, printers, and lists. The following table describes leaf objects:LABEL="12" PGWIDE=1 TOCENTRY="1" Types of Leaf ObjectsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Leaf objectCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AFP ServerCOLNAME=2 ROTATE="0" MOREROWS="0"Represents an AFP server that is operating as a node on your NetWare network and usually also acting as a NetWare router to, and the AppleTalk server for, several Macintosh computers. (See IDREF="FM83400""AFP Server object.")COLNAME=1 ROTATE="0" MOREROWS="0"AliasCOLNAME=2 ROTATE="0" MOREROWS="0"Points to the original location of an object in the Directory. Any Directory object located in one place in the Directory can also appear to be in another place in the Directory by using an Alias. (See IDREF="FM28929""Alias object.")COLNAME=1 ROTATE="0" MOREROWS="0"BinderyCOLNAME=2 ROTATE="0" MOREROWS="0"Represents an object placed in the Directory tree by an upgrade or migration utility, but that NDS can't identify. This object provides backward compatibility for bindery-oriented utilities. (See IDREF="FM96444""Bindery object.")COLNAME=1 ROTATE="0" MOREROWS="0"Bindery QueueCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a queue placed in the Directory tree by an upgrade or migration utility, but that NDS can't identify. This object provides backward compatibility for bindery-oriented utilities. COLNAME=1 ROTATE="0" MOREROWS="0"ComputerCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a computer on the network. (See IDREF="FM72100""Computer object.")COLNAME=1 ROTATE="0" MOREROWS="0"Directory MapCOLNAME=2 ROTATE="0" MOREROWS="0"Refers to a directory on a volume. (See IDREF="FM48764""Directory Map object.")COLNAME=1 ROTATE="0" MOREROWS="0"Distribution ListCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a list of mail recipients. (See IDREF="FM74578""Distribution List object.")COLNAME=1 ROTATE="0" MOREROWS="0"External EntityCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a non-native NDS object that is imported into NDS or registered in NDS. (See IDREF="FM75406""External Entity object.")COLNAME=1 ROTATE="0" MOREROWS="0"GroupCOLNAME=2 ROTATE="0" MOREROWS="0"Assigns a name to a list of User objects in the Directory. You can assign rights to the group instead of to each user---the rights transfer to each user in the group. (See IDREF="FM36715""Group object.")COLNAME=1 ROTATE="0" MOREROWS="0"Message Routing GroupCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a group of messaging servers that can transfer messages directly among themselves. (See IDREF="FM45790""Message Routing Group object.")COLNAME=1 ROTATE="0" MOREROWS="0"Messaging ServerCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a NetWare MHS server that resides on a NetWare server. A NetWare MHS Server object is automatically created in the Directory tree when you install NetWare MHS on a NetWare server. (See IDREF="FM48140""Messaging Server object.")COLNAME=1 ROTATE="0" MOREROWS="0"NetWare ServerCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a server running any version of NetWare. (See IDREF="FM70205""NetWare Server object.")COLNAME=1 ROTATE="0" MOREROWS="0"Organizational RoleCOLNAME=2 ROTATE="0" MOREROWS="0"Defines a position or role within an organization. (See IDREF="FM87339""Organizational Role object.")COLNAME=1 ROTATE="0" MOREROWS="0"Print QueueCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a network print queue.COLNAME=1 ROTATE="0" MOREROWS="0"Print ServerCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a network print server.COLNAME=1 ROTATE="0" MOREROWS="0"PrinterCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a network printing device.COLNAME=1 ROTATE="0" MOREROWS="0"ProfileCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a login script used by a group of users who need to share common login script commands but who aren't necessarily located under the same container in the Directory tree, or who are a subset of users in the same container.COLNAME=1 ROTATE="0" MOREROWS="0"UserCOLNAME=2 ROTATE="0" MOREROWS="0"Represents the people who use your network. (See IDREF="FM20517""User object.")COLNAME=1 ROTATE="0" MOREROWS="0"UnknownCOLNAME=2 ROTATE="0" MOREROWS="0"Represents an NDS object that has been corrupted and can't be identified as belonging to any of the other object classes.COLNAME=1 ROTATE="0" MOREROWS="0"VolumeCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a physical volume on the network. (See IDREF="FM53478""Volume object.")PAGENUM=238 ID="BP239"RENDERAS="SECT2"Location of Objects in the Directory TreeIn a Directory tree, you can place container objects and leaf objects in different configurations, according to your company's needs. The following figure shows possible configurations:PAGENUM=239 ID="BP240"LABEL="56" FLOAT="0"Possible Configurations for a Directory TreeFILEREF="n41co69a.tif"The Country and Organizational Unit objects are optional, but you must include at least one Organization object in your Directory tree.You aren't limited to using only one container object in a tree; you can use many at each level. The following figure shows an example Directory tree that has several container objects at each level:PAGENUM=240 ID="BP241"LABEL="57" FLOAT="0"Example Directory Tree with Several Container ObjectsFILEREF="n41co65a.tif"RENDERAS="SECT2"IDXID="w2196"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"IDXID="w2197"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"
Object NamesThe path from an object to the root of the Directory tree forms the object's complete name, which is a unique name. Most leaf objects also have a IDXID="w2198"BOOK="_idx" COLLECTION="nw41" TIDREF="i694"common name. For User objects, the common name is their login name, displayed in the Directory tree.Other leaf objects also have common names displayed in the Directory tree, such as a Printer object name or a Server object name.Container objects don't have common names. They are referred to by their Organizational Unit name, or Organization name, or Country name.IDXID="w2199"BOOK="_idx" COLLECTION="nw41" TIDREF="i718"
An object's complete name consists of its common name (if it has one), followed by a period (.), then the name of the container object, also followed by a period, and on up through succeeding container object names to the root of the tree.For example, in the following figure the complete name for ESAYERS would beESAYERS.SALES PV.SALES.NOVELL USPAGENUM=241 ID="BP242"LABEL="58" FLOAT="0"IDXID="w2200"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"Complete and Common NamesFILEREF="n41co70a.tif"When querying the Directory, you can supply the object's complete name to receive information that describes that object. Or, you can supply an object's property value and receive a list of object names that have that value.For example, to find all users with a last name of Smith, search for "Smith" in the last name property of User objects.RENDERAS="SECT2"IDXID="w2201"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"IDXID="w2202"BOOK="_idx" COLLECTION="nw41" TIDREF="i2727"
Object ContextsNDS allows you to refer to objects according to their positions within a tree. When you add an object (such as a server or user) to the network, you place that object in a container object in the Directory tree.PAGENUM=242 ID="BP243"The position of the object within its container is its context. For example, in the previous figure, the context for User object ESAYERS is SALES PV.SALES.NOVELL US.When you move from one container object to another, you change contexts. Whenever you change contexts, you must indicate the complete name of the object you are changing contexts to. (If you're changing to a context that includes spaces between words, be sure to include an underscore in place of the space.)If you are referring to an object in the same container object as your User object, then you need only refer to that object by its common name, not its complete name.For example, in the previous figure, if ESAYERS located in SALES PV.SALES.NOVELL US wants information on ESMITH located in the same context, then ESAYERS need only refer to the User object as ESMITH.RENDERAS="SECT2"IDXID="w2203"BOOK="_idx" COLLECTION="nw41" TIDREF="i2727"IDXID="w2204"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"IDXID="w2205"BOOK="_idx" COLLECTION="nw41" TIDREF="i3575"
Object PropertiesEach type of object has certain properties that hold information about the object.For example, some User object properties include the login name, password restrictions, and group memberships. Some Profile object properties are the profile name, login script, and volume.The only properties required for objects are those you enter when you create a new object. You must enter a value in each field.Properties you must specify when you create an object areMARK=BULLETProperties that name the objectProperties required to create the object but that don't name itFor example, when you create a Volume object, you must specify the volume's host server.PAGENUM=243 ID="BP244"Many of an object's properties can contain multiple values. For example, the telephone number property, found in many object types, can contain several different telephone numbers.The NETADMIN and NetWare Administrator utilities allow you to see and change properties for any object to which you have sufficient rights.See also IDREF="FM83674""NetWare Directory Services"; "BOOK="superenu" COLLECTION="nw41"Object Rights" in Chapter 1 of Supervising the Network.RENDERAS="SECT1"Object rightsQualities assigned to an object that control what the object can do with directories, files, or other objects.See IDREF="FM74455""Rights."RENDERAS="SECT1"ID="FM26135"ODI(Open Data-Link Interface) An architecture that allows multiple LAN drivers and protocols to coexist on network systems.See IDREF="FM33588""Open Data-Link Interface."RENDERAS="SECT1"ID="FM19164"ODINSUPIDXID="w2206"BOOK="_idx" COLLECTION="nw41" TIDREF="i3060"IDXID="w2207"BOOK="_idx" COLLECTION="nw41" TIDREF="i3060"(Open Data-Link Interface Network Driver Interface Specification Support) An interface that allows the coexistence of two network driver interfaces: Network Driver Interface Specification (NDIS) and ODI. (See also IDREF="FM33588""Open Data-Link Interface.")ODINSUP allows you to connect to dissimilar networks from your workstation and use them as if they were one network.ODINSUP also allows NDIS protocol stacks to communicate through the ODI's LSL and MLID. This way, NDIS and ODI protocol stacks can coexist in the same system, making use of a single ODI MLID.For example, after you load ODINSUP on your workstation, you can log in to 3Com* 3+Share*, Microsoft LAN Manager, or IBM LAN Server network, and also log in to a NetWare network, using the same network board in the workstation.PAGENUM=244 ID="BP245"You can then copy files and run applications between the two networks as if they were one.When ODINSUP is loaded, you can use a wider variety of programs without having to worry about compatibility and without reconfiguring or rebooting your workstation to switch from one type of network to another.ODINSUP functions as a default protocol stack. As a default protocol stack, it accepts packets from the ODI Link Support Layer (LSL) that aren't specifically marked with a protocol identifier (PID) for registered ODI protocol stacks (such as IPX or TCP/IP).When it receives a packet, ODINSUP provides the packet to the NDIS Protocol Manager and passes it on to the NDIS protocol stack.ODINSUP allows the NDIS protocol stack to communicate with a network board.The NDIS protocol stack acts as though it is communicating with the network through an NDIS 2.0 MAC driver, and isn't aware of the ODINSUP protocol stack.The details of the packet's transmission are handled by the MLID, which is the ODI driver. This is illustrated in the following figure:PAGENUM=245 ID="BP246"LABEL="59" FLOAT="0"IDXID="w2208"BOOK="_idx" COLLECTION="nw41" TIDREF="i3060"ODINSUPFILEREF="n40co25a.tif"RENDERAS="SECT1"ID="FM33588"Open Data-Link InterfaceIDXID="w2209"BOOK="_idx" COLLECTION="nw41" TIDREF="i3083"(ODI) An architecture that allows multiple LAN drivers and protocols to coexist on network systems.ODI describes the set of interface and software modules used to decouple device drivers from protocol stacks and to enable multiple protocol stacks to share the network hardware and media transparently.The following figure illustrates the components of the ODI model in the server environment:PAGENUM=246 ID="BP247"LABEL="60" FLOAT="0"ODI ModelFILEREF="n40co23a.tif"The major components of the ODI architecture are described in the following sections.RENDERAS="SECT2"IDXID="w2210"BOOK="_idx" COLLECTION="nw41" TIDREF="i2563"
Multiple Link Interface Driver (MLID)The MLID is a device driver written to the ODI specification that handles the sending and receiving of packets to and from a physical or logical LAN medium.Each driver is unique due to the adapter hardware and media, but the ODI eliminates the need to write separate drivers for each protocol stack.ODI allows LAN drivers to function with protocol stacks independently of the media frame type and protocol stack details.An MLID interfaces with a network board and handles media frame header appending and stripping.They also help demultiplex the incoming packets by determining their frame format.Novell has made ODI LAN driver development easier by furnishing a set of support modules that provide all tools necessary to interface a LAN driver to the LSL.PAGENUM=247 ID="BP248"These modules are the Media Support ModuleTM (MSM), which contains general functions common to all drivers, and the Topology Specific ModuleTM (TSM), which provides support for the standardized media types of Ethernet, token ring, RX-Net, and FDDI.These modules and the Hardware Specific ModuleTM (HSM) are described later in this section.The following figure illustrates the modules which make up an MLID. Note that in the server environment, the MSMTM, TSMTM, and HSMTM are modules that are loaded separately.LABEL="61" FLOAT="0"MLID ModulesFILEREF="n40co24a.tif"In DOS and OS/2 environments, the MSM and TSM are linked in with the HSM so that only one module is loaded.RENDERAS="SECT2"IDXID="w2211"BOOK="_idx" COLLECTION="nw41" TIDREF="i2120"
Link Support Layer (LSL)The LSL is a software module that interfaces between drivers and protocol stacks. It essentially acts like a switchboard, directing packets between the drivers and protocol stacks.Any ODI LAN driver can communicate with any ODI protocol stack through the LSL. The LSL handles the communication between protocol stacks and MLID software.PAGENUM=248 ID="BP249"Because the ODI allows the physical LAN medium to support many different types of protocols (for example, IPX, TCP/IP, AppleTalk, and LAT might all be supported on one Ethernet network adapter), the MLID receives packets destined for different protocol stacks that might be present in the system.The LSL then determines which protocol stack the packet should be delivered to. Next, the protocol stack determines what should be done with the packet.When the protocol stack must transmit a packet, the protocol stack returns the packet to the LSL, which then routes the packet to the appropriate MLID.The LSL enables the protocol stacks to handle sending and receiving.The LSL also tracks the various protocols and MLID software loaded in the system. It also provides a consistent method of finding and using each of the loaded modules.RENDERAS="SECT2"IDXID="w2212"BOOK="_idx" COLLECTION="nw41" TIDREF="i2366"
Media Support Module (MSM)The MSM standardizes and manages primary details of interfacing ODI MLID software to the LSL and operating system.The MSM handles generic initialization and runtime issues common to all drivers.RENDERAS="SECT2"IDXID="w2213"BOOK="_idx" COLLECTION="nw41" TIDREF="i4531"
Topology Specific Module (TSM)The TSM manages operations unique to a specific media type, such as Ethernet or token ring. Multiple frame support is implemented in the TSM so that all frame types for a given media are supported.RENDERAS="SECT2"IDXID="w2214"BOOK="_idx" COLLECTION="nw41" TIDREF="i1643"
Hardware Specific Module (HSM)The HSM is created for a specific network board. The HSM handles all hardware interactions. Its primary functions include adapter initialization, reset, shutdown, and removal.It also handles packet reception and transmission. Additional procedures may also provide support for timeout detection, multicast addressing, and promiscuous mode reception.PAGENUM=249 ID="BP250"RENDERAS="SECT1"ID="FM28062"Open Shortest Path FirstIDXID="w2215"BOOK="_idx" COLLECTION="nw41" TIDREF="i3089"(OSPF) A link state internal gateway protocol. OSPF is part of the TCP/IP protocol suite.Link state routers exchange information about the state of their network connections or links. Using this information, each router can construct the topology of the internetwork and derive routing information. This method is generally considered superior when compared to using distance vector routing protocols, which have little direct knowledge of the network's topology.OSPF routers exchange information using link state advertisements. For each destination, the router examines its link state database and selects the shortest path as the route to that destination. The link state information is then shared with other routers to varying degrees as determined by how the routers in your network are grouped and how they are related to each other.For administrative purposes, the OSPF internetwork can be divided into different regions, called areas. All routers within an area share complete link state information. The route information shared between areas can be filtered and is generally a distillation of the rest of the autonomous system's topology.RENDERAS="SECT1"Optical discIDXID="w2216"BOOK="_idx" COLLECTION="nw41" TIDREF="i3099"IDXID="w2217"BOOK="_idx" COLLECTION="nw41" TIDREF="i1109"(Also optical disk) A form of removable media used to store data. An optical disc can be one- or two-sided. Some optical discs are read-only; others can be read from and written to.HCSS uses rewritable optical discs.See also IDREF="FM40870""High Capacity Storage System."RENDERAS="SECT1"Optical disc libraryA high-capacity storage device, sometimes called a jukebox, that uses an autochanger mechanism to mount and dismount optical discs as needed.PAGENUM=250 ID="BP251"See also IDREF="FM40870""High Capacity Storage System."RENDERAS="SECT1"ID="FM72322"Organization objectIDXID="w2218"BOOK="_idx" COLLECTION="nw41" TIDREF="i3115"A container object that helps you organize other objects in the Directory and allows you to set template information for users created in it.For example, you could use an Organization object to represent a company, or a university with various departments, or a department with several project teams.The Organization object is a level below the Country object (if used), and a level above the Organizational Unit object (if used).See also IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Creating Container Objects" in Chapter 1 of Supervising the Network; Chapter 5, "BOOK="getstenu" COLLECTION="nw41"Planning NetWare Directory Services Implementation," of Introduction to NetWare Directory Services.RENDERAS="SECT1"ID="FM87339"Organizational Role objectIDXID="w2219"BOOK="_idx" COLLECTION="nw41" TIDREF="i3120"A leaf object that defines a position or role within an organization. Use the Organizational Role object to specify a position that can be filled by different people, such as Team Leader or Vice President.See also IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Managing Organizational Role Objects" in Chapter 1 of Supervising the Network.RENDERAS="SECT1"ID="FM12169"Organizational Unit objectIDXID="w2220"BOOK="_idx" COLLECTION="nw41" TIDREF="i3122"A container object, a level below the Organization object, that helps you to further organize objects in the Directory and also allows you to set template information for users created in it.For example, an organizational unit could be a division, a business unit, a project team, or a university department within your organization. You can use an Organizational Unit object to logically arrange these entities in your directory tree.See also IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Creating Container Objects" in Chapter 1 of Supervising the Network; Chapter 5, "BOOK="getstenu" COLLECTION="nw41"Planning NetWare Directory Services Implementation," of Introduction to NetWare Directory Services.PAGENUM=251 ID="BP252"RENDERAS="SECT1"ID="FM68243"OS/2 clientIDXID="w2221"BOOK="_idx" COLLECTION="nw41" TIDREF="i3133"An OS/2 computer that connects to the network using NetWare Client for OS/2 software.The OS/2 client can store and retrieve data from the network and can run executable network files.OS/2 client workstations support IPX/SPX, NetBIOS, and Named Pipes to allow users access to OS/2-based applications such as the SQL Server.See also IDREF="FM93979""NetWare Client for OS/2."RENDERAS="SECT1"OS/2 RequesterA component of the software that connects OS/2 workstations to NetWare networks, allowing OS/2 users to share network resources.See IDREF="FM93979""NetWare Client for OS/2."RENDERAS="SECT1"OSPF(Open Shortest Path First) A link state internal gateway protocol. OSPF is part of the TCP/IP protocol suite.See IDREF="FM28062""Open Shortest Path First."PAGENUM=252 ID="BP253"PRENDERAS="SECT1"ID="FM21658"PacketIDXID="w2222"BOOK="_idx" COLLECTION="nw41" TIDREF="i3169"A unit of information used in network communication.Messages sent between network devices (such as workstations or NetWare servers) are formed into packets at the source device.The packets are reassembled, if necessary, into complete messages when they reach their destination.A packet might contain a request for service, information on how to handle the request, and the data to be serviced.An individual packet consists of headers and a data portion. The different headers are appended to the data portion as the packet travels through the communication layers.A message that exceeds the maximum size is partitioned and carried as several packets. When the packet arrives at its destination, the headers are stripped off in reverse order and the request is serviced.For example, NCP attaches a write request header and an IPX header to a piece of data to be written.Then the workstation's IPX communication protocol fills in the IPX header, designating, among other things, the source of the request and the packet length.Finally, the MLID adds a hardware or MAC frame header.See also IDREF="FM34819""Communication protocols"; IDREF="FM81286""Ethernet configuration"; IDREF="FM31073""Large Internet Packet"; IDREF="FM62017""NetWare Core Protocol."PAGENUM=253 ID="BP254"RENDERAS="SECT1"ID="FM53004"Packet Burst protocolIDXID="w2223"BOOK="_idx" COLLECTION="nw41" TIDREF="i3171"A protocol built on top of IPX that speeds the transfer of multiple-packet NCP file reads and writes.The Packet BurstTM protocol speeds the transfer of NCP data between a workstation and a NetWare server by eliminating the need to sequence and acknowledge each packet.Packet Burst protocol is more efficient than the one-request/one-response protocol in earlier NetWare versions. With Packet Burst protocol, the server or workstation can send a whole set (burst) of packets before it requires an acknowledgment.LABEL="62" FLOAT="0"IDXID="w2224"BOOK="_idx" COLLECTION="nw41" TIDREF="i3171"Packet Burst ProtocolFILEREF="n41co26a.tif"By allowing multiple packets to be acknowledged, Packet Burst protocol reduces network traffic. PAGENUM=254 ID="BP255"Packet Burst protocol also monitors dropped packets and retransmits only the missing packets.NetWare 4 doesn't require an NLM to enable Packet Burst at the server. For workstations to send and receive Packet Burst data, you must enable Packet Burst under the NetWare DOS Requester.When Packet Burst-enabled servers or workstations transfer data to servers or workstations that don't have Packet Burst enabled, the data defaults to normal NCP mode (one-request/one-response).RENDERAS="SECT1"ID="FM51228"Packet receive bufferIDXID="w2225"BOOK="_idx" COLLECTION="nw41" TIDREF="i3169"An area in the NetWare server's memory set aside to temporarily hold data packets arriving from the various workstations. The packets remain in this buffer until the server is ready to process them and send them to their destination. This ensures the smooth flow of data into the server, even during times of particularly heavy input/output operations.The number of packet receive buffers is set during server installation. This number is increased by the operating system as needed due to heavy buffer activity, within the following parameters (also set during server installation).MARK=BULLETMaximum packet receive buffers. The maximum number of packet receive buffers that the operating system can allocate.Minimum packet receive buffers. The minimum number of packet receive buffers that the operating system can use.New packet receive buffer wait time. The operating system can increase the number of packet receive buffers as needed, within the set parameters.However, rather than allocating a new packet immediately on demand, the operating system waits for the specified time, after which the packet is allocated if still needed.This ensures that new packet receive buffers aren't allocated needlessly due to sporadic peak activity.PAGENUM=255 ID="BP256"If the set maximum number of packet receive buffers is reached, and a waiting packet isn't processed within the specified wait time, the operating system discards the packet, and the station must resend the packet.The default range of packet receive buffers should be satisfactory for most server installations, even with many users performing many read/write operations.Because more system overhead is required to manage large numbers of packet receive buffers, we recommend that you increase the maximum range only if you are running out of buffers. For example, if your server is slow when first brought up, but later speeds up, the minimum packet receive buffer setting may be too low. The delay is caused by the accumulation of packet receive buffer wait times. If your server always allocates at least 200 packet receive buffers, set the minimum to 200. See also IDREF="FM64813""Watchdog."RENDERAS="SECT1"ID="FM45002"PagingIDXID="w2226"BOOK="_idx" COLLECTION="nw41" TIDREF="i3203"IDXID="w2227"BOOK="_idx" COLLECTION="nw41" TIDREF="i1176"Allows NetWare 4 to assign memory noncontiguously. This is a feature of most high-powered CPU architectures (such as the Intel* 80386/80486 and the Pentium*). Rather than assign memory to processes in large blocks of contiguously-addressed pages, NetWare 4 uses segmentation to assign memory noncontiguously.Page tables are used to map physical addresses to logical memory. Each page table entry corresponds to a page in memory. A memory page is a 4KB block of RAM. A group of page tables is a domain.Other systems sometimes use paging to create virtually contiguous blocks from physically non-contiguous blocks of memory. The NetWare operating system doesn't use paging for this purpose.The main function of paging in NetWare is for memory protection. For instance, NetWare maps out certain memory addresses to prevent access to those pages in memory. PAGENUM=256 ID="BP257"A domain's page tables are listed in the page directory table.The two levels of lookup tables in NetWare 4 are illustrated in the following figure:LABEL="63" FLOAT="0"IDXID="w2228"BOOK="_idx" COLLECTION="nw41" TIDREF="i3203"PagingFILEREF="n40co27a.tif"RENDERAS="SECT1"ID="FM31531"Parallel portIDXID="w2229"BOOK="_idx" COLLECTION="nw41" TIDREF="i3207"IDXID="w2230"BOOK="_idx" COLLECTION="nw41" TIDREF="i3337"A printer interface that allows data to be transmitted a byte at a time, all eight bits moving in parallel.See also IDREF="FM25427""LPT ports"; "BOOK="printenu" COLLECTION="nw41"Selecting the Best Type of Printer for Your Setup" in Appendix A of Print Services.PAGENUM=257 ID="BP258"RENDERAS="SECT1"Parent directoryIDXID="w2231"BOOK="_idx" COLLECTION="nw41" TIDREF="i3216"The directory immediately above any subdirectory. For example, SYS:ACCTS would be the parent directory of the subdirectory SYS:ACCTS/RECEIVE.See also IDREF="FM22177""File system."RENDERAS="SECT1"Parent objectsContainer objects that contain other objects.See IDREF="FM13600""Object." RENDERAS="SECT1"Parent VLMIDXID="w2232"BOOK="_idx" COLLECTION="nw41" TIDREF="i3219"IDXID="w2233"BOOK="_idx" COLLECTION="nw41" TIDREF="i4770"IDXID="w2234"BOOK="_idx" COLLECTION="nw41" TIDREF="i2566"IDXID="w2235"BOOK="_idx" COLLECTION="nw41" TIDREF="i4770"
Acts as a multiplexor that routes calls to the correct child VLM. It ensures that each request to a child VLM reaches its destination.For example, NWP.VLM is the multiplexor that handles calls to and from the child VLM programs BIND.VLM, NDS.VLM, and PNW.VLM. Similarly, TRAN.VLM is the multiplexor that coordinates communication at the transport layer when its child VLM, IPXNCP.VLM and other transport protocols, are concurrently loaded. See also IDREF="FM82431""Child VLM"; IDREF="FM28012""Virtual Loadable Module."RENDERAS="SECT1"ParityA method of checking for errors in transmitted data.See IDREF="FM44412""Serial communication."RENDERAS="SECT1"Partition (NetWare Directory)A logical division of the NetWare Directory database.See IDREF="FM61672""NetWare Directory partition."PAGENUM=258 ID="BP259"RENDERAS="SECT1"ID="FM23688"Partition (disk)A logical unit into which NetWare server hard disks can be divided.See IDREF="FM76186""Disk partition."RENDERAS="SECT1"Partition managementIDXID="w2236"BOOK="_idx" COLLECTION="nw41" TIDREF="i2718"The method of managing NetWare Directory partitions and replicas.Partition management allows you to divide the Directory into partitions and manage various Directory replicas of these Directory partitions.Partition management allows you toMARK=BULLETCreate, merge, and move Directory partitionsDisplay partitions and partition detailsAdd, delete, synchronize, and display Directory replicasRelated utilities: "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" and "BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities Reference.RENDERAS="SECT1"Passive hubIDXID="w2237"BOOK="_idx" COLLECTION="nw41" TIDREF="i3240"IDXID="w2238"BOOK="_idx" COLLECTION="nw41" TIDREF="i1734"A device used in some network topologies to split a transmission signal, allowing additional workstations to be added.See IDREF="FM27825""Hub."RENDERAS="SECT1"PasswordIDXID="w2239"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"The characters a user must type to log in. NetWare allows the network supervisor to specify whether passwords are required and, if so, to assign a login password to each user on the network.The network supervisor can also specify whether passwords must be unique and whether they must be changed periodically.PAGENUM=259 ID="BP260"In NetWare 4, login passwords are encrypted at the workstation and put into a format that only the NetWare server can decode. This format helps prevent intruders from accessing network files.See also IDREF="FM52521""Security"; IDREF="FM20517""User object."RENDERAS="SECT1"PathThe location of a file or directory in the file system.For example, the path for file REPORT.FIL in subdirectory ACCTG in directory CORP on volume SYS: of server ADMIN isFORMAT="LINESPECIFIC"MOREINFO="NONE"ADMIN\SYS:CORP\ACCTG\REPORT.FILSee also IDREF="FM59413""Authentication"; IDREF="FM22177""File system."RENDERAS="SECT1"Physical memoryIDXID="w2240"BOOK="_idx" COLLECTION="nw41" TIDREF="i3305"IDXID="w2241"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"The RAM installed in a computer.NetWare servers use paging to address physical memory in 4KB blocks, or pages.See also IDREF="FM84055""Logical memory"; IDREF="FM72408""Memory protection"; IDREF="FM45002""Paging."RENDERAS="SECT1"ID="FM11558"PMMONIDXID="w2242"BOOK="_idx" COLLECTION="nw41" TIDREF="i3324"A graphical utility that runs under the Presentation Manager* in OS/2. PMMON is used for monitoring resources, allocating processing time, and setting memory options on NetWare Server for OS/2.See "BOOK="utlrfenu" COLLECTION="nw41"PMMON" in Utilities Reference and "BOOK="superenu" COLLECTION="nw41"Managing NetWare Server for OS/2" in Supervising the Network.RENDERAS="SECT1"ID="FM52438"Polled modeIDXID="w2243"BOOK="_idx" COLLECTION="nw41" TIDREF="i3334"IDXID="w2244"BOOK="_idx" COLLECTION="nw41" TIDREF="i3496"A printer configuration option through which the port driver (NPRINTER) periodically checks, or polls, the data port to determine whether it is ready to accept data for transmission to the printer. PAGENUM=260 ID="BP261"The port's status is indicated by an electronic signal called a flag. Polling queries are made at each CPU timer tick (18 times per second).In NetWare 4, polled mode is the default for printer configurations. Using polled mode allows users to set up a printer without having to determine which interrupt the port is set to or whether the port supports interrupts. In earlier releases of NetWare, polled mode with RPRINTER was considerably slower than the alternative interrupt mode.However, the enhanced performance of NPRINTER for NetWare 4 makes polled mode considerably faster than before. In most instances, users see little difference in performance between polled mode and interrupt mode. The advantage of polled mode is that it eliminates any possibility of interrupt conflicts among different hardware configurations. (However, I/O port addresses must still be unique.)In complex printing setups with multiple printers running off a single workstation, polled mode may noticeably slow other tasks on that workstation.RENDERAS="SECT1"Port (IDXID="w2245"BOOK="_idx" COLLECTION="nw41" TIDREF="i1638"
hardwareIDXID="w2246"BOOK="_idx" COLLECTION="nw41" TIDREF="i3337"
)A connecting component that allows a microprocessor to communicate with a compatible peripheral, such as a printer.See also IDREF="FM31531""Parallel port"; IDREF="FM18990""Serial port."RENDERAS="SECT1"Port (softwareIDXID="w2247"BOOK="_idx" COLLECTION="nw41" TIDREF="i4200"IDXID="w2248"BOOK="_idx" COLLECTION="nw41" TIDREF="i3337"
)A memory address that identifies the physical circuit used to transfer information between a microprocessor and a peripheral.RENDERAS="SECT1"Port driverA driver that routes print jobs out of the print queue and through the proper port (for example, LPT1, LPT2, COM1) to the printer that will handle the job. The NPRINTER utility functions as a port driver in NetWare.RENDERAS="SECT1"PostmasterA user who has all of the following rights:PAGENUM=261 ID="BP262"MARK=BULLETSupervisor access to the NetWare MHS Messaging Server objectSupervisor access to the Mailbox Location, Mailbox ID, and E-mail Address properties of users of the NetWare MHS messaging serverRead access to the Message Routing Group that the NetWare MHS messaging server is inBasic NetWare MHS sends a message to the Postmaster's mailbox when certain types of errors occur. For example, if a message is not in valid NetWare MHS format, the NetWare MHS Messaging Server cannot determine who the sender is. So, it sends a message to the Postmaster.RENDERAS="SECT1"Postmaster GeneralA user who has Supervisor access to the Message Routing Group that he or she resides in. A Postmaster General can add a messaging server to, or remove a messaging server from, the Message Routing Group.You can assign several Postmasters General to a Message Routing Group.RENDERAS="SECT1"Power conditioningIDXID="w2249"BOOK="_idx" COLLECTION="nw41" TIDREF="i3358"Methods of protecting sensitive network hardware components against power disturbances.Power disturbances can be categorized in several ways:MARK=BULLETA transient (sometimes called a spike or surge). A very short, but extreme, burst of voltage.Noise or static. A smaller change in voltage.Blackouts and brownouts. The temporary drop in or loss of electrical power.Three types of protection are available:MARK=BULLETSuppression. Protects against transients. The most common suppression devices are surge protectors that usually include circuitry to prevent excess voltage.PAGENUM=262 ID="BP263"Isolation. Protects against noise, using ferro-resonant isolation transformers to control voltage irregularities.Regulation. Protects against brownouts and blackouts. The uninterruptible power upply (UPS) is the most commonly used form of regulation.Proper use of power conditioning devices greatly reduces network maintenance costs.Make sure the proper amperage is available for each system; dedicated power lines should provide ample amperage.Also, make sure all outlets are grounded. Power conditioning devices connected to poorly grounded outlets offer very little protection.See also IDREF="FM99587""Uninterruptible power supply"; IDREF="FM71926""UPS monitoring."RENDERAS="SECT1"IDXID="w2250"BOOK="_idx" COLLECTION="nw41" TIDREF="i3386"IDXID="w2251"BOOK="_idx" COLLECTION="nw41" TIDREF="i4125"
Primary serverThe SFT III NetWare server that has been operating longer than its partner and is currently servicing workstations.The primary server is the SFT III server that network workstations see, and the one to which they send requests for network services. Routers on the internetwork see only the primary server and send routing packets to it. The primary server's IOEngine determines the order and type of events that are sent to the MSEngine. Only the primary server sends reply packets to network workstations.The secondary server is the SFT III NetWare server that is activated after the primary server. Either server may function as primary or secondary, depending on the state of the system. You cannot permanently designate which server is primary or secondary; system failure determines each server's role. When the primary server fails, the secondary server becomes the new primary server. When the failed server is restored, it becomes the new secondary server.PAGENUM=263 ID="BP264"RENDERAS="SECT1"Primary time serverA server that synchronizes the time with at least one other Primary or Reference time server, and provides the time to Secondary time servers and to workstations.See IDREF="FM65772""Time synchronization."RENDERAS="SECT1"ID="FM27166"Print device definitionIDXID="w2252"BOOK="_idx" COLLECTION="nw41" TIDREF="i3390"A set of functions and modes found in a file with a .PDF extension that corresponds to a printer, plotter, or other peripheral. A print device definition does not necessarily represent the full functionality of the printer. A print device definition can be modified to change the functions the machine can perform.Print device definitions contain the necessary control sequences for setting or resetting the printer and for controlling bold, emphasis, italics, print size, font selection, colors, and other features, depending on the printer.If your application does not have the print driver for your printer, NetWare supplies the control sequences in the form of print device definitions for many common printers. These print device definitions are copied to the SYS:PUBLIC directory during installation. Each print device definition has a .PDF (print device function) extension. Definitions required for your environment must be imported into NetWare print services using the NetWare Administrator or PRINTDEF.If your printer does not match the predefined print devices, you can create a print device by defining the correct control sequences in the NetWare Administrator or PRINTDEF. The control sequences for your machine are found in your printer manual.Print device definitions also allow you to specify modes (groups of one or more functions) for use in print job configurations. Modes can prepare the printer for a print job, combine functions, reset the printer back to default settings, etc.PAGENUM=264 ID="BP265"You specify print device modes using the NetWare Administrator or PRINTDEF. These modes can then be included in print job configurations you create in PRINTCON. The NPRINT, CAPTURE, and PCONSOLE utilities use the print job configurations to send print jobs to your printer with the correct control sequences.See also IDREF="FM33109""Print header and print tail"; Chapter 9, "BOOK="printenu" COLLECTION="nw41"Working with Print Device Definitions and Printer Forms," of Print Services.RENDERAS="SECT1"Print driverIDXID="w2253"BOOK="_idx" COLLECTION="nw41" TIDREF="i1557"IDXID="w2254"BOOK="_idx" COLLECTION="nw41" TIDREF="i3390"IDXID="w2255"BOOK="_idx" COLLECTION="nw41" TIDREF="i1226"A driver that converts print jobs (usually generated by an application) to a format that can be read by the type of printer being used.RENDERAS="SECT1"ID="FM33109"Print header and print tailIDXID="w2256"BOOK="_idx" COLLECTION="nw41" TIDREF="i3390"IDXID="w2257"BOOK="_idx" COLLECTION="nw41" TIDREF="i3390"Contain transport control codes for the modes defined in PRINTDEF. The print header precedes the data to the print queue, and the print tail follows it. The default lengths are 64 and 16 bytes, respectively. These are especially critical for postscript printing.RENDERAS="SECT1"ID="FM41066"Print jobIDXID="w2258"BOOK="_idx" COLLECTION="nw41" TIDREF="i3416"A file stored in a print queue directory waiting to be printed. As soon as a print server sends a print job to the printer, the print job is deleted from the queue directory.Each print job is assigned a filename with a variation of the first four characters of the print queue directory ID, four more numerals, and a .Q extension.For example, if the print queue directory is named 4B020057.QDR, the first print job to enter the empty print queue would be named 024B0001.Q.If more print jobs entered the print queue before the current print job was printed, they would be named 024B0002.Q, 024B0003.Q, 024B0004.Q, etc.As soon as print job 024B0001.Q is printed, the next print job to enter the print queue is named 024B0001.Q. Like all print jobs, it would follow the first-in, first-out basis, unless the print job was held, or a print queue operator changed the order of service.PAGENUM=265 ID="BP266"Print jobs can be submitted to the print queue through NDS or through bindery services.RENDERAS="SECT1"Print job configurationIDXID="w2259"BOOK="_idx" COLLECTION="nw41" TIDREF="i3416"IDXID="w2260"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"A set of options that determine how a job is printed. The characteristics may include the following:MARK=BULLETPrinter to be usedPrint queue to be usedNumber of copies to printUse of a banner pagePrinter formPrint device modeUsers can create print job configurations using the NetWare Administrator or PRINTCON.See also "BOOK="printenu" COLLECTION="nw41"Printing Tasks Handled Through NetWare Administrator" in Chapter 3 and "BOOK="printenu" COLLECTION="nw41"Working with Print Device Definitions and Printer Forms" in Chapter 9 of Print Services.RENDERAS="SECT1"ID="FM87171"Print queueIDXID="w2261"BOOK="_idx" COLLECTION="nw41" TIDREF="i3439"A network directory that stores print jobs. When the printer assigned to a print queue is ready, the print server takes the print job out of the print queue and sends it to the printer.The print queue can hold as many print jobs as disk space allows.RENDERAS="SECT2"Print Queue SetupWhen you create a print queue in NetWare Administrator or PCONSOLE, a corresponding directory is created.PAGENUM=266 ID="BP267"In NDS, the print queue directory resides in the QUEUES directory on the volume specified.In a bindery server, the print queue directory resides in the SYSTEM directory on volume SYS: of the current server.The Quick Setup option in PCONSOLE automatically creates a print queue for each printer. This simplifies your printing setup. (See Chapter 2, "BOOK="printenu" COLLECTION="nw41"Planning and Setting Up NetWare Print Services," in Print Services.)When you create a print queue, user ADMIN is assigned as a print queue operator, and all users in the same context are assigned as print queue users.To change these default assignments, use NetWare Administrator or PCONSOLE.Group EVERYONE (if it exists) is also automatically assigned as a print queue user. (See also IDREF="FM75638""Print queue operator.") RENDERAS="SECT2"Print Queue Directories and FilenamesThe print queue directory is assigned a random number. This number is the print queue ID seen in NetWare Administrator with a .QDR extension. The number is also displayed in PCONSOLE without the extension.If you name the queue according to the type or location of the printer, it is easier to remember which queue is serviced by which printer.For example, print queue LETTERHEAD_Q might be directory LEGAL/SYS:QUEUES/4B020057.QDR if configured on NetWare server LEGAL. The print queue ID would then be 4B020057.All print queue directories have the extension .QDR and contain files with .SYS and .SRV extensions that are flagged hidden and system. These files are visible with the NDIR utility.These filenames begin with "Q_" and use a variation of the first four digits of the print queue directory ID.PAGENUM=267 ID="BP268"The print queue directory in the previous example would contain hidden and system files named Q_024B.SYS and Q_024B.SRV. (See also IDREF="FM41066""Print job.")See Chapter 3, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with the NetWare Administrator Utility," and Chapter 4, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with PCONSOLE," in Print Services.RENDERAS="SECT1"ID="FM75638"Print queue operatorIDXID="w2262"BOOK="_idx" COLLECTION="nw41" TIDREF="i3439"A user who can edit other users' print jobs, delete print jobs from the print queue, or modify the print queue status by changing the operator flags.Print queue operators can also change the order in which print jobs are serviced. User ADMIN or equivalent can assign users to be print queue operators as necessary.See also Chapter 3, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with the NetWare Administrator Utility," and Chapter 4, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with PCONSOLE," in Print Services.RENDERAS="SECT1"ID="FM67352"Print queue sampling intervalIDXID="w2263"BOOK="_idx" COLLECTION="nw41" TIDREF="i3439"The time interval the print server waits between checking the print queues for jobs ready to be printed. The time period can be specified in PCONSOLE under "Printers." The default is 15 seconds.RENDERAS="SECT1"ID="FM15181"Print serverIDXID="w2264"BOOK="_idx" COLLECTION="nw41" TIDREF="i3453"A server that takes print jobs out of a print queue and sends them to a network printer.NetWare print servers run through PSERVER.NLM on a NetWare 4 server and can service up to 255 printers with any number of print queues assigned to the printers.In NetWare 3, print servers are loaded through either PSERVER.NLM on a file server or PSERVER.EXE on a dedicated workstation.PAGENUM=268 ID="BP269"See also Chapter 6, "BOOK="printenu" COLLECTION="nw41"Setting Up and Servicing Print Servers," in Print Services.RENDERAS="SECT1"Print Server objectIDXID="w2265"BOOK="_idx" COLLECTION="nw41" TIDREF="i3457"A leaf object appearing in the Directory tree that represents a network print server.See also IDREF="FM13600""Object"; IDREF="FM15181""Print server"; Chapter 6, "BOOK="printenu" COLLECTION="nw41"Setting Up and Servicing Print Servers," in Print Services.RENDERAS="SECT1"ID="FM55665"Print Server operatorIDXID="w2266"BOOK="_idx" COLLECTION="nw41" TIDREF="i3453"A user or member of a group delegated rights by User object ADMIN to manage the print server.A print server operator has rights to control notify lists, printers, and queue assignments.See also Chapter 3, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with the NetWare Administrator Utility," and Chapter 4, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with PCONSOLE," in Print Services.RENDERAS="SECT1"Print tailContains transport control codes for the modes defined in PRINTDEF. See IDREF="FM33109""Print header and print tail."RENDERAS="SECT1"ID="FM10765"PrinterIDXID="w2267"BOOK="_idx" COLLECTION="nw41" TIDREF="i3496"A peripheral piece of hardware used to produce printed material.Network printers can be attachedMARK=BULLETDirectly to the networkTo the printer port of a NetWare serverTo the printer port of a PC workstationIn NetWare 4, users can specify printer names as the destination of their print jobs. (Users can still specify print queues.) PAGENUM=269 ID="BP270"In NetWare 3, users must specify the print queue. RENDERAS="SECT2"Network Printer DriversEvery network printer driver requires a network printer (port) driver to pass a print job from the network to the printer. The type of driver depends on how the printer is attached to the network.Network-attached printers store their own port driver.Printers attached to workstations need NPRINTER.EXE loaded on the workstation.Printers attached to NetWare servers need NPRINTER.NLM loaded on the NetWare server.If PSERVER.NLM is loaded on the same NetWare server, it can load NPRINTER.NLM automatically for each printer cabled directly to the NetWare server.RENDERAS="SECT2"Differences between the Bindery and NetWare Directory Services In bindery-based NetWare, printers are defined as a subset of the print server. For that reason, a print server must exist before you can define a printer.With NDS, printers are objects used in conjunction with Print Server and Print Queue objects. They can be added, modified, or removed independently.Each network printer object must be defined using NetWare Administrator or PCONSOLE.See also IDREF="FM51702""Printing"; IDREF="FM27166""Print device definition"; Chapter 6, "BOOK="printenu" COLLECTION="nw41"Setting Up and Servicing Printers," in Print Services.RENDERAS="SECT1"ID="FM14172"Printer formIDXID="w2268"BOOK="_idx" COLLECTION="nw41" TIDREF="i3496"A print option designed to prevent print jobs from being printed on the wrong paper.NetWare print services allows you to designate a printer form for a print job. The print jobs will not print if the correct paper is not in the printer.PAGENUM=270 ID="BP271"For example, suppose your printer uses regular, letterhead, and bond paper. For each type of paper, you can create a printer form. Each form has a unique name and number (between 0 and 255).If you specify a form in a print job configuration, in NPRINT, or in CAPTURE with the form option, the print job does not print unless the mounted form matches the number required by the print job.You can change the number of the currently mounted form at the print server console, from NetWare Administrator, or from PCONSOLE.Printer forms are defined using NetWare Administrator or PRINTDEF.See also Chapter 3, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with the NetWare Administrator Utility," Chapter 4, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with PCONSOLE," and Chapter 9, "BOOK="printenu" COLLECTION="nw41"Working with Print Device Definitions and Printer Forms," of Print Services.RENDERAS="SECT1"Printer modeIDXID="w2269"BOOK="_idx" COLLECTION="nw41" TIDREF="i3390"A sequence of print functions (also called printer commands, control sequences, or escape sequences) that determines the appearance of the printed file.A printer mode can define the style, size, boldness, and orientation of the typeface.Print device modes are designated using NetWare Administrator or PRINTDEF.See also Chapter 3, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with the NetWare Administrator Utility," and Chapter 9,"BOOK="printenu" COLLECTION="nw41"Working with Print Device Definitions and Printer Forms," in Print Services.RENDERAS="SECT1"Printer objectIDXID="w2270"BOOK="_idx" COLLECTION="nw41" TIDREF="i3517"A leaf object that represents a physical printing device on the network.See also IDREF="FM13600""Object."PAGENUM=271 ID="BP272"RENDERAS="SECT1"ID="FM51702"PrintingIDXID="w2271"BOOK="_idx" COLLECTION="nw41" TIDREF="i3538"The ability to transfer data from computer files to paper.NetWare 4 allows users to share printers on the network, where previously each personal computer had to have a printer attached to one of its printer ports.The following figure shows non-network printing:FILEREF="n40co40a.tif"NetWare 4 uses a print queue and print server to allow workstations to print to a printer. The print server takes print jobs from the print queue and sends them to the printer.LABEL="64" FLOAT="0"Network PrintingFILEREF="n40co41a.tif"See also IDREF="FM15181""Print server"; IDREF="FM87171""Print queue"; IDREF="FM10765""Printer"; Chapter 1, "BOOK="printenu" COLLECTION="nw41"Introduction to NetWare Print Services," of Print Services.PAGENUM=272 ID="BP273"RENDERAS="SECT1"Profile login scriptIDXID="w2272"BOOK="_idx" COLLECTION="nw41" TIDREF="i3565"IDXID="w2273"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"A type of login script that sets environments for a group of users. Use profile login scripts if there are groups of users with identical login script needs.Profile login scripts are optional; if used, they execute after the container login script and before the user login script.See also IDREF="FM23712""Login scripts."RENDERAS="SECT1"Profile objectIDXID="w2274"BOOK="_idx" COLLECTION="nw41" TIDREF="i3569"A leaf object that represents a login script used by a group of users who need to share common login script commands.The group of users need not be located under the same container in the Directory tree. They can also be a subset of users in the same container.See also IDREF="FM13600""Object"; "BOOK="superenu" COLLECTION="nw41"Managing Profile Objects" in Chapter 1 of Supervising the Network.RENDERAS="SECT1"PromptIDXID="w2275"BOOK="_idx" COLLECTION="nw41" TIDREF="i3572"A character or message that appears on the display screen and requires a response (such as a command or a utility name) from the user.Standard types of prompts includeMARK=BULLETThe DOS prompt, which, by default, displays the current drive letter followed by a > symbol (for example, F>)The OS/2 prompt, which, by default, displays the current drive mapping in brackets (for example, [C:\])The NetWare server console prompt, which displays a colon (:)The DOS prompt is a DOS environment setting. You can change the DOS prompt using the SET PROMPT command in a batch file (such as AUTOEXEC.BAT), in the login script, or at the command line.PAGENUM=273 ID="BP274"For example, to change your DOS prompt at the command line so that the prompt displays the current drive mapping followed by the > symbol, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"SET PROMPT=$P$G MOREINFO="NONE"<Enter>The OS/2 prompt is an OS/2 environment setting that is included in a workstation's CONFIG.SYS file.You can change the OS/2 prompt by modifying the SET PROMPT parameter in the CONFIG.SYS file, or by using a SET PROMPT command in the login script or at the command line.See your respective DOS or OS/2 manual for further details on changing prompts, including prompt variables. (The NetWare server console prompt can't be changed.)See also IDREF="FM39775""Drive mapping"; IDREF="FM23712""Login scripts."RENDERAS="SECT1"PropertyIDXID="w2276"BOOK="_idx" COLLECTION="nw41" TIDREF="i3575"IDXID="w2277"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"A characteristic of an NDS object. Each type of object (such as a User object, Organization object, or Profile object) has certain properties that hold information about the object.For example, a User object's properties include login name, E-mail address, password restrictions, group memberships, etc.As another example, a Profile object's properties include profile name, login script, and volume.The only properties required for objects are those you enter when you create a new object. You must enter a value in each field.Properties you must enter when you create an object can be properties that name the object, or properties required to create the object.For example, when you create a volume object, you must specify the volume's host server.PAGENUM=274 ID="BP275"Many of an object's properties can contain multiple values. For example, the telephone number property, found in many object types, can contain several different telephone numbers.NETADMIN and NetWare Administrator allow you to see and change properties for any object to which you have sufficient rights.See also IDREF="FM13600""Object."RENDERAS="SECT1"Property rightsRights that apply to the properties of an NDS object.See also IDREF="FM74455""Rights."RENDERAS="SECT1"ID="FM77302"Protected modeIDXID="w2278"BOOK="_idx" COLLECTION="nw41" TIDREF="i3583"IDXID="w2279"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"Provides the capability of multitasking (running more than one application or process at a time).Protected mode allocates memory to various processes running concurrently so that memory used by one process doesn't overlap memory used by another process.By default, 80286, 80386, 80486 and Pentium processors run in protected mode. When running in protected mode, these processors aren't subject to the same memory constraints as 8086 processors.The 80286 processor uses a 24-bit address bus and can address up to 16 MB of memory. The 80386, 80486, and the Pentium processors use a 32-bit address bus and can address up to 4 GB of memory.By contrast, 8086 processors can address only 1 MB of memory, and can run only one application or process at a time.80286, 80386, 80486, and the Pentium processors can be set to run in real mode, in which case they emulate an 8086 processor (and are subject to its memory constraints).See also IDREF="FM25891""Read/write replica."PAGENUM=275 ID="BP276"RENDERAS="SECT1"ProtocolsIDXID="w2280"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"IDXID="w2281"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"Conventions or rules used by a program or operating system to communicate between two or more endpoints.See also IDREF="FM41940""AppleTalk protocols"; IDREF="FM34819""Communication protocols"; IDREF="FM46616""NetWare protocols and transports."RENDERAS="SECT1"Proxy ARPIDXID="w2282"BOOK="_idx" COLLECTION="nw41" TIDREF="i3617"A technique by which a router replies to an Address Resolution Protocol (ARP) request from a host on behalf of the ARP target host.Proxy ARP enables a router to support routing within a subnetted IP network with hosts that do not recognize the subnetting. In this situation, knowledge of the subnets is limited to the subnet routers, and the hosts see only the IP network. By letting the subnet routers reply to ARP requests from hosts on behalf of hosts on other subnets reachable through the router, the hosts do not have to know about the subnets attached to the network. This use of Proxy ARP is referred to as ARP subnet routers.However, because most IP hosts now understand subnetting, ARP subnet routers are not used as often as they once were. Instead, the network configuration, called stub subnetworks or stub networks, is now the most common use of Proxy ARP.A stub network is a segment that has an address range that is a subset of the address range of another segment (the parent network). The parent network and the stub network are separated by a router. An example is a parent network with an address range of 89.0.0.1 to 89.255.255.254 and a stub network with an address range of 89.1.0.1 to 89.1.255.254.For more information on Proxy ARP, refer to RFC 1027.See also IDREF="FM81485""Address Resolution Protocol."PAGENUM=276 ID="BP277"RENDERAS="SECT1"IDXID="w2283"BOOK="_idx" COLLECTION="nw41" TIDREF="i3623"
Pseudo hop countThe number of hops that the primary server adds to the true hop count (the number of internal and external bridges and routers between a client and the server) when it advertises the route to the SFT III MSEngine.If SFT III servers reside on different network segments, the hop count for one server is higher than the other. To ensure that packets are rerouted properly to the surviving server in the event one server fails, the primary server advertises an artificially high hop count---the true hop count plus a pseudo hop count, as shown in the following figure:LABEL="65" FLOAT="0"Pseudo Hop CountFILEREF="n41co55a.tif"SFT III uses the pseudo hop count to accelerate routing changes when a server switchover occurs in mirrored servers on different network segments. PAGENUM=277 ID="BP278"If the SFT III servers are installed on the same network segment, there are no routers and SFT III does not use the pseudo hop count.If the primary server fails, the surviving server advertises the true hop count. Routers immediately see the surviving server as the best route to the MSEngine.The total hop count (the true hop count plus the pseudo hop count) between a client and the server cannot exceed 16.SET parameters enable the pseudo hop count and determine its maximum value.RENDERAS="SECT1"ID="FM82664"PUBLIC directoryIDXID="w2284"BOOK="_idx" COLLECTION="nw41" TIDREF="i3634"The SYS:PUBLIC directory, created during network installation, that allows general access to the network and contains NetWare utilities and programs for network users.NetWare users running DOS have a search drive mapped to SYS:PUBLIC through the container login script and are assigned Read and File Scan rights to this directory.NetWare users running OS/2 access NetWare utilities from the SYS:PUBLIC/OS2 directory.Don't delete the PUBLIC directory.See also IDREF="FM22177""File system"; IDREF="FM52477""LOGIN directory"; IDREF="FM38021""MAIL directory"; IDREF="FM79008""SYSTEM directory."RENDERAS="SECT1"Public filesIDXID="w2285"BOOK="_idx" COLLECTION="nw41" TIDREF="i3631"Files that must be accessed by all NetWare users, including NetWare utilities, help files, and some message and data files.By convention, the files are located in SYS:PUBLIC for DOS users, and in SYS:PUBLIC/OS2 for OS/2 users.All NetWare users have Read and File Scan rights to the files.PAGENUM=278 ID="BP279"RENDERAS="SECT1"Public trusteeIDXID="w2286"BOOK="_idx" COLLECTION="nw41" TIDREF="i3631"IDXID="w2287"BOOK="_idx" COLLECTION="nw41" TIDREF="i4591"A special trustee that can be added to any object, directory, or file. By default, [Public] includes the Read right and the File Scan right.By making [Public] a trustee of an object, directory, or file, you effectively grant all objects in NDS rights to that object, directory, or file.[Public] is only used in trustee assignments and must always be entered within square brackets. [Public] can be added or deleted like any other trustee. An Inherited Rights Filter blocks inherited rights for [Public] as it would any other trustee.Assigning [Public] as a trustee is similar to granting trustee rights to user GUEST or group EVERYONE in previous NetWare versions.You can make [Public] a trustee of areas that every object should have access to. (A user doesn't have to log in to access areas where [Public] is granted rights.)However, in most cases, it is better to make a container object a trustee rather than making [Public] a trustee. This grants rights only to the objects within the container, improving security control.During NetWare 4.1 installation, [Public] is granted the Browse object right at the root object of the Directory tree.See also IDREF="FM13738""Inherited Rights Filter"; IDREF="FM26134""Trustee."RENDERAS="SECT1"Purge (P) attributeIDXID="w2288"BOOK="_idx" COLLECTION="nw41" TIDREF="i3640"A file system attribute that causes NetWare to purge the directory or file when it is deleted.See also IDREF="FM85330""Attributes."PAGENUM=279 ID="BP280"QRENDERAS="SECT1"QueueIDXID="w2289"BOOK="_idx" COLLECTION="nw41" TIDREF="i3647"A network directory that stores each print job. When the printer assigned to the print queue is ready, the print server takes the print job out of the print queue and sends it to the printer.See IDREF="FM87171""Print queue." See also Chapter 3, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with the NetWare Administrator Utility," and Chapter 4, "BOOK="printenu" COLLECTION="nw41"Managing Print Services with PCONSOLE," in Print Services.RENDERAS="SECT1"Queue sampling intervalIDXID="w2290"BOOK="_idx" COLLECTION="nw41" TIDREF="i3652"The time interval the print server waits between checking the print queues for jobs ready and waiting to be printed.See IDREF="FM67352""Print queue sampling interval."RENDERAS="SECT1"ID="FM29980"Queue server modeAn operating mode used by many network-direct printers and hardware queue servers produced by various manufacturers. These devices either connect to a printer and then to the network or are installed in a port at the printer.In many cases, these devices offer a fast, effective, low-cost printing solution in NetWare 4 as well as NetWare 3 environments. In queue server mode, the hardware print server directly accesses the print queue using NCP calls. Under most circumstances, this mode places the least load on a NetWare server. In NetWare 3, it was also faster than remote printer mode, but the improved performance of the NetWare 4 PSERVER has minimized this distinction.Queues created in the bindery context can be seen by both NDS and bindery users, so both types of users can access these hardware print servers.PAGENUM=280 ID="BP281"See also "BOOK="printenu" COLLECTION="nw41"Using Third-Party Network-Direct Print Devices with NetWare 4" in Chapter 6 of Print Services.PAGENUM=281 ID="BP282"RRENDERAS="SECT1"ID="FM21738"RAMIDXID="w2291"BOOK="_idx" COLLECTION="nw41" TIDREF="i3666"(Random Access Memory) The internal dynamic storage of a computer that can be addressed by the computer's operating system.See also IDREF="FM11327""Memory."RENDERAS="SECT1"RARP(Reverse Address Resolution Protocol) The process of determining the Internet address from a local data link address.See IDREF="FM24801""Reverse Address Resolution Protocol."RENDERAS="SECT1"Read-after-write verificationIDXID="w2292"BOOK="_idx" COLLECTION="nw41" TIDREF="i3689"A means of assuring that data written to the hard disk matches the original data still in memory.If the data from the disk matches the data in memory, the data in memory is released.If the data doesn't match, the block location is recognized as bad, and Hot Fix redirects the data to a good block location within the Hot Fix Redirection Area.See also IDREF="FM20059""Data protection."RENDERAS="SECT1"Read-only replicaThe Directory replica used to view, but not modify, Directory information.See IDREF="FM27324""NetWare Directory replica."RENDERAS="SECT1"Read Only (Ro) attributeIDXID="w2293"BOOK="_idx" COLLECTION="nw41" TIDREF="i3681"A file system attribute that indicates that no one can write to the file.PAGENUM=282 ID="BP283"See also IDREF="FM85330""Attributes."RENDERAS="SECT1"Read rightIDXID="w2294"BOOK="_idx" COLLECTION="nw41" TIDREF="i3686"A file system right that grants the right to open and read files.Also, a property right that grants the right to read the values of the property.See also IDREF="FM74455""Rights."RENDERAS="SECT1"ID="FM25891"Read/write replicaThe Directory replica used to read or update Directory information (such as adding or deleting objects).See IDREF="FM27324""NetWare Directory replica."RENDERAS="SECT1"Real modeIDXID="w2295"BOOK="_idx" COLLECTION="nw41" TIDREF="i3695"The mode that allows an 80286, 80386, or 80486 processor to emulate an 8086 processor and run as though it were an 8086 processor.The 8086 processor uses a 20-bit address bus, and can address up to 1 MB of memory. The 8086 processor is also limited to running only one application or process at a time.When running in protected mode, the 80286, 80386, and 80486 processors are capable of multitasking and addressing much more than 1 MB of memory.When running in real mode, these processors are subject to the same 1MB memory constraint as the 8086 processor, and they can run only one application or process at a time.However, the 80286, 80386, and 80486 processors running in real mode still perform more efficiently than the 8086 processor because they operate at a faster clock rate.See also IDREF="FM77302""Protected mode."PAGENUM=283 ID="BP284"RENDERAS="SECT1"ID="FM29327"Record lockingIDXID="w2296"BOOK="_idx" COLLECTION="nw41" TIDREF="i3703"IDXID="w2297"BOOK="_idx" COLLECTION="nw41" TIDREF="i2180"A feature of the NetWare operating system that prevents different users from gaining simultaneous access to the same record in a shared file, preventing overlapping disk writes and ensuring data integrity.See also IDREF="FM51849""File locking."RENDERAS="SECT1"Recursive copyingIDXID="w2298"BOOK="_idx" COLLECTION="nw41" TIDREF="i3713"IDXID="w2299"BOOK="_idx" COLLECTION="nw41" TIDREF="i849"The process of copying a specified source directory to a destination directory until all files and subdirectories in and below the specified source directory are copied.Recursive copying copies all directories and files of a logical drive to the destination, keeping them exactly as they were in the source directory.The DOS and OS/2 XCOPY and BACKUP utilities use recursive copying, as does the NetWare NCOPY command.RENDERAS="SECT1"Redirection areaIDXID="w2300"BOOK="_idx" COLLECTION="nw41" TIDREF="i3717"(Hot Fix Redirection Area) The space on a hard disk set aside to hold data redirected from faulty disk blocks.See IDREF="FM95725""Hot Fix."RENDERAS="SECT1"Reference time serverA server that specifies the time to which all other time servers and workstations synchronize.See also IDREF="FM65772""Time synchronization."RENDERAS="SECT1"Registered resourcesIDXID="w2301"BOOK="_idx" COLLECTION="nw41" TIDREF="i3723"IDXID="w2302"BOOK="_idx" COLLECTION="nw41" TIDREF="i3821"Network resources that report information to the NetWare Management Agent.Registration is the process by which key software, hardware, and data components identify themselves, along with the objects they control and all associated attributes, to the NetWare Management Agent.PAGENUM=284 ID="BP285"A registered resource can then be monitored and managed by a management software program designed to work with the NetWare Management Agent.For example, a server could have its disk drive and certain drive attributes registered as a manageable object. A management software program would then be able to monitor and manage the server's disk drive.RENDERAS="SECT1"Remote bootIDXID="w2303"BOOK="_idx" COLLECTION="nw41" TIDREF="i3738"IDXID="w2304"BOOK="_idx" COLLECTION="nw41" TIDREF="i489"A method that allows a user to boot a workstation from remote boot image files on a NetWare server rather than from a boot diskette in the workstation's local drive.Client workstations that can start using remote booting do not need a floppy or hard drive to function on the network, and are therefore called diskless workstations. A diskless workstation relies on a Programmable Read Only Memory (PROM) chip installed in its network board to communicate with the boot server. NetWare allows you to use a default image file for all diskless workstations on the network or to use customized image files unique to each workstation's particular system and network environment.See also IDREF="FM88007""Remote printer mode."RENDERAS="SECT1"Remote connectionIDXID="w2305"BOOK="_idx" COLLECTION="nw41" TIDREF="i3738"IDXID="w2306"BOOK="_idx" COLLECTION="nw41" TIDREF="i780"A connection between a LAN on one end and a workstation or network on the other, often using telephone lines and modems.A remote connection allows data to be sent and received across greater distances than those allowed by normal cabling.RENDERAS="SECT1"Remote consoleIDXID="w2307"BOOK="_idx" COLLECTION="nw41" TIDREF="i3738"IDXID="w2308"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"Software that allows network supervisors to manage servers from a workstation. To create a remote console session, invoke the RCONSOLE.EXE client utility. PAGENUM=285 ID="BP286"RCONSOLE enhances security since you can lock servers in a safe place and remove the keyboards and monitors.From a remote console, network supervisors canMARK=BULLETUse console commands as if they were at the server consoleScan directories and edit text files in both NetWare and non-NetWare partitions on a serverTransfer files to (but not from) a serverBring down a serverInstall or upgrade NetWare on a remote serverYou can set up direct or asynchronous connections to a server:MARK=BULLETDirect connection. A station establishes a remote console session with a server on the local or wide area network, connected by cabling or by a wide-area link using IPX/SPX protocol.Asynchronous connection. A station establishes a remote console session with a server through a modem or null modem cable.See also "BOOK="superenu" COLLECTION="nw41"Using Remote Console to Manage a Server" in Chapter 7 of Supervising the Network.RENDERAS="SECT1"ID="FM88537"Remote Program LoadIDXID="w2309"BOOK="_idx" COLLECTION="nw41" TIDREF="i3759"(RPL) Technology based on the concept of storing an image of a bootable floppy disk on a NetWare volume. Remote boot workstations use this image to start up the system prompt.These client workstations do not need a floppy or hard drive to function on the network and are, therefore, called diskless workstations. A diskless workstation relies on a programmable read-only memory (PROM) chip installed in its network board. This chip allows the workstation to communicate with the boot server.PAGENUM=286 ID="BP287"When the workstation is turned on, it uses the boot image stored on a server to load the DOS system and NetWare Client files necessary to connect to the network. The image file can include any files you would normally load from a boot diskette.NetWare allows you to use a default image file for all diskless workstations on the network, or to use customized image files unique to each workstation's particular system and network environment.RENDERAS="SECT1"ID="FM88007"Remote printer modeIDXID="w2310"BOOK="_idx" COLLECTION="nw41" TIDREF="i3496"An operating mode used by many network-direct printers and hardware queue servers produced by various manufacturers. Network-direct printers and hardware queue servers either connect to a printer and then to the network or are installed in a port at the printer. In many cases, these devices offer a fast, effective, low-cost printing solution in NetWare 4 and NetWare 3 environments. In this mode, the device functions in a way similar to a workstation running NetWare 4 NPRINTER or NetWare 3 RPRINTER. Devices configured for remote printer mode are controlled by a NetWare print server.Devices running in this mode under NetWare 4 run considerably faster than they did under NetWare 3. The increased speed and flexibility offered with NetWare 4 makes remote printer mode a very effective way of providing network printing with these devices.In order to run these devices in remote printer mode under NetWare 4, be sure you have loaded PSERVER.NLM at the NetWare server console. See also "BOOK="printenu" COLLECTION="nw41"Using Third-Party Network-Direct Print Devices with NetWare 4" in Chapter 6 of Print Services. RENDERAS="SECT1"Remote ResetIDXID="w2311"BOOK="_idx" COLLECTION="nw41" TIDREF="i3738"IDXID="w2312"BOOK="_idx" COLLECTION="nw41" TIDREF="i3816"Software that allows you to boot a DOS workstation (including a diskless workstation) from a remote boot image file on a NetWare server, rather than from a boot diskette in the workstation's local drive.PAGENUM=287 ID="BP288"To use Remote Reset to boot a workstation, install a Remote Reset PROM on the station's network board and run the DOSGEN utility.DOSGEN uploads the station's boot files into a remote boot image file, NET$DOS.SYS, in the server's LOGIN directory.The remote boot image file includes the station's AUTOEXEC.BAT file, used by the station as if the file were present on a local boot diskette.Copy the workstation's AUTOEXEC.BAT file to the remote boot image file, to the LOGIN directory, and to any default directory named in the workstation's login script.RENDERAS="SECT2"Using Remote Reset with Multiple ServersIf you have multiple NetWare servers on your network, copy the remote boot image files onto each server that may come up as the remote boot workstation's default server.Then, if the first default server isn't available, the station can boot from the next available server.RENDERAS="SECT2"Using Multiple Remote Boot Image FilesFor multiple workstations with different configurations to use Remote Reset, upload multiple remote boot image files into SYS:LOGIN.Instead of the single NET$DOS.SYS file, create a separate remote boot image file for each workstation. Name the image files for each user (for example, FRED.SYS for user FRED).Then, in the LOGIN directory, create a BOOTCONF.SYS file, which is a DOS text file that, for each station's network board, identifies theMARK=BULLETIPX external network numberNode numberRemote boot image filename (FRED.SYS)PAGENUM=288 ID="BP289"See also Chapter 6, "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Remote Client Workstations," of NetWare Client for DOS and MS Windows User Guide.RENDERAS="SECT1"Remote workstationIDXID="w2313"BOOK="_idx" COLLECTION="nw41" TIDREF="i3738"IDXID="w2314"BOOK="_idx" COLLECTION="nw41" TIDREF="i4837"A terminal or personal computer connected to the LAN by a router or through a remote asynchronous connection.A remote workstation can be either a standalone computer or a workstation on another network.RENDERAS="SECT1"Rename Inhibit (Ri) attributeIDXID="w2315"BOOK="_idx" COLLECTION="nw41" TIDREF="i3774"A file system attribute that prevents any user from renaming the directory or file.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"Rename rightIDXID="w2316"BOOK="_idx" COLLECTION="nw41" TIDREF="i3777"An object right that grants the right to change the name of an object, in effect changing the naming property.See also IDREF="FM74455""Rights."RENDERAS="SECT1"ID="FM87430"ReplicaA copy of a NetWare Directory partition.See IDREF="FM27324""NetWare Directory replica."RENDERAS="SECT1"Resource forkIDXID="w2317"BOOK="_idx" COLLECTION="nw41" TIDREF="i3818"IDXID="w2318"BOOK="_idx" COLLECTION="nw41" TIDREF="i1542"The part of a Macintosh file that contains file resources, including Macintosh-specific information such as the windows and icons used with the file.See also IDREF="FM57339""Data fork"; IDREF="FM86837""Macintosh files."RENDERAS="SECT1"Resource tagsIDXID="w2319"BOOK="_idx" COLLECTION="nw41" TIDREF="i3820"IDXID="w2320"BOOK="_idx" COLLECTION="nw41" TIDREF="i4421"Operating system tags that keep track of NetWare server resources such as screens and allocated memory.PAGENUM=289 ID="BP290"NLM programs request a resource from the NetWare server for each kind of resource they use and then give it a resource tag name.NLM programs return resources when they no longer need them. When the NLM is unloaded, the resources are returned to the NetWare server.Resource tags ensure that allocated resources are properly returned to the operating system upon termination of an NLM program.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.RENDERAS="SECT1"ResourcesIDXID="w2321"BOOK="_idx" COLLECTION="nw41" TIDREF="i3821"The manageable components of a network, includingMARK=BULLETNetworking components, such as cabling, hubs, concentrators, adapters, and network boardsHardware components, such as servers, workstations, hard disks, and printersMajor software components, such as the NetWare operating system and resulting network services (including file, mail, queue, and communication)Minor software components that are controlled by the operating system of its subsystems---protocols, gateways, LAN and disk drivers, etc.Data structures and other network resources such as volumes, queues, users, processes, security, etc.RENDERAS="SECT1"ID="FM84298"RestoreIDXID="w2322"BOOK="_idx" COLLECTION="nw41" TIDREF="i3830"A retrieval of data previously copied and backed up to a storage media. Perform a restore if data has been lost or corrupted since the backup.See also IDREF="FM24312""Backup"; IDREF="FM76561""Data set."PAGENUM=290 ID="BP291"RENDERAS="SECT1"IDXID="w2323"BOOK="_idx" COLLECTION="nw41" TIDREF="i3836"
ResynchronizationThe process of returning SFT III servers to a mirrored (identical) state.When both SFT III servers are restored to operation following a failure, they automatically resynchronize memory images and remirror disks. The time it takes the servers to complete resynchronization depends on the amount of memory and the disk storage in each server. Server memory synchronization is much faster than disk remirroring because disk remirroring speed is limited by the disk channel.Both servers---primary and secondary---continually poll each other so that each server is aware of its partner's state. Whenever an SFT III server is running in an unmirrored state, it searches for its partner. As soon as it detects the presence of its partner on the other end of the mirrored server link, it automatically attempts to synchronize with the other server and return to a mirrored state.Following a failure, SFT III tracks changes to the surviving server's disk and remirrors only the information that has changed. New data from the surviving server's disk is copied to the failed server's disk when the failed server is restored to operation.Workstation and printer activity halts during memory synchronization, and workstations may appear to freeze for a few seconds. However, workstations are unaffected while the two servers' disks are remirrored because this process occurs in background mode. Heavy network activity may slow down the remirroring process. Until disk remirroring is complete, the secondary server gets its disk data from the primary server. Thus, the secondary server is not fully operational until all disks are remirrored.RENDERAS="SECT1"ID="FM24801"Reverse Address Resolution ProtocolIDXID="w2324"BOOK="_idx" COLLECTION="nw41" TIDREF="i3848"(RARP) The process of determining the Internet address from a local data link address.PAGENUM=291 ID="BP292"To communicate with a device on Ethernet, the router first must determine the 8-bit MAC or local data link address of that device. The process of determining the local data link address from an Internet address is called address resolution. RARP provides the reverse functionality.See also IDREF="FM81485""Address Resolution Protocol."RENDERAS="SECT1"Ribbon cableIDXID="w2325"BOOK="_idx" COLLECTION="nw41" TIDREF="i3850"IDXID="w2326"BOOK="_idx" COLLECTION="nw41" TIDREF="i560"A cable in which the wires are placed side by side in the insulation material instead of being bunched or twisted together in a circle inside the insulation material.Typically, ribbon cables are used for connecting internal disks or tape drives.RENDERAS="SECT1"ID="FM74455"RightsIDXID="w2327"BOOK="_idx" COLLECTION="nw41" TIDREF="i3851"Qualities assigned to an object that control what the object can do with directories, files, or other objects. Creating, reading, and other operations can be done only if an object has rights to perform them.Rights are granted to a specific directory, file, or object by trustee assignments. An object with a trustee assignment to a file, directory, or another object is a trustee of that file, directory, or object.Within each object is a list of who has rights to the object and what rights the object has to other objects. This list is the ACL property of the object. (Files and directories contain similar information, but not an ACL.)For example, to grant user JILL the right to delete a Printer object, go to the Printer object and make JILL a trustee; don't go to Jill and make the Printer object a trustee.RENDERAS="SECT2"Directory RightsIDXID="w2328"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"Directory rights apply to the directory in the NetWare file system they are assigned to, as well as to all files and subdirectories in that directory (unless redefined at the file or subdirectory level).Directory rights are a part of the file system. They aren't assigned to NDS objects. But, a User object can be granted Directory rights to a directory on a volume.PAGENUM=292 ID="BP293"IDXID="w2329"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"
The following table describes directory rights.LABEL="13" PGWIDE=1 TOCENTRY="1" Directory RightsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"RightCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SupervisorCOLNAME=2 ROTATE="0" MOREROWS="0"Grants all rights to the directory, its files, and subdirectories. The Supervisor right can't be blocked by an Inherited Rights Filter. Users with this right can grant other users rights to the directory, its files, and subdirectories.COLNAME=1 ROTATE="0" MOREROWS="0"ReadCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to open files in the directory and read the contents or run the programs.COLNAME=1 ROTATE="0" MOREROWS="0"WriteCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to open and change the contents of files in the directory.COLNAME=1 ROTATE="0" MOREROWS="0"CreateCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to create new files and subdirectories in the directory. If Create is the only right granted to a trustee for the directory, and no other rights are granted below the directory, a drop box directory is created.In a drop box directory, you can create a file and write to it. Once the file is closed, however, only a trustee with more rights than Create can see or update the file. You can copy files or subdirectories into the directory and assume ownership of them, but other users' rights are revoked.COLNAME=1 ROTATE="0" MOREROWS="0"EraseCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to delete the directory, its files, and subdirectories.COLNAME=1 ROTATE="0" MOREROWS="0"ModifyCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to change the attributes or name of the directory and of its files and subdirectories, but does not grant the right to change the contents of them. (Changing the contents requires the Write right.)COLNAME=1 ROTATE="0" MOREROWS="0"File ScanCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to see the directory and its files with the DIR or NDIR command.COLNAME=1 ROTATE="0" MOREROWS="0"Access ControlCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to change the trustee assignments and the Inherited Rights Filter of the directory and of its files and subdirectories.RENDERAS="SECT2"File RightsIDXID="w2330"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"File rights apply only to the file they are assigned to. A trustee can also inherit rights to a file from the directory above the file.PAGENUM=293 ID="BP294"The following table describes file rights.LABEL="14" PGWIDE=1 TOCENTRY="1" File RightsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"RightCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SupervisorCOLNAME=2 ROTATE="0" MOREROWS="0"Grants all rights to the file. The Supervisor file right can't be blocked with an Inherited Rights Filter. Users who have this right can also grant other users any rights to the file and can change the file's Inherited Rights Filter.COLNAME=1 ROTATE="0" MOREROWS="0"ReadCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to open and read the file.COLNAME=1 ROTATE="0" MOREROWS="0"CreateCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right create a file and to salvage a file after it has been deleted.COLNAME=1 ROTATE="0" MOREROWS="0"WriteCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to open and write to an existing file.COLNAME=1 ROTATE="0" MOREROWS="0"EraseCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to erase (delete) the file.COLNAME=1 ROTATE="0" MOREROWS="0"ModifyCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to change the attributes and name of the file, but does not grant the right to change its contents. (Changing the contents requires the Write right.)COLNAME=1 ROTATE="0" MOREROWS="0"File ScanCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to see the file with the DIR or NDIR directory command, including the directory structure from that file to the root directory.COLNAME=1 ROTATE="0" MOREROWS="0"Access ControlCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to change the trustee assignments and the Inherited Rights Filter of the file.RENDERAS="SECT2"Object RightsIDXID="w2331"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"
Object rights apply to NDS objects. Object rights don't affect the properties of an object (see property rights later in this section). A trustee can inherit rights to an object from the object above it.PAGENUM=294 ID="BP295"The following table describes object rights.LABEL="15" PGWIDE=1 TOCENTRY="1" Object RightsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"RightCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SupervisorCOLNAME=2 ROTATE="0" MOREROWS="0"Grants all access privileges. A trustee with the Supervisor object right also has unrestricted access to all properties. The Supervisor object right can be blocked by an Inherited Rights Filter below the object where the Supervisor right is granted.COLNAME=1 ROTATE="0" MOREROWS="0"BrowseCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to see this object in the Directory tree. The name of the object is returned when a search is made that matches the object.COLNAME=1 ROTATE="0" MOREROWS="0"CreateCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to create a new object below this object in the Directory tree. Rights are not defined for the new object. This right is only available on container objects because non-container objects can't have subordinates.COLNAME=1 ROTATE="0" MOREROWS="0"DeleteCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to delete the object from the Directory tree. Objects that have subordinates can't be deleted (unless subordinates are deleted first).COLNAME=1 ROTATE="0" MOREROWS="0"RenameCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to change the name of the object, in effect changing the naming property. This changes the object's complete name.RENDERAS="SECT2"Property RightsIDXID="w2332"BOOK="_idx" COLLECTION="nw41" TIDREF="i3580"
Property rights apply to the properties of an NDS object. Rights can be assigned to all properties as a whole or to selected properties.The following table describes property rights:LABEL="16" PGWIDE=1 TOCENTRY="1" Property RightsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"RightCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SupervisorCOLNAME=2 ROTATE="0" MOREROWS="0"Grants all rights to the property. The Supervisor property right can be blocked by an object's Inherited Rights Filter.COLNAME=1 ROTATE="0" MOREROWS="0"CompareCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to compare any value to a value of the property. With the compare right, an operation can return True or False, but you can't see the value of the property. The Read right includes the Compare right.COLNAME=1 ROTATE="0" MOREROWS="0"ReadCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to read the values of the property. Compare is a subset of Read. If the Read right is given, compare operations are also allowed.COLNAME=1 ROTATE="0" MOREROWS="0"WriteCOLNAME=2 ROTATE="0" MOREROWS="0"Grants the right to add, change, or remove any values of the property. The Write right includes the Add or Delete Self right.COLNAME=1 ROTATE="0" MOREROWS="0"Add or Delete SelfCOLNAME=2 ROTATE="0" MOREROWS="0"Grants a trustee the right to add or remove itself as a value of the property. The trustee can't affect any other values of the property. This right is only meaningful for properties that contain object names as values, such as group membership lists or mailing lists. The Write right includes Add or Delete Self.PAGENUM=295 ID="BP296"To grant directory or file rights to other objects, a trustee must have the Access Control right to a directory or file.To grant object or property rights to other objects, a trustee must have the Write, Add or Delete Self, or Supervisor right to the ACL property of the object.Rights are granted and revoked by creating trustee assignments with the RIGHTS, NETADMIN, or NetWare Administrator utilities.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN," "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator," and "BOOK="utlrfenu" COLLECTION="nw41"RIGHTS" in Utilities Reference.See also IDREF="FM53605""Access Control List"; IDREF="FM52521""Security."RENDERAS="SECT1"ID="FM93357"RIP
 (IPX)(Router Information Protocol) A protocol that provides a way for routers to exchange routing information on a NetWare internetwork.See IDREF="FM72567""Router Information Protocol."RENDERAS="SECT1"RIP (TCP/IP)IDXID="w2333"BOOK="_idx" COLLECTION="nw41" TIDREF="i3890"A distance vector internal gateway protocol for TCP/IP networks.PAGENUM=296 ID="BP297"A TCP/IP Routing Information Protocol (RIP) router periodically broadcasts a routing update message that contains an entry for each network it can reach and the cost (distance) to that network. TCP/IP RIP routers listen to all TCP/IP RIP broadcast messages.Each entry in a received routing update message is added to the routing table. The router that sent the routing update message is remembered as the next router (hop) on the route to the network in the entry. If a router learns about two routes to a network, it keeps the one with the lower cost. Cost is defined in RIP in terms of hop count, or the number of routers along the path to the destination. TCP/IP RIP allows a maximum cost (hop count) of 15.Once a route is learned, it must be refreshed at certain intervals. This is done to ensure that the route is still valid. TCP/IP RIP routers normally broadcast a routing update message containing known routes once every 30 seconds. A timer is started when a route is learned from a routing update message. If a subsequent routing update message does not refresh the route within 180 seconds, the route is assumed to be unusable because of a network or node failure. The route is removed from the routing table.See also IDREF="FM72567""Router Information Protocol."RENDERAS="SECT1"IDXID="w2334"BOOK="_idx" COLLECTION="nw41" TIDREF="i3890"
RIP II (TCP/IP)An enhancement to RIP that includes the subnetwork mask in its routes. The lack of subnet mask information limits RIP to advertising only network routes, or requires RIP routers to make assumptions about the subnetwork mask. When RIP is used in a subnetted network, all subnets are usually required to use the same subnetwork mask.RIP II can be used in network topologies requiring variable length subnet masks, and it is able to support subnet 0. RIP II can also authenticate routing message exchanges.Not all RIP routers support RIP II.PAGENUM=297 ID="BP298"RENDERAS="SECT1"Root directoryIDXID="w2335"BOOK="_idx" COLLECTION="nw41" TIDREF="i3875"IDXID="w2336"BOOK="_idx" COLLECTION="nw41" TIDREF="i1096"The highest directory level in a hierarchical directory structure. With NetWare, the root directory is the volume; all other directories are subdirectories of the volume.See also IDREF="FM77617""Failure handling"; IDREF="FM22177""File system."RENDERAS="SECT1"Root objectIDXID="w2337"BOOK="_idx" COLLECTION="nw41" TIDREF="i3875"An object in the Directory tree whose purpose is to provide a highest point to access different Country and Organization objects, and to allow trustee assignments granting rights to the entire Directory tree.Country, Organization, and Alias objects can be created at the Root object.The Root object is a place holder; it contains no information.See also IDREF="FM69136""Directory tree"; IDREF="FM13600""Object."RENDERAS="SECT1"ID="FM86375"RouterIDXID="w2338"BOOK="_idx" COLLECTION="nw41" TIDREF="i3885"A workstation or NetWare server running software that manages the exchange of information (in the form of data packets) between network cabling systems.A NetWare router runs as part of a NetWare server. It connects separate network cabling topologies or separate networks by way of the server's NetWare operating system.NetWare automatically routes IPX/SPX packets. However, NetWare is enabled for non-routing TCP/IP and AppleTalk protocols. To set your server to route TCP/IP and AppleTalk packets, use the INETCFG utility.PAGENUM=298 ID="BP299"LABEL="66" FLOAT="0"RouterFILEREF="n40co89a.tif"RENDERAS="SECT2"NetWare Router versus Traditional BridgeA NetWare router, unlike a traditional bridge, does more than just transfer data packets between networks that use the same communications protocol.A NetWare router is intelligent. It not only passes packets of data between different cabling systems, but also routes the packets through the most efficient path.A NetWare router can also connect cabling systems that use different kinds of transmission media and different addressing systems.For example, a NetWare router can connect a network using the Ethernet addressing structure and RG/58 coaxial cable to another network using the ARCnet addressing structure and RG/62 coaxial cable.RENDERAS="SECT2"Local versus RemoteWhen a router is used within the cable length limitations for its LAN drivers, it is a local router. If the router is connected beyond its driver limitations or through a modem, it is a remote router.RENDERAS="SECT1"ID="FM72567"Router Information ProtocolIDXID="w2339"BOOK="_idx" COLLECTION="nw41" TIDREF="i3890"IDXID="w2340"BOOK="_idx" COLLECTION="nw41" TIDREF="i3890"(RIP) A protocol that provides a way for routers to exchange routing information on a NetWare internetwork.PAGENUM=299 ID="BP300"RIP allows NetWare routers to create and maintain a database (or router table) of current internetwork routing information.Workstations can query the nearest router to find the fastest route to a distant network by broadcasting a RIP request packet.Routers send periodic RIP broadcast packets containing current routing information to keep all routers on the internetwork synchronized. Routers also send RIP update broadcasts whenever they detect a change in the internetwork configuration.By default, a NetWare router sends RIP packets to each of its connected network segments every 60 seconds.Routes that don't appear in these periodic broadcasts (because a router has failed) are aged. After a certain period of time (default: 3 minutes), routers delete the aged routes from their router tables.To reduce traffic on lower bandwidth (X.25 and asynchronous) segments, network supervisors can configure routers to send only RIP updates rather than periodic RIP broadcasts over those segments.However, turning off the periodic RIP broadcasts can cause inconsistencies on the internetwork. For example, if an unreliable segment loses a RIP update packet, routers on that segment broadcast old information.INETCFG and FILTCFG allow network supervisors to configure RIP broadcasts for each network segment. To avoid inconsistencies in broadcast and aging intervals, all routers on the same network segment must have the same RIP configuration.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" and "BOOK="utlrfenu" COLLECTION="nw41"FILTCFG" in Utilities Reference. See also IDREF="FM86375""Router"; IDREF="FM51570""Service Advertising Protocol."RENDERAS="SECT1"RPL(Remote Program Load) Technology based on the concept of storing an image of a bootable floppy disk on a NetWare volume.See IDREF="FM88537""Remote Program Load."PAGENUM=300 ID="BP301"SRENDERAS="SECT1"Salvageable filesIDXID="w2341"BOOK="_idx" COLLECTION="nw41" TIDREF="i3937"IDXID="w2342"BOOK="_idx" COLLECTION="nw41" TIDREF="i1447"IDXID="w2343"BOOK="_idx" COLLECTION="nw41" TIDREF="i3711"Files saved by NetWare, after being deleted by users, that can be salvaged (recovered).Salvageable files are usually stored in the directory from which they were deleted. If the user deletes that directory, the file is saved in a DELETED.SAV directory located in the volume's root directory.The user can view a list of deleted files in a directory and recover files by using the FILER utility. Recovered files contain information about who deleted the files and when they were deleted.Deleted files are saved until the user deliberately purges them or until the NetWare server runs out of disk allocation blocks on the volume.When the NetWare server runs out of blocks, it purges deleted files beginning with the files that were the first deleted.Files and directories can also be purged as they are deleted. You can do this one of two ways:MARK=BULLETUse the SET command at the NetWare server to disable the salvageable file feature. This increases performance, but at the cost of losing the salvageable file feature.Set the Purge file system attribute. When a file is flagged with the Purge attribute, the file is purged when it is deleted. When a directory is flagged with the Purge attribute, any file in that directory is purged when the directory is deleted. Such files and directories can't be recovered with the FILER utility.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities Reference.PAGENUM=301 ID="BP302"RENDERAS="SECT1"SAP(Service Advertising Protocol) A protocol that provides a way for servers to advertise their services on a NetWare internetwork.See IDREF="FM51570""Service Advertising Protocol."RENDERAS="SECT1"IDXID="w2344"BOOK="_idx" COLLECTION="nw41" TIDREF="i3953"SBACKUPA backup engine that provides backup and restore capabilities.See IDREF="FM66936""Storage Management Services."RENDERAS="SECT1"ID="FM75975"SCSIIDXID="w2345"BOOK="_idx" COLLECTION="nw41" TIDREF="i3969"(Small Computer Systems Interface, commonly pronounced scuzzy) An industry standard that sets guidelines for connecting peripheral devices (such as hard drives and tape backup systems) and their controllers to a microprocessor.The SCSI interface defines both hardware and software standards for communication between a host computer and a peripheral device.Computers and peripheral devices designed to meet SCSI specifications have a large degree of compatibility.RENDERAS="SECT1"ID="FM83109"SCSI busIDXID="w2346"BOOK="_idx" COLLECTION="nw41" TIDREF="i3969"An interface that connects additional HBAs to controllers and hard disks. When using a SCSI bus, make sure connected peripherals are properly terminated and addressed.You can identify a SCSI bus by its 50-pin connector. (As opposed to an IDE bus, which has a 40-pin connector.) See also IDREF="FM19745""Hard disk"; IDREF="FM27496""Termination."RENDERAS="SECT1"SCSI disconnectIDXID="w2347"BOOK="_idx" COLLECTION="nw41" TIDREF="i3969"IDXID="w2348"BOOK="_idx" COLLECTION="nw41" TIDREF="i1108"A feature of the NetWare SCSI driver that signals a disk that it should prepare for I/O.PAGENUM=302 ID="BP303"Formerly, a SCSI driver made a connection with a hard disk over the computer's bus; asked the hard disk to prepare for I/O; waited for the hard disk to prepare for I/O; performed I/O to the disk; and then disconnected.This disk I/O method was inefficient because the SCSI driver was idle during the time that the disk was preparing for I/O.Currently, the SCSI driver no longer waits idly while hard disks prepare for I/O as it did in the past.While the disk is preparing for I/O, the SCSI driver can send messages to other hard disks or perform I/O to other hard disks.When the disk is ready to receive or send data, the disk sends a message back to the SCSI driver, signaling the driver that the disk is ready for I/O. The SCSI driver then performs the I/O.SCSI disconnect occurs automatically if the board supports it. For example, the IBM SCSI board supports SCSI disconnect.RENDERAS="SECT1"Search algorithmIDXID="w2349"BOOK="_idx" COLLECTION="nw41" TIDREF="i3973"IDXID="w2350"BOOK="_idx" COLLECTION="nw41" TIDREF="i151"The search sequence that NetWare workstation utilities use to find and then load message and Unicode files in DOS and OS/2 environments.RENDERAS="SECT2"Finding Text FilesNetWare workstation utilities search for message files---.MSG, .HLP, .IDX, and .XLT files---in the following places, in this order:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The current working directoryThe NWLANGUAGE environment variable directoryIf the NWLANGUAGE variable is set, it should contain a directory name or names that specifies a languages. For example,TYPE="VERT"MOREINFO="NONE"NWLANGUAGE=EnglishTYPE="VERT"MOREINFO="NONE"NWLANGUAGE=French,EnglishPAGENUM=303 ID="BP304"The NetWare workstation utilities search the child directory of the NLS directory as specified by the NWLANGUAGE variable. The NLS directory in this case is itself a child directory of the executable file's load directory.If the file is not found in the child directory of the NLS directory, NetWare utilities search for in the NWLANGUAGE subdirectory of the NLS directory, which is a sibling of the executable's load directory.For example, if the executable file's load directory is SERVER\SYS:PUBLIC\OS2 and the NWLANGUAGE variable is set to English, the following directory is searched:TYPE="VERT"MOREINFO="NONE"SERVER\SYS:PUBLIC\OS2\NLS\ENGLISHThen, if the file has not been found, NetWare utilities searchTYPE="VERT"MOREINFO="NONE"SERVER\SYS:PUBLIC\NLS\ENGLISHThe load directory (the directory containing the current utility's .EXE file). This is normally your PUBLIC directory.The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found either in the user's login script or in the AUTOEXEC.BAT file.All of the directories found under the child NLS subdirectory of the load directory.All of the directories found under the sibling NLS subdirectory of the load directory.RENDERAS="SECT2"Finding Unicode FilesNetWare workstation utilities search for Unicode files in the following places, in this order:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The current working directory.The load directory (the directory containing the current utility's .EXE file). This is normally your PUBLIC directory.The NLS directory that is located within the load directory (the directory containing the current utility's .EXE file). PAGENUM=304 ID="BP305"If the Unicode files are not found in the NLS directory within the load directory, the utility searches the NLS directory that is a sibling of the load directory (that is, at the same level as the load directory).The NWLanguage environment variable does not apply here.The PATH and DPATH (for OS/2 only) environment variables.These environment variables can be found either in the user's login script or in the AUTOEXEC.BAT file.See also IDREF="FM17174""Unicode."RENDERAS="SECT1"Search driveIDXID="w2351"BOOK="_idx" COLLECTION="nw41" TIDREF="i3974"A drive that the operating system searches when a requested file isn't found in the current directory.Search drives are supported only from DOS workstations.A search drive allows a user working in one directory to access an application or data file located in another directory.See also IDREF="FM39775""Drive mapping."RENDERAS="SECT1"Search modesIDXID="w2352"BOOK="_idx" COLLECTION="nw41" TIDREF="i3980"Methods of operation that specify how a program uses search drives when looking for a data file.When an .EXE or .COM file requires an auxiliary file, it makes an open request through the operating system. The request might or might not specify the path to that file.If a path is specified, the operating system searches that path. Otherwise, it only searches the default directory.If the file isn't found, the NetWare shell uses the search mode of the executable file to determine if it should continue looking for the file in the search drives.PAGENUM=305 ID="BP306"FLAG allows you to set the search mode for executable files individually, or you can set the shell's search mode in the NET.CFG file for the majority of your files.The following table describes the types of search modes.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="3*"COLNAME=2 COLWIDTH="22*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ModeCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0COLNAME=2 ROTATE="0" MOREROWS="0"The default setting for all executable files. The executable file looks for instructions in the NET.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"1 COLNAME=2 ROTATE="0" MOREROWS="0"The executable file searches the path specified in the file itself. If there is no path, the file searches the default directory and then all search drives.COLNAME=1 ROTATE="0" MOREROWS="0"2 COLNAME=2 ROTATE="0" MOREROWS="0"The executable file searches the path specified in the file itself. If there is no path, the file searches only the default directory.COLNAME=1 ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"The executable file searches the path specified in the file itself. If there is no path, the file searches the default directory; then if the open request is read-only, the file searches the search drives.COLNAME=1 ROTATE="0" MOREROWS="0"4COLNAME=2 ROTATE="0" MOREROWS="0"Reserved.COLNAME=1 ROTATE="0" MOREROWS="0"5COLNAME=2 ROTATE="0" MOREROWS="0"The executable file searches the path specified first and then all search drives. If there is no path, the file searches the default directory and then all search drives.COLNAME=1 ROTATE="0" MOREROWS="0"6COLNAME=2 ROTATE="0" MOREROWS="0"Reserved.COLNAME=1 ROTATE="0" MOREROWS="0"7 COLNAME=2 ROTATE="0" MOREROWS="0"The executable file searches the path specified first. If the open request is read only, the file searches the search drives. If there is no path, the file searches the default directory and then all search drives.For example, if you assign an executable file mode 2, it won't use search drives.If you assign mode 5, the executable file can use search drives to find a data file if the file isn't found in the first directory the executable file looks in.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.PAGENUM=306 ID="BP307"RENDERAS="SECT1"IDXID="w2353"BOOK="_idx" COLLECTION="nw41" TIDREF="i3987"IDXID="w2354"BOOK="_idx" COLLECTION="nw41" TIDREF="i4125"
Secondary serverThe SFT III server that is activated after the primary server.The secondary server receives a mirrored copy of the memory and disk from the primary server (the first server activated). In addition to mirroring the primary server, the secondary server provides split seeks. SFT III splits multiple read requests between the two servers' disks for faster disk reads.Though it cannot be used to do additional work (because it uses all of its CPU cycles keeping up with the primary server), the secondary server acts as a router for the local network segments to which it is directly attached. If both SFT III servers are on the same network segment, the secondary server doesn't do any routing.If a secondary server acting as a router goes down, so does the routing. The primary server doesn't take over the routing that the secondary server provided.Either SFT III server may function as primary or secondary, depending on the state of the system. You cannot permanently designate which server is primary or secondary; system failure determines each server's role. When the primary server fails, the secondary server becomes the new primary server. When the failed server is restored, it becomes the new secondary server.RENDERAS="SECT1"Secondary time serverA server that obtains the time from a Single Reference, Primary, or Reference time server and provides the time to workstations.See IDREF="FM65772""Time synchronization."RENDERAS="SECT1"ID="FM52521"SecurityIDXID="w2355"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"Elements that control access to the network or to specific information on the network. Six categories of security features areMARK=BULLETLogin security. Controls which users can access the network.Trustees. Designate which users can access directories, files, or objects.Rights. Determine the level of access for each trustee.PAGENUM=307 ID="BP308"Inheritance. Passes rights from higher to lower levels.Attributes. Describe characteristics of directories and files.Effective rights. List a user's actual rights to a directory, file, or object (including explicitly granted rights and inherited rights).RENDERAS="SECT2"IDXID="w2356"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
Login SecurityThe LOGIN command controls who can access the network by determining if a valid user is attempting to log in.A person must know the User object's name and the correct password (if required) to log in.The network supervisor establishes this login security by creating a User object in NDS and by then assigning values to the properties of that user. Those values determine how the user can access the network.A User object's properties affect when a user can log in, which workstations a user can log in to, when the user's account is disabled, etc.Passwords aren't required, but they should be used. Without one, an intruder can access the network with only a user's name. Don't use family or pet names as passwords; they are easily guessed by an intruder.Passwords are encrypted and are never displayed on the monitor or transmitted across the network. The password authenticates every action of a user.You can assign and change passwords, or you can assign initial passwords and allow users to change them. To increase login security, consider requiring these password options:MARK=BULLETMinimum password length. Prevents the use of passwords that might be easily guessed. (Default: 5 characters.)Periodic password change. Prevents the user from keeping a password indefinitely. (Default: every 40 days.)PAGENUM=308 ID="BP309"Unique password. Prevents alternating between a few favorite passwords. The server remembers and rejects the use of the eight passwords most recently used for one day or longer.RENDERAS="SECT2"IDXID="w2357"BOOK="_idx" COLLECTION="nw41" TIDREF="i4591"
TrusteesA trustee is a User or Group object that has been granted access to a directory, file, or object. Access is granted through a trustee assignment.Any object with sufficient rights can make trustee assignments with the RIGHTS, NETADMIN, or NetWare Administrator utilities.MARK=BULLETTrustee list. Each directory, file, and object has a list of trustee assignments, called a trustee list, that specifies who can access that directory, file, or object. An object's trustee list is stored in the object's ACL property.Trustees of groups. For several users to access a directory, file, or object, a trustee assignment is required for each user. Rather than make trustee assignments for each user individually, create a Group object, include the users in the group, and then grant access for the group with one trustee assignment.[Public] trustee. [Public] is a special trustee that can be added to an object, directory or file. The rights assigned to [Public] are effective for anyone who has no rights to the file, directory, or object.RENDERAS="SECT2"IDXID="w2358"BOOK="_idx" COLLECTION="nw41" TIDREF="i3851"
RightsRights determine the type of access a trustee has to a directory, file, or object. For example, if a trustee assignment grants the Create right to a directory, a trustee can create files in the directory.A trustee assignment grants one object rights to another object. By default, every trustee assignment includes the Browse object right and the Read right for all properties.PAGENUM=309 ID="BP310"Rights are granted within the object a trustee has rights to, not within the trustee object. For example, to grant JILL the right to delete a Printer object, make JILL a trustee of the Printer object and include the delete right in her assignment---don't make the Printer object a trustee of JILL.Because directories, files, and objects contain such different information, the rights that control access to each are different. Rights to directories and files and to other objects are controlled in different sections of the utilities.There are four kinds of rights in NetWare 4:MARK=BULLETIDXID="w2359"BOOK="_idx" COLLECTION="nw41" TIDREF="i1072"Directory rights. Control what a trustee can do with a directory. Directory rights also apply to files in the directory if file rights aren't granted and if the file's Inherited Rights Filter doesn't block the directory rights.File rights. Control what a trustee can do with a file.IDXID="w2360"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"Object rights. Control what a trustee can do with an object. These rights control the object as a single piece in the directory tree, but don't allow access to information stored within that object (except the Supervisor object right, which also allows access to an object's properties).IDXID="w2361"BOOK="_idx" COLLECTION="nw41" TIDREF="i3580"Property rights. Control a trustee's access to information stored within the object---that is, the information stored in the object's properties. Each object type has a different set of properties.Property rights can be managed in NETADMIN or NetWare Administrator using the "All Properties" or the "Selected Properties" option.Rights assigned using "All Properties" affect every property equally. Rights assigned using "Selected Properties" affect individual properties only.PAGENUM=310 ID="BP311"To grant directory or file rights to other objects, an object must have the Access Control right to that directory or file. To grant object or property rights, a user must have the Write right to the object's ACL property.For a list and description of all rights, see IDREF="FM74455""Rights."Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"RIGHTS," "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN," and ""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.RENDERAS="SECT2"IDXID="w2362"BOOK="_idx" COLLECTION="nw41" TIDREF="i1802"
InheritanceIDXID="w2363"BOOK="_idx" COLLECTION="nw41" TIDREF="i3851"Creating a trustee assignment for every user and for every directory, file, and object would be a huge job. Inheritance simplifies the task.Through inheritance, rights granted in a trustee assignment apply to objects, directories, and files below the assignment. Rights change if another trustee assignment is made or if the rights are blocked by an IRF.Inheritance applies both to directories and files on a volume and to objects in the Directory tree.For directories and files, all access rights are inherited. For objects, only object rights and rights assigned with "All Properties" are inherited. Rights to specific properties of an object can't be inherited.Rights assigned to NDS objects do not affect file system rights. For example, object rights assigned to a Volume object do no affect the directory and file system rights in the physical volume represented by that Volume object.However, one exception exists: Any trustee with the Supervisor right to a NetWare Server object or to that object's ACL property is granted the Supervisor right to any physical volume attached to that server.IDXID="w2364"BOOK="_idx" COLLECTION="nw41" TIDREF="i1804"IDXID="w2365"BOOK="_idx" COLLECTION="nw41" TIDREF="i3851"An IRF stops rights from being inherited. An IRF has the same set of possible rights as a trustee assignment, but instead of granting rights, it revokes rights.Every directory, file, and object has an IRF. With this filter, you can grant access more freely at the top of the object tree or volume, then filter out rights in sensitive areas.PAGENUM=311 ID="BP312"With all rights in sensitive areas blocked by an IRF, only users with a trustee assignment in those areas have access. No one can inherit rights blocked by an IRF. (See IDREF="FM13738""Inherited Rights Filter.")Be careful not to block everyone's rights to an object with an Inherited Rights Filter, leaving no one with access to part of the Directory tree.The utilities don't allow you to block the Supervisor object right unless a trustee already has the Supervisor object right at that point. But you could still delete the trustee object, making the trustee assignment invalid and cutting off access to that part of the Directory tree.RENDERAS="SECT2"IDXID="w2366"BOOK="_idx" COLLECTION="nw41" TIDREF="i336"
AttributesAttributes (also called flags) describe the characteristics of a directory or file and tell NetWare what actions are allowed, and in a few cases, what actions have been performed. They aren't used for objects.NetWare reads the attributes you set (for example, to compress, back up, or not allow deletion of a file) and sets other attributes to tell you what has been done (for example, that a file has been compressed, migrated, or indexed).Attributes are separate from rights. Attributes aren't inherited, and if an attribute indicates that a file can't be deleted, not even a supervisor can delete it without first changing the attribute.To change the attributes of a directory or file, an object must be granted the Modify right in a trustee assignment for the directory or file. (See IDREF="FM85330""Attributes.")Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"FLAG," "BOOK="utlrfenu" COLLECTION="nw41"FILER," "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN," and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.RENDERAS="SECT2"IDXID="w2367"BOOK="_idx" COLLECTION="nw41" TIDREF="i1294"
Effective RightsEffective rights are the rights that a user actually has to a directory, file, or object. NetWare calculates your effective rights to a directory, file, or object whenever you take an action.PAGENUM=312 ID="BP313"Effective rights to a file or directory are determined byMARK=BULLETAn object's trustee assignments to the directory or fileInherited rights from an object's trustee assignments to parent directoriesTrustee assignments of Group objects that a User object belongs toTrustee assignments of objects listed in a User object's "Security Equal To" listIf a user has a trustee assignment to a directory on a given level in the file system, and also one on a higher level, the current trustee assignment overrides the higher one.However, trustee assignments to a group are added to individual user trustee assignments.Effective rights to an object are shown in the following figure.LABEL="67" FLOAT="0"Effective RightsFILEREF="n41co57a.tif"PAGENUM=313 ID="BP314"In the previous figure, MWILKENS' effective rights to access the MANAGERS profile can come fromMARK=BULLETTrustee assignments on MANAGERS that list MWILKENS (explicit rights are granted)Trustee assignments on MANAGERS that list SALES PV (inherited from the trustee's container)Trustee assignments on SALES LA that list MWILKENS (inherited from the object's container)Rights must pass through MANAGERS' IRF before becoming effective.Trustee assignments on SALES LA that list SALES PV (inherited from object's container and trustee's container)Rights must pass through MANAGERS' IRF before becoming effective.Trustee assignments to any Group object that MWILKENS is a member of (only valid when the object requesting rights is a User object)Trustee assignments to any object listed in MWILKENS' "Security Equal To" list (only valid when the object requesting rights is a User object)If MWILKENS has a trustee assignment to SALES LA and to MANAGERS, the Trustee assignment on MANAGERS overrides the trustee assignment on SALES LA.Trustee assignments to groups, however, are added to previous trustee assignments for User objects.No rights are granted by default. They must be granted by a trustee assignment at some point.The Supervisor right can be filtered for object and property rights, but can't be filtered for file system rights.See also IDREF="FM85330""Attributes"; IDREF="FM57690""Effective rights"; IDREF="FM13738""Inherited Rights Filter"; IDREF="FM74455""Rights"; IDREF="FM87658""Security Equal To"; IDREF="FM26134""Trustee."PAGENUM=314 ID="BP315"RENDERAS="SECT1"ID="FM87658"Security Equal ToIDXID="w2368"BOOK="_idx" COLLECTION="nw41" TIDREF="i3575"IDXID="w2369"BOOK="_idx" COLLECTION="nw41" TIDREF="i3997"A property of every User object that lists other objects. The user is granted all rights that any object (such as User, Group, or Printer objects) in that list is granted, both to objects and to files and directories.Use the Security Equal To property to give a user temporary access to the same information or rights another user has access to. When a user is added to the membership list of a Group object or the occupant list of an Organizational Role object, the Group or Organizational Role is listed in that user's "Security Equal To" list. By using a security equal, you avoid having to review the whole directory structure and determine which rights need to be assigned to which directories, files, and objects.However, if an object in a user's "Security Equal To" list is deleted from NDS, the user no longer has the rights granted through that object.Use the Security Equal To property with caution. If users have rights to add to their own "Security Equal To" list, they could add the name of a network supervisor and change anything on the network. Be careful when granting the Write or Supervisor property right to this property and consider blocking it in the Inherited Rights Filter of each User object. This way, only network supervisors and those granted specific rights to this property can add to the list.Users who manage other users should be granted the Write right to this property. This allows user account managers to make users security equal to other users that they manage.Every object is security equal to all container objects that are part of its complete name. Because of this, you can make a container a trustee.Every object in that container has the rights that are granted to the container, through the Security Equal To property. However, none of these containers are listed in a users "Security Equal To" list.The Security Equal To property is not transitive; tPAGENUM=315 ID="BP316"hat is, if TOM is security equal to JILL, and JILL is security equal to BOB, TOM is not security equal to BOB through JILL. The Security Equal To property only grants TOM those rights that JILL is explicitly granted.To add an object to a user's "Security Equal To" list, you must have at least the Write property right to the ACL property of the object you want to add to the list. You don't need rights to the Security Equal property of the user; only the Browse object right.In networks containing confidential data that only selected users have access to, take care that you don't inadvertently give a user access to restricted information.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN " in Utilities Reference and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.See also IDREF="FM20517""User object."RENDERAS="SECT1"Seed routerIDXID="w2370"BOOK="_idx" COLLECTION="nw41" TIDREF="i3885"IDXID="w2371"BOOK="_idx" COLLECTION="nw41" TIDREF="i4006"A router that defines the range of network numbers for all routers in an AppleTalk network segment.Each AppleTalk network segment must have at least one seed router.RENDERAS="SECT1"ID="FM30179"SemaphoreIDXID="w2372"BOOK="_idx" COLLECTION="nw41" TIDREF="i4018"An integer value used to coordinate activities of both programs and processes to prevent data corruption in multiprocessor environments.Semaphores are used to synchronize interprocess communication by ensuring that certain event sequences do or do not occur.Another use of semaphores is a binary semaphore, which controls the use of shared resources by enforcing mutually exclusive access to those resources. For example, access to a shared file could be controlled by using a binary semaphore. If the file is not in use, the semaphore value is 1 and the file is available. If the file is in use, the semaphore value is 0. While the semaphore value is 0, no other process can access the file. PAGENUM=316 ID="BP317"Semaphores can also allow a limited number of users access to a resource, such as to network applications with limited-user licenses. When the specified number is reached, the semaphore denies access to additional users.NetWare supervisors never see or change a semaphore's value in NetWare. NLM developers use semaphores extensively.If you receive system messages that refer to semaphores, it is likely that the message is referring to shared resource management issues.See also IDREF="FM51849""File locking."RENDERAS="SECT1"ID="FM44412"Serial communicationIDXID="w2373"BOOK="_idx" COLLECTION="nw41" TIDREF="i4033"IDXID="w2374"BOOK="_idx" COLLECTION="nw41" TIDREF="i697"The transmission of data between devices over a single line, one bit at a time.NetWare uses the RS-232 serial communication standard to send information to serial printers, remote workstations, remote routers, and asynchronous communication servers.The RS-232 standard, developed by the Electronic Industries Association (EIA), enhances the delivery of information from one system to another.A system can be any device or group of devices that can handle and process the data received.For example, a printer can be thought of as a system that transforms the binary data it receives from the computer into printed text.The RS-232 standard uses several parameters that must match on both systems for valid information to be transferred. These parameters include baud rate, character length, parity, stop bit, and XON/XOFF:MARK=BULLETIDXID="w2375"BOOK="_idx" COLLECTION="nw41" TIDREF="i424"Baud rate. The signal modulation rate, or the speed at which a signal changes.Since most modems or serial printers attached to personal computers send only one bit per signaling event, baud can be thought of as bits per second; however, higher-speed modems may transfer several bits per signal change.PAGENUM=317 ID="BP318"Typical baud rates are 1200, 2400, 4800, and 9600. The higher the number, the greater the number of signal changes and, therefore, the faster the transmission.IDXID="w2376"BOOK="_idx" COLLECTION="nw41" TIDREF="i615"Character length. The number of data bits used to form a character.The standard ASCII character set (including letters, numbers, and punctuation) consists of 128 characters and requires a character length of 7 bits for transmissions.Extended character sets (containing line drawings or the foreign characters used in IBM's extended character set) contain an additional 128 characters and require a character length of 8 bits.IDXID="w2377"BOOK="_idx" COLLECTION="nw41" TIDREF="i3221"Parity. A method of checking for errors in transmitted data. You can set parity to even or odd, or not use parity at all.Serial communication sends information in a stream of bits called a frame. Each frame consists of start bits, data bits, an optional parity bit, and stop bits.The parity bit is set to 0 or 1 so that the sum of the data bits is even or odd. Upon reception, each transmitted frame is checked to ensure that the parity is still even or odd.If it is incorrect (because a bit was changed during transmission), the communications software determines that a transmission error has occurred and can request that the data be retransmitted.The following table shows examples of parity checking:COLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="5*"COLNAME=3 COLWIDTH="6*"COLNAME=4 COLWIDTH="5*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Character lengthCOLNAME=2 ROTATE="0" MOREROWS="0"Sample bitsCOLNAME=3 ROTATE="0" MOREROWS="0"Even parityCOLNAME=4 ROTATE="0" MOREROWS="0"Odd parityVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"7 data bitsCOLNAME=2 ROTATE="0" MOREROWS="0"0010110COLNAME=3 ROTATE="0" MOREROWS="0"00101101COLNAME=4 ROTATE="0" MOREROWS="0"00101100COLNAME=1 ROTATE="0" MOREROWS="0"7 data bitsCOLNAME=2 ROTATE="0" MOREROWS="0"1110111COLNAME=3 ROTATE="0" MOREROWS="0"11101110COLNAME=4 ROTATE="0" MOREROWS="0"11101111COLNAME=1 ROTATE="0" MOREROWS="0"8 data bitsCOLNAME=2 ROTATE="0" MOREROWS="0"10001000COLNAME=3 ROTATE="0" MOREROWS="0"100010000COLNAME=4 ROTATE="0" MOREROWS="0"100010001COLNAME=1 ROTATE="0" MOREROWS="0"8 data bitsCOLNAME=2 ROTATE="0" MOREROWS="0"11011111COLNAME=3 ROTATE="0" MOREROWS="0"110111111COLNAME=4 ROTATE="0" MOREROWS="0"110111110PAGENUM=318 ID="BP319"Stop bit. A special signal that indicates the end of that character. Today's modems are fast enough that the stop bit is always set to 1. Slower modems require two stop bits.XON/XOFF. One of many methods that prevents the sending system from transmitting data faster than the receiving system can accept it.RENDERAS="SECT1"ID="FM18990"Serial portIDXID="w2378"BOOK="_idx" COLLECTION="nw41" TIDREF="i4033"IDXID="w2379"BOOK="_idx" COLLECTION="nw41" TIDREF="i3337"A port that allows data to be transmitted asynchronously, one bit at a time. Typically, serial ports are used for modems or serial printers.On IBM PC-compatible computers, COM1 and COM2 are asynchronous serial ports.RENDERAS="SECT1"SerializationIDXID="w2380"BOOK="_idx" COLLECTION="nw41" TIDREF="i4041"The process of serializing software to prevent unlawful software duplication.Each NetWare operating system has a unique serial number.If two NetWare operating systems with the same serial number exist on the same internetwork, each NetWare server displays a copyright violation warning at the server console and at each logged-in workstation.If you suspect you have received the copyright violation warning in error, contact your Novell reseller. Or contact Novell directly:MARK=BULLETIn the USA or Canada, call 1-800-NETWARE (1-800-638-9273). In all other locations, call 1-801-429-7000. You may be charged for the technical support to correct the errors.If you suspect criminal copyright violation, please contact Novell at the following numbers: MARK=BULLETIn the USA and Canada, call 1-800-PIRATES (747-2837).In all other locations, call 1-801-429-3607.PAGENUM=319 ID="BP320"RENDERAS="SECT1"ServerA computer in a network shared by multiple users. NetWare server. A computer running the NetWare operating system software. (See IDREF="FM34874""NetWare server.")Print server. A computer that takes print jobs out of a print queue and sends them to a network printer. (See IDREF="FM15181""Print server.")RENDERAS="SECT1"ID="FM65589"Server consoleIDXID="w2381"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"IDXID="w2382"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"The monitor and keyboard where you view and control NetWare server activity. You canMARK=BULLETView network trafficSend messagesSet configuration parametersShut down the serverLoad and unload NLM programsMany server console tasks are done in MONITOR and PSERVER.MONITOR allows you to view server and memory use, connections, and many disk and network statistics. PSERVER allows you to control active printers on the network.RCONSOLE.EXE allows a workstation to function as a server console. Be aware of the following console security issues:MARK=BULLETUnauthorized access of the server console. Control keyboard access by requiring the use of a password. (See "BOOK="superenu" COLLECTION="nw41"Securing the Server Console" in Chapter 7 of Supervising the Network.)Use the SECURE CONSOLE command to secure your console against breaches of security. (See "BOOK="utlrfenu" COLLECTION="nw41"SECURE CONSOLE" in Utilities Reference.)PAGENUM=320 ID="BP321"Software tampering. An expert could use the built-in debugger to disable or bypass the security system. To prevent this, use SECURE CONSOLE.Hardware tampering. Keep your server in a secure location. An intruder could disable the power-on password or remove hard disks to access data.RENDERAS="SECT1"ID="FM84857"IDXID="w2383"BOOK="_idx" COLLECTION="nw41" TIDREF="i4054"IDXID="w2384"BOOK="_idx" COLLECTION="nw41" TIDREF="i2476"IDXID="w2385"BOOK="_idx" COLLECTION="nw41" TIDREF="i4125"
Server mirroringAn SFT III configuration that provides a secondary, identical server to immediately take over network operations when the primary server fails.Server mirroring requires two similarly configured network servers. They should be evenly matched in terms of CPU speed, memory, and storage capacity.The servers are not required to be identical in terms of microprocessor type (386/486), microprocessor revision level, or clock speed. However, identical servers are recommended for better performance. If the two servers are unequal, then SFT III performs at the speed of the slower server.The servers must be directly connected by a mirrored server link. SFT III servers can reside on different network segments, as long as they share a dedicated mirrored server link and each can reach the other server on the internetwork.RENDERAS="SECT1"Server protocolProcedures that a NetWare server follows to accept and respond to workstation requests.See IDREF="FM62017""NetWare Core Protocol."RENDERAS="SECT1"ID="FM51570"Service Advertising ProtocolIDXID="w2386"BOOK="_idx" COLLECTION="nw41" TIDREF="i4073"(SAP) A protocol that provides a way for servers to advertise their services on a NetWare internetwork.Servers advertise their services with SAP, allowing routers to create and maintain a database of current internetwork server information.PAGENUM=321 ID="BP322"Routers send periodic SAP broadcasts to keep all routers on the internetwork synchronized. Routers also send SAP update broadcasts whenever they detect a change in the internetwork configuration.Workstations can query the network to find a server by broadcasting SAP request packets. When a workstation logs in to a network, it broadcasts a "Get Nearest Server" SAP request and attaches to the first server that replies.To keep workstations from attaching to a server, network supervisors can turn off the "Get Nearest Server" SAP option.By default, a NetWare router sends SAP packets to each of its connected network segments every 60 seconds.With time synchronization, Single reference and Primary time servers advertise their services using SAP. Secondary time servers don't advertise their services.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"MONITOR," "BOOK="utlrfenu" COLLECTION="nw41"INETCFG," and "BOOK="utlrfenu" COLLECTION="nw41"TIMESYNC" in Utilities Reference.See also IDREF="FM86375""Router"; IDREF="FM72567""Router Information Protocol."RENDERAS="SECT1"ID="FM66501"SFT(System Fault Tolerance) A means of protecting data by providing procedures that allow you to recover from hardware failures.There are three levels of SFT: Hot Fix; Disk mirroring or duplexing; Server mirroring.See IDREF="FM93344""System Fault Tolerance."RENDERAS="SECT1"Shareable (Sh) attributeIDXID="w2387"BOOK="_idx" COLLECTION="nw41" TIDREF="i4131"A file system attribute that allows a file to be accessed by more than one user at a time.See also IDREF="FM85330""Attributes."PAGENUM=322 ID="BP323"RENDERAS="SECT1"ID="FM97289"Short machine typeIDXID="w2388"BOOK="_idx" COLLECTION="nw41" TIDREF="i4140"IDXID="w2389"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"A four-letter (or less) name representing a brand of DOS workstations. The short machine type is similar to the long machine type, except the short machine type is used specifically with overlay files.Files using the short machine type include the IBM$RUN.OVL file for windowing utilities and the CMPQ$RUN.OVL file that uses a default black-and-white color palette for NetWare menus.The short machine type is set in the NET.CFG file, using the SHORT MACHINE TYPE parameter. The default is IBM.The short machine type can be accessed in login scripts, using the %SMACHINE identifier variable.See also IDREF="FM23712""Login scripts"; IDREF="FM83726""Long machine type."RENDERAS="SECT1"SIDF(System Independent Data Format) The format standard SBACKUP uses. All data backed up using SBACKUP can be read by other backup applications that read and write SIDF.RENDERAS="SECT1"ID="FM94361"Simple Network Management ProtocolIDXID="w2390"BOOK="_idx" COLLECTION="nw41" TIDREF="i4160"(SNMP) An industry-standard protocol that specifies a format for collecting network management data. With Desktop SNMP services, NetWare client workstations can send status information to an SNMP management program running on an IPX or TCP/IP network.Desktop SNMP services can be managed using NMSTM software, industry-standard SNMP management consoles, or other third-party management systems.RENDERAS="SECT2"Community Names and TypesIDXID="w2391"BOOK="_idx" COLLECTION="nw41" TIDREF="i709"PAGENUM=323 ID="BP324"Desktop SNMP and other SNMP entities use community names and types to provide access control. Desktop SNMP provides default community names for the monitor and control communities, as well as default community types used for traps. Desktop SNMP supports the following three communities, as described in the following table:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"NameCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Control communityCOLNAME=2 ROTATE="0" MOREROWS="0"Describes the read/write community (the community that is allowed to do SET operations). COLNAME=1 ROTATE="0" MOREROWS="0"Monitor community COLNAME=2 ROTATE="0" MOREROWS="0"Describes the read-only community (the community that is allowed to do GET and GET NEXT operations). COLNAME=1 ROTATE="0" MOREROWS="0"Trap communityCOLNAME=2 ROTATE="0" MOREROWS="0"Describes the community name used for traps. The community name contained in a request message from an SNMP management station must match the name expected by Desktop SNMP. A community name can be any ASCII string, up to 32 characters in length. It cannot include space, tab, open square bracket ([), equal sign (=), colon (:), semicolon (;), single quotation mark ("), or number sign (#).Community name strings are case-sensitive. Always enclose the community name string in quotation marks.RENDERAS="SECT2"Management Information Base (MIB-II) SupportDesktop SNMP automatically supports three MIB-II groups: MARK=BULLETSystem and SNMP groupsInterface groupTCP/IP groups (except interface, system, and SNMP, which are supported by other VLM files, and EGP and transmission, which are not supported)PAGENUM=324 ID="BP325"RENDERAS="SECT1"Single Reference time serverA server that provides time to Secondary time servers and to workstations. The Single Reference time server is the sole source of time on the network.See also IDREF="FM65772""Time synchronization."RENDERAS="SECT1"ID="FM20838"Small Computer Systems Interface(SCSI) An industry standard that sets guidelines for connecting peripheral devices and their controllers to a microprocessor.See IDREF="FM75975""SCSI."RENDERAS="SECT1"SMDR(Storage Management Data Requester) IDXID="w2392"BOOK="_idx" COLLECTION="nw41" TIDREF="i4295"
Passes commands and information between SBACKUP and Target Service Agents.See IDREF="FM73920""Storage Management Data Requester."RENDERAS="SECT1"ID="FM65894"SMS(Storage Management Services) A combination of related services that allow data to be stored and retrieved.See IDREF="FM66936""Storage Management Services."RENDERAS="SECT1"SMSDI(SMS Storage Device Interface) A set of routines that allows SBACKUP to access various storage devices and media.See IDREF="FM13841""SMS Storage Device Interface."RENDERAS="SECT1"ID="FM13841"SMS Storage Device Interface(SMSDI) A set of routines that allows SBACKUP to access various storage devices and media.If more than one storage device is attached to the host, the SMSDI sends SBACKUP a list of storage devices and media, each labeled Available or Unavailable.PAGENUM=325 ID="BP326"SBACKUP displays this list so you can select an available device to store backup data on.If a storage device is unavailable, it is being used by another application. Such a device remains unavailable until the application gives it up, or until the application is exited.See also IDREF="FM24312""Backup"; IDREF="FM52079""Backup hosts and targets"; IDREF="FM74176""Media Manager"; IDREF="FM66936""Storage Management Services."RENDERAS="SECT1"SNA(System Network Architecture) IBM's proprietary networking architecture, was first introduced in 1974.See IDREF="FM60628""System Network Architecture."RENDERAS="SECT1"SNMP(Simple Network Management Protocol) An industry standard protocol that specifies a format for collecting network management data.See IDREF="FM94361""Simple Network Management Protocol."RENDERAS="SECT1"ID="FM10425"SocketIDXID="w2393"BOOK="_idx" COLLECTION="nw41" TIDREF="i4195"IDXID="w2394"BOOK="_idx" COLLECTION="nw41" TIDREF="i4195"The part of an IPX internetwork address, within a network node, that represents the destination of an IPX packet.Some sockets are reserved by Novell for specific applications. For example, IPX delivers all NCP request packets to socket 451h.Third-party developers can also reserve socket numbers for specific purposes by registering those numbers with Novell.The following table lists key socket numbers reserved by Novell:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"SocketCOLNAME=2 ROTATE="0" MOREROWS="0"ProcessVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"451hCOLNAME=2 ROTATE="0" MOREROWS="0"NCPCOLNAME=1 ROTATE="0" MOREROWS="0"452hCOLNAME=2 ROTATE="0" MOREROWS="0"SAPCOLNAME=1 ROTATE="0" MOREROWS="0"453hCOLNAME=2 ROTATE="0" MOREROWS="0"RIPCOLNAME=1 ROTATE="0" MOREROWS="0"455hCOLNAME=2 ROTATE="0" MOREROWS="0"NetBIOSCOLNAME=1 ROTATE="0" MOREROWS="0"456hCOLNAME=2 ROTATE="0" MOREROWS="0"DiagnosticsCOLNAME=1 ROTATE="0" MOREROWS="0"8063hCOLNAME=2 ROTATE="0" MOREROWS="0"Novell Virtual Terminal® (NVT)COLNAME=1 ROTATE="0" MOREROWS="0"4000-6000hCOLNAME=2 ROTATE="0" MOREROWS="0"Temporary sockets used for interaction with NetWare servers and other network communicationsPAGENUM=326 ID="BP327"See also IDREF="FM70179""IPX internetwork address."RENDERAS="SECT1"IDXID="w2395"BOOK="_idx" COLLECTION="nw41" TIDREF="i3918"
Source routingIDXID="w2396"BOOK="_idx" COLLECTION="nw41" TIDREF="i4214"A method used by IBM to route data across source-routing bridges. NetWare source routing programs allow an IBM token ring network bridge to forward NetWare packets (or frames).IBM bridges can be configured as either single-route broadcast or all-routes broadcast. (Default: single-route broadcast.)MARK=BULLETIDXID="w2397"BOOK="_idx" COLLECTION="nw41" TIDREF="i4163"Single-route broadcasting. Only designated single-route bridges pass the packet and only one copy of the packet arrives on each ring in the network.Single-route bridges can transmit single-route, all-routes, and specifically-routed packets.IDXID="w2398"BOOK="_idx" COLLECTION="nw41" TIDREF="i162"All-routes broadcasting. Sends the packet across every possible route in the network, resulting in as many copies of the frame at the destination as there are bridges in the network.All-routes bridges pass both all-routes broadcasts and specifically-routed packets.To support IBM hardware and applications, Novell provides ROUTE.NLM for the NetWare server and ROUTE.COM for DOS workstations (or ROUTE.SYS for OS/2 workstations).PAGENUM=327 ID="BP328"These drivers allow users running NetWare 4 to communicate across IBM Token Ring network bridges. They also allow IBM applications that require source routing support to run unmodified on NetWare networks.Parameters for ROUTE.NLM determine which packets are broadcast as all-routes packets or as single-route packets.At the workstation, ROUTE.COM determines the type of packets the workstation broadcasts. Add the command to load ROUTE.COM after LANSUP.COM or TOKEN.COM, but before the protocol stack (for example, IPXODI.COM).RENDERAS="SECT1"ID="FM24361"Source serverIDXID="w2399"BOOK="_idx" COLLECTION="nw41" TIDREF="i4216"IDXID="w2400"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"The server from which you migrate data files, bindery files, and other information to a NetWare 4 destination server during upgrade.See also IDREF="FM91450""Destination server."RENDERAS="SECT1"Sparse fileIDXID="w2401"BOOK="_idx" COLLECTION="nw41" TIDREF="i4220"IDXID="w2402"BOOK="_idx" COLLECTION="nw41" TIDREF="i474"IDXID="w2403"BOOK="_idx" COLLECTION="nw41" TIDREF="i1307"A file with at least one empty block. (NetWare won't write any block that is completely empty.)Databases often create sparse files.For example, suppose the disk allocation block size for volume VOL1: is 4 KB. Also suppose that a database opens a new file, seeks out the 1,048,576th byte, writes five bytes, and closes the file.An inefficient operating system would save the entire file to disk.The file would be comprised of 256 zero-filled disk allocation blocks (the first 1 MB) and one more disk allocation block with five bytes of data and 4,091 zeros. This method would waste 1 MB of disk space.However, NetWare writes only the last block to disk, saving time and disk space.Sparse files aren't limited to large files. If a two-block file is created and the first block is empty, the operating system treats the file as a sparse file.PAGENUM=328 ID="BP329"If a program tries to read from a file's empty blocks, the operating system generates and returns zeros.The NetWare NCOPY command doesn't copy sparse files automatically. NCOPY has a /f option that forces the operating system to copy sparse files.RENDERAS="SECT1"ID="FM43851"SPXIDXID="w2404"BOOK="_idx" COLLECTION="nw41" TIDREF="i4245"(Sequenced Packet Exchange) A NetWare DOS Requester module that enhances the IPX protocol by supervising data sent out across the network.SPX verifies and acknowledges successful packet delivery to any network destination by requesting a verification from the destination that the data was received.The SPX verification must include a value that matches the value calculated from the data before transmission. By comparing these values, SPX ensures not only that the data packet made it to the destination, but that it arrived intact.SPX can track data transmissions consisting of a series of separate packets. If an acknowledgment request brings no response within a specified time, SPX retransmits it.After a reasonable number of retransmissions fail to return a positive acknowledgment, SPX assumes the connection has failed and warns the operator of the failure.SPX is derived from Novell IPX using the Xerox Packet Protocol.See also IDREF="FM21900""NetWare DOS Requester"; IDREF="FM93979""NetWare Client for OS/2"; IDREF="FM50073""NetWare user tools." RENDERAS="SECT1"STARTUP.NCFIDXID="w2405"BOOK="_idx" COLLECTION="nw41" TIDREF="i4266"A NetWare server boot file that loads the NetWare server's disk driver and name spaces and some SET parameters.See also IDREF="FM50252""Boot files."PAGENUM=329 ID="BP330"RENDERAS="SECT1"ID="FM62441"StationIDXID="w2406"BOOK="_idx" COLLECTION="nw41" TIDREF="i4274"Usually a shortened form of workstation, but can also be a server, router, printer, fax machine, or any computer device connected to a network by a network board and a communication medium.RENDERAS="SECT1"Station addressIDXID="w2407"BOOK="_idx" COLLECTION="nw41" TIDREF="i4274"A number that uniquely identifies a network board; usually referred to as the node number.See IDREF="FM74415""Node number."RENDERAS="SECT1"Stop bitIDXID="w2408"BOOK="_idx" COLLECTION="nw41" TIDREF="i4292"A signal that indicates the end of a character.See also IDREF="FM44412""Serial communication."RENDERAS="SECT1"Storage deviceA device used to back up data from a server or workstation. An example of a storage device is an external tape drive that backs up data from a hard disk to magnetic tape.RENDERAS="SECT1"ID="FM73920"Storage Management Data RequesterIDXID="w2409"BOOK="_idx" COLLECTION="nw41" TIDREF="i4295"(SMDR) Passes commands and information between SBACKUP and Target Service Agents.See also IDREF="FM66936""Storage Management Services."RENDERAS="SECT1"ID="FM66936"Storage Management ServicesIDXID="w2410"BOOK="_idx" COLLECTION="nw41" TIDREF="i4297"(SMS) Services that allow data to be backed up and restored. SMS is independent of backup/restore hardware and file systems (such as DOS, OS/2, Macintosh, MS Windows, or UNIX).RENDERAS="SECT2"SMS ArchitectureNetWare provides the following SMS-compliant NLM programs and other software modules that run on servers:PAGENUM=330 ID="BP331"MARK=BULLETIDXID="w2411"BOOK="_idx" COLLECTION="nw41" TIDREF="i3953"SBACKUP. A backup engine that provides backup and restore capabilities.IDXID="w2412"BOOK="_idx" COLLECTION="nw41" TIDREF="i4295"SMDR (Storage Management Data Requester). Passes commands and information between SBACKUP and Target Service Agents.SMSDI (SMS Storage Device Interface). Passes commands and information between SBACKUP and the storage devices and media.IDXID="w2413"BOOK="_idx" COLLECTION="nw41" TIDREF="i3953"Device drivers (IDE.DSK, TAPEDAI.DSK, AHAnnnn.DSK). Control the mechanical operation of storage devices and media by acting on commands passed from SBACKUP through the SMSDI.IDXID="w2414"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"IDXID="w2415"BOOK="_idx" COLLECTION="nw41" TIDREF="i4425"NetWare Server Target Service Agents (such as TSA410). Pass requests for data (generated within SBACKUP) to the NetWare server where the data resides and then return requested data through the SMDR to SBACKUP.IDXID="w2416"BOOK="_idx" COLLECTION="nw41" TIDREF="i924"IDXID="w2417"BOOK="_idx" COLLECTION="nw41" TIDREF="i4425"Database Target Service Agents (such as TSANDS). Pass commands and data between the host server (where SBACKUP resides) and the database where the data to be backed up resides, then return the requested data through the SMDR to SBACKUP.IDXID="w2418"BOOK="_idx" COLLECTION="nw41" TIDREF="i4842"IDXID="w2419"BOOK="_idx" COLLECTION="nw41" TIDREF="i4425"Workstation Target Service Agents (such as TSADOS and TSAOS2). Pass commands and data between the host server (where SBACKUP resides) and the station where the data to be backed up resides, then return the requested data through the SMDR to SBACKUP.IDXID="w2420"BOOK="_idx" COLLECTION="nw41" TIDREF="i3953"IDXID="w2421"BOOK="_idx" COLLECTION="nw41" TIDREF="i4838"Workstation Manager (WSMAN). Receives "I am here" messages from stations available to be backed up. It keeps the names of these stations in an internal list.Although all SMS software modules are loaded on the host server, all modules aren't used in all backups.See also Chapter 9, "BOOK="superenu" COLLECTION="nw41"Backing Up and Restoring Data," in Supervising the Network.PAGENUM=331 ID="BP332"RENDERAS="SECT2"Backing Up a Host ServerThe following figure shows a simplified diagram of backing up a host server:LABEL="68" FLOAT="0"Backing Up a Host Server IDXID="w2422"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"FILEREF="n41co58a.tif"The numbered portions in the preceding diagram are explained in the following list:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"From the host server command line, the network supervisor initiates SBACKUP, which uses SMDR to access the NetWare server Target Service Agent.The server Target Service Agent (such as TSA410.NLM and TSA312.NLM) obtains the requested data, then passes it through the SMDR to SBACKUP, which passes it on to the SMSDI.PAGENUM=332 ID="BP333"The SMSDI uses device drivers to send the data to the selected device and media for storage.RENDERAS="SECT2"Backing Up a Target ServerThe following figure shows a simplified diagram of backing up a target server (any server other than the host):LABEL="69" FLOAT="0"IDXID="w2423"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"IDXID="w2424"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"Backing Up a Target ServerFILEREF="n41co59a.tif"The numbered portions in the preceding diagram are explained in the following list:PAGENUM=333 ID="BP334"NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"From the host server command line, the network supervisor initiates SBACKUP. SBACKUP uses the SMDR to access the Target Service Agent on the target server.The Target Service Agent on the target (such as TSA312.NLM) obtains the requested data, then passes it through SMDR to SBACKUP, which passes it on to the SMSDI.The SMSDI uses device drivers to send the data to the selected device and media for storage.RENDERAS="SECT2"Backing Up a Dos WorkstationThe following figure shows a DOS workstation backup:LABEL="70" FLOAT="0"IDXID="w2425"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"Backing Up a DOS WorkstationFILEREF="n41co60a.tif"PAGENUM=334 ID="BP335"The numbered portions in the preceding diagram are explained in the following list.NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"From the host server command line, the network supervisor initiates SBACKUP.When the DOS Target Service Agent is loaded on the workstation, the DOS Target Service Agent contacts the Workstation Manager on the host server.The Workstation Manager keeps an internal list of all Target Service Agents that have contacted it. By implication, this is a list of workstations that have their Target Service Agent loaded.SBACKUP uses the workstation Target Service Agent to access the Workstation Manager, which, in turn, obtains the data for the backup from the DOS Target Service Agent (TSASMS.COM) and returns it to SBACKUP, which passes it on to the SMSDI.The SMSDI uses device drivers to send the data to the selected device and media for storage.RENDERAS="SECT2"Backing Up an OS/2 WorkstationThe following figure shows a simplified diagram of an OS/2 workstation backup:PAGENUM=335 ID="BP336"LABEL="71" FLOAT="0"IDXID="w2426"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"Backing Up an OS/2 WorkstationFILEREF="n41co61a.tif"The numbered portions in the preceding diagram are explained in the following list:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"From the host server command line, the network supervisor initiates SBACKUP. SBACKUP uses the workstation Target Service Agent to access a connection with the OS/2 Target Service Agent (TSAOS2.EXE).TSAOS2.NLM keeps an internal list of all Target Service Agents that have contacted it. By implication, this is a list of workstations that are available for backup by the host file server.SBACKUP begins to communicate directly with the OS/2 Target Service Agent, bypassing the workstation Target Service Agent.SBACKUP passes the requested data to the SMSDI which uses device drivers to send the data to the selected device and media for storage.PAGENUM=336 ID="BP337"RENDERAS="SECT2"Backing Up a Btrieve DatabaseThe following figure shows a simplified diagram of backing up a Btrieve database:LABEL="72" FLOAT="0"IDXID="w2427"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"Backing Up a Btrieve DatabaseFILEREF="n41co62a.tif"The numbered portions in the preceding diagram are explained in the following list.NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"From the host server command line, the network supervisor initiates SBACKUP, which uses the SQL Target Service Agent to access the Btrieve database (or databases) to obtain the data for the backup.The SQL Target Service Agent (TSASQL) obtains the requested data from the database and passes it through the SMDR to SBACKUP, which passes the requested data to the SMSDI.PAGENUM=337 ID="BP338"The SMSDI receives the data for storage from SBACKUP and uses device drivers to send the data to the selected device and media for storage.RENDERAS="SECT2"Backing Up a Netware Directory Services DatabaseThe following figure shows a simplified diagram of backing up a NetWare Directory Services database:LABEL="73" FLOAT="0"IDXID="w2428"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"Backing Up a NetWare Directory Services DatabaseFILEREF="n41co63a.tif"The numbered portions in the preceding diagram are explained in the following list.NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"From the host server command line, the network supervisor initiates SBACKUP, which uses the NDS Target Service Agent to access the NDS database (or databases) to obtain the data for the backup.PAGENUM=338 ID="BP339" An NDS database can be located on a local or remote server, or both, or on several servers. SBACKUP can back up the database regardless of where it is located.The NDS Target Service Agent (TSANDS.NLM) obtains the requested data from the NDS database and passes it through the SMDR to SBACKUP, which sends it on to the SMSDI.The SMSDI receives the data for storage from SBACKUP and uses device drivers to send the data to the selected device and media for storage.See also IDREF="FM52079""Backup hosts and targets"; IDREF="FM40161""NetWare Directory database"; IDREF="FM68484""NetWare Loadable Module"; IDREF="FM66936""Storage Management Services"; IDREF="FM82095""Target Service Agent."RENDERAS="SECT1"STREAMSIDXID="w2429"BOOK="_idx" COLLECTION="nw41" TIDREF="i4303"IDXID="w2430"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"An NLM program that provides a common interface between NetWare and transport protocols such as IPX/SPX, TCP/IP, SNA, and OSI that need to deliver data and requests to NetWare for processing.By making the transport protocol transparent to the network operating system, STREAMSTM allows services to be provided across the network, regardless of the transport protocols used.Network managers can install the protocols of their choice or change the protocols used without affecting the level of services delivered to the user, if the applications support multiple protocols.The relationship between STREAMS and the transport protocol stacks is illustrated in the following figure:IDXID="w2431"BOOK="_idx" COLLECTION="nw41" TIDREF="i4303"IDXID="w2432"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"LABEL="74" FLOAT="0"STREAMS StructureFILEREF="n40co34a.tif"PAGENUM=339 ID="BP340"RENDERAS="SECT1"SubdirectoryIDXID="w2433"BOOK="_idx" COLLECTION="nw41" TIDREF="i4314"A directory below another in the file system structure. For example, in SYS:ACCTS\RECEIVE, RECEIVE is a subdirectory of SYS:ACCTS.See also IDREF="FM22177""File system."RENDERAS="SECT1"Subnetwork maskIDXID="w2434"BOOK="_idx" COLLECTION="nw41" TIDREF="i4321"Indicates how the host portion of the IP address is divided into subnetwork addresses and local host address portions. The network mask is a 32-bit number with all ones for all network and subnetwork address portions of the complete IP address, and all zeros for host address portions. With a 16-bit Class B IP network address, a 4-bit subnetwork address, and a 12-bit host address, the subnetwork mask consists of 20 ones and 12 zeros. In essence, a subnetwork mask locally extends the network address portion of an IP address.RENDERAS="SECT1"Subordinate replicaA Directory replica that is automatically placed on a server if the parent Directory partition has a master, read/write, or read-only replica and the child Directory partition does not.Subordinate replicas cannot be modifiedRENDERAS="SECT1"Supervisor rightIDXID="w2435"BOOK="_idx" COLLECTION="nw41" TIDREF="i4330"A file system right that grants all rights to the respective directory and files.Also, an object right that grants all access privileges to all objects.Also, a property right that grants all rights to all properties or to selected properties.See also IDREF="FM74455""Rights."RENDERAS="SECT1"Supported gatewayIDXID="w2436"BOOK="_idx" COLLECTION="nw41" TIDREF="i1592"IDXID="w2437"BOOK="_idx" COLLECTION="nw41" TIDREF="i2765"A protocol that is supported by a Messaging Server object.PAGENUM=340 ID="BP341"For example, you may want the users of your NetWare MHS messaging server to be able to communicate with (non-native) users from a SNADS or X.400 messaging environment. You can add the SNADS and X.400 protocols to the messaging server as supported gateways.RENDERAS="SECT1"ID="FM26599"Surface testIDXID="w2438"BOOK="_idx" COLLECTION="nw41" TIDREF="i4348"IDXID="w2439"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"A test in the NetWare INSTALL program that lets you test the NetWare partition on a hard disk for bad blocks. It is normally not necessary to run this test.The surface test can run in the background on one or more dismounted hard disks so that you (or other users) can work on mounted volumes on other hard disks.You can choose either a destructive or a nondestructive surface test:MARK=BULLETDestructive test. Acts like a disk format---it destroys data as it makes several passes over the disk surface, reading and writing test patterns.Nondestructive test. Pre-reads and saves existing data while it reads and writes test patterns to the hard disk. Then the program writes the data back to the disk.Neither surface test option can be executed unless the volumes on the hard disk are dismounted.RENDERAS="SECT1"Switch blockIDXID="w2440"BOOK="_idx" COLLECTION="nw41" TIDREF="i4352"A set of switches mounted to form a single component.In some NetWare servers, a switch block is used to control system configuration data, such as type of monitor, amount of memory, and number of drives.Some network boards use switch blocks to set system addresses (such as station, base I/O, and base memory addresses).PAGENUM=341 ID="BP342"RENDERAS="SECT1"SynchronizationReplica synchronization. A means of ensuring that replicas of a Directory partition contain the same information as other replicas of that partition. (See IDREF="FM27324""NetWare Directory replica.")Time synchronization. A method of ensuring that all servers in a Directory tree report the same time. (See IDREF="FM65772""Time synchronization.")RENDERAS="SECT1"IDXID="w2441"BOOK="_idx" COLLECTION="nw41" TIDREF="i4374"
System (Sy) attributeA file system attribute that marks directories or files for use only by the operating system.See also IDREF="FM85330""Attributes."RENDERAS="SECT1"ID="FM79008"SYSTEM directoryIDXID="w2442"BOOK="_idx" COLLECTION="nw41" TIDREF="i4377"The SYS:SYSTEM directory, created during network installation, that contains NetWare operating system files as well as NLM programs and NetWare utilities for managing the network.By default user ADMIN, or a user with ADMIN equivalent rights, has rights to the SYS:SYSTEM directory.Don't delete the SYSTEM directory.See also IDREF="FM22177""File system"; IDREF="FM52477""LOGIN directory"; IDREF="FM38021""MAIL directory"; IDREF="FM82664""PUBLIC directory."RENDERAS="SECT1"System Independent Data Format(SIDF) The format standard SBACKUP uses. All data backed up using SBACKUP can be read by other backup applications that read and write SIDF.RENDERAS="SECT1"ID="FM93344"System Fault ToleranceIDXID="w2443"BOOK="_idx" COLLECTION="nw41" TIDREF="i4378"(SFT) A means of protecting data by providing procedures that allow you to automatically recover from hardware failures.There are three levels of SFT; each level of redundancy (duplication) decreases the possibility of data loss.PAGENUM=342 ID="BP343"MARK=BULLETSFT Level I: Hot Fix. Ensures that data is not saved to faulty blocks on the server's hard disk. (See IDREF="FM95725""Hot Fix.")SFT Level II: Disk Mirroring or Duplexing. Disk mirroring protects against hard disk failures by pairing two hard disks on the same channel. The disks operate in tandem, constantly storing and updating the same files. (SeeIDREF="FM66029""Disk mirroring.")Disk duplexing pairs two disks on different channels, which protects data from the failure of the hard disk or the channel that joins the hard disk to the NetWare server. (See IDREF="FM60634""Disk duplexing.")SFT Level III: Server Mirroring. Provides protection from server failure with a secondary, identical server that immediately takes over network operations when the primary server fails. (See IDREF="FM84857""Server mirroring.")Each level of SFT protection includes the previous levels; that is, SFT III includes level I and level II protection.See also IDREF="FM20059""Data protection."RENDERAS="SECT1"System login scriptIDXID="w2444"BOOK="_idx" COLLECTION="nw41" TIDREF="i4384"IDXID="w2445"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"In NetWare 2 and NetWare 3, a type of login script that sets general environments for all users.In NetWare 4, the container login script replaces the system login script.See IDREF="FM56194""Container login script"; IDREF="FM23712""Login scripts."RENDERAS="SECT1"ID="FM60628"System Network ArchitectureIDXID="w2446"BOOK="_idx" COLLECTION="nw41" TIDREF="i4387"(SNA) IBM's proprietary networking architecture first introduced in 1974. SNA is the technology that makes it possible to connect LAN systems to IBM mainframe computers.SNA has reached a position of prominence in the computer industry based on its completeness and its continued support by IBM. PAGENUM=343 ID="BP344"RENDERAS="SECT1"IDXID="w2447"BOOK="_idx" COLLECTION="nw41" TIDREF="i4389"IDXID="w2448"BOOK="_idx" COLLECTION="nw41" TIDREF="i3718"
System redundancyThe duplication of key system components in order to protect against failure.SFT III provides a high level of system redundancy through mirrored network servers. When one server fails, the other instantly takes over. But SFT III only protects against a single hardware failure in one of the servers.For protection from other failures, install redundant cabling, power supplies, disk storage, gateways, routers, network boards, mirrored server links, printers, and other mission-critical network components.PAGENUM=344 ID="BP345"TRENDERAS="SECT1"Tape backup deviceIDXID="w2449"BOOK="_idx" COLLECTION="nw41" TIDREF="i4423"Either an internal or external tape drive that backs up data from hard disks.RENDERAS="SECT1"ID="FM46936"TargetIDXID="w2450"BOOK="_idx" COLLECTION="nw41" TIDREF="i3953"Any server, workstation, or service on the network which has a Target Service Agent loaded. A target can have its data backed up or restored.If you are backing up and restoring to the host server, the target and the host are the same.See also IDREF="FM71612""Host"; IDREF="FM82095""Target Service Agent."RENDERAS="SECT1"ID="FM82095"Target Service AgentIDXID="w2451"BOOK="_idx" COLLECTION="nw41" TIDREF="i4425"A program that processes data moving between a specific target and an SMS-compliant backup engine, such as SBACKUP. When using SBACKUP, the host sends requests to the Target Service Agent, whichMARK=BULLETReceives the commands from SBACKUP and processes them so that the target operating system can handle the request for dataPasses the data request from SBACKUP to the targetReceives the requested data from the target and returns it to SBACKUP in standard SMS formatServers and workstations running different software releases, or having different operating systems, require NetWare-compatible Target Service Agents to communicate with SBACKUP.See also IDREF="FM52079""Backup hosts and targets"; IDREF="FM66936""Storage Management Services."RENDERAS="SECT1"PAGENUM=345 ID="BP346"Target Service Agent resourcesIDXID="w2452"BOOK="_idx" COLLECTION="nw41" TIDREF="i4425"IDXID="w2453"BOOK="_idx" COLLECTION="nw41" TIDREF="i3821"Categories of data, referred to as major resources and minor resources, created by each Target Service Agent. (See IDREF="FM34549""Major resource" and IDREF="FM51647""Minor resource.")Because these resources vary with each Target Service Agent, SBACKUP processes these resources in different ways.See also IDREF="FM82095""Target Service Agent."RENDERAS="SECT1"Task-switching support softwareIDXID="w2454"BOOK="_idx" COLLECTION="nw41" TIDREF="i4438"The TBMI2.COM and TASKID.COM files that act as a buffer and manager between IPX and SPX requests and an application's calling process in a task switching environment.IDXID="w2455"BOOK="_idx" COLLECTION="nw41" TIDREF="i1978"
When a task switch is made during an application's call process, the task-switching support software in NetWare ensures that IPX and SPX transport protocols send the call to the proper network resource. This prevents any breaking down of communication between IPX and software processes when a task switch is made.Use support software if you use a DOS task switcher or if you switch DOS sessions within MS Windows in standard or real mode.If your application requires the NetWare task-switching support software and you do not use it, your client workstation may experience session failure.RENDERAS="SECT1"ID="FM82397"TCP/IPIDXID="w2456"BOOK="_idx" COLLECTION="nw41" TIDREF="i4455"(Transmission Control Protocol/Internet Protocol) An industry-standard suite of networking protocols that enables dissimilar nodes in a heterogenous environment to communicate with one another.TCP/IP is built upon four layers that roughly correspond to the seven layer OSI model. The TCP/IP layers areTYPE="VERT"Process/applicationHost to hostInternetNetwork accessPAGENUM=346 ID="BP347"RENDERAS="SECT2"NetWare TCP/IPA collection of NLM programs that support applications requiring TCP/IP connectivity. Its routing capabilities forward IP traffic from one network to another.NetWare TCP/IP uses Routing Information Protocol (RIP) to communicate the internet's configuration with other routers.It also provides communication between NetWare (IPX) networks across an IP internet that doesn't directly support IPX. This is known as IPX/IP tunneling.NetWare TCP/IP also provides a transport interface for higher-level network services. This interface is used by the Network File System (NFS) and third-party applications written for either the 4.3 BSD UNIX socket interface or the AT&T* Streams Transport Layer Interface (TLI).NetWare TCP/IP supports Ethernet, token ring, and ARCnet networks through the ODI. It works with any network adapters of these types supported by a NetWare driver certified for NetWare 3.11 and later versions (including NetWare 4).RENDERAS="SECT1"Technical Service AllianceIDXID="w2457"BOOK="_idx" COLLECTION="nw41" TIDREF="i4458"(TSA) A cooperative program supported by Novell and numerous companies. The Technical Service AllianceCM companies work together to solve technical problems for customers they share.See also IDREF="FM82095""Target Service Agent."RENDERAS="SECT1"ID="FM27496"TerminationIDXID="w2458"BOOK="_idx" COLLECTION="nw41" TIDREF="i4466"Placing a terminating resistor at the end of a bus, line, chain, or cable to prevent signals from being reflected or echoed.Data signals travel along a cable or bus that is in many ways analogous to a pipe. You must terminate the end components to ensure that the signal doesn't echo back along the cable or bus and cause corruption.PAGENUM=347 ID="BP348"If you connect a disk subsystem to your server's HBA using a SCSI bus, the bus must be terminated on both ends. The hard disks connected to the respective controllers must also be terminated, as in the following figure:LABEL="75" FLOAT="0"Termination of Disk SubsystemFILEREF="n40co14a.tif"See also IDREF="FM19745""Hard disk"; IDREF="FM26878""Host Bus Adapter"; IDREF="FM83109""SCSI bus."RENDERAS="SECT1"ID="FM65772"Time synchronizationIDXID="w2459"BOOK="_idx" COLLECTION="nw41" TIDREF="i4492"IDXID="w2460"BOOK="_idx" COLLECTION="nw41" TIDREF="i4355"A method of ensuring that all servers in a Directory tree report the same time.Clocks in computers can deviate slightly, resulting in different times on different servers. Time synchronization corrects these deviations so that all servers in a Directory tree report the same time and provide a time stamp to order NDS events.Whenever an event occurs in the Directory, such as when a password is changed, or an object renamed, NDS requests a time stamp.IDXID="w2461"BOOK="_idx" COLLECTION="nw41" TIDREF="i4489"A time stamp is a unique code that includes the time and identifies this event. The NDS event is assigned a time stamp so that the order in which Directory replicas are updated is correct.NDS uses time stamps toMARK=BULLETEstablish the order of events (such as object creation and Directory partition replication)PAGENUM=348 ID="BP349"Record "real world" time valuesSet expiration datesTime stamps are especially important when Directory partitions are replicated and need to be concurrent with one another.Replication allows Directory partition updates to originate from many locations. As various users update theDirectory replicas of the Directory partition, some updates inevitably pertain to the same data.For example, a user might delete an object and then recreate it. But without a method of recording the order of these events, the Directory could try to create the object and then delete it.Time stamps allow the Directory to reproduce the order of events acurately.RENDERAS="SECT2"IDXID="w2462"BOOK="_idx" COLLECTION="nw41" TIDREF="i4484"
Time ServersWhen you install NetWare 4.1 on a server, you are prompted to designate it as a Single Reference, Primary, Reference, or Secondary time server.Each designation performs a particular time synchronization function:MARK=BULLETIDXID="w2463"BOOK="_idx" COLLECTION="nw41" TIDREF="i4162"Single Reference time server. Provides time to Secondary time servers and to workstations.This server determines the time for the entire network and is the only source of time on the network. The network supervisor sets the time on the Single Reference time server.Because the Single Reference time server is the source of time on the network, all other servers must be able to contact it.The following figure illustrates a Single Reference time server providing time to Secondary time servers and to its own workstations. The Secondary time servers, in turn, provide time to their workstations.PAGENUM=349 ID="BP350"LABEL="76" FLOAT="0"Single Reference Time ServerFILEREF="n40co66a.tif"The Single Reference time server works on networks of any size, but this configuration is used primarily for small networks that aren't WANs.If you use a Single Reference time server, don't use any Primary or Reference time servers on the network.IDXID="w2464"BOOK="_idx" COLLECTION="nw41" TIDREF="i3389"Primary time server. Synchronizes the time with at least one other Primary or Reference time server and provides the time to Secondary time servers and to workstations.Primary time servers also vote with other Primary or Reference time servers to determine what the common network time should be.PAGENUM=350 ID="BP351"The following figure shows Primary time servers in various locations providing time to their respective Secondary time servers. Secondary time servers, in turn, provide time to their workstations.LABEL="77" FLOAT="0"Primary Time ServersFILEREF="n40co47a.tif"Use the Primary time server on larger networks to increase fault tolerance by providing redundant paths for Secondary time servers.If a Primary time server goes down, the Secondary time server can get the time from an alternate Primary time server.PAGENUM=351 ID="BP352"Place a Primary time server in each geographically distinct area so that secondary servers and workstations can access them without using WAN links.You must have at least one other Primary or Reference time server that the Primary time server can contact. Whenever Primary and Reference time servers are on a network, they must be able to contact each other for polling.However, Primary servers do adjust their internal clocks to synchronize with that common network time. Because all Primary servers adjust their clocks, network time may drift slightly.IDXID="w2465"BOOK="_idx" COLLECTION="nw41" TIDREF="i3720"Reference time server. Provides a time to which all other time servers and workstations synchronize.Reference time servers may be synchronized with an external time source, such as a radio clock.Reference time servers vote with other Primary or Reference time servers to determine what the common network time should be.However, Reference time servers don't adjust their internal clocks; instead, the Primary servers' internal clocks are adjusted to synchronize with the Reference time server.Therefore, a Reference time server acts as a central point to set network time. Eventually, all Primary time servers adjust their clocks to agree with a Reference time server.The following figure shows a Reference time server synchronized to an external clock. The Reference time server, in turn, provides time to its own secondary servers and workstations, as well as to the Primary time server at another location.PAGENUM=352 ID="BP353"LABEL="78" FLOAT="0"Reference Time ServerFILEREF="n40co46a.tif"Use a Reference time server when it is important to have a central point to control time on the network. Usually, only one Reference time server is installed on a network.You can use more than one Reference time server on a network, but you must synchronize each Reference time server with an external time source, such as a radio clock.You must have at least one other Primary time server that the Reference time server can contact.Whenever Primary and Reference time servers are on a network, they must be able to contact each other for polling.IDXID="w2466"BOOK="_idx" COLLECTION="nw41" TIDREF="i3990"Secondary time server. Secondary time servers obtain the time from a Single Reference, Primary, or Reference time server. They adjust their internal clocks to synchronize with the network time, and they provide the time to workstations.A Secondary time server doesn't participate in determining the correct network time.If you have designated a server on the network as a Single Reference time server, then designate all other servers on the network as Secondary time servers.PAGENUM=353 ID="BP354"If you have designated several servers on the network as Primary or Reference time servers, then designate all other servers on the network as Secondary time servers.To keep network traffic to a minimum, connect Secondary time servers to Primary or Reference time servers that are physically nearby.For optimal time synchronization, minimize the number of intervening routers and slow LAN segments between Secondary time servers and their Single Reference, Primary, or Reference time server.RENDERAS="SECT2"SAP and Custom ConfigurationTime source servers use one of two methods to find each other: SAP and custom configuration.MARK=BULLETSAP. IDXID="w2467"BOOK="_idx" COLLECTION="nw41" TIDREF="i4073"By default, Primary, Reference, and Single Reference servers use SAP to announce their presence on the network.Primary and Reference time servers use SAP information to determine the other servers to poll to determine the network time.Secondary time servers use SAP information to pick a time server to follow.An advantage of SAP is that it allows quick installation without regard to the network layout. It also allows automatic reconfiguration if operating modes are changed or if new servers are added to the network.A disadvantage of the SAP method is that it generates a small amount of additional network traffic.Another disadvantage is that the SAP method can be disruptive in large network environments where test servers come and go, especially if the test server is polled and its time is substantially different than network time.IDXID="w2468"BOOK="_idx" COLLECTION="nw41" TIDREF="i4484"IDXID="w2469"BOOK="_idx" COLLECTION="nw41" TIDREF="i896"IDXID="w2470"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"Custom configuration. You can list the specific time servers that a particular server should contact.You can also specify that a server shouldn't listen for SAP information from other time sources and that it shouldn't advertise its presence using SAP.PAGENUM=354 ID="BP355"An advantage of custom configuration is that the network supervisor maintains complete control of the time synchronization environment.Also, custom configuration helps eliminate nonessential network SAP traffic, as well as errors associated with accidental reconfiguration.A disadvantage of custom configuration is the increased time required for planning and installation.Also, it is more difficult to install or remove Primary, Reference, or Single Reference time servers. You must manually change the approved server list maintained on each server.RENDERAS="SECT2"Time Synchronization MethodsOn small networks where it is unlikely that servers will be added or reconfigured after initial installation, we recommend that you use a Single Reference time server using SAP (the installation defaults).On larger networks, or on networks subject to frequent accidental reconfiguration when servers are added or removed, custom configuration is recommended.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"TIMESYNC" in Utilities Reference.PAGENUM=355 ID="BP356"RENDERAS="SECT1"ID="FM64932"TopologyIDXID="w2471"BOOK="_idx" COLLECTION="nw41" TIDREF="i4530"The physical layout of network components (such as cables, stations, gateways, and hubs). There are three basic topologies:MARK=BULLETIDXID="w2472"BOOK="_idx" COLLECTION="nw41" TIDREF="i4530"Star network. Workstations are connected directly to a NetWare server but not to each other.IDXID="w2473"BOOK="_idx" COLLECTION="nw41" TIDREF="i4530"Ring network. The NetWare server and workstations are cabled in a ring; a workstation's messages may have to pass through several other workstations before reaching the NetWare server.IDXID="w2474"BOOK="_idx" COLLECTION="nw41" TIDREF="i4530"Bus network. All workstations and the NetWare server are connected to a central cable (called a trunk or bus).RENDERAS="SECT1"ID="FM67355"Transaction Tracking SystemIDXID="w2475"BOOK="_idx" COLLECTION="nw41" TIDREF="i4547"(TTS) A system that protects data from corruption by backing out incomplete transactions that result from a failure in a network component.When a transaction is backed out, data is returned to the state it was in before the transaction began.TTS is a standard feature on NetWare 4 servers.TTS is extremely important because it protects the NetWare Directory database and the queuing database files from corruption.Do not disable TTS on a server because this prevents updates to the Directory database on that server. RENDERAS="SECT2"Advantages of Having TTS in the Netware ServerMainframe, minicomputer, and network database systems have offered transaction backout capability for some time.However, in most cases this capability is implemented as part of the database application software and not as part of the operating system.NetWare TTS is implemented at the operating system level on the NetWare server. This method provides two major advantages over application-level implementation:PAGENUM=356 ID="BP357"MARK=BULLETImproved tracking. Transactions are tracked in the NetWare server, where file writes are transacted. Less data is transferred across the network, and all transactions benefit from the speed of the disk caching system in NetWare.Support for applications without backout capability. When a database application without backout capability allocates a physical record lock to a database file or a logical record lock to an open database, the application implies that it is making a transaction.At this point, if you have set the correct parameters, TTS begins tracking this implicit transaction so that the transaction can be backed out if a failure occurs.When a database application without backout capability releases physical or logical record locks, TTS infers that the application has completed a transaction.At this point, TTS ceases tracking the transaction.To enable this feature, use the SET command to set TTS parameters. Three kinds of database applications benefit from TTS:MARK=BULLETApplications that don't have transaction backout capability (implicit transactions)Applications that have built-in transaction backout capability (such as Btrieve)Applications that use explicit NetWare TTS calls to provide transaction backout capability (such as begin, abort, and end)PAGENUM=357 ID="BP358"RENDERAS="SECT2"TTS ProtectionA transaction on a network can be saved improperly in any of the following situations:MARK=BULLETPower to a server or a station is interrupted during a transaction.Server or station hardware fails during a transaction (for example, a parity error on a network board).A server or a station hangs (a software failure) during a transaction.A network transmission component (such as a hub, a repeater, or a cable) fails during a transaction.TTS protects data from failure in these cases by making a copy of the original data before it is overwritten by new data.If a failure occurs during the transaction, TTS can back out the transaction and restore the original data.MARK=BULLETIf the server fails, TTS backs out the transaction when the server comes up again.If a station or network transmission component fails, TTS backs out the transaction immediately.TTS can protect against these types of failures for any type of application that issues record-locking calls and stores information in records, including traditional databases, some electronic mail applications, and some workgroup appointment schedulers.Files that aren't organized into discrete records (such as word processing files) aren't protected by TTS.RENDERAS="SECT2"TTS OperationTTS guarantees that all changes to a file are either wholly completed or not made at all. To track transactions on a given file with TTS, flag the file as Transactional.PAGENUM=358 ID="BP359"A file flagged Transactional can't be deleted or renamed; a file can't be flagged while it is open.When a workstation begins a transaction in a database file, TTS follows four basic steps to maintain the integrity of the file:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"TTS makes a copy of the original data so that the original data can be restored if the transaction fails.The copy is placed in a file external to the database file. This external file contains all transaction backout information; only the operating system uses it.TTS writes the changed data to the database file after the copy of the original has been written to the backout file.TTS repeats Steps 1 and 2 for additional transactions (a single transaction can consist of a sequence of changes).When all changed data has been written to disk, TTS writes a record to the backout file, indicating that the transaction is complete.Completed transactions won't be backed out if the NetWare server, workstation, or network transmission components fail.RENDERAS="SECT2"Record-Locking ThresholdsSince some database applications leave one or more records locked at all times (usually for copy protection), TTS allows you to set a locking threshold in the workstation.This locking threshold can be set so that an implicit transaction isn't unnecessarily tracked when the application is started and the first record lock occurs.Setting the locking threshold prevents having an entire database session tracked as a single transaction or having too many transactions per file update.PAGENUM=359 ID="BP360"RENDERAS="SECT2"Special Backout CasesIn addition to handling routine backout tasks, TTS can back out file truncations or extensions and multiple changes to the same data area during a single transaction.TTS can also back out interrupted transaction backouts (if the NetWare server fails in the middle of backing out transactions from a previous failure).TTS also holds all workstation record locks until a transaction is completed. This prevents the disaster that would result from the following situation:MARK=BULLETThe application in station 1 releases a lock on a record before the transaction is completed (written to disk).Station 2 locks and changes the same record in NetWare server cache memory (also before the first transaction is completed).Station 1 fails and station 2 completes its transaction (it is written to disk).Because station 1 failed, its transaction is backed out, in this case over the transaction that station 2 completed.If TTS didn't hold station record locks until transaction completion, the database wouldn't contain the correct information, since the latest transaction (from station 2) would have been incorrectly overwritten with data that existed before the failed transaction (from station 1).Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"FILER," "BOOK="utlrfenu" COLLECTION="nw41"FLAG," and "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.See also IDREF="FM22916""Cache memory."RENDERAS="SECT1"Transactional (T) attributeIDXID="w2476"BOOK="_idx" COLLECTION="nw41" TIDREF="i4548"A file system attribute that indicates the file is protected by TTS.See also IDREF="FM85330""Attributes."PAGENUM=360 ID="BP361"RENDERAS="SECT1"ID="FM32342"Transmission Control ProtocolIDXID="w2477"BOOK="_idx" COLLECTION="nw41" TIDREF="i4449"(TCP) An industry-standard suite of networking protocols that enabls dissimilar nodes in a heterogenous environment to communicate with one another.See IDREF="FM82397""TCP/IP."RENDERAS="SECT1"ID="FM26134"TrusteeIDXID="w2478"BOOK="_idx" COLLECTION="nw41" TIDREF="i4591"A user or group granted rights to work with a directory, file, or object; the object is called a trustee of that directory, file, or object.Rights are granted to objects (making them trustees) by trustee assignments. Trustee assignments are part of the directory, file, or object to which they grant access.Trustee assignments are stored in a trustee list. An object's trustee list is stored in the object's ACL property.For example, to make group WRITERS a trustee of directory PROJECTS, go to PROJECTS and make WRITERS a trustee.[Public] is a special trustee. You can always specify [Public] as the trustee of a file, directory, or object.Anyone who tries to access a file, directory, or object without any other rights is allowed the rights granted to the [Public] trustee.RENDERAS="SECT2"Granting RightsTrustee assignments for objects and for directories and files are made in the same way, but the rights granted by a trustee assignment are different for objects than for directories and files.Also, object rights have no affect on directories and files, and file and directory rights have no affect on objects.One exception exists: A trustee of a Server object with the Supervisor right is automatically granted the Supervisor right to the root directory of each volume on that server.PAGENUM=361 ID="BP362"When you make a trustee assignment to a directory, file, or object, the trustee has access to the directory, its files, and its subdirectories (unless rights are redefined at the file or subdirectory level) or to the subordinate objects. This is called inheritance.Through inheritance, rights granted to a trustee pass down through the structure unless one of the following is true:MARK=BULLETOther trustee assignments are granted for the same object at a lower level of the directory structureThe Inherited Rights Filter of a subdirectory or file or subordinate object revokes rights granted in a trustee assignment above that pointAn explicit trustee of a directory, file, or object is an object that has a trustee assignment to that directory, file, or object.A trustee through inheritance is an object that has a trustee assignment to a directory, file, or object higher in the structure and inherits rights for the current directory, file, or object.RENDERAS="SECT2"Securing the Directory TreeA trustee assignment for a file or directory always allows the user to see the path to the root directory of the volume. A trustee assignment for an object, however, doesn't automatically show the user the directory tree to the root.This security feature, called the hole in the tree, prevents a user who has rights in one branch of the tree from jumping over a place where he or she doesn't have rights and then browsing the entire tree.Similarly, the Supervisor right, which can't be blocked by an Inherited Rights Filter on a file or directory, can be blocked by the Inherited Rights Filter for an object, either for object or property rights.Use caution when blocking the Supervisor right to objects. If you delete the only object that has the Supervisor right to part of the tree and the Inherited Rights Filter blocks others from inheriting the Supervisor object right, that part of the tree is cut off.PAGENUM=362 ID="BP363"To make trustee assignments for a directory or file, an object must be a trustee of that directory or file with the Access Control right.To make a trustee assignment for an object, an object must be a trustee of that object with the Write or Add Self right to the object's ACL property. Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"FILER", "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN", "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator,"  and "BOOK="utlrfenu" COLLECTION="nw41"RIGHTS" in Utilities Reference.See also IDREF="FM13738""Inherited Rights Filter"; IDREF="FM52521""Security."RENDERAS="SECT1"TSA(Technical Service Alliance) A cooperative program supported by Novell and numerous companies. The TSACM companies work together to solve technical problems for customers they share.See also IDREF="FM82095""Target Service Agent."RENDERAS="SECT1"ID="FM63347"ID="FM90220"TTS(Transaction Tracking System) A system that protects database applications from corruption by backing out incomplete transactions that result from a failure in a network component.See IDREF="FM67355""Transaction Tracking System."RENDERAS="SECT1"ID="FM24560"Turbo FAT index IDXID="w2479"BOOK="_idx" COLLECTION="nw41" TIDREF="i4609"A special FAT index used when a file exceeds 64 blocks (and the corresponding number of FAT entries). NetWare creates a turbo FAT index to group together all FAT entries for that file.The first entry in a turbo FAT index consists of the first FAT number of the file. The second entry consists of the second FAT number, etc.A turbo FAT index enables a large file to be accessed quickly.See also IDREF="FM79681""File Allocation Table."PAGENUM=363 ID="BP364"URENDERAS="SECT1"UnbindingThe process of removing a communication protocol from network boards and LAN drivers.See IDREF="FM34556""Binding and unbinding."RENDERAS="SECT1"UNC redirection(Universal Naming Convention redirection) A technology that allows you to connect and map to network resources without formally connecting to them. IDREF="FM67229""Universal Naming Convention redirection."RENDERAS="SECT1"ID="FM17174"UnicodeIDXID="w2480"BOOK="_idx" COLLECTION="nw41" TIDREF="i4644"IDXID="w2481"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"
A 16-bit character representation, defined by the Unicode Consortium, that supports up to 65,536 unique characters. Unicode allows you to represent the characters for multiple languages using a single Unicode representation.All objects and their attributes in the Directory database are stored in their Unicode representation.However, clients (including DOS and OS/2) use 256-character code pages (using 8-bit characters). Not every character created using a given code page displays correctly on a workstation using a different code page. (For more information on code pages, see your DOS or OS/2 manual.)When you change code pages, you need a different set of Unicode translation tables in order to run NetWare utilities and manage the Directory database.PAGENUM=364 ID="BP365"For example, to use code page 850 (Europe) with country information for France (for which the international telephone country code is 33), you need the following Unicode files:MARK=BULLET850_UNI.033---translates code page 850 to UnicodeUNI_850.033---translates Unicode to code page 850UNI_MON.033---handles monocasing (the proper alphabetization of upper-and lower-case letters)UNI_COL.033---handles collation and sorted listsFor different code pages and locales, you need Unicode tables with corresponding code page numbers and country codes.If you anticipate managing objects created from different code pages, you must limit object names and properties to characters common to all the applicable code pages.See also IDREF="FM75667""Code page."RENDERAS="SECT1"ID="FM99587"Uninterruptible power supplyIDXID="w2482"BOOK="_idx" COLLECTION="nw41" TIDREF="i4647"(UPS) A backup power unit that supplies uninterrupted power if a commercial power outage occurs.Types of UPS are online and offline:MARK=BULLETIDXID="w2483"BOOK="_idx" COLLECTION="nw41" TIDREF="i4647"Online UPS. Actively modifies the power as it moves through the unit. If a power outage occurs, the unit is already active and continues to provide power.An online UPS is usually more expensive than an offline UPS, but provides a nearly constant source of energy during power outages.IDXID="w2484"BOOK="_idx" COLLECTION="nw41" TIDREF="i4647"Offline UPS. Monitors the power line. When power drops, the UPS is activated.The drawback to this method is the slight lag before the offline UPS becomes active. However, most offline UPS systems are fast enough to offset this lag.PAGENUM=365 ID="BP366"Because UPS systems can be expensive, most companies attach them only to the most critical devices, such as NetWare servers, routers, and hard disk subsystems.Attaching a UPS to a server enables the server to properly close files and rewrite the system directory to disk.Unfortunately, most programs run on the workstation and data stored in RAM is not saved during a power outage unless each station has its own UPS.If the UPS doesn't have its own form of surge protection, install a surge protector to protect the UPS from power surges.See also IDREF="FM71926""UPS monitoring."RENDERAS="SECT1"ID="FM67229"Universal Naming Convention redirectionIDXID="w2485"BOOK="_idx" COLLECTION="nw41" TIDREF="i4650"(UNC redirection) A technology that allows you to connect and map to network resources without formally connecting to them. Using UNC redirection, you can do the following:MARK=BULLETUse applications and programs within MS Windows to access network volumes and directoriesAssign network applications, volumes, and directories to icons within MS WindowsThe following utilities and programs let you set up UNC redirection on your DOS and MS Windows client workstations:MARK=BULLETThe MS-DOS NET USE commandThe MS Windows File Manager or Print ManagerNetWare supports the use of UNC redirection for path statements in dialog boxes within the following MS Windows conventions:MARK=BULLETProgram group files (.GRP)Program items filesPAGENUM=366 ID="BP367"Program information files (PIF)Referencing filesRENDERAS="SECT1"UNIX clientIDXID="w2486"BOOK="_idx" COLLECTION="nw41" TIDREF="i4654"A UNIX computer connected to the network.The UNIX client stores and retrieves data from the NetWare server and runs executable network files. The UNIX client provides multiple NetWare-client multitasking on a single station.UNIX clients include IPX/SPX and NCP/IPX communication protocols to allow other NetWare clients access to UNIX applications.See also IDREF="FM99174""Client."RENDERAS="SECT1"Unknown objectIDXID="w2487"BOOK="_idx" COLLECTION="nw41" TIDREF="i4661"A leaf object that represents an NDS object that has been corrupted and can't be identified as belonging to any of the other object classes.After migrating  to NetWare 4 from NetWare 2 or 3, bindery objects might appear as Unknown objects.See also IDREF="FM13600""Object."RENDERAS="SECT1"UnloadingThe process of unlinking NLM programs from the NetWare operating system.See IDREF="FM72737""Loading and unloading."RENDERAS="SECT1"ID="FM21704"UpgradeIDXID="w2488"BOOK="_idx" COLLECTION="nw41" TIDREF="i4683"The process of convertingIDXID="w2489"BOOK="_idx" COLLECTION="nw41" TIDREF="i4683"
 your network to NetWare 4 from any earlier version of NetWare or from another network operating system.You can upgrade to NetWare 3 or NetWare 4 from the following network operating systems:MARK=BULLETNetWare 2PAGENUM=367 ID="BP368"NetWare 3IBM PCLP 1.3 (Extended Services)IBM LAN Server 1.0IBM LAN Server 1.1IBM LAN Server 1.2IBM LAN Server 1.3Microsoft LAN Manager 2.0For descriptions of each upgrade method, see "BOOK="upmigenu" COLLECTION="nw41"Upgrade Options," in Upgrade .RENDERAS="SECT2"MigrationThe NetWare Migration utility converts servers from NetWare 2 or NetWare 3, or from another network operating system, to NetWare 4 using either of two methods:MARK=BULLETIDXID="w2490"BOOK="_idx" COLLECTION="nw41" TIDREF="i2461"Across-the-wire. You transfer network information from a NetWare 2 or NetWare 3 server or other network operating system to an existing NetWare 4.1 server on the same network.IDXID="w2491"BOOK="_idx" COLLECTION="nw41" TIDREF="i2461"Same-server. You change your NetWare 2 or NetWare 3 server to a NetWare 4.1 server.RENDERAS="SECT2"IDXID="w2492"BOOK="_idx" COLLECTION="nw41" TIDREF="i1896"
In-Place UpgradeThe In-Place Upgrade utility allows you to upgrade a NetWare 2.1x or 2.2 server to NetWare 3.11 using SERVER.EXE. You can then continue the upgrade to NetWare 4. The In-Place Upgrade includes three parts:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The file system is upgraded.PAGENUM=368 ID="BP369"Upgrade occurs in the following sequential phases::COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PhaseCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"System AnalysisCOLNAME=2 ROTATE="0" MOREROWS="0"Inventories each disk and volume. Ensures that the system has enough memory and free disk space to complete the upgrade.COLNAME=1 ROTATE="0" MOREROWS="0"Disk AnalysisCOLNAME=2 ROTATE="0" MOREROWS="0"Analyzes each disk. An image of the new NetWare 3.11 disk is built and stored in memory. This phase won't damage the existing NetWare 2.1x file system.COLNAME=1 ROTATE="0" MOREROWS="0"Disk ModificationCOLNAME=2 ROTATE="0" MOREROWS="0"Writes the new NetWare 3.11 file system to disk, destroying the NetWare 2.1x file system. A hardware failure during this phase will result in an irrecoverable loss of data on the server.COLNAME=1 ROTATE="0" MOREROWS="0"BinderyCOLNAME=2 ROTATE="0" MOREROWS="0"Updates bindery objects, properties, and values such as user accounts and passwords. Random user passwords are assigned if requested.The new operating system is installed.At this point, you have a NetWare 3.11 file system. The new operating system and utilities have not been installed in the SYSTEM and PUBLIC directories on volume SYS: yet.Complete the upgrade to NetWare 4.1 by installing NetWare 4.1. (See "BOOK="upmigenu" COLLECTION="nw41"Upgrade Using In-Place Upgrade," in Upgrade.)RENDERAS="SECT1"UPS(Uninterruptible power supply) A backup power unit that supplies uninterrupted power if a commercial power outage occurs.See IDREF="FM99587""Uninterruptible power supply."PAGENUM=369 ID="BP370"RENDERAS="SECT1"ID="FM71926"UPS monitoringIDXID="w2493"BOOK="_idx" COLLECTION="nw41" TIDREF="i4696"The process a NetWare server uses to ensure that an attached UPS is functioning properly.A Novell-certified UPS is attached to a server to provide backup power. (You can also attach a UPS to workstations without installing UPS monitoring hardware on the stations.)When a power failure occurs, NetWare notifies users. After a timeout specified in SERVER.CFG, the server logs out remaining users, closes open files, and shuts itself down.If you install a Novell-approved UPS, you must also install or set a board in the server to monitor the UPS. (If you have a server with an IBM PS/2-style mouse port, the UPS can be monitored through the mouse port.)A board can function as a UPS monitor board if the board's mounting bracket has a stereo phone jack. The following boards can be used:MARK=BULLETAn AT-compatible HBA or third-party equivalentStandalone UPS monitor boardSee also IDREF="FM99587""Uninterruptible power supply."RENDERAS="SECT1"ID="FM12693"User Datagram ProtocolIDXID="w2494"BOOK="_idx" COLLECTION="nw41" TIDREF="i4706"(UDP) A transport protocol in the TCP/IP suite of protocols. UDP is not connection oriented and does not acknowledge data receipt. Because UDP doesn't establish and deestablish connections or control data flow, it performs faster than TCP. However, it is less reliable.RENDERAS="SECT1"User login scriptIDXID="w2495"BOOK="_idx" COLLECTION="nw41" TIDREF="i4709"IDXID="w2496"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"A type of login script that sets environments specific to a user. Use user login scripts to contain items that can't be included in system or profile login scripts.User login scripts are optional; if used, they execute after system and profile login scripts.See also IDREF="FM23712""Login scripts."PAGENUM=370 ID="BP371"RENDERAS="SECT1"ID="FM20517"User objectIDXID="w2497"BOOK="_idx" COLLECTION="nw41" TIDREF="i4717"A leaf object in NDS that represents a person with access to the network. A User object stores information about the person it represents.The following items are important to managing User objects:RENDERAS="SECT2"Login NamesThe login name is the name the user logs in with. A login name is mandatory when creating a User object.You can have a login name of up to 64 characters; however, for efficiency, use one of the following conventions when creating login names:MARK=BULLETGiven name (for example, user JANE)Surname (for example, user DOE)Initials and surname (for example, user JDOE)Do not use special characters or control characters in a login name. Spaces can be used but aren't recommended.When you use a login name with spaces in a login script, enclose the entire login name within quotation marks. (To avoid this, use underscores in the login name rather than spaces.)RENDERAS="SECT2"Group MembershipYou can assign a user to Group objects. When added to a group, a user inherits the rights assigned to that group.RENDERAS="SECT2"Home DirectoriesA home directory serves as a user's personal workspace.If you create home directories, plan a parent directory (such as SYS:HOME or SYS:USERS) for them. Or, for a large system, set aside a separate volume for users' home directories.PAGENUM=371 ID="BP372"To simplify system administration, make each user's home directory name the same as that user's login name (for example, SYS:USER\JANE or SYS:HOME\RDSMITH).If you grant all trustee rights to users in their own directories, users can control access to files in their directories. (Users who have the Supervisor directory right to the directory above home directories still have access.)This allows users to work on projects in their home directory and prevents others from accessing their work.Once the work is completed, the files can be copied to a work or project directory (group work space) where other users can access the information.RENDERAS="SECT2"Trustee RightsIf users need to access specific directories and files (other than those assigned by the system), you must grant users trustee rights to these directories.RENDERAS="SECT2"Security Equal To PropertyThe Security Equal To property allows users to exercise rights equivalent to those of another user.Assigning the Security Equal To property is convenient when you need to give a user access to the same information that another user already has access to.In networks that contain confidential data for selected users, make sure that you don't inadvertently give a user access to restricted information.Use particular caution when making a user security equal to a user who has the Supervisor object right.You can add the Security Equal To property only to User objects. However, every object (including User objects) is automatically security equal to all container objects directly above it. This cannot be altered or modified.PAGENUM=372 ID="BP373"RENDERAS="SECT2"User Login ScriptsThese configurable batch files customize the network environment for users by initializing environment variables, mapping drives, and executing other commands.Up to three login scripts are used at login, executed in the following order:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The login script of the user's immediate containerThe login script in a profile object specified for that userThe user's individual login scriptWhere there are conflicting or contradicting commands in login scripts, the commands in the most recently executed login script are effective.If no login scripts exist, a default login script executes and maps a drive to NetWare utilities.RENDERAS="SECT2"Print Job ConfigurationsEach user can use printing defaults, or you can create print job configurations for a container or User object.RENDERAS="SECT2"Account ManagementAny user who has the Supervisor object right to another User object manages that User object and can modify information about that user.Users who don't have the Supervisor object right can be granted rights to other User objects to fulfill specific responsibilities. For example, the network supervisor may want only the phone book manager to be granted rights to each user's phone number property.RENDERAS="SECT2"User Account RestrictionsEvery user account can be restricted to prevent unauthorized users from accessing the network. Some restrictions can even disable the account so that no one can log in as that user.PAGENUM=373 ID="BP374"The network supervisor can restrict logins in the following ways:MARK=BULLETAccount balance restrictions. If you install Accounting to monitor or limit network resources, you can assign account balances for users and specify credit limits. When the balance is depleted, the account is disabled.If accounting hasn't been installed, this option isn't available.Expiration restrictions. You can specify an expiration date for a user account. For example, set the account to expire at 12:01 a.m. the following day.Any attempt to log in after the account expires disables the account. (Default: no expiration.)Password restrictions. You can require passwords.If you require passwords, you can also specify the minimum length (default: 5 characters), how often the password must be changed (default: 40 days), whether the user can change the password (default: Yes), and whether the password must be unique (default: No).For a password to be unique, it must be different from the previous eight passwords used by the account.You can also specify the number of times a user can log in with an expired password (grace logins, default: 6) or the number of incorrect login attempts allowed (default: 6 times).When either number is exceeded, the account is disabled.See also IDREF="FM52521""Security."Disk space restrictions. You can set a limit to the maximum number of blocks available to a user.Connection restrictions. You can limit the number of workstations (connections) from which a user can be logged in at any one time.Time restrictions.PAGENUM=374 ID="BP375" You can restrict the hours and days during which users can log in. Times are specified in half-hour blocks. You can assign all users the same times, or you can restrict users individually (default: no time restriction).Network address restrictions. You can restrict the physical locations that a user can log in from by specifying the network and node addresses of the workstation the user can log in from.Workstation restrictions can't be set with system default restrictions; they must be assigned individually. If no network address restrictions are listed, no station restrictions are in effect.Related utilities: "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.See also IDREF="FM43837""Accounting"; IDREF="FM36715""Group object"; IDREF="FM23712""Login scripts"; IDREF="FM87658""Security Equal To"; "BOOK="superenu" COLLECTION="nw41"Creating Leaf Objects," "BOOK="superenu" COLLECTION="nw41"Managing Groups of User Objects," and "BOOK="superenu" COLLECTION="nw41"Cautions When Deleting User Objects" in Chapter 1 of Supervising the Network.RENDERAS="SECT1"User object ADMINIDXID="w2498"BOOK="_idx" COLLECTION="nw41" TIDREF="i4712"A User object, created automatically during NetWare 4.1 installation, that has rights to create and manage objects.When you first create the Directory tree, ADMIN is given a trustee assignment to the root object. This trustee assignment includes the Supervisor object right, which means that ADMIN has rights to create and manage all objects in the tree.As you create other User objects in the Directory tree, you can give them the Supervisor object right to create and manage other container objects and all their leaf objects. Control of the network is as dispersed or centralized as you make it.After you assign the Supervisor object right to other User objects, you can rename ADMIN or delete it.However, don't delete ADMIN until you've created other User objects and granted one the Supervisor object right to the root object. Otherwise, no one has full access to the Directory tree.PAGENUM=375 ID="BP376"Unlike SUPERVISOR in earlier versions of NetWare, ADMIN doesn't have any special significance. It is just the first User object created and therefore must have the ability to create other objects.See also IDREF="FM20517""User object."RENDERAS="SECT1"User templateIDXID="w2499"BOOK="_idx" COLLECTION="nw41" TIDREF="i4721"A file containing default information you can apply to new User objects to give them default property values. This helps if you are creating many users who need the same property values.You create user templates in Organization or Organizational Unit objects.When you create a User object, you can specify that you want to use a user template. In this case, the property values entered in the user template for that container (or the container above, if no user template exists in the current container) are copied into the new User object as it is created.The user template saves you from re-entering information---such as a fax number, login time restrictions, addresses, password restrictions, or language---that is common to every User object in a container.When you create a user template in a container, you can copy information from the parent container's user template.For example, if you create a template in SALES.NOVELL, you are asked whether you want to start by copying the user template (if one exists) from NOVELL.A user template is actually a User object named USER_TEMPLATE. You enter information in this object just as you do any other User object, although not all properties of a User object can be copied from a user template.Information assigned to a new User object from a template can be changed after the User object is created. However, you can't log in as USER_TEMPLATE, grant rights with a user template, apply a user template to existing User objects, nor apply user template updates to User objects created with that template.PAGENUM=376 ID="BP377"RENDERAS="SECT1"ID="FM89838"UtilitiesIDXID="w2500"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"Programs that add functionality to the NetWare operating system. NetWare 4 utilities support MS Windows, OS/2, and DOS environments. (See 
BOOK="utlrfenu" COLLECTION="nw41"Utilities Reference.)RENDERAS="SECT2"IDXID="w2501"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"IDXID="w2502"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
Server Utilities and NLM ProgramsIDXID="w2503"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"NetWare server utilities and NLM programs run at the server console of a NetWare 4 server or a NetWare for OS/2 server.Use the server utility commands at the server console prompt toMARK=BULLETChange memory allocationsMonitor how the server is being usedControl workstations' use of the resources on the serverThe server NLM programs link disk drivers, LAN drivers, name space modules, management applications, etc., with the server's operating system.RENDERAS="SECT2"IDXID="w2504"BOOK="_idx" COLLECTION="nw41" TIDREF="i4837"IDXID="w2505"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
Workstation UtilitiesNetWare workstation utilities can be run from a DOS, MS Windows, or OS/2 workstation.Graphical utilities, new under NetWare 4, allow network supervisors to manage the network through MS Windows 3.1 or OS/2 Presentation Manager 2.0.Text utilities for DOS and OS/2 support both bindery and NDS.See also IDREF="FM50073""NetWare user tools"; IDREF="FM68484""NetWare Loadable Module."PAGENUM=377 ID="BP378"VRENDERAS="SECT1"ID="FM44520"Value-added processIDXID="w2506"BOOK="_idx" COLLECTION="nw41" TIDREF="i4744"(VAP) A process that ties enhanced operating system features to a NetWare 2 operating system without interfering with the network's normal operation.VAPs run on top of the operating system in much the same way a word processing or spreadsheet application runs on top of DOS.NLM programs provide this type of enhancement for NetWare 3 and NetWare 4. (See IDREF="FM68484""NetWare Loadable Module.")RENDERAS="SECT1"Value-added serverIDXID="w2507"BOOK="_idx" COLLECTION="nw41" TIDREF="i4746"IDXID="w2508"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"A separate, specialized, dedicated computer (such as a print server or a database server) that fulfills a specific function for network users.RENDERAS="SECT1"VAPA process that ties enhanced operating system features to a NetWare 2 operating system.SeeIDREF="FM44520""Value-added process."RENDERAS="SECT1"VDTA table that keeps track of volume segment information.See IDREF="FM89508""Volume Definition Table."RENDERAS="SECT1"ID="FM28012"Virtual Loadable ModuleIDXID="w2509"BOOK="_idx" COLLECTION="nw41" TIDREF="i4770"(VLM) A modular executable program that runs at each DOS workstation and enables communication with the NetWare server.A VLM file has a .VLM filename extension. For example, the IPX VLM file is IPXNCP.VLM.PAGENUM=378 ID="BP379"The NetWare DOS Requester is composed of several VLM programs. These VLM programs replace, and provide backward compatibility with, NetWare shells (NETX) used in previous NetWare versions.There are two types of VLM programs: child VLM and multiplexor VLM programs.RENDERAS="SECT2"IDXID="w2510"BOOK="_idx" COLLECTION="nw41" TIDREF="i628"IDXID="w2511"BOOK="_idx" COLLECTION="nw41" TIDREF="i4770"
Child VLM ProgramsChild VLM programs handle a particular implementation of a logical grouping of functionality. For example, each NetWare server type has its own child VLM:MARK=BULLETNDS.VLM for NetWare 4 serversBIND.VLM for bindery-based servers (prior to NetWare 4)PNW.VLM for NetWare desktop-based serversVarious implementations of transport protocols also have their individual child VLM programs. For example, IPXNCP.VLM handles IPX services, and TCPNCP.VLM handles TCP functions.RENDERAS="SECT2"IDXID="w2512"BOOK="_idx" COLLECTION="nw41" TIDREF="i2566"IDXID="w2513"BOOK="_idx" COLLECTION="nw41" TIDREF="i4770"
Multiplexor VLM ProgramsA multiplexor is a VLM that routes calls to the proper child VLM. NetWare Requester multiplexors can be considered parent VLM programs, ensuring that requests to child VLM programs reach the appropriate VLM module.See also IDREF="FM21900""NetWare DOS Requester."RENDERAS="SECT1"ID="FM56941"VLMA modular executable program that runs at each DOS workstation and enables communication with the NetWare server.See IDREF="FM28012""Virtual Loadable Module."PAGENUM=379 ID="BP380"RENDERAS="SECT1"ID="FM96914"VolumeIDXID="w2514"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"A physical amount of hard disk storage space, fixed in size. A NetWare volume is the highest level in the NetWare file system (on the same level as a DOS root directory).In NDS, each volume is also a Volume object in the Directory.When you create a volume with the INSTALL utility, INSTALL puts a Volume object in the same context as the NetWare server within the Directory tree. By default, INSTALL names the Volume object servername_volumeobject.You can change the context of Volume objects with NETADMIN or NetWare Administrator.If you rename a volume, change the volume name on the server using the INSTALL utility, and change the volume object's name in the Directory using NETADMIN or NetWare Administrator.You can create a new volume on any hard disk that has a NetWare 4 partition. A NetWare 4 server supports up to 64 volumes.NetWare volumes are subdivided in two ways:MARK=BULLETIDXID="w2515"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"Logically. Volumes are divided into directories by network supervisors and users who have the appropriate rights.IDXID="w2516"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"Physically. Volumes are divided into volume segments; different segments of a volume can be stored on one or more hard disks.A single hard disk can contain up to eight volume segments belonging to one or more volumes, and each volume can consist of up to 32 volume segments.By placing segments of the same volume on multiple hard disks, different parts of the same volume can be read from or written to simultaneously, speeding up disk input/output.However, when you spread segments of a volume over several disks, protect the volumes against disk failure by mirroring; otherwise, if a single disk fails, one or more entire volumes shut down.PAGENUM=380 ID="BP381"A volume's size can be increased by adding another hard disk to the NetWare server, by setting up a NetWare partition on the disk, or by adding the new NetWare partition to the existing volume as one or more new volume segments.Volume size can be increased, in many cases, while the server is running and the volume still mounted.IDXID="w2517"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"
The first network volume is named SYS:. Additional volumes can be defined with INSTALL and are assigned volume names between 2 and 15 characters.Several NetWare utilities---including FILER, MAP, and VOLINFO---list a NetWare server's volume names.In addition, the DOS DIR command lists the volume name for the specified network drive (for example, "Volume in drive F: is SYS:").This corresponds to the DOS or OS/2 volume label shown by the DIR command for local disks (floppy disks or workstation hard disks). A local disk can be given a volume label during formatting or with the DOS or OS/2 LABEL command.When a volume is used as part of a directory path, either in NetWare documentation or on the screen (for example, when running the MAP command), the volume name is followed by a colon (:), as in SYS:PUBLIC.IDXID="w2518"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"
When you boot the NetWare server, each volume is "mounted," meaning thatMARK=BULLETThe volume becomes visible to the operating systemThe volume's FAT is loaded into memoryEach file block of data takes up one entry in the FAT.Because of this, volumes with a smaller block size require more server memory to mount and manage.However, if most of your files are small, a large block size wastes disk space.The volume's DET is loaded into memoryPAGENUM=381 ID="BP382"If a volume fails to mount, it might be because you have run out of RAM. This is because the FAT takes up cache buffers.Related utility: "BOOK="utlrfenu" COLLECTION="nw41"INSTALL" in Utilities Reference.See also IDREF="FM22177""File system"; IDREF="FM89508""Volume Definition Table."RENDERAS="SECT1"ID="FM89508"IDXID="w2519"BOOK="_idx" COLLECTION="nw41" TIDREF="i4782"
Volume Definition Table(VDT) A table that keeps track of volume segment information such as volume name, volume size, and where volume segments are located on various network hard disks.Each NetWare volume contains a VDT in its NetWare partition.See also IDREF="FM96914""Volume."RENDERAS="SECT1"ID="FM53478"Volume objectIDXID="w2520"BOOK="_idx" COLLECTION="nw41" TIDREF="i4788"A leaf object that represents a physical volume on the network.In the Volume object's properties, you can store information about which NetWare server the physical volume is located on and the volume name recorded when the volume was initialized at the server (for example, SYS:).You can also store information such as the volume's owner, space use restrictions for users, or a description of its use.You can also view statistical information on disk space availability, block size, directory entries, name space support, etc.See also IDREF="FM13600""Object"; IDREF="FM96914""Volume"; "BOOK="superenu" COLLECTION="nw41"Creating Leaf Objects" in Chapter 1 of Supervising the Network.RENDERAS="SECT1"Volume segmentsIDXID="w2521"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"A physical division of a volume. Different segments of a volume can be stored on one or more hard disks, allowing you to create large volumes. PAGENUM=382 ID="BP383"A single hard disk can contain up to eight volume segments belonging to one or more volumes, and each volume can span up to 32 segments.By placing segments of the same volume on multiple hard disks, different parts of the same volume can be read from or written to simultaneously, thus speeding up disk I/O. You can add segments to a volume (with INSTALL.NLM), but removing a segment from a volume can destroy the volume.NetWare maintains a VDT that maps the segments on the hard disk to the volume.See also IDREF="FM96914""Volume."PAGENUM=383 ID="BP384"WRENDERAS="SECT1"Wait stateIDXID="w2522"BOOK="_idx" COLLECTION="nw41" TIDREF="i4803"A period of time when the processor does nothing; it simply waits. A wait state is used to synchronize circuitry or devices operating at different speeds.For example, wait states used in memory access slow down the CPU so all components seem to be running at the same speed.RENDERAS="SECT1"Wait timeIDXID="w2523"BOOK="_idx" COLLECTION="nw41" TIDREF="i4804"IDXID="w2524"BOOK="_idx" COLLECTION="nw41" TIDREF="i4647"In a NetWare UPS system, the number of seconds the UPS waits before signaling to the NetWare server that the normal power supply is off.The NetWare server then alerts attached workstations to log out.See also IDREF="FM99587""Uninterruptible power supply."RENDERAS="SECT1"ID="FM54190"WAN(Wide area network) A network that communicates over a long distance, such as across a city or around the world.See IDREF="FM30129""Wide area network."RENDERAS="SECT1"ID="FM64813"WatchdogIDXID="w2525"BOOK="_idx" COLLECTION="nw41" TIDREF="i4820"Packets used to make sure workstations are still connected to the NetWare server.All settings are determined by the SET parameters. You can set parameters so that if the server hasn't received a packet from a station in a certain time, a watchdog packet is sent to the station. If the station doesn't respond within a certain time, another watchdog packet is sent.PAGENUM=384 ID="BP385"If the station still doesn't respond to a certain number of watchdog packets, the server assumes that the station is no longer connected and clears the station's connection.The time period before the first watchdog packet, the time period between watchdog packets, and the number of watchdog packets is configurable using the SET utility. Related Utility: "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.See also IDREF="FM51228""Packet receive buffer."RENDERAS="SECT1"ID="FM30129"Wide area networkIDXID="w2526"BOOK="_idx" COLLECTION="nw41" TIDREF="i4824"(WAN) A network that communicates over a long distance, such as across a city or around the world.A local area network becomes a part of a wide area network when a link is established (using modems, remote routers, phone lines, satellites, or a microwave connection) to a mainframe system, a public data network, or another local area network.See also IDREF="FM88066""Local area network."RENDERAS="SECT1"ID="FM99199"ID="FM70532"WorkstationIDXID="w2527"BOOK="_idx" COLLECTION="nw41" TIDREF="i4837"A personal computer connected to a NetWare network and used to perform tasks through application programs or utilities. Also referred to as a client or shortened to station.See also IDREF="FM99174""Client."RENDERAS="SECT1"Write rightIDXID="w2528"BOOK="_idx" COLLECTION="nw41" TIDREF="i4854"A file system right that grants the right to open and write to files.Also, a property right that grants the right to add, change, or remove any values of the property.See also IDREF="FM74455""Rights."PAGENUM=385 ID="BP386"XRENDERAS="SECT1"IDXID="w2529"BOOK="_idx" COLLECTION="nw41" TIDREF="i4864"IDXID="w2530"BOOK="_idx" COLLECTION="nw41" TIDREF="i4864"
Xerox Network Systems(XNS) Novell IPX is a variation on XNS. One major difference between IPX and XNS is that they do not use the same Ethernet encapsulation format. A second difference is that IPX uses Novell's proprietary Service Advertisement Protocol (SAP).See also IDREF="FM16854""IPX."RENDERAS="SECT1"ID="FM46206"XON/XOFFA handshake protocol that prevents a sending system from transmitting data faster than a receiving system can accept it.See also IDREF="FM98858""Handshaking"; IDREF="FM44412""Serial communication."RENDERAS="SECT1"XNS(XNS) Novell IPX is a variation on XNS.See BOOK="utlrfenu" COLLECTION="nw41"Utilities.PAGENUM=386 ID="BP387"ZRENDERAS="SECT1"ID="FM76792"ZonesIDXID="w2531"BOOK="_idx" COLLECTION="nw41" TIDREF="i4878"IDXID="w2532"BOOK="_idx" COLLECTION="nw41" TIDREF="i254"Arbitrary groups of nodes on an AppleTalk internetwork. Zones provide divisions in a large internetwork.Each node belongs to only one zone at a time. The zone that a node belongs to is determined automatically when that node connects to the network.Zones are referred to by names. Each zone name can be up to 32 characters. (In a network without routers, only one zone exists. The zone name is invisible to users.)Zone names are converted to addresses on the internetwork by the Name Binding protocol. The names are exchanged by the Zone Information protocol.Zone names and addresses are maintained in a zone information table within each router. A NetWare server can act as a router for AppleTalk nodes connected to it.See also IDREF="FM41940""AppleTalk protocols."