#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'Supervising the NetworkSupervising the NetworkNovell, 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=13 ID="BP1"How to Use This ManualSupervising the Network has two purposes: to help you set up your network after completing the installation procedure, and to help you manage your network after you have installed or upgraded servers to NetWare® 4.1.This manual is to be used by network supervisors responsible for maintaining all or part of a NetWare 4.1 network.The checklist in the following section explains the process of planning and setting up a network, and refers you to the manual containing the information and instructions you need to complete that step in the process.RENDERAS="SECT1"Checklist for Installing and Setting Up Your NetworkTo set up your NetWare 4.1 network, use the manuals in your NetWare 4.1 set in the order shown in the following checklist. (Chapter-only references refer to chapters within this manual.)MARK=CHECKBOXPlan the network.BOOK="newftenu" COLLECTION="nw41"New Features gives you an overview of NetWare 4.1 features and the planning information you need.Install or upgrade servers to NetWare 4.1. See BOOK="instlenu" COLLECTION="nw41"Installation or BOOK="upmigenu" COLLECTION="nw41"Upgrade for instructions.Set up NetWare Directory ServicesTM (NDS) objects, such as organizations, groups, and user accounts. IDREF="FM93061"Chapter 1, "Managing NetWare Directory Services Objects," gives you information and procedures.Set up your file system and install network applications. IDREF="FM37004"Chapter 2, "Managing Directories, Files, and Applications," contains planning guidelines and instructions for creating directories and installing applications.PAGENUM=14 ID="BP2"Plan and create login scripts. IDREF="FM34948"Chapter 3, "Creating Login Scripts," explains the types of login scripts you can use and gives you instructions for setting them up.Set up printing. See BOOK="printenu" COLLECTION="nw41"Print Services for information and instructions.Set up workstations. See 
BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User Guide or 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide for information and intructions.For a list of the command format conventions used in Novell® documentation, see Chapter 1, "BOOK="utlrfenu" COLLECTION="nw41"Command Syntax," of Utilities Reference.RENDERAS="SECT1"Managing Your NetworkAfter setting up your network, use this manual to help you keep it updated and running efficiently. Use this manual to help you perform such routine tasks as managing your NetWare Directory database and its associated objects, maintaining your netware file system, and setting up servers and keeping your network running efficiently. You can also use it as a reference for backing up and restoring network data, using optical storage devices to increase and manage your available disk space, and using the new NetWare DynaText* online documentation.To get an overview of how this manual can help you manage your network, review the tasks listed in the Table of Contents.The printed version of this manual is divided into two volumes. Volume I contains the Table of Contents and Chapters 1 through 6. Volume II consists of Chapters 7 through 9, Appendixes A through C, and the Index.LABEL="1"PAGENUM=15 ID="BP3"ID="FM93061"Managing NetWare Directory Services ObjectsThis chapter helps you start managing your network after installing the NetWare® 4.1 operating system.The first section in this chapter explains what objects exist in the Directory tree immediately after you have installed NetWare 4.1 or upgraded to NetWare 4.1.The rest of the sections explain basic "getting started" tasks, such asMARK=BULLETInstalling a workstation and logging in to the network for the first timeCreating and managing objects, such as Users, Groups, Organizational Roles, and ProfilesSearching for objectsMoving, deleting, and renaming objectsChanging properties of objectsYou can use either the NetWare Administrator graphical utility or the NETADMIN text utility to do those tasks. Both methods are explained. In some cases, a third method is available, which is also explained.PAGENUM=16 ID="BP4"RENDERAS="SECT1"IDXID="w7518"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"
Default Objects and Rights for NetWare 4.1IDREF="FM37383"Table 1-1 explains what objects exist in a Directory tree immediately after you install NetWare 4.1 or upgrade to NetWare 4.1, and what default rights those objects have.LABEL="1-1" PGWIDE=1 TOCENTRY="1"ID="FM37383" Default Objects and Rights in a Directory TreeCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="11*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Default Objects after NetWare 4.1 InstallationCOLNAME=2 ROTATE="0" MOREROWS="0"Default Objects after NetWare 4.1 UpgradeCOLNAME=3 ROTATE="0" MOREROWS="0"Default Rights after NetWare 4.1 Installation or UpgradeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare IDXID="w7519"BOOK="_idx" COLLECTION="nw41" TIDREF="i4055"
Server object for the server on which NetWare 4.1 was installedCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare Server object for the server you upgraded to NetWare 4.1COLNAME=3 ROTATE="0" MOREROWS="0"User object ADMIN has the Supervisor object right to the NetWare Server object, which means that User object ADMIN also has the Supervisor right to the root directory of the file system of all volumes attached to the server.COLNAME=1 ROTATE="0" MOREROWS="0"Volume object SYSCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7520"BOOK="_idx" COLLECTION="nw41" TIDREF="i3855"
Volume object SYS for volume SYS: on the server you upgradedCOLNAME=3 ROTATE="0" MOREROWS="0"The container object for Volume object SYS is granted Read and File Scan rights to the volume's SYS:PUBLIC directory. This means that when users are created, they can access utilities located in the SYS:PUBLIC directory.COLNAME=1 ROTATE="0" MOREROWS="0"Volume objects for any other volumes on the server's disk besides SYS: that you created during installationCOLNAME=2 ROTATE="0" MOREROWS="0"Volume objects for every other volume besides SYS: on the server you upgradedCOLNAME=3 ROTATE="0" MOREROWS="0"[Root] is granted the Read property right to the Host Server Name and Host Resource properties on all Volume objects. This means that all objects in the Directory tree have access to the physical volume name and the physical server name.User object ADMIN has the Supervisor right to the root directory of the file systems on these volumes.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7521"BOOK="_idx" COLLECTION="nw41" TIDREF="i118"
User object ADMINWhen IDXID="w7522"BOOK="_idx" COLLECTION="nw41" TIDREF="i3857"
User object 
ADMIN is first created, by default it is placed in the Organization container object. This may not be the same context in which you installed the server.COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7523"BOOK="_idx" COLLECTION="nw41" TIDREF="i118"
User object ADMINWhen User object ADMIN is first created, by default it is placed in the Organization container object. This may not be the same context in which you installed the server.All other objects that were on the server's bindery are placed in the same container as the server that was upgraded.COLNAME=3 ROTATE="0" MOREROWS="0"User object ADMIN receives a trustee assignment of Supervisor object right to the Root object of the Directory tree. This means that User object ADMIN has all rights to all the objects in the Directory tree.User object ADMIN also has the Supervisor object right to the NetWare Server object, which means that User object ADMIN has the Supervisor right to the root directory of the file system of all volumes attached to the server.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"[Public] has Browse object right at the root. IDXID="w7524"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"
This means that users who are attached to a NetWare Directory ServicesTM server, but who are not authenticated, can browse the tree.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"The network supervisor can remove [Public] browse rights so that users cannot do this.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"IDXID="w7525"BOOK="_idx" COLLECTION="nw41" TIDREF="i3857"
Users IDXID="w7526"BOOK="_idx" COLLECTION="nw41" TIDREF="i4710"
are granted all rights to their home directories, which are migrated when you migrate User objects.PAGENUM=17 ID="BP5"The upgrade utility converts most existing bindery objects to NetWare Directory Services (NDS) objects. For more information, see 
BOOK="upmigenu" COLLECTION="nw41"Upgrade.PAGENUM=18 ID="BP6"IDXID="w7527"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"IDREF="FM76561"Figure 1-1 shows objects in a 
Directory tree after you have upgraded one server (DSERVER) and installed a NetWare 4.1 server (TSERVER).LABEL="1-1" FLOAT="0"IDXID="w7528"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"ID="FM76561"Example of a New Directory TreeFILEREF="n40su32a.tif"DSERVER was upgraded from NetWare 3.11 and placed in the context DEVELOPMENT.MEDTEC (that is, in Organizational Unit DEVELOPMENT, which is in Organization MEDTEC).The volumes and users on the NetWare 3.11 server (DSERVER_SYS, DSERVER_APPS, DSERVER_PROJECTS, JODY, and PAUL) were converted into Directory objects when the server was upgraded to NetWare 4.1.PAGENUM=19 ID="BP7"TSERVER is a newly installed NetWare 4.1 server that was placed in the context TEST.MEDTEC (that is, in Organizational Unit TEST, which is in Organization MEDTEC). Volume object TSERVER_SYS was created by default, and Volume object TSERVER_PROJECTS was defined by the network supervisor during installation.RENDERAS="SECT1"IDXID="w7529"BOOK="_idx" COLLECTION="nw41" TIDREF="i120"
Setting Up Administration UtilitiesIDXID="w7530"BOOK="_idx" COLLECTION="nw41" TIDREF="i118"
The first time the network supervisor logs in, it must be as IDXID="w7531"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
User object ADMIN. This is the only object that has rights to create and manage objects immediately after installation or upgrade.However, before you can log in, you must first use the instructions in this section to install a single client workstation, from which you can run either the NetWare Administrator or NETADMIN utility to start creating objects on your network.You can install and customize other workstations later, using the appropriate client manual (
BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User Guide or 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide).If you have installed the NetWare server from CD-ROM, you also need to create installation diskettes for NetWare clients (DOS, MS Windows, and OS/2) before you can install a workstation. Then proceed with the workstation operation.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Create workstation installation diskettes from CD-ROMCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM51628""Creating Client Install Diskettes from CD-ROM" on page 20COLNAME=1 ROTATE="0" MOREROWS="0"Install an MS Windows workstationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM68342""Installing an MS Windows Workstation and Starting NetWare Administrator" on page 23COLNAME=1 ROTATE="0" MOREROWS="0"Install an OS/2 workstationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM57581""Installing an OS/2 Workstation and Starting NetWare Administrator" on page 26COLNAME=1 ROTATE="0" MOREROWS="0"Install a DOS workstationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM81892""Installing a DOS Workstation and Starting NETADMIN" on page 29PAGENUM=20 ID="BP8"RENDERAS="SECT2"ID="FM51628"IDXID="w7532"BOOK="_idx" COLLECTION="nw41" TIDREF="i646"
Creating Client Install Diskettes from CD-ROMIDXID="w7533"BOOK="_idx" COLLECTION="nw41" TIDREF="i1137"
You can install the IDXID="w7534"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"
CD-ROM either as a 
DOS volume or as a network device.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"For DOS or MS Windows, format five high-density diskettes using the DOS FORMAT command. For 
OS/2, format seven diskettes.PERFORMANCE="REQUIRED"(DOS volume only) Install the C
D-ROM drive as a DOS device according to manufacturer's instructions.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Go to the drive corresponding to the C
D-ROM.PERFORMANCE="REQUIRED"Change to the CLIENT directory.PERFORMANCE="REQUIRED"Skip to Step 4.PERFORMANCE="REQUIRED"(Network device only) Map a drive to a server directory containing th
e NetWare 4.1 files.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Change to the SYS:PUBLIC\CLIENT directory.PERFORMANCE="REQUIRED"Continue with Step 4.PERFORMANCE="REQUIRED"Change to one of the following subdirectories.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If creating diskettes forCOLNAME=2 ROTATE="0" MOREROWS="0"Go to this subdirectoryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DOSCOLNAME=2 ROTATE="0" MOREROWS="0"DOSWINCOLNAME=1 ROTATE="0" MOREROWS="0"MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"DOSWINCOLNAME=1 ROTATE="0" MOREROWS="0"OS/2COLNAME=2 ROTATE="0" MOREROWS="0"OS2PAGENUM=21 ID="BP9"PERFORMANCE="REQUIRED"If you are installing a language version other than English (the default language), set the "nwlanguage" environment variable by typing the following at the 
workstation command line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NWLANGUAGE=language MOREINFO="NONE"<Enter>Replace 
language with the appropriate language found in the NLS subdirectory under either CLIENT\OS2 or CLIENT\DOSWIN
.PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAKEDISK drive_letter: MOREINFO="NONE"<Enter>Replace 
drive_letter with the letter representing the drive you will insert the blank formatted diskettes into. For example, type either
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAKEDISK A: MOREINFO="NONE"<Enter>or
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAKEDISK B: MOREINFO="NONE"<Enter>The MAKEDISK utility copies the client installation files from the C
D-ROM directory to the diskettes. It prompts you to insert new blank formatted diskettes.
PAGENUM=22 ID="BP10"PERFORMANCE="REQUIRED"Attach a label to each diskette
, and 
then label the diskettes as described in the following table.LABEL="1-2" PGWIDE=0 TOCENTRY="1" Client Diskette LabelsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="3*"COLNAME=2 COLWIDTH="14*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette #COLNAME=2 ROTATE="0" MOREROWS="0"Label for DOS/MS WindowsCOLNAME=3 ROTATE="0" MOREROWS="0"Label for OS/2VALIGN="TOP"COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKWSOS2_1COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKWSOS2_2COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 3COLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKWSOS2_3COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"4COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 4COLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKOSUTIL1COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"5COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN driversCOLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKOS2DOC_XCLASS=DISK1=EnglishCLASS=DISK2=FrenchCLASS=DISK3=GermanCLASS=DISK4=ItalianCLASS=DISK5=SpanishCOLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"6COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKWSDRV_1COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"7COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"VLMBOOT (optional)PERFORMANCE="REQUIRED"Save these diskettes unti
l you are ready to install 
the client software
.PAGENUM=23 ID="BP11"RENDERAS="SECT2"ID="FM68342"
Installing an MS Windows Workstation and Starting NetWare AdministratorIf you want to use the NetWare Administrator graphical utility on an MS Windows 
workstation to set up your network, follow the instructions in this section.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation cabled to the network and running Microsoft* Windows (MS Windows) 3.1At least one NetWare 4.1 server installedThe CLASS=DISKWSDOS_1, CLASS=DISKWSWIN_1, CLASS=DISKWSDRV_1, and CLASS=DISKWSDRV_2 diskettes1.2 MB of free disk space on the workstationRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Insert the CLASS=DISKWSDOS_1 diskette into your workstation's disk drive.PERFORMANCE="REQUIRED"Load th
e client installation program by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"drive:install MOREINFO="NONE"<Enter>Replace 
drive with the letter of you
r workstation disk drive.PERFORMANCE="REQUIRED"Follow the installation instructions o
n the workstation screen.Use the arrow keys to move between the fields. Press MOREINFO="NONE"<Enter> to modify a particular field.Because this workstation is being installed to get you started with the network setup, you can do a standard installation with the default settings now and configure other options later.PERFORMANCE="REQUIRED"Exit the installation program
.PERFORMANCE="REQUIRED"Reboo
t the workstation
.In order for your modifications or new installation to function, you need to reboo
t the workstation.
PAGENUM=24 ID="BP12"PERFORMANCE="REQUIRED"From
 network drive F:
, use the LOGIN command to log in to the network as ADMI
N.The LOGIN command must include your context. Depending on the Directory tree structure you set up for the server during installation, use th
e sequence of Common Name, Organizational Unit, Organization, and Country.For example, i
f this server 
were installed in an Organization called ABC_INC, with no Organizational Unit or Country defined in the Directory tree, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN .ADMIN.ABC_INC MOREINFO="NONE"<Enter>For more information on the LOGIN syntax and options, see "
BOOK="utlrfenu" COLLECTION="nw41"LOGIN" i
n Utilities Reference.PERFORMANCE="REQUIRED"Enter a password if prompted; then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Map the next network drive to the PUBLIC directory of volume SYS: by typin
gFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP N SYS:PUBLIC MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the PUBLIC subdirectory
.For example, if you mapped network drive Z:, you'd type
FORMAT="LINESPECIFIC"MOREINFO="NONE"Z: MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Start 
MS Windows.PERFORMANCE="REQUIRED"Choose the NetWare program group or
, 
if you prefer, choose 
another program group you want to star
t IDXID="w7535"BOOK="_idx" COLLECTION="nw41" TIDREF="i4825"
NetWare Administrator from.PERFORMANCE="REQUIRED"From the Program Manager 
"File
" menu
, choose "New
."PERFORMANCE="REQUIRED"Select 
"Program Item.
"PERFORMANCE="REQUIRED"Choose "OK.
"PERFORMANCE="REQUIRED"Ente
r "NWADMIN" in the "Description
" field
 and press MOREINFO="NONE"<Tab>.
PAGENUM=25 ID="BP13"PERFORMANCE="REQUIRED"Choose "BROWSE."PERFORMANCE="REQUIRED"From the "Drives" drop-down list, select the drive that points to SYS:PUBLIC.PERFORMANCE="REQUIRED"From the list under "File Name," select NWADMIN.EXE and choose "OK.
"The path to the executable file is placed in the "Command Line" text box.PERFORMANCE="REQUIRED"Again, choose "OK," and then choose "Yes."NetWare Administrator is created as a program item icon in the group you selected.You can now use the NetWare Administrator graphical utility to complete your network setup
.PERFORMANCE="REQUIRED"To start NetWare Administrator, choose the "NWADMIN" icon.PERFORMANCE="REQUIRED"Before exiting Windows, from the "Options" menu, select "Save Settings on Exit.
"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Installing MS Windows workstation softwareCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User GuideCOLNAME=1 ROTATE="0" MOREROWS="0"Logging inCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=26 ID="BP14"RENDERAS="SECT2"ID="FM57581"Installing an OS/2 Workstation and Starting NetWare AdministratorIDXID="w7536"BOOK="_idx" COLLECTION="nw41" TIDREF="i2785"
If you want to use the 
NetWare Administrator graphical utility on an OS/2 workstation to set up your network, follow the instructions in this section.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation cabled to the network and running OS/2* v2.x and MicroSoft Windows or WIN-OS/2At least one NetWare 4.1 server installedThe CLASS=DISKWSOS2_1, CLASS=DISKWSOS2_2, CLASS=DISKWSOS2_3, CLASS=DISKOSUTIL_1, CLASS=DISKOS2DOC_X, CLASS=DISKVLMBOOT, and CLASS=DISKWSDRV_1 diskettesRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Start the OS/2 workstation and open an OS/2 full screen or window.PERFORMANCE="REQUIRED"Insert the CLASS=DISKWSOS2_1 diskette into your workstation's disk drive.PERFORMANCE="REQUIRED"Change to the drive where you inserted the diskette and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "Requester on Client" from the "Installation" menu.PERFORMANCE="REQUIRED"Follow the online help and the screen prompts to finish installing the Requester.See BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide 
if you need more information.Because this workstation is being installed to get you started with the network setup, you can do a standard installation with the default settings 
now and configure other options later.On the drive you booted OS/2 from, a directory called NETWARE is created for the Requester files during installation. A program group called Novell® is also created on the OS/2 desktop.PERFORMANCE="REQUIRED"Install VLM Boot.For instructions, see "BOOK="ws_osenu" COLLECTION="nw41"Installing and Using NetWare VLM Boot" in NetWare Client for OS/2 User Guide.PERFORMANCE="REQUIRED"Exit VLM Boot installation.
PAGENUM=27 ID="BP15"PERFORMANCE="REQUIRED"Remove the diskette from the drive; then select the OS/2 Shutdown feature to reboot the workstation.PERFORMANCE="REQUIRED"After the workstation reboots, from the Novell folder launch NetWare VLM Boot by choosing the "VLMBOOT" icon.PERFORMANCE="REQUIRED"From network drive F:, use the LOGIN command to log in to the network as ADMIN.The LOGIN command must include your context. Depending on the Directory tree structure you set up for the server during installation, use the sequence of Common Name, Organizational Unit, Organization, and Country.For example, if this server were installed in an Organization called ABC_Inc., with no Organizational Unit or Country defined in the Directory tree, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN .CN=ADMIN.O=ABC_INC MOREINFO="NONE"<Enter>For more information on the LOGIN syntax and options, see "
BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities Reference.PERFORMANCE="REQUIRED"Enter a password if prompted; then press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Map the next network drive to the PUBLIC directory of volume SYS: by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP N SYS:PUBLIC MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the PUBLIC subdirectory.For example, if you mapped network drive Z:, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"Z: MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Start MS Windows or WIN-OS/2.PERFORMANCE="REQUIRED"IDXID="w7537"BOOK="_idx" COLLECTION="nw41" TIDREF="i3135"IDXID="w7538"BOOK="_idx" COLLECTION="nw41" TIDREF="i1750"Choose the NetWare program group or, if you prefer, choose another program group you want to start NetWare Administrator from.
PAGENUM=28 ID="BP16"PERFORMANCE="REQUIRED"From the Program Manager "File" menu, choose "New."PERFORMANCE="REQUIRED"Select "Program Item" and choose "OK."PERFORMANCE="REQUIRED"Enter "NWADMIN" in the "Description" field and press MOREINFO="NONE"<Tab>.PERFORMANCE="REQUIRED"Choose "BROWSE."PERFORMANCE="REQUIRED"From the "Drives" drop-down list, select the drive that points to SYS:PUBLIC.PERFORMANCE="REQUIRED"From the list under "File Name," select NWADMIN.EXE and choose "OK."The path to the executable file is placed in the "Command Line" text box.PERFORMANCE="REQUIRED"Again, choose "OK," and then choose "Yes."NetWare Administrator is created as a program item icon in the group you selected.You can now use the NetWare Administrator graphical utility to complete your network setup.PERFORMANCE="REQUIRED"To start NetWare Administrator, choose the "NWADMIN" icon.PERFORMANCE="REQUIRED"Before exiting Windows, from the "Options" menu, select "Save Settings on Exit."RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Installing OS/2 workstation softwareCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User GuideCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Logging inCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities ReferencePAGENUM=29 ID="BP17"RENDERAS="SECT2"ID="FM81892"Installing a DOS Workstation and Starting NETADMINIf you want to use text utilities, such as NETADMIN, to set up your network, follow these instructions to install DOS workstation software.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation cabled to the network and running DOS 3.30 or laterAt least one NetWare 4.1 server installedThe CLASS=DISKWSDOS_1, CLASS=DISKWSWIN_1, CLASS=DISKWSDRV_1, and CLASS=DISKWSDRV_2 diskettes1.2 MB of free disk space on the workstationRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Insert the CLASS=DISKWSDOS_1 diskette into the workstation's disk drive.PERFORMANCE="REQUIRED"Load the INSTALL.EXE program by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"drive:INSTALL MOREINFO="NONE"<Enter>Replace 
drive with the 
drive letter of your
 disk drive.PERFORMANCE="REQUIRED"Follow the instructions on your screen.Use the arrow keys to move between the fields. Press MOREINFO="NONE"<Enter> to modify a particular field.Because this workstation is being installed to get you started with the network setup, you can do a standard installation with the default settings now and configure other options later.PERFORMANCE="REQUIRED"Exit the installation program
.PERFORMANCE="REQUIRED"Reboot your workstation.In order for your modifications or new installation to function, you need to reboot your workstation.PERFORMANCE="REQUIRED"Fro
m network drive F:, 
use the LOGIN command to log in to the network as ADMIN.
PAGENUM=30 ID="BP18"Th
e LOGIN command must include your context. Depending on the Directory tree structure you set up for the server during installation, use th
e sequence of Common Name, Organizational Unit, Organization, and Country.For example, i
f this server 
were installed in an Organization called ABC_INC, with no Organizational Unit or Country defined in the Directory tree, 
you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN .ADMIN.ABC_INC MOREINFO="NONE"<Enter>For more information on the LOGIN syntax and options, see "
BOOK="utlrfenu" COLLECTION="nw41"LOGIN" i
n Utilities Reference.PERFORMANCE="REQUIRED"Enter a password if prompted; then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Map the next network drive to the PUBLIC directory of volume SYS: by typin
gFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP N SYS:PUBLIC MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the PUBLIC subdirectory
.For example, if you mapped network drive Z:, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"Z: MOREINFO="NONE"<Enter>You can now use text utilities such as NETADMIN to complete your network setup.PERFORMANCE="REQUIRED"To star
t NETADMI
N, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Installing DOS workstation softwareCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User GuideCOLNAME=1 ROTATE="0" MOREROWS="0"Logging inCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferencePAGENUM=31 ID="BP19"RENDERAS="SECT1"ID="FM92449"Rights Needed to Create and Manage ObjectsAs User object ADMIN, IDXID="w7539"BOOK="_idx" COLLECTION="nw41" TIDREF="i118"
you have all rights to all objects on the Directory tree. However, to allow various parts of the Directory tree to be managed by other users, you need to give those users the rights necessary for them to manage their sections of the tree.When you give an object, such as a User, rights to another object, such as a container, you have made a trustee assignment. That User is now a trustee of that container. An object with a trustee assignment to another object is a trustee of that object.Each object contains a list of trustee assignments called a trustee list. This list tells who can access that object. An object's trustee list is stored in its Access Control List (ACL) property.Four kinds of rights exist in NetWare 4.1:MARK=BULLETObject 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 (unless the Supervisor object right is granted).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 has several properties.IDXID="w7540"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"Directory rights: Control what a trustee can do with a directory. Directory rights also apply to files in the directory only if file rights aren't granted and the file's Inherited Rights Filter doesn't block the directory rights.File rights: Control what a trustee can do with a file.In previous versions of NetWare, you could assign directory and file rights. In NetWare 4.1, you can also assign rights to an object and to properties belonging to an object.This section covers only object rights and property rights.Directory rights and file rights apply only to the file system. For a discussion of these rights, see IDREF="FM80724""Loading Operating Systems and Applications onto the Network" on page 125.PAGENUM=32 ID="BP20"Object and property rights are assigned separately so that you can control access to the pieces of information (or properties) contained in the object.Any object to which you grant sufficient rights can make trustee assignments, using the NetWare Administrator or NETADMIN utility.RENDERAS="SECT2"ID="FM54098"Object RightsIDXID="w7541"BOOK="_idx" COLLECTION="nw41" TIDREF="i3857"
Object rights control what trustees can do with the object that they are trustees of. Object rights control the object as a single piece in the Directory tree, but do not allow the trustee to access information stored in that object's properties (unless the Supervisor object right is granted).IDREF="FM62078"Table 1-3 listsIDXID="w7542"BOOK="_idx" COLLECTION="nw41" TIDREF="i3857"
 and describes the object rights that you can assign to a trustee.  LABEL="1-3" PGWIDE=0 TOCENTRY="1"ID="FM62078"Object RightsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"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"Gives you all rights to the object and to all its properties. However, the Supervisor object right can be blocked by the Inherited Rights Filter (IRF) below the object where the Supervisor right is granted.(An IRF is a list of rights that can be created for any object. It controls the rights that a trustee can inherit from container objects.)COLNAME=1 ROTATE="0" MOREROWS="0"BrowseCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to see the object in the Directory tree. Also, when you perform a search for a value that matches the object, the Browse right to an object allows that object to be listed.COLNAME=1 ROTATE="0" MOREROWS="0"CreateCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to create a new object within a container object in the Directory tree. This right applies only to container objects because leaf objects cannot contain other objects.COLNAME=1 ROTATE="0" MOREROWS="0"DeleteCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to delete an object from the Directory tree. However, you cannot delete a container object unless all the objects in the container are deleted first. See IDREF="FM36317""Moving Container Objects Using NETADMIN" on page 94 or IDREF="FM44519""Moving Container Objects Using NetWare Administrator" on page 92COLNAME=1 ROTATE="0" MOREROWS="0"RenameCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to change the name of the object, in effect changing the naming property. This changes what the object is called when it's a part of complete names. See IDREF="FM86810""Renaming Leaf and Container Objects" on page 100PAGENUM=33 ID="BP21"RENDERAS="SECT2"ID="FM98432"Property RightsIDXID="w7543"BOOK="_idx" COLLECTION="nw41" TIDREF="i3858"
While object rights allow you to see the object, delete the object, create a new object, etc., they do not allow you to see the information stored in the object's properties.To read the information in an object's properties, you must have the correct property rights. Property rights control access to each property in an object.For example, if you include a private telephone number as a property for a User object, you can use property rights to prevent anyone else from seeing that telephone number. At the same time, you can allow other properties, such as Address or Fax Number, to be viewed.PAGENUM=34 ID="BP22"IDREF="FM31948"Table 1-4 lists and describes 
property IDXID="w7544"BOOK="_idx" COLLECTION="nw41" TIDREF="i3858"
rights that you can assign to a trustee  LABEL="1-4" PGWIDE=0 TOCENTRY="1"ID="FM31948"Property RightsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"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"Gives you all rights to the property. You can block the Supervisor property right with an Inherited Rights Filter. See "BOOK="cncptenu" COLLECTION="nw41"Security" in Concepts.COLNAME=1 ROTATE="0" MOREROWS="0"CompareCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to compare any value to an existing value of the property. The comparison can return True or False, but cannot give the value of the property.COLNAME=1 ROTATE="0" MOREROWS="0"ReadCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to read the values of the property. This right includes the Compare right; that is, if the Read right is given, Compare operations are also allowed.COLNAME=1 ROTATE="0" MOREROWS="0"WriteCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to add, change, or remove any values of the property. The Write right includes the Add or Delete Self rightThe Write right to the ACL property is the same as giving the Supervisor right to the object.COLNAME=1 ROTATE="0" MOREROWS="0"Add or Delete SelfCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to add or remove yourself as a value of the property, but you cannot change any other values of the property. This right is only used for properties where your User object can be listed as a value, such as group membership lists or mailing lists. The Write right includes the Add or Delete Self right.See the following references for more detailed information.Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Access Control ListCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Access Control List" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Container and leaf objectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Trustees and rightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Security" in ConceptsPAGENUM=35 ID="BP23"RENDERAS="SECT1"Managing Trustee Assignments to ObjectsAn object granted rights to work with another object is called a trustee of the 
object. Through trustee assignments, you determine what level of rights you want trustees to have on the objects they are assigned to.For example, to make user KSMITH a trustee of Organizational Unit MARKETING, go to the Organizational Unit MARKETING and add KSMITH as a trustee, giving KSMITH whatever object and property rights you think are sufficient.KSMITH's trustee assignment to MARKETING overrides any other rights that KSMITH may have inherited or received through security equivalence.You can manage trustee 
assignments to objects using either the NetWare Administrator graphical utility or the NETADMIN text utility. Both procedures are documented in this section.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Inherited Rights FilterCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Inherited Rights Filter" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"SecurityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Security" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"TrusteesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Trustee" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=36 ID="BP24"RENDERAS="SECT2"Using NetWare Administrator to Manage Trustee AssignmentsRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Supervisor object right to the object to which trustees are to be assignedRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager or the OS/2 desktop, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"Select the object you want to assign trustees to.PERFORMANCE="REQUIRED"Click once on the right button of your mouse and choose "Trustees of this Object," or, from the "Object
" menu
, choose "Trustees of this Object."All the curent trustees of this object are listed in the "Trustees" box.From the "Trustees" dialog, you can
MARK=BULLETView or change a trustee's effective rights to this objectAdd a trustee to this objectDelete a trustee from this objectChange the object IDXID="w7545"BOOK="_idx" COLLECTION="nw41" TIDREF="i3857"
rights of a trusteeChange the property rights of a trusteeView or change the Inherited Rights Filter (IRF) of this objectPERFORMANCE="REQUIRED"For instructions on completing any of the above procedures, press the "Help" button and then select one of the procedures from the list.
PAGENUM=37 ID="BP25"RENDERAS="SECT2"Using NETADMIN to Manage Trustee AssignmentsRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Supervisor object right to the object to which trustees are to be assignedRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manag
e Objec
ts" from the "NETADMIN Options
" menu.PERFORMANCE="REQUIRED"Browse the Directory tree until you see the object you want to assign trustees to.Use the instructions at the bottom of the screen to browse the directory. Press 
MOREINFO="NONE"<F1> if you need h
elp.PERFORMANCE="REQUIRED"When the desired object appears in the 
"Object
, Class " list, select it and pres
s MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Select "View or Edit the Trustees of This Object."From the "Trustees of This Object" menu you can
MARK=BULLETSet the "Inherited Rights Filter" (IRF), which affects all trustees that are not explicitly assigned to this object.Add or change trustee assignments (which override the IRF)View the "Effective Rights" for a trusteePERFORMANCE="REQUIRED"From the "Trustees of This Object" menu, select one of the options.PERFORMANCE="REQUIRED"For instructions on completing a procedure, press 
MOREINFO="NONE"<F1>.
PAGENUM=38 ID="BP26"RENDERAS="SECT1"IDXID="w7546"BOOK="_idx" COLLECTION="nw41" TIDREF="i807"
Creating Container ObjectsYou can create container objects by using either the NetWare Administrator graphical utility or the NETADMIN text utility. Each of these methods is explained in this section.Considerations for naming container objects and suggestions for creating searchable objects are also covered.RENDERAS="SECT2"Types of Container ObjectsThe kinds of container objects you can create are Country, Organization, and Organizational Unit. The top object, called Root, is created by default and is placed at the top of the Directory tree when NetWare 4.1 is installed.Container objects form the top levels of the Directory tree. Use them to manage and organize the Directory by relating groups of objects, both container objects and leaf objects.For more information about planning the top levels of your Directory tree, see Chapter 5, "BOOK="getstenu" COLLECTION="nw41"Planning NetWare Directory Services Implementation," of Introduction to NetWare Directory Services.IDREF="FM89920"Figure 1-2 illustrates the hierarchy of container objects and leaf objects in NetWare Directory Services. (The icons represent the leaf objects as they appear in the NetWare Administrator graphical utility.)PAGENUM=39 ID="BP27"LABEL="1-2" FLOAT="0"ID="FM89920"Hierarchy of ObjectsFILEREF="n41su02a.tif"The first three leaf objects in the figure---Message Routing Group, External Entity, and Distribution List---are NetWare Message Handling ServiceTM (NetWare MHS) objects. They appear in NetWare Administrator only if you have installed NetWare MHSTM Services on your NetWare server.You can create leaf objects only under the Organization and Organizational Unit container objects.PAGENUM=40 ID="BP28"IDXID="w7547"BOOK="_idx" COLLECTION="nw41" TIDREF="i807"IDREF="FM95508"Table 1-5 describes each type of container object you can create and when to use it.LABEL="1-5" PGWIDE=1 TOCENTRY="1"ID="FM95508" Container Objects You Can CreateCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="11*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Container ObjectCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"When to Use ItVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7548"BOOK="_idx" COLLECTION="nw41" TIDREF="i861"
CountryCOLNAME=2 ROTATE="0" MOREROWS="0"Designates the countries where your network resides and organizes other objects within the country.You must always include the name type of the object in complete names when you include the Country container object in your Directory tree. Even when you refer to objects located in the same container object, you must designate the name type (CN, OU, or O) of the object.COLNAME=3 ROTATE="0" MOREROWS="0"This object is optional. You do not have to create a Country object.If you choose to create a Country object, you can use it to represent the country where your organization headquarters reside or, if you have a multinational network, to represent each country that is a part of your network.You can create a Country container object only under the Root object.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7549"BOOK="_idx" COLLECTION="nw41" TIDREF="i3114"
OrganizationCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to organize other objects in the Directory, to set defaults in a login script, and to create a user template for User objects you create in this container.For example, you can use an Organization object to designate a corporation.COLNAME=3 ROTATE="0" MOREROWS="0"The Organization container object is mandatory. The Directory tree must contain at least one.You can create an Organization object only under the Root or Country object.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7550"BOOK="_idx" COLLECTION="nw41" TIDREF="i3121"
Organizational UnitCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to organize leaf objects in the Directory tree, to set defaults in a login script, and to create a user template for User objects you create in this container.COLNAME=3 ROTATE="0" MOREROWS="0"You can use an Organizational Unit object to designate a division, a business unit, or a project team.You can create multiple levels of Organizational Units.You can create Organizational Units in Organization objects and in other Organizational Unit objects.PAGENUM=41 ID="BP29"RENDERAS="SECT2"ID="FM57540"Naming Container ObjectsIDXID="w7551"BOOK="_idx" COLLECTION="nw41" TIDREF="i807"
Try to IDXID="w7552"BOOK="_idx" COLLECTION="nw41" TIDREF="i2571"
keep container object names short and simple. This makes it easier for users to change context and to remember their own context.The following rules apply to most objects. For specific rules about naming leaf objects, see IDREF="FM31118""Naming Leaf Objects" on page 53.RENDERAS="SECT3"Object Naming RulesMARK=BULLETThe name must be unique in the branch (container) of the Directory tree where the object is located.The object name can be up to 64 characters in length.You can use any special characters. But if the object needs to be accessed from a client running a version of NetWare earlier than NetWare 4TM, you should avoid using special characters. (For a list of these characters, see IDREF="FM63830""Object Name Restrictions for Bindery Services" on page 42.)You can enter object names in either upper or lowercase. Object names are displayed with uppercase and lowercase letters as they were first entered, but they are not case sensitive. Therefore, "ManagerProfile" and "MANAGERPROFILE" are considered to be identical names.You can use both spaces and underscores, but they are both displayed as spaces. Therefore, "Manager_Profile" and "Manager Profile" are considered to be identical names.Country objects can have only a two-character name.If you anticipate managing objects created from different code pages, you must limit object names and properties to those characters common to all the applicable code tables.Nondisplayable Unicode* characters for your code page are represented by an ASCII 3 character (a "heart" symbol). For more information, see "BOOK="cncptenu" COLLECTION="nw41"Unicode" in Concepts.PAGENUM=42 ID="BP30"RENDERAS="SECT3"ID="FM63830"Object Name Restrictions for Bindery ServicesWhen you create objects to be accessed from a client running a version of NetWare earlier than NetWare 4, the names of the objects must follow bindery naming rules or the non-NetWare 4.1 client will not recognize them. Object names in bindery services are interpreted as the following:MARK=BULLETSpaces in object names are replaced by underscores.Object names longer than 47 characters are cut off after the 47th character.You cannot use the following characters in an object name that must be accessed from a client running a version of NetWare earlier than NetWare 4:TYPE="VERT"/ Slash\ Backslash: Colon, Comma* Asterisk? Question markRENDERAS="SECT2"Creating Searchable Container ObjectsIDXID="w7553"BOOK="_idx" COLLECTION="nw41" TIDREF="i3982"
When you create a container object, you can enter various types of information about that object into its properties, such as location and telephone number. If you enter data into the containers' properties in a consistent format, it is easier to search the Directory database for a particular type of information.Many container object properties are optional; you are not required to enter information about the property in order to create the object. However, information in objects' properties can help you track and manage container objects.After you have created container objects, you can use the NetWare Administrator, NETADMIN, or NLIST utility to search for and list these objects. You can also search for their various properties.PAGENUM=43 ID="BP31"RENDERAS="SECT2"IDXID="w7554"BOOK="_idx" COLLECTION="nw41" TIDREF="i808"
Creating Container Objects Using INSTALLWhen you install NetWare 4.1 on a server, you are required to type a context (the pathname from the container object to the Root object) in which the NetWare Server object is placed.If you create a new context, several events happen by default:MARK=BULLETAn Organization or Organizational Unit container object is created, depending on the context you create.Bindery services are set for that container object, so that the server you installed in the container object is running bindery services.A read/write replica of the Directory partition that the container object is in is stored on the server that you just installed.For more information on how to create container objects using the installation process, see Chapter 2, "BOOK="instlenu" COLLECTION="nw41"Simple Installation," or Chapter 3, "BOOK="instlenu" COLLECTION="nw41"Custom Installation," of Installation.RENDERAS="SECT2"IDXID="w7555"BOOK="_idx" COLLECTION="nw41" TIDREF="i808"
Creating Container Objects Using NetWare AdministratorRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Create object right to the container that will contain the new container objectRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager or the OS/2 desktop, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"Select the object that will contain the new container object.For information on moving around in th
e browser and choosing objects, press 
MOREINFO="NONE"<F1>.PERFORMANCE="REQUIRED"Choose "Create" from the "Object" menu.
PAGENUM=44 ID="BP32"PERFORMANCE="REQUIRED"Select the new container object class that you want from the 
"New Object" dialog.If the container object class you want to create does not appear under "New Object," you cannot create that object in the selected container. Choose "Cancel" to return to the browser; then select a different container type.PERFORMANCE="REQUIRED"Choose "OK."The "Create Object" dialog appears.PERFORMANCE="REQUIRED"Type a name for the object in the box provided.PERFORMANCE="REQUIRED"(Optional) Select "Define Additional Properties."Select this option if you want to enter more information for the new container object.Examples of additional properties are Login Script, Intruder Detection, Postal Address, and See Also. The Login Script and Intruder Limit apply to User objects in the new container object.PERFORMANCE="REQUIRED"(Optional) Select "Define User Defaults."Select this option if you want to use the same default information in the new container as was present in the parent container. This default information is used whenever you create a new user.The user default information for each container is actually stored in a User object named USER_TEMPLATE.PERFORMANCE="REQUIRED"Choose "Create."PERFORMANCE="REQUIRED"(Optional) Choose "Yes" if you want to inherit user template properties from the parent container, or "No" if you want to define a new user template.PERFORMANCE="REQUIRED"(Optional) Add information to the object dialog pages.If you chose 
"Define Additional Properties,
" add the information now. Press 
MOREINFO="NONE"<F1> to get help on each field.PERFORMANCE="REQUIRED"Choose "OK
" to save the properties you have just entered in the dialog pages
.PAGENUM=45 ID="BP33"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"User templatesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88652""Managing User Templates" on page 78COLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using object dialog pages in NetWare AdministratorCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT2"ID="FM69041"IDXID="w7556"BOOK="_idx" COLLECTION="nw41" TIDREF="i808"
Creating Container Objects Using NETADMINRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterThe Create object right to the object that will contain the new container objectRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manage Objects
" from the "NETADMIN Options
" menu.PERFORMANCE="REQUIRED"Select the container object that will contain the new container object
.The objects in the selected container are listed.To see if you're in the right context, look at the title bar on the screen. Press 
MOREINFO="NONE"<F1> if you need h
elp.PAGENUM=46 ID="BP34"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"Select the container object class that you want to create from the 
"Select an Object Class
" screen.If the container object class you want to create does not appear, you cannot create that object in the selected container. Press 
MOREINFO="NONE"<Esc> to return to th
e browser; then select a different container type.PERFORMANCE="REQUIRED"Type the new container object name
.PERFORMANCE="REQUIRED"Enter a Mailbox Location and press 
MOREINFO="NONE"<Enter>.If you are creating a Country object, you are not prompted to define a Mailbox Location or create a user template.PERFORMANCE="REQUIRED"If you want to create a user template to be applied to new User objects created in this container, type 
"Y
" and press 
MOREINFO="NONE"<Enter>.A user template contains default information that you can apply to users that you create to give them default property values
.The user template is actually a User object named USER_TEMPLATE.If you do not want to create a user template, type 
"N
" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to save the information.PERFORMANCE="REQUIRED"If you want to create another container object
, choose "Yes.
" If you do not
, choose "No" and 
then press 
MOREINFO="NONE"<Enter>.If yo
u chose "Yes,
" you are prompted to type the new container object name. Repeat Steps 6 through 9, and then continue with Step 
12.If yo
u chose No, then the container object is displayed in the Directory tree. Continue with Step 
12.PERFORMANCE="REQUIRED"ID="FM12921"To edit this object, press 
MOREINFO="NONE"<F10>.A menu appears from which you can choose to view or edit properties of this object and make trustee assignments to this object and to files and directories.PERFORMANCE="REQUIRED"Choose an option from the "Actions
" menu and add any necessary information.
PAGENUM=47 ID="BP35"PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until you return to the "NETADMIN Options
" menu
.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Object propertiesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Property" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"User templatesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88652""Managing User Templates" on page 78COLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceRENDERAS="SECT1"ID="FM76532"Creating Leaf ObjectsIDXID="w7557"BOOK="_idx" COLLECTION="nw41" TIDREF="i2099"Leaf objects represent network resources, such as users, computers, printers, and lists. They do not contain any other objects.IDXID="w7558"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"
You create leaf objects within a container object. IDREF="FM68453"Figure 1-3 lists the leaf objects you can create. (The icons represent the leaf objects as they appear in the NetWare Administrator graphical utility.)LABEL="1-3" FLOAT="0"ID="FM68453"Leaf Objects You Can CreateFILEREF="n41su05a.tif"PAGENUM=48 ID="BP36"The first three leaf objects in the figure---Message Routing Group, External Entity, and Distribution List---are NetWare MHS Services objects. They appear in NetWare Administrator only if you have installed NetWare MHS Services on your NetWare server.RENDERAS="SECT2"How to Use Leaf ObjectsIDXID="w7559"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"IDREF="FM54279"Table 1-6 describes each leaf object you can create and when to use it.LABEL="1-6" PGWIDE=1 TOCENTRY="1" Leaf Objects You Can CreateID="FM54279"COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="14*"COLNAME=3 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Leaf ObjectCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"When to UseVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7560"BOOK="_idx" COLLECTION="nw41" TIDREF="i136"
AFP ServerCOLNAME=2 ROTATE="0" MOREROWS="0"Represents an AppleTalk* Filing Protocol- based server that is operating as a node on your NetWare network (and possibly also acting as a NetWare router to, and the AppleTalk* server for, several Apple* Macintosh* workstations).COLNAME=3 ROTATE="0" MOREROWS="0"Create this object when you have an AFP server that you need to represent on the network. Use it to store information about this server, such as its description, location, and network address.This object has no effect on the operation of the network; it only stores information about the AFP server.COLNAME=1 ROTATE="0" MOREROWS="0"AliasCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7561"BOOK="_idx" COLLECTION="nw41" TIDREF="i152"
Points to another object in the Directory tree and makes it appear as if the object that it points to actually exists in the Directory tree where the Alias object is.Although an object appears both where it was actually created and where an Alias referring to it was created, only one copy of the object really exists.If you delete or rename an Alias, the Alias itself (not the object it is pointing to) is deleted or renamed.COLNAME=3 ROTATE="0" MOREROWS="0"Use this object to allow access to an object that is in another context.For example, you can use an Alias to represent a resource, such as a special printer, that most users in the tree need to access.Also, 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, NetWare Administrator automatically creates the alias for you and assigns it the same name as the original object.Creating an alias in place of a moved or renamed container object allows users to continue logging into the network and to see the container object (and the objects it contains) in its original Directory locationCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7562"BOOK="_idx" COLLECTION="nw41" TIDREF="i732"
ComputerCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a nonserver computer on the network, such as a workstation or a router.COLNAME=3 ROTATE="0" MOREROWS="0"Use this object to store information about a nonserver computer, such as its network address, or serial number, or the person the computer is assigned to.This object has no effect on the operation of the network; it only stores information about the computer.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7563"BOOK="_idx" COLLECTION="nw41" TIDREF="i1060"
Directory MapCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7564"BOOK="_idx" COLLECTION="nw41" TIDREF="i1220"
Represents a particular directory in the file system. Directory Map objects can be especially useful in login scripts by pointing to directories that contain applications or other frequently used files.For example, if you have a directory that contains DOS 5.0, you will probably map a search drive to that directory in any login scripts you create. Later, if you upgrade to DOS 6.0 and rename the directory, you would have to change the mapping in every login script where that search mapping appears.With a Directory Map object, you only change the information in that one object.COLNAME=3 ROTATE="0" MOREROWS="0"Use this object to avoid making changes to many login scripts when the location of applications changes; instead, you change only the Directory Map object.For more information on Directory Map objects, see IDREF="FM80724""Loading Operating Systems and Applications onto the Network" on page 125COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7565"BOOK="_idx" COLLECTION="nw41" TIDREF="i1161"
Distribution ListCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a list of mail recipients.COLNAME=3 ROTATE="0" MOREROWS="0"Use this object to simplify sending mail to recipients.For example, you could create a Distribution List object called Recreation Committee. Anyone wanting to send a message to all the members in the Recreation Committee can simply address the message to Recreation Committee, rather to each member.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7566"BOOK="_idx" COLLECTION="nw41" TIDREF="i1408"
External EntityCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a nonnative NDSTM (NetWare Directory Services) object that is imported into NDS or registered in NDS.NetWare MHS Services use External Entity objects to represent users from non- NDS directories to provide an integrated address book for sending mail.COLNAME=3 ROTATE="0" MOREROWS="0"If your messaging environment contains non-MHS servers, such as SMTP hosts, SNADS nodes, or X.400 MTAs, you might choose to add users and lists at these servers to your NetWare database as External Entities.Adding these objects to the database as External Entities adds them to the address books of your messaging applications. When addressing messages, local users can choose non-MHS users and lists from a directory list.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7567"BOOK="_idx" COLLECTION="nw41" TIDREF="i1617"
GroupCOLNAME=2 ROTATE="0" MOREROWS="0"Assigns a name to a list of User objects that can be located anywhere in the Directory tree.COLNAME=3 ROTATE="0" MOREROWS="0"Create a Group when you have many User objects that need the same trustee assignments. Rather than making many trustee assignments, you make just one trustee assignment to all the users who belong to the group, by making the trustee assignment to the Group object itself.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7568"BOOK="_idx" COLLECTION="nw41" TIDREF="i2415"
Message Routing GroupCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a group of messaging servers that can transfer messages directly with each other.COLNAME=3 ROTATE="0" MOREROWS="0"Create a Message Routing Group when you have two or more messaging servers that need to communicate with each other.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7569"BOOK="_idx" COLLECTION="nw41" TIDREF="i2428"
Messaging ServerCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a messaging server that resides on a NetWare server. A Messaging Server object is automatically created in the NDS tree when you install NetWare MHS Services on a NetWare server.COLNAME=3 ROTATE="0" MOREROWS="0"Create a Messaging Server (by installing NetWare MHS Services on a NetWare server) when you need a server to handle messaging between users and groups on the network.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7570"BOOK="_idx" COLLECTION="nw41" TIDREF="i2794"
NetWare ServerCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a server running NetWare on your network.Store information about the server in the NetWare Server object's properties, such as the server's address, the physical location of the server, and what services it provides.In addition to storing information about the NetWare server, the NetWare Server object affects the network in that it is referred to by several other objects.COLNAME=3 ROTATE="0" MOREROWS="0"Use the NetWare Server object to tie the physical server on the network to the Directory tree. Without this object, you cannot access file systems that are on that server's volumes.If you have a non-NetWare 4.1 server, you must create this object to be able to access those non-NetWare 4.1 volumes. When you create a NetWare Server object for a non-NetWare 4.1 server, the non- NetWare 4.1 server must be running.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7571"BOOK="_idx" COLLECTION="nw41" TIDREF="i3118"
Organiza- tional RoleCOLNAME=2 ROTATE="0" MOREROWS="0"Defines a position or role within an organization.COLNAME=3 ROTATE="0" MOREROWS="0"Create an Organizational Role object so that you can assign rights to a particular position rather than to the person who may occupy that position. The occupant may change frequently, but the responsibilities of that position do not.You can assign any user to be an occupant of the Organizational Role object because every occupant receives the same rights that you granted to the Organizational Role object.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7572"BOOK="_idx" COLLECTION="nw41" TIDREF="i3441"
Print QueueCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a print queue on the network.COLNAME=3 ROTATE="0" MOREROWS="0"You must create a 
Print Queue object for every print queue on the network.This object cannot be created with NETADMIN.See 
BOOK="printenu" COLLECTION="nw41"Print Services for more information.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7573"BOOK="_idx" COLLECTION="nw41" TIDREF="i3457"
Print ServerCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a network print server.COLNAME=3 ROTATE="0" MOREROWS="0"You must create a Print Server object for every print server on the network.This object cannot be created with NETADMIN.See 
BOOK="printenu" COLLECTION="nw41"Print Services for more information.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7574"BOOK="_idx" COLLECTION="nw41" TIDREF="i3517"
PrinterCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a physical printing device on the network.COLNAME=3 ROTATE="0" MOREROWS="0"You must create a Printer object for every printer on the network.This object cannot be created with NETADMIN.See 
BOOK="printenu" COLLECTION="nw41"Print Services for more information.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7575"BOOK="_idx" COLLECTION="nw41" TIDREF="i3567"
ProfileCOLNAME=2 ROTATE="0" MOREROWS="0"Contains a profile script (login script). When the Profile object is listed as a User object's property, the Profile object's login script is executed when that User object logs in. The Profile login script executes after the system login script and before the user login script.COLNAME=3 ROTATE="0" MOREROWS="0"Create a Profile object for a set of users who need to share common login script commands but who are not located in the same container in the Directory tree, or who are a subset of users in the same container.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7576"BOOK="_idx" COLLECTION="nw41" TIDREF="i4710"
UserCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a person who uses your network.In the User object properties, you can set login restrictions, intruder detection limits, password and password restrictions, security equivalences, etc.COLNAME=3 ROTATE="0" MOREROWS="0"You must create a User object for every user who needs to log in to the network. When you create a User object, you can create a home directory for that user who will have default rights to that home directory. When you create User objects, you can also choose to apply a user template to the user that provides default property values.For users who have NetWare 4.1 workstations, you can create the User objects anywhere in the Directory tree, but the users must know their context in order to log in. You should create User objects in the container where the users will typically log in.For users who have non-NetWare 4.1 workstations, you must create the User objects in the container at which the bindery services context is set for the server that they need to log in to. (Bindery services is set by default for every NetWare 4.1 server that is installed.) Non- NetWare 4.1 users do not need to know their context because they log in to the server rather than to the Directory tree.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7577"BOOK="_idx" COLLECTION="nw41" TIDREF="i4787"
VolumeCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a physical volume on the network.In the Volume object's properties, you can enter identification information, such as the Host server, volume location, etc. You can also set restrictions for use of the volume, such as space limits for users.COLNAME=3 ROTATE="0" MOREROWS="0"You can create a Volume object for every physical volume on the network. (During installation of NetWare 4.1 on a server, Volume objects are created for every physical volume on that server.)When you create a Volume object, you are prompted for the server name and the volume name on the server. That information is placed in the Volume object's properties.You can use the Volume object to display information about the directories and files on that volume.PAGENUM=53 ID="BP37"RENDERAS="SECT2"ID="FM31118"Naming Leaf ObjectsIDXID="w7578"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"
The IDXID="w7579"BOOK="_idx" COLLECTION="nw41" TIDREF="i2571"
object naming rules described in the next section apply to most objects. Special rules applying to NetWare Server objects and objects viewed through bindery services are described in separate sections. For rules about naming container objects, see IDREF="FM57540""Naming Container Objects" on page 41.RENDERAS="SECT3"Object Naming RulesMARK=BULLETThe name must be unique in the branch (container) of the Directory tree where the object is located.The object name can be up to 64 characters in length.You can use any special characters. But if the object needs to be accessed from a client running a version of NetWare earlier than NetWare 4, you should avoid using special characters. (For a list of these characters, see IDREF="FM63830""Object Name Restrictions for Bindery Services" on page 42.)You can enter object names in either upper or lowercase. Object names are displayed with uppercase and lowercase letters as they were first entered, but they are not case sensitive. Therefore, "ManagerProfile" and "MANAGERPROFILE" are considered to be identical names.PAGENUM=54 ID="BP38"You can use both spaces and underscores, but they are both displayed as spaces. Therefore, "Manager_Profile" and "Manager Profile" are considered to be identical names.(If you use a space in a name, you must place quote marks around that text string whenever you use a command line utility that includes that text string.)If you anticipate managing objects created from different code pages, you must limit object names and properties to those characters common to all the applicable code tables.Nondisplayable Unicode characters for your code page are represented by an ASCII 3 character (a "heart" symbol). For more information, see "BOOK="cncptenu" COLLECTION="nw41"Unicode" in Concepts.RENDERAS="SECT3"ID="FM87375"Object Name Restrictions for Bindery ServicesIDXID="w7580"BOOK="_idx" COLLECTION="nw41" TIDREF="i457"
When you create objects to be accessed from a client running a version of NetWare earlier than NetWare 4, the names of the objects must follow bindery naming rules or the pre-NetWare 4 client does not recognize them. Object names in bindery services are interpreted as the following:MARK=BULLETSpaces in object names are replaced by underscores.Object names longer than 47 characters are cut off after the 47th character.You cannot use the following characters in an object name that must be accessed from a client running a version of NetWare earlier than NetWare 4:TYPE="VERT"/ Slash\ Backslash: Colon, Comma* Asterisk? Question mar
kRENDERAS="SECT3"Naming Restrictions for NetWare Server ObjectsIDXID="w7581"BOOK="_idx" COLLECTION="nw41" TIDREF="i2794"ID="FM17060"The first NetWare Server object for a NetWare 4.1 server must be created with INSTALL. The object is given the same name as the physical server. Rules for naming physical servers are in the MOREINFO="NONE"<F1> Help of INSTALL.PAGENUM=55 ID="BP39"If you create a NetWare Server object for a non-NetWare 4.1 server, you must use the physical server name as well, because NetWare Directory Services must search for the server on the network to verify its existence.For example, if you create a Server object for a NetWare 3TM server whose physical name on the network is SURFBOY, you must name the Server object SURFBOY.Because of these restrictions, you can never rename a NetWare Server object, even if you have the Supervisor object right to it. For more information on NetWare Server objects, see "BOOK="cncptenu" COLLECTION="nw41"Object" in Concepts.RENDERAS="SECT2"Creating Searchable Leaf ObjectsIDXID="w7582"BOOK="_idx" COLLECTION="nw41" TIDREF="i3982"
When you create an object, you enter various types of information about that object into its properties. An object's properties can include a telephone number, a description, an address, etc.Many object properties are optional; you are not required to enter information about such properties to create the object. However, information in objects' properties can help you track and manage those objects.After you have created objects, you can use the NetWare Administrator, NETADMIN, or NLIST utility to search for and list these objects. You can also search for the values contained in the objects' properties.If you enter data into the properties in a consistent format, it is easier to search the Directory database for different types of information when you need it.For example, you may want to search for all User objects at a certain location, such as building M1. You cannot easily list all objects located in building M1 if you have entered "Bldg. M1," "BLDG M1," and "M1" as values in the Location property of multiple User objects.Standardizing the value for the Location property for all User objects at the site (such as M1, M2, and M3) makes it possible to search for objects located in each building.PAGENUM=56 ID="BP40"RENDERAS="SECT2"Creating Leaf Objects Using NetWare AdministratorRENDERAS="SECT3"IDXID="w7583"BOOK="_idx" COLLECTION="nw41" TIDREF="i2099"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Create object right to the container that will contain the new leaf objectRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select the object that will contain the new leaf object.For information o
n moving around in th
e browser and selecting objects, press 
MOREINFO="NONE"<F1>.If you are creating User objects, remember that users who are using non-NetWare 4.1 workstations must be created in the container where the bindery services context is set for the server that they need to log in to.You can create User objects for users who have NetWare 4.1 workstations anywhere in the Directory tree, but the users must know their context in order to log in. You should create User objects in the container where the users will typically log in.PERFORMANCE="REQUIRED"Choose "Create
" from the "Object
" menu
.PERFORMANCE="REQUIRED"From the "New Object" dialog, select the class of object yo
u want to create.If the class of object you selected does not appear under 
"New Object,
" you cannot create this object in this containe
r. Select or create another container to hold the object.PERFORMANCE="REQUIRED"Choose "OK
."Eac
h type of leaf object that you create has a different 
"Create
" dialo
g. For details on each dialo
g, choose "Help.
"IDXID="w7584"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"
The 
property fields that are displayed in the 
"Create
" dialo
g are mandator
y. You must enter information in these fields
.PAGENUM=57 ID="BP41"The check boxes that are displayed in the 
"Create
" dialo
g are optional. Usually, you can select only one box, not both.For example, if yo
u select "Define Additional Properties," the 
"Identification
" page is displayed 
immediately after the object is created. If yo
u select "Create Another Objec
t," another 
"Creat
e" dialog is displaye
d immediately after the object is created.PERFORMANCE="REQUIRED"Choose "Create.
"If you chose "Define Additional Properties," the object dialog appears. If you chose "Create Another Object," another "Create Object
" dialo
g appears
.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the object dialog in NetWare AdministratorCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT2"Creating Leaf Objects Using NETADMINRENDERAS="SECT3"IDXID="w7585"BOOK="_idx" COLLECTION="nw41" TIDREF="i2099"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterThe Create object right to the container object that will contain the new leaf objectRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.
PAGENUM=58 ID="BP42"PERFORMANCE="REQUIRED"Choose "Manage Objects
" from the "NETADMIN Options
" menu.PERFORMANCE="REQUIRED"Select the container that will contain the new leaf object
.The objects in the selected container are listed.To see if you're in the right context, look at the title bar on the screen
.Press 
MOREINFO="NONE"<F1> if you need h
elp.If you are creating User objects, remember that users who are using non-NetWare 4.1 workstations must be created in the container at which the bindery services context is set for the server that they need to log in to.You can create User objects for users who have NetWare 4.1 workstations anywhere in the Directory tree, but the users must know their context in order to log in. You should create User objects in the container where the users will typically log in.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"From the "Select an Object Class" screen, select the object class that you want to creat
e.If the object class you want to create does not appear, you cannot create that object in the selected container. Press 
MOREINFO="NONE"<Esc> to return to th
e browser; then select a different container type
.PERFORMANCE="REQUIRED"Type the information you are prompted for and press 
MOREINFO="NONE"<Enter>.Each leaf object that you create has a differen
t dialog. For details on eac
h dialog, press 
MOREINFO="NONE"<F1> for help.PERFORMANCE="REQUIRED"If you want to create another leaf object
, choose "Yes.
" If you do not
, choose "No."If yo
u choose "Yes,
" you are prompted for information about the next object you want to add. Repeat Step 6, and then continue with Step 8.If yo
u choose "No
", the leaf object is displayed in the Directory tree. Continue with the next step.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to edit this object.A menu appears from which you can choose to view or edit information about this object.
PAGENUM=59 ID="BP43"PERFORMANCE="REQUIRED"Choose an option from the "Actions
" menu and add any necessary information.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until you return to the "NETADMIN Options
" menu
.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceRENDERAS="SECT1"ID="FM76225"Managing Groups of User ObjectsIDXID="w7586"BOOK="_idx" COLLECTION="nw41" TIDREF="i1617"
NetWare 4.1 allows you to manage User objects as a group, which is often more efficient than managing them individually. Six objects that can help you manage groups of User objects are described in IDREF="FM28157"Table 1-7.LABEL="1-7" PGWIDE=1 TOCENTRY="1"ID="FM28157" Objects That Help Manage UsersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Organization objectCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to assign trustee rights, login scripts, and user defaults to the User objects in the Organization.COLNAME=1 ROTATE="0" MOREROWS="0"Organizational Unit objectCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to assign trustee rights, login scripts, and user defaults to the User objects in the Organizational Unit.COLNAME=1 ROTATE="0" MOREROWS="0"Group objectCOLNAME=2 ROTATE="0" MOREROWS="0"Provides an efficient way for you to manage only one object, the Group object, instead of many individual User objects.COLNAME=1 ROTATE="0" MOREROWS="0"Profile objectCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to set up a specific work environment by using a common login script for groups of users who need similar work environments but who are not located in the same container object.COLNAME=1 ROTATE="0" MOREROWS="0"Organizational Role objectCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to assign rights to a particular position and set of responsibilities, rather than to a person. The person who occupies that position may change frequently, but the responsibilities of that position do not.The difference between a Group object and an Organizational Role object is that a Group object usually has many members, whereas an Organizational Role object usually has only one or two.COLNAME=1 ROTATE="0" MOREROWS="0"USER_TEMPLATECOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to apply default property values to any user that you create in a container object. You can choose to apply the information in the user template when you create new User objects.PAGENUM=60 ID="BP44"RENDERAS="SECT2"ID="FM53699"Managing Group ObjectsIf you want a user to have access to an object, you must make a trustee assignment to that object. Rather than make trustee assignments to many users, you can create a Group object and then, with just one trustee assignment, grant access to all the users who belong to the Group.If a trustee assignment names a Group object as the trustee, every user in the membership list of the Group object is granted the same access that is granted to the Group object.After you have created a Group object and added User object names to it, you manage the rights of the Group object rather than the rights of the individual group members.For example, suppose you have a word processing application on the network that many users need to access. You could create a Group object named WORD PROCESSOR USERS and add the User object names of the users who need access to the application.Then, rather than granting file trustee rights to each of the individual User objects, you grant the file trustee rights to the Group object WORD PROCESSOR USERS for the application and the working directory.The users can then use the word processing application just as if you had granted them file trustee rights to the application individually.When a user is added to the membership list of a Group object, the Group is listed in that user's Security Equal To property. Security Equal To is a property of every User object that lists other objects. The user is granted all rights that any object (User, Group, Printer, etc.) in that list is granted, both object and file rights.Only User objects can be listed in a Group, and you can add User objects from any part of the Directory tree to a Group.PAGENUM=61 ID="BP45"A Group object is not a container. It does not "contain" User objects; users' names are merely assigned to a Group object.To create a Group object, see IDREF="FM76532""Creating Leaf Objects" on page 47.You must create User objects before you can add them to the membership list of a Group object. See IDREF="FM76532""Creating Leaf Objects" on page 47 for instructions on creating User objects.After you have created a Group object, use the following procedures toMARK=BULLETAdd members to a Group objectGive a Group object rights to files and directoriesDelete members from a Group objectYou can use either the NetWare Administrator or NETADMIN utility to manage Group objects. Both procedures are documented in this section.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"GroupsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Group object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Object and property rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM92449""Rights Needed to Create and Manage Objects" on page 31COLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=62 ID="BP46"RENDERAS="SECT3"Adding Members to a Group Object Using NetWare AdministratorRENDERAS="SECT4"IDXID="w7587"BOOK="_idx" COLLECTION="nw41" TIDREF="i1617"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorAt minimum, the Write right to the Members property of the Group objectAt minimum, the Write right to the Security Equal To property of the User objectAt minimum, the Write right to the ACL property of the Group objectThe Group object must already exist, and the User objects you want to add as members of the Group must already existRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select the Group object you want to edit.For information on moving around in th
e browser and selecting objects, press 
MOREINFO="NONE"<F1>.PERFORMANCE="REQUIRED"Choose "Details
" from the
 "Object
" menu.PERFORMANCE="REQUIRED"Select the 
"Members
" button at the right side of the 
"Objec
t" dialog.PERFORMANCE="REQUIRED"Choose the 
"Add
" button to browse the Directory tree for User objects.PERFORMANCE="REQUIRED"Browse the Directory tree until the User object you want appears in the 
"Objects
" box.PERFORMANCE="REQUIRED"Choose "OK
."PERFORMANCE="REQUIRED"Repeat Steps 5 through 7 to add more User objects to the Group object.
PAGENUM=63 ID="BP47"PERFORMANCE="REQUIRED"When you have finished adding User objects to the Group object
, choose "OK
" to save your changes and return to th
e browser.RENDERAS="SECT3"Adding Members to a Group Object Using NETADMINRENDERAS="SECT4"IDXID="w7588"BOOK="_idx" COLLECTION="nw41" TIDREF="i1617"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Supervisor right to the Group object, or the Write or Supervisor right to the Members property of the Group objectThe Supervisor right to the Group object, or the Write or Supervisor right to the Security Equal To property of the User objectThe Supervisor or Write right to the ACL property of the Group and User objectsThe Group object must already exist, and the User objects you want to add as members of the Group must already existRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manag
e Objec
ts" from the "NETADMIN Options
" menu.PERFORMANCE="REQUIRED"Browse the Directory until the Group object appears on the screen.Use the instructions at the bottom of the screen to browse the directory. Press 
MOREINFO="NONE"<F1> if you need h
elp.PERFORMANCE="REQUIRED"When the Group object appears in the 
"Object
" list, select it and pres
s MOREINFO="NONE"<F10>.The 
"Actions
" menu appears.
PAGENUM=64 ID="BP48"PERFORMANCE="REQUIRED"Choose "View o
r Edi
t Properties o
f Thi
s Object
."PERFORMANCE="REQUIRED"Choose Grou
p members from the "View or Edit Group
" menu.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert> at th
e "Group Members" screen, and then press 
MOREINFO="NONE"<Insert> again to browse for the User object you want to add to the Group object.PERFORMANCE="REQUIRED"When the User object you want to add appears in the Directory, select it and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"When the selected User object appears in the "Members" screen, press 
MOREINFO="NONE"<Enter>.To select multiple User objects, us
e MOREINFO="NONE"<F5>.PERFORMANCE="REQUIRED"Continue to press 
MOREINFO="NONE"<Insert> and select User objects until you have added all the users you want as Group members.PERFORMANCE="REQUIRED"To save the list of Group members, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until you return to the "NETADMIN Options
" menu.RENDERAS="SECT3"Giving Group Object Rights to Files and Directories Using NetWare AdministratorRENDERAS="SECT4"IDXID="w7589"BOOK="_idx" COLLECTION="nw41" TIDREF="i1617"
PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Read object right to the Volume objectRights to the file systemPAGENUM=65 ID="BP49"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select the Group object you want to edit.For information on moving around i
n the browser and selecting objects, press 
MOREINFO="NONE"<F1>.PERFORMANCE="REQUIRED"Choose "Details
" from the "Object
" menu.PERFORMANCE="REQUIRED"Select the 
"Rights to File System
" button on the right side of the 
"Objec
t" dialog.PERFORMANCE="REQUIRED"To select a volume
, select "Include.
"A list of volumes appears in th
e "Select Objec
t" box. Or, you can browse the Directory for a volume.PERFORMANCE="REQUIRED"From the 
"Volumes
" list, select the volume that contains the directory or file.PERFORMANCE="REQUIRED"Choose "Add.
"PERFORMANCE="REQUIRED"Select the volume that contains the directory or file you want to grant rights to.PERFORMANCE="REQUIRED"From the "Files and Directories" dialog, select the directory or file that you want to grant rights t
o.The default rights that make up this object's trustee assignment to the file or directory appear in the
" Rights
" area.PERFORMANCE="REQUIRED"Select the check boxes next to the rights that you want to add.You must have the Access Control right to the file or directory to make trustee assignments to the file or directory.PERFORMANCE="REQUIRED"Choose "OK.
"The new trustee assignment is now effective for this object.
PAGENUM=66 ID="BP50"RENDERAS="SECT3"Giving Group Object Rights to Files and Directories Using NETADMINRENDERAS="SECT4"IDXID="w7590"BOOK="_idx" COLLECTION="nw41" TIDREF="i1617"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Read object right to the Volume objectRights to the file systemRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manage Objects
" from th
e "NETADMIN Options" 
menu.PERFORMANCE="REQUIRED"Browse the Directory until the Group object appears on the screen.Use the instructions at the bottom of the screen to browse the directory. Press 
MOREINFO="NONE"<F1> if you need h
elp.PERFORMANCE="REQUIRED"When the Group object appears in the 
"Object
" list, select it and pres
s MOREINFO="NONE"<F10>.The 
"Actions
" menu appears.PERFORMANCE="REQUIRED"Choose "View or Edi
t Rights t
o Files an
d Directories.
"PERFORMANCE="REQUIRED"Select a Volume where you want to make the Group object the trustee of a directory or file.Press 
MOREINFO="NONE"<Insert> to type the Volume object name or press 
MOREINFO="NONE"<Insert> twice to browse the Directory.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert> to type a beginning pathname to the directories in which you want to make trustee assignments, or press 
MOREINFO="NONE"<Insert> again to browse for the path.
PAGENUM=67 ID="BP51"PERFORMANCE="REQUIRED"Select 
"Directories/Files
" and press 
MOREINFO="NONE"<Enter>.Choose whether you want to view files, directories, or both when you are selecting one to give a trustee assignment to.PERFORMANCE="REQUIRED"Select 
"Trustee Search Depth
" and press 
MOREINFO="NONE"<Enter>.Choose whether you want to view only the files or directories in the current directory, or to search subdirectories.PERFORMANCE="REQUIRED"T
o list the trustee assignments, press 
MOREINFO="NONE"<F10>.The "Trustee Directory Assignments" screen appears.PERFORMANCE="REQUIRED"To select a directory or file in which the Group object should be added as a trustee, press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"To accept the directory you specified earlier, press 
MOREINFO="NONE"<Enter>; or, to browse fo
r fi
le system directories
, press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"To add or delete the rights granted, select "Trustee Directory Assignments" and press 
MOREINFO="NONE"<Enter>.The 
"Trustee Rights Granted" menu appears.PERFORMANCE="REQUIRED"To view or add rights that are not yet granted, press 
MOREINFO="NONE"<Insert>.Press 
MOREINFO="NONE"<F1> if you h
elp.PERFORMANCE="REQUIRED"To save the trustee assignments, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Continue selecting directories and files and granting rights until finished.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until you return to the "NETADMIN Options" 
menu.
PAGENUM=68 ID="BP52"RENDERAS="SECT3"Deleting Members from a Group Object Using NetWare AdministratorRENDERAS="SECT4"IDXID="w7591"BOOK="_idx" COLLECTION="nw41" TIDREF="i1617"
PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Supervisor right to the Group object, or the Write or Supervisor right to the Members property of the Group objectThe Supervisor right to the Group object, or the Write or Supervisor right to the Security Equal To property of the User objectThe Supervisor or Write right to the ACL property of the Group and User objectsRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select the Group object you want to edit.For information on moving around in th
e browser and selecting objects, pres
s MOREINFO="NONE"<F1>.PERFORMANCE="REQUIRED"Choose "Details
" from the "Object
" menu.PERFORMANCE="REQUIRED"Select the 
"Members
" button at the right side of the 
"Object
" dialog
.The list of User objects for this group appears.PERFORMANCE="REQUIRED"ID="FM88158"From the 
"Members" dialog, select the name you want to delete.PERFORMANCE="REQUIRED"Choose "Delete."PERFORMANCE="REQUIRED"If you want to delete other names, continue selecting names and choosing "Delete."You can delete several users at a time by holding down the button on the mouse, dragging the mouse arrow over the names, and choosing "Delete."PAGENUM=69 ID="BP53"PERFORMANCE="REQUIRED"When you have finished deleting members, 
ID="FM68213"choose "OK" to save your changes and return to the browser.RENDERAS="SECT3"ID="FM76149"Deleting Members from a Group Object Using NETADMINRENDERAS="SECT4"IDXID="w7592"BOOK="_idx" COLLECTION="nw41" TIDREF="i1617"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Supervisor right to the Group object, or the Write or Supervisor right to the Members property of the Group objectThe Supervisor right to the Group object, or the Write or Supervisor right to the Security Equal To property of the User objectThe Supervisor or Write right to the ACL property of the Group and User objectsRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manage Objects" from the "NETADMIN Options" menu.PERFORMANCE="REQUIRED"Browse the Directory until the Group object appears on the screen.Use the instructions at the bottom of the screen to browse the directory. Press 
MOREINFO="NONE"<F1> if you need help.PERFORMANCE="REQUIRED"When the Group object appears in the 
"Object
" list, select it and pres
s MOREINFO="NONE"<F10>.The 
"Actions
" menu appears.PERFORMANCE="REQUIRED"Choose "View or Edit Properties of This Object."PERFORMANCE="REQUIRED"Select Group members from the "View or Edit Groups" menu.
PAGENUM=70 ID="BP54"PERFORMANCE="REQUIRED"Select the User object you want to delete from the Group object and press 
MOREINFO="NONE"<Delete>.To select multiple User objects, us
e MOREINFO="NONE"<F5>.PERFORMANCE="REQUIRED"To confirm the deletion
, choose "Yes.
"PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until you return to th
e "NETADMIN Options" 
menu
.RENDERAS="SECT2"ID="FM60968"Managing Profile ObjectsIDXID="w7593"BOOK="_idx" COLLECTION="nw41" TIDREF="i3567"
Profile objects contain login scripts that are used by groups of users who need similar work environments but who are not located in the same container object.When a Profile object is named in a User object, the login script contained in the Profile object is executed when the user logs in, after any login script in the Organization or Organizational Unit has executed.Users can have only one Profile, so only one profile script can execute for any user.For information about creating a login script, see IDREF="FM34948"Chapter 3, "Creating Login Scripts."For an example of a login script used in a Profile object, see IDREF="FM13871""Profile Login Script" on page 250.You can use either the NetWare Administrator or NETADMIN utility to create a Profile object. Both procedures are documented in this section.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Profile objectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Profile object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Creating login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM34948"Chapter 3, "Creating Login Scripts."COLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=71 ID="BP55"RENDERAS="SECT3"Creating Profile Objects Using NetWare AdministratorRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Create object right to the object that will contain the new Profile objectRENDERAS="SECT4"IDXID="w7594"BOOK="_idx" COLLECTION="nw41" TIDREF="i3567"
ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select the object that will contain the new Profile object.For information on moving around i
n the browser and choosing objects, press 
MOREINFO="NONE"<F1>.Only Organization and Organizational Unit objects can contain Profile objects.PERFORMANCE="REQUIRED"Choose "Create
" from the "Object
" menu.PERFORMANCE="REQUIRED"Select "Profil
e" from the "New Object
" 
dialog.The 
"Create Profil
e" dialog appears.If Profile does not appear under 
"New Object,
" you cannot create Profile objects in this containe
r. Select or create another object to contain the Profile object
.PERFORMANCE="REQUIRED"Choose "OK."PERFORMANCE="REQUIRED"Type the Profile object name in the box provided.PERFORMANCE="REQUIRED"(Optional) Select 
"Define additional properties
."Select this option if you want to write a Profile login script or supply additional information about the new Profile object. Instructions for creating a Profile script are i
n IDREF="FM34948"Chapter 3, "Creating Login Scripts."PERFORMANCE="REQUIRED"Choose "Create.
"PAGENUM=72 ID="BP56"If you selected 
"Define Additional Properties,
" the 
"Identificatio
n" dialog appears.PERFORMANCE="REQUIRED"(Optional) Enter information in the fields provided in the 
"Identification
" page of the 
"Objec
t" dialog.PERFORMANCE="REQUIRED"(Optional
) Select the 
"See Also
" button at the right side of the objec
t dialog.The 
"See Also
" page allows you to add information about the Profile object you are creating. For example, you might list the User objects to whom you have assigned this script.Choose "Help
" at any time for information on the current task.PERFORMANCE="REQUIRED"(Optional
) Choose the 
"Login Scri
pt" page at the right side of the objec
t dialog to add commands to the Profile login script
.Use this page to specify commands that execute when a user logs in, such as a drive mapping.PERFORMANCE="REQUIRED"To save the new Profile object and return to the browser, choose 
"OK.
"RENDERAS="SECT3"Creating Profile Objects Using NETADMINRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Create object right to the object that will contain the new Profile objectRENDERAS="SECT4"IDXID="w7595"BOOK="_idx" COLLECTION="nw41" TIDREF="i3567"
ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manage Objects" from th
e "NETADMIN Options" 
menu.
PAGENUM=73 ID="BP57"PERFORMANCE="REQUIRED"Select the object that will contain the new Profile object
.The objects in the selected container are listed. To see if you're in the right context, look at the title bar on the screen
.Press 
MOREINFO="NONE"<F1> if you need h
elp.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"Select "Profile.
"If the Profile object class does not appear, you cannot create that object in the selected container. Press 
MOREINFO="NONE"<Esc> to return to th
e browser, and then select a different container type
.PERFORMANCE="REQUIRED"Type the new Profile object name and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"If you want to create another Profile object
, choose "Yes.
" If you do not
, choose "No."If yo
u chose "Ye
s" you are prompted to type the new Profile object name. Repeat Steps 3 through 7, and then continue with Step 8.If yo
u chose "No,
" then the Profile object is displayed in the Directory tree. Continue with Step 8.PERFORMANCE="REQUIRED"To edit this object, press 
MOREINFO="NONE"<F10>.A menu appears from which you can choose to view or edit information about this object.PERFORMANCE="REQUIRED"Choose "View or Edit Properties of This Object."PERFORMANCE="REQUIRED"Choose "Login Script.
"PERFORMANCE="REQUIRED"To ente
r commands for this Profile login script
, choose "No
" or, to copy a login script from another Profile object
, choose "Yes
."The commands you place in the Profile login script are executed when users who belong to this Profile object log in.For information on the commands, press 
MOREINFO="NONE"<F1> o
r see 
IDREF="FM27425""Login Script Commands and Variables" on page 194.PERFORMANCE="REQUIRED"To save your changes, press 
MOREINFO="NONE"<F10>.
PAGENUM=74 ID="BP58"PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until you return to th
e "NETADMIN Options" 
menu
.RENDERAS="SECT2"Managing Organizational Role ObjectsIDXID="w7596"BOOK="_idx" COLLECTION="nw41" TIDREF="i3118"
An Organizational Role object allows you to assign rights to a particular position rather than to the person who occupies that position. The people who occupy that position may change frequently, but the responsibilities of the position do not.The user assigned to an Organizational Role is called the occupant and is granted all rights that are granted to the Organizational Role object.When a user is added to the occupant list of an Organizational Role object, the Organizational Role is listed in that user's Security Equal To property.Security Equal To is a property of every User object that lists other objects. The user is granted all rights that any object (User, Group, Printer, etc.) in that list is granted, both to objects and to files and directories.You can use the NetWare Administrator or NETADMIN utility to create an Organizational Role object. Both procedures are documented in this section.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Organizational Role objectCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Organizational Role object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Security equivalenceCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Security Equal To" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=75 ID="BP59"RENDERAS="SECT3"Creating Organizational Role Objects Using NetWare AdministratorRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Create object right to the object that will contain the new Organizational Role objectRENDERAS="SECT4"IDXID="w7597"BOOK="_idx" COLLECTION="nw41" TIDREF="i3118"
ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select the object that will contain the new Organizational Role object.For information on moving around in th
e browser and selecting objects, press 
MOREINFO="NONE"<F1>.Only Organization and Organizational Unit objects can contain Organizational Role objects.PERFORMANCE="REQUIRED"Choose "Create
" from the "Object
" menu.PERFORMANCE="REQUIRED"Select "Organizational Role" from the "New Objec
t" dialog.If "Organizational Role" does not appear under "New Object," you cannot create Organizational Role objects in this container. Select or create another object to contain the Organizational Role object.PERFORMANCE="REQUIRED"Choose "OK.
"The 
"Create Organizational Rol
e" dialog appears.PERFORMANCE="REQUIRED"Type the Organizational Role object name in the box provided.PERFORMANCE="REQUIRED"(Optional) 
"Select Defin
e Additiona
l Properties.
"PERFORMANCE="REQUIRED"Select the 
"Create
" button at the bottom of the window.PERFORMANCE="REQUIRED"Enter information in the fields provided in the 
"Identificatio
n" dialog.The 
"Identification
" page of the 
"Object
" dialog appears.
PAGENUM=76 ID="BP60"PERFORMANCE="REQUIRED"Select the button to the right of 
"Occupant.
"PERFORMANCE="REQUIRED"Choose "Ad
d."The 
"Select Object
" window appears.PERFORMANCE="REQUIRED"Select User objects from the 
"Directory Context
" window until the objects you want are shown in the 
"Object
" window.PERFORMANCE="REQUIRED"Select the User object in the left window to occupy the Organizational Role; the
n choose "OK.
"The object you selected appears in the
" Occupant
" window.PERFORMANCE="REQUIRED"Choose "OK
" in the 
"Occupant
" window.PERFORMANCE="REQUIRED"When you are finished adding User objects as Occupants
, choose "OK
" in the 
"Organizational Role
" window.PERFORMANCE="REQUIRED"(Optional
) Select the 
"See Als
o" button at the right side of the objec
t dialog.The 
"See Also
" page allows you to add information about the Organizational Role object you are creating. For example, you might list the User objects that you have assigned as occupants.PERFORMANCE="REQUIRED"To save the new Organizational Role object and return to th
e browser, choose "OK
."RENDERAS="SECT3"Creating Organizational Role Objects Using NETADMINRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Create object right to the object that will contain the new Organizational Role objectPAGENUM=77 ID="BP61"RENDERAS="SECT4"IDXID="w7598"BOOK="_idx" COLLECTION="nw41" TIDREF="i3118"
ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manage Objects" from th
e "NETADMIN Options" 
menu.PERFORMANCE="REQUIRED"Select the object that will contain the new Organizational Role object
.The objects in the selected container are listed. To see if you're in the right context, look at the title bar on the screen
.Press 
MOREINFO="NONE"<F1> if you need h
elp.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"Select "Organizational Role."If th
e Organizational Role 
object class does not appear, you cannot create that object in the selected container. Press 
MOREINFO="NONE"<Esc> to return to th
e browser, and then select a different container type
.PERFORMANCE="REQUIRED"Type the new Organizational Role object name
.PERFORMANCE="REQUIRED"Type the Mailbox Location and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"If you want to create another Organizational Role object
, choose "Yes.
" If you do not
, choose "No."If yo
u chose "Yes,
" you are prompted to type the new Organizational Role object name. Repeat Step 6 and then continue with Step 8.If yo
u chose "No," then the Organizational Role object is displayed in the Directory tree. Continue with Ste
p 9.PERFORMANCE="REQUIRED"To edit this object, press 
MOREINFO="NONE"<F10>.A menu appears from which you can choose to view or edit information about this object.
PAGENUM=78 ID="BP62"PERFORMANCE="REQUIRED"Choose "View or Edit Properties of This Object."PERFORMANCE="REQUIRED"Choose "Identification
" from the "View or Edit Organizational Role
" menu.PERFORMANCE="REQUIRED"Specify a User object for the Organizational Role.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the field next to "Occupant" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"Type the complete name of a User object in the space provided, or press
MOREINFO="NONE" <Insert> to browse the Directory and select a User object to be the occupant of the Organizational Role.The path from the object to the root of the tree forms the object's complete name.PERFORMANCE="REQUIRED"Select additional User objects as needed.PERFORMANCE="REQUIRED"To save the list of occupants, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Enter information in other fields as needed.PERFORMANCE="REQUIRED"To save changes, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> to return to th
e "NETADMIN Options" 
menu
.RENDERAS="SECT2"ID="FM88652"IDXID="w7599"BOOK="_idx" COLLECTION="nw41" TIDREF="i4720"
Managing User TemplatesA user template contains default information that you can apply to User objects to give them default property values.You can create a user template in an Organization or Organizational Unit object either when you create the container object or later on.Then, when you create a User object, you are prompted to use the defaults in the user template. If you do, the property values you entered in the user template, such as login time restrictions, password restrictions, etc., are copied into the User object's properties.PAGENUM=79 ID="BP63"The user template is actually a User object named USER_TEMPLATE. You enter information in this User object just as you would for any other User object. However, not all properties of a User object can be copied from a user template.When you create a user template, you can copy information from the parent container's user template. For example, if you create a user template in SALES.NOVELL, you are prompted to copy the user template from NOVELL, if one exists. Using this feature, you can avoid having to reenter similar information for lower-level containers.User template information is taken from the nearest parent container. If the container object in which you create a User object does not have a user template, you can apply the parent container's user template to the User object.When working with user templates, remember the following:MARK=BULLETChanging values in a user template does not change those values in existing User objects. The changes apply only to User objects created after the user template values have been changed.To update information for existing users, you must enter the changes for each User object.You cannot use a user template to grant NDS or file system rights.You can use the NetWare Administrator or NETADMIN utility to create a user template. Both procedures are documented in this section.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"User defaultsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"User template" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"User objectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"User object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=80 ID="BP64"RENDERAS="SECT3"Creating and Editing User Templates with NetWare AdministratorRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Create object right to the container object that will contain the user templateRENDERAS="SECT4"IDXID="w7600"BOOK="_idx" COLLECTION="nw41" TIDREF="i4720"
ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select the object that will contain the new user template.For information on moving around in th
e browser and selecting objects, pres
s MOREINFO="NONE"<F1>.Only Organization and Organizational Unit objects can contain User objects.PERFORMANCE="REQUIRED"Choose "User Defaults
" from th
e "Object" menu.PERFORMANCE="REQUIRED"If you want the new user template to inherit the properties from the parent container's user template
, choose "Yes.
" If not
, choose "No.
"If there is no parent container, you are not given this prompt. Continue with Step 5.If yo
u chose "Yes
," a USER_TEMPLATE User object is created and the first page of defaults,
" Identification,
" appears with the same information that is in the parent container's user template.If yo
u chose "No
," a USER_TEMPLATE User object is created and the first page of defaults, "Identification," appears.PERFORMANCE="REQUIRED"(Optional) On the 
"Identification
" page, enter or change the information that you want to apply to new User objects
.For example, the location for all User objects to which you will apply the user template might be New York. You would then type "New York" in the 
"Location
" field.
PAGENUM=81 ID="BP65"PERFORMANCE="REQUIRED"Select other USER_TEMPLATE pages as needed and enter the template information.PERFORMANCE="REQUIRED"To save the user template and return to th
e browser, choose "OK.
"RENDERAS="SECT3"Creating and Editing User Templates with NETADMINRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterThe Create object right to the container object that will contain the user templateRENDERAS="SECT4"IDXID="w7601"BOOK="_idx" COLLECTION="nw41" TIDREF="i4720"
ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manage Objects" from th
e "NETADMIN Options" 
menu.PERFORMANCE="REQUIRED"Browse the Directory tre
e to find and select the container object in which you want to add a new container object
.The objects in the selected container are listed.To see if you're in the right context, look at the title bar on the screen. Press 
MOREINFO="NONE"<F1> for help.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"From the "Select an Object Class" screen, select the container type that you want to creat
e.If the container object class you want to create does not appear, you cannot create that object in the selected container. Press 
MOREINFO="NONE"<Esc> to return to th
e browser, and then select a different container type
.PAGENUM=82 ID="BP66"PERFORMANCE="REQUIRED"Type the new container object name and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"If you want to create a user template to be applied to new User objects created in this container, type 
"Y
" and press 
MOREINFO="NONE"<Enter>.You are not prompted to create a user template if you are creating a Country container object.PERFORMANCE="REQUIRED"Choose "View or Edit Properties of This Object."PERFORMANCE="REQUIRED"Choose "Edi
t Templat
e User
."The 
"View o
r Edi
t User
" screen appears.PERFORMANCE="REQUIRED"Enter or change the values of the user template as needed.The help line at the bottom of the screen gives information on each of the options as you highlight them
.For more information, press 
MOREINFO="NONE"<F1>.PERFORMANCE="REQUIRED"To save the informatio
n, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until you return to th
e "NETADMIN Options" 
menu
.RENDERAS="SECT1"Searching for ObjectsWhen you want to find information in the Directory database without opening numerous containers to view the objects, you can use the Search feature.With the Browse object right, you can search for object classes anywhere in the Directory tree. With the Compare property right, you can search for objects with properties that match a particular value.You can search for objects using the NetWare Administrator, NETADMIN, or NLIST utility. All three procedures are documented in this section.PAGENUM=83 ID="BP67"RENDERAS="SECT2"Searching for Objects Using NetWare AdministratorIDXID="w7602"BOOK="_idx" COLLECTION="nw41" TIDREF="i3982"
The NetWare Administrator utility searches each object in the Directory database unless you narrow the search by specifying properties in combination with additional variables such as "less than" or "equal to."For example, to find all users in New York, you could search for User objects with State or Province Name "equal to" New York. The Search feature then displays objects that meet the search criteria.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Browse object right to the object you want to see in the searchRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select an object in the Directory tree where the search should start.PERFORMANCE="REQUIRED"Choose "Searc
h" from th
e "Object
" menu.A 
"Search
" window appears.PERFORMANCE="REQUIRED"Choose th
e browser icon (to the right of the 
"Star
t Fro
m" field) to select an object to start the search from.PERFORMANCE="REQUIRED"Specify how much of the Directory tree to search.
MARK=BULLETTo search everything below the "Start From" object, select "Search Entire Subtree."To search only among objects one level below the "Start From" object, do not select "Search Entire Subtree." Continue with Step 6.PAGENUM=84 ID="BP68"PERFORMANCE="REQUIRED"Select th
e down-arrow to the right of the "Search for" field to select an object class to search for.
MARK=BULLETChoose "OK" if you want all the objects of this selected object class to be listed.If you want only those objects having properties that match certain criteria to be listed, continue with Step 7.PERFORMANCE="REQUIRED"(Optional) Select th
e down-arrow to the right of the 
"Property
" field to select which property's value will be examined.The properties in this list change depending on which object class you selected in the
 "Searc
h for
" field.PERFORMANCE="REQUIRED"(Optional) Select how you want to compare a value to the selected property.You can select "Equal to," "Greater than," "Less than," or other choices.PERFORMANCE="REQUIRED"(Optional) Enter a value in the field to the right of the comparison method that you entered in Step 8.For example, if you are searching for a Profile object that has the value "Manager's Profile" in the Other Names property, you might select the property "Other Names," then use the comparison method "Equal T
o" and the value of "Manager's Profile.
"PERFORMANCE="REQUIRED"Choose "OK.
"Objects that match your selections are displayed in a 
"Search Results
" window
.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PropertiesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Property" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=85 ID="BP69"RENDERAS="SECT2"Searching for Objects Using NETADMINIDXID="w7603"BOOK="_idx" COLLECTION="nw41" TIDREF="i3982"NETADMIN searches each object in the Directory database unless you narrow the search by specifying properties in combination with additional variables such as "less than" or "equal to."For example, to find all users in New York, you could search for User objects with State or Province Name "equal to" New York. The Search feature then displays objects that meet the search criteria.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterThe Browse object right to the object you want to see in the searchRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manage According to Search Pattern
" from th
e "NETADMIN Options" 
menu.PERFORMANCE="REQUIRED"Enter the object name you wish to search on in the 
"Enter Object Name
" field, use * to view all objects, or limit the search by combining characters with the *.For example, if you want to view all objects whose names begin with 
"P,
" enter 
"P*
" in the 
"Enter Object Name
" field.PERFORMANCE="REQUIRED"Select the object class or classes you want to search on in the 
"Object Class
" field. To search on all object types, select 
"/All classes/.
"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to select the object classes.PERFORMANCE="REQUIRED"If the object classes you want to search on don't appear in the "Object Classes Included" screen, press MOREINFO="NONE"<Insert> to select additional object classes.
PAGENUM=86 ID="BP70"PERFORMANCE="REQUIRED"Choose 
"Yes
" in the 
"Show Alias Class
" field if you want to view an Alia
s object as a
n alias, and not as the object th
e alias represents.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<F10>.Objects that match your selections are displayed in the browse screen
.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PropertiesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Property" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceRENDERAS="SECT2"Searching for Objects Using NLISTNLIST is a workstation command IDXID="w7604"BOOK="_idx" COLLECTION="nw41" TIDREF="i3982"
line utility that allows you toMARK=BULLETList objects and object propertiesView information about users, groups, volumes, and servers (such as object properties, names, property groups, and login information)Search for objects and object properties (including groups of properties for objects) on NetWare 2 and NetWare 3 serversFor instructions on using NLIST, see "BOOK="utlrfenu" COLLECTION="nw41"NLIST" in Utilities Reference.PAGENUM=87 ID="BP71"RENDERAS="SECT1"ID="FM37086"Moving Objects in the Directory TreeIDXID="w7605"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"IDXID="w7606"BOOK="_idx" COLLECTION="nw41" TIDREF="i3054"
IDXID="w7607"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"IDXID="w7608"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"While previous versions of NetWare allowed you to move only leaf objects, NetWare 4.1 allows you to move both leaf objects and container objects to other containers in the Directory tree.You can IDXID="w7609"BOOK="_idx" COLLECTION="nw41" TIDREF="i809"
move a container object only if it is the root of a NetWare Directory Services (NDS) partition that has no subordinate partitions.When you move a container object, IDXID="w7610"BOOK="_idx" COLLECTION="nw41" TIDREF="i152"
create an alias object that points to the container object you're moving. Then users can continue logging in to the network and finding the container object (and the objects it contains) in its original Directory location.If you move a container object and do not create an alias, users who are unaware of the object's new location will not easily find the object in the Directory tree, since they will look for it in its original Directory location.Also, users may not be able to log in if the name context in their configuration file (NET.CFG file) references the moved container.When you move a leaf or container object, NDS changes all references to the moved object. Although the object's common name remains unchanged, the context name of the object (and of all its subordinates) changes.Because the context of a container object changes when you move it, users whose name context in their configuration file (NET.CFG file) references the moved container need to update their NET.CFG so that it references the container's new name.To automatically update users' NET.CFG file with a new name context after you move a container object, use the IDXID="w7611"BOOK="_idx" COLLECTION="nw41" TIDREF="i2625"
NCUPDATE utility. For instructions, see "BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities Reference.You can use NetWare Administrator or NETADMIN to move objects in the Directory tree. Both procedures are documented in this section.PAGENUM=88 ID="BP72"RENDERAS="SECT2"Moving Leaf Objects Using NetWare AdministratorIDXID="w7612"BOOK="_idx" COLLECTION="nw41" TIDREF="i3054"IDXID="w7613"BOOK="_idx" COLLECTION="nw41" TIDREF="i2101"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Supervisor right o the object you want to moveThe Create object right to the destination containerRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager or the OS/2 desktop, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the browser window, select one or more leaf objects.To select multiple leaf objects, pres
s MOREINFO="NONE"<Ctrl> o
n the keyboard and, without releasing MOREINFO="NONE"<Ctrl>, select the objects with the mouse.PERFORMANCE="REQUIRED"From the "Object
" menu, choose "Move.
"PERFORMANCE="REQUIRED"Select the browser button to the right of the "Destination
" box.The "Directory Context
" box appears in the lowe
r right corner of the screen. Use this field to browse the Directory tree's containers.The "Objects
" box that appears in the lowe
r left corner shows the containers that appear when you browse the Director
y.PERFORMANCE="REQUIRED"From the "Objects
" box, select a container object (an Organization or Organizational Unit) as the place to move the objects to; then choose "OK.
"PERFORMANCE="REQUIRED"In the "Move
" dialo
g, choose "OK.
"The listed objects are moved to the destination container
.PAGENUM=89 ID="BP73"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory tree" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsRENDERAS="SECT2"Moving Leaf Objects Using NetWare Administrator (Drag-and-Drop)IDXID="w7614"BOOK="_idx" COLLECTION="nw41" TIDREF="i2527"IDXID="w7615"BOOK="_idx" COLLECTION="nw41" TIDREF="i2101"IDXID="w7616"BOOK="_idx" COLLECTION="nw41" TIDREF="i3054"IDXID="w7617"BOOK="_idx" COLLECTION="nw41" TIDREF="i809"IDXID="w7618"BOOK="_idx" COLLECTION="nw41" TIDREF="i2101"NetWare Administrator allows you to move an object to a different location in the Directory tree using the drag-and-drop method.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Supervisor right to the object you want to moveThe Create object right to the destination containerRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"(Optional) From the "Tools" menu, open another browser window by selecting "Browse.
"If you can see both the object and the destination container in one browser window, it is not necessary to open two browser windows. Go directly to Step 4.PERFORMANCE="REQUIRED"Reshape the browser windows, using the window borders, so that you can view both windows at once.PERFORMANCE="REQUIRED"From one of the browser windows, select one or more leaf objects.
PAGENUM=90 ID="BP74"To select multiple leaf objects, pres
s MOREINFO="NONE"<Ctrl> o
n the keyboard and, without releasing MOREINFO="NONE"<Ctrl>, select the objects with the mouse.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Ctrl> on the keyboard and, without releasing 
MOREINFO="NONE"<Ctrl>, click and hold down on the object(s) and drag the object(s) to the destination container; then release the mouse button.PERFORMANCE="REQUIRED"In the "Move
" dialog, choose "OK.
"The listed objects are moved to the destination container
.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory tree" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT2"Moving Leaf Objects Using NETADMINIDXID="w7619"BOOK="_idx" COLLECTION="nw41" TIDREF="i3054"IDXID="w7620"BOOK="_idx" COLLECTION="nw41" TIDREF="i2101"IDXID="w7621"BOOK="_idx" COLLECTION="nw41" TIDREF="i2527"
IDXID="w7622"BOOK="_idx" COLLECTION="nw41" TIDREF="i2527"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Create object right to the destination containerThe Supervisor right to the object you want to moveRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utilit
y.PAGENUM=91 ID="BP75"PERFORMANCE="REQUIRED"From th
e "NETADMIN Options" menu, choose "Manage Objects.
"Your current context appears in the uppe
r left corner.PERFORMANCE="REQUIRED"Select the object that you want to mov
e.MARK=BULLETIf the object you want to move appears on the list, select it and press MOREINFO="NONE"<F10>.If the object is not on the list, browse the Directory by selecting container objects and pressing MOREINFO="NONE"<Enter> until you see the object you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"From the "Actions
" menu, choose "Move.
"PERFORMANCE="REQUIRED"U
sing th
e Down-arrow key 
to reach the field, highlight the "New Context
" field.PERFORMANCE="REQUIRED"Assign a new context to the object you want to mov
e.MARK=BULLETIf you know the new context that you want the object to be in, type the new context in the highlighted field.If you don't know the new context that you want the object to be in, press MOREINFO="NONE"<Insert> twice to browse the Directory for the destination container; then select the destination container and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"To accept the new context as the destination container, press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"To confirm that you want to move the object listed in the "Old Context
" field to the container listed in the "New Context
" field, press 
MOREINFO="NONE"<F10>.The selected object is moved to the destination container.You need to wait for processes throughout the Directory to be completed before you can move this object again.PAGENUM=92 ID="BP76"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory tree" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceRENDERAS="SECT2"ID="FM44519"Moving Container Objects Using NetWare AdministratorIDXID="w7623"BOOK="_idx" COLLECTION="nw41" TIDREF="i3054"IDXID="w7624"BOOK="_idx" COLLECTION="nw41" TIDREF="i809"IDXID="w7625"BOOK="_idx" COLLECTION="nw41" TIDREF="i2527"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Supervisor right to the object you want to moveThe Create object right to the destination containerRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager or the OS/2 desktop, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From th
e "Tools
" menu, choose "Partition Manager.
"PERFORMANCE="REQUIRED"From the "Partition Manager
" browser, select the partition that you want to move.You can move a container object only if it is the root of 
a NetWare Directory Services (NDS) partition, and only if it contains no subordinate partitions.In Partition Manager, the partition icon appears to the left of the object icon. If the container you want to move is not a partition, select the container and choose "Create as New Partition."PERFORMANCE="REQUIRED"From the "Object
" menu, choose "Move Partition.
"PERFORMANCE="REQUIRED"Select the browser button to the right of the "Destination
" box.
PAGENUM=93 ID="BP77"Use the browser in the "Directory Context
" box to view the Directory tree's containers.The "Objects
" bo
x that appears in the lowe
r left corner shows the containers that you select in the "Directory Context
" box.PERFORMANCE="REQUIRED"From the "Objects
" box, select a container object (an Organization or Organizational Unit) as the place to move the listed objects to; then choose "OK.
"PERFORMANCE="REQUIRED"Choose "Create Alias in Place of Moved Container.
"The alias object will point to the partition's new location.If you move a container object and do not create an alias, users who are unaware of the object's new location will not easily find the object in the Directory tree, since they will look for it in its original Directory location.Also, users may not be able to log in if the name context in their configuration file (NET.CFG file) references the moved container.PERFORMANCE="REQUIRED"In the "Move
" dialog, choose "OK.
"If you chose to create an alias in place of the moved container, NetWare Administrator polls for the creation of the alias object before it moves the selected partition.If you moved a container and created an alias in its place, you should use the NCUPDATE utility to update the name context of users in the moved container. For instructions, see "
BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in 
Utilities Reference.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Alias objectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Alias object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory tree" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NCUPDATECOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferencePAGENUM=94 ID="BP78"RENDERAS="SECT2"ID="FM36317"Moving Container Objects Using NETADMINIDXID="w7626"BOOK="_idx" COLLECTION="nw41" TIDREF="i3054"IDXID="w7627"BOOK="_idx" COLLECTION="nw41" TIDREF="i809"IDXID="w7628"BOOK="_idx" COLLECTION="nw41" TIDREF="i2527"
IDXID="w7629"BOOK="_idx" COLLECTION="nw41" TIDREF="i2527"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Create object right to the destination containerRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility
.PERFORMANCE="REQUIRED"From th
e "NETADMIN Options" menu, choose "Manage Objects.
"Your current context appears in the uppe
r left corner.PERFORMANCE="REQUIRED"Select the object that you want to mov
e.MARK=BULLETIf the object you want to move appears on the list, select it and press MOREINFO="NONE"<F10>.If the object is not on the list, browse the Directory by selecting container objects and pressing MOREINFO="NONE"<Enter> until you see the object you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"From the "Actions
" menu, choose "Move.
"You can move a container object only if it is the root of a 
NetWare Directory Service
s (NDS) partition, and only if it contains no subordinate partitions.In 
NETADMIN, when you select a container object that is a partition, the context-sensitive help at the bottom of the screen reads "This is a partition."If the container you want to move is not a partition, you mus
t first use a partition management utility (PARTMGR or NetWare Administrator) and create the container as a new partition.PAGENUM=95 ID="BP79"PERFORMANCE="REQUIRED"U
sing th
e Down-arrow key 
to reach the field, highlight the "New Context
" field.PERFORMANCE="REQUIRED"Assign a new context to the object you want to mov
e.MARK=BULLETIf you know the new context that you want the object to be in, type the new context in the highlighted field.If you don't know the new context that you want the object to be in, press MOREINFO="NONE"<Insert> twice to browse the Directory for the destination container; then select the destination container and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"To accept the new context as the destination container, press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"To confirm that you want to move the object listed in the "Old Context
" field to the container listed in the "New Context
" field, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"To create an alias in place of the moved container, choose 
"Yes.
"If you don't create an alias, users who are unaware of the object's new location cannot easily find the object in the Directory tree, since they will look for it in its original Directory location.Also, users might not be able to log in if the name context in their configuration file (NET.CFG file) references the moved container.The alias object will point to the partition's new location.The selected object is moved to the destination container.You need to wait for processes throughout the Directory to be completed before you can move this object again.If you moved a container, and created an alias in its place, you should use the NCUPDATE utility to update the name context of users in the moved container. For instructions, see "BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities Reference.PAGENUM=96 ID="BP80"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory tree" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceRENDERAS="SECT1"ID="FM48449"Deleting Objects from the Directory TreeIDXID="w7630"BOOK="_idx" COLLECTION="nw41" TIDREF="i991"When you delete leaf objects, NetWare Directory Services (NDS) removes references to the deleted object. For example, if you delete a Profile object, that Profile object is deleted from any User objects that list it. Or, if you delete a User object, all trustee assignments listing that user are deleted.Some special considerations apply when you delete particular objects, such as a NetWare Server object, a User object, or an Alias object. These cautions are explained in the next three sections.You cannot undo a Delete Object operation. To get the object back, you must re-create it and reenter all data in its properties.You can use NetWare Administrator or NETADMIN to delete objects from the Directory tree. Both procedures are documented in this section.RENDERAS="SECT2"Cautions When Deleting NetWare Server ObjectsIDXID="w7631"BOOK="_idx" COLLECTION="nw41" TIDREF="i4055"IDXID="w7632"BOOK="_idx" COLLECTION="nw41" TIDREF="i991"
An NDS NetWare server is one that you have installed in the Directory tree. Any server that is not in the Directory tree is a bindery server.You can use NetWare Administrator or NETADMIN to delete bindery servers. But consider the following before you delete an NDS Server object:MARK=BULLETYou cannot delete a NetWare server from the Directory tree using the NETADMIN utility.You must use the Partition Manager tool in the NetWare Administrator utility to delete an NDS NetWare server from the Directory tree.PAGENUM=97 ID="BP81"If the server you want to delete contains a master replica, you must first change the master to a different type and designate another replica on another server as the master.RENDERAS="SECT2"Cautions When Deleting User ObjectsYou must be careful not to delete a trustee object which has the only trustee assignment to a part of the Directory tree. If you did, you could cut off access to that part of the Directory tree.IDXID="w7633"BOOK="_idx" COLLECTION="nw41" TIDREF="i4710"
You must also 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.Therefore, be aware of the following before you delete a User object:MARK=BULLETTo avoid losing access to any object, check the "Rights to Other Objects" and "Trustees of This Object" attributes of the User object you want to delete. To view these attributes, select the User object, and right-click once. Then select the attribute you want to view from the available options.If the User object you want to delete has the Supervisor right to another object, transfer that Supervisor right to another User object before you delete the original User object.Or, give a User object in a higher container object the Supervisor right to objects, and then block other users from deleting those objects.Do not delete user ADMIN until you have given another User object the same Supervisor right that ADMIN has.When you delete a User object, any security equivalences that you have assigned to other trustees are lost.When you delete a User object, the home directories and mail directories will not be deleted.PAGENUM=98 ID="BP82"RENDERAS="SECT2"Cautions When Deleting Alias ObjectsIDXID="w7634"BOOK="_idx" COLLECTION="nw41" TIDREF="i152"Be aware of the following before you delete an Alias object:MARK=BULLETIf you delete an alias object (which appears as the actual object it is pointing to), you only delete the alias object, not what it points to.When you delete an alias object, it does not affect the object that the alias object points to.If you delete the object that an alias object points to, the alias object is also deleted.RENDERAS="SECT2"ID="FM45304"Deleting Objects Using NetWare AdministratorIDXID="w7635"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"RENDERAS="SECT3"IDXID="w7636"BOOK="_idx" COLLECTION="nw41" TIDREF="i991"
PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Delete object right to the object that you want to deleteRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using th
e browser, select the object you want to delete.Only leaf objects and container objects that are empt
y can be deleted.PERFORMANCE="REQUIRED"Select (check
) the 
"Trustees o
f Thi
s Object
" and the 
"Rights t
o Othe
r Object
s" dialogs.If the User object you want to delete has the Supervisor right to another object, give another User object that Supervisor right before you delete the original User object.PERFORMANCE="REQUIRED"Choose "Delete
" from the "Object
" menu.You cannot undo an object deletion. To get the object back, you must re-create it and reenter all data in its properties.PERFORMANCE="REQUIRED"To confirm the deletion
, choose "OK."PAGENUM=99 ID="BP83"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT2"ID="FM59133"Deleting Objects Using NETADMINIDXID="w7637"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"RENDERAS="SECT3"IDXID="w7638"BOOK="_idx" COLLECTION="nw41" TIDREF="i991"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Delete object right to the object that you want to delete from the Directory treeRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manage Objects" from th
e "NETADMIN Options" 
menu.PERFORMANCE="REQUIRED"Browse the Directory until the object you want to delete appears.Use the instructions at the bottom of the screen to browse the Directory. Press 
MOREINFO="NONE"<F1> if you need h
elp.PERFORMANCE="REQUIRED"Select the object and press 
MOREINFO="NONE"<Delete>.If the User object you want to delete has the Supervisor right to another object, give another User object that Supervisor right before you delete the original User object.PAGENUM=100 ID="BP84"You cannot undo an object deletion. To get the object back, you must re-create it and reenter all data in its properties.PERFORMANCE="REQUIRED"To confirm the deletion
, choose "Yes
."The object is deleted from the Directory tree
.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until you return to th
e "NETADMIN Options" 
men
uRENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceRENDERAS="SECT1"ID="FM86810"Renaming Leaf and Container ObjectsIDXID="w7639"BOOK="_idx" COLLECTION="nw41" TIDREF="i807"IDXID="w7640"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"IDXID="w7641"BOOK="_idx" COLLECTION="nw41" TIDREF="i3052"IDXID="w7642"BOOK="_idx" COLLECTION="nw41" TIDREF="i3780"
You may want to rename objects to make their names more descriptive or to reflect your changing environment. For example, you may want to rename a printer from LASER IN BLDG D to LASER IN BLDG A, or an Organizational Unit from SALES to ACCOUNTS.When you rename an object, NetWare Directory Services changes all references to the renamed object.Renaming a leaf object changes only the object's common name, which is the name that is displayed in the Directory tree. It does not change the object's context. However, renaming a container object changes the object's common name as well as its context.When renaming a container object, you should seriously consider creating an IDXID="w7643"BOOK="_idx" COLLECTION="nw41" TIDREF="i152"
alias object that points to the container object you're renaming. Then users can continue logging in to the network and can see the container object's original name.PAGENUM=101 ID="BP85"If you rename a container object and do not create an alias, users who are unaware of the object's new name will not easily find the object in the Directory tree, since they will look for its original name.Also, users may not be able to log in if the name context in their configuration file (NET.CFG file) references the renamed container.To automatically update users' NET.CFG file with a new name context after you rename a container object, you can place a command in the renamed container's login script that will run the IDXID="w7644"BOOK="_idx" COLLECTION="nw41" TIDREF="i2625"
NCUPDATE utility.RENDERAS="SECT2"Renaming Objects Using NetWare AdministratorIDXID="w7645"BOOK="_idx" COLLECTION="nw41" TIDREF="i3052"IDXID="w7646"BOOK="_idx" COLLECTION="nw41" TIDREF="i3780"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Rename object right to the object that you want to renameRENDERAS="SECT3"IDXID="w7647"BOOK="_idx" COLLECTION="nw41" TIDREF="i3780"
ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager or the OS/2 desktop, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"Using th
e browser, select the object that you want to rename
.PERFORMANCE="REQUIRED"From the "Object
' menu, choose "Rename.
"PERFORMANCE="REQUIRED"Typ
e the name you want to give to the object you selected.PERFORMANCE="REQUIRED"(Optional) Selec
t "Save Old Name.
"Select this option if you want the old name saved as a value in the "Other Names" field of the "Details
" scree
n.With the old name saved, users wh
o don't know the object's new name can search for the object under the old name.PERFORMANCE="REQUIRED"(Optional) If you are renaming a container object, selec
t "Create Alias in Place of Renamed Container
."If you don't create an alias, users who are unaware that the container has been renamed cannot easily find the object in the Directory tree. Also, users whose name context in their NET.CFG file references the renamed container might be unable to log in.PAGENUM=102 ID="BP86"PERFORMANCE="REQUIRED"To save the changes and return to th
e browser, choose "OK.
"If you renamed a container object, you shoul
d use the NCUPDATE utility to update the name context of users in the renamed container. For instructions, see "BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities Reference.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Alias objectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Alias object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory tree" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NCUPDATECOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT2"Renaming Objects Using NETADMINIDXID="w7648"BOOK="_idx" COLLECTION="nw41" TIDREF="i3780"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Rename object right to the object that you want to renameRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"From the "NETADMIN Options" 
menu, choose "Manage Objects
."Your current context appears in the uppe
r left corner
 of the screen.
PAGENUM=103 ID="BP87"PERFORMANCE="REQUIRED"Select the object that you want to renam
e.MARK=BULLETIf the object appears on the list, select it and press MOREINFO="NONE"<F10>.If the object is not on the list, browse the Directory by selecting container objects and pressing MOREINFO="NONE"<Enter> until you see the object you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "Rename
."PERFORMANCE="REQUIRED"In the "New Name
" field, enter a new name for the objec
t.PERFORMANCE="REQUIRED"Choose "Yes
" to save the old name
; choose "No
" to discard the old name.Choose "Yes
" if you want the old name s
aved as a value in the
" Other Names
" field of the "Details
" scree
n.With the old name saved, users who do not know the object's new name can search for the object under the old name.PERFORMANCE="REQUIRED"To save your changes, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"To confirm 
you want to save the new name
, choose "Yes.
"PERFORMANCE="REQUIRED"(Optional) To create an alias in place of the renamed container, choose "Yes.
"If you don't create an alias, users who are unaware that the container has been renamed cannot easily find the object in the Directory tree. Also, users whose name context in their NET.CFG file references the renamed container might be unable to log in.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until you return to th
e "NETADMIN Options" 
menu.If you renamed a container object, you shoul
d use the NCUPDATE utility to update the name context of users in the renamed container. For instructions, see "BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities Reference.
PAGENUM=104 ID="BP88"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Alias objectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Alias object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NCUPDATECOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceRENDERAS="SECT1"ID="FM99706"Changing Object Property ValuesIDXID="w7649"BOOK="_idx" COLLECTION="nw41" TIDREF="i3114"
You can use the NetWare Administrator or NETADMIN utility to change object property values.IDXID="w7650"BOOK="_idx" COLLECTION="nw41" TIDREF="i807"
In this section, the general procedures for changing object property values are followed by tables that describe how to change specific properties of specific objects.IDXID="w7651"BOOK="_idx" COLLECTION="nw41" TIDREF="i3121"
For a complete list of all
 properties for all objects, see Appendix A, "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties," in Utilities Reference.RENDERAS="SECT2"ID="FM38953"Changing Object Property Values Using NetWare AdministratorRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorThe Create object right to the container of the object whose property value will be changedRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PAGENUM=105 ID="BP89"PERFORMANCE="REQUIRED"From th
e browser, select the object whose property values you want to change.For information on moving around in th
e browser and selecting objects, choose the "Help" button.PERFORMANCE="REQUIRED"Choose "Details" from the "Object" menu.The "Identification" page appears.PERFORMANCE="REQUIRED"Make any necessary changes.See IDREF="FM24954"Table 1-8 and IDREF="FM25159"Table 1-9 for details on object property values you can change.Click on "Help" for details on each field and option.Do not choose "OK" until you have entered all the changes you want to make to every page of the object dialog.Do not choose "Cancel" unless you want to lose all changes made to every page of the object dialog.IDXID="w7652"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"IDREF="FM24954"Table 1-8 describes how to change User object property values.
IDXID="w7653"BOOK="_idx" COLLECTION="nw41" TIDREF="i4710"LABEL="1-8" PGWIDE=1 TOCENTRY="1"ID="FM24954" Changing User Object Property Value with NetWare AdministratorCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="14*"COLNAME=2 COLWIDTH="21*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Choose this page of the object dialog; then...VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Change the User's last name, other names, title, description, department, telephone number, fax number, or email addressCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Disable the User's accountCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "Login Restrictions," and select (check) "Account Disabled."COLNAME=1 ROTATE="0" MOREROWS="0"Change the User's passwordCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "IDXID="w7654"BOOK="_idx" COLLECTION="nw41" TIDREF="i3245"
Password Restrictions," choose "Change Password," and then enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Set the User's IDXID="w7655"BOOK="_idx" COLLECTION="nw41" TIDREF="i63"
account expiration date or number of concurrent connectionsCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "Login Restrictions," check "Account Has Expiration Date" or "Limit Concurrent Connections," and then enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change the User's password restrictions (password length, periodic changes, uniqueness, grace logins)COLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "Password Restrictions," and enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Restrict the User's login timesCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "Login Time Restrictions," and choose the days and hours that the User is restricted from logging in to the network.COLNAME=1 ROTATE="0" MOREROWS="0"Set the User's login address restrictionsCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "Network Address," select the appropriate protocol, choose "Add," and then enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change the User'sIDXID="w7656"BOOK="_idx" COLLECTION="nw41" TIDREF="i2211"
 login scriptCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "Login Script," and enter login script commands.COLNAME=1 ROTATE="0" MOREROWS="0"Specify the User's Profile login scriptCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "Login Script," choose the browser button next to the "Profile" field, and then select a new Profile object from the "Select Object" dialog.COLNAME=1 ROTATE="0" MOREROWS="0"Add the User to an existing GroupCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "Group Membership," choose "Add," and then select a Group from the "Select Object" dialog.COLNAME=1 ROTATE="0" MOREROWS="0"Unlock a User's accountCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "Intruder Lockout," and enter information in fields to reset the User's account.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7657"BOOK="_idx" COLLECTION="nw41" TIDREF="i1889"
View, reset, or set up intruder detection on a user's accountCOLNAME=2 ROTATE="0" MOREROWS="0""Details"; then choose "Intruder Lockout," and view or reset information in fields to detect intruder attempts.To set up intruder detection, you must go to the "Details" page of the container that the users reside in; then choose "Intruder Detection," and enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7658"BOOK="_idx" COLLECTION="nw41" TIDREF="i94"
Change a User's mailing addressCOLNAME=2 ROTATE="0" MOREROWS="0""IDXID="w7659"BOOK="_idx" COLLECTION="nw41" TIDREF="i3345"
Postal Address"; then enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Set up the User's IDXID="w7660"BOOK="_idx" COLLECTION="nw41" TIDREF="i3999"
security equivalencesCOLNAME=2 ROTATE="0" MOREROWS="0""Security Equivalence"; then choose "Add," and select an object from the "Select Object" dialog.PAGENUM=107 ID="BP90"IDREF="FM25159"Table 1-9 describes how to change other objec
t property values.LABEL="1-9" PGWIDE=1 TOCENTRY="1"ID="FM25159" Changing Other Object Property Values with NetWare AdministratorCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Select this class of objectCOLNAME=3 ROTATE="0" MOREROWS="0"Choose this page of the object dialog; then...VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Change information about the object's description, location, department, organization, etc.COLNAME=2 ROTATE="0" MOREROWS="0"Any classCOLNAME=3 ROTATE="0" MOREROWS="0""Details"; then enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change the object's mailing addressCOLNAME=2 ROTATE="0" MOREROWS="0"Organization, Organizational UnitCOLNAME=3 ROTATE="0" MOREROWS="0""Details"; then choose "Postal Address," and enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change the object's login scriptCOLNAME=2 ROTATE="0" MOREROWS="0"Organization, Organizational Unit, IDXID="w7661"BOOK="_idx" COLLECTION="nw41" TIDREF="i3567"
ProfileCOLNAME=3 ROTATE="0" MOREROWS="0""Details"; then choose "Login Script," and enter login script commands.COLNAME=1 ROTATE="0" MOREROWS="0"View, reset, or set up intruder detection for the objectCOLNAME=2 ROTATE="0" MOREROWS="0"Organization, Organizational UnitCOLNAME=3 ROTATE="0" MOREROWS="0""Details"; then choose "Intruder Detection," and enter information in the fields to detect intruder attempts.COLNAME=1 ROTATE="0" MOREROWS="0"Change the list of operators or resources associated with this objectCOLNAME=2 ROTATE="0" MOREROWS="0"AFP Server, Computer, NetWare ServerCOLNAME=3 ROTATE="0" MOREROWS="0""Details"; then choose "Operators," "Supported Services," "Resources," or "User"; click on "Add," and then select other objects from the "Select Object" dialog.COLNAME=1 ROTATE="0" MOREROWS="0"Set the object's network address and protocolCOLNAME=2 ROTATE="0" MOREROWS="0"AFP Server, Computer, NetWare Server, VolumeCOLNAME=3 ROTATE="0" MOREROWS="0""Details"; then choose "Network Addresses"; select a network protocol, choose "Add," and then complete the fields associated with that protocol.COLNAME=1 ROTATE="0" MOREROWS="0"Change the list of other objects affiliated with this objectCOLNAME=2 ROTATE="0" MOREROWS="0"Any classCOLNAME=3 ROTATE="0" MOREROWS="0""Details"; then choose "See Also," choose "Add," and then select other objects from the "Select Object" dialog.COLNAME=1 ROTATE="0" MOREROWS="0"Change the list of objects belonging to the GroupCOLNAME=2 ROTATE="0" MOREROWS="0"GroupCOLNAME=3 ROTATE="0" MOREROWS="0""Details"; then choose "Members," choose "Add," and then select other objects from the "Select Object" dialog.COLNAME=1 ROTATE="0" MOREROWS="0"Change the object's volume time or usage informationCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7662"BOOK="_idx" COLLECTION="nw41" TIDREF="i4790"
VolumeCOLNAME=3 ROTATE="0" MOREROWS="0""Details"; then choose "IDXID="w7663"BOOK="_idx" COLLECTION="nw41" TIDREF="i4790"
Statistics," "Dates and Times," or "IDXID="w7664"BOOK="_idx" COLLECTION="nw41" TIDREF="i4719"
User Space Limits"; then enter information in the fields.PAGENUM=108 ID="BP91"PERFORMANCE="REQUIRED"To save the changes you made in all pages of the dialog, and return to th
e browser, choose "OK
."RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Object propertiesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Property" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT2"IDXID="w7665"BOOK="_idx" COLLECTION="nw41" TIDREF="i807"
Changing Object Property Values Using NETADMINRENDERAS="SECT3"IDXID="w7666"BOOK="_idx" COLLECTION="nw41" TIDREF="i3114"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterThe Create object right to the container of the object whose property value will be changedPAGENUM=109 ID="BP92"RENDERAS="SECT3"IDXID="w7667"BOOK="_idx" COLLECTION="nw41" TIDREF="i3121"
ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility.PERFORMANCE="REQUIRED"Choose "Manage Objects" from the "NETADMIN Options" menu.PERFORMANCE="REQUIRED"Browse the Directory until the object you want appears.Use the instructions at the bottom of the screen to browse the Directory. Press 
MOREINFO="NONE"<F1> if you need help.PERFORMANCE="REQUIRED"Select the object and press 
MOREINFO="NONE"<F10>.The "Actions" dialog appears.PERFORMANCE="REQUIRED"Choose "View or Edit Properties of This Object."PERFORMANCE="REQUIRED"Select an option and make any necessary changes.See IDREF="FM11593"Table 1-10 and IDREF="FM84425"Table 1-11 for details on object property values you can change.Press MOREINFO="NONE"<F1> 
for details on each field and option.IDXID="w7668"BOOK="_idx" COLLECTION="nw41" TIDREF="i2098"IDREF="FM11593"Table 1-10 describes how to modify User object property values.
IDXID="w7669"BOOK="_idx" COLLECTION="nw41" TIDREF="i4710"LABEL="1-10" PGWIDE=1 TOCENTRY="1"ID="FM11593" Changing User Object Property Values with NETADMINCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="14*"COLNAME=2 COLWIDTH="21*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Choose this option from the "View or Edit Properties of This Object" menu; then...VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Change the User's last name, other names, title, description, location, department, telephone number, fax number, or E-mail addressCOLNAME=2 ROTATE="0" MOREROWS="0""Identification"; enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Disable the User's accountCOLNAME=2 ROTATE="0" MOREROWS="0""IDXID="w7670"BOOK="_idx" COLLECTION="nw41" TIDREF="i69"
Account restrictions," and then choose "Login restrictions"; enter "Yes" in the "Account disabled" field.COLNAME=1 ROTATE="0" MOREROWS="0"Change the User's IDXID="w7671"BOOK="_idx" COLLECTION="nw41" TIDREF="i3245"
passwordCOLNAME=2 ROTATE="0" MOREROWS="0""Change password"; enter new password as prompted.COLNAME=1 ROTATE="0" MOREROWS="0"Set the User's IDXID="w7672"BOOK="_idx" COLLECTION="nw41" TIDREF="i63"
account expiration date or number of concurrent connectionsCOLNAME=2 ROTATE="0" MOREROWS="0""Account restrictions," and then choose "Login restrictions"; enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change the User's password restrictions (password length, changes, uniqueness, grace logins)COLNAME=2 ROTATE="0" MOREROWS="0""Account restrictions," and then choose "Password restrictions"; enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"View, reset, or IDXID="w7673"BOOK="_idx" COLLECTION="nw41" TIDREF="i1889"
set up intruder detection on a user's accountCOLNAME=2 ROTATE="0" MOREROWS="0""Account restrictions," and then choose "Intruder lockout status"; view or reset information in fields to detect intruder attempts.To set up intruder detection, you must go to the "View or Edit Properties of This Object" page of the container that the users reside in; then choose "Intruder Detection," enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Restrict the User's login timesCOLNAME=2 ROTATE="0" MOREROWS="0""Account restrictions," and then choose "Login time restrictions"; enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change the User'sIDXID="w7674"BOOK="_idx" COLLECTION="nw41" TIDREF="i2211"
 login scriptCOLNAME=2 ROTATE="0" MOREROWS="0""Login script"; enter login script commands.COLNAME=1 ROTATE="0" MOREROWS="0"Set the User's login address restrictionsCOLNAME=2 ROTATE="0" MOREROWS="0""Account restrictions," and then choose "Net address restrictions"; press MOREINFO="NONE"<Insert>, select the address type, and then enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Specify the User's Profile login scriptCOLNAME=2 ROTATE="0" MOREROWS="0""Groups/Security Equal To/Profile"; choose "Profile," and then enter the name and context of the Profile object (or press MOREINFO="NONE"<Insert> and select the name from the list).COLNAME=1 ROTATE="0" MOREROWS="0"Add the User to an existing Group.COLNAME=2 ROTATE="0" MOREROWS="0""Groups/Security Equal To/Profile"; select "Groups" and press MOREINFO="NONE"<Enter>, and then press MOREINFO="NONE"<Insert> and enter the Group name (or press MOREINFO="NONE"<Insert> again and select the Group name from the list).COLNAME=1 ROTATE="0" MOREROWS="0"Give the User IDXID="w7675"BOOK="_idx" COLLECTION="nw41" TIDREF="i3999"
security equivalence to another User.COLNAME=2 ROTATE="0" MOREROWS="0""Groups/Security Equal To/Profile"; select "Security Equal To" and press MOREINFO="NONE"<Enter>, and then press MOREINFO="NONE"<Insert> and enter the complete name (or press MOREINFO="NONE"<Insert> again and select the name from the list).COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7676"BOOK="_idx" COLLECTION="nw41" TIDREF="i94"
Change the User's mailing address.COLNAME=2 ROTATE="0" MOREROWS="0""IDXID="w7677"BOOK="_idx" COLLECTION="nw41" TIDREF="i3345"
Postal address"; enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change the User's account balance, credit, or allow unlimited balance.COLNAME=2 ROTATE="0" MOREROWS="0""Account restrictions," and then choose "Account balance"; enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change the list of other objects affiliated with this User object.COLNAME=2 ROTATE="0" MOREROWS="0""See also"; enter names (or press MOREINFO="NONE"<Insert> and select names from the list).PAGENUM=111 ID="BP93"IDREF="FM84425"Table 1-11 describes how to modify othe
r object property value
s.LABEL="1-11" PGWIDE=1 TOCENTRY="1"ID="FM84425" Changing Other Object Property Values With NETADMINCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Select this class of objectCOLNAME=3 ROTATE="0" MOREROWS="0"Choose this option from the "View or edit properties of this object" menu; then...VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Change the information about an object's description, location, department, organization, etc.COLNAME=2 ROTATE="0" MOREROWS="0"Any class except Print Queue, Print Server, PrinterCOLNAME=3 ROTATE="0" MOREROWS="0""Identification"; enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change information about the object's mailing addressCOLNAME=2 ROTATE="0" MOREROWS="0"Organization, Organizational Role, Organizational UnitCOLNAME=3 ROTATE="0" MOREROWS="0""Postal address"; enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change the object's login scriptCOLNAME=2 ROTATE="0" MOREROWS="0"Organization, Organizational Unit, IDXID="w7678"BOOK="_idx" COLLECTION="nw41" TIDREF="i3567"
ProfileCOLNAME=3 ROTATE="0" MOREROWS="0""Login script"; enter login script commands.COLNAME=1 ROTATE="0" MOREROWS="0"Change the object's passwordCOLNAME=2 ROTATE="0" MOREROWS="0"AFP ServerCOLNAME=3 ROTATE="0" MOREROWS="0""Change password"; enter a new password.COLNAME=1 ROTATE="0" MOREROWS="0"Set up the object's accounting informationCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare ServerCOLNAME=3 ROTATE="0" MOREROWS="0""Accounting," and then choose "Submenus"; enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Set up the object's intruder detection lockoutCOLNAME=2 ROTATE="0" MOREROWS="0"Organization, Organizational UnitCOLNAME=3 ROTATE="0" MOREROWS="0""Intruder detection"; enter information in the fields.COLNAME=1 ROTATE="0" MOREROWS="0"Set the object's network address and protocolCOLNAME=2 ROTATE="0" MOREROWS="0"ComputerCOLNAME=3 ROTATE="0" MOREROWS="0""Other properties," and then choose "Network address" and press MOREINFO="NONE"<Enter>; press MOREINFO="NONE"<Insert> and select an address type, and then enter information in other fields.COLNAME=1 ROTATE="0" MOREROWS="0"Change the list of other objects affiliated with this objectCOLNAME=2 ROTATE="0" MOREROWS="0"Any class except Print Queue, Print Server, Printer, UserCOLNAME=3 ROTATE="0" MOREROWS="0""See also"; enter names of objects (or press MOREINFO="NONE"<Insert> and select names from the list).COLNAME=1 ROTATE="0" MOREROWS="0"Change the list of objects belonging to the GroupCOLNAME=2 ROTATE="0" MOREROWS="0"GroupCOLNAME=3 ROTATE="0" MOREROWS="0""Group members"; enter names of objects (or press MOREINFO="NONE"<Insert> and select names from the list).COLNAME=1 ROTATE="0" MOREROWS="0"View the object's volume time or usage informationCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7679"BOOK="_idx" COLLECTION="nw41" TIDREF="i4790"
VolumeCOLNAME=3 ROTATE="0" MOREROWS="0""Volume statistics," "Volume restrictions," "Volume features," or "Volume dates/times"; enter information in the fields.PAGENUM=112 ID="BP94"PERFORMANCE="REQUIRED"To save your changes, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until you return to th
e "NETADMIN Options" 
menu.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Object propertiesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Property" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceLABEL="2"PAGENUM=113 ID="BP95"ID="FM37004"Managing Directories, Files, and ApplicationsThis chapter gives you step-by-step procedures for setting up your network file system and giving users access to the resources they need, while still keeping the files secure.RENDERAS="SECT1"Planning Directory StructuresIDXID="w7680"BOOK="_idx" COLLECTION="nw41" TIDREF="i1092"
How can you design your file system to make network IDXID="w7681"BOOK="_idx" COLLECTION="nw41" TIDREF="i3318"
administration easiest? This section gives you some basic information and suggestions about organizing directories and files. 
See also "BOOK="instlenu" COLLECTION="nw41"Suggestions for Creating Volumes" in Installation.RENDERAS="SECT2"System-Created DirectoriesIDXID="w7682"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"IDXID="w7683"BOOK="_idx" COLLECTION="nw41" TIDREF="i1092"
During installation, IDXID="w7684"BOOK="_idx" COLLECTION="nw41" TIDREF="i4394"
the following directories are IDXID="w7685"BOOK="_idx" COLLECTION="nw41" TIDREF="i2739"
automatically created.MARK=BULLETIDXID="w7686"BOOK="_idx" COLLECTION="nw41" TIDREF="i987"SYS:DELETED.SAV contains IDXID="w7687"BOOK="_idx" COLLECTION="nw41" TIDREF="i3939"
the files that are deleted before they IDXID="w7688"BOOK="_idx" COLLECTION="nw41" TIDREF="i4395"
are purged.IDXID="w7689"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"SYS:ETCIDXID="w7690"BOOK="_idx" COLLECTION="nw41" TIDREF="i4397"
contains IDXID="w7691"BOOK="_idx" COLLECTION="nw41" TIDREF="i1349"
sample files to help you configure the server.IDXID="w7692"BOOK="_idx" COLLECTION="nw41" TIDREF="i4399"SYS:LOGIN contains the programs necessary for users to log in to the network, such as LOGIN.EXE. It has a special subdirectory for OS/2 login programs and a subdirectory called NLS, containing subdirectories for each supported language for login message files.IDXID="w7693"BOOK="_idx" COLLECTION="nw41" TIDREF="i4401"SYS:MAILIDXID="w7694"BOOK="_idx" COLLECTION="nw41" TIDREF="i2301"
may or may not contain subdirectories or files.If you upgrade your server from a previous version of the NetWare® operating system, existing users will still have directories here for their login scripts, but their login scripts will become properties of the new User objects.If you create new users after upgrading, the new users won't have directories in SYS:MAIL.PAGENUM=114 ID="BP96"IDXID="w7695"BOOK="_idx" COLLECTION="nw41" TIDREF="i4407"SYS:SYSTEMIDXID="w7696"BOOK="_idx" COLLECTION="nw41" TIDREF="i4377"
contains NetWare operating system files as well as NetWare utilities and programs for the supervisor. SYS:SYSTEM also has an NLS subdirectory, containing subdirectories for each supported language for message files.IDXID="w7697"BOOK="_idx" COLLECTION="nw41" TIDREF="i4403"SYS:PUBLICIDXID="w7698"BOOK="_idx" COLLECTION="nw41" TIDREF="i3633"
allows general access to the network and contains NetWare utilities and programs for network users. Like SYS:LOGIN, SYS:PUBLIC has a special subdirectory for OS/2 utilities and a subdirectory called NLS, containing the message files for utilities.IDXID="w7699"BOOK="_idx" COLLECTION="nw41" TIDREF="i4396"SYS:DOC contains electronic versions of the NetWare manuals. This directory is created if you install DynaText.*RENDERAS="SECT2"High Capacity Storage System (HCSS) DirectoriesIDXID="w7700"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"You can create HCSS directories specifically to contain files that migrate to optical disk. Migration begins when allocated space on the hard disk is filled to a set capacity. This feature can be used in place of or in conjunction with file compression and disk suballocation to manage volume space on a server.HCSS directories can contain DOS program files, applications, batch files, and data files. In HCSS, directories and files are moved back and forth between hard disk and optical disk to optimize the server's storage capacity.For more information about HCSS directories, see IDREF="FM16817"Chapter 6, "Migrating Data Using the High Capacity Storage System." See also "BOOK="cncptenu" COLLECTION="nw41"High Capacity Storage System" in Concepts.RENDERAS="SECT2"Workstation Operating System DirectoriesYou may want to put the workstation operating system files on the network to save workstation disk space or to make diskless workstations possible.Since the workstation operating system files don't normally change, you can keep them on one set of backup diskettes and then skip these directories when you do network backups.For information about loading operating system software on a network, see IDREF="FM80724""Loading Operating Systems and Applications onto the Network" on page 125.PAGENUM=115 ID="BP97"RENDERAS="SECT2"Application DirectoriesFor ease of management, you should keep application files in a different directory than data files.Since the application programs don't normally change, you can keep one set of application files on backup diskettes and then skip the application directories when you do network backups.For more information about loading applications on the network, see IDREF="FM80724""Loading Operating Systems and Applications onto the Network" on page 125.RENDERAS="SECT2"Data DirectoriesData directories can include work areas where groups or users keep work files. You can also create a directory to serve as a transfer point for copying files to and from other areas of the network.RENDERAS="SECT2"Sample Directory StructureA sample directory structure is shown in IDREF="FM87946"Figure 2-1.PAGENUM=116 ID="BP98"LABEL="2-1" FLOAT="0"IDXID="w7701"BOOK="_idx" COLLECTION="nw41" TIDREF="i3318"IDXID="w7702"BOOK="_idx" COLLECTION="nw41" TIDREF="i1092"IDXID="w7703"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"ID="FM87946"Sample Network Directory StructureFILEREF="n41su11a.tif"PAGENUM=117 ID="BP99"RENDERAS="SECT1"ID="FM42808"Creating Directories and Copying FilesFor each NetWare volume, you can create directories and subdirectories to organize data and applications. (If you haven't created the volume, see IDREF="FM90777""Maintaining Volumes" on page 499.)Use one of several tools to divide a NetWare volume into directories. For example, use the NetWare Administrator graphical utility, the FILER text utility, or the DOS MKDIR (MD) command.Two methods of creating directories and copying files (NetWare Administrator and FILER) are documented in this section.RENDERAS="SECT2"ID="FM58150"Creating Directories Using NetWare AdministratorIDXID="w7704"BOOK="_idx" COLLECTION="nw41" TIDREF="i1092"RENDERAS="SECT3"IDXID="w7705"BOOK="_idx" COLLECTION="nw41" TIDREF="i874"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Create right to the parent directory of the new directoryRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the Microsoft Windows (MS Windows) Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using th
e browser, select the director
y to be the parent directory of the one yo
u want to create.To create a root directory, select the Volume object. For more about moving around in th
e browser and selecting objects, choose 
"Help
" from the menu bar. For a list of directories and files on a volume, select "View/Set Context
" and specify the volume name
.PERFORMANCE="REQUIRED"Choose 
"Create
" from the 
"Object
" menu
.PERFORMANCE="REQUIRED"Enter the name for the new directory in th
e "Directory Name
" b
ox.PERFORMANCE="REQUIRED"(Optional) Choose 
"Define Additional Properties
" if you want to enter properties for the directory.
PAGENUM=118 ID="BP100"Choose this item 
if you want to assign properties to the new directory now. You can 
also add or modify properties after the directory is created. Properties include items such as trustees and access rights.PERFORMANCE="REQUIRED"(Optional) Choose "Create Another Directory" to create another directory immediately after this one.PERFORMANCE="REQUIRED"Choose 
"Create
" to create a directory with the name you entered.The new directory is created. You are returned to the browser.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating HCSS directoriesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54389""Setting Up the HCSS File System" on page 397COLNAME=1 ROTATE="0" MOREROWS="0"Directories for workstation operating systemsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"File system" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"File system rightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Attributes," "BOOK="cncptenu" COLLECTION="nw41"Effective rights," "BOOK="cncptenu" COLLECTION="nw41"Inherited Rights Filter," "BOOK="cncptenu" COLLECTION="nw41"Rights," and "BOOK="cncptenu" COLLECTION="nw41"Security" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Assigning directory and file rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM37656""Making the File System Secure and Accessible" on page 138COLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=119 ID="BP101"RENDERAS="SECT2"ID="FM64957"Creating Directories Using FILERIDXID="w7706"BOOK="_idx" COLLECTION="nw41" TIDREF="i874"RENDERAS="SECT3"IDXID="w7707"BOOK="_idx" COLLECTION="nw41" TIDREF="i1092"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Create right to the parent directory of the new directoryRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeMOREINFO="NONE"FILER 
MOREINFO="NONE"<Enter>A list of available options appears.Your current context, Volume object, and path are shown in the upper left corner of the screen. Make sure you are in the correct location in the Directory tree when you create the new directory
.PERFORMANCE="REQUIRED"Select "Manage Files and Directories.
"The "Directory Contents
" list appears.PERFORMANCE="REQUIRED"Find and select the volume, directory, or subdirectory in which you want to create a new directory or subdirectory by completing the following steps:
MARK=BULLETIf the item you want appears on the list, select it and press MOREINFO="NONE"<Insert>.If the item is not on the list, browse a directory or subdirectory by selecting it and pressing MOREINFO="NONE"<Enter> until you see the item you want. Select it and press MOREINFO="NONE"<Insert>.If you can't find what you want, check the Volume object name in the upper left corner of the screen. If you are in the wrong volume, you can change it by returning to the "Available Options" menu and choosing "Select Current Directory."PERFORMANCE="REQUIRED"When you are prompted, type the name of the new director
y and press 
MOREINFO="NONE"<Enter>.
PAGENUM=120 ID="BP102"The 
new director
y is created
. After you create it, you can change default attributes, assign rights, and make trustee assignments for the directory or subdirectory.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until the menu you want appear
s.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Assigning directory and file rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM37656""Making the File System Secure and Accessible" on page 138COLNAME=1 ROTATE="0" MOREROWS="0"File system rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99516""Understanding File and Directory Rights" on page 138"BOOK="cncptenu" COLLECTION="nw41"Attributes" "BOOK="cncptenu" COLLECTION="nw41"Effective rights" "BOOK="cncptenu" COLLECTION="nw41"Inherited Rights Filter" "BOOK="cncptenu" COLLECTION="nw41"Rights" and "BOOK="cncptenu" COLLECTION="nw41"Security" in ConceptsIDREF="FM40052""Adding a Trustee to a Directory or File" on page 141COLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferenceRENDERAS="SECT2"Copying or Moving Files Using NetWare AdministratorIDXID="w7708"BOOK="_idx" COLLECTION="nw41" TIDREF="i1487"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 MAC and DOS name spaces, and volume 2 has MAC, DOS, and OS/2, and you copy a Macintosh file from one volume to another, you lose extended attributes even though both volumes have the MAC name space.RENDERAS="SECT3"IDXID="w7709"BOOK="_idx" COLLECTION="nw41" TIDREF="i845"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare Administrator.The File Scan right to the source directory and the Create right to the destination directory. In addition, to move files (delete them from the source directory), you need the Erase right.PAGENUM=121 ID="BP103"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using th
e browser, select the directory, and then select one or more files in that directory that you want to copy or move.To select multiple files, press 
MOREINFO="NONE"<Ctrl> on the keyboard while clicking on the files.For information about moving around in th
e browser and selecting objects, choose "Help" from the menu bar.PERFORMANCE="REQUIRED"Choose "Move
" or 
"Copy
" from the "Object
" menu.A list appears of the files you selected.PERFORMANCE="REQUIRED"Select either "Move
" or "Copy
" from the "Operation
" dialog.PERFORMANCE="REQUIRED"Choose th
e browser
 button next to the "Destination
" field.PERFORMANCE="REQUIRED"Using the browser, select a director
y in a volume for the destination of the 
directories or files.PERFORMANCE="REQUIRED"Choose "OK
."The destination directory is listed in the "Destination" field.PERFORMANCE="REQUIRED"Choose "OK.
"The listed files are copied or moved to the destination director
yPAGENUM=122 ID="BP104"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"File system directories and filesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"File system" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"File system rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99516""Understanding File and Directory Rights" on page 138"BOOK="cncptenu" COLLECTION="nw41"Attributes" "BOOK="cncptenu" COLLECTION="nw41"Effective rights" "BOOK="cncptenu" COLLECTION="nw41"Inherited Rights Filter" "BOOK="cncptenu" COLLECTION="nw41"Rights" and "BOOK="cncptenu" COLLECTION="nw41"Security" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT2"Copying or Moving Files Using FILERIDXID="w7710"BOOK="_idx" COLLECTION="nw41" TIDREF="i1487"RENDERAS="SECT3"IDXID="w7711"BOOK="_idx" COLLECTION="nw41" TIDREF="i845"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later.A minimum of 512 KB of memory available on the workstation.The File Scan right to the source directory and the Create right to the destination directory. In addition, to move files (delete them from the source directory), you need the Erase right.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.Your current context, volume object, and path are shown in the upper left corner of the screen.PERFORMANCE="REQUIRED"Select "Manage Files and Directories.
"The "Directory Contents
" list appears.
PAGENUM=123 ID="BP105"PERFORMANCE="REQUIRED"Find the volume, directory, or subdirector
y that contains the source files.Browse the directory structure by selecting a directory or subdirectory and pressing 
MOREINFO="NONE"<Enter> until you see the directory or files you want to copy.If you can't find the directory or files you want, check the Volume object 
name in the upper left corner of the screen. If you are in the wrong volume, you 
can change it by returning to the "Available Options" menu and choosing "Select Current Directory."Depending on the operation you want to perform next, go to either Step 4 or Step 5.PERFORMANCE="REQUIRED"(Optional) If you want to move or copy a directory or subdirectory and all its contents, complete the following steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the directory or subdirectory and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Select the option you want from the "Subdirectory Options" menu.PERFORMANCE="REQUIRED"At the prompt, type in the complete path to the destination directory, or press 
MOREINFO="NONE"<Insert> to browse for the destination directory.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to start the copy or move process.The progress of the transaction is shown in an information box.PERFORMANCE="REQUIRED"(Optional) To copy specific files, complete the following steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the 
directory or subdirectory containing the files and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<F5> to mark files you want to copy.Browse the directory structure by selecting a directory or subdirectory and pressing 
MOREINFO="NONE"<Enter> until you see the directory or files you want to copy.If you can't find the directory or files you want, check the Volume object 
name in the upper left corner of the screen. If you are in the wrong volume, 
you can change it by returning to the "Available Options" menu and choosing 
"Select Current Directory."PERFORMANCE="REQUIRED"After all of the files are marked, press 
MOREINFO="NONE"<F10>.PAGENUM=124 ID="BP106"PERFORMANCE="REQUIRED"From the "Multiple File Operations" menu, select "Copy Marked Files."The "Copy Files to" box appears.PERFORMANCE="REQUIRED"Type in the complete path to the destination directory or press 
MOREINFO="NONE"<Insert> to browse for the destination directory.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to start copying the files.The progress of the transaction is shown.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until the menu you want appears.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating HCSS directoriesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54389""Setting Up the HCSS File System" on page 397COLNAME=1 ROTATE="0" MOREROWS="0"Directories and filesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"File system" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"File system rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99516""Understanding File and Directory Rights" on page 138"BOOK="cncptenu" COLLECTION="nw41"Attributes" "BOOK="cncptenu" COLLECTION="nw41"Effective rights" "BOOK="cncptenu" COLLECTION="nw41"Inherited Rights Filter," "BOOK="cncptenu" COLLECTION="nw41"Rights" and "BOOK="cncptenu" COLLECTION="nw41"Security" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferencePAGENUM=125 ID="BP107"RENDERAS="SECT1"ID="FM80724"ID="FM55031"Loading Operating Systems and Applications onto the IDXID="w7712"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
NetworkIDXID="w7713"BOOK="_idx" COLLECTION="nw41" TIDREF="i3093"IDXID="w7714"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
IDXID="w7715"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"IDXID="w7716"BOOK="_idx" COLLECTION="nw41" TIDREF="i259"
You may want to load workstation operating system (OS) files onto the network to save workstation disk space or to allow diskless IDXID="w7717"BOOK="_idx" COLLECTION="nw41" TIDREF="i1092"
workstations to log in to the network.RENDERAS="SECT2"ID="FM12240"Loading DOS onto the NetworkIDXID="w7718"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"IDXID="w7719"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterThe Supervisor or Create right to the directory where you want to load the applicationRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Create a directory in SYS:PUBLIC for each workstation type and version of DOS you will be using on your network.Name your directories according to the following convention:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SYS:PUBLIC/machine/os_type/os_versionFor each directory, replace 
machine with the six-letter machine name of the workstation (such as IBM_PC or COMPAQ).Replace 
os_type with the type of DOS you are using (such as MSDOS or DRDOS). Replace 
os_version with the DOS version number.For example, to install MS-DOS* 5.0 on an IBM PC, go to SYS:PUBLIC to create the DOS subdirectory. To use the DOS MD command, type the commands shown below (in order):
FORMAT="LINESPECIFIC"MOREINFO="NONE"MD IBM_PC MOREINFO="NONE"<Enter>
CD IBM_PC MOREINFO="NONE"<Enter>
MD MSDOS MOREINFO="NONE"<Enter>
CD MSDOS MOREINFO="NONE"<Enter>
MD 50 MOREINFO="NONE"<Enter>
CD 50 MOREINFO="NONE"<Enter>
PAGENUM=126 ID="BP108"PERFORMANCE="REQUIRED"Load DOS.Follow the instructions in the DOS documentation to load the DOS software into the directories you created.PERFORMANCE="REQUIRED"In the system login script, map the second search drive to the DOS directory.If all users have the same types o
f workstations and are using the same version of DOS, you will probably 
have only one DOS directory. In this case, add a line similar to the following, substituting the correct directory names:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S2:=SYS:PUBLIC\IBM_PC\MSDOS\50If your network has more than one DOS directory, use variables to indicate the directory path. These variables are replaced by the correct information from the workstation software when each user logs in. Enter the following command, exactly as shown, in the login script:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S2:=SYS:PUBLIC\%MACHINE\%OS\%OS_VERSION(The first search drive should be mapped to the PUBLIC directory so that users can access NetWare utilities.) For the %MACHINE variable to work, make sure the long machine type is set in each station's NET.CFG file. For example, a station might have the following line in its NET.CFG file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LONG MACHINE TYPE = IBM_PCPERFORMANCE="REQUIRED"Add COMSPEC to the system login script.Following is the proper syntax for the COMSPEC command:
FORMAT="LINESPECIFIC"MOREINFO="NONE"COMSPEC=Y:COMMAND.COMThis command tells the workstation where to find the command processorPAGENUM=127 ID="BP109"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Loading DOS on the networkCOLNAME=2 ROTATE="0" MOREROWS="0"The DOS manual that came with your softwareCOLNAME=1 ROTATE="0" MOREROWS="0"Login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM34948"Chapter 3, "Creating Login Scripts"COLNAME=1 ROTATE="0" MOREROWS="0"Mapping search drivesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM96559""Mapping Search Drives" on page 220COLNAME=1 ROTATE="0" MOREROWS="0"Running DOS on a workstationCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User GuideRENDERAS="SECT2"Loading MS Windows onto the NetworkIDXID="w7720"BOOK="_idx" COLLECTION="nw41" TIDREF="i4825"IDXID="w7721"BOOK="_idx" COLLECTION="nw41" TIDREF="i4825"
IDXID="w7722"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"You can load MS Windows onto a network in several ways:MARK=BULLETLoad all MS Windows files on a user's local hard drive.Load MS Windows program files on the server, and load user files on local hard drives.Load all MS Windows program and user files on the server. In most cases, this installation provides the easiest maintenance and most efficient use of resources.Instructions for the first two options are included in the documentation that came with your MS Windows software. Instructions for loading program and user files on the server are included in this section.Following are some advantages of having all MS Windows files installed on the server:MARK=BULLETProgram and configuration files are backed up and secure.No hard disk is required on the user workstation.The .INI and driver files for all users can be updated from one location.Configuration files always match hardware.PAGENUM=128 ID="BP110"The only real disadvantage of having all MS Windows files installed on the server is that it causes more network traffic.RENDERAS="SECT3"IDXID="w7723"BOOK="_idx" COLLECTION="nw41" TIDREF="i4825"
Files Needed for NetWare Functionality in MS WindowsUse the following files to run MS Windows with NetWare functionality. These files are in the Workstation for DOS/Windows kit.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"FileCOLNAME=2 ROTATE="0" MOREROWS="0"FunctionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NETWARE.DRVCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare device driver. Contains executable code for NetWare-related functions.COLNAME=1 ROTATE="0" MOREROWS="0"NETWARE.HLPCOLNAME=2 ROTATE="0" MOREROWS="0"Help file for NETWARE.DRV.COLNAME=1 ROTATE="0" MOREROWS="0"NETWARE.INICOLNAME=2 ROTATE="0" MOREROWS="0"Initialization file for NETWARE.DRV and other MS Windows utilities for NetWare. Automatically created by NETWARE.DRV.COLNAME=1 ROTATE="0" MOREROWS="0"NWPOPUP.EXECOLNAME=2 ROTATE="0" MOREROWS="0"Handler for broadcast messages.COLNAME=1 ROTATE="0" MOREROWS="0"VNETWARE.386COLNAME=2 ROTATE="0" MOREROWS="0"Virtual NetWare device driver. Performs virtualization among sessions when MS Windows is in 386 Enhanced mode.COLNAME=1 ROTATE="0" MOREROWS="0"VIPX.386COLNAME=2 ROTATE="0" MOREROWS="0"Virtual IPX device driver. Virtualizes IPX communications among sessions when MS Windows is in 386 Enhanced mode.RENDERAS="SECT3"ID="FM84576"Guidelines for Running MS Windows on the NetworkIDXID="w7724"BOOK="_idx" COLLECTION="nw41" TIDREF="i4825"MARK=BULLETUse a permanent swap file on a local hard drive if possible; do not use network directories for swap files. If a local swap file is not possible, consider increasing RAM to a minimum of 8 MB.RAM plus swap file size should be a minimum of 10 MB.Remove MS Windows search drives from the workstation AUTOEXEC.BAT file.If users are running DR DOS, make sure DR DOS files are dated 07 April 1992 or later.PAGENUM=129 ID="BP111"If users are running DR DOS, make sure their CONFIG.SYS files install EMM386.SYS and configure it for use with MS Windows. See your DR DOS manual or DR DOS online help for configuration information.RENDERAS="SECT3"Loading and Setting Up MS WindowsRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterThe Supervisor or Create right to the directory where you are loading MS WindowsA licensed network copy of MS Windows 3.1 or later16 MB of available disk spaceNetWare Client for DOS and MS WindowsRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Install MS Windows server software, using the SETUP /A option.For complete information about the MS Windows SETUP options and the 
installation procedure, see the documentation that came with your MS Windows 
software.PERFORMANCE="REQUIRED"Create a Group object for users who will be running MS Windows.For instructions for creating a Group object, see IDREF="FM53699""Managing Group Objects" on page 60.PERFORMANCE="REQUIRED"Make the MS Windows Group object a trustee of the MS Windows directory.For instructions on granting trustee assignments, see IDREF="FM40052""Adding a Trustee to a Directory or File" on page 141.PERFORMANCE="REQUIRED"Create a directory for each user to store user-specific MS Windows files.WIN.COM and files such as .GRP and .INI files are stored here.
PAGENUM=130 ID="BP112"PERFORMANCE="REQUIRED"IDXID="w7725"BOOK="_idx" COLLECTION="nw41" TIDREF="i2215"
Add the following information to the system login script.An example of the syntax for these login script entries appears at the end of this step.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Map a drive to the user-specific directories for the MS Windows group.PERFORMANCE="REQUIRED"Map a search drive to the MS Windows directory for the MS Windows Group object.PERFORMANCE="REQUIRED"Set the MS Windows TEMP directory to a subdirectory of the user directory.The following example shows the system login script entries you would add to set up MS Windows 3.1 on the network:
FORMAT="LINESPECIFIC"MOREINFO="NONE"IF MEMBER OF "WIN31" THEN
MAP INS P:=SYS:USERS\%LOGIN_NAME\WIN31
MAP INS S16:=SYS:APPS\WINAPPS\WIN31
SET TEMP = "P:\USERS\%LOGIN_NAME\WIN31\TEMP"
ENDPERFORMANCE="REQUIRED"Set up the workstations by completing the following steps.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Change to the search drive mapped to the MS Windows directory.Enter the drive letter only.PERFORMANCE="REQUIRED"Modify the user AUTOEXEC.BAT and CONFIG.SYS files by typing:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SETUP /N MOREINFO="NONE"<Enter>Select the "Custom" option to make sure environment variables are correct. When MS Windows prompts for a path during setup, enter the drive letter instead of the path.PERFORMANCE="REQUIRED"Install the NetWare Workstation for MS Windows software.Follow the instructions in BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User Guide to install the workstation software and update NetWare-specific files in the MS Windows directory.PAGENUM=131 ID="BP113"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM34948"Chapter 3, "Creating Login Scripts"COLNAME=1 ROTATE="0" MOREROWS="0"Installing MS Windows on the networkCOLNAME=2 ROTATE="0" MOREROWS="0"The MS Windows manual that came with your softwareCOLNAME=1 ROTATE="0" MOREROWS="0"Mapping search drivesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM96559""Mapping Search Drives" on page 220COLNAME=1 ROTATE="0" MOREROWS="0"Running MS Windows on a workstationCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User GuideRENDERAS="SECT2"ID="FM86694"Loading Other Applications onto the NetworkIDXID="w7726"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"IDXID="w7727"BOOK="_idx" COLLECTION="nw41" TIDREF="i259"
You can load various types of network applications, such as word processing or spreadsheet programs, to make them available to users. When loading applications, keep the following in mind:MARK=BULLETYou need the Create right in the directory where you will be loading the application.Follow the instructions in the application's documentation for loading the application onto a network.Make sure the application is designed for network (multiuser) use, and that you observe any licensing restrictions on the number of users who can access the application.To allow users to access network-based applications, map search drives to the directories that contain these applications. To make these search drives permanent, place them in login scripts, which are executed when users log in.If the application requires that it be installed at the root of a volume, but you would rather install it in a subdirectory for security reasons, you can map the directory to a fake root. To map a fake root directory, use the MAP ROOT command as explained in IDREF="FM99801""MAP" on page 218.You can create a Directory Map object that points to an application directory.PAGENUM=132 ID="BP114"Directory Map objects are useful in login scripts. Instead of mapping a drive to a specific directory path, you map a drive to a Directory Map object that points to a directory.Then, if you change the directory path, you need to change only the Directory Map object's definition.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM34948"Chapter 3, "Creating Login Scripts"COLNAME=1 ROTATE="0" MOREROWS="0"Mapping search drives and fake roots in login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99801""MAP" on page 218RENDERAS="SECT2"ID="FM27577"Assigning Trustee Rights to Operating System and Application DirectoriesIDXID="w7728"BOOK="_idx" COLLECTION="nw41" TIDREF="i3855"IDXID="w7729"BOOK="_idx" COLLECTION="nw41" TIDREF="i259"
Application programs need a set of file system rights that make them available to users, yet protect them from being corrupted. Keep the following guidelines in mind as you assign file and directory rights to executable, application, and program files.When you are ready to assign file and directory attributes and rights, see IDREF="FM37656""Making the File System Secure and Accessible" on page 138.Use the FLAG utility to assign the following rights:MARK=BULLETAssign the Shareable and Read-Only attributes to application and workstation operating system files.Assign the Execute Only attribute to executable files for which you keep permanent backups.Assign Read and File Scan rights to the User or Group objects that need to use the application.PAGENUM=133 ID="BP115"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Understanding file system rightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Effective rights" and "BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Assigning file and directory rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM30743""Changing Attributes of a Directory or File" on page 153COLNAME=1 ROTATE="0" MOREROWS="0"Using the FLAG utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities ReferenceRENDERAS="SECT1"Creating and Using Directory Map ObjectsRENDERAS="SECT2"How to Use Directory Map ObjectsIDXID="w7730"BOOK="_idx" COLLECTION="nw41" TIDREF="i1220"A IDXID="w7731"BOOK="_idx" COLLECTION="nw41" TIDREF="i1060"
Directory Map object represents a particular directory in the file system.Directory Map objects can be especially useful in login scripts by indicating directories that contain applications or other frequently used files.For example, if you have a directory that contains DOS 5.0, you will probably map a search drive to that directory in any login scripts you create.If you should later upgrade to DOS 6.0 and rename the directory, you would have to change the mapping in every login script where that search mapping appears.By using a Directory Map object, you could avoid having to make changes to the login scripts.First, you could create a Directory Map object called CURRENT_DOS that points to the DOS directory (SYS:PUBLIC\IBM_PC\MSDOS\5.0).IDXID="w7732"BOOK="_idx" COLLECTION="nw41" TIDREF="i2215"
Then, in a MAP command in your login scripts, map a search drive to the Directory Map object, rather than to the specific directory:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP INS S2:=.CURRENT_DOS.SALES.NOVELL_USWhen users log in, their search drive is mapped to the CURRENT_DOS Directory Map object, which points to the directory containing DOS 5.0.PAGENUM=134 ID="BP116"Later, if you upgrade to DOS 6.0 and change the directory's name to SYS:PUBLIC\IBM_PC\MSDOS\60, you would change only the Directory Map object to indicate the new path.You would not have to change the MAP command in the login script because the MAP command still indicates the correct Directory Map object.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="12*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM34948"Chapter 3, "Creating Login Scripts"COLNAME=1 ROTATE="0" MOREROWS="0"Mapping drives to Directory Map objects in login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99801""MAP" on page 218COLNAME=1 ROTATE="0" MOREROWS="0"Using the MAP utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"MAP" in Utilities ReferenceRENDERAS="SECT2"Creating a Directory Map ObjectYou can create a Directory Map object using either the NetWare Administrator graphical utility or the NETADMIN text utility. Both procedures are documented in this section.RENDERAS="SECT3"Using NetWare Administrator to Create a Directory Map ObjectIDXID="w7733"BOOK="_idx" COLLECTION="nw41" TIDREF="i873"RENDERAS="SECT4"IDXID="w7734"BOOK="_idx" COLLECTION="nw41" TIDREF="i1060"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Create object right to the container where the Directory Map object will be createdRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PAGENUM=135 ID="BP117"PERFORMANCE="REQUIRED"From th
e browser, select the Organization or Organizational Unit object that will contain the Directory Map object.For information about moving around i
n the browser and selecting objects, choose "Help
" from the menu bar.PERFORMANCE="REQUIRED"Choose "Create
" from the "Object
" menu.PERFORMANCE="REQUIRED"Choose "Directory Map" from the "New Object
" dialog box.PERFORMANCE="REQUIRED"Choose "OK.
"PERFORMANCE="REQUIRED"Enter the name for the Directory Map object in the space provided.PERFORMANCE="REQUIRED"In th
e "Volume
" field, enter the name of th
e volume this Directory Map object will point to.You can type in the complete name of the Volume object, or you can choose th
e browser
 butto
n to the right of the "Volume
" field t
o browse for the Volume object.PERFORMANCE="REQUIRED"In the "Path
" field, enter the path of the directory this Directory Map object will point to.You can type in the path, or you can choose the browser button to the right of the "Path" field to browse for the directory that the Directory Map object will point to.If the Directory Map object will point to the root of the specified volume, leave the "Path
" field blank.PERFORMANCE="REQUIRED"(Optional) To define additional properties immediately after creating the Directory Map object, choose "Define Additional Properties.
"PERFORMANCE="REQUIRED"(Optional) To create another Directory Map object immediately after this one, choose "Create Another Directory Map.
"PERFORMANCE="REQUIRED"Choose "Create
."The Directory Map object is createdIf you chose "Create Another Directory Map,
" the Create dialog appears.
PAGENUM=136 ID="BP118"If you chose "Define Additional Properties
," the identification screen appears.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Directory Map objectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory Map object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Using NETADMIN to Create a Directory Map ObjectIDXID="w7735"BOOK="_idx" COLLECTION="nw41" TIDREF="i1060"RENDERAS="SECT4"IDXID="w7736"BOOK="_idx" COLLECTION="nw41" TIDREF="i873"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Create object right in the container where the Directory Map object will be createdRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeMOREINFO="NONE"NETADMIN 
MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Manage Objects" from the "Netadmin Options" menu.PERFORMANCE="REQUIRED"Select the Organization or Organizational Unit object that will contain the Directory Map object.Browse the Directory tree by selecting objects and pressing 
MOREINFO="NONE"<Enter>. When you find the object that 
you want to contain the Directory Map object, select it and then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Pres
s MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"From the "Select an Object Class" menu, select "Directory Map
."PAGENUM=137 ID="BP119"PERFORMANCE="REQUIRED"Type the name for the Directory Map object and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"In the "Volume Object Name" field, press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"Enter the name of the Volume object this Directory Map object will point to.You can either type the Volume object's complete name or you can press 
MOREINFO="NONE"<Insert> to browse through the Directory tree
, select an object, and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"In the "Path on Volume
" field, press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"Enter the path of the directory this Directory Map object will point to.You can either type the 
full pat
h or you can press 
MOREINFO="NONE"<Insert> to brows
e th
e file system directory structure in the volume defined in Steps 7 and 8; then press <MOREINFO="NONE"Enter>.If the Directory Map object will point to the root of the specified volume, leave the "Path" field blank
 and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"From the "Name Spaces" box, select the type of name spac
e for the volume and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"To save the changes, press 
MOREINFO="NONE"<F10>.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Directory Map objectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory Map object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferencePAGENUM=138 ID="BP120"RENDERAS="SECT1"ID="FM37656"Making the File System Secure and AccessibleRENDERAS="SECT2"ID="FM99516"Understanding File and Directory RightsIDXID="w7737"BOOK="_idx" COLLECTION="nw41" TIDREF="i3855"File system security includes assigning trustee rights and setting file and directory attributes. These two types of security are discussed in the following sections.RENDERAS="SECT3"ID="FM54644"Trustee RightsIDXID="w7738"BOOK="_idx" COLLECTION="nw41" TIDREF="i3855"
Trustee rights determine the access users have to directories and files. These rights can be given to User objects, Group objects, or Organizational Role objects.Trustee rights are explained in IDREF="FM42496"Table 2-1.LABEL="2-1" PGWIDE=0 TOCENTRY="1"ID="FM42496" Trustee RightsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"RightCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Access ControlCOLNAME=2 ROTATE="0" MOREROWS="0"Add and remove trustees and change rights to files and directories.COLNAME=1 ROTATE="0" MOREROWS="0"CreateCOLNAME=2 ROTATE="0" MOREROWS="0"Create subdirectories and files.COLNAME=1 ROTATE="0" MOREROWS="0"EraseCOLNAME=2 ROTATE="0" MOREROWS="0"Delete directories and files.COLNAME=1 ROTATE="0" MOREROWS="0"File ScanCOLNAME=2 ROTATE="0" MOREROWS="0"View file and directory names in the file system structure.COLNAME=1 ROTATE="0" MOREROWS="0"ModifyCOLNAME=2 ROTATE="0" MOREROWS="0"Rename directories and files, and to change file attributes.COLNAME=1 ROTATE="0" MOREROWS="0"ReadCOLNAME=2 ROTATE="0" MOREROWS="0"Open and read files, and to open, read, and execute applications.COLNAME=1 ROTATE="0" MOREROWS="0"SupervisorCOLNAME=2 ROTATE="0" MOREROWS="0"Grant all rights listed in this table.COLNAME=1 ROTATE="0" MOREROWS="0"WriteCOLNAME=2 ROTATE="0" MOREROWS="0"Open, write to, and modify a file.PAGENUM=139 ID="BP121"RENDERAS="SECT3"ID="FM39493"Directory and File AttributesDirectory and file attributes assign properties to individual directories or files. Some attributes are meaningful only when applied at the file level, but some apply to both the directory and the file levels.Be careful when assigning directory and file attributes. The attribute applies to all users.For example, if you assign the Delete Inhibit attribute to a file, no one, including the owner of the file or the system supervisor, can delete the file. But any trustee with the Modify right can change the attribute to allow deletion.Directory and file attributes are explained in IDREF="FM56851"Table 2-2.LABEL="2-2" PGWIDE=1 TOCENTRY="1"ID="FM56851" Directory and File AttributesCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="4*"COLNAME=2 COLWIDTH="22*"COLNAME=3 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Attribute codeCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"Applies toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ACOLNAME=2 ROTATE="0" MOREROWS="0"Archive Needed identifies files that have been modified since the last backup. This attribute is assigned automatically.COLNAME=3 ROTATE="0" MOREROWS="0"Files onlyCOLNAME=1 ROTATE="0" MOREROWS="0"CiCOLNAME=2 ROTATE="0" MOREROWS="0"Copy Inhibit prevents Macintosh users from copying a file. This attribute overrides Read and File Scan trustee rights.COLNAME=3 ROTATE="0" MOREROWS="0"Files onlyCOLNAME=1 ROTATE="0" MOREROWS="0"DcCOLNAME=2 ROTATE="0" MOREROWS="0"Don't Compress keeps data from being compressed. This attribute overrides settings for automatic compression of files not accessed within a specified number of days.COLNAME=3 ROTATE="0" MOREROWS="0"Directories and filesCOLNAME=1 ROTATE="0" MOREROWS="0"DiCOLNAME=2 ROTATE="0" MOREROWS="0"Delete Inhibit means that the file or directory cannot be deleted. This attribute overrides the Erase trustee right.COLNAME=3 ROTATE="0" MOREROWS="0"Directories and filesCOLNAME=1 ROTATE="0" MOREROWS="0"DmCOLNAME=2 ROTATE="0" MOREROWS="0"Don't Migrate prevents files and directories from being migrated from the server's hard disk to another storage medium.COLNAME=3 ROTATE="0" MOREROWS="0"Directories and filesCOLNAME=1 ROTATE="0" MOREROWS="0"DsCOLNAME=2 ROTATE="0" MOREROWS="0"Don't Suballocate prevents data from being suballocated.COLNAME=3 ROTATE="0" MOREROWS="0"Files onlyCOLNAME=1 ROTATE="0" MOREROWS="0"HCOLNAME=2 ROTATE="0" MOREROWS="0"The Hidden attribute hides files and directories so they can't be listed using the DIR command. A user with File Scan rights can use FILER or the NDIR command to list directories and files with the Hidden attribute.COLNAME=3 ROTATE="0" MOREROWS="0"Directories and filesCOLNAME=1 ROTATE="0" MOREROWS="0"ICOLNAME=2 ROTATE="0" MOREROWS="0"Index allows large files to be accessed quickly by indexing files with more than 64 File Allocation Table (FAT) entries. This attribute is set automatically.COLNAME=3 ROTATE="0" MOREROWS="0"Files onlyCOLNAME=1 ROTATE="0" MOREROWS="0"IcCOLNAME=2 ROTATE="0" MOREROWS="0"Immediate Compress sets data to be compressed as soon as a file is closed. If applied to a directory, every file in the directory is compressed as each file is closed.COLNAME=3 ROTATE="0" MOREROWS="0"Directories and filesCOLNAME=1 ROTATE="0" MOREROWS="0"NCOLNAME=2 ROTATE="0" MOREROWS="0"Normal indicates the Read/Write attribute is assigned and the Shareable attribute is not. This is the default attribute assignment for all new files.COLNAME=3 ROTATE="0" MOREROWS="0"Directories and filesCOLNAME=1 ROTATE="0" MOREROWS="0"PCOLNAME=2 ROTATE="0" MOREROWS="0"Purge flags a file or directory to be erased from the system as soon as it is deleted. Purged files and directories cannot be recovered.COLNAME=3 ROTATE="0" MOREROWS="0"Directories and filesCOLNAME=1 ROTATE="0" MOREROWS="0"RiCOLNAME=2 ROTATE="0" MOREROWS="0"Rename Inhibit prevents the file or directory name from being modified.COLNAME=3 ROTATE="0" MOREROWS="0"Directories and filesCOLNAME=1 ROTATE="0" MOREROWS="0"RoCOLNAME=2 ROTATE="0" MOREROWS="0"Read Only prevents a file from being modified. This attribute automatically sets Delete Inhibit and Rename Inhibit.COLNAME=3 ROTATE="0" MOREROWS="0"Files onlyCOLNAME=1 ROTATE="0" MOREROWS="0"RwCOLNAME=2 ROTATE="0" MOREROWS="0"Read/Write allows you to write to a file. All files are created with this attribute.COLNAME=3 ROTATE="0" MOREROWS="0"Files onlyCOLNAME=1 ROTATE="0" MOREROWS="0"ShCOLNAME=2 ROTATE="0" MOREROWS="0"Shareable allows more than one user to access the file at the same time. This attribute is usually used with Read Only.COLNAME=3 ROTATE="0" MOREROWS="0"Files onlyCOLNAME=1 ROTATE="0" MOREROWS="0"SyCOLNAME=2 ROTATE="0" MOREROWS="0"The System attribute hides the file or directory so it can't be seen by using the DIR command. It can be seen if a user with File Scan rights uses FILER or the NDIR command. System is normally used with operating system files, such as DOS system files.COLNAME=3 ROTATE="0" MOREROWS="0"Directories and filesCOLNAME=1 ROTATE="0" MOREROWS="0"TCOLNAME=2 ROTATE="0" MOREROWS="0"Transactional allows a file to be tracked and protected by the Transaction Tracking System (TTS).COLNAME=3 ROTATE="0" MOREROWS="0"Files onlyCOLNAME=1 ROTATE="0" MOREROWS="0"XCOLNAME=2 ROTATE="0" MOREROWS="0"The Execute Only attribute prevents the file from being copied, modified, or backed up. It does allow renaming. The only way to remove this attribute is to delete the file. Use the attribute for program files such as .EXE or .COM. Make a copy of a file before you flag it as Execute Only, so you can replace the file if it becomes corrupted.COLNAME=3 ROTATE="0" MOREROWS="0"Files onlyPAGENUM=141 ID="BP122"RENDERAS="SECT2"ID="FM40052"Adding a Trustee to a Directory or FileYou can add a trustee to a directory or file using either the NetWare Administrator graphical utility or the FILER text utility. Both procedures are documented in this section.RENDERAS="SECT3"Using NetWare Administrator to Add a TrusteeRENDERAS="SECT4"IDXID="w7739"BOOK="_idx" COLLECTION="nw41" TIDREF="i1073"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Access Control right to the file or directory you want to add the trustee toRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using the browser, select the directory or file that you want to add a trustee to.For information about moving around in the browser and selecting objects, choose "Help" from the menu bar
.PERFORMANCE="REQUIRED"From the "Object" menu, choose "Details."PERFORMANCE="REQUIRED"From the "Identification" page, choose "Trustees of this Directory."PERFORMANCE="REQUIRED"From the "Trustees of this Directory" page, choose "Add Trustee."PERFORMANCE="REQUIRED"Select a trustee from the list.If the object does not appear in the list, browse the Directory tree to find the object that you want to make a trustee of the file or directory.PERFORMANCE="REQUIRED"Choose "OK."PERFORMANCE="REQUIRED"To grant rights to the trustee, mark the appropriate check boxes below the trustee.
PAGENUM=142 ID="BP123"PERFORMANCE="REQUIRED"To return to th
e browser, choose "OK."RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"TrusteesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Trustee" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"File system rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54644""Trustee Rights" on page 138COLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"ID="FM81376"
Using FILER to Add a TrusteeRENDERAS="SECT4"IDXID="w7740"BOOK="_idx" COLLECTION="nw41" TIDREF="i1073"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available in the workstationAccess Control right to the file or directory you want to add the trustee toRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears
.Your current context, Volume object, and path are shown in the uppe
r left corner of the screen
.PERFORMANCE="REQUIRED"Select "Manage Files and Directories."The "Directory Contents
" list appears.
PAGENUM=143 ID="BP124"PERFORMANCE="REQUIRED"Find and select the file, directory, or subdirectory you wan
t.MARK=BULLETIf the item you want appears on the list, select it and press MOREINFO="NONE"<F10>.MARK=BULLETIf the item is not in the list, browse a directory or subdirectory by selecting it and pressing MOREINFO="NONE"<Enter> until you see the item you want. Select it and press <MOREINFO="NONE"F10>.If you can't find the directory you want, check the Volume object name in the upper left corner of the screen. If you are in the wrong volume, you can change it by returning to the "Available Options" menu and choosing "Select Current Directory."PERFORMANCE="REQUIRED"Select "View/Set File [or Directory] Information" and press 
MOREINFO="NONE"<Enter>.Information for that file or directory appears.PERFORMANCE="REQUIRED"Use the arrow keys to move to the "Trustees" field, and the
n press 
MOREINFO="NONE"<Enter>.A list of trustees for that file or directory appears.PERFORMANCE="REQUIRED"To add a trustee, press 
MOREINFO="NONE"<Insert> and locate the trustee's name in the list. Select the name and 
then press 
MOREINFO="NONE"<Enter>.The new trustee, object type, and default rights appear in the list.PERFORMANCE="REQUIRED"(Optional
) To add another trustee to this file or director
y, press 
MOREINFO="NONE"<Esc> until you get to the "File Information" scree
n. Then repeat Steps 5 and 6.PERFORMANCE="REQUIRED"(Optional) Assign rights to the new trustee.You can assign or modify trustee rights now, or at any time after the trustee has been assigned to the directory or file.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"From the trustee list, select the user you want to assign or modify rights for, and then press 
MOREINFO="NONE"<Enter>.The "Trustee Rights" list appears, showing the rights the trustee currently has to this directory or file.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert> to see a list of rights you can assign.
PAGENUM=144 ID="BP125"PERFORMANCE="REQUIRED"Select a right you want to give the trustee and press 
MOREINFO="NONE"<Enter>. To give the trustee more than one right, press 
MOREINFO="NONE"<F5> to mar
k each righ
t, and then press 
MOREINFO="NONE"<Enter>.The "Trustee Rights" list reappears with the new rights added.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>.The new rights appear next to the trustee name.PERFORMANCE="REQUIRED"Exit FILER by pressing 
MOREINFO="NONE"<Esc> until you reach the Exit confirmation box, and then select "Yes.
"RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"TrusteesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Trustee" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"File system rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54644""Trustee Rights" on page 138COLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferenceRENDERAS="SECT2"Deleting a Trustee from a Directory or FileYou can delete a trustee from a directory or file using either the NetWare Administrator graphical utility or the FILER text utility. Both procedures are documented in this section.RENDERAS="SECT3"Using NetWare Administrator to Delete a TrusteeIDXID="w7741"BOOK="_idx" COLLECTION="nw41" TIDREF="i1073"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Access Control right to the file or directory you want to delete the trustee fromRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PAGENUM=145 ID="BP126"PERFORMANCE="REQUIRED"Using th
e browser, select a directory or file that you want t
o delete a truste
e from.For information on moving around in 
the browser and selecting objects, choose "Help
" from the menu bar.PERFORMANCE="REQUIRED"From the "Object
" menu, choose "Details
."PERFORMANCE="REQUIRED"From the "Identification
" page, choose "Trustees of This Directory."PERFORMANCE="REQUIRED"From the "Trustees
" list, select a truste
e.PERFORMANCE="REQUIRED"Choose "Delete Trustee
."PERFORMANCE="REQUIRED"To delete that object as a trustee, choose "Yes.
"PERFORMANCE="REQUIRED"To return to th
e browser, choose "OK.
"RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"TrusteesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Trustee" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Using FILER to Delete a TrusteeRENDERAS="SECT4"IDXID="w7742"BOOK="_idx" COLLECTION="nw41" TIDREF="i1073"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Access Control right to the file or directory you want to delete the trustee fromPAGENUM=146 ID="BP127"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.Your current context, Volume object, and path are shown in the upper left corner of the screen
.PERFORMANCE="REQUIRED"Select "Manage Files and Directories."The "Directory Contents
" list appears.PERFORMANCE="REQUIRED"Find and select the file, directory, or subdirectory you wan
t.MARK=BULLETIf the item you want appears on the list, select it and press MOREINFO="NONE"<F10>.If the item is not on the list, browse a directory or subdirectory by selecting it and pressing MOREINFO="NONE"<Enter> until you see the item you want. Select it and press MOREINFO="NONE"<F10>.If you can't find what you want, check the Volume object name in the upper left corner of the screen. If you are in the wrong volume, you can change it by returning to the "Available Options" menu and choosing "Select Current Directory."PERFORMANCE="REQUIRED"Select "View/Set File [or Directory] Information" and press 
MOREINFO="NONE"<Enter>.Information for that file or directory appears.PERFORMANCE="REQUIRED"Use the arrow keys to move to the "Trustees" field, and then press 
MOREINFO="NONE"<Enter>.A list of trustees for that file or directory appear.PERFORMANCE="REQUIRED"Select the trustee you want to delete, and then press 
MOREINFO="NONE"<Delete>.You are prompted to delete that trustee from the directory.PERFORMANCE="REQUIRED"Select "Yes.
"PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until the menu you want appears
.PAGENUM=147 ID="BP128"RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"TrusteesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Trustee" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferenceRENDERAS="SECT2"ID="FM68904"Modifying a Trustee's Rights to a Directory or FileYou can modify trustee rights to a directory or file through the NetWare Administrator graphical utility or the FILER text utility. Both procedures are documented in this section.RENDERAS="SECT3"Using NetWare Administrator to Modify a Trustee's RightsIDXID="w7743"BOOK="_idx" COLLECTION="nw41" TIDREF="i1073"RENDERAS="SECT4"IDXID="w7744"BOOK="_idx" COLLECTION="nw41" TIDREF="i3855"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Access Control right to the file or directory for which you want to change the trustee's rightsRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using the browser, selec
t the directory or file 
for which you want to change trustee rights.For information on moving around in the browser and selecting objects, choose "Help
" from the menu bar.PERFORMANCE="REQUIRED"From the "Object
" menu, choose "Details.
"PERFORMANCE="REQUIRED"From the "Identification
" page, choose "Trustees of this Directory."PERFORMANCE="REQUIRED"From the "Trustees
" list, select a trustee.
PAGENUM=148 ID="BP129"PERFORMANCE="REQUIRED"Grant or revoke rights by marking the check boxes below the trustee.PERFORMANCE="REQUIRED"Choose "OK
" to save the trustee rights
.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"File system rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54644""Trustee Rights" on page 138"BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"TrusteesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Trustee" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare AdministratorCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"IDXID="w7745"BOOK="_idx" COLLECTION="nw41" TIDREF="i3855"
Using FILER to Modify a Trustee's RightsRENDERAS="SECT4"IDXID="w7746"BOOK="_idx" COLLECTION="nw41" TIDREF="i1073"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available in the workstationThe Access Control right to the file or directory for which you want to change the trustee's rightsRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.Your current context, Volume object, and path are shown in the upper left corner of the screen
.PERFORMANCE="REQUIRED"Select "Manage Files and Directories."The "Directory Contents
" list appears.
PAGENUM=149 ID="BP130"PERFORMANCE="REQUIRED"Find and select the file, directory, or subdirectory you wan
t.MARK=BULLETIf the item you want appears on the list, select it and press MOREINFO="NONE"<F10>.If the item is not on the list, browse a directory or subdirectory by selecting it and pressing MOREINFO="NONE"<Enter> until you see the item you want. Select it and press MOREINFO="NONE"<F10>.If you cannot find the item you want, check the Volume object name in the upper left corner of the screen. If you are in the wrong volume, you can change it by backing out to the "Available Options" menu and choosing "Select Current Directory."PERFORMANCE="REQUIRED"Select "View/Set File [or Directory] Information" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Using the arrow keys, move to the "Trustee" field, and then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Select the name of the trustee whose rights you want to modify and press 
MOREINFO="NONE"<Enter>.A list of the trustee's current rights appears.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert> to see a list of rights you can assign.PERFORMANCE="REQUIRED"Select a right you want to give the trustee
, and then press 
MOREINFO="NONE"<Enter>. If you want to assign more than one right, press 
MOREINFO="NONE"<F5> to mar
k each righ
t, and then press 
MOREINFO="NONE"<Enter>.The "Trustee Rights" list reappears
, showing the new list of rights.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc>.The new rights appear next to the trustee name
.PAGENUM=150 ID="BP131"RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"File system rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54644""Trustee Rights" on page 138"BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"TrusteesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Trustee" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferencesRENDERAS="SECT2"Viewing/Modifying the Inherited Rights Filter for Directories and FilesYou can view and modify the Inherited Rights Filter (IRF) for a directory or file using the NetWare Administrator graphical utility or the FILER text utility. Both procedures are documented in this section.RENDERAS="SECT3"IDXID="w7747"BOOK="_idx" COLLECTION="nw41" TIDREF="i3855"
Using NetWare Administrator to View/Modify an Inherited Rights FilterIDXID="w7748"BOOK="_idx" COLLECTION="nw41" TIDREF="i1806"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Access Control right to the file or directory for which you want to view or modify the IRFRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using th
e browser, select a directory or file.For information on moving around in th
e browser and selecting objects, choose "Help
" from the menu bar.PERFORMANCE="REQUIRED"From the "Object
" menu, choose "Details
."PERFORMANCE="REQUIRED"From the "Identification
" page, choose "Trustees of This Directory
."PAGENUM=151 ID="BP132"PERFORMANCE="REQUIRED"Under "Inheritance Filter
," select the check boxes for the rights that you want to allow to be inherited for that directory or file.PERFORMANCE="REQUIRED"Choose 
"OK
."The 
"Trustees
" dialog reappears.PERFORMANCE="REQUIRED"To return to th
e browser, choose "OK.
"RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Inherited rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39493""Directory and File Attributes" on page 139"BOOK="cncptenu" COLLECTION="nw41"Attributes" "BOOK="cncptenu" COLLECTION="nw41"Inherited Rights Filter" and "BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"IDXID="w7749"BOOK="_idx" COLLECTION="nw41" TIDREF="i3855"
Using FILER to View/Modify the Inherited Rights FilterIDXID="w7750"BOOK="_idx" COLLECTION="nw41" TIDREF="i1806"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Access Control right to the file or directory for which you want to view or modify the filterRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.Your current context, Volume object, and path are shown in the uppe
r left corner of the screen
.PAGENUM=152 ID="BP133"PERFORMANCE="REQUIRED"Select "Manage Files and Directories."The "Directory Contents"
 list appears.PERFORMANCE="REQUIRED"Find and select the file, directory, or subdirectory you wan
t.MARK=BULLETIf the item you want appears on the list, select it and press MOREINFO="NONE"<F10>.If the item is not on the list, browse a directory or subdirectory by selecting it and then pressing MOREINFO="NONE"<Enter> until you see the item you want. Select it and press MOREINFO="NONE"<F10>.If you can't find the item you want, check the Volume object name in the upper left corner of the screen. If you are in the wrong volume, you can change it by returning to the "Available Options" menu and choosing "Select Current Directory."PERFORMANCE="REQUIRED"Select "View/Set File [or Directory] Information" and press 
MOREINFO="NONE"<Enter>.Information for that file or directory appears. The curren
t inherited rights are shown in th
e "Inherited Rights Filter"
 field.PERFORMANCE="REQUIRED"Use the arrow keys to move to the "Inherited Rights Filter" field and 
then press 
MOREINFO="NONE"<Enter>.A list of the rights inherited by the file or directory appears.PERFORMANCE="REQUIRED"Select a file or directory attribute you want to revoke
, and 
then press 
MOREINFO="NONE"<Delete>. To revoke more than one attribute, press 
MOREINFO="NONE"<F5> to mar
k each attribut
e, and then press 
MOREINFO="NONE"<Delete>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>.The "File [or Directory] Information" screen reappears with a listing of the rights that can be inherited.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until the menu you want appears
.PAGENUM=153 ID="BP134"RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Inherited rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39493""Directory and File Attributes" on page 139"BOOK="cncptenu" COLLECTION="nw41"Attributes" "BOOK="cncptenu" COLLECTION="nw41"Inherited Rights Filter" and "BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferenceRENDERAS="SECT2"ID="FM30743"Changing Attributes of a Directory or FileYou can change the attributes of a directory or file with the NetWare Administrator graphical utility or the FILER text utility. Both procedures are documented in this section.RENDERAS="SECT3"Using NetWare Administrator to Change AttributesRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Modify right to the file or directory whose attributes you want to changeRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using th
e browser, select a directory or file.For information on moving around in th
e browser and selecting objects, choose "Help" from the menu bar.PERFORMANCE="REQUIRED"From the "Object
" menu, choose "Details
."PERFORMANCE="REQUIRED"From the "Identification
" page, choos
e "Attributes
."PERFORMANCE="REQUIRED"Select the check boxes for the attributes that you want to set or reset for this directory or file.
PAGENUM=154 ID="BP135"PERFORMANCE="REQUIRED"To close th
e object dialog box and save the new attributes, choose "OK
."RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"File and directory attributesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39493""Directory and File Attributes" on page 139"BOOK="cncptenu" COLLECTION="nw41"Attributes" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Using FILER to Change AttributesRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Modify right to the file or directory whose attributes you want to changeRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.Your current context, Volume object, and path are shown in the upper left corner of the screen
.PERFORMANCE="REQUIRED"Select "Manage Files and Directories."The "Directory Contents
" list appears.
PAGENUM=155 ID="BP136"PERFORMANCE="REQUIRED"Find and select the file, directory, or subdirectory you wan
t.MARK=BULLETIf the item you want appears on the list, select it and then press MOREINFO="NONE"<F10>.If the item is not on the list, browse a directory or subdirectory by selecting it and then pressing MOREINFO="NONE"<Enter> until you see the item you want. Select it and press MOREINFO="NONE"<F10>.If you can't find what you want, check the volume object name in the upper left corner of the screen. If you are in the wrong volume, you can change it by returning to the "Available Options" menu and choosing "Select Current Directory."PERFORMANCE="REQUIRED"Select "View/Set File [or Directory] Information" and press 
MOREINFO="NONE"<Enter>.Information for the file or directory appears.PERFORMANCE="REQUIRED"To modify an attribute, use the arrow keys to move to th
e "Attributes
" field, and then press 
MOREINFO="NONE"<Enter>.The attributes for that file or directory appear.PERFORMANCE="REQUIRED"Modify the attribute by completing one of the following steps:
MARK=BULLETTo delete an attribute, select it and press MOREINFO="NONE"<Delete>. Select "Yes" when you are prompted to delete the attribute.To add an attribute, press MOREINFO="NONE"<Insert>. Select the attribute you want to add and press MOREINFO="NONE"<Enter>.To assign more than one right, press MOREINFO="NONE"<F5> to mark each right, and then press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until the menu you want appears
.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"File and directory attributesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39493""Directory and File Attributes" on page 139"BOOK="cncptenu" COLLECTION="nw41"Attributes" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferencePAGENUM=156 ID="BP137"RENDERAS="SECT2"Changing the Owner of a Directory or FileYou can change the owner of a directory or file using the NetWare Administrator graphical utility or the FILER text utility. Both procedures are documented in this section.RENDERAS="SECT3"IDXID="w7751"BOOK="_idx" COLLECTION="nw41" TIDREF="i1073"
Using NetWare Administrator to Change the OwnerRENDERAS="SECT4"IDXID="w7752"BOOK="_idx" COLLECTION="nw41" TIDREF="i3166"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Modify right to the file or directory for which you want to change the ownerRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using th
e browser, selec
t the directory or file 
for which you want to change the owne
r.For information on moving around in 
the browser and selecting objects, choose
 "Help
" from the menu bar.PERFORMANCE="REQUIRED"From the "Object
" menu, choose "Details
."PERFORMANCE="REQUIRED"From the "Identification
" page, choose "Facts.
"PERFORMANCE="REQUIRED"To change the owner
 of this file or directory, click on th
e browse
r button to the right of the "Owner
" field
.PERFORMANCE="REQUIRED"Choose the object that you want to make the new owner of this directory or file.PERFORMANCE="REQUIRED"When the correct user is displayed in the "Object Name
" field, choose "OK.
"The new owner appears in the 
"Owner
" field of the object dialog box.PERFORMANCE="REQUIRED"To 
save any changes, choose "OK."PAGENUM=157 ID="BP138"RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM93061"Chapter 1, "Managing NetWare Directory Services Objects""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Using FILER to Change the OwnerIDXID="w7753"BOOK="_idx" COLLECTION="nw41" TIDREF="i3166"RENDERAS="SECT4"IDXID="w7754"BOOK="_idx" COLLECTION="nw41" TIDREF="i1073"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Modify right to the file or directory for which you want to change the ownerRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.Your current context, Volume object, and path are shown in the uppe
r left corner of the screen.PERFORMANCE="REQUIRED"Select "Manage Files and Directories."The "Directory Contents" menu appears.
PAGENUM=158 ID="BP139"PERFORMANCE="REQUIRED"Find and select the file, directory, or subdirectory you wan
t.MARK=BULLETIf the item you want appears on the list, select it and then press MOREINFO="NONE"<F10>.If the item is not on the list, browse a directory or subdirectory by selecting it and then pressing MOREINFO="NONE"<Enter> until you see the item you want. Select it and press MOREINFO="NONE"<F10>.If you can't find what you want, check the Volume object name in the upper left corner of the screen. If you are in the wrong volume, you can change it by returning to the "Available Options" menu and choosing "Select Current Directory."PERFORMANCE="REQUIRED"Select "View/Set File [or Directory] Information" and press 
MOREINFO="NONE"<Enter>.Information for the file or directory appears. The current owner of the file or directory appears in the "Owner" field.PERFORMANCE="REQUIRED"Use the arrow keys to move to the "Owner" field and
 then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Select the user that you want to be the owner of the file or directory and press 
MOREINFO="NONE"<Enter>.(For directories only) You can apply the change of ownership to either the entire subdirectory structure or to a selected directory.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until the menu you want appears
.RENDERAS="SECT4"Additional InformationID="FM74142"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM93061"Chapter 1, "Managing NetWare Directory Services Objects""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferencePAGENUM=159 ID="BP140"RENDERAS="SECT1"Viewing Effective Rights and Other InformationRENDERAS="SECT2"Viewing a Trustee's Effective Rights to a Directory or FileYou can see the effective rights a trustee has to a directory or file by using either the NetWare Administrator graphical utility or the FILER text utility. Both procedures are documented in this section.RENDERAS="SECT3"Using NetWare Administrator to View a Trustee's Effective RightsIDXID="w7755"BOOK="_idx" COLLECTION="nw41" TIDREF="i1293"RENDERAS="SECT4"IDXID="w7756"BOOK="_idx" COLLECTION="nw41" TIDREF="i3855"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Access Control right to the file or directory, and the Read property right to the trustee object's ACL propertyRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using th
e browser, select a directory or file.For information on moving around in 
the browser and selecting objects, choose "Help
" from the menu bar.PERFORMANCE="REQUIRED"From the "Object
" menu, choose "Details
."PERFORMANCE="REQUIRED"From the "Identification" page
, choos
e "Trustees of this Directory
."PERFORMANCE="REQUIRED"Select the trustee whose effective rights you want to view.PERFORMANCE="REQUIRED"Choose "Effective Rights
."The selected trustee's effective rights are bolded in the "Effective Rights
" box.PERFORMANCE="REQUIRED"(Optional) To view a different object's rights to this directory or file, choose the browser button to the right of the "Trustee
" text box and select an object from the browser.
PAGENUM=160 ID="BP141"PERFORMANCE="REQUIRED"To return to th
e browser, choos
e "Cancel
."RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Effective rightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Effective rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Modifying trustee rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM68904""Modifying a Trustee's Rights to a Directory or File" on page 147COLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Using FILER to View a Trustee's Effective RightsIDXID="w7757"BOOK="_idx" COLLECTION="nw41" TIDREF="i1293"RENDERAS="SECT4"IDXID="w7758"BOOK="_idx" COLLECTION="nw41" TIDREF="i3855"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Access Control right to the file or directory, and the Read property right to the trustee object's ACL propertyRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.Your current context, Volume object, and path are shown in the upper left corner of the screen
.PERFORMANCE="REQUIRED"Select "Manage Files and Directories."The "Directory Contents" menu appears.
PAGENUM=161 ID="BP142"PERFORMANCE="REQUIRED"Find and select the file, directory, or subdirectory you wan
t.MARK=BULLETIf the item you want appears on the list, select it and then press MOREINFO="NONE"<F10>.If the item is not on the list, browse a directory or subdirectory by selecting it and then pressing MOREINFO="NONE"<Enter> until you see the item you want. Select it and press MOREINFO="NONE"<F10>.If you can't find the item on the list, check the Volume object name in the upper left corner of the screen. If you are in the wrong volume, you can change it by returning to the "Available Options" menu and choosing "Select Current Directory."PERFORMANCE="REQUIRED"Select "View/Set File [or Directory] Information" and press 
MOREINFO="NONE"<Enter>.Information for that file or directory appears.PERFORMANCE="REQUIRED"Use the arrow keys to mov
e to the "Trustees
" field, and then press 
MOREINFO="NONE"<Enter>.A list of trustees for the file or directory appears, along with the object type of the trustee and the current rights the trustee has to the file or directory.If the trustee list is empty, no effective rights exist for this file or directory. To assign trustee rights, se
e IDREF="FM81376""Using FILER to Add a Trustee" on page 142.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Effective rightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Effective rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Modifying trustee rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM68904""Modifying a Trustee's Rights to a Directory or File" on page 147COLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferencePAGENUM=162 ID="BP143"RENDERAS="SECT2"ID="FM57663"Viewing Other Information about a Directory or FileIDXID="w7759"BOOK="_idx" COLLECTION="nw41" TIDREF="i3134"IDXID="w7760"BOOK="_idx" COLLECTION="nw41" TIDREF="i1464"You can see extended information about a directory or file using either the NetWare Administrator graphical utility or the FILER or NDIR text utilities. You can see file information such asMARK=BULLETIDXID="w7761"BOOK="_idx" COLLECTION="nw41" TIDREF="i3166"
Owner and trusteesAttributes, effective rights, and the Inherited Rights Filter (IRF)IDXID="w7762"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
Name IDXID="w7763"BOOK="_idx" COLLECTION="nw41" TIDREF="i2585"
spaceIDXID="w7764"BOOK="_idx" COLLECTION="nw41" TIDREF="i1464"
File sizeCreation, access, archive, and modify datesYou can see directory information such asMARK=BULLETOwner and trusteesCreation date and timeAttributes, effective rights, and the IRFDisk space limitationsProcedures for using the NetWare Administrator, FILER, and NDIR are documented in this section.RENDERAS="SECT3"IDXID="w7765"BOOK="_idx" COLLECTION="nw41" TIDREF="i1464"
Using NetWare Administrator to View Other InformationIDXID="w7766"BOOK="_idx" COLLECTION="nw41" TIDREF="i2263"IDXID="w7767"BOOK="_idx" COLLECTION="nw41" TIDREF="i4656"RENDERAS="SECT4"IDXID="w7768"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Access Control right to the file or directory you want to see information aboutPAGENUM=163 ID="BP144"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using th
e browser, select the file or director
y you want to see information about.For help moving around in th
e browser and selecting objects, choos
e "Help
" from the menu bar.PERFORMANCE="REQUIRED"Choose "Details
" from the "Object
" menu.PERFORMANCE="REQUIRED"Select an "Information
" page to view for this file or directory.PERFORMANCE="REQUIRED"If you have made any changes on any pages, choose "OK
" to save changes and return to the browser.If you haven't made any changes, choose "Cancel" to return to the browse
r.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"IDXID="w7769"BOOK="_idx" COLLECTION="nw41" TIDREF="i1464"
Using FILER to View Other InformationIDXID="w7770"BOOK="_idx" COLLECTION="nw41" TIDREF="i2263"IDXID="w7771"BOOK="_idx" COLLECTION="nw41" TIDREF="i3134"
IDXID="w7772"BOOK="_idx" COLLECTION="nw41" TIDREF="i4656"RENDERAS="SECT4"IDXID="w7773"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Access Control right to the file or directory you want to see information aboutPAGENUM=164 ID="BP145"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.Your current context, Volume object, and path are shown in the uppe
r left corner of the screen.PERFORMANCE="REQUIRED"Select "Manage Files and Directories."The "Directory Contents"
 list appears.PERFORMANCE="REQUIRED"Find and select the file, directory, or subdirectory you wan
t.MARK=BULLETIf the item you want appears on the list, select it and then press MOREINFO="NONE"<F10>.If the item is not on the list, browse a directory or subdirectory by selecting it and then pressing MOREINFO="NONE"<Enter> until you see the item you want. Select it and press MOREINFO="NONE"<F10>.If you can't find what you want, check the Volume object name in the upper left corner of the screen. If you are in the wrong volume, you can change it by returning to the "Available Options" menu and choosing "Select Current Directory."PERFORMANCE="REQUIRED"Select "View/Set File [or Directory] Information."Information for the file or directory appears.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until the menu you want appears
.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferencePAGENUM=165 ID="BP146"RENDERAS="SECT3"IDXID="w7774"BOOK="_idx" COLLECTION="nw41" TIDREF="i2628"
Using NDIR to View Other InformationIDXID="w7775"BOOK="_idx" COLLECTION="nw41" TIDREF="i2263"IDXID="w7776"BOOK="_idx" COLLECTION="nw41" TIDREF="i1464"
IDXID="w7777"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"IDXID="w7778"BOOK="_idx" COLLECTION="nw41" TIDREF="i3134"
For IDXID="w7779"BOOK="_idx" COLLECTION="nw41" TIDREF="i4656"
online help with the NDIR utility's features, type one of the following commands:MARK=BULLETFor information on the NDIR utility's sorting features, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NDIR /? SORT MOREINFO="NONE"<Enter>For information on search filters (restrictions), typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NDIR /? RES MOREINFO="NONE"<Enter>For information on attribute filters, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NDIR /? AT MOREINFO="NONE"<Enter>For information on other options, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NDIR /? OPT MOREINFO="NONE"<Enter>For NDIR syntax information, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NDIR /? SYN MOREINFO="NONE"<Enter>To view all of the NDIR utility's help screens, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NDIR /? ALL MOREINFO="NONE"<Enter>RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Access Control right to the file or directory you want to see information aboutPAGENUM=166 ID="BP147"RENDERAS="SECT4"ProcedureUse the NDIR commands in IDREF="FM59932"Table 2-3 to find information about files, directories, volumes, etc. For more information about using NDIR, see "BOOK="utlrfenu" COLLECTION="nw41"NDIR" in Utilities Reference.LABEL="2-3" PGWIDE=0 TOCENTRY="1"ID="FM59932" Using NDIR to Get File and Directory InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"To get information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Use this NDIR commandVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Files onlyCOLNAME=2 ROTATE="0" MOREROWS="0"NDIR path /FOCOLNAME=1 ROTATE="0" MOREROWS="0"Directories onlyCOLNAME=2 ROTATE="0" MOREROWS="0"NDIR path /DOCOLNAME=1 ROTATE="0" MOREROWS="0"All subdirectoriesCOLNAME=2 ROTATE="0" MOREROWS="0"NDIR path /SCOLNAME=1 ROTATE="0" MOREROWS="0"VolumesCOLNAME=2 ROTATE="0" MOREROWS="0"NDIR /VOLCOLNAME=1 ROTATE="0" MOREROWS="0"Directory spaceCOLNAME=2 ROTATE="0" MOREROWS="0"NDIR /SPACOLNAME=1 ROTATE="0" MOREROWS="0"File versionCOLNAME=2 ROTATE="0" MOREROWS="0"NDIR /VERCOLNAME=1 ROTATE="0" MOREROWS="0"File detailsCOLNAME=2 ROTATE="0" MOREROWS="0"NDIR filename /DRENDERAS="SECT1"Salvaging and Purging Deleted Files and DirectoriesFiles deleted from the NetWare server remain on the disk until the deleted files are purged. Deleted files can be salvaged any time before they are purged.Purging frees the space used to store the deleted files on the server's hard disk. If a disk runs out of free space, NetWare automatically purges first the files that were deleted first.RENDERAS="SECT2"Salvaging Deleted FilesFiles deleted from the NetWare server can be recovered unless they have been purged.You can salvage files by using either the NetWare Administrator graphical utility or the FILER text utility. Both procedures are documented in this section.PAGENUM=167 ID="BP148"RENDERAS="SECT3"IDXID="w7780"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"
Using NetWare Administrator to Salvage FilesIDXID="w7781"BOOK="_idx" COLLECTION="nw41" TIDREF="i1094"IDXID="w7782"BOOK="_idx" COLLECTION="nw41" TIDREF="i3939"RENDERAS="SECT4"IDXID="w7783"BOOK="_idx" COLLECTION="nw41" TIDREF="i986"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Create right to the file that has been deleted. If the file is in the "Deleted Directories" area, you need the Supervisor right to the fileRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select the directory containing the files or directories you want to salvage
.PERFORMANCE="REQUIRED"From the "Tools
" menu, choose "Salvage
."PERFORMANCE="REQUIRED"Select the source directory (current or deleted) from the "Source Options
" drop box.If you salvage files from deleted directories on the SYS: volume, the list of files takes a long time to appear.PERFORMANCE="REQUIRED"Specify the deleted files you want listed by enter
ing a file specification (such as wildcards) in the "Include
" fiel
d.For example, to see a list of deleted batch files in the current directory, you would typ
e *.BAT
 in the "Include" field.If you leave the field blank or typ
e *.
* you get a list of all deleted files in th
e selected directory.PERFORMANCE="REQUIRED"Choose "List
" to display the file
names you included.PERFORMANCE="REQUIRED"(Optional) Specify how you want the files to be listed by selecting a sort option from the "Sort Options
" drop box
.For example, you can sort by deletion date, deletor, etc. The default listing is by filename.PERFORMANCE="REQUIRED"Select the files you want to salvage
.PAGENUM=168 ID="BP149"PERFORMANCE="REQUIRED"Choose "Salvage.
"If you salvage files from an existing directory, the files are restored to that directory. If you salvage files from a deleted directory, the files are restored under the root directory.PERFORMANCE="REQUIRED"To return to th
e browser, choose "Close
."RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Salvaging filesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Salvageable files" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"IDXID="w7784"BOOK="_idx" COLLECTION="nw41" TIDREF="i986"
Using FILER to Salvage FilesIDXID="w7785"BOOK="_idx" COLLECTION="nw41" TIDREF="i3710"RENDERAS="SECT4"IDXID="w7786"BOOK="_idx" COLLECTION="nw41" TIDREF="i1094"
PrerequisitesMARK=CHECKBOXA IDXID="w7787"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"
workstation IDXID="w7788"BOOK="_idx" COLLECTION="nw41" TIDREF="i3939"
running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Create right to the file that has been deleted. If the File is in the "Deleted Directories" area, you need the Supervisor right to the fileRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.Your current context, Volume object, and path are shown in the uppe
r left corner of the screen.PERFORMANCE="REQUIRED"Select "Salvage Deleted Files."The "Salvage" menu appears.
PAGENUM=169 ID="BP150"PERFORMANCE="REQUIRED"Salvage files from an existing directory or a deleted directory by completing one of the following steps:
MARK=BULLETTo salvage files from an existing directory, select "View/Recover Deleted Files" from the "Salvage" menu.To salvage files from a deleted directory, select "Salvage Deleted Directories" from the "Salvage" menu; then select the volume that contained the deleted directory and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"When prompted
, type a filename or wildcard t
o indicate the files you want to salvage, and then press 
MOREINFO="NONE"<Enter>.For example, if you want to recover all files wit
h the .EXE extension, typ
e *.EXE. Or, if you want to recover all files that hav
e RPT in their names, typ
e *RPT*.If you do not specify a filename or wildcard, all files 
that have been deleted from the directory will be listed.A list of deleted 
the files appears. If you salvage files from deleted directories on the SYS: volume, the list of files takes a long time to appear.PERFORMANCE="REQUIRED"(Optional) Specify how you want the fil
enames to be listed by using the sort option.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F3>.PERFORMANCE="REQUIRED"From the "Salvage Sort Options" menu, select the way you want the files to be listed.You can sort the files by deletion date, deletor, etc. The default listing is by filename.PERFORMANCE="REQUIRED"Select the files to salvage from the list
, and press 
MOREINFO="NONE"<Enter>. To salvage more than one file, press 
MOREINFO="NONE"<F5> to mar
k each fil
e, and then press 
MOREINFO="NONE"<Enter>.If you salvage files from an existing directory, the files are restored to that directory.If you salvage files from a deleted directory, the files are restored under the root directory.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until the menu you want appears
.PAGENUM=170 ID="BP151"RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Salvaging filesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Salvageable files" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferenceRENDERAS="SECT2"ID="FM26561"Purging FilesPurging files frees disk space on the NetWare server's hard disk.Purged files cannot be salvaged.You can purge files using either the NetWare Administrator graphical utility or the FILER text utility. Both procedures are documented in this section.RENDERAS="SECT3"IDXID="w7789"BOOK="_idx" COLLECTION="nw41" TIDREF="i1094"
Using NetWare Administrator to Purge FilesRENDERAS="SECT4"IDXID="w7790"BOOK="_idx" COLLECTION="nw41" TIDREF="i985"
PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare AdministratorThe Erase right to the deleted file or directory you want to purge. If the file is in the "Deleted Directories" area, you need the Supervisor right to the fileRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select the directory containing the files or directories to be purged.PERFORMANCE="REQUIRED"From the "Tools
" menu, choose "Salvage
."PERFORMANCE="REQUIRED"Select the source directory (current or deleted) from the "Source
" drop box.
PAGENUM=171 ID="BP152"PERFORMANCE="REQUIRED"Enter a file specification (such as wildcards) in the "Include" field to specify files to be listed.For example, to see a list of deleted batch files in the current directory, you would type .ba
t in the Include field.If you leave the field blank or type *.* you get a list of all deleted files in the current directory.PERFORMANCE="REQUIRED"Choose List to display the file
names yo
u specified.PERFORMANCE="REQUIRED"(Optional) Specify how you want the file
names to be listed by selecting a sort option from the 
"Sort Options" drop box.For example, you can sort by deletion date, deletor, etc. The default listing is by filename.PERFORMANCE="REQUIRED"Select the files to be purged.If no files are selected, then all deleted files are purged. PERFORMANCE="REQUIRED"Choose "Purge.
"PERFORMANCE="REQUIRED"To return to th
e browser, choose "OK.
"RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Purging filesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Purge (P) attribute" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=172 ID="BP153"RENDERAS="SECT3"Using FILER to Purge FilesIDXID="w7791"BOOK="_idx" COLLECTION="nw41" TIDREF="i1094"RENDERAS="SECT4"IDXID="w7792"BOOK="_idx" COLLECTION="nw41" TIDREF="i985"
PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Erase right to the deleted file or directory you want to purge. If the file is in the "Deleted Directories" area, you need the Supervisor right to the fileRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.Purge does
 not allow you to browse directories. Your current context, Volume object, and path are shown in the upper left corner of the screen. Make sure you are in the correct location in the Directory tree.PERFORMANCE="REQUIRED"Select "Purge Deleted Files."You are prompted for a filename pattern.PERFORMANCE="REQUIRED"Type a filename or a wildcard to specify the deleted files that you want to purge, and then press 
MOREINFO="NONE"<Enter>.If you do not specify a filename pattern, all deleted files are purged. As soon as you press <MOREINFO="NONE"Enter> for Step 4, purging starts.PERFORMANCE="REQUIRED"From the "Purge Options" menu, specify whether to purge files in the current directory only, or in the entire subdirectory structure of the current directory.A list of 
the directories being checked and the files being purge
d appea
rs.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc> until the menu you want appears
.PAGENUM=173 ID="BP154"RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Purging filesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Purge (P) attribute" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferenceLABEL="3"PAGENUM=175 ID="BP155"ID="FM34948"Creating Login ScriptsRENDERAS="SECT1"ID="FM36168"About Login ScriptsIDXID="w7793"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
You can use login scripts to automatically set up your users' workstation environments whenever they log in to the network. Login scripts are similar to configurable 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, Microsoft* Windows (MS Windows), and OS/2* workstations.Some login script commands that apply to DOS and MS Windows workstations may not apply to OS/2 workstations. These differences are indicated in the description of each command later in this chapter.PAGENUM=176 ID="BP156"RENDERAS="SECT2"IDXID="w7794"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Four Types of Login ScriptsWhen a user logs in, the LOGIN utility executes the appropriate login scripts. Four types of login scripts are available, and they can be used separately or together to tailor a custom environment for your users. All four types of login scripts are optional.MARK=BULLETA IDXID="w7795"BOOK="_idx" COLLECTION="nw41" TIDREF="i805"
container login script sets the general environments for all users in that container. The LOGIN utility executes container login scripts first. A user can use only one container login script.A container login script replaces the system login script from NetWare 3TM. IDXID="w7796"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
A 
profile login script sets environments for several users at the same time. The LOGIN utility executes a profile login script after the container login script.A user can be assigned only one profile login script, but can specify other profile login scripts on the command line. Several users can use the same profile login script.IDXID="w7797"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
A 
user login script sets environments specific to a single user, such as printing options or a username for electronic mail. The LOGIN utility executes the user login script after any container and profile login scripts have executed.A user can have only one user login script.The 
default login script is precoded into the LOGIN.EXE command and is not editable. It executes if a user doesn't have his or her own user login script, even if a container or profile login script exists.The default login script is executed for all users (including user ADMIN) unless you create a user login script. The IDXID="w7798"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
default login script contains only essential commands such as drive mappings to the NetWare® utilities.(To see the commands in the default login script, see IDREF="FM58770""Default Login Script" on page 246.)If you don't want to create any user login scripts and you don't want the default login script to execute for any users, you can disable the default login script by including the IDXID="w7799"BOOK="_idx" COLLECTION="nw41" TIDREF="i2994"
NO_DEFAULT command in the container or profile login script.PAGENUM=177 ID="BP157"To use the login script from an Organization, Organizational Unit, or Profile object, users must have the Browse right to the object and the Read right to the object's Login Script property.For more information on Browse or Read rights for a file, object, or property, see "BOOK="cncptenu" COLLECTION="nw41"Browsing" and "BOOK="cncptenu" COLLECTION="nw41"Rights" in Concepts.PAGENUM=178 ID="BP158"RENDERAS="SECT2"Deciding Which Login Scripts to CreateIDXID="w7800"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"
Maintaining many user login scripts can be time consuming. IDXID="w7801"BOOK="_idx" COLLECTION="nw41" TIDREF="i3318"
Therefore, you should try to 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 the 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 several users with identical login script needs.Finally, in user login scripts, include only those individual items that can't be included in profile or container login scripts.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. IDREF="FM28001"Table 3-1 shows which 
objects can contain which login scripts.LABEL="3-1" PGWIDE=0 TOCENTRY="1"IDXID="w7802"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"ID="FM28001" Objects That Contain Login ScriptsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="12*"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"UserIDREF="FM43813"Figure 3-1 shows where the different types of login scripts can reside in a Directory tree.PAGENUM=179 ID="BP159"LABEL="3-1" FLOAT="0"IDXID="w7803"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"ID="FM43813"Where Login Scripts Are LocatedFILEREF="n41su01a.tif"In the previous figure, there are three users, ESAYERS, SWILLIAMS, and MRICHARD. The following table shows which login scripts execute when each of these users 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"When this user 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' user login scriptCOLNAME=1 ROTATE="0" MOREROWS="0"SWILLIAMSCOLNAME=2 ROTATE="0" MOREROWS="0"1. Sales PV's container login script2. Default 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=180 ID="BP160"Container login scripts only affect users in the Organization or Organizational Unit that contains the login script.For example, in IDREF="FM43813"Figure 3-1, although there are two levels of container objects above users ESAYERS and SWILLIAMS, only the container login script they're in (OU=SALES_PV) executes when they log in.If the SALES_PV Organizational Unit 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.Because user SWILLIAMS has no user login script defined, the default login script executes after the container login script.Since user MRICHARD belongs to the profile CLERKS, the CLERKS profile login script executes before MRICHARD's user login script. Users can be assigned to only one Profile object, but other profile login scripts can be specified at the command line. For example,FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN username /p profile_objectYou can, however, assign users to more than one Group object. Then use the MEMBER OF "group" identifier variable to specify that different parts of a login script execute, depending on the Group objects that the user belongs to.For more information about using the MEMBER OF "group" identifier variable in login scripts, see IDREF="FM87639""IF...THEN" on page 210 and IDREF="FM24405""Identifier Variables" on page 240.PAGENUM=181 ID="BP161"RENDERAS="SECT2"IDXID="w7804"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Using Login Scripts from Other NetWare VersionsIDXID="w7805"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"
When you use INSTALL.NLM to IDXID="w7806"BOOK="_idx" COLLECTION="nw41" TIDREF="i4685"
upgrade a previous version of NetWare to NetWare 4TM, the login scripts in the former login directory are automatically added to the Directory database as properties of their respective objects.216In most cases, these earlier login scripts are compatible with NetWare 4 running NetWare Directory Services`. However, we recommend you review all your login scripts to see if they should be updated to take advantage of NetWare 4 functionality.If you use a previous version of the NetWare MENU utility to execute a menu program from within a login script, see IDREF="FM81162""Converting Old Menu Files" on page 280 for instructions on updating the menu program.After you convert the menu, change the command in the login script from "#MENU menu_name" to "#NMENU menu_name."In previous versions of NetWare, login scripts for OS/2 and DOS were separate. In NetWare 4, only one login script is used for both OS/2 and DOS environments.If a NetWare 3.11 user, for example, has both an OS/2 and a DOS login script, both of those login scripts are combined into a single login script when that user is upgraded to NetWare 4.The commands from the OS/2 login script appear first in the upgraded login script, followed by the commands from the DOS script.When the user logs in, the LOGIN utility determines whether the user is using OS/2 or DOS. Because of IF statements put in the script during migration/upgrade, LOGIN executes only the section of the upgraded script that contains the corresponding commands.PAGENUM=182 ID="BP162"RENDERAS="SECT1"ID="FM36951"Creating, Modifying, Copying, and Printing Login ScriptsTo create or modify login scripts and to copy one object's login script into another's, you can use either the NetWare Administrator graphical utility or the NETADMIN text utility. Both procedures are documented in this section.If you are logged in to a server running NetWare 2 or NetWare 3 and that server is in a Directory tree, you must not create or edit a login script using the SYSCON utility. If you do, the changes to that login script will not appear in your NetWare Directory Services login script.The reason is that your NetWare Directory Services login script is a property of your User object, while your bindery-based login script is a file in your MAIL directory.The main difference in creating container, profile, and user login scripts is the object you select to contain the login scripts.MARK=BULLETContainer login scripts are assigned to container objects (Organization or Organizational Unit objects).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.User login scripts are assigned to User objects.All four types of login scripts use the same conventions, commands, and variables.PAGENUM=183 ID="BP163"RENDERAS="SECT2"IDXID="w7807"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Login Script HintsIDXID="w7808"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"
The following hints can help you plan effective login scripts. For a description of the commands you can use in a login script, see IDREF="FM27425""Login Script Commands and Variables" on page 194. For login script examples, see IDREF="FM41942""Examples of Login Scripts" on page 246.IDXID="w7809"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"  LABEL="3-2" PGWIDE=1 TOCENTRY="1"Login Script ConventionsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="25*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"SubjectCOLNAME=2 ROTATE="0" MOREROWS="0"ConventionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Minimum login scriptCOLNAME=2 ROTATE="0" MOREROWS="0"No minimum. All four types of login scripts are optional. Login scripts can have only one line or they can have many. There are no required commands for login scripts.COLNAME=1 ROTATE="0" MOREROWS="0"CaseCOLNAME=2 ROTATE="0" MOREROWS="0"Either uppercase or lowercase is accepted. Exception: identifier variables enclosed in quotation marks and preceded by a percent sign (%) must be uppercase. See IDREF="FM24405""Identifier Variables" on page 240.COLNAME=1 ROTATE="0" MOREROWS="0"Characters per lineCOLNAME=2 ROTATE="0" MOREROWS="0"150 characters per line is maximum; 78 characters per line (common screen width) is recommended for readability.COLNAME=1 ROTATE="0" MOREROWS="0"Punctuation and symbolsCOLNAME=2 ROTATE="0" MOREROWS="0"Type all symbols (#, %, ", _ ) and punctuation exactly as shown in examples and syntax.COLNAME=1 ROTATE="0" MOREROWS="0"Commands per lineCOLNAME=2 ROTATE="0" MOREROWS="0"Use only one command per line. Start each command on a new line; press MOREINFO="NONE"<Enter> to end each command and start a new command.Lines that wrap automatically are considered one command.WRITE command output displays better if WRITE is repeated at the beginning of each wrapped line.COLNAME=1 ROTATE="0" MOREROWS="0"Sequence of commandsCOLNAME=2 ROTATE="0" MOREROWS="0"Generally, enter commands in the order you want them to execute, with the following restrictions:MARK=BULLETATTACH commands must precede related MAP commands to avoid prompting the user for a username/password during login.If you use "#" to execute an external program, it must follow any necessary MAP commands.If sequence is not important, group similar commands, such as MAP and WRITE commands, together to make the login script easier to read.COLNAME=1 ROTATE="0" MOREROWS="0"Blank linesCOLNAME=2 ROTATE="0" MOREROWS="0"Blank lines don't affect login script execution. Use them to visually separate groups of commands.COLNAME=1 ROTATE="0" MOREROWS="0"Remarks (REMARK, REM, asterisks, and semicolons)COLNAME=2 ROTATE="0" MOREROWS="0"Lines beginning with REMARK, REM, an asterisk, or a semicolon are comments, which don't display when the login script executes. Use remarks to record the purpose of each command or group of commands. (For examples, see IDREF="FM63873""REMARK" on page 229.)COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w7810"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"IDXID="w7811"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Identifier variablesCOLNAME=2 ROTATE="0" MOREROWS="0"Type identifier variables exactly as shown. For the value of an identifier variable to be displayed on the workstation's screen as part of a WRITE command, you must enclose the identifier in quotation marks and precede it by a percent sign (%). See IDREF="FM24405""Identifier Variables" on page 240.PAGENUM=184 ID="BP164"RENDERAS="SECT2"ID="FM30839"Creating or Modifying a Login Script Using NetWare AdministratorIDXID="w7812"BOOK="_idx" COLLECTION="nw41" TIDREF="i880"IDXID="w7813"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"Use the following instructions to create any of the three user-created types of login scripts (container, profile, or user).RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running NetWare Administrator.The Write property right to the object that will contain the login script.The object to which you are going to assign the login script must already exist (Organization, Organizational Unit, Profile, or User object).RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using the browser, select the object whose login script you are creating or modifying.For information about moving around in the browser and selecting objects, choose Help from the menu bar.PERFORMANCE="REQUIRED"Choose 
"Details
" from the 
"Object
" menu.
PAGENUM=185 ID="BP165"PERFORMANCE="REQUIRED"Choose the 
"Login Script
" page.PERFORMANCE="REQUIRED"Enter the login script commands and information into the login script text box.For a description of all login script commands, see 
IDREF="FM27425""Login Script Commands and Variables" on page 194. For login script examples, see 
IDREF="FM41942""Examples of Login Scripts" on page 246.PERFORMANCE="REQUIRED"Choose 
"OK
" to save the login script and close the 
"Details
" dialog box.If the login script you just created was a container or user login script, you're finished.If the login script you just created was for a Profile object, continue with Step 7.PERFORMANCE="REQUIRED"IDXID="w7814"BOOK="_idx" COLLECTION="nw41" TIDREF="i3567"
(Profile login scripts only) 
IDXID="w7815"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"
Using the browser, select the User object that needs to use the profile login script.PERFORMANCE="REQUIRED"Choose 
"Details
" from the 
"Object
" menu.PERFORMANCE="REQUIRED"Choose the 
"Login Script
" page.PERFORMANCE="REQUIRED"Enter the name of the Profile object in the 
"Default Profile
" field located under the login script text box.You can type in the complete name of the Profile object, or you can choose the browser button next to the 
"Default Profile
" field to select the Profile object.PERFORMANCE="REQUIRED"To save the Profile object name and close the 
"Details
" dialog box, choose 
"OK.
"Now you must add the User object as a trustee of the Profile object.PERFORMANCE="REQUIRED"Using the browser, select the Profile object.PERFORMANCE="REQUIRED"Choose 
"Trustees o
f This Object
" from the 
"Object
" menu.PERFORMANCE="REQUIRED"Choose 
"Add Trustee.
"PAGENUM=186 ID="BP166"PERFORMANCE="REQUIRED"Enter the name of the User object who is using this Profile object.You can type in the complete name of the User object, or you can choose the browser button to select the Profile object.PERFORMANCE="REQUIRED"Make sure the Browse object right and the Read property right are checked, and then choose 
"OK
" to assign these rights to the User object.The User object is now a trustee of the Profile object and has the rights necessary to run the profile login scriptRENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="17*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toCOLNAME=1 ROTATE="0" MOREROWS="0"Creating a Profile objectCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM60968""Managing Profile Objects" on page 70COLNAME=1 ROTATE="0" MOREROWS="0"Examples of login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41942""Examples of Login Scripts" on page 246COLNAME=1 ROTATE="0" MOREROWS="0"Login script commands and variablesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM27425""Login Script Commands and Variables" on page 194COLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT2"ID="FM17542"Creating or Modifying a Login Script Using NETADMINIDXID="w7816"BOOK="_idx" COLLECTION="nw41" TIDREF="i880"IDXID="w7817"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"Use 
the 
following instructions to create any of the three user-created types of login script (container, profile, or user).RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Write property right to the object that will contain the login script.The object to which you are going to assign the login script must already exist (Organization, Organizational Unit, Profile, or User object).PAGENUM=187 ID="BP167"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS Prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose 
"Manage Objects
" from the 
"NetAdmin Options
" menu.PERFORMANCE="REQUIRED"Select the object whose login script you want to create.
MARK=BULLETIf the object you want appears in the list, select it and press MOREINFO="NONE"<F10>.If the object is not in the list, browse the directory by selecting container objects and pressing MOREINFO="NONE"<Enter> until you see the object you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Select 
"View o
r Edi
t Properties o
f Thi
s Object.
"PERFORMANCE="REQUIRED"Select 
"Login Script.
"If you are editing an existing login script that already contains some commands, continue with 
IDREF="FM87572"Step 6.IDXID="w7818"BOOK="_idx" COLLECTION="nw41" TIDREF="i847"IDXID="w7819"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"
If this login script is empty, a message appears asking if you want to copy a login script from another object.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If you do not want to copy the login script from another object, answer No and continue with 
IDREF="FM87572"Step 6.PERFORMANCE="REQUIRED"ID="FM65623"To copy a login script from another object, answer Yes and select the name of the object whose script you want to copy. Then continue with IDREF="FM87572"Step 6.The login script is copied into the login script text box.PERFORMANCE="REQUIRED"ID="FM87572"Enter the login script commands and information in the login script text box.For a description of all login script commands, see 
IDREF="FM27425""Login Script Commands and Variables" on page 194. For login script examples, see 
IDREF="FM41942""Examples of Login Scripts" on page 246.PERFORMANCE="REQUIRED"To save the login script, press 
MOREINFO="NONE"<F10>.If the login script you just created was a container or a user login script, you're finished.
PAGENUM=188 ID="BP168"If the login script you just created was for a Profile object, continue with 
IDREF="FM62083"Step 8.PERFORMANCE="REQUIRED"ID="FM62083"IDXID="w7820"BOOK="_idx" COLLECTION="nw41" TIDREF="i3567"
(Profile login scripts only) Press 
MOREINFO="NONE"<Esc> repeatedly until you return to the browser.PERFORMANCE="REQUIRED"Select the User object that needs to use the profile login script.You can either type the object's complete name and press 
MOREINFO="NONE"<F10>, or you can press 
MOREINFO="NONE"<Insert> to browse through the Directory tree and choose the name.PERFORMANCE="REQUIRED"Select 
"View o
r Edi
t Properties o
f Thi
s Object.
"PERFORMANCE="REQUIRED"Select 
"Memberships.
"PERFORMANCE="REQUIRED"Select the 
"Profile
" field and press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"Enter the name of the Profile object in the box that appears.You can either type the object's complete name and press 
MOREINFO="NONE"<F10>, or you can press 
MOREINFO="NONE"<Insert> to browse through the Directory tree and select the name.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to save the changes.Now you must add the User object as a trustee of the Profile object.PERFORMANCE="REQUIRED"Return to the 
"Manage Objects
" menu.PERFORMANCE="REQUIRED"Through the browser, select the Profile object.Press 
MOREINFO="NONE"<Insert> to browse through the Directory tree and choose the name.PERFORMANCE="REQUIRED"Select 
"View o
r Edit th
e Trustees o
f Thi
s Object.
"PERFORMANCE="REQUIRED"Select 
"Trustees.
"PERFORMANCE="REQUIRED"To add the User object as a trustee of this Profile object, press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"Enter the name of the User object who needs to be a trustee of this Profile object.
PAGENUM=189 ID="BP169"You can either type the object's complete name and press 
MOREINFO="NONE"<F10>, or you can press 
MOREINFO="NONE"<Insert> to browse through the Directory tree and choose the name.PERFORMANCE="REQUIRED"Select 
"[All Properties Rights].
"PERFORMANCE="REQUIRED"To add the user as a trustee and grant the default property right, press 
MOREINFO="NONE"<Enter>.The User object is added as a trustee of the Profile object and is given the Read right to all of the Profile's properties.Now you must assign the Browse object right to the User object.PERFORMANCE="REQUIRED"Enter the name of the User object.You can either type the object's complete name and press 
MOREINFO="NONE"<F10>, or you can press 
MOREINFO="NONE"<Insert> to browse through the Directory tree and choose the name.PERFORMANCE="REQUIRED"Choose 
"[Object Right].
"PERFORMANCE="REQUIRED"To grant the default object right, press 
MOREINFO="NONE"<Enter>.The User object is given the Browse object right. The User object now has all rights necessary to use the Profile object's login script.PERFORMANCE="REQUIRED"To exit NETADMIN, press 
MOREINFO="NONE"<Esc> until you get to the confirmation prompt, 
and then select 
"Yes.
"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating a Profile objectCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM60968""Managing Profile Objects" on page 70 COLNAME=1 ROTATE="0" MOREROWS="0"Examples of login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41942""Examples of Login Scripts" on page 246COLNAME=1 ROTATE="0" MOREROWS="0"Login script commands and variablesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM27425""Login Script Commands and Variables" on page 194COLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferencePAGENUM=190 ID="BP170"RENDERAS="SECT2"Copying a Login Script Using NetWare AdministratorIDXID="w7821"BOOK="_idx" COLLECTION="nw41" TIDREF="i847"IDXID="w7822"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"IDXID="w7823"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"
Use the 
following 
instructions to copy all or part of a login script and paste it into another object's login script.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running NetWare Administrator.The Write property right to the object that will contain the login script.The objects whose login scripts you will be working with must already exist (Organization, Organizational Unit, Profile, or User object).RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the MS Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Using the browser, select the object whose login script you want to copy.For information about moving around in the browser and selecting objects, choose Help from the menu bar.PERFORMANCE="REQUIRED"Choose 
"Details
" from the 
"Object
" menu.PERFORMANCE="REQUIRED"Choose the 
"Login Script
" page.PERFORMANCE="REQUIRED"In the login script text box, highlight the text you want to copy.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Ctrl>+<Insert> to copy the highlighted text.The highlighted text has been placed in clipboard memory and can be pasted into another login script.PERFORMANCE="REQUIRED"To save the login script and close the 
"Details
" dialog box, choose 
"OK.
"PERFORMANCE="REQUIRED"Using the browser, select the object whose login script you want to paste the copied text into.
PAGENUM=191 ID="BP171"PERFORMANCE="REQUIRED"Choose 
"Details
" from the 
"Object
" menu.PERFORMANCE="REQUIRED"Choose the 
"Login Script
" page.PERFORMANCE="REQUIRED"In the login script text box, place the cursor where you want the copied text to appear.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Shift>+<Insert> to paste the copied text into the login script.PERFORMANCE="REQUIRED"To save the login script and close the 
"Details
" dialog box, choose 
"OK.
"RENDERAS="SECT2"Copying a Login Script Using NETADMINIDXID="w7824"BOOK="_idx" COLLECTION="nw41" TIDREF="i847"IDXID="w7825"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"Use the following instructions to copy all or part of a login script and paste it into another object's login script.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later and the NETADMIN utilityThe Write property right to the object that will contain the login script.The objects whose login scripts you will be working with must already exist (Organization, Organizational Unit, Profile, or User object).RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose 
"Manage Objects
" from the 
"NetAdmin Options
" menu.
PAGENUM=192 ID="BP172"PERFORMANCE="REQUIRED"Select the object whose login script you want to copy.
MARK=BULLETIf the object you want appears in the list, select it and press MOREINFO="NONE"<F10>.If the object is not in the list, browse the Directory by selecting container objects and pressing MOREINFO="NONE"<Enter> until you see the object you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Select 
"View o
r Edi
t Properties o
f Thi
s Object.
"PERFORMANCE="REQUIRED"Select 
"Login Script.
"PERFORMANCE="REQUIRED"In the login script text box, place the cursor at the beginning of the text you want to copy and press 
MOREINFO="NONE"<F5> to mark the beginning of the text.PERFORMANCE="REQUIRED"Use the arrow keys to move to the end of the text you want to copy.As you move the cursor, text in the login script is highlighted. This highlighted text will be copied by first deleting it here, then reinserting it here, and then inserting it into the new login script.PERFORMANCE="REQUIRED"To delete the text from the login script, press 
MOREINFO="NONE"<Delete>.Although you have deleted the text, the text has been placed in a clipboard memory and can be retrieved.PERFORMANCE="REQUIRED"To insert the text from the login script, press 
MOREINFO="NONE"<Insert>.The deleted text has now been restored to your login script. A copy of the text still resides in the clipboard memory, so you can paste it into another object's memory.PERFORMANCE="REQUIRED"To exit the login script, press 
MOREINFO="NONE"<Esc>, and select 
"No
" when asked if you want to save the changes you made.PERFORMANCE="REQUIRED"Return to the browser screen.PERFORMANCE="REQUIRED"Select the object whose login script you want to paste the copied text into.You can either type the object's complete name and press 
MOREINFO="NONE"<F10>, or you can press 
MOREINFO="NONE"<Insert> to browse through the Directory tree and choose the name.
PAGENUM=193 ID="BP173"PERFORMANCE="REQUIRED"Select 
"View o
r Edi
t Properties o
f Thi
s Object.
"PERFORMANCE="REQUIRED"Select 
"Login Script.
"PERFORMANCE="REQUIRED"In the login script text box, place the cursor where you want the copied text to appear.PERFORMANCE="REQUIRED"To paste the copied text into the login script, press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"To save the changes, press 
MOREINFO="NONE"<F10>.RENDERAS="SECT2"Printing Login ScriptsUse the following instructions to print a login script.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterThe Read and File Scan property rights to the object to be printed.RENDERAS="SECT3"ProcedureTo print a login script from the command line, use the NLIST command and redirect the output to a file or a printer. You must be in an object's parent container to see and print the login script of that object.To print a user's login script, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"NLIST user <username> show "login script" >LPT1To print a container's login script, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"NLIST "organizational unit" = "ou name" show "login script" >LPT1Any parameter of the NLIST command that includes a space in its name must be enclosed in quotes.PAGENUM=194 ID="BP174"RENDERAS="SECT1"ID="FM27425"IDXID="w7826"BOOK="_idx" COLLECTION="nw41" TIDREF="i4750"IDXID="w7827"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Login Script Commands and VariablesIDXID="w7828"BOOK="_idx" COLLECTION="nw41" TIDREF="i4737"
This section describes the commands you can use in a login script. The commands are presented in alphabetical order.IDXID="w7829"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"
Syntax conventions for login script commands, as shown in IDREF="FM47000"Table 3-3, are the same as those for workstation text utilities, with one exception: Some login script commands must be preceded by the # symbol.Following is an example of the syntax for the MAP login script command:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP [option] drive:=drive:|path MOREINFO="NONE"<Enter>The command syntax is described in the table.LABEL="3-3" PGWIDE=1 TOCENTRY="1"ID="FM47000" Command Syntax ConventionsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="25*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ConventionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"MAPCOLNAME=2 ROTATE="0" MOREROWS="0"Words in uppercase letters are keywords that must be included in the command and spelled exactly as shown. However, it doesn't matter if you type them in uppercase or lowercase letters.COLNAME=1 ROTATE="0" MOREROWS="0"[ ]COLNAME=2 ROTATE="0" MOREROWS="0"Square brackets indicate that the enclosed item is optional.COLNAME=1 ROTATE="0" MOREROWS="0"|COLNAME=2 ROTATE="0" MOREROWS="0"A vertical bar means you can use either the item to the left of the bar or the item to the right, but not both. In the previous MAP example, you can enter either the drive letter or a complete path.COLNAME=1 ROTATE="0" MOREROWS="0"driveCOLNAME=2 ROTATE="0" MOREROWS="0"Words in italics are variables. Replace variables with information specific to your task.COLNAME=1 ROTATE="0" MOREROWS="0"[option]COLNAME=2 ROTATE="0" MOREROWS="0"Options or parameters for each command are listed with the command. Options and parameters can often be abbreviated.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Enter>COLNAME=2 ROTATE="0" MOREROWS="0"Angle brackets indicate a key you should press.COLNAME=1 ROTATE="0" MOREROWS="0"[[ ]]COLNAME=2 ROTATE="0" MOREROWS="0"Nested square brackets indicate that all enclosed items are optional. However, if you use the items within the innermost brackets, you must also use the items within the outer brackets.PAGENUM=195 ID="BP175"RENDERAS="SECT2"ID="FM95209"#IDXID="w7830"BOOK="_idx" COLLECTION="nw41" TIDREF="i13"IDXID="w7831"BOOK="_idx" COLLECTION="nw41" TIDREF="i688"
 (Execute External Program)IDXID="w7832"BOOK="_idx" COLLECTION="nw41" TIDREF="i1375"
Use this IDXID="w7833"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
command (the # symbol) to execute a program that is external to the login script.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"# [path] filename [parameter]Replace path with a drive letter, or, if you have specified NOSWAP on the command line or in the login script, you may replace path with a full directory path beginning with the NetWare volume name.Replace filename with an executable file (files that end in .EXE, .COM, or .BAT, for example). Do not include the extension.Replace parameter with any parameters that must accompany the executable file.RENDERAS="SECT3"Using #IDXID="w7834"BOOK="_idx" COLLECTION="nw41" TIDREF="i2980"
If you want the LOGIN utility to execute a program that is external IDXID="w7835"BOOK="_idx" COLLECTION="nw41" TIDREF="i4351"
to the login script, enter the # command (symbol) followed by the name of the file you want to execute.This command fails whenMARK=BULLETThe given directory is invalidProper security rights are lackingThe executable file cannot be foundInsufficient workstation memory is available to load the fileLOGIN swaps to extended or expanded memory or to disk unless NOSWAP is specified on the command line or in the login script.NOSWAP prevents LOGIN from being swapped out of conventional memory. Then, if the station does not have enough memory to handle both LOGIN and the # command, the # command fails but the rest of the login script executes normally.For more information, see IDREF="FM41465""SWAP" on page 236.PAGENUM=196 ID="BP176"RENDERAS="SECT3"ExamplesWhen you want to define a default print queue and printer, you can make the login script execute the NetWare CAPTURE utility. This allows you to send print jobs to a network print queue (named QUEUE_FOR_LASERJET in this example).If you have a search drive mapped to SYS:PUBLIC where the NetWare utilities are stored, you could enter the following command in the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"#CAPTURE Q=QUEUE_FOR_LASERJET NB TI=10 NFFYou do not need to enter a path in this case because CAPTURE is located in a search drive.If you do not have a search drive mapped to a directory, include the path to that directory in the command. For example, to run a batch file named BATCH.BAT in the ACCOUNTS directory, use the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"#Z:\ACCOUNTS\BATCHRENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the NOSWAP commandCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM91860""NOSWAP" on page 226COLNAME=1 ROTATE="0" MOREROWS="0"Using the SWAP commandCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41465""SWAP" on page 236PAGENUM=197 ID="BP177"RENDERAS="SECT2"ATTACHIDXID="w7836"BOOK="_idx" COLLECTION="nw41" TIDREF="i329"IDXID="w7837"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"IDXID="w7838"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
Use IDXID="w7839"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
ATTACH to connect to a bindery-based NetWare server (NetWare 2 or NetWare 3), or to a NetWare 4 server using bindery services, while the login script is running.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"ATTACH [server[/username[;password]]]RENDERAS="SECT3"Using ATTACHReplace server with the name of the NetWare server to which you want to attach.Replace username with the login name. If you do not include the username, the user is prompted for a login name when the ATTACH command is executed from the login script.You can replace password with the correct password for that user and server. If the username and password are the same as the primary login username and password, you can omit the password and not be prompted for it.Use caution when including passwords in a login script, however. It is more secure to eliminate the password. Then, at the point in the login script where the ATTACH command is executed, the user is prompted for the password.RENDERAS="SECT3"ExampleTo attach user MRICHARD (whose password is "GOLFING") to a server named REPORTS (which is a bindery-based server running NetWare 3), add the following line to her login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"ATTACH REPORTS/MRICHARD;GOLFING
PAGENUM=198 ID="BP178"RENDERAS="SECT2"ID="FM94944"BREAKIDXID="w7840"BOOK="_idx" COLLECTION="nw41" TIDREF="i510"Use BREAK ON to allow the user to terminate execution of the login script. The default is BREAK OFF.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"BREAK ON|OFFRENDERAS="SECT3"Using BREAKIf BREAK ON is included in a login script, you can press MOREINFO="NONE"<Ctrl>+<C> or MOREINFO="NONE"<Ctrl>+<Break> to abort the normal execution of your login script.Including BREAK ON in a login script does not affect the DOS MOREINFO="NONE"<Ctrl>+<Break> check. For more details, see IDREF="FM70330""DOS BREAK" on page 202.When the BREAK option is ON, type-ahead keyboard input is not saved in the buffer.RENDERAS="SECT2"CLSIDXID="w7841"BOOK="_idx" COLLECTION="nw41" TIDREF="i661"IDXID="w7842"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
Use IDXID="w7843"BOOK="_idx" COLLECTION="nw41" TIDREF="i4846"
CLS to clear the display from the workstation's screen during the login process.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"CLSRENDERAS="SECT3"Using CLSWhen a user logs in, a login script may display messages on the user's workstation screen.If the CLS command is added to the login script, any messages generated by commands earlier in the login script are cleared from the screen.PAGENUM=199 ID="BP179"RENDERAS="SECT2"COMSPECIDXID="w7844"BOOK="_idx" COLLECTION="nw41" TIDREF="i691"IDXID="w7845"BOOK="_idx" COLLECTION="nw41" TIDREF="i733"IDXID="w7846"BOOK="_idx" COLLECTION="nw41" TIDREF="i1190"To execute DOS commands from the network, use COMSPEC in the login script. Specify the directory where DOS and the DOS command processor (COMMAND.COM) are loaded.COMSPEC is originally set when DOS is booted. It must be reset after you log in to change the location that COMMAND.COM loads from while you're in the network.Users running virtual DOS sessions under OS/2 should not use this command in the login script. For more information, see IDREF="FM31624""Using COMSPEC with OS/2" on page 200.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"COMSPEC=[path]COMMAND.COMReplace path with either a drive letter or a full directory path beginning with the NetWare volume name.RENDERAS="SECT3"Using COMSPECMARK=BULLETIf users are running DOS from a network directory, first map a search drive in the login script to that directory and then add the COMSPEC command to the login script.(You may want to map a fake root to the DOS directory. For information about mapping a fake root, see IDREF="FM99801""MAP" on page 218.)If all users use the same version of DOS from the network, you can add the COMSPEC command to the container login script.If more than one version of DOS is available on your network, a network directory should exist for each DOS version. In this case, you can put COMSPEC commands in either profile or user login scripts, to make sure each workstation accesses the version of DOS it needs.If users are running DOS from their local drives, do not add COMSPEC to login scripts.PAGENUM=200 ID="BP180"To use an environment variable as the value in a COMSPEC command," precede it with the percent sign (%), as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"COMSPEC=%environment variableRENDERAS="SECT3"ID="FM31624"Using COMSPEC with OS/2IDXID="w7847"BOOK="_idx" COLLECTION="nw41" TIDREF="i733"For information about accessing the correct version of DOS from OS/2, see BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.RENDERAS="SECT2"CONTEXTIDXID="w7848"BOOK="_idx" COLLECTION="nw41" TIDREF="i815"IDXID="w7849"BOOK="_idx" COLLECTION="nw41" TIDREF="i817"IDXID="w7850"BOOK="_idx" COLLECTION="nw41" TIDREF="i2575"IDXID="w7851"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"IDXID="w7852"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"
Use IDXID="w7853"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
CONTEXT to set a user's current context in the Directory tree.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"CONTEXT contextRENDERAS="SECT3"Using CONTEXTTo change the current Directory tree context, replace context with the context you want the user to see after login.Similarly to the workstation CX utility, you can enter a complete name to move down through the context, or you can use periods to move up toward the root of the tree.CONTEXT does not support all options that the CX workstation utility does. It only sets the context.RENDERAS="SECT3"ExampleTo change the context to the Organizational Unit SALES, under the Organization NOVELL_US, add the following line to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"CONTEXT .SALES.NOVELL_USYou can type a single period instead of a container name to indicate that you want to move up one level.PAGENUM=201 ID="BP181"For example, if you are in the context SALES.NOVELL_US and you want to move up one level to the context NOVELL_US, add the following line to the login script.FORMAT="LINESPECIFIC"MOREINFO="NONE"CONTEXT .To move up two levels, enter two periods, and so on.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ContextCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Context" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the CX utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities ReferenceRENDERAS="SECT2"ID="FM16630"DISPLAYIDXID="w7854"BOOK="_idx" COLLECTION="nw41" TIDREF="i1145"IDXID="w7855"BOOK="_idx" COLLECTION="nw41" TIDREF="i4470"Use IDXID="w7856"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
DISPLAY
 to show the contents of a text file on a workstation's screen when the user logs in.This command works best with an ASCII file. If you use DISPLAY with a word-processing file, printer and word-processing codes are displayed with the text.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"DISPLAY [path] filenameReplace path with either a drive letter or a full directory path beginning with the NetWare volume name.Replace filename with the complete name (including the extension) of the file you want to display.RENDERAS="SECT3"Using DISPLAYWhen you use DISPLAY to display the contents of a file on the screen, the exact characters in the file, including any printer and word-processing codes, appear on the workstation screen. (To display only the text and suppress codes, use FDISPLAY. See IDREF="FM74267""Using FDISPLAY" on page 207)PAGENUM=202 ID="BP182"If the given directory does not exist or if the file is not found, no error message appears on the screen when the user logs in.RENDERAS="SECT3"ExampleSuppose you put messages in a file called SYSNEWS.TXT, in the directory SYS:PUBLIC\MESSAGES, and you want your users to see this file on their screens when they log in on Mondays. Add the following lines to the container login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"IF DAY_OF_WEEK="Monday" THEN
   DISPLAY SYS:PUBLIC\MESSAGES\SYSNEWS.TXT
ENDRENDERAS="SECT2"ID="FM70330"DOS BREAKIDXID="w7857"BOOK="_idx" COLLECTION="nw41" TIDREF="i1190"IDXID="w7858"BOOK="_idx" COLLECTION="nw41" TIDREF="i1190"Use DOS BREAK to set the MOREINFO="NONE"<Ctrl>+<Break> checking level for DOS.If DOS BREAK is set to ON, you can terminate a program (other than the login script) by pressing MOREINFO="NONE"<Ctrl>+<Break>. This command does not apply to OS/2 workstations.This command is different from the BREAK command that terminates a login script. For more details, see IDREF="FM94944""BREAK" on page 198.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"DOS BREAK [ON|OFF]RENDERAS="SECT3"Using DOS BREAKEnter the following command in the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"DOS BREAK ONThe default is DOS BREAK OFF.PAGENUM=203 ID="BP183"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the DOS BREAK commandCOLNAME=2 ROTATE="0" MOREROWS="0"Your DOS manualCOLNAME=1 ROTATE="0" MOREROWS="0"Using the BREAK login script commandCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94944""BREAK" on page 198RENDERAS="SECT2"DOS SETSee IDREF="FM74868""SET" on page 231.RENDERAS="SECT2"DOS VERIFYIDXID="w7859"BOOK="_idx" COLLECTION="nw41" TIDREF="i839"IDXID="w7860"BOOK="_idx" COLLECTION="nw41" TIDREF="i1190"IDXID="w7861"BOOK="_idx" COLLECTION="nw41" TIDREF="i845"IDXID="w7862"BOOK="_idx" COLLECTION="nw41" TIDREF="i1190"Use DOS VERIFY to verify that data written to a local drive is not written to a bad sector and can be read without an error.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"DOS VERIFY [ON|OFF]RENDERAS="SECT3"Using DOS VERIFYThe DOS COPY and NCOPY commands do not automatically verify that data copied to a local drive can be read after the copy.To assure verification of each copy operation after login, add the VERIFY ON and DOS VERIFY ON commands (for network and DOS copies respectively) to the login script.Another option, since VERIFY ON can affect performance by slowing down write operations, is to use the /V option at the command line with each COPY or NCOPY operation.The default in the login script is DOS VERIFY OFF.These commands may not work with some software that is copy protected.PAGENUM=204 ID="BP184"RENDERAS="SECT2"DRIVEIDXID="w7863"BOOK="_idx" COLLECTION="nw41" TIDREF="i1219"IDXID="w7864"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"IDXID="w7865"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"IDXID="w7866"BOOK="_idx" COLLECTION="nw41" TIDREF="i1235"
Use IDXID="w7867"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
DRIVE to change the default drive while the login script is executing.On OS/2 workstations, DRIVE is effective only during execution of the login script. When the login script completes, you're returned to the drive in effect when the LOGIN command was issued..RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"DRIVE [drive:|*n:]Replace drive with a local or network drive letter, or replace n with a drive number. Use of either is dependant on their already being assigned within the login script.RENDERAS="SECT3"Using DRIVEUnless this command is in your login script, the default drive is set to the first network drive, which is often assigned to your home directory when you log in.If you don't want the default drive to be the first network drive, map a drive in the login script to the directory you want to be the default; then, use the DRIVE command to change the default drive.Instead of specifying a drive letter such as F: or G:, you can use an asterisk followed by a number n to represent the nth network drive (for example, *3). This allows drive letters to reorder themselves automatically if previous drive mappings are deleted or added.RENDERAS="SECT3"ExampleSuppose you expect to work on only one project for several days and the files for that project are located on drive S:. You can use the DRIVE command to set your default drive to S: so you won't have to change your default drive manually every time you log in.First, make sure you've mapped drive S: to the correct directory in your login script. Then enter the following command in the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"DRIVE S:
PAGENUM=205 ID="BP185"RENDERAS="SECT2"ID="FM89141"EXITIDXID="w7868"BOOK="_idx" COLLECTION="nw41" TIDREF="i1380"IDXID="w7869"BOOK="_idx" COLLECTION="nw41" TIDREF="i688"IDXID="w7870"BOOK="_idx" COLLECTION="nw41" TIDREF="i1375"
Use EXIT to terminate execution of the login script and execute an external program.This command does not apply to OS/2 workstations. RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"EXIT ["filename [parameters]"]RENDERAS="SECT3"Using EXITThe length of information between quotes can't exceed your keyboard buffer length minus 1 (commonly 15 - 1 = 14 characters).IDXID="w7871"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
You can use the EXIT command in a IDXID="w7872"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
login script to stop the login script and execute a program, such as a word processing or menu program.Because EXIT stops the login script, make sure you put this command at the end of the login script.You can also use EXIT in an IF...THEN statement, so that the login script stops and exits to an external program only if a certain condition exists. If the condition doesn't exist, the login script skips the EXIT command and continues executing.If the program you are executing with the EXIT command requires any DOS paths or NetWare search drives to be set, make sure they are specified in the login script ahead of the EXIT command.If you add EXIT to a container login script, it prevents other profile or user login scripts from running. If you put EXIT in a profile login script, it prevents the user login script from running.IDXID="w7873"BOOK="_idx" COLLECTION="nw41" TIDREF="i1380"
The EXIT command works only on IBM-compatible workstations IDXID="w7874"BOOK="_idx" COLLECTION="nw41" TIDREF="i4846"
running DOS. Therefore, if your DOS workstation has a machine name different from 
IBM_PC specified in its NET.CFG file, you must add the IDXID="w7875"BOOK="_idx" COLLECTION="nw41" TIDREF="i2256"
PCCOMPATIBLE IDXID="w7876"BOOK="_idx" COLLECTION="nw41" TIDREF="i3264"
login script command to the login script.For more information about the PCCOMPATIBLE command, see IDREF="FM77977""PCCOMPATIBLE" on page 227.PAGENUM=206 ID="BP186"RENDERAS="SECT3"ExamplesMARK=BULLETSuppose the workstation's long machine name is IBM_PC. To execute a menu program called TRAINING when the login script is finished, add the following line at the end of the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"EXIT "NMENU TRAINING"If you are using a Hewlett Packard computer and you have changed the long machine name to HE_PAC in the NET.CFG file, add the following lines at the end of the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"PCCOMPATIBLE
EXIT "NMENU TRAINING"Suppose you want the login script to exit to a word processing program when the user logs in on Mondays, but not on other days. You could add the following IF...THEN statement to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"IF DAY_OF_WEEK="MONDAY" THEN EXIT "WP"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Changing the machine name in NET.CFGCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User GuideCOLNAME=1 ROTATE="0" MOREROWS="0"Creating a menuCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM50463""Creating a Menu File" on page 274 in Creating MenusPAGENUM=207 ID="BP187"RENDERAS="SECT2"ID="FM96761"FDISPLAYIDXID="w7877"BOOK="_idx" COLLECTION="nw41" TIDREF="i1440"IDXID="w7878"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"Use IDXID="w7879"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
FDISPLAY to show the text of a word processing file on a workstation's screen when the user logs in.To display both the text and the printer and word processing codes of a file, or to display an ASCII file, see IDREF="FM16630""DISPLAY" on page 201.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"FDISPLAY [path] filenameReplace path with either a drive letter or a full directory path beginning with the NetWare volume name.Replace filename with the complete name (including the extension) of the file you want to display.RENDERAS="SECT3"ID="FM74267"Using FDISPLAYWhen you use FDISPLAY to display the contents of a word processing file on the screen, the text in the file is filtered and formatted so that only the text itself is displayed. FDISPLAY will not display tabs.If the given directory does not exist or if the file is not found, no error message appears on the screen when the user logs in.RENDERAS="SECT3"ExampleSuppose you put messages in a file called SYSNEWS.TXT, in the directory SYS:PUBLIC\MESSAGES, and you want your users to see this file on their screens when they log in on Mondays.Add the following lines to the container login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"IF DAY_OF_WEEK="Monday" THEN
   FDISPLAY SYS:PUBLIC\MESSAGES\SYSNEWS.TXT
END
PAGENUM=208 ID="BP188"RENDERAS="SECT2"FIRE PHASERSIDXID="w7880"BOOK="_idx" COLLECTION="nw41" TIDREF="i1513"IDXID="w7881"BOOK="_idx" COLLECTION="nw41" TIDREF="i3304"FIRE PHASERS signals the workstation to emit a phaser sound.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"FIRE nReplace n with the number of times you want this sound to occur.RENDERAS="SECT3"Using FIRE PHASERSUse this command by itself to generate the phaser sound whenever a user logs in. Use FIRE PHASERS with the IF...THEN command to make the sound execute a different number of times depending on the circumstances of the login.RENDERAS="SECT3"ExampleThe following line executes the phaser sound four times upon login:FORMAT="LINESPECIFIC"MOREINFO="NONE"FIRE 4To use an environment variable as the number of times to fire, use % before the variable, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"FIRE %environment variableEither of the following lines fires the phaser five times on Thursdays:FORMAT="LINESPECIFIC"MOREINFO="NONE"IF DAY_OF_WEEK="Thursday" THEN FIRE 5orFORMAT="LINESPECIFIC"MOREINFO="NONE"FIRE %NDAY_OF_WEEKThe identifier variable %NDAY_OF_WEEK indicates a number that corresponds to the day of the week. Since Thursday is the fifth day of the week, phasers fire five times on Thursdays.For more information about using identifier variables, see IDREF="FM24405""Identifier Variables" on page 240.PAGENUM=209 ID="BP189"RENDERAS="SECT2"GOTOIDXID="w7882"BOOK="_idx" COLLECTION="nw41" TIDREF="i1609"Use GOTO to execute a portion of the login script out of the regular sequence.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"GOTO labelUse label to indicate where the login script should continue executing.RENDERAS="SECT3"Using GOTOIDXID="w7883"BOOK="_idx" COLLECTION="nw41" TIDREF="i510"
Set BREAK ON in your login script before experimenting with GOTO loops so that you can break out of a login script if necessary.For more information about the BREAK login script command, see IDREF="FM94944""BREAK" on page 198.Do not use GOTO to enter or exit a nested IF...THEN statement. This usage confuses the program.RENDERAS="SECT3"ExampleTo execute a loop of commands, you could include the following lines in your login script. In this case, the commands to be executed are labeled AGAIN (as indicated in the second line).FORMAT="LINESPECIFIC"MOREINFO="NONE"SET X="1"
AGAIN:
SET X=<X> + "1"
;see compound strings for this
WRITE <X>
IF <X> < "9" THEN GOTO AGAINThe GOTO command looks at the value of <X> (a DOS environment variable). If the value of <X> is less than 9, then <X> increments by 1 and GOTO loops back to the AGAIN label. When <X> gains the value of 9, the IF...THEN test becomes false, the GOTO is ignored, and the script continues normally. See the IF...THEN command below.PAGENUM=210 ID="BP190"RENDERAS="SECT2"ID="FM87639"IF...THENIDXID="w7884"BOOK="_idx" COLLECTION="nw41" TIDREF="i1759"Use IDXID="w7885"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
IF...THEN when you want the login script to perform an action only under certain conditions.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"IF conditional [AND|OR [conditional]] THEN
   commands[ELS
E   command]
[END]IDXID="w7886"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"IDXID="w7887"BOOK="_idx" COLLECTION="nw41" TIDREF="i1759"
Replace conditional with identifier variables. For more information about identifier variables, see IDREF="FM24405""Identifier Variables" on page 240.Replace commands with any login script commands that you want to be executed if the specified condition is true.RENDERAS="SECT3"Using IF...THENMARK=BULLETUse IF...THEN statements to execute commands only under certain conditions.An example of a IDXID="w7888"BOOK="_idx" COLLECTION="nw41" TIDREF="i735"
conditional statement isFORMAT="LINESPECIFIC"MOREINFO="NONE"IF MEMBER OF "CLERKS"In this statement, some action is performed if the user who logged in belongs to the Group object named CLERKS.The following is a different type of conditional statement:FORMAT="LINESPECIFIC"MOREINFO="NONE"IF DAY_OF_WEEK="MONDAY"In this statement, the equal sign (=) indicates the relationship between the variable (DAY_OF_WEEK) and its value (Monday). Note that the value (Monday) is inside quotation marks.PAGENUM=211 ID="BP191"When using IF...THEN statements, be aware of the following syntax rules:MARK=BULLETUse AND or OR to include two or more conditionals in an IF...THEN statement.Values of conditional statements must be enclosed in quotation marks.The ELSE statement is optional.IF, ELSE, and END must be on separate lines. THEN does not need to be on a separate line.If you include a WRITE command as part of the IF...THEN command, the WRITE command must be on a separate line.IF...THEN statements can be nested (up to 10 levels). However, GOTO should not be used in a nested IF...THEN statement to enter or exit from the body of an IF...THEN statement.If your IF...THEN statement consists of only one line, even if that line wraps, you do not need to include END. If your IF...THEN statement must be on more than one line (for example, you used ELSE or WRITE, which must be on separate lines), you must include END.Six relationships are possible between the elements of an IF...THEN statement. Represent these relationships with the following symbols:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ID="FM24522"SymbolCOLNAME=2 ROTATE="0" MOREROWS="0"DefinitionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"=COLNAME=2 ROTATE="0" MOREROWS="0"EqualsCOLNAME=1 ROTATE="0" MOREROWS="0"<>COLNAME=2 ROTATE="0" MOREROWS="0"Does not equalCOLNAME=1 ROTATE="0" MOREROWS="0">COLNAME=2 ROTATE="0" MOREROWS="0"Is greater thanCOLNAME=1 ROTATE="0" MOREROWS="0">=COLNAME=2 ROTATE="0" MOREROWS="0"Is greater than or equal toCOLNAME=1 ROTATE="0" MOREROWS="0"<COLNAME=2 ROTATE="0" MOREROWS="0"Is less thanCOLNAME=1 ROTATE="0" MOREROWS="0"<=COLNAME=2 ROTATE="0" MOREROWS="0"Is less than or equal toPAGENUM=212 ID="BP192"RENDERAS="SECT3"ExamplesMARK=BULLETIf you place the following command in a login script, the message "Status report is due today" appears when the user logs in on Monday and "Have a nice day!" on other days.FORMAT="LINESPECIFIC"MOREINFO="NONE"IF DAY_OF_WEEK="MONDAY" THEN
   WRITE "Status report is due today"
ELSE
   WRITE "Have a nice day!"
ENDThe following line means "If the hour (on a 24-hour scale) is greater than or equal to 12, then write `afternoon'."FORMAT="LINESPECIFIC"MOREINFO="NONE"IF HOUR24>="12" THEN
   WRITE "afternoon"
ENDThe following command executes the CAPTURE utility on the fourth day of the week (Wednesday):FORMAT="LINESPECIFIC"MOREINFO="NONE"IF NDAY_OF_WEEK="4" THEN
   #CAPTURE Q=FAST_Q NB TI=10 NFF
ENDThe following example shows nested IF...THEN statements. Notice that there are two IF statements, so each one must have its own END statement.FORMAT="LINESPECIFIC"MOREINFO="NONE"IF DAY_OF_WEEK="MONDAY" THEN
   MAP *6:=VOL1:APPL\WP
   IF MEMBER OF CLERKS THEN
      WRITE "Your report is due immediately!"
   END
END
PAGENUM=213 ID="BP193"Conditionals can be joined with commas, the word AND, or the word OR to form compound conditionals.The first line of the following IF...THEN statement is a compound conditional that means "If it is the evening of the first day of the month":FORMAT="LINESPECIFIC"MOREINFO="NONE"IF GREETING_TIME="EVENING" AND DAY="01" THEN
   WRITE "The system will be backed up tonight."
ENDThe following line is a compound conditional that means "If it is 11:59:59 p.m.":FORMAT="LINESPECIFIC"MOREINFO="NONE"IF HOUR24="23" AND MINUTE="59" AND SECOND="59"An IF...THEN statement can include several commands that must be executed if the conditional is true.The following example shows two commands that are executed on Tuesdays: a WRITE command that displays a message about a staff meeting, and an INCLUDE command that tells the login script to process any commands or messages contained in the file SYS:PUBLIC\UPDATE.FORMAT="LINESPECIFIC"MOREINFO="NONE"IF DAY_OF_WEEK="TUESDAY" THEN
   WRITE "Staff meeting today at 10 a.m."   INCLUDE SYS:PUBLIC\UPDATE
ENDRENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using identifier variablesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM24405""Identifier Variables" on page 240COLNAME=1 ROTATE="0" MOREROWS="0"Using the WRITE login script command to display messagesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM10783""WRITE" on page 237PAGENUM=214 ID="BP194"RENDERAS="SECT2"ID="FM64707"INCLUDEIDXID="w7889"BOOK="_idx" COLLECTION="nw41" TIDREF="i1773"IDXID="w7890"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Use IDXID="w7891"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
INCLUDE to execute independent files or another object's login script as a part of the login script currently being processed.These sub-scripts can be text files that contain valid login script commands (any of the commands explained in this section) or login scripts that belongs to a different object you have rights to.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"INCLUDE [path]filenameorFORMAT="LINESPECIFIC"MOREINFO="NONE"INCLUDE object_nameIDXID="w7892"BOOK="_idx" COLLECTION="nw41" TIDREF="i4324"
To use a IDXID="w7893"BOOK="_idx" COLLECTION="nw41" TIDREF="i4470"
text file as a sub-script, replace path with either a drive letter or a full directory path beginning with the NetWare volume name.Replace filename with the complete name (including the extension) of the text file.To execute another object's login script as part of a login script, replace object_name with the name of the object whose login script you want to use.RENDERAS="SECT3"Using INCLUDEText files that contain login script commands and other object's login scripts can be used as sub-scripts. Use these sub-scripts to supplement the main login script.You can create and edit text file sub-scripts using any text editor. Sub-scripts do not have to have any particular filenames or extensions.The INCLUDE command executes the login script commands contained in the sub-script. It does not display the text of the sub-scripts.INCLUDE nesting is limited only by available memory. This means that one sub-script file can include another sub-script file, which can include yet another sub-script file, and so on.PAGENUM=215 ID="BP195"If the sub-script is a text file, users must have at least File Scan and Read rights to the directory containing the sub-script.If you are using another object's login script as a sub-script, users must have the Browse right to the object whose script you are including, and the Read right to the object's Login Script property.RENDERAS="SECT3"ExamplesMARK=BULLETTo execute a text file called SCRIPT.NEW (located in the VOL1: volume) as a sub-script, add the following line to your main login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"INCLUDE VOL1:ADMIN\USERS\SCRIPT.NEWSuppose you are creating a container login script for all users under the Organizational Unit object SALES_LA. You recently created a container login script for users under the Organizational Unit object SALES_PV.Now you've decided that the login scripts for the two different groups of users are very similar. In fact, you decide that the SALES_LA users could use the same login script as the SALES_PV users, but with a few more drive mappings.In the SALES_LA login script, you could add the additional drive mappings, and then use the INCLUDE command to execute the entire SALES_PV login script as a part of the SALES_LA login script, as follows:MARK=BULLETCreate an alias for the SALES_PV Organizational Unit in the SALES_LA Organizational Unit.Add this line to the SALES_LA Organizational Unit's login script.FORMAT="LINESPECIFIC"MOREINFO="NONE"INCLUDE .SALES_PV_ALIAS.SALES.NOVELL_USIDREF="FM73541"Figure 3-2 illustrates how the INCLUDE command executes the SALES_PV login script as part of the SALES_LA login script.PAGENUM=216 ID="BP196"LABEL="3-2" FLOAT="0"ID="FM73541"Using INCLUDE in a Login ScriptFILEREF="n41su04a.tif"RENDERAS="SECT2"LASTLOGINTIMEIDXID="w7894"BOOK="_idx" COLLECTION="nw41" TIDREF="i2093"IDXID="w7895"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"Use IDXID="w7896"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
LASTLOGINTIME to display the last time the user logged in.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"LASTLOGINTIMERENDERAS="SECT3"Using LASTLOGINTIMEIf you include this command in your login script, the time of the last login is displayed on the user's workstation screen.PAGENUM=217 ID="BP197"RENDERAS="SECT2"MACHINEIDXID="w7897"BOOK="_idx" COLLECTION="nw41" TIDREF="i712"
Use 
MACHINE IDXID="w7898"BOOK="_idx" COLLECTION="nw41" TIDREF="i2255"
to set the IDXID="w7899"BOOK="_idx" COLLECTION="nw41" TIDREF="i2967"
DOS IDXID="w7900"BOOK="_idx" COLLECTION="nw41" TIDREF="i2601"
machine IDXID="w7901"BOOK="_idx" COLLECTION="nw41" TIDREF="i4846"
name (such as IBM or EDIT_ROOM) of the IDXID="w7902"BOOK="_idx" COLLECTION="nw41" TIDREF="i2256"
workstation. The MACHINE command is necessary for some programs (such as NETBIOS) written to run under PC DOS.The MACHINE command does not apply to OS/2 workstations.Do not confuse the MACHINE command with the identifier of the same name. The identifier is used with a preceding percent (%) sign in MAP and WRITE statements. The identifier reads its value from the NET.CFG file.It is unlikely that you will need to use this command. However, it is provided in case you come upon a program that requires it.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"MACHINE=nameRENDERAS="SECT3"Using MACHINEThe IDXID="w7903"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
machine name can be up to 15 characters. (Longer machine names are truncated to 15 characters.)For example, to specify that the machine name is IBM_PS2, add the following line to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"MACHINE=IBM_PS2RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting machine names in the NET.CFG fileCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User GuideCOLNAME=1 ROTATE="0" MOREROWS="0"Using identifier variablesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM24405""Identifier Variables" on page 240PAGENUM=218 ID="BP198"RENDERAS="SECT2"ID="FM99801"MAPIDXID="w7904"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"IDXID="w7905"BOOK="_idx" COLLECTION="nw41" TIDREF="i2333"IDXID="w7906"BOOK="_idx" COLLECTION="nw41" TIDREF="i1220"IDXID="w7907"BOOK="_idx" COLLECTION="nw41" TIDREF="i2215"
Use IDXID="w7908"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
MAP to IDXID="w7909"BOOK="_idx" COLLECTION="nw41" TIDREF="i3974"
map drives and search drives to network directories.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP [option] [drive:=path]Replace drive with any valid network drive letter, local drive letter, or search drive number.Replace path with either a drive letter, a full directory path, or a Directory Map object.More than one command can be on the map line if the commands are separated by a semicolon (;), as shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP *1:=SYS:PUBLIC;*2:=SYS:PUBLIC\DOSWhen mapping a drive to a directory on a NetWare Directory Services (NDS) server, begin the path with either the Volume object name or server/volume.When mapping to a directory on a bindery-based server or to an NDS server that isn't your current server, begin the path with the server's name.Replace option with one of the following:MARK=BULLETDISPLAY ON/OFF: Determines whether drive mappings are displayed on the screen when the user logs in. The default setting is ON. This option is valid only in login scripts.ERRORS ON/OFF: Determines whether MAP error messages are displayed when the user logs in. MAP ERROR OFF must be placed before MAP commands in the login script. The default setting is ON. This option is valid only in login scripts.INS: Inserts a drive mapping between existing search mappings. This option is valid in login scripts and at the DOS command line.IDXID="w7910"BOOK="_idx" COLLECTION="nw41" TIDREF="i1220"DEL:IDXID="w7911"BOOK="_idx" COLLECTION="nw41" TIDREF="i3974"
Deletes a drive mapping, making that drive letter available for other mapping assignments. This option is valid in login scripts and at the command line.PAGENUM=219 ID="BP199"IDXID="w7912"BOOK="_idx" COLLECTION="nw41" TIDREF="i259"IDXID="w7913"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"IDXID="w7914"BOOK="_idx" COLLECTION="nw41" TIDREF="i1429"ROOT:IDXID="w7915"BOOK="_idx" COLLECTION="nw41" TIDREF="i1220"IDXID="w7916"BOOK="_idx" COLLECTION="nw41" TIDREF="i3879"
Maps a fake root. OS/2 is always mapped to the root. IDXID="w7917"BOOK="_idx" COLLECTION="nw41" TIDREF="i3974"
Some applications require their executable files to be located in a root directory.Since you may not want users to have rights at the root directory, you can map a fake root to a subdirectory instead. This option is valid in login scripts and at the command line.C (CHANGE): Changes a search drive mapping to a regular mapping, and a regular mapping to a search drive mapping. This option is valid in login scripts and at the command line.NP (No prompt): When a MAP command conflicts with an existing drive mapping, MAP NP eliminates the prompt that asks the user if the new drive mapping should overwrite the old mapping.This option is valid only at the command line.IDXID="w7918"BOOK="_idx" COLLECTION="nw41" TIDREF="i1220"IDXID="w7919"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"P (Physical):IDXID="w7920"BOOK="_idx" COLLECTION="nw41" TIDREF="i3974"
Maps a drive to the physical volume of a server, rather than to the Volume object's name.It is possible to have a Volume object name that conflicts with a physical volume name. (For example, object ACCT is an Accounting volume, but there is also an ACCT which is a physical volume.)Therefore, if you prefer to map a drive to the physical volume name, use MAP P. This option is valid in login scripts and at the command line.N (Next): When used without specifying a drive number or letter, maps the next available drive. This option is valid in login scripts and at the command line.RENDERAS="SECT3"ID="FM73074"Using MAPMARK=BULLETIf you use MAP to automate drive map assignments during execution of the login script, users don't have to manually map drives every time they log in.Specify drive mappings in a login script by entering the same commands that you would enter if you were using MAP at the command line.To avoid having the result of each mapping displayed as it is executed, you can put the MAP DISPLAY OFF command at the beginning of your login script. When all drive map assignments have been completed, add the line MAP DISPLAY ON and MAP to your login script. This sequence provides a cleaner display for the users as they log in.PAGENUM=220 ID="BP200"Instead of specifying drive letters such as F: or G:, you could use an asterisk followed by a number n to represent the nth network drive. For example, if your first network drive is F: then using MAP *3:= would assign H: {F G H---1 2 3}, or if your first network drive is D: then using MAP *4:= would assign G: {D E F G---1 2 3 4}.This allows drive letters to reorder themselves automatically when local drives are removed or added or when the first network drive is changed.This also allows users to log in from workstations with a different number of local drives than their regular workstation.You can map a local drive (usually A: through C:) to a network directory, but you cannot access the local drive until you remove the network drive mapping.You must not map a redirected drive, such as a CD-ROM drive, to a network drive.IDXID="w7921"BOOK="_idx" COLLECTION="nw41" TIDREF="i1220"
In many cases, you might find it useful to map network drives in the following order:MARK=BULLETMap the first network drive to the user's home directory.IDXID="w7922"BOOK="_idx" COLLECTION="nw41" TIDREF="i2785"
If your users are running OS/2, map IDXID="w7923"BOOK="_idx" COLLECTION="nw41" TIDREF="i4403"
network drive P: to the IDXID="w7924"BOOK="_idx" COLLECTION="nw41" TIDREF="i3633"
SYS:PUBLIC directory.This drive mapping is used by OS/2 workstations, as explained in BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.If users are running MS Windows from the network, map a drive to each user's directory that contains user-specific files.Map remaining drives to any directories that users work in frequently, such as project directories.RENDERAS="SECT3"ID="FM96559"Mapping Search DrivesOS/2 workstations do not use search drives. Instead, IDXID="w7925"BOOK="_idx" COLLECTION="nw41" TIDREF="i4737"
OS/2 users use the OS/2 commands PATH, DPATH, and LIBPATH in their CONFIG.SYS files.For DOS and MS Windows workstations, you can map search drives to directories that contain applications, executable files, and so forth. Then users can execute those applications regardless of the directory they are currently working in.PAGENUM=221 ID="BP201"A maximum of 16 NetWare search drives are allowed.Any object names in the login script should either be in the user's context or should have an alias point to the real object in another context. Any object referenced by a name outside the user's context will break when that object is moved or renamed, or the context is renamed. See "BOOK="cncptenu" COLLECTION="nw41"Alias object" in Concepts.When you map a search drive, use a search drive number (an S followed by a number). This search drive number assigns the next available drive letter to the mapping, starting with Z and working backwards through the English alphabet.The letter assigned to the search drive is put into the DOS path statement. If you already have search drives in the path statement, the command MAP S1: will overwrite the first one in the path. To prevent search drive assignments from overriding existing DOS PATH letters, use the INSERT option when assigning search drives. For example, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP INS S16:=pathTo ensure that users can access NetWare utilities, DOS directories, and applications, we recommend you map search drives to these directories in the following IDXID="w7926"BOOK="_idx" COLLECTION="nw41" TIDREF="i3974"
order:MARK=BULLETIDXID="w7927"BOOK="_idx" COLLECTION="nw41" TIDREF="i4737"
Map the first search drive (S1:) to the IDXID="w7928"BOOK="_idx" COLLECTION="nw41" TIDREF="i4403"IDXID="w7929"BOOK="_idx" COLLECTION="nw41" TIDREF="i3633"
SYS:PUBLIC directory, which contains the NetWare utilities for DOS and MS Windows workstations.Map the second search drive (S2:) to the DOS directory if users access DOS from the network.Map the third and subsequent search drives (S3:, S4:, etc.) to directories containing applications and the electronic NetWare documentation.IDXID="w7930"BOOK="_idx" COLLECTION="nw41" TIDREF="i4825"
If your users are running 
MS Windows from the network, map a search drive to the MS Windows directory for the MS Windows group.To avoid inadvertently changing the order of any search drives that must be mapped to a specific drive letter, you can map all remaining search drives with the number S16:, which assigns the next lowest search number each time it is used.This command assigns the next available drive letter to the search drive, without displacing the previous search drives.PAGENUM=222 ID="BP202"If you have an application that requires a particular drive letter, you can use the following command to map the search drive, replacing drive with the drive letter:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S16:=drive:=pathIf you map a search drive using a number already assigned to a search drive, NetWare makes the old search drive a network drive. The letter assigned to the old search drive remains assigned as the converted drive mapping. The new search drive takes the next unused letter of the alphabet.RENDERAS="SECT3"ID="FM95342"IDXID="w7931"BOOK="_idx" COLLECTION="nw41" TIDREF="i1060"IDXID="w7932"BOOK="_idx" COLLECTION="nw41" TIDREF="i1220"
Mapping Drives to Directory Map ObjectsAnother way to IDXID="w7933"BOOK="_idx" COLLECTION="nw41" TIDREF="i2333"
map a drive to a directory is to create a Directory Map object that points to the directory. Then, if you move the directory, you only need to change the Directory Map object rather than all of the login scripts that may include that mapping.It is best to use map objects in the user's current context. Don't use complete names that point to other contexts. If the map is in another context, you should create an alias that points to the real directory map object. See "BOOK="cncptenu" COLLECTION="nw41"Alias object" in Concepts.For example, to map a search drive to a Directory Map object whose complete name is APPL.SALES_LA.NOVELL_US, add the following line to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S2:=.APPL.SALES_LA.NOVELL_USIn the above example, the Directory Map object's name begins with a period, which indicates that the drive is mapped to the drive root.If the user whose login script this line appears in is also located in the SALES_LA.NOVELL_US context, the MAP command does not have to specify the Directory Map object's complete name. Instead, the line would beFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S2:=APPLFor more information about using Directory Map objects, see IDREF="FM80724""Loading Operating Systems and Applications onto the Network" on page 125.PAGENUM=223 ID="BP203"RENDERAS="SECT3"ExamplesIDXID="w7934"BOOK="_idx" COLLECTION="nw41" TIDREF="i1220"MARK=BULLETTo map the first search drive to the SYS:PUBLIC directory (which contains the NetWare utilities for DOS and MS Windows workstations) add the following line to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S1:=SYS:PUBLICIDXID="w7935"BOOK="_idx" COLLECTION="nw41" TIDREF="i1190"
The second search drive should be mapped to the DOS directory if users run DOS from the network.If your network has more than one DOS directory, use variables to indicate the directory path. These variables are replaced by the correct information from the workstation software when each user logs in.To use variables for the DOS directory path, enter the following command in the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S2:=SYS:PUBLIC\%MACHINE\%OS\%OS_VERSIONIf all users have the same types of computers and are using the same version of DOS, you probably only have one DOS directory. In this case, add a line similar to the following, substituting the correct directory names:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S2:=SYS:PUBLIC\IBM_PC\MSDOS\50You can also create a Directory Map object that points to the DOS directory, then map the search drive to the Directory Map object.For more information about creating DOS directories, see IDREF="FM12240""Loading DOS onto the Network" on page 125.To map the next available search drive to the SYS:APPL\WORDPROC directory, add the following line to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S16:=SYS:APPL\WORDPROCIf you have mapped a Directory Map object to this directory, you can substitute the Directory Map object's name for the directory path.For example, suppose you created a Directory Map object called WPROC, which is located in the context SALES.NOVELL_US, and mapped that object to the SYS:APPL\WORDPROC directory.PAGENUM=224 ID="BP204"Following the rule of no complete names in a login script, you would create an alias in your own context to the object in .SALES.NOVELL_US. Then use the following line in your IDXID="w7936"BOOK="_idx" COLLECTION="nw41" TIDREF="i3879"
login 
script:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S16:=WPROCIDXID="w7937"BOOK="_idx" COLLECTION="nw41" TIDREF="i259"IDXID="w7938"BOOK="_idx" COLLECTION="nw41" TIDREF="i1429"
Suppose an application in the FORM directory requires that it reside in the root directory of drive P:, but you don't want to put the application in the root directory for security reasons.You can map a fake root to the directory and map a search drive to it at the same time by adding the following line to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP ROOT S16:=P:=SYS:APPL\FORMTo map Richard's first four regular drive mappings to his home directory, the SYS:PUBLIC\OS2 directory (which contains the NetWare utilities for OS/2), the REPORTS directory, and the PROJECTS directory, add the following four lines to Richard's user login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP *1:=VOL1:HOME\RICHARD
MAP *2:=SYS:PUBLIC\OS
2MAP *3:=VOL1:ACCOUNTS\REPORT
SMAP *4:=VOL1:UPDATES\PROJECTSTo map Richard's fifth drive to the PUBLIC directory on a NetWare 3.11 server named FS1, you need to include the server name in the MAP command. Use the following line in your login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP *5:=FS1\SYS:PUBLICIf you are mapping a drive to a directory that is located on a volume within your current context, include the volume's common name in the MAP command, as demonstrated in the previous examples.If you are mapping a drive to a volume that is not in your current context, first create an alias to that volume; then include the volume's common name in the MAP command.For example, if the complete name of a volume not in your current context is VOL1.SALES.NOVELL_US, then create an alias named VOL1: to that volume. The MAP command would include only this common name.PAGENUM=225 ID="BP205"To map a drive to the APPL directory in this volume, the line in the login script would beFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP *6:=VOL1:APPLRENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Drive mappingsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Drive mapping" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Enabling users to run DOS from the networkCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM12240""Loading DOS onto the Network" on page 125COLNAME=1 ROTATE="0" MOREROWS="0"Setting paths for OS/2 workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User GuideCOLNAME=1 ROTATE="0" MOREROWS="0"Using Directory Map objectsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80724""Loading Operating Systems and Applications onto the Network" on page 125RENDERAS="SECT2"NO_DEFAULTIDXID="w7939"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
Use IDXID="w7940"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
NO_DEFAULT in a container or profile login script if you do not want the default user login script to run.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"NO_DEFAULTRENDERAS="SECT3"Using NO_DEFAULTIDXID="w7941"BOOK="_idx" COLLECTION="nw41" TIDREF="i2994"
If you do not want to create any user login scripts, and you do not want the default user login script to run, add this command to either the container or the profile login script.If you have created a user login script for someone, that login script executes whether or not the NO_DEFAULT command is in the container or profile login script.PAGENUM=226 ID="BP206"RENDERAS="SECT2"ID="FM91860"NOSWAPIDXID="w7942"BOOK="_idx" COLLECTION="nw41" TIDREF="i2980"
Use IDXID="w7943"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
NOSWAP to IDXID="w7944"BOOK="_idx" COLLECTION="nw41" TIDREF="i2393"
prevent the LOGIN utility from being moved out of conventional IDXID="w7945"BOOK="_idx" COLLECTION="nw41" TIDREF="i4351"
memory into higher memory (if available) or onto the disk to execute a # command and LOGIN at the same time.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"NOSWAPRENDERAS="SECT3"Using NOSWAPLOGIN always swaps to extended or expanded memory unless NOSWAP is specified on the command line or in the login script.If you do not want LOGIN to be temporarily stored in higher memory or on the workstation's disk, use the NOSWAP command. NOSWAP prevents LOGIN from being swapped out of conventional memory.Then, if the workstation does not have enough memory to handle both LOGIN and the # command, the # command fails but the rest of the login script executes as usual.If you want LOGIN to be swapped out of conventional memory immediately every time a # command is executed, place the SWAP command in the login script, before the # command.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the # commandCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM95209""# (Execute External Program)" on page 195COLNAME=1 ROTATE="0" MOREROWS="0"Using the SWAP commandCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41465""SWAP" on page 236PAGENUM=227 ID="BP207"RENDERAS="SECT2"PAUSEIDXID="w7946"BOOK="_idx" COLLECTION="nw41" TIDREF="i3258"
Use IDXID="w7947"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
PAUSE to create a pause in the execution of the login script.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"PAUSERENDERAS="SECT3"Using PAUSEEnter this command in your login script at any point you want a pause to occur.You can add PAUSE to the login script following a message so that the user has time to read the message before it scrolls off the screen.If you include PAUSE, the message "Strike any key when ready..." appears on the workstation screen. The LOGIN utility then waits for a key to be pressed before it executes the rest of the login script.RENDERAS="SECT2"ID="FM77977"PCCOMPATIBLEIDXID="w7948"BOOK="_idx" COLLECTION="nw41" TIDREF="i3264"Use IDXID="w7949"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
PCCOMPATIBLE to enable the EXIT "command" login script command to work if your workstation's LONG MACHINE NAME is not IBM_PC.This command does not apply to OS/2 workstations.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"PCCOMPATIBLERENDERAS="SECT3"Using PCCOMPATIBLEIf your computer is an IBM PC compatible machine and not an IBM PC, use PCCOMPATIBLE in your login script to inform the LOGIN utility that your machine's long name is something other than IBM_PC. The LONG MACHINE NAME (AT&T, COMPAQ, or others) must be included in the NET.CFG file.Place the following anywhere before EXIT in the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"PCCOMPATIBLE
PAGENUM=228 ID="BP208"RENDERAS="SECT3"ExampleIf you have a Hewlett Packard computer and you have changed the LONG MACHINE NAME to HE_PAC in the NET.CFG file, and you want to exit to NETADMIN from within your login script, put the following commands in your login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"PCCOMPATIBLE
EXIT "NETADMIN"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting the machine name in NET.CFGCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User GuideCOLNAME=1 ROTATE="0" MOREROWS="0"Using the EXIT commandCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM89141""EXIT" on page 205RENDERAS="SECT2"PROFILEUse PROFILE in a container script to set or override a user's assigned or command-line-specified profile script. It is useful when defining a group profile.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"PROFILE profile_object_nameRENDERAS="SECT3"ExampleTo override the profile script assigned to a user or specified at the command line, and cause the user to execute a PROFILE script called team_profile, use the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROFILE team_profile
PAGENUM=229 ID="BP209"RENDERAS="SECT2"ID="FM63873"REMARKIDXID="w7950"BOOK="_idx" COLLECTION="nw41" TIDREF="i15"IDXID="w7951"BOOK="_idx" COLLECTION="nw41" TIDREF="i12"IDXID="w7952"BOOK="_idx" COLLECTION="nw41" TIDREF="i692"IDXID="w7953"BOOK="_idx" COLLECTION="nw41" TIDREF="i3732"Use IDXID="w7954"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
REMARK to insert explanatory text into your login script. This text does not display on the screen.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"REM[ARK] [text]orFORMAT="LINESPECIFIC"MOREINFO="NONE"* [text]orFORMAT="LINESPECIFIC"MOREINFO="NONE"; [text]Replace text with the comment you want to include in the login script.RENDERAS="SECT3"Using REMARKIDXID="w7955"BOOK="_idx" COLLECTION="nw41" TIDREF="i308"IDXID="w7956"BOOK="_idx" COLLECTION="nw41" TIDREF="i4019"
To include explanatory text in your login script, begin a line with REMARK, REM, an asterisk (*), or a semicolon (;).Any text that follows these symbols is ignored when the LOGIN command executes your login script. Remarks do not appear on the screen.Using remarks in your login script can make the script much easier for you or other users to read and understand.The REMARK command and its associated text must be the only entry on a line. Placing remarks on the same line as other login script commands can cause errors.If a remark is several lines long, begin each line with the remark keyword (REMARK, REM, an asterisk, or a semicolon).PAGENUM=230 ID="BP210"RENDERAS="SECT3"ExampleThe following are examples of explanatory text that you might use with the REMARK command and its variants:FORMAT="LINESPECIFIC"MOREINFO="NONE"* This is Richard's login script
; Mapped network drives follow:
REM The next mapping is a fake root.
REMARK This login script is for new users.RENDERAS="SECT2"SCRIPT_SERVERNetWare 2 and 3 users can use SCRIPT_SERVER to set a home server from where the bindery login script is read.SCRIPT_SERVER has no effect on NetWare 4 users. RENDERAS="SECT3"Command FormatSCRIPT_SERVER server_nameRENDERAS="SECT3"Using SCRIPT_SERVERThis command has no effect on NetWare Directory Services.PAGENUM=231 ID="BP211"RENDERAS="SECT2"ID="FM74868"SETIDXID="w7957"BOOK="_idx" COLLECTION="nw41" TIDREF="i4750"IDXID="w7958"BOOK="_idx" COLLECTION="nw41" TIDREF="i1190"IDXID="w7959"BOOK="_idx" COLLECTION="nw41" TIDREF="i1330"IDXID="w7960"BOOK="_idx" COLLECTION="nw41" TIDREF="i4093"
Use SET to set a DOS or OS/2 environment variable to a specified value.For OS/2 workstations, SET commands affect the environment only while the login script is running; the settings disappear when LOGIN terminates.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"[TEMP] SET name="value"Replace name with an environment parameter that identifies the environment you want to change.Replace value with identifier variable substitutions. Values must be enclosed in quotation marks.To change the environment for the login script, but not for the workstation itself after the login script has finished executing, use the optional keyword TEMP.Variables set in the login script for an OS/2 workstation affect the environment only while the login script is running. Therefore, the TEMP option does not work with OS/2 workstations.RENDERAS="SECT3"Using SETUse the SET login script command the same way you use the DOS command called SET. However, when you use SET in a login script, you must enter quotation marks (" ") around values.If a variable is set to a path that ends in a \", these two characters are interpreted as an embedded quote preceded by an escape character. To avoid this problem, use two backslashes before the ending double quotes (\\").SET commands do not have to be included in login scripts.For example, you may decide that it is easier to put some SET commands in the workstation's AUTOEXEC.BAT file. Where you use SET commands depends upon your individual needs.For information about values you can set, see the SET command in your DOS or OS/2 documentation.PAGENUM=232 ID="BP212"This command does not work in a login script if the DOS workstation's environment is too small. In this case, you should set the environment size in the CONFIG.SYS file.See the SHELL command in your DOS manual for more information about the environment size. (OS/2 workstations do not have this limitation.)After you use the SET command to set a value for an environment variable, you can use that variable in other login script commands.To include an environment variable as an identifier variable in a command, enclose the name of the variable in angle brackets; for example, <emailuser>.RENDERAS="SECT3"ExamplesMARK=BULLETIDXID="w7961"BOOK="_idx" COLLECTION="nw41" TIDREF="i1190"IDXID="w7962"BOOK="_idx" COLLECTION="nw41" TIDREF="i3574"
You can use SET to make a prompt display the current directory path, such as F:\HOME\MARY>, rather than just the drive letter. To do this, add the following line to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET PROMPT="$P$G""$P" lists the current directory path; "$G" displays a ">" (greater than) character. See your DOS or OS/2 manual for more information.To set a path for a program called DAILY, which is in the REPORTS subdirectory beneath drive G:, you would add the following line:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET PATH="G:\REPORTS\DAILY"This sets the variable PATH to G:\REPORTS\DAILY.Setting the variable PATH in the login script removes any search drives previously assigned. Use SET PATH only before you map search drives. SET PATH also overwrites any paths set in the user's AUTOEXEC.BAT file.To display this path, you can include PATH as an identifier variable in a WRITE command by enclosing the variable (not the value) in angle brackets. For example, the following line displays "My path is G:\REPORTS\DAILY"FORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "My path is "%<path>To include an environment variable in a MAP command, precede the variable with a percent sign (%).PAGENUM=233 ID="BP213"For example, you could include the following lines in a login script to set and map a drive to the variable NWS:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NWS="C:\XYZ"
MAP S16:=%<NWS>RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using environment variables as identifier variables in other login script commandsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM24405""Identifier Variables" on page 240COLNAME=1 ROTATE="0" MOREROWS="0"Using the SET commandCOLNAME=2 ROTATE="0" MOREROWS="0"Your DOS or OS/2 manualRENDERAS="SECT2"SET_TIMEIDXID="w7963"BOOK="_idx" COLLECTION="nw41" TIDREF="i4113"
Use SET_TIME to IDXID="w7964"BOOK="_idx" COLLECTION="nw41" TIDREF="i4846"
set the IDXID="w7965"BOOK="_idx" COLLECTION="nw41" TIDREF="i4478"
workstation time equal to the time on the NetWare server that the workstation first connects to.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"SET_TIME ON|OFFRENDERAS="SECT3"Using SET TIMEThe default value is IDXID="w7966"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
SET_TIME ON, which means the workstation time is set to the NetWare server time whenever the user logs in. If you include SET_TIME OFF in the login script, the workstation time does not update to the server's time.RENDERAS="SECT2"ID="FM57858"SHIFTIDXID="w7967"BOOK="_idx" COLLECTION="nw41" TIDREF="i4137"IDXID="w7968"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"IDXID="w7969"BOOK="_idx" COLLECTION="nw41" TIDREF="i2221"IDXID="w7970"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"
Use IDXID="w7971"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
SHIFT to change the order in which %n identifier variables are interpreted in the login script. SHIFT allows users to enter LOGIN parameters in any order.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"SHIFT [n]
PAGENUM=234 ID="BP214"Replace n with the number of places you want the variable to shift. The default is SHIFT 1.RENDERAS="SECT3"Using SHIFTYou can shift up to 10 arguments.When users execute LOGIN, they can include additional parameters. Each of these parameters is assigned a IDXID="w7972"BOOK="_idx" COLLECTION="nw41" TIDREF="i14"
%n variable; in this way, the parameter's real value can be substituted for the %n variable that appears in the login script.In the login script, you can add SHIFT with a positive or negative number to move the variables in either direction. For example, SHIFT -3 moves each %n variable three positions to the left.RENDERAS="SECT3"ExampleWhen Mary logs in, she wants to access her word processing program, change the way it is set up, and map a drive to her work directory called ACCNTS.Mary also has a command in her login script to map a drive to her LOTUS directory, but she does not need it today. The commands in Mary's login script are shown here.FORMAT="LINESPECIFIC"MOREINFO="NONE"LOOP
IF "%2"="WP" THEN   SET WP="\U-CML\B-10\D" 
MAP S16:=SYS:APPL\WP\SETUP
IF "%2"="ACCNTS" THEN   
MAP G:=SYS:ACCNTS
IF "%2"="LOTUS" THEN   
MAP S16:=SYS:APPL\LOTUS
SHIFT
IF "%2"<>"" THEN GOTO LOOP(In the last line, "IF "%2" <>" is followed by closed quotation marks, which means "If %2 isn't blank".)With these commands in her login script, Mary can log in to the primary file server (named FS1) using her username, MARY, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN FS1\MARY WP ACCNTS
PAGENUM=235 ID="BP215"The parameters in Mary's LOGIN command are given the following values:TYPE="VERT"%0=FS1%1=MARY%2=WP%3=ACCNTSMary's login script looks for %2, which is WP, and sets the word processing environment. Then the login script shifts the variables one to the right so that %2 now becomes ACCNTS. Upon executing the loop, the login script maps a drive to the ACCNTS directory.Mary could also change the order of her LOGIN command without affecting the way her work environment is set up, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN MARY ACCNTS WPThe parameters in this LOGIN command are given the following values:TYPE="VERT"%0=FS1%1=MARY%2=ACCNTS%3=WPIn this case, Mary's login script looks for %2, which is now ACCNTS.The login script maps a drive to the ACCNTS directory. Then the login script shifts the variables to the right so that %2 now becomes WP.Upon executing the loop, the login script sets the word processing environment.PAGENUM=236 ID="BP216"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using %n variables in login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM38017"Table 3-6 on page 241RENDERAS="SECT2"ID="FM41465"SWAPIDXID="w7973"BOOK="_idx" COLLECTION="nw41" TIDREF="i4351"
Use IDXID="w7974"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
SWAP to move the LOGIN utility out of conventional memory into higher memory (if available) or onto the disk. This allows execution of a # command and LOGIN at the same time.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"SWAP [path]You can replace path with either a drive letter or a full directory path beginning with the NetWare volume name.RENDERAS="SECT3"Using SWAPBy default, the LOGIN utility always swaps to extended or expanded memory, unless NOSWAP is specified on the command line or in the login script.The SWAP option doesn't work with the DR DOS 6.0 EMM386 Memory Manager option unless upper memory is disabled.If you specify a path in the SWAP command, LOGIN swaps into the directory you specified. If the directory specified in that path does not exist or if you do not have rights there, LOGIN prompts you for another path.If you don't specify a path, LOGIN swaps either into higher memory (if available) or to the current drive. If LOGIN tries to swap to the current drive and you don't have rights to the current drive, LOGIN prompts you for a path to use. If you specify a valid path, LOGIN always swaps to the specified path.Then, if the workstation doesn't have enough memory to handle both LOGIN and the # command, the # command fails but the rest of the login script executes as usual.PAGENUM=237 ID="BP217"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the # commandCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM95209""# (Execute External Program)" on page 195COLNAME=1 ROTATE="0" MOREROWS="0"Using the NOSWAP commandCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM91860""NOSWAP" on page 226RENDERAS="SECT2"TEMP SETSee IDREF="FM74868""SET" on page 231.RENDERAS="SECT2"ID="FM10783"WRITEIDXID="w7975"BOOK="_idx" COLLECTION="nw41" TIDREF="i4850"IDXID="w7976"BOOK="_idx" COLLECTION="nw41" TIDREF="i692"IDXID="w7977"BOOK="_idx" COLLECTION="nw41" TIDREF="i2418"IDXID="w7978"BOOK="_idx" COLLECTION="nw41" TIDREF="i4473"Use IDXID="w7979"BOOK="_idx" COLLECTION="nw41" TIDREF="i2210"
WRITE to display messages on the workstation screen when a user logs in.RENDERAS="SECT3"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "[text][%identifier]" [;][identifier]Replace text with the words you want to display on the screen.Replace identifier with a variable you want to display, such as a user's login name. (See IDREF="FM94135""Using Identifier Variables" on page 243 for a complete list of variables.)RENDERAS="SECT3"Using WRITEText you want to display must be enclosed in quotation marks ("").IDXID="w7980"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"
There are several ways to display variables in the text message. The way you enter the variable in the WRITE command determines the display format, as follows:MARK=BULLETIf you type the identifier variable exactly as shown, with no special punctuation, only the variable is displayed on the screen. (See IDREF="FM38017""Login Script Identifier Variables" on page 241)If you enclose the identifier variable inside quotation marks, precede the variable with a percent sign (%), and type it in uppercase letters.PAGENUM=238 ID="BP218"This method is often used to combine regular text with an identifier variable because both the text and the variable can be enclosed in the same quotation marks.To join several text strings and identifier variables into a single display without enclosing the variables in quotation marks, use a semicolon between the text and the variables.If you have several WRITE commands, each one appears on a separate line on your workstation. However, if you put a semicolon at the end of all but the last WRITE commands, the displays all appear as one continuous sentence or paragraph (although they may wrap onto additional lines on the workstation's screen).Text strings can include the following special characters:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"CharacterCOLNAME=2 ROTATE="0" MOREROWS="0"MeaningVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"\rCOLNAME=2 ROTATE="0" MOREROWS="0"Makes a carriage return occurCOLNAME=1 ROTATE="0" MOREROWS="0"\nCOLNAME=2 ROTATE="0" MOREROWS="0"Starts a new line of the textCOLNAME=1 ROTATE="0" MOREROWS="0"\"COLNAME=2 ROTATE="0" MOREROWS="0"Displays a quotation mark on the screenCOLNAME=1 ROTATE="0" MOREROWS="0"\7COLNAME=2 ROTATE="0" MOREROWS="0"Makes a beep soundIn addition to the semicolon, there are additional operators you can use to form compound strings (in other words, to join text and identifier variables into one command). These operators are listed in the following table, in order of precedence.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OperatorCOLNAME=2 ROTATE="0" MOREROWS="0"MeaningVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"* / %COLNAME=2 ROTATE="0" MOREROWS="0"Multiply, divide, modulosCOLNAME=1 ROTATE="0" MOREROWS="0"+ -COLNAME=2 ROTATE="0" MOREROWS="0"Add, subtractCOLNAME=1 ROTATE="0" MOREROWS="0">> <<COLNAME=2 ROTATE="0" MOREROWS="0"Shift left or right (1000 >> 3 becomes 1)PAGENUM=239 ID="BP219"RENDERAS="SECT3"ExamplesMARK=BULLETTo display the message "Hello," add the following line to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "Hello"To display the user's last name (surname) along with a greeting, add the identifier LAST_NAME to the command. To do this, either join the text and the identifier with a semicolon or include the variable in the quotation marks with the text.Either of the following lines displays "Hello, Smith" when user Bob Smith logs in:FORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "Hello, ";%LAST_NAMEFORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "Hello, %LAST_NAME"To make a beep sound occur while the phrase "Good morning" appears on the screen, add the following line to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "Good %GREETING_TIME \7"
PAGENUM=240 ID="BP220"RENDERAS="SECT1"ID="FM24405"Identifier VariablesIDXID="w7981"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
With 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 LAST_NAME), rather than a specific name (such as Smith) in a login script command. When the login script executes, it substitutes real values for the identifier variables.By using the variable, you can make the login script command applicable to many users instead of limiting it to one user.For example, the commandFORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "Hello, "%LAST_NAMEdisplays the following message on Bob's Smith's workstation screen when he logs in:FORMAT="LINESPECIFIC"MOREINFO="NONE"Hello, SMITHSimilarly, when Mary Jones logs in, the message she sees isFORMAT="LINESPECIFIC"MOREINFO="NONE"Hello, JONESIn the previous example, when the user logged in, the user's actual last name was substituted for the LAST_NAME variable in the command.PAGENUM=241 ID="BP221"IDREF="FM38017"Table 3-6 lists all the available identifier variables.ID="FM82950"IDXID="w7982"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"  IDXID="w7983"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"LABEL="3-6" PGWIDE=1 TOCENTRY="1"ID="FM38017"Login Script Identifier VariablesCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="10*"COLNAME=3 COLWIDTH="18*"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"IDXID="w7984"BOOK="_idx" COLLECTION="nw41" TIDREF="i939"IDXID="w7985"BOOK="_idx" COLLECTION="nw41" TIDREF="i4478"IDXID="w7986"BOOK="_idx" COLLECTION="nw41" TIDREF="i942"
DAYCOLNAME=3 ROTATE="0" MOREROWS="0"Day number (01 through 31)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7987"BOOK="_idx" COLLECTION="nw41" TIDREF="i945"
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"IDXID="w7988"BOOK="_idx" COLLECTION="nw41" TIDREF="i2513"
MONTHCOLNAME=3 ROTATE="0" MOREROWS="0"Month number (01 through 12)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7989"BOOK="_idx" COLLECTION="nw41" TIDREF="i2514"
MONTH_NAMECOLNAME=3 ROTATE="0" MOREROWS="0"Month name (January, February, etc.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7990"BOOK="_idx" COLLECTION="nw41" TIDREF="i2627"
NDAY_OF_WEEKCOLNAME=3 ROTATE="0" MOREROWS="0"Weekday number (1 through 7; 1=Sunday)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7991"BOOK="_idx" COLLECTION="nw41" TIDREF="i4141"
SHORT_YEARCOLNAME=3 ROTATE="0" MOREROWS="0"Last two digits of year (94, 95, 96, etc.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7992"BOOK="_idx" COLLECTION="nw41" TIDREF="i4868"
YEARCOLNAME=3 ROTATE="0" MOREROWS="0"All four digits of year (1994, 1995, 1996, etc.)COLNAME=1 ROTATE="0" MOREROWS="0"TimeCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7993"BOOK="_idx" COLLECTION="nw41" TIDREF="i171"
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"IDXID="w7994"BOOK="_idx" COLLECTION="nw41" TIDREF="i1613"
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"IDXID="w7995"BOOK="_idx" COLLECTION="nw41" TIDREF="i1702"
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"IDXID="w7996"BOOK="_idx" COLLECTION="nw41" TIDREF="i1703"
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"IDXID="w7997"BOOK="_idx" COLLECTION="nw41" TIDREF="i2469"
MINUTECOLNAME=3 ROTATE="0" MOREROWS="0"Minute (00 through 59)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7998"BOOK="_idx" COLLECTION="nw41" TIDREF="i3986"
SECONDCOLNAME=3 ROTATE="0" MOREROWS="0"Second (00 through 59)COLNAME=1 ROTATE="0" MOREROWS="0"UserCOLNAME=2 ROTATE="0" MOREROWS="0"%CNCOLNAME=3 ROTATE="0" MOREROWS="0"User's full login name as it exists in NDSCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"ALIAS_CONTEXTCOLNAME=3 ROTATE="0" MOREROWS="0""Y" IF REQUESTER_CONTEXT is an AliasCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w7999"BOOK="_idx" COLLECTION="nw41" TIDREF="i1587"IDXID="w8000"BOOK="_idx" COLLECTION="nw41" TIDREF="i2571"IDXID="w8001"BOOK="_idx" COLLECTION="nw41" TIDREF="i4713"
FULL_NAMECOLNAME=3 ROTATE="0" MOREROWS="0"User's unique username. It is the value of the FULL_NAME property for both NDS and bindery- based NetWare. Spaces are replaced with underscoresCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8002"BOOK="_idx" COLLECTION="nw41" TIDREF="i2094"IDXID="w8003"BOOK="_idx" COLLECTION="nw41" TIDREF="i2571"IDXID="w8004"BOOK="_idx" COLLECTION="nw41" TIDREF="i4713"
LAST_NAMECOLNAME=3 ROTATE="0" MOREROWS="0"User's last name (surname) in NetWare Directory Services, or full login name in bindery-based NetWareCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8005"BOOK="_idx" COLLECTION="nw41" TIDREF="i2224"IDXID="w8006"BOOK="_idx" COLLECTION="nw41" TIDREF="i817"
LOGIN_CONTEXTCOLNAME=3 ROTATE="0" MOREROWS="0"Context where user existsCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8007"BOOK="_idx" COLLECTION="nw41" TIDREF="i2225"IDXID="w8008"BOOK="_idx" COLLECTION="nw41" TIDREF="i2571"IDXID="w8009"BOOK="_idx" COLLECTION="nw41" TIDREF="i4713"
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"IDXID="w8010"BOOK="_idx" COLLECTION="nw41" TIDREF="i2374"IDXID="w8011"BOOK="_idx" COLLECTION="nw41" TIDREF="i1617"
MEMBER OF "group"COLNAME=3 ROTATE="0" MOREROWS="0"Group object that the user is assigned toCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8012"BOOK="_idx" COLLECTION="nw41" TIDREF="i2981"
NOT MEMBER OF "group"COLNAME=3 ROTATE="0" MOREROWS="0"Group object that the user is not assigned toCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8013"BOOK="_idx" COLLECTION="nw41" TIDREF="i3252"IDXID="w8014"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
PASSWORD_EXPIRESCOLNAME=3 ROTATE="0" MOREROWS="0"Number of days before password expiresCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8015"BOOK="_idx" COLLECTION="nw41" TIDREF="i3800"IDXID="w8016"BOOK="_idx" COLLECTION="nw41" TIDREF="i817"
REQUESTER_CONTEXTCOLNAME=3 ROTATE="0" MOREROWS="0"Context when login startedCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8017"BOOK="_idx" COLLECTION="nw41" TIDREF="i4733"IDXID="w8018"BOOK="_idx" COLLECTION="nw41" TIDREF="i4713"
USER_IDCOLNAME=3 ROTATE="0" MOREROWS="0"Number assigned to each userCOLNAME=1 ROTATE="0" MOREROWS="0"NetworkCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8019"BOOK="_idx" COLLECTION="nw41" TIDREF="i1492"IDXID="w8020"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
FILE_SERVERIDXID="w8021"BOOK="_idx" COLLECTION="nw41" TIDREF="i94"IDXID="w8022"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"IDXID="w8023"BOOK="_idx" COLLECTION="nw41" TIDREF="i2894"
NETWORK_ADDRESSIDXID="w8024"BOOK="_idx" COLLECTION="nw41" TIDREF="i4846"COLNAME=3 ROTATE="0" MOREROWS="0"NetWare server nameIPX external network number of the cabling system (8-digit hexadecimal number)COLNAME=1 ROTATE="0" MOREROWS="0"WorkstationCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8025"BOOK="_idx" COLLECTION="nw41" TIDREF="i2256"
MACHINEIDXID="w8026"BOOK="_idx" COLLECTION="nw41" TIDREF="i712"COLNAME=3 ROTATE="0" MOREROWS="0"Type IDXID="w8027"BOOK="_idx" COLLECTION="nw41" TIDREF="i2967"
of IDXID="w8028"BOOK="_idx" COLLECTION="nw41" TIDREF="i2601"
computer 
(IBM_PC, etc.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8029"BOOK="_idx" COLLECTION="nw41" TIDREF="i2834"IDXID="w8030"BOOK="_idx" COLLECTION="nw41" TIDREF="i2785"
NETWARE_REQUESTERCOLNAME=3 ROTATE="0" MOREROWS="0"Version of the NetWare Requester for OS/2 or VLM usersCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8031"BOOK="_idx" COLLECTION="nw41" TIDREF="i3127"IDXID="w8032"BOOK="_idx" COLLECTION="nw41" TIDREF="i1190"
OSCOLNAME=3 ROTATE="0" MOREROWS="0"Type of operating system on the workstation (MSDOS, OS2, etc.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8033"BOOK="_idx" COLLECTION="nw41" TIDREF="i3146"IDXID="w8034"BOOK="_idx" COLLECTION="nw41" TIDREF="i1190"
OS_VERSIONCOLNAME=3 ROTATE="0" MOREROWS="0"Operating system version on the workstation (3.30, etc.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8035"BOOK="_idx" COLLECTION="nw41" TIDREF="i3644"IDXID="w8036"BOOK="_idx" COLLECTION="nw41" TIDREF="i94"IDXID="w8037"BOOK="_idx" COLLECTION="nw41" TIDREF="i2950"
P_STATIONIDXID="w8038"BOOK="_idx" COLLECTION="nw41" TIDREF="i4846"COLNAME=3 ROTATE="0" MOREROWS="0"Workstation's node number (12-digit hexadecimal)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8039"BOOK="_idx" COLLECTION="nw41" TIDREF="i4136"IDXID="w8040"BOOK="_idx" COLLECTION="nw41" TIDREF="i4135"IDXID="w8041"BOOK="_idx" COLLECTION="nw41" TIDREF="i2784"
SHELL_TYPEIDXID="w8042"BOOK="_idx" COLLECTION="nw41" TIDREF="i2806"COLNAME=3 ROTATE="0" MOREROWS="0"Version of the workstation's DOS shell (1.02, etc.); supports NetWare 2 and 3 shells and NetWare 4 Requester for DOS.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8043"BOOK="_idx" COLLECTION="nw41" TIDREF="i2601"IDXID="w8044"BOOK="_idx" COLLECTION="nw41" TIDREF="i2256"
SMACHINEIDXID="w8045"BOOK="_idx" COLLECTION="nw41" TIDREF="i712"COLNAME=3 ROTATE="0" MOREROWS="0"IDXID="w8046"BOOK="_idx" COLLECTION="nw41" TIDREF="i2967"
Short machine name (IBM, etc.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8047"BOOK="_idx" COLLECTION="nw41" TIDREF="i4275"IDXID="w8048"BOOK="_idx" COLLECTION="nw41" TIDREF="i4846"IDXID="w8049"BOOK="_idx" COLLECTION="nw41" TIDREF="i784"
STATIONCOLNAME=3 ROTATE="0" MOREROWS="0"Workstation's connection numberCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8050"BOOK="_idx" COLLECTION="nw41" TIDREF="i1330"
DOS 
environmentCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8051"BOOK="_idx" COLLECTION="nw41" TIDREF="i1756"IDXID="w8052"BOOK="_idx" COLLECTION="nw41" TIDREF="i4750"
<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 MAP, COMSPEC, and FIRE PHASERS commands add a percent sign (%) in front of the variable. For example,MAP S16:=%<path>COLNAME=1 ROTATE="0" MOREROWS="0"MiscellaneousCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8053"BOOK="_idx" COLLECTION="nw41" TIDREF="i54"IDXID="w8054"BOOK="_idx" COLLECTION="nw41" TIDREF="i58"
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"IDXID="w8055"BOOK="_idx" COLLECTION="nw41" TIDREF="i1347"
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. For more information, see IDREF="FM38017"Table 3-6 on page 241.COLNAME=1 ROTATE="0" MOREROWS="0"Object propertiesCOLNAME=2 ROTATE="0" MOREROWS="0"property nameCOLNAME=3 ROTATE="0" MOREROWS="0"You can use property values of NDS objects as variables. Use the property values just as you do any other identifier variable. If the property value includes a space, enclose the name in quotation marks.To use a property name with a space, within a WRITE statement, you must place it at the end of the quoted string:WRITE "Given name=%GIVEN_NAME"IF "%MESSAGE SERVER"="MS1" THENMAP INS S16:=MS1\SYS:EMAILTo see a list of object properties, see Appendix A, "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties," of Utilities Reference. Not all properties are supported.PAGENUM=243 ID="BP222"RENDERAS="SECT2"ID="FM94135"Using Identifier VariablesIDXID="w8056"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"When using identifier variables in login script commands, observe the following conventions.MARK=BULLETIDXID="w8057"BOOK="_idx" COLLECTION="nw41" TIDREF="i1759"
Identifier variables are used most often with commands such as IF...THEN, MAP, and WRITE. They can also be used with commands for which you can specify a path, such as COMSPEC.Type the variable exactly as shown.To use DOS environment variables as identifiers, enclose them in angle brackets.PAGENUM=244 ID="BP223"Identifier variables can be placed within literal text strings in a WRITE statement. However, the identifier variable must be in uppercase letters and preceded by a percent sign. (Literal text is the text that is displayed on the screen, such as "Sales report is due today." Literal text must be enclosed in quotation marks.)RENDERAS="SECT3"Examples:IDXID="w8058"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"MARK=BULLETIf user Smith logs in during the morning, both of the following lines display the same message on his screen ("Good morning, SMITH"):FORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "Good "; GREETING_TIME; ", "; LAST_NAME
WRITE "Good %GREETING_TIME, %LAST_NAME"To use DOS environment variables as identifiers, enclose them in angle brackets. The following example uses the DOS environment variable "path:"FORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "my path is "%<path>The text displayed on the screen is similar toFORMAT="LINESPECIFIC"MOREINFO="NONE"my path is z:.;y:.;c:\WINDOWSRENDERAS="SECT2"Using LOGIN Parameters with %n VariablesIDXID="w8059"BOOK="_idx" COLLECTION="nw41" TIDREF="i14"IDXID="w8060"BOOK="_idx" COLLECTION="nw41" TIDREF="i1755"Some variables in a login script can be indicated by a percent sign (%) followed by a number from 0 to 9.When a user logs in, he or she can type additional parameters that the LOGIN utility passes to the login script. The login script then substitutes these parameters for any %n variables in the login script. These variables are replaced in order by the parameters the user typed when executing the LOGIN utility.The %0 variable is replaced by the name of the NetWare server the user typed at the command line, and %1 is replaced by the user's login name. The remaining variables change, depending on what the user types when executing LOGIN. The %n variables must precede all command line options.The SHIFT login script command allows you to change the order in which these %n variables are substituted. For more information about the SHIFT command, see IDREF="FM57858""SHIFT" on page 233.PAGENUM=245 ID="BP224"The %n variables can be used in WRITE statements if included within the quotes:FORMAT="LINESPECIFIC"MOREINFO="NONE"WRITE "My login name is %1."RENDERAS="SECT3"ExampleSuppose a login script contains the following commands:FORMAT="LINESPECIFIC"MOREINFO="NONE"IF "%2"="SALES" THEN
   WRITE "Meeting today"
END
IF "%3"="LEGAL" THEN
WRITE "Report is due tomorrow"
ENDIf user RON logged in by typing the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN COUNT\RON SALES MARKETINGthen the login script would substitute the values Ron entered at the keyboard for the %n variables in the login script, as shown here:%0=COUNTTYPE="VERT"%1=RON%2=SALES%3=MARKETINGSince %2 is replaced by "SALES," the message "Meeting today" is displayed on Ron's screen. However, since %3 is replaced by "Marketing," Ron doesn't see "Report is due tomorrow."PAGENUM=246 ID="BP225"RENDERAS="SECT1"IDXID="w8061"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"ID="FM41942"Examples of Login ScriptsThe IDXID="w8062"BOOK="_idx" COLLECTION="nw41" TIDREF="i2214"
following examples of login scripts may help you plan your own container, profile, and user login scripts. Each example login script is shown in a table.The left column of each table shows the commands in the login script. The right column explains the command's purpose.For instructions on creating login scripts, see IDREF="FM30839""Creating or Modifying a Login Script Using NetWare Administrator" on page 184 or IDREF="FM17542""Creating or Modifying a Login Script Using NETADMIN" on page 186.RENDERAS="SECT2"ID="FM58770"Default Login ScriptIDXID="w8063"BOOK="_idx" COLLECTION="nw41" TIDREF="i118"
The default login script executes the first time User object ADMIN logs in. It also executes for any users who do not have user login scripts.You can't modify the default login script because it is coded into the LOGIN utility. Instead, you can create container, profile, or user login scripts.The following table lists the content of the default login script.LABEL="3-7" PGWIDE=1 TOCENTRY="1"Default Login ScriptCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Login Script CommandCOLNAME=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 LOGIN_NAME is the same as 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, the first drive is mapped to SYS:SYSTEM instead of to the user's home directory.COLNAME=1 ROTATE="0" MOREROWS="0"MAP P:=SYS:PUBLICCOLNAME=2 ROTATE="0" MOREROWS="0"If the user logs in from an OS/2 workstation, drive P: is mapped to SYS:PUBLIC.This mapping is used by OS/2 workstations, as explained in 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.If the user is not using an OS/2 workstation, this drive mapping is not included in the default login script.COLNAME=1 ROTATE="0" MOREROWS="0"MAP INS S1:=SYS:PUBLICMAP INS S2:=SYS:PUBLIC\%MACHINE\%OS\  %OS_VERSIONCOLNAME=2 ROTATE="0" MOREROWS="0"If the user is using a DOS or MS Windows workstation, the first search drive is mapped to SYS:PUBLIC, where DOS-based NetWare utilities are stored.Then the second search drive is mapped to the directory where DOS is stored. (The two MAP commands are joined by a semicolon.)If the user logs in from an OS/2 workstation, these drive mappings are not included in the default login script.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 on the user's screen.PAGENUM=248 ID="BP226"RENDERAS="SECT2"IDXID="w8064"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Container Login ScriptThe 
container login script should contain as much information as possible that applies to all users. An example is shown in the following table.  LABEL="3-8" PGWIDE=1 TOCENTRY="1"Sample Container Login ScriptCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="18*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Login script commandCOLNAME=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 *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 LOGIN_NAME is the same as 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, the first drive is mapped to SYS:SYSTEM instead of to the user's home directory.COLNAME=1 ROTATE="0" MOREROWS="0"IF OS="OS2" THENMAP P:=SYS:PUBLICELSEMAP 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 workstation, drive P: is mapped to SYS:PUBLIC.This mapping is used by OS/2 workstations, as explained in 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.If the user is not using an OS/2 workstation, 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.If all workstations use DOS, you can use the following two commands instead of the IF...THEN command:MAP INS S1:=SYS:PUBLICMAP 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 the 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 EMAIL 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 (Novell DynaText*).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 Group object MANAGERS, the login 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 Group object TESTERS, the login 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, %LAST_NAME."COLNAME=2 ROTATE="0" MOREROWS="0"Displays a greeting to the user. Example: "Good morning, SMITH."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 3COLNAME=2 ROTATE="0" MOREROWS="0"Makes the phaser sound occur three times to tell the user that the login process is complete.PAGENUM=250 ID="BP227"RENDERAS="SECT2"ID="FM13871"IDXID="w8065"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Profile Login ScriptIf you have groups of users with identical login script needs, you can create a Profile object, then create a login script for it. Then you can assign each user to be a member of that Profile object.The following table shows an 
example of a profile login script you might create for users in the Profile object ACCOUNTING. This profile login script would execute after the container login script had executed.  LABEL="3-9" PGWIDE=1 TOCENTRY="1"Sample Profile Login ScriptCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Login script commandCOLNAME=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 any user login scripts from executing.If you want a user login script to execute after the profile login script, put these lines at the end of the user login script instead.(DOS workstations with the machine name IBM_PC do not need the PCCOMPATIBLE line.)The EXIT command does not work on OS/2 workstations.PAGENUM=252 ID="BP228"RENDERAS="SECT2"IDXID="w8066"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
User Login ScriptThe following table shows an example of a user login script for user Mary. The user login script executes after the container and profile login scripts have executed.  LABEL="3-10" PGWIDE=1 TOCENTRY="1"Sample User Login ScriptCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Login script commandCOLNAME=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 login 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 login scripts) to the FORMS directory.COLNAME=1 ROTATE="0" MOREROWS="0"REM Mary needs access to FORMS while she's on the REM troubleshooting team. Remove this drive mapping REM when she's reassigned.COLNAME=2 ROTATE="0" MOREROWS="0"This remark is intended as a reminder to the person who created the login script.This remark isn't displayed on the user's screen. (Because the remark is several lines long, each line starts with 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 her word processing application.COLNAME=1 ROTATE="0" MOREROWS="0"SET USR="mrichard"COLNAME=2 ROTATE="0" MOREROWS="0"Sets Mary's username (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 nonnetwork 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 stations with the machine name IBM_PC don't need the PCCOMPATIBLE line.)EXIT doesn't work on OS/2 workstations.LABEL="4"PAGENUM=253 ID="BP229"Creating MenusRENDERAS="SECT1"ID="FM57011"Creating, Converting, and Modifying Menu FilesMenus create a simple front end to the users' working environment. They make it easy to access network resources by presenting a list of options instead of requiring the user to enter cryptic DOS commands.Menus can be shared by multiple users, requiring the creation of fewer menus. Or, for the unique requirements of some users, custom menus can be easily created as needed.In the NetWare 4TM operating system, IDXID="w8067"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
NMENU.BAT replaces the IDXID="w8068"BOOK="_idx" COLLECTION="nw41" TIDREF="i3668"
MENU.EXE utility included in earlier versions of NetWare. IDXID="w8069"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
NMENU files are easy to script, require less memory, and run faster than did the old MENU utility files.Existing menu files from earlier NetWare versions can be easily converted for use by the newer NMENU program (see IDREF="FM81162""Converting Old Menu Files" on page 280). NMENU works in all versions of NetWare® 2, NetWare 3, and NetWare 4.Because NMENU relies on special files to execute, and those files are dependent upon a few special commands, this chapter focuses on use of the scripting commands that make up a menu file.Guidelines for planning your menus are located in IDREF="FM71323""Planning Your Menus" on page 261. Commands and their usage are explained in IDREF="FM54366""Using the NMENU Commands" on page 262. Several example programs are given in IDREF="FM50463""Creating a Menu File" on page 274.Making menus available to users (see IDREF="FM95514""Setting Up the User Environment" on page 278) and converting old menu files (see IDREF="FM81162""Converting Old Menu Files" on page 280) are the final two topics of this chapter.PAGENUM=254 ID="BP230"RENDERAS="SECT1"Getting Acquainted with NMENUSince the sole function of NMENU is to cause a scripted file to execute, there is little to learn about NMENU.BAT except its syntax. The command is followed by the menu filename.RENDERAS="SECT2"IDXID="w8070"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
NMENU SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"nmenu filenameReplace filename with the menu filename.PAGENUM=255 ID="BP231"RENDERAS="SECT2"What Menus Look LikeIDREF="FM73736"Figure 4-1 shows the display created by a single-window menu with only three options. Whether a menu displays one or more windows, the top and bottom bars of the screen remain the same.The top bar always displays the NMENU version number on the left and the day, date, and time on the right. The bottom bar displays the available options.LABEL="4-1" FLOAT="0"IDXID="w8071"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"ID="FM73736"A Single-Window MenuFILEREF="n41su81a.tif"When you create menus with multiple windows, the windows cascade from left to right (see IDREF="FM90573""A Multiple-Window Menu" on page 257). Window sizing is automatically determined by the content of each window.PAGENUM=256 ID="BP232"RENDERAS="SECT2"What Makes Menus WorkYou create menu files with a text editor and save the file with a .SRC extension. Then you use the MENUMAKE program to compile the file. It is given a .DAT extension and, as a compiled file, is no longer editable. Any edits must be made to the .SRC file and then the .SRC file must be recompiled.RENDERAS="SECT3"IDXID="w8072"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
Elements of a MenuThere are three primary elements to every menu: MENU, ITEM, and EXEC. As these elements are expanded and repeated, controlled options are displayed within each window.IDREF="FM33751"Figure 4-2 shows the .SRC file used to create the menu in IDREF="FM73736"Figure 4-1. This file shows how these three elements are used. Details about these elements and their options are covered later in the chapter.LABEL="4-2" FLOAT="0"ID="FM33751"Primary Elements of a MenuFILEREF="n41su74a.tif"MARK=BULLETElement 1: MENUMENU specifies a window within the menu file. It includes a menu number and a menu name. The menu name is the title bar for the menu.Element 2: ITEMITEM includes the text the user will see. It is given an indicator letter by default, or you can determine the character to precede it. Each option to be displayed in the window must be preceded by the word ITEM. Some options are available for the ITEM line; these options are discussed in IDREF="FM31184""ITEM" on page 264.PAGENUM=257 ID="BP233"Element 3: EXECEXEC is the primary command for the third element. In the menu file shown in IDREF="FM33751"Figure 4-2, EXEC issues three separate commands: a directory listing, a display of the current version of DOS running, and a command to exit the menu.RENDERAS="SECT3"Combining the ElementsIDREF="FM90573"Figure 4-3 illustrates a menu with 10 windows, created by including 10 MENU commands in the same file. Each window is automatically sized and cascaded across the screen.LABEL="4-3" FLOAT="0"ID="FM90573"A Multiple-Window MenuFILEREF="n41su83a.tif"RENDERAS="SECT3"ID="FM27236"Menu Creation StepsThere are generally six steps to follow when considering a new menu. The relationship between steps is shown in IDREF="FM93890"Figure 4-4.PAGENUM=258 ID="BP234"LABEL="4-4" FLOAT="0"IDXID="w8073"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"IDXID="w8074"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"ID="FM93890"Charting the Steps in Creating a MenuFILEREF="n41su73a.tif"RENDERAS="SECT4"ProcedureEach step in the flowchart is explained below.PERFORMANCE="REQUIRED"IDXID="w8075"BOOK="_idx" COLLECTION="nw41" TIDREF="i3318"
Plan and design your menu. Before starting, answer the following questions:MARK=BULLETWho is it for?What do the users need access to?Should they have access to a NetWare prompt?Should they be forced to log out when exiting?How complex is the menu? Will it need to be in multiple files?PERFORMANCE="REQUIRED"IDXID="w8076"BOOK="_idx" COLLECTION="nw41" TIDREF="i4247"
Use a text editor to create your menu with a .SRC extension.PERFORMANCE="REQUIRED"IDXID="w8077"BOOK="_idx" COLLECTION="nw41" TIDREF="i913"IDXID="w8078"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"IDXID="w8079"BOOK="_idx" COLLECTION="nw41" TIDREF="i716"
Compile the .SRC file with the MENUMAKE program. This will create a .DAT version of the file.
PAGENUM=259 ID="BP235"The results of any errors occurring during the compile process, including detailed error messages per line of script, are displayed on your screen. Fix the errors in the .SRC version of the file according to the error messages, and then recompile. When you have eliminated all of the errors, continue with Step 4.PERFORMANCE="REQUIRED"Run NMENU 
MOREINFO="NONE"filenameMOREINFO="NONE".dat to verify that it does what you expect.PERFORMANCE="REQUIRED"Change the program if needed, as described in Step 3
, and then repeat Step 4. When Step 4 is successful, go on to Step 6.PERFORMANCE="REQUIRED"Provide access to the intended users by placing the .DAT file in an appropriate directory and granting sufficient rights to the users.Information on placement of files and required rights is in IDREF="FM93412""Making Menus Work" on page 278.Following these six steps can help you learn how to use the scripting language and how to manage the menu files you create.Use of the NMENU program is almost unlimited. When considering the uses for menus, remember that they can be as simple as presenting available application programs (see IDREF="FM67334"Figure 4-5).LABEL="4-5" FLOAT="0"IDXID="w8080"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"IDXID="w8081"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"ID="FM67334"Example of a Simple MenuFILEREF="n41su82a.tif"They also can be more complex, such as guiding data entry for cataloging (see IDREF="FM55497"Figure 4-6).PAGENUM=260 ID="BP236"LABEL="4-6" FLOAT="0"IDXID="w8082"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"IDXID="w8083"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"ID="FM55497"Example of a More Complex MenuFILEREF="n41su80a.tif"The text used to create the four menus shown in this section (IDREF="FM73736"Figure 4-1, IDREF="FM90573"Figure 4-3, IDREF="FM67334"Figure 4-5, and IDREF="FM55497"Figure 4-6) is included in IDREF="FM76457""Example Menu Programs" on page 274.Before you look at how these menus were created, however, you should be familiar with the guidelines for planning menus and with the scripting language rules.PAGENUM=261 ID="BP237"RENDERAS="SECT1"IDXID="w8084"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"ID="FM71323"Planning Your MenusSeveral considerations are important when planning a menu. Details are presented throughout this chapter, but some general rules include the following:MARK=BULLETYou must include an EXIT or LOGOUT command in the menu to be able to leave the menu. For security reasons, the MOREINFO="NONE"EMOREINFO="NONE"sMOREINFO="NONE"c key doesn't work.The IDXID="w8085"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
maximum number of windows per menu is 11 (1 main window and 10 subwindows).The IDXID="w8086"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
maximum number of menus you can define in a single file is 255.The maximum "MENU" IDXID="w8087"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
name length (title bar) is 40 characters.The IDXID="w8088"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
maximum number of "ITEM" lines per window is 12.The maximum width of each window "ITEM" is 40 characters.The maximum text file width is 78 characters.The main menu must be at the beginning of the .SRC file.Submenus defined in the same file are called with the SHOW command by menu number.Menus in separate files are called as submenus, by menu name, with the LOAD command.IDXID="w8089"BOOK="_idx" COLLECTION="nw41" TIDREF="i2938"
If a command wraps to another line, type a plus sign (+) at the end of the line and continue the command on the next line.Menu colors are determined by the settings in the COLORPAL utility. See "BOOK="utlrfenu" COLLECTION="nw41"COLORPAL" in Utilities Reference.PAGENUM=262 ID="BP238"RENDERAS="SECT1"ID="FM54366"Using the NMENU CommandsIDXID="w8090"BOOK="_idx" COLLECTION="nw41" TIDREF="i2938"Menu programs use two types of commands: organizational and control. The following sections describe these commands and their options.RENDERAS="SECT2"IDXID="w8091"BOOK="_idx" COLLECTION="nw41" TIDREF="i2938"
NMENU Organizational Commands and OptionsOrganizational commands establish the content and organization of the menus the user sees on the screen. Use these commands to determine what the menus look like.Table 4-1 gives an overview of the organizational commands. Detailed information about each command follows the table.ID="FM88276"LABEL="4-1" PGWIDE=1 TOCENTRY="1"ID="FM61387" NMENU Organizational CommandsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="21*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"CommandCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"MENUCOLNAME=2 ROTATE="0" MOREROWS="0"Marks the beginning of a new menu or submenu screen in the text. COLNAME=1 ROTATE="0" MOREROWS="0"ITEMCOLNAME=2 ROTATE="0" MOREROWS="0"Identifies an item to be listed on the menu. Specifies execution parameters. PAGENUM=263 ID="BP239"RENDERAS="SECT3"ID="FM26044"MENUIndicates a new window definition within your menu file.RENDERAS="SECT4"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"MENU menu_number,menu_nameReplace menu_number with the number you want to assign to this menu. Menus are called and displayed by their number.A menu number can be any number from 1 through 255. Each menu within a source file must be assigned a unique number, but the number sequence doesn't matter.Replace menu_name with the title you want to appear at the top of the menu. Menu names can be a maximum of 40 characters long.RENDERAS="SECT4"IDXID="w8092"BOOK="_idx" COLLECTION="nw41" TIDREF="i4315"IDXID="w8093"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"IDXID="w8094"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
Using MENUThe first menu defined in the source file is always the first menu displayed, no matter what number is assigned to it. Subsequent menus are referenced by their numbers, no matter what order they appear in the .SRC file.For example, if you have defined three menus and assigned them numbers 1, 2, and 5, and menu 5 is the first menu in the source file, menu 5 is displayed first. Menus 1 and 2 are referenced in control commands and displayed depending upon user selection.RENDERAS="SECT4"ExampleTo define a main menu for a program to be used by accountants in your company, type a line similar to the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"MENU 1,Accounting Main MenuSince this is the first menu you want to appear, place it at the beginning of your menu program.PAGENUM=264 ID="BP240"RENDERAS="SECT3"ID="FM31184"ITEMIndicates an option in the menu.RENDERAS="SECT4"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"ITEM item_name {MOREINFO="NONE"[option...]}Replace item_name with the list item you want to appear in the menu. The maximum length for an item is 40 characters.Replace option with one or more of the options shown in the following table. Separate multiple options with a space. Enclose all options for a single ITEM in a single set of braces.These options provide you with better control of menu execution. You determine how memory is used, which directory the user remains in, and what information is presented to those users.
IDXID="w8095"BOOK="_idx" COLLECTION="nw41" TIDREF="i2938"IDXID="w8096"BOOK="_idx" COLLECTION="nw41" TIDREF="i1993"LABEL="4-2" PGWIDE=0 TOCENTRY="1" ITEM Command OptionsID="FM85439"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ITEM OptionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8097"BOOK="_idx" COLLECTION="nw41" TIDREF="i1993"IDXID="w8098"BOOK="_idx" COLLECTION="nw41" TIDREF="i419"
BATCHCOLNAME=2 ROTATE="0" MOREROWS="0"Removes the menu program from memory before executing the item.Without this option, a portion of the memory stays resident, requiring approximately 32 KB of available memory, even though an application may be running.For example, if you enterMOREINFO="NONE"ITEM Word 5.0 {BATCH}the menu program is removed from memory when Word 5.0 is executed.Setting this option automatically sets the CHDIR option. Don't use this command with the EXEC DOS command; use EXEC CALL.For more information, see IDREF="FM36562""EXEC" on page 268.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8099"BOOK="_idx" COLLECTION="nw41" TIDREF="i1993"IDXID="w8100"BOOK="_idx" COLLECTION="nw41" TIDREF="i622"
CHDIRCOLNAME=2 ROTATE="0" MOREROWS="0"Changes back to the drive and directory that were in effect before an ITEM was executed.For example, to change back to the drive and directory the user was in before executing a word processing application in another directory, type]ITEM WordPerfect 5.0 {CHDIR}.When the word processing application is closed, the directory is changed to the original directory for the menu.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8101"BOOK="_idx" COLLECTION="nw41" TIDREF="i1993"IDXID="w8102"BOOK="_idx" COLLECTION="nw41" TIDREF="i3259"
PAUSECOLNAME=2 ROTATE="0" MOREROWS="0"Allows users to read messages associated with a command being executed from the menu, by pausing the screen display.The message "Press any key to continue" is also displayed, and the screen does not change until a user presses a key.For example, to display a message when a user selects the item "DOS Copy" from the menu, include the line:ITEM DOS Copy {PAUSE}When the copy function is complete, the display waits at the "Press any key..." prompt for a key to be pressed before returning to the menu.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8103"BOOK="_idx" COLLECTION="nw41" TIDREF="i1993"IDXID="w8104"BOOK="_idx" COLLECTION="nw41" TIDREF="i4144"
SHOWCOLNAME=2 ROTATE="0" MOREROWS="0"Displays the command name, such as COPY or DIR, in the upper left corner of the screen.For example, if you enterITEM Copy Files {SHOW}the DOS command COPY is displayed when the item is executed.PAGENUM=266 ID="BP241"RENDERAS="SECT4"Using ITEMList items appear on the menu in the order in which they appear in the source file. They are not displayed in alphabetical order.Each item is automatically assigned an alphabetic selection character.If you want to assign a different character, place a carat (^) and the character you want in front of the item name (no spaces).Forcing the selection character shortens the maximum line length to 38 characters.If you assign selection letters, you should assign them to all menu list items. Otherwise another item may be automatically assigned a character you have previously assigned.RENDERAS="SECT3"ExampleFor example, if the first menu item is "Word Processing" and you want to assign it the letter "W" instead of the automatic letter designation of "A," typeMOREINFO="NONE"ITEM ^WWord ProcessingPAGENUM=267 ID="BP242"RENDERAS="SECT2"IDXID="w8105"BOOK="_idx" COLLECTION="nw41" TIDREF="i2938"
NMENU Control Commands and OptionsControl commands tell NMENU how to perform an action, such as displaying a submenu or user prompt, performing a DOS function, or starting an application. You also use these commands to tell the menu program how to process information and execute commands.Table 4-3 gives an overview of the control commands. Detailed information about each command follows the table.LABEL="4-3" PGWIDE=1 TOCENTRY="1"ID="FM21891"NMENU Control CommandsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="21*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"CommandCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"EXECCOLNAME=2 ROTATE="0" MOREROWS="0"Executes a DOS or NetWare command following an ITEM statement. COLNAME=1 ROTATE="0" MOREROWS="0"SHOWCOLNAME=2 ROTATE="0" MOREROWS="0"Displays a submenu from the same .DAT file. COLNAME=1 ROTATE="0" MOREROWS="0"LOADCOLNAME=2 ROTATE="0" MOREROWS="0"Calls and displays a menu as a submenu from a different .DAT file than the one you are running.COLNAME=1 ROTATE="0" MOREROWS="0"GETOCOLNAME=2 ROTATE="0" MOREROWS="0"Requests information from the user before a menu item is executed. User input is optional. (See IDREF="FM85911""GETx (GETO, GETP, GETR)" on page 271.)COLNAME=1 ROTATE="0" MOREROWS="0"GETPCOLNAME=2 ROTATE="0" MOREROWS="0"Requests information from the user before a menu item is executed. User input is required for the program to proceed. Assigns a variable (%n) to the information so it can be used again. (See IDREF="FM85911""GETx (GETO, GETP, GETR)" on page 271.)COLNAME=1 ROTATE="0" MOREROWS="0"GETRCOLNAME=2 ROTATE="0" MOREROWS="0"Requests information from the user before a menu item is executed. User input is required for the program to proceed. (See IDREF="FM85911""GETx (GETO, GETP, GETR)" on page 271.)PAGENUM=268 ID="BP243"RENDERAS="SECT3"ID="FM36562"IDXID="w8106"BOOK="_idx" COLLECTION="nw41" TIDREF="i1374"
EXECInstructs NMENU to perform the command that follows EXEC.RENDERAS="SECT4"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"EXEC commandReplace command with the command required to execute the ITEM. This could be the name of an executable file, a DOS or NetWare command, or one of the options associated with EXEC. The EXEC options are described in IDREF="FM29957"Table 4-4. LABEL="4-4" PGWIDE=0 TOCENTRY="1"IDXID="w8107"BOOK="_idx" COLLECTION="nw41" TIDREF="i1374"ID="FM29957" EXEC Command OptionsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"EXEC OptionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"EXEC CALLCOLNAME=2 ROTATE="0" MOREROWS="0"Runs a batch file, and returns to NMENU. If you want to return to NMENU after a batch file executes, use this command to call batch files.COLNAME=1 ROTATE="0" MOREROWS="0"EXEC DOSCOLNAME=2 ROTATE="0" MOREROWS="0"Runs the DOS command processor. If this command is used, the menu user must type "EXIT" when DOS processing is completed in order to return to NMENU.COLNAME=1 ROTATE="0" MOREROWS="0"EXEC EXITCOLNAME=2 ROTATE="0" MOREROWS="0"Exits the user from NMENU, but leaves the user logged in to NetWare. For security reasons, users cannot access the NetWare prompt unless this command is included in the menu.COLNAME=1 ROTATE="0" MOREROWS="0"EXEC LOGOUTCOLNAME=2 ROTATE="0" MOREROWS="0"Exits the user from NMENU and logs the user out of the network, leaving the user at the DOS prompt. (See IDREF="FM95514""Setting Up the User Environment" on page 278.)RENDERAS="SECT4"Using EXECEXEC must follow the ITEM it applies to. It must also follow other control commands needed by ITEM.RENDERAS="SECT4"ExampleTo load Word 5.0 from a menu, include the two following lines in the menu file:FORMAT="LINESPECIFIC"MOREINFO="NONE"ITEM Word 5.0
   EXEC word5
PAGENUM=269 ID="BP244"RENDERAS="SECT3"LOADIDXID="w8108"BOOK="_idx" COLLECTION="nw41" TIDREF="i2145"Instructs NMENU to execute a separate menu file.RENDERAS="SECT4"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD filenameReplace filename with the name of another NMENU program.If you have several menu programs created with the .DAT extension, use this command to call another menu program from the active menu program. LOAD always calls menus by their filename, not number.RENDERAS="SECT4"Using LOADUse this command when you have multiple menu programs defined. Although you can define up to 255 menus per source file, smaller, separate files are easier to manage and update.The NMENU file being loaded must be in the current directory, or you must have a search path to the file defined.RENDERAS="SECT4"ID="FM32328"ExampleIf you are writing a menu program for Sales and you want to call up the Accounting menu program, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"MENU 1,Sales Main Menu
   ITEM Accounting Menu
   LOAD ACCOUNTPAGENUM=270 ID="BP245"RENDERAS="SECT3"SHOWInstructs NMENU to execute a submenu defined within the same file.RENDERAS="SECT4"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"SHOW menu_numberReplace menu_number with the number of the submenu IDXID="w8109"BOOK="_idx" COLLECTION="nw41" TIDREF="i4143"
to be displayed.RENDERAS="SECT4"Using SHOWInclude SHOW commands to identify the submenu to be displayed when an item is selected from a menu.SHOW commands always use menu numbers, not titles.RENDERAS="SECT4"ExampleIf you have a menu with items listing categories of applications such as "Word Processing" and "Spreadsheets," each ITEM has the following SHOW commands to call up the appropriate submenus for those categories:FORMAT="LINESPECIFIC"MOREINFO="NONE"ITEM Word Processing
   SHOW 3FORMAT="LINESPECIFIC"MOREINFO="NONE"ITEM Spreadsheets
   SHOW 5To continue this example, if menu "3,Word Processing" is a list of available word processing programs needed by both Sales and Accounting, and each group has its own menus defined, the programs can "share" that screen and the screen's calls to execute the applications.PAGENUM=271 ID="BP246"RENDERAS="SECT3"ID="FM85911"GETx (GETO, GETP, GETR)The GETx commands provide access to user input. You can request or require user input. You can even store user input for future use. Each variation of the GETx command uses the same parameters to control what the users sees and does. Pay close attention to the use of spaces, commas, and braces { }.RENDERAS="SECT4"ID="FM10077"Command FormatFORMAT="LINESPECIFIC"MOREINFO="NONE"GETx prompt {prepend} length,[prefill], {append}Replace x with the letter "O," "R," or "P."MARK=BULLETIf you want the user to decide whether to enter information, use GETO.If you want to require the user to enter information (such as a password), use GETR.If you want user input to be used by more than one EXEC command after it is entered, use GETP. The information is assigned a variable (such as %1, %2, etc.).Replace prompt with the text (instructions) to be displayed to the user (40 characters maximum). For example: "Enter your Password."Prepend is a value added to the beginning of the user response. A space is usually required in the first GETx command, to separate it from the command issued in its associated EXEC command.Replace length with the maximum number of characters the user can enter. This parameter is required. For example, if you use GETR for a phone number, limit the length to 11 characters to match the field length for the phone number. Or, if you want a state or country abbreviation entered, limit the length to two characters.PAGENUM=272 ID="BP247"Replace prefill with a default response displayed with the prompt. The user can accept the default, change the response by typing over the default, or cancel selection of the item. Prefill cannot be longer than the specified length.The prefill parameter is optional. If you do not want to include a default response, enter the two commas together. (See the GETx examples on the following page.)Append is the value added to the end of the user response. If no value is needed, enter braces with a blank space between them.Append doesn't work with GETP. RENDERAS="SECT4"IDXID="w8110"BOOK="_idx" COLLECTION="nw41" TIDREF="i2938"IDXID="w8111"BOOK="_idx" COLLECTION="nw41" TIDREF="i1603"
Using GETx Interactive CommandsFollowing are some general guidelines on the use of the GETx commands.MARK=BULLETYou must define commands for each menu ITEM separately.Enter commands between the ITEM and the EXEC command(s) associated with the ITEM.Enter the commands in either uppercase or lowercase.Limit each prompt to one line.PAGENUM=273 ID="BP248"RENDERAS="SECT4"GETx Command ExamplesMARK=BULLETAssume that you want to require users to enter a project code to keep track of work performed for that project. Type the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"GETR Please enter the project code: { } 08,, { }
GETR Please enter your password: {} 08,, {}
GETO Load default macros? { } 01,, { }To get input for a program that calculates mortgages, using GETR, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"GETR Enter the loan amount: { } 7,,{ }
GETR Enter the interest rate: { } 5,8.5, { }
GETO Enter the period (/m=months or /y=years):+   { } 7,/y=30, { }
EXEC mortgageThe input values will be appended to the "EXEC mortgage" command before it is executed.To create the previous program using GETP in place of other GET commands, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8112"BOOK="_idx" COLLECTION="nw41" TIDREF="i4750"IDXID="w8113"BOOK="_idx" COLLECTION="nw41" TIDREF="i1602"
GETP Enter the loan amount: { } 7,,{ }
GETP Enter the interest rate: { } 5,8.5, { }
GETP Optional-Enter the period (/m=months or+   /y=years): { } 7,/y=30, { }
EXEC echo %1
EXEC echo %2
EXEC echo %3
EXEC mortgage %1 %2 %3
EXEC pause
PAGENUM=274 ID="BP249"RENDERAS="SECT1"ID="FM50463"Creating a Menu FileRENDERAS="SECT2"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterThe Read, File Scan, Write, Create, and Erase file system rights to the directory where you will create and edit the menuA DOS text editorRENDERAS="SECT2"IDXID="w8114"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"ID="FM76457"Example Menu ProgramsStudy the following examples by creating and trying them. By entering, executing, and debugging each example, you will gain the depth of understanding necessary to use the scripting language effectively.In the following examples, indents are used to help readability; they are not required.The examples include those script files used for the menus in IDREF="FM73736"Figure 4-1, IDREF="FM90573"Figure 4-3, IDREF="FM67334"Figure 4-5, and IDREF="FM55497"Figure 4-6. Subsequent examples show other ways of using the NMENU scripting language.PAGENUM=275 ID="BP250"RENDERAS="SECT3"Example 1: Single-Window MenuThis example in the following figure is the text used to create the menu in IDREF="FM73736"Figure 4-1 on page 255.LABEL="4-7" FLOAT="0"ID="FM25166"Single-Window Menu ScriptFILEREF="n41su74a.tif"RENDERAS="SECT3"Example 2: A Simple MenuText from the .SRC file used for the menu in IDREF="FM67334"Figure 4-5 on page 259 is shown in the following figure. This menu demonstrates how submenus can be used.LABEL="4-8" FLOAT="0"ID="FM12282"A Simple Menu ScriptFILEREF="n41su75a.tif"PAGENUM=276 ID="BP251"RENDERAS="SECT3"Example 3: A More Complex MenuThe menu in IDREF="FM55497"Figure 4-6 on page 260 was created from the text file in the following figure. This menu incorporates the GETR command with simple DOS functionality.LABEL="4-9" FLOAT="0"A More Complex Menu ScriptFILEREF="n41su76a.tif"As this menu script shows, by combining regular DOS commands with special NMENU conventions you have a simple means of organizing data. You don't need a database program just to catalog some information.PAGENUM=277 ID="BP252"RENDERAS="SECT3"Example 4: Combining DOS and NetWare CommandsUsers can accomplish more work when access to DOS and NetWare functionality is combined in the same menu.LABEL="4-10" FLOAT="0"Combining Commands in a ScriptFILEREF="n41su78a.tif"PAGENUM=278 ID="BP253"RENDERAS="SECT1"ID="FM93412"Making Menus WorkIDXID="w8115"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"Now that you have working menus, you must make them available to your users. Following is a list of rules for usage.MARK=BULLETYou must create a search drive to the directory where the menu files exist. Search mappings can be created in container, profile, or user login scripts.Users must have at least Read and File Scan rights to the directory where the menu files exist.NMENU uses temporary files. You must create a permanent drive mapping assignment to a directory where the temporary files will be used.Users must have at least Read, File Scan, Write, Create, and Erase rights to the directory where the temporary files will be stored.You can simplify management of the menu system by keeping all menu files in one place, such as SYS:MENUS. It becomes even easier to manage if the temporary files are kept in one place, such as SYS:MENUS\TEMP.RENDERAS="SECT2"IDXID="w8116"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"ID="FM95514"Setting Up the User EnvironmentIf you are storing users' temporary files in a network directory, place the following commands in the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET S_FILEDIR=
SET S_FILE=.For example, if you have created a subdirectory called TEMP under a MENUS directory, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"SET S_FILEDIR="Z:\\MENUS\\TEMP\\"
SET S_FILE="%STATION"These commands point to the directory where temporary files are stored and create unique files in the temporary directory for each workstation ID number. The trailing backslash on the S_FILEDIR path is required.If you choose not to use the %STATION identifier variable, you must manually create a file with a maximum length of seven characters. The NMENU program automatically prepends the # symbol to the beginning of the S_FILE filename.PAGENUM=279 ID="BP254"If the user will be using a menu with the logout option, set the S_FILEDIR environment variable to a path on the user's local drive. Set the S_FILE to "%STATION."A copy of the MENU-X.BAT file needs to be in the SYS:LOGIN directory if the NMENU LOGOUT option is going to be used.EXEC LOGOUT gives the message "Batch file not found" unless the temporary directory is on a local drive, and MENU_X.BAT is in the LOGIN directory.RENDERAS="SECT3"IDXID="w8117"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
Starting NMENU from a Login ScriptIDXID="w8118"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
If you want the menu to execute from within a login script, add the EXIT login script command. For example, to execute the ACCOUNT menu from a user's login script, add the following line to the login script:FORMAT="LINESPECIFIC"MOREINFO="NONE"EXIT "NMENU ACCOUNT"
PAGENUM=280 ID="BP255"RENDERAS="SECT1"ID="FM81162"IDXID="w8119"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
Converting Old Menu FilesUse this procedure to IDXID="w8120"BOOK="_idx" COLLECTION="nw41" TIDREF="i2398"
convert an existing MENU file (created with an earlier version of NetWare) to an IDXID="w8121"BOOK="_idx" COLLECTION="nw41" TIDREF="i2937"
NMENU file. These older menu programs usually have the extension 
.MNU.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Create a directory for the new menu files and temporary files.If you want to use the directories you already have set up for menu programs, you do not need to create new ones.PERFORMANCE="REQUIRED"Change the old .MNU file to the new .SRC source file format with the MENUCNVT command. Complete the following steps.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"IDXID="w8122"BOOK="_idx" COLLECTION="nw41" TIDREF="i2938"IDXID="w8123"BOOK="_idx" COLLECTION="nw41" TIDREF="i2399"
At the workstation command line, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"MENUCNVT menu_nameMOREINFO="NONE".mnuMOREINFO="NONE" <Enter>Replace menu_name with the name of the old menu you want to IDXID="w8124"BOOK="_idx" COLLECTION="nw41" TIDREF="i2400"
convert. If the menu is not in your current directory, enter the complete path to the menu name.The program creates a new .SRC file, leaving the original .MNU file unchanged.PERFORMANCE="REQUIRED"Edit the new menu source file.You will probably need to edit the new file to eliminate incorrect commands. For example, if your original MENU file used the SYSCON command, you must remove it from your new NMENU file and replace it with an appropriate NetWare 4 command (such as NETADMIN or NETUSER). NetWare 4 does not use SYSCON.There can be substantial differences between the original .MNU file and the converted .SRC file. MENUCNVT takes care of most differences, but not all of them. Some typical entries requiring changes by hand include the following:MARK=BULLETInvalid commands such as SYSCONPreceding letters or numbers from the old menuConversion of former @1, @2, etc., variables into the newer GETP variablesPAGENUM=281 ID="BP256"PERFORMANCE="REQUIRED"Follow the same six steps discussed in IDREF="FM27236""Menu Creation Steps" on page 257.RENDERAS="SECT3"ExampleTo help you see the differences between MENU and NMENU files, IDREF="FM72281"Figure 4-11 shows a part of the file for the menu in IDREF="FM90573"Figure 4-3 on page 257.The figure shows both the .MNU and the unedited .SRC file formats. They are shown side-by-side to help you make the comparison.The "After Conversion (.SRC)" side has not yet been edited. Try to find changes to make the file execute properly and efficiently. Look for commands that are no longer supported in NetWare 4 and replace them with appropriate commands. One example is SLIST, which must be replaced with NLIST SERVER.If you create your own file to test the .SRC file, remember to create some text file(s) to be displayed by the TYPE command.LABEL="4-11" FLOAT="0"ID="FM72281"Conversion ScriptsFILEREF="n41su79a.tif"PAGENUM=282 ID="BP257"LABEL="5"PAGENUM=283 ID="BP258"ID="FM57530"Managing the NetWare Directory TreeRENDERAS="SECT1"IDXID="w8125"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
About NetWare Directory ServicesNetWare® Directory ServicesTM (NDS) is a distributed name service that provides global access to all network resources regardless of where they are physically located. Users log into a multiserver network and view the entire network as a single information system.This single information system is the basis for increased productivity and reduced administrative costs. You can manage NDSTM by using the utilities and programs described in this chapter.The following utilities and programs help you maintain the NDS database.MARK=BULLETPartition Manager utilities allow you to distribute your NDS database by placing copies (replicas) of parts (partitions) of the database on different servers.A text utility (PARTMGR) and a graphical utility (NetWare Administrator) help you manage the database partitions and replicas. You can also remove NDS from a server using the INSTALL NetWare Loadable Module (NLM) program.UIMPORT allows you to import information from an existing database (any database capable of converting records to an ASCII file will work) to the NDS database. Use this utility and your database records to create, delete, and update User objects and their properties.DSREPAIR checks and repairs local portions of the database, similar to the way VREPAIR fixes volumes on a server.DSMERGE allows you to merge one Directory tree into another at the [Root], resulting in a single tree. This merging process would be used to create a single tree structure when previously separate organizations are joined together.PAGENUM=284 ID="BP259"DSTRACE allows you to determine whether NDS synchronization processes are complete and diagnose NDS errors.RENDERAS="SECT1"ID="FM34584"Creating and Managing Directory Services PartitionsRENDERAS="SECT2"About Partitions and ReplicasIDXID="w8126"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"IDXID="w8127"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"
A 
partition 
is a part of the total Directory and contains one or more containers and its associated leaf objects.When a partition is subordinate to another in the Directory tree, it is referred to as a child partition. The partition above it is referred to as the parent partition.IDXID="w8128"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
You can make copies of a partition, called replicas, and store them on different servers in your network. Distributing replicas reduces network traffic by making information accessible locally and enabling users to utilize the network services even when a particular server is down.IDXID="w8129"BOOK="_idx" COLLECTION="nw41" TIDREF="i3318"
Replicas also provide fault tolerance by ensuring that more than one copy of the partition information is available. For example, if a replica of the partition becomes unavailable, you can use a different replica to re-create it.Partitions contain only NDS database information, not file and directory information.RENDERAS="SECT2"ID="FM22788"Planning and Using Partitions and ReplicasIDXID="w8130"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"RENDERAS="SECT3"What Happens During Installation?IDXID="w8131"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"By default, the installation utility adds a replica of the partition that contains the server's context only if the total of existing replicas is less than three.However, if the server is not a NetWare 4 server and contains bindery files (SYS:SYSTEM\NET$*.SYS) a replica will be added, regardless of the number of replicas.These default settings ensure that bindery services will work correctly for networks running both NetWare 3TM and 4 software.PAGENUM=285 ID="BP260"For more information about bindery services, see Chapter 3, "BOOK="getstenu" COLLECTION="nw41"Understanding Bindery Services ," of Introduction to NetWare Directory Services and "BOOK="cncptenu" COLLECTION="nw41"Bindery services" in Concepts.You can create additional partitions and replicas using the NetWare Administrator graphical utility or the PARTMGR text utility. Instructions for using these utilities are included in this section.For more information on Directory partitions, see Chapter 2, "BOOK="getstenu" COLLECTION="nw41"Understanding Management Features" of Introduction to NetWare Directory Services and "BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition" in Concepts.RENDERAS="SECT3"IDXID="w8132"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"
Guidelines for Managing Partitions and ReplicasMARK=BULLETMake sure all the servers that contain partition replicas are up and running before you attempt any partition operation.If you attempt a partition operation while a server (that contains a replica) is down, NetWare Directory Services (NDS) won't be able to synchronize, since it won't be able to communicate with the replica on the downed server.You can create partitions only at the container level of the Directory tree.NDS does not require you to have a replica of the complete database in any location; the database is designed to be divided into usable pieces.Operations to manage partitions or replicas take place in the background and take time to complete, since the replicas need to be synchronized with new information.You cannot store more than one replica of the same partition on a server. It is not necessary for all servers in your tree to store replicas, unless you want to be able to log in to every server in your tree using bindery services.PAGENUM=286 ID="BP261"You can create as many replicas of a partition as you need; however, we recommend that you create between three and six replicas of each partition in your Directory tree.Having too many replicas may slow down your network because it will be busy synchronizing.You can have only one master replica. Replica typesIDXID="w8133"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"
 are explained in the following table.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ReplicaCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"MasterCOLNAME=2 ROTATE="0" MOREROWS="0"Partition information can be read from and written to this replica. The master replica can also be used to change the logical structure of the Directory (by creating a new partition, for example).When you create a new partition, a master replica is created and stored on the same server as the parent partition.COLNAME=1 ROTATE="0" MOREROWS="0"Read/writeCOLNAME=2 ROTATE="0" MOREROWS="0"Partition information can be read from and written to this replica. For example, it can be used to log in, add or delete objects, and view directory information.COLNAME=1 ROTATE="0" MOREROWS="0"Read-onlyCOLNAME=2 ROTATE="0" MOREROWS="0"Partition information can be read from this replica, but it cannot be written to by anything other than a read/write or master replica.Users cannot authenticate the network through a read- only replica because the login process changes the NDS database.You cannot set a bindery context when you log in to a read-only replica.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8134"BOOK="_idx" COLLECTION="nw41" TIDREF="i4323"
SubordinateCOLNAME=2 ROTATE="0" MOREROWS="0"This replica cannot be modified by any user. It is automatically placed on a server by NDS if the parent partition has either a master, read/write, or read-only replica on the server and the child partition does not.If you add a read/write or read-only replica of the child partition to the server, the subordinate replica is removed.PAGENUM=287 ID="BP262"Because partition and replica management is such a vital part of managing your network, read Chapter 7, "BOOK="getstenu" COLLECTION="nw41"Managing NetWare Directory Services," of Introduction to NetWare Directory Services before you use the Partition Manager utilities.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Bindery servicesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Bindery services" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Partition Manager utilitiesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Planning and using partitionsCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 5, "BOOK="getstenu" COLLECTION="nw41"Planning NetWare Directory Services Implementation," of Introduction to NetWare Directory ServicesRENDERAS="SECT2"Restricting Access to Partition ManagerIDXID="w8135"BOOK="_idx" COLLECTION="nw41" TIDREF="i3226"As administrator, you may want to limit which users in your network can access the Partition Manager that can be launched from NetWare Administrator.There are two ways you can limit access to Partition Manager:MARK=BULLETIDXID="w8136"BOOK="_idx" COLLECTION="nw41" TIDREF="i3033"
Restrict rights to NWPAR.DLL (found in SYS:PUBLIC) by giving Read and File Scan rights only to those who you want to have access to Partition Manager.Remove NWPAR.DLL from SYS:PUBLIC and place it in your path or in a directory to where you have a search drive mapped.This allows only you to see Partition Manager under the "Tools" menu in NetWare Administrator.You can also limit rights to PARTMGR (in DOS) by restricting rights to PARTMGR.EXE or by removing it from SYS:PUBLIC and placing it in your path or in a directory to where you have a search drive mapped.PAGENUM=288 ID="BP263"RENDERAS="SECT2"ID="FM54466"Creating a New PartitionA partition can consist of one or more container objects and their associated leaf objects. A partition cannot contain only leaf objects. The container that is the first object in the partition is called the "root" of the partition.When you create a new partition, you split the parent partition and end up with two partitions. The new partition becomes a child partition.For example, if you select an Organizational Unit and choose to create it as a new partition, you are choosing to split the Organizational Unit from its parent partition ([Root], for example, which is always a partition). The Organizational Unit you selected becomes the partition root of a new partition.The replicas of the parent partition will remain on the same servers, and information for the new partition will migrate from the parent partition's replicas to the new partition's replicas.The master replica of the new partition will be stored on the same server as the master replica of the parent partition.Creating a partition may take some time, since all of the replicas need to be synchronized with the new partition information.When you create a new partition, the utility you use will inform you that the partition is created successfully, but the actual creating is still completing on the servers. You will need to wait a while before being able to perform another partition operation.Partitions can be created using the PARTMGR text utility or the NetWare Administrator graphical utility. Both procedures are documented in this section.RENDERAS="SECT3"IDXID="w8137"BOOK="_idx" COLLECTION="nw41" TIDREF="i875"
Creating a Partition Using NetWare AdministratorRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationThe Supervisor object right to the container object you are partitioningPAGENUM=289 ID="BP264"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."Partition Manager will launch from the container you selected in NetWare Administrator.PERFORMANCE="REQUIRED"To locate the container object that you want to create as a partition, browse th
e "Partition Manager" 
scree
n.If the container object does not appear in the window, browse the tree b
y choosing an object to see its subordinate
s, or by choosing the arrow to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen
.For information about moving around in th
e "Partition Manager"
 screen and selecting objects
, choose th
e "Help"
 button.PERFORMANCE="REQUIRED"Selec
t a container object
.PERFORMANCE="REQUIRED"Choose "Create as New Partition."PERFORMANCE="REQUIRED"To confirm the creation of a new partition, choose "Yes."The new partition is create
d when the process is completed on the servers. To see the partition icon that signifies that a container is a partition, 
you need to refresh the screen by choosing the up arrow and then expanding the parent container again.A master replica is stored on the server where the parent partition'
s master replica resides. An icon appears next to the Organization (O) or Organizational Unit (OU) to show that the container i
s the root of a partition.To see where th
e master replica is stored, select the Organization (O) or Organizational Unit (OU) that you just partitioned, and the
n choose "Replicas.
" The server name appears in the "Servers
" column an
d "Master"
 appears next to it in the 
"Type
" column.
PAGENUM=290 ID="BP265"If you want to make additional replicas of this partition, se
e IDREF="FM94649""Creating a Replica" on page 302.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Creating a Partition Using PARTMGRIDXID="w8138"BOOK="_idx" COLLECTION="nw41" TIDREF="i875"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation logged in to the network, running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Supervisor object right to the container object you are partitioningRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"PARTMGR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Partition Administration"
 menu, choose "Manage Partitions
."Your current context appears in the upper-left corner of the screen.PERFORMANCE="REQUIRED"Select the container object to partitio
n.MARK=BULLETIf the container you want to partition appears on the list, select it and press MOREINFO="NONE"<F10>.If the container is not on the list, browse the directory by selecting containers and pressing MOREINFO="NONE"<Enter> until you see the container you want. Select it and press MOREINFO="NONE"<F10>.PAGENUM=291 ID="BP266"PERFORMANCE="REQUIRED"To create the new partition, choose "Yes."The new partition is created when the process is completed on the servers. To see the partition icon that signifies that a container is a partition, you need to refresh the screen by choosing the up arrow and then expanding the parent container again.A master replica is stored on the server where the parent partition's master replica resides. An icon appears next to the Organization (O) or Organizational Unit (OU) to show that the container is the root of a partition.To see where the master replica is stored, select the Organization (O) or Organizational Unit (OU) that you just partitioned, and then choose "View/Edit Replicas." The server name appears in the "Replicas Stored on Server" column, and "Master" appears next to it in the "Type" column.If you want to make additional replicas of this partition, see IDREF="FM94649""Creating a Replica" on page 302.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferenceRENDERAS="SECT2"ID="FM32409"Merging PartitionsIDXID="w8139"BOOK="_idx" COLLECTION="nw41" TIDREF="i2406"
You might want to 
merge two partitions if the Directory information in the two partitions is closely related.In other words, you would merge a partition with its parent partition when you want to delete the partition without deleting the objects in the partition.Consider keeping partitions separate if the partitions are large, because large partitions slow down response time.The partition is merged when the process is completed on the servers. To see that the icon of the partition you merged is gone (which signifies that the merge is complete), you need to refresh the screen by choosing the up arrow and then expanding the container again.PAGENUM=292 ID="BP267"Merging a partition with its parent partition might take some time, since the replicas need to be deleted and the parent replicas updated with the merging partition information.You can merge a subordinate partition with its parent partition using either the NetWare Administrator graphical utility or the PARTMGR text utility. Both procedures are documented in this section.RENDERAS="SECT3"Merging Partitions Using NetWare AdministratorIDXID="w8140"BOOK="_idx" COLLECTION="nw41" TIDREF="i2406"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationThe Supervisor object right to the object and its parent partitionRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."PERFORMANCE="REQUIRED"To locate the container object that you want to merge with the parent partition, browse th
e "Partition Manager"
 scree
n.If th
e partition does not appear in the window, browse the tree by selecting an object to see its subordinates, or by choosing the arrow to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen
.For information about moving around in th
e "Partition Manager"
 screen and selecting objects
, choose th
e "Help"
 button.PERFORMANCE="REQUIRED"Select th
e partition you want to merge.PERFORMANCE="REQUIRED"Choose "Merge Partition
."PAGENUM=293 ID="BP268"PERFORMANCE="REQUIRED"To merge the partition with its parent, choose "Yes."The partition is merged when the process is completed on the servers. To see the that the icon of the partition you merged is gone (which signifies that the merge is complete), you need to refresh the screen by choosing the up arrow and then expanding the container again.Merging a partition with its parent partition might take some ti
me, since the replicas need to be deleted and the parent replicas updated with the merging partition information.The replicas of the partitions are also merged.A partition with no parent 
partition will merge with th
e [Root] partition.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilitiesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"IDXID="w8141"BOOK="_idx" COLLECTION="nw41" TIDREF="i2406"
Merging Partitions Using PARTMGRRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Supervisor object right to the object at the root of the parent partitionRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"PARTMGR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Partition Administration
" menu, choose "Manage Partitions
."Your current context appears in the upper-left corner of the screen.
PAGENUM=294 ID="BP269"PERFORMANCE="REQUIRED"Select the partition to merg
e.MARK=BULLETIf the partition appears on the list, select it and press MOREINFO="NONE"<F10>.If the partition is not on the list, browse the directory by selecting objects and pressing MOREINFO="NONE"<Enter> until you see the partition you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "Merge with the Parent Partition
."PERFORMANCE="REQUIRED"To merge the selected partition with its parent partition, choose "Yes."The partition is merged when the process is completed on the servers. To see the that the icon of the partition you merged is gone (which signifies that the merge is complete), you need to refresh the screen by choosing the up arrow and then expanding the container again.Merging a partition with its parent partition might take some time, since the replicas need to be deleted and the parent replicas updated with the merging partition informatio
n.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferenceRENDERAS="SECT2"IDXID="w8142"BOOK="_idx" COLLECTION="nw41" TIDREF="i2528"
Moving a PartitionYou can move a container object only if it is the root of a Directory partition that has no subordinate partitions. So, moving a container is really moving a partition.When you move a container object, NetWare Directory Services (NDS) changes all references to the container. Although the object's common name remains unchanged, the context name of the container (and of all its subordinates) changes.When you move a partition, create an alias object that points to the partition you're moving. Doing so allows users to continue logging into the network and finding objects in their original Directory location.PAGENUM=295 ID="BP270"If 
you move a partition and do not create an alias, users who are unaware of the partition's new location will not easily find objects in the Directory tree, since they will look for them in their original Directory location.This might also cause client workstations to fail at login if the NAME CONTEXT parameter in the NET.CFG file is set to the original location in the Directory tree.Because the context of an object changes when you move it, users whose name context in their configuration file (NET.CFG file) references the moved object need to update their NET.CFG so that it references the object's new name.To automatically update users' NET.CFG file with a new name context after moving an object, use the NCUPDATE utility. For instructions, see "BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities Reference.You can use NetWare Administrator or NETADMIN to move partitions in the Directory tree. Both procedures are documented in this section.RENDERAS="SECT3"Moving a Partition Using NetWare AdministratorIDXID="w8143"BOOK="_idx" COLLECTION="nw41" TIDREF="i2527"RENDERAS="SECT4"IDXID="w8144"BOOK="_idx" COLLECTION="nw41" TIDREF="i2528"
PrerequisitesMARK=CHECKBOXA workstation running MS Windows 3.1 and NetWare AdministratorThe Supervisor right to the object you want to moveThe Create object right to the destination containerRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."PERFORMANCE="REQUIRED"From the "Partition Manager" browser, select the partition that you want to move.You can move a container object only if it is the root of a partition, and only if it contains no subordinate partitions.In Partition Manager, the partition icon appears to the left of the object icon. If the container you want to move is not a partition, select the container and choose "Create as New Partition." Then refresh the screen so that the partition icon appears and go to the next step.
PAGENUM=296 ID="BP271"If 
there are subordinate partitions in the container you want to move, you can merge those partitions with their parent partition.PERFORMANCE="REQUIRED"From the "Object" menu, choose "Move Partition."PERFORMANCE="REQUIRED"Select the browser button to the right of the "Destination" box.Use the browser in the "Directory Context" box to view the Directory tree's containers.The "Objects" box that appears in the lower-left corner shows the containers that you select in the "Directory Context" box.PERFORMANCE="REQUIRED"From the "Objects" box, select a container object (an Organization or Organizational Unit) as the place to move the listed objects to; then choose "OK."PERFORMANCE="REQUIRED"Choose "Create Alias in Place of Moved Container."The alias object will point to the partition's new location.If you move an object do not create an alias, users who are unaware of the object's new location will not easily find objects in the Directory tree, since they will look for them in their original Directory location.This might also cause client workstations to fail at login if the NAME CONTEXT parameter in the NET.CFG file is set to the original location in the Directory tree.Because the context of an object changes when you move it, users whose name context in their configuration file (NET.CFG file) references the moved object need to update their NET.CFG so that it references the object's new name.To automatically update users' NET.CFG file with a new name context after moving an object, use the NCUPDATE utility. For instructions, see "BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities Reference.PERFORMANCE="REQUIRED"In the "Move" dialog box, choose "OK."If you chose to create an alias in place of the moved container, NetWare Administrator polls for the creation of the alias object before it moves the selected partition.Unless you want the partition you just moved to remain a partition, you should merge it with its parent partition to avoid having an unnecessary partition in the Directory tree. See 
IDREF="FM32409""Merging Partitions" on page 291.
PAGENUM=297 ID="BP272"You will need to wait for processes throughout the Directory to be complete before you can perform a partition operation with this object again.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Merging partitionsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM32409""Merging Partitions" on page 291COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Alias objectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Alias object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory tree" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NCUPDATECOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceRENDERAS="SECT3"Moving a Partition Using NETADMINIDXID="w8145"BOOK="_idx" COLLECTION="nw41" TIDREF="i2527"IDXID="w8146"BOOK="_idx" COLLECTION="nw41" TIDREF="i2527"RENDERAS="SECT4"IDXID="w8147"BOOK="_idx" COLLECTION="nw41" TIDREF="i2528"
PrerequisitesMARK=CHECKBOXA DOS workstation running DOS 3.30 or later and the NETADMIN utilityThe Create object right to the destination containerRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>For information on moving around in NETADMIN and selecting objects, press 
MOREINFO="NONE"<F1> after starting the utility. To see which container objects in the Directory tree are partitions, exit NETADMIN and type "PARTMGR" at the command line. Then browse the tree.PERFORMANCE="REQUIRED"From the NETADMIN options menu, choose "Manage Objects."Your current context appears in the upper-left corner.
PAGENUM=298 ID="BP273"PERFORMANCE="REQUIRED"Select the object that you want to move.
MARK=BULLETIf the object you want to move appears on the list, select it and press MOREINFO="NONE"<F10>.If the object is not on the list, browse the directory by selecting container objects and pressing MOREINFO="NONE"<Enter> until you see the object you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"From the "Actions" menu, choose "Move."You can move a container object only if it is the root of a Directory partition, and only if it contains no subordinate partitions.In NETADMIN, when you select a container object that is a partition, the context-sensitive help at the bottom of the screen reads "This is a partition." Also, an asterisk (*) is displayed in front of the object name.If the container you want to move is not a partition, you must first use a partition management utility (PARTMGR or NetWare Administrator) and create the container as a new partition.PERFORMANCE="REQUIRED"Use the Down-arrow key and highlight the "New Context" field.PERFORMANCE="REQUIRED"Assign a new context to the object you want to move.
MARK=BULLETIf you know the new context that you want the object to be in, type the new context in the highlighted field.If you don't know the new context that you want the object to be in, press MOREINFO="NONE"<Insert> twice to browse the Directory for the destination container; then select the destination container and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"To accept the new context as the destination container, press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"To confirm that you want to move the object listed in the "Old Context" field to the container listed in the "New Context" field, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"To create an alias in place of the moved container, choose "Yes."The alias object will point to the partition's new location, and the selected object is moved to the destination container.
PAGENUM=299 ID="BP274"If you move an object do not create an alias, users who are unaware of the object's new location will not easily find objects in the Directory tree, since they will look for them in their original Directory location.This might also cause client workstations to fail at login if the NAME CONTEXT parameter in the NET.CFG file is set to the original location in the Directory tree.Because the context of an object changes when you move it, users whose name context in their configuration file (NET.CFG file) references the moved object need to update their NET.CFG so that it references the object's new name.To automatically update users' NET.CFG file with a new name context after moving an object, use the NCUPDATE utility. For instructions, see "BOOK="utlrfenu" COLLECTION="nw41"NCUPDATE" in Utilities Reference.You will need to wait for processes throughout the Directory to be complete before you can perform a partition operation with this object again.Unless you want the partition you just moved to remain a partition, you should merge it with its parent partition to avoid having an unnecessary partition in the Directory tree. See IDREF="FM32409""Merging Partitions" on page 291.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ObjectsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Object" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RightsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Rights" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory tree" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NETADMIN utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities ReferenceRENDERAS="SECT2"IDXID="w8148"BOOK="_idx" COLLECTION="nw41" TIDREF="i46"
Aborting a Partition OperationIf you have begun the process of creating, merging, or moving a partition, or changing a replica type, you can still abort the process since partition operations take time. You can abort a partition operation only before the operation is in its final stages.You would want to use this feature if you begin a partition operation and find that your database will not synchronize.If NetWare Directory Services (NDS) cannot synchronize replica information in your database because it is corrupted, or because a server in your Directory tree is down, you probably want to abort any partition operation in progress.PAGENUM=300 ID="BP275"If you choose to abort a partition operation when there is no operation in progress, no partitions will be affected.You can abort a partition operation using the NetWare Administrator graphical utility or the PARTMGR text utility. Both procedures are documented in this section.RENDERAS="SECT3"Aborting a Partition Operation Using NetWare AdministratorIDXID="w8149"BOOK="_idx" COLLECTION="nw41" TIDREF="i46"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationThe Supervisor object right to the object at the root of the partitionRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."PERFORMANCE="REQUIRED"To locate the partition that is executing a partition operation, browse th
e "Partition Manager" 
scree
n.If the container object does not appear in the window, browse the tree by selecting an object to see its subordinates, or by selecting the arrow key to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen.For information about moving around in th
e "Partition Manager"
 screen and selecting objects
, choose th
e "Help"
 button.PERFORMANCE="REQUIRED"Select the partition that i
s executing a partition operation and choose 
"Abort Partition Operation
."As long as at least one of the replica
s has not y
et completed the operation (as shown in the "State" box), you can stil
l abort the operation
.PAGENUM=301 ID="BP276"PERFORMANCE="REQUIRED"T
o abort the partition operation
, choose "Abort" and then choose "Yes."The partition operation i
s aborted, and any replicas that have been merge
d, created
, 
or moved (depending on the operation you had begun) are retu
rned to their original Directory location.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Aborting a Partition Operation Using PARTMGRIDXID="w8150"BOOK="_idx" COLLECTION="nw41" TIDREF="i46"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Supervisor object right to the object at the root of the partitionRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"PARTMGR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Partition Administration
" menu, choose "Manage Partitions
."Your current context appears in the upper-left corner.PERFORMANCE="REQUIRED"Select the parent partitio
n that is involved in a partition operation.MARK=BULLETIf the partition appears on the list, select it and press MOREINFO="NONE"<F10>.If the partition is not on the list, browse the directory by selecting objects and pressing MOREINFO="NONE"<Enter> until you see the partition you want. Select it and press MOREINFO="NONE"<F10>.PAGENUM=302 ID="BP277"PERFORMANCE="REQUIRED"Choose "Abort Partition Operation.
"A list of the replicas of the selected partition appears. Each replica's type and state are also displayed.As long as at least one of the replicas has not yet finished th
e operation you had begu
n, you can stil
l abort the operatio
n. If the state of the replica is "On," all operations are complete and cannot be aborted.PERFORMANCE="REQUIRED"T
o abort the partition operation, press 
MOREINFO="NONE"<F10> an
d choose "Yes."The partition operation i
s aborted, and any replicas tha
t began to be merge
d or created (depending on the operation you had begun) ar
e returned to their previous state.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferenceRENDERAS="SECT2"ID="FM94649"Creating a ReplicaIDXID="w8151"BOOK="_idx" COLLECTION="nw41" TIDREF="i883"IDXID="w8152"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"When you create a partition, a master replica is automatically created and stored on the server where the parent partition's master replica resides. You can create additional replicas of the partition, within these guidelines:MARK=BULLETYou can have only one master replica. Additional replicas must be read/write or read-only. For a description of replica types, see IDREF="FM22788""Planning and Using Partitions and Replicas" on page 284.You can store only one replica of a partition on a server.Replicas can be created using the NetWare Administrator graphical utility or the PARTMGR text utility. Both procedures are documented in this section.PAGENUM=303 ID="BP278"RENDERAS="SECT3"IDXID="w8153"BOOK="_idx" COLLECTION="nw41" TIDREF="i883"
Creating a Replica Using NetWare AdministratorRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationThe Supervisor object right to the object at the root of the partitionRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."PERFORMANCE="REQUIRED"Browse th
e "Partition Manager"
 screen to locate the partition that you want to create a replica for.If the container object does not appear in the window, browse the tree by selecting an object to see its subordinates, or by selecting the arrow key to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen
.For information about moving around in th
e "Partition Manager"
 screen and selecting objects, choose th
e "Help"
 button.PERFORMANCE="REQUIRED"Select the container object and choos
e "Replicas
."PERFORMANCE="REQUIRED"Choose "Add Replica.
"PERFORMANCE="REQUIRED"Browse the objects in th
e "Server
" box to locate the server you want to store the replica on
.The partition 
for which you are creating the replic
a appears at the top of the screen. The context and server information changes as you move through the Directory tree structure.PERFORMANCE="REQUIRED"Select the server you want the new replica to be stored on.PERFORMANCE="REQUIRED"Choose the replica type you want to create.
PAGENUM=304 ID="BP279"PERFORMANCE="REQUIRED"To create the replica, choose "OK.
"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Creating a Replica Using PARTMGRIDXID="w8154"BOOK="_idx" COLLECTION="nw41" TIDREF="i883"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Supervisor object right to the object at the root of the partitionRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"PARTMGR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Partition Administration
" menu, choose "Manage Partitions
."Your current context appears in the upper-left corner.PERFORMANCE="REQUIRED"Select the partition to replicat
e.MARK=BULLETIf the partition appears on the list, select it and press MOREINFO="NONE"<F10>.If the partition is not on the list, browse the tree by selecting objects and pressing MOREINFO="NONE"<Enter> until you see the partition you want. Select it and press MOREINFO="NONE"<F10>.PAGENUM=305 ID="BP280"PERFORMANCE="REQUIRED"Choose "View/Edit Replicas
."A list of the replicas of the selected partition appears. Each replica's type is also displayed
.PERFORMANCE="REQUIRED"To add a replica to the server, press 
MOREINFO="NONE"<Insert>.PERFORMANCE="REQUIRED"Enter the replica information.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"At the "Replica Type
" fiel
d, press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose the type of replica you want to create from the "Replica Type
" menu at the top of the screen.PERFORMANCE="REQUIRED"At the "Store on Server" fiel
d, press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Typ
e the name of the server you want to add the replica to, or press 
MOREINFO="NONE"<Insert> to select a server from the browser.PERFORMANCE="REQUIRED"To create the replica, press 
MOREINFO="NONE"<Esc> or 
MOREINFO="NONE"<F10> an
d choose "Yes."The new replica appears on the list of replicas for the server.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferenceRENDERAS="SECT2"ID="FM81755"IDXID="w8155"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"
Deleting a ReplicaReplicas can be deleted using the NetWare Administrator graphical utility or the PARTMGR text utility. Both procedures are documented in this section.When you delete replicas, keep the following guidelines in mind:MARK=BULLETIf a master replica becomes corrupted (for example, if the server will be down for a long time or the master replica becomes corrupted), change a read/write or read-only replica on another server to the master replica. This automatically changes the old master replica to a read/write replica.For fault tolerance, you should maintain at least one replica of the master partition on different servers.PAGENUM=306 ID="BP281"RENDERAS="SECT3"Deleting a Replica Using NetWare AdministratorRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationThe Supervisor object right to the object at the root of the partition whose replica you want to deleteRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."PERFORMANCE="REQUIRED"Browse th
e "Partition Manager"
 screen to locate the partition whose replica you want to delete.If the object where the container is stored does not appear in the window, browse the tree by selecting an object to see its subordinates, or by choosing the arrow to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen
.For information about moving around in th
e "Partition Manager"
 screen and selecting objects, choose th
e "Help"
 button.PERFORMANCE="REQUIRED"Select the partition and choose "Replicas
."PERFORMANCE="REQUIRED"Select the server you want to delete the replica from and choose "Delete Replica.
"You cannot delete 
a master replica. If the replica you want to delete is 
a master, go to a server with another replica of th
e master and make it the ne
w master replica. This automatically changes the ol
d master replica to 
a read/write replica, which you can then delete.For instructions, se
e IDREF="FM10660""Viewing a List of Partitions in a Directory Tree" on page 318.PAGENUM=307 ID="BP282"PERFORMANCE="REQUIRED"Choose "OK.
"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsRENDERAS="SECT3"Deleting a Replica Using PARTMGRRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Supervisor object right to the object at the root of the partition whose replica you want to deleteRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"PARTMGR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Partition Administration
" menu, choose "Manage Partitions
."Your current context appears in the upper-left corner.PERFORMANCE="REQUIRED"Select th
e partition that has a replica you want to delet
e.MARK=BULLETIf the partition appears on the list, select it and press MOREINFO="NONE"<F10>.If the partition is not on the list, browse the directory by selecting objects and pressing MOREINFO="NONE"<Enter> until you see the partition you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "View/Edit Replicas
."A list of the replicas of the selected partition appears. Each replica's type is also displayed.
PAGENUM=308 ID="BP283"PERFORMANCE="REQUIRED"Select the replica to delete and press 
MOREINFO="NONE"<Delete>.You cannot delete 
a master replica. If the replica you want to delete is 
a master, go to a server with another replica of th
e master and make it the ne
w master replica. This automatically changes the ol
d master replica to 
a read/write replica, which you can then delete.For instructions, se
e IDREF="FM10660""Viewing a List of Partitions in a Directory Tree" on page 318.PERFORMANCE="REQUIRED"To delete the replica, choose "Yes."COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferenceRENDERAS="SECT2"ID="FM90490"Sending Updates to Other ReplicasIDXID="w8156"BOOK="_idx" COLLECTION="nw41" TIDREF="i4678"
Although NetWare Directory Services automatically synchronizes the directory data of replicas (so that each replica contains the most recently updated data), you can manually start the process to synchronize (update) the directory data of replicas, if necessary.You should use the DSREPAIR utility to discover if the data in some replicas is out of sync with the master replica or not. If the data is out of sync, you would want to manually send updates to those replicas. The data in the other replicas would be updated and the directory data of each replica would be synchronized.You can send updates to other replicas using the NetWare Administrator graphical utility or the PARTMGR text utility. Both procedures are documented in this section.PAGENUM=309 ID="BP284"RENDERAS="SECT3"Sending Updates Using NetWare AdministratorIDXID="w8157"BOOK="_idx" COLLECTION="nw41" TIDREF="i3791"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationThe Supervisor object right to the object at the root of the partition whose replicas you want to send updates toRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."PERFORMANCE="REQUIRED"Browse th
e "Partition Manager"
 screen to locate the partition whose replicas you want to update.If the container object does not appear in the window, browse the tree by selecting an object to see its subordinates, or by selecting the arrow key to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen.For information about moving around in th
e "Partition Manager"
 screen and selecting objects, choose th
e "Help"
 button.PERFORMANCE="REQUIRED"Select the partition and choos
e "Replicas."PERFORMANCE="REQUIRED"From th
e "Replicas"
 screen, select which replica you want to send updates from (the on
e that contains updated dat
a) and choos
e "Send Updates to Other Replicas."The updated data is sent to all existing replicas of the same partition.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=310 ID="BP285"RENDERAS="SECT3"IDXID="w8158"BOOK="_idx" COLLECTION="nw41" TIDREF="i4678"
Sending Updates Using PARTMGRIDXID="w8159"BOOK="_idx" COLLECTION="nw41" TIDREF="i3791"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Supervisor object right to the object at the root of the partition whose replicas you want to send updates toRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE" PARTMGR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Partition Administration" menu, choose "Manage Partitions."Your current context appears in the upper-left corner.PERFORMANCE="REQUIRED"Select the partition whose replicas you want to updat
e.MARK=BULLETIf the partition appears on the list, select it and press MOREINFO="NONE"<F10>.If the partition is not on the list, browse the tree by selecting objects and pressing MOREINFO="NONE"<Enter> until you see the partition you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "View/Edit Replicas."A list of the replicas of the selected partition appears. Each replica's type is also displayed
.PERFORMANCE="REQUIRED"Select the replica you want to send updates from and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "Send Updates to Other Replicas
."PAGENUM=311 ID="BP286"PERFORMANCE="REQUIRED"To send updates to all the other replicas, choose "Yes."Th
e replica information is sent to all other replicas of the partition (including the master replica).COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferenceRENDERAS="SECT2"ID="FM49989"Receiving Updates from Other ReplicasIDXID="w8160"BOOK="_idx" COLLECTION="nw41" TIDREF="i3791"IDXID="w8161"BOOK="_idx" COLLECTION="nw41" TIDREF="i4678"
Although NetWare Directory Services (NDS) automatically synchronizes the directory data of replicas (so that each replica contains the most recently updated data) you can manually synchronize (update) the directory data of replicas if they ever get out of sync.You should use the DSREPAIR utility to discover if the data in some replicas is out of sync with the master replica or not. If the data is out of sync, you would want to manually receive updates from the Master replica.You cannot choose "Receive Updates From Other Replicas" from a master replica. The master is assumed to be the most current and accurate copy of the partition. If it's not, you should assign one of the other replicas to be the master using the PARTMGR utilityReplica.If you choose "Receive Updates From Other Replica" from any replica, that replica will receive NDS information from the master.You can receive updates from other replicas using the NetWare Administrator graphical utility or the PARTMGR text utility. Both procedures are documented in this section.PAGENUM=312 ID="BP287"RENDERAS="SECT3"IDXID="w8162"BOOK="_idx" COLLECTION="nw41" TIDREF="i4678"
Receiving Updates Using NetWare AdministratorIDXID="w8163"BOOK="_idx" COLLECTION="nw41" TIDREF="i3791"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationThe Supervisor object right to the object at the root of the partition whose replicas you want to send updates toRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."PERFORMANCE="REQUIRED"Browse th
e "Partition Manager"
 screen to locate the partition whose replicas you want to update.If the container object does not appear in the window, browse the tree by selecting an object to see its subordinates, or by choosing the arrow to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen
.For information about moving around in th
e "Partition Manager"
 screen and selecting objects, choose th
e "Help"
 button.PERFORMANCE="REQUIRED"Select the partition and choos
e "Replicas."PERFORMANCE="REQUIRED"From the "Partition Replicas
" screen, select which replica you want to update and choose 
"Receive Updates.
"The replica you have chosen receive
s NDS information fro
m the master replic
a.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferencePAGENUM=313 ID="BP288"RENDERAS="SECT3"Receiving Updates Using PARTMGRIDXID="w8164"BOOK="_idx" COLLECTION="nw41" TIDREF="i3791"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Supervisor object right to the object at the root of the partition whose replicas you want to updateRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"PARTMGR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Partition Administration" menu, choose "Manage Partitions."Your current context appears in the upper-left corner.PERFORMANCE="REQUIRED"Select the partition whose replicas you want to updat
e.MARK=BULLETIf the partition appears on the list, select it and press MOREINFO="NONE"<F10>.If the partition is not on the list, browse the tree by selecting objects and pressing MOREINFO="NONE"<Enter> until you see the partition you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "View/Edit Replicas."A list of the replicas of the selected partition appears. Each replica's type is also displayed
.PERFORMANCE="REQUIRED"Select the replica you want to update and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "Receive Updates from Other Replicas."
PAGENUM=314 ID="BP289"PERFORMANCE="REQUIRED"To receive updates from all the other replicas, choose "Yes."The selected replica receive
s NDS information fro
m the master replic
a.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferenceRENDERAS="SECT2"Viewing a List of Partitions Stored on a NetWare ServerWhen you view a list of partitions stored on a NetWare server, you are seeing all the partitions that have a replica stored on the selected server and the type of each replica.You can see a list of partitions stored on a NetWare Server object using the NetWare Administrator graphical utility or the PARTMGR text utility. Both procedures are documented in this section.RENDERAS="SECT3"Listing Partitions Using NetWare AdministratorRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationThe Write property right to the ACL property of the NetWare Server object whose partitions you want to viewRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."
PAGENUM=315 ID="BP290"PERFORMANCE="REQUIRED"Browse th
e "Partition Manager"
 to find the NetWare Server object whose partition list you want to view.If the NetWare Server object does not appear in the window, browse the tree by choosing an object to see its subordinates, or by choosing the arrow to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen
.For information about moving around in th
e "Partition Manager"
 screen and selecting objects, choose th
e "Help"
 button.PERFORMANCE="REQUIRED"Select the NetWare Server object and choose "Server Partitions.
"A list of the partitions 
that have a replica stored on the server is displayed.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Listing Partitions Using PARTMGRRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Write property right to the ACL property of the NetWare Server object whose partitions you want to viewRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"PARTMGR MOREINFO="NONE"<Enter>
PAGENUM=316 ID="BP291"PERFORMANCE="REQUIRED"From the "Partition Administration" menu, choose "Manage Partitions."Your current context appears in the upper-left corner.PERFORMANCE="REQUIRED"Select the server whose partitions you want to lis
t.MARK=BULLETIf the server appears on the list, select it and press MOREINFO="NONE"<F10>.If the server is not on the list, browse the tree by selecting containers and pressing MOREINFO="NONE"<Enter> until you see the server you want. Select it and press MOREINFO="NONE"<F10>.A list of partitions stored on the server appears.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferenceRENDERAS="SECT2"Viewing a List of Replicas of a PartitionYou can see a list of a partition's replicas, the servers where the replicas are stored, and whether a replica is a master, read/write, read-only, or subordinate replica type.You can view a replica list using the NetWare Administrator graphical utility or the PARTMGR text utility. Both procedures are documented in this section.RENDERAS="SECT3"Listing Replicas Using NetWare AdministratorIDXID="w8165"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationThe Write property right to the ACL property of the NetWare Server object whose replicas you want to viewPAGENUM=317 ID="BP292"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."PERFORMANCE="REQUIRED"Browse th
e "Partition Manager"
 screen to locate the partition whose replica list you want to view.If the partition does not appear in the window, browse the tree by choosing an object to see its subordinates, or by choosing the arrow to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen.For information about moving around in th
e "Partition Manager"
 screen and selecting objects, choose th
e "Help"
 button.PERFORMANCE="REQUIRED"Select the partition and choos
e "Replicas."A list of replicas appears, includin
g the server wher
e each replica is stored
, the replica type
, and the time and date of the last time the replica was synchronized with the other replicas.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Listing Replicas Using PARTMGRIDXID="w8166"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 512 KB of memory available on the workstationThe Write property right to the ACL property of the Server object whose replicas you want to viewPAGENUM=318 ID="BP293"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"PARTMGR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Partition Administration" menu, choose "Manage Partitions."Your current context appears in the upper-left corner.PERFORMANCE="REQUIRED"Select the partition whose replicas you want to lis
t.MARK=BULLETIf the partition appears on the list, select it and press MOREINFO="NONE"<F10>.If the partition is not on the list, browse the tree by selecting containers and pressing MOREINFO="NONE"<Enter> until you see the partition you want. Select it and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "View/Edit Replicas."The "Replicas Stored on Server
" screen appears, which lists the replica
s of the selected partition, the server they reside on, and the type of each replica.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferenceRENDERAS="SECT2"ID="FM10660"Viewing a List of Partitions in a Directory TreeYou can see a list of all partitions to which you have Browse rights in a NetWare Directory Services (NDS) tree using the NetWare Administrator graphical utility.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationPAGENUM=319 ID="BP294"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Object"
 menu, choose "Search
."PERFORMANCE="REQUIRED"Choose th
e drop-down arrow button at the right of the "Search For
" field.PERFORMANCE="REQUIRED"Scrol
l the drop-down list until you find "Partition.
"PERFORMANCE="REQUIRED"Select "Partition
" and choose "OK.
"A list of the partitions in the NDS tree appears. If you do not have th
e Browse
 right to the object at th
e root of the partition, the partition does not appear in the list.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT2"ID="FM89590"Changing a Replica's TypeYou can change replica types according to the following guidelines:MARK=BULLETYou can have only one master replica of a partition. Creating a new master replica automatically changes the old master replica to a read/write replica.You can change read/write replicas to read-only, and vice versa, without affecting other replicas of the same partition.You can change a replica's type using the NetWare Administrator graphical utility or the PARTMGR text utility. Both procedures are documented in this section.PAGENUM=320 ID="BP295"RENDERAS="SECT3"Changing a Replica's Type Using NetWare Administrator
IDXID="w8167"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running NetWare AdministratorA minimum of 6 MB of memory available on the workstationThe Supervisor object right to the object at the root of the partition whose replica you want to changeRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."PERFORMANCE="REQUIRED"Browse th
e "Partition Manager"
 screen to locate th
e partition tha
t has a replica whose type you want to change.If the NetWare Server object does not appear in the window, browse the tree by choosing an object to see its subordinates, or by choosing the arrow to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen
.For information about moving around in th
e "Partition Manager"
 screen and selecting objects, choos
e the "Help"
 button.PERFORMANCE="REQUIRED"Select the partition whose replica you want to change and choos
e "Replicas."PERFORMANCE="REQUIRED"From the list of replicas, select the replica you want to change.Be careful to select the correct replica by noting the serve
r's 
name as well as its type.PERFORMANCE="REQUIRED"Choose "Change Type.
"PERFORMANCE="REQUIRED"Choose the typ
e you want the replica to become.
PAGENUM=321 ID="BP296"PERFORMANCE="REQUIRED"Choose "OK.
"The new replica type appears on the 
"Partition Replicas
" screen
.If you 
changed a replica type to a master an
d a master replica already existed, the replica you jus
t changed to master is now th
e master replica
, and the ol
d master replica has been changed automatically to 
a read/write replica.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT3"Changing a Replica's Type Using PARTMGRIDXID="w8168"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS v3.30 or laterThe Supervisor object right to the object at the root of the partitionRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the DOS prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"PARTMGR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Partition Administration" menu, choose "Manage Partitions."Your current context appears in the upper-left corner.PERFORMANCE="REQUIRED"Select the partition whose replica you want to chang
e.MARK=BULLETIf the partition is on the list, select it and press MOREINFO="NONE"<F10>.If the partition is not on the list, browse the tree by selecting partitions and pressing MOREINFO="NONE"<Enter> until you see the partition you want. Select it and press MOREINFO="NONE"<F10>.PAGENUM=322 ID="BP297"PERFORMANCE="REQUIRED"Choose "View/Edit Replicas."A list of the replicas of the selected partition appears. Each replica's type is also displayed
.PERFORMANCE="REQUIRED"Select the replica you want to chang
e and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "Change Replica Type."PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> and choose t
he replica type you want the replica to become.PERFORMANCE="REQUIRED"To save the replica as the new type, press 
MOREINFO="NONE"<F10>.The new replica type appears on the list. The new replica type appears on the "Partition Replicas
" screen
.If you changed a replica type to a master and a master replica already existed, the replica you just changed to master is now the master replica and the old master replica has been changed automatically to a read/write replica.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PartitionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition," "BOOK="cncptenu" COLLECTION="nw41"Partition management," and "BOOK="cncptenu" COLLECTION="nw41"Replica" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferencePAGENUM=323 ID="BP298"RENDERAS="SECT1"Removing NetWare Directory Services from a ServerRENDERAS="SECT2"Considerations Before Removing NDSRemoving NetWare Directory Services (NDS) from a server may corrupt your NDS database. In most cases, this procedure is not necessary to correct a NetWare 4 problem. Before removing NDS, askMARK=BULLETDo other servers get Directory information (such as partition replicas) from this server?Could a bad LAN driver (one that doesn't communicate properly with NDS) be causing the problem?Could routers, network boards, or other hardware components be causing the problem?If you answered "yes" to any of these questions, only remove NDS as a last resort, after resolving all other problem areas.By removing NDS from a server, you remove the NetWare Server object from the Directory tree and downgrade the server's volumes to bindery volumes. Trustee assignments and all NDS information, such as links to subordinate partitions, are lost.If you installed this server into the wrong container, it isn't necessary to remove NDS. Use the Partition Manager tool in the NetWare Administrator utility to move the Server object to the correct container.Removing NDS may corrupt your Directory database. You must remove NDS if you are reformatting this server's hard drive. Do not remove NDS unless Novell Technical Support advises you to remove NDS from this server.PAGENUM=324 ID="BP299"RENDERAS="SECT2"ID="FM29387"Removing NDS from a ServerRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to the server console.The Supervisor object right to the NetWare Server object and its associated Volume objects.Make sure all of the server's volumes are mounted. Unmounted volumes won't get their Volume objects removed from the Directory database.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the 
"Installation Options
" menu, select "Directory Options (Install NetWare Directory Services
" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"From the "Directory Services Options
" menu, select "Remove Directory Services from this Server
" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"At the confirmation prompt
, choose "Yes."The "Directory Services Login/Authentication
" screen appears.PERFORMANCE="REQUIRED"Typ
e the password 
for User ADMIN in the "Password
" field and press 
MOREINFO="NONE"<Enter>.After you enter the password, the server's mounted volumes are downgraded and a messag
e displays the number of volumes affected. Then the system checks for Directory connections to other servers.
PAGENUM=325 ID="BP300"PERFORMANCE="REQUIRED"(Conditional) If this server contains 
a master replic
a, you must designate another server to hold it. Choose one of the following and press MOREINFO="NONE"<Enter>:
MARK=BULLETDo it automatically.INSTALL finds the first server with a replica of this partition and changes its type to "master."Designate the server yourself.Highlight the server where you want the master replica located.Press MOREINFO="NONE"<F10> to save and continue.A message notifies you that the master replica has moved.PERFORMANCE="REQUIRED"To continue, press MOREINFO="NONE"<Enter>.INSTALL removes NDS and deletes the Server object and Volume objects associated with it from the Directory database.If a Directory link is down (such as another server containing objects from this server), you must use Partition Manager to delete the Server and Volume objects from the Directory database.PERFORMANCE="REQUIRED"To exit INSTALL, press 
MOREINFO="NONE"<Esc>.RENDERAS="SECT2"Reinstalling NDS on a ServerThis procedure reinstalls Directory Services on a server. It doesn't preserve the trustee assignments from the first time NDS was installed on the server; you must make those assignments again.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to the server consoleThe Supervisor object right to the container you want to install the server inPAGENUM=326 ID="BP301"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the 
"Installation Options
" menu, select "Directory Options (Install NetWare Directory Services
" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"From the "Directory Services Options
" menu, select "Install Directory Services onto this Server
" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Install Directory Services on the server.To select a Directory tree and install Directory Services on the server, follow the instructions in Chapte
r 2, "BOOK="instlenu" COLLECTION="nw41"Simple Installation," or Chapter 3, "BOOK="instlenu" COLLECTION="nw41"Custom Installation," of Installation.PERFORMANCE="REQUIRED"To exit INSTALL, press 
MOREINFO="NONE"<Esc>.RENDERAS="SECT1"Deleting a NetWare Server Object from the NDS DatabaseRENDERAS="SECT2"Considerations Before Deleting NetWare Server ObjectsIDXID="w8169"BOOK="_idx" COLLECTION="nw41" TIDREF="i3790"Deleting a NetWare Server object permanently removes it from your network! It also permanently removes its data and resources from the network.Deleting a NetWare Server object may corrupt your NDS database, especially if the Server object provides NDS database services (such as storing partition replicas). Before deleting the Server object with the Partition Manager tool, consider these alternatives:MARK=BULLETChange the master replicas stored on this server to read/write replicas and then delete all replicas on the server. Once all the processes are complete, you can delete the server.Remove NDS from the server with the INSTALL NLM (described in IDREF="FM29387""Removing NDS from a Server" on page 324). This procedure protects your NDS database from lost services.PAGENUM=327 ID="BP302"To move the NetWare Server object to another context, use the "Move Server Object" option in the Partition Manager tool . (You do not need to delete the Server object and re-create it in another context.)If the Server object you are deleting doesn't contain any NDS database partitions or replicas, follow the procedures in IDREF="FM36317""Moving Container Objects Using NETADMIN" on page 94.RENDERAS="SECT2"Deleting a NetWare Server Object Using NetWare AdministratorIDXID="w8170"BOOK="_idx" COLLECTION="nw41" TIDREF="i2794"
IDXID="w8171"BOOK="_idx" COLLECTION="nw41" TIDREF="i2794"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running NetWare Administrator.A minimum of 6 MB of memory available on the workstation.The Supervisor object right to the container of the Server object you want to delete.Create a new master replica (if a master replica is stored on the NetWare Server object). See IDREF="FM10660""Viewing a List of Partitions in a Directory Tree" on page 318.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console, bring down the server by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>For more information, see IDREF="FM10818""Bringing Down a Server" on page 436.PERFORMANCE="REQUIRED"From the MS Windows Program Manager at your workstation, choose th
e "NetWare Administrator"
 ico
n.PERFORMANCE="REQUIRED"From the "Tools" menu, choose "Partition Manager."
PAGENUM=328 ID="BP303"PERFORMANCE="REQUIRED"Browse th
e "Partition Manager"
 screen to locate the NetWare Server object that you want to delete.If the NetWare Server object does not appear in the window, browse the tree by choosing an object to see its subordinates, or by choosing the arrow to move toward th
e [Root]. Your current context appears in the upper-left corner of the screen
.For information about moving around in th
e "Partition Manager"
 screen and selecting objects, choose th
e "Help"
 button.PERFORMANCE="REQUIRED"Select the NetWare Server object and choose "Delete Server.
"The NetWare Server object is deleted from the NDS database.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Deleting objects from the NDS databaseCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM36317""Moving Container Objects Using NETADMIN" on page 94COLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities ReferenceRENDERAS="SECT2"Deleting a NetWare Server Object Using PARTMGRIDXID="w8172"BOOK="_idx" COLLECTION="nw41" TIDREF="i2794"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS v3.30 or later.A minimum of 512 KB of memory available on the workstation.The Supervisor object right to the container of the Server object you want to delete.Create a new master replica (if a master replica is stored on the NetWare Server object). See IDREF="FM10660""Viewing a List of Partitions in a Directory Tree" on page 318.PAGENUM=329 ID="BP304"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console, bring down the server by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>For more information, see 
IDREF="FM10818""Bringing Down a Server" on page 436.PERFORMANCE="REQUIRED"At your workstation's DOS prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"PARTMGR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Partition Administration" menu, choose "Manage Partitions."Your current context appears in the upper-left corner.PERFORMANCE="REQUIRED"Select the NetWare Server object you want to delet
e.MARK=BULLETIf the NetWare Server object appears on the list, select it and press MOREINFO="NONE"<Delete>.If the NetWare Server object is not on the list, browse the tree by selecting objects and pressing MOREINFO="NONE"<Enter> until you see the NetWare Server object you want. Select it and press MOREINFO="NONE"<Delete>.The
 NetWare Server object is deleted from the NDS database.It may take a long time for all the other servers to know that a server is down. You should wait awhile after downing a server before deleting it.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Deleting objects from the NDS databaseCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM36317""Moving Container Objects Using NETADMIN" on page 94COLNAME=1 ROTATE="0" MOREROWS="0"Using the PARTMGR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PARTMGR" in Utilities ReferencePAGENUM=330 ID="BP305"RENDERAS="SECT1"Importing User Information into the Directory Services DatabaseIDXID="w8173"BOOK="_idx" COLLECTION="nw41" TIDREF="i2794"IDXID="w8174"BOOK="_idx" COLLECTION="nw41" TIDREF="i1770"IDXID="w8175"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"
The UIMPORT utility allows you to import data from an existing database into the NetWare Directory Services (NDS) database. This utility is particularly valuable if you have hundreds, or thousands, of user records that you want to record in NDS without having to manually re-create each user.Any application capable of converting records to a comma-separated ASCII file will work with UIMPORT.You can use IDXID="w8176"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"
UIMPORT to automate the maintenance of your NDS database when you want toMARK=BULLETCreate User IDXID="w8177"BOOK="_idx" COLLECTION="nw41" TIDREF="i4710"
objects in the NDS database using records from another database.Update User properties in the NDS database when records are changed in your original database program.Delete User objects when their accounts on the network are no longer needed.RENDERAS="SECT2"Understanding the Import ProcessIDXID="w8178"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"IDXID="w8179"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"The process for importing records from your database into the NDS database is as follows:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Generate a data file---a delimited ASCII text file---from your existing database records.Most applications let you save data as a comma-separated ASCII text file with quotation marks as delimiters.IDXID="w8180"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"Create an 
import control file to interpret the data file.You can create the import control file using any text editor under DOS or OS/2. This file defines how records in the data file are imported into NDS and which fields (properties) the data will be placed in.IDXID="w8181"BOOK="_idx" COLLECTION="nw41" TIDREF="i924"Create 
User objects using UIMPORT to transfer data from your database to the NDS database.PAGENUM=331 ID="BP306"The following figure provides a general overview of the import process.LABEL="5-1" FLOAT="0"IDXID="w8182"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"Import ProcessFILEREF="n41su10a.tif"RENDERAS="SECT2"Preparing to Import User Information into the Directory Services DatabaseRENDERAS="SECT3"ID="FM96458"IDXID="w8183"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"
Generating the Data FileIDXID="w8184"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"IDXID="w8185"BOOK="_idx" COLLECTION="nw41" TIDREF="i917"
IDXID="w8186"BOOK="_idx" COLLECTION="nw41" TIDREF="i4470"You generate a data file from within your database application, or any other application, by saving the data as a delimited ASCII text file. Most applications use commas as the default field separator and quotation marks as the default delimiter.The following figure shows a sample database table created using Borland's Paradox for Windows, and the data file generated from it.PAGENUM=332 ID="BP307"LABEL="5-2" FLOAT="0"Generate a Data FileFILEREF="n41su43a.tif"If you need instructions on how to save your data as a delimited ASCII file, see the documentation accompanying your application.Before you generate a data file from within your database application, look for embedded punctuation in the data fields.If the fields in your database have embedded punctuation (for example, quotation marks or commas), you should not use the same punctuation as field separators or delimiters when you export the data.IDXID="w8187"BOOK="_idx" COLLECTION="nw41" TIDREF="i917"If you do, UIMPORT won't be able to distinguish between new fields and embedded punctuation.Since embedded quotation marks and commas are the most commonly found punctuation in database fields, here are some guidelines to help you avoid problems in generating a data file.They are grouped according to four situations you might encounter:PAGENUM=333 ID="BP308"MARK=BULLETYou have both embedded quotation marks and embedded commas that you don't want to delete:We recommend that you export the data using an alternate character for the comma separator, and that you not use quotation marks as delimiters.For example, you could export data with carets (^) in place of comma separators. As a result, carets would separate each field in the data file you generate. You must specify in the import control file the replacement character you use. (See IDREF="FM76715"Table 5-1 on page 336.)You should also export data without using quotation marks to delimit the fields. If your application uses quotation marks as the default delimiter, you must change the delimiter to an alternate character or choose to use no delimiter.If you use an alternate character, you must specify in the import control file the replacement character you use. (See IDREF="FM76715"Table 5-1 on page 336.)You have neither embedded quotation marks nor embedded commas:We recommend that you export the data using commas to separate the fields.If your application inserts quotation marks as delimiters around each field, you can accept this default, or you can choose to use no delimiter.You have embedded commas, but no embedded quotation marks:We recommend that you export the data using an alternate character for the comma separator.For example, you could export data with carets (^) in place of comma separators. As a result, carets would separate each field in the data file you generate. You must specify in the import control file the replacement character you use. (See IDREF="FM76715"Table 5-1 on page 336.)If your application inserts quotation marks as delimiters around each field, you can accept this default, or you can choose to use no delimiter.You have embedded quotation marks, but no embedded commas:We recommend that you export data using commas to separate the fields and without using quotation marks to delimit the fields.PAGENUM=334 ID="BP309"However, if your application uses quotation marks as the default delimiter, you must change the delimiter to an alternate character or tell your application to use no delimiter.If you use an alternate character, you must specify in the import control file the replacement character you use. (See IDREF="FM76715"Table 5-1 on page 336.)One of the fields required to create new user objects in the NDS database is name. If you don't have a field in your database that records each individual's login name, you have a few options:MARK=BULLETYou can create a login name field within your application (and assign each individual a unique eight-character login name) before generating the data file. This option is recommended.You can generate the data file and then add a unique login name field to each string of user information in the data file.You can use an existing field in your application to represent the login name field. For example, you may have a field of employee or ID numbers. You can generate the data file and import the unique numbers into NDS as user login names. (Keep in mind that numbers are not as easy to recognize or manage as names.)RENDERAS="SECT3"Creating the Import Control FileIDXID="w8188"BOOK="_idx" COLLECTION="nw41" TIDREF="i4628"IDXID="w8189"BOOK="_idx" COLLECTION="nw41" TIDREF="i1768"
IDXID="w8190"BOOK="_idx" COLLECTION="nw41" TIDREF="i1768"IDXID="w8191"BOOK="_idx" COLLECTION="nw41" TIDREF="i821"
IDXID="w8192"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"You can create the import control file using any text editor under DOS or OS/2.This file controls how the information in the data file will be imported into the Directory Services database, and determines which fields (called properties in NDS) the data will be placed in. The import control file contains two types of information:MARK=BULLETIDXID="w8193"BOOK="_idx" COLLECTION="nw41" TIDREF="i1768"IDXID="w8194"BOOK="_idx" COLLECTION="nw41" TIDREF="i4628"Control parameters define characters used in the data file and specify how data is updated.IDXID="w8195"BOOK="_idx" COLLECTION="nw41" TIDREF="i1768"IDXID="w8196"BOOK="_idx" COLLECTION="nw41" TIDREF="i4628"Field definitions determine where data is put in the NDS database (which properties the fields are imported into).PAGENUM=335 ID="BP310"Enter control parameters first, followed by field definitions. (Control parameters are explained in IDREF="FM76715"Table 5-1 on page 336. Field definitions are explained in IDREF="FM45494"Table 5-2 on page 341.) For example:TYPE="VERT"Import control   Separator=^   User template=yFields   Last name   Name   Telephone   TitleControl and field parameters are not case-sensitive, though the headings "Import Control" and "Fields" must be left aligned (you don't have to specify import control parameters if you use the defaults). Entries under the headings must be preceded by at least one space or a tab.To create a new user, two field definitions are required: "Name" (the user's login name) and "Last name." To update records for users who have already been created, only the "name" field is required. These fields are explained in IDREF="FM45494"Table 5-2 on page 341.All fields in the data file must have a corresponding field definition in the import control file. To see a sample data file and its corresponding import control file, see IDREF="FM32317""Data File Created from Exported Database Fields" on page 351.Although you don't have to save the import control file in the same directory in which you saved the data file, doing so makes locating the files and running UIMPORT easier. If you don't, you will have to specify the path to each of the files when you run UIMPORT.After generating the data file and creating the import control file, see IDREF="FM51525""Creating User Objects with the UIMPORT Utility" on page 354 to start the import process.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating a comma-separated ASCII fileCOLNAME=2 ROTATE="0" MOREROWS="0"Your database application documentationCOLNAME=1 ROTATE="0" MOREROWS="0"Creating and managing User objectsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM93061"Chapter 1, "Managing NetWare Directory Services Objects"Chapter 1, "Managing NetWare Directory Services Objects"COLNAME=1 ROTATE="0" MOREROWS="0"Starting the import processCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM51525""Creating User Objects with the UIMPORT Utility" on page 354"Creating User Objects with the UIMPORT Utility" on page 354COLNAME=1 ROTATE="0" MOREROWS="0"NetWare Directory ServicesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory Services" in Concepts, and Chapter 1, "BOOK="getstenu" COLLECTION="nw41"Understanding NetWare Directory Services," of Introduction to NetWare Directory ServicesPAGENUM=336 ID="BP311"RENDERAS="SECT4"Control ParametersIDXID="w8197"BOOK="_idx" COLLECTION="nw41" TIDREF="i821"
Use the IDXID="w8198"BOOK="_idx" COLLECTION="nw41" TIDREF="i824"
applicable control IDXID="w8199"BOOK="_idx" COLLECTION="nw41" TIDREF="i1768"
parameters in IDXID="w8200"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"
the following table to create the "Import control" section of the import control file. These can be changed by adding the control parameter in the data file. When doing so, add an exclamation point (!) before the control parameter in the data file. (See IDREF="FM13792""Data File Edited to Update User Objects" on page 352.)LABEL="5-1" PGWIDE=1 TOCENTRY="1"IDXID="w8201"BOOK="_idx" COLLECTION="nw41" TIDREF="i4628"ID="FM76715" UIMPORT Control ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="28*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Control ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8202"BOOK="_idx" COLLECTION="nw41" TIDREF="i868"
Create IDXID="w8203"BOOK="_idx" COLLECTION="nw41" TIDREF="i1682"
home directoryCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8204"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
Allows you to create a home directory for User objects.If you create a home directory, users are automatically given file system rights to work in that directory. This option will not work unless you set the "Home directory path" and "Home directory volume" control parameters.(Also, this option will not work if you define a data field for "Home Directory," because that field will override Create home directory.)For example, if you want the users you are importing to have a home directory, type CREATE HOME DIRECTORY=Y.The default setting is "N", so if you don't want to create home directories, no parameter is needed.Note: If you don't set this parameter to Y, you can still import Home Directory values through the control section of the import control file or through the data file. These values will be put into the object's Home Directory property, but the directory on the file system will not be created.COLNAME=1 ROTATE="0" MOREROWS="0"Delete Mailbox DirsCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to delete the mailbox directories when moving a user's mailbox from one messaging server to another or changing the mailbox ID of a user.To delete the mailbox directories, type DELETE MAILBOX DIRS=Y.The default is "N"; so if you don't want to delete the mailbox directories, no parameter is needed.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8205"BOOK="_idx" COLLECTION="nw41" TIDREF="i979"
Delete propertyCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to delete values for a property of a User object.For example, to delete all titles from a User object's Title property, type DELETE PROPERTY=#DEL, and then edit the data file by putting "#DEL" in the Title field.If you delete a group membership, you will also delete the security equals for the group.You cannot delete the following properties with the Delete property parameter:Volume restrictions. To delete volume restrictions, enter the volume name and a negative integer such as -1 for the restrictions. For example: VOL1:-1Password. To delete the password, enter "" (a null field) for the password field.Home directory. You can delete the Home directory property, but the home directory path will not be deleted by UIMPORT. You will need to manually go to this directory and delete it, if desired.There is no default for this property, so if you don't want to delete properties, no parameter is needed.For more information, see IDREF="FM51525""Creating User Objects with the UIMPORT Utility" on page 354COLNAME=1 ROTATE="0" MOREROWS="0"Home IDXID="w8206"BOOK="_idx" COLLECTION="nw41" TIDREF="i3256"
directory pathCOLNAME=2 ROTATE="0" MOREROWS="0"If you create a home directory for User objects, you must specify a path in the file system where you want the directories to be created. This and the Home directory volume must be entered as a pair. If you specify a Home directory volume, the path will be assumed to be null unless this field is also specified.If you want home directories created in the Users directory, type HOME DIRECTORY PATH="USERS". Do not include the volume name in the path.COLNAME=1 ROTATE="0" MOREROWS="0"Home directory volumeCOLNAME=2 ROTATE="0" MOREROWS="0"If you create a home directory for User objects, you must specify the name and context of the Volume object associated with the file system where the home directories are created.For example, if the file specified in "Home directory path" is on volume SYS:, enter the Volume object's complete DS name. For example: HOME DIRECTORY VOLUME="SYS.STUDENT RECORDS.UNIVERSITY".When creating users, the Home directory volume is set in the following order:1. Information in the data file. If the data file has a home directory specified, its value will be used.2. If there is no home directory specified in the data file, the home directory from the User Template object will be used. This happens regardless of whether or not you select to copy the User Template properties when creating users.3. If the home directory is not found in the data file or the User Template, this control parameter (Home directory volume) will be used.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8207"BOOK="_idx" COLLECTION="nw41" TIDREF="i1769"
Import modeCOLNAME=2 ROTATE="0" MOREROWS="0"Controls how the User objects will be created or updated. Options are C (create new objects only), U (update data for existing objects only), B (both create and update), and R (remove objects).The default is "B", so if you want new objects to be created and existing users updated, no parameter is needed.Note: You can use the same import control file for adding and deleting users by just changing the Import Mode to R (Remove objects). This can be especially useful if you have just created some users with incorrect information and need to restart the entire process. Just change the Import mode to R, run UIMPORT to delete the users, then change the Import Mode back to C or B and rerun UIMPORT.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8208"BOOK="_idx" COLLECTION="nw41" TIDREF="i2353"
Maximum directory retriesCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to specify how many times UIMPORT should attempt to get the object ID of the user you have just added in order to create home directories and mailbox directories.For example, type Maximum directory retries=5.If Directory Services creates your user on one server's replica and you create the home or mailbox directory on another server, the second server may not know about the user immediately. This option allows time for the network to catch up with the request to add the user on the other server.Initially this option is set to 5; but if you get the message "991: An error occurred in NWDSMapNameToID...," you should increase this number.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8209"BOOK="_idx" COLLECTION="nw41" TIDREF="i817"
Name IDXID="w8210"BOOK="_idx" COLLECTION="nw41" TIDREF="i2575"
contextCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the Directory Services context where user objects will be created. You should always use this parameter.For example, if you are in the Organization Development.ACME and you want to create user objects in a different Organizational Unit (Engineering), type NAME CONTEXT=.Engineering.ACMEThe default is your current context (the context displayed when you type CX from the command line).COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8211"BOOK="_idx" COLLECTION="nw41" TIDREF="i3663"
QuoteCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the character used to delimit fields when exporting data to the data file. You might want to change the delimiter from quotes to different characters if your data has embedded quotation marks and you don't want to delete them.For example, if you have any embedded quotation marks in fields in your database, you could export data using carets (^) as the delimiter. You would enter QUOTE=^ as the quote parameter.The default character for delimiters are quotes (""). If you don't have embedded quotation marks in fields in your database, and you generate the data file with quote delimiters, no parameter is needed.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8212"BOOK="_idx" COLLECTION="nw41" TIDREF="i3788"
Replace valueCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to overwrite or add data to multivalue properties.For example, to import new telephone numbers to User properties without saving the existing numbers, type REPLACE VALUE=Y.The default is "N," so if you don't want data to be added to multivalued properties, no parameter is needed. You do not need to set this parameter for single-value fields, because the new value automatically overwrites the existing value.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8213"BOOK="_idx" COLLECTION="nw41" TIDREF="i4028"
SeparatorCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the character used to separate fields when exporting data to the data file.If the fields in your database have embedded punctuation, (such as commas), you should not use the same punctuation as field separators when you export the data to the data file. If you do, UIMPORT won't be able to distinguish between new fields and embedded punctuation. Instead, use a different character as the separator.For example, if you have any embedded commas in fields in your database, you could export the data using a semicolon (;) as the field separator. You would enter SEPARATOR=; as a control parameter.The default separator is a comma. If you have no embedded commas in fields in your database, and you generate the data file with comma separators, no parameter is needed.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8214"BOOK="_idx" COLLECTION="nw41" TIDREF="i4720"
User templateCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies whether you want user template defaults to be applied to the User objects being created. (User template defaults are explained in IDREF="FM88652""Managing User Templates" on page 78To apply template properties to User objects, type USER TEMPLATE=Y. Template properties are applied first, and then properties from the data file are imported.The default is "N", so if you do not want the user template defaults applied to the new User objects, no parameter is needed.The following fields are copied from the user Template:Account balance, Account has expiration date, Allow unlimited credit, Allow user to change password, City, Days between forced changes, Default server, Department, Description, Fax number, Foreign Email address, Foreign Email alias, Full name, Generational qualifier, Given name, Grace logins allowed, Group membership, Home directory, Language, Location, Login allowed time, Login script, Low balance limit, Mailbox location, Mailing label information, Maximum connections, Minimum password length, Network address restriction, Postal (ZIP) code, Postal office box, Profile, Remaining grace logins, Require a password, Require unique passwords, Security equal to, See also, State or province, Street address, Telephone, TitlePAGENUM=341 ID="BP312"RENDERAS="SECT4"Field DefinitionsIDXID="w8215"BOOK="_idx" COLLECTION="nw41" TIDREF="i972"
Use the applicable IDXID="w8216"BOOK="_idx" COLLECTION="nw41" TIDREF="i1444"
definitions in the following table to create the IDXID="w8217"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"
import control file.A single-value property can contain only one entry (property). If you put more than one entry for a single-value property in the control file, only the last one will be saved.A multivalue property can contain more than one entry. If you want to replace existing values in existing users, make sure to set the Replace Value control parameter to Y. By default, all values will be added to those already in the user object.LABEL="5-2" PGWIDE=1 TOCENTRY="1"ID="FM45494"ID="FMUIMPO"UIMPORTID="FMFIELD"Field DefinitionsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="22*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PropertyCOLNAME=2 ROTATE="0" MOREROWS="0"Property descriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Account balanceCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the beginning account balance for the user. If accounting is not turned on, this field will have no use.COLNAME=1 ROTATE="0" MOREROWS="0"Account disabledCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter Y if you want to disable this account.If you enter Y, you can't modify Password or Login script.The default is N; so if you don't want the account disabled, no field is required.COLNAME=1 ROTATE="0" MOREROWS="0"Account has expiration dateCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the date in the form MM/DD/YY. It will expire at 12:01 am on that date.COLNAME=1 ROTATE="0" MOREROWS="0"Allow unlimited creditCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter Y to allow unlimited credit. Enter N to not allow unlimited credit. If accounting is not turned on, this field will have no use.The default value for this property is N.COLNAME=1 ROTATE="0" MOREROWS="0"Allow user to change passwordCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. If you don't want the user to be able to change his/her password, enter N in the data file. The default is "Y"; so if you want to allow the user to change his/her password, no parameter is needed.COLNAME=1 ROTATE="0" MOREROWS="0"CityCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the name of the city.COLNAME=1 ROTATE="0" MOREROWS="0"Date password expiresCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the date the password expires in the form MM/DD/YY. It will expire at 12:01 am on that date.COLNAME=1 ROTATE="0" MOREROWS="0"Days between forced changesCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the number of days before requiring the user to change his/her password.The default for this value is 40.The possible values for this field are numbers 1-365. Do not set this value to 0.COLNAME=1 ROTATE="0" MOREROWS="0"Default serverCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the name of the server from which the user gets his/her messages when they are sent with the SEND utility.In the data file, enter the Directory Services name of the server, including the context if the server is not in the same context as the user.COLNAME=1 ROTATE="0" MOREROWS="0"DepartmentCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. In the data file, enter the department name, code, number, or other type of information.COLNAME=1 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter any type of information about the user that you want to import. The field must be enclosed in quotes (or the delimiter defined in the control file) if it contains commas or new-line characters.This field is a string; all data from the opening quote to the closing quote is considered part of the field.COLNAME=1 ROTATE="0" MOREROWS="0"Fax numberCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. In the data file, enter the fax number for each user you want to import.COLNAME=1 ROTATE="0" MOREROWS="0"Foreign Email addressCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the foreign Email address of the user, which specifies a mailbox that resides in a foreign Email system. This information is used by NetWare MHS Services.The format for this value is Type:Value, where Type is the type of messaging protocol and Value is the the user's address (in the format required by the foreign Email system).For example, in your data file you could enter a field such as SMTP:Jjones@Acme.comCOLNAME=1 ROTATE="0" MOREROWS="0"Foreign Email aliasCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. In the data file, enter the Foreign Email aliases of the user, which specify an object's aliases as known in a foreign messaging system. This information is used by NetWare MHS Services.For example, an 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.The format for this value is Type:Value, where Type is the type of messaging protocol and Value is the user's name (in the format required by the foreign Email system).For example, in your data file you could enter a field such as X400:g=joe;s=jones;ou=sales;o=acme;p=acmemd;a=att;c=usCOLNAME=1 ROTATE="0" MOREROWS="0"Full nameCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the user's full name.For example: Roland D BrunsCOLNAME=1 ROTATE="0" MOREROWS="0"Generational qualifierCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the generational qualifier for the user's name. Usually this is a Jr., Sr., II or III.If the user's name is Bob Wilson III, enter III in the data file.COLNAME=1 ROTATE="0" MOREROWS="0"Given nameCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the given name of the user. For example, for John Doe, enter John.COLNAME=1 ROTATE="0" MOREROWS="0"Grace logins allowedCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the number of grace logins allowed before the account is locked. 0 implies no limit.COLNAME=1 ROTATE="0" MOREROWS="0"Group membershipCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. This field allows you to organize groups of users who need similar rights and access to network resources. In the data file, enter the names of the groups to which this user belongs. If the group object is in a different context than the user, enter the complete Directory Services name of the group, including its context.COLNAME=1 ROTATE="0" MOREROWS="0"Home directoryCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the volume and path of the home directory in the following format:Volume Name:pathIf the volume is in a different context than the user, enter the complete Directory Services name. Separate the volume name and the path by a colon (:). Include the full path, including the final directory.For example, for user ABC1, create the home directory on volume object VOL1. VOL1 is in the same context as the user.VOL1:USERS\ABC1This field in the data file will override the Home Directory field in the control section.COLNAME=1 ROTATE="0" MOREROWS="0"InitialsCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the middle initial of the user. For John I. Doe, enter I here.COLNAME=1 ROTATE="0" MOREROWS="0"LanguageCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. In the data file, enter the language directories to be searched to find the message files for NetWare utilities for this user.If more than one language directory should be searched, enter multiple language fields. The order is important. The first entry will be the first language directory to be searched, the second is the second language directory to be searched, etc.COLNAME=1 ROTATE="0" MOREROWS="0"Last nameCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the user's last name. A value is required for this field when you are creating new User objects.COLNAME=1 ROTATE="0" MOREROWS="0"LocationCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. In the data file, enter any information about a user's work, department, or division location.COLNAME=1 ROTATE="0" MOREROWS="0"Login scriptCOLNAME=2 ROTATE="0" MOREROWS="0"The value of the login script is the name of a file containing the ASCII text for the login script. You can reuse the same file for all users or have a separate file for each user. In the data file, enter the path to the file as a DOS path. For example:    C:\DIR1\MYLOGIN.SCRThe maximum size of the login script is 16,384 bytes. If the file is larger than this, only the first 16,384 bytes will be copied to the login script.COLNAME=1 ROTATE="0" MOREROWS="0"Low balance limitCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. If unlimited credit is not allowed, in the data file, enter the lowest balance the user can have and still receive services that are chargeable.If accounting is not turned on, this field has no effect. Also, if Allow unlimited credit is set to "Yes," this field has no effect.COLNAME=1 ROTATE="0" MOREROWS="0"Mailbox IDCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. This is a unique name that specifies the directory in which all of the object's inbound mail will be placed. This information is used by NetWare MHS Services.In the data file, assign the user a mailbox ID using the user's login name. If the user's name has spaces in it, or if it uses non-DOS characters, assign the user a mailbox ID using the user's login name, but eliminate the spaces and other illegal characters to form a legal DOS name.If you do not assign a user a mailbox ID, UIMPORT will do so automatically.COLNAME=1 ROTATE="0" MOREROWS="0"Mailbox locationCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the name of the messaging server on which the user's mailbox is located. If the messaging server is not in the same context as the user, enter the complete Directory Services name of the messaging server.For example, if the user's mailbox is located on a messaging server named SERVMAN_MSG and the context of SERVMAN_MSG is Publications.Novell, enter SERVMAN_MSG.Publications.Novell.COLNAME=1 ROTATE="0" MOREROWS="0"Maximum connectionsCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the number of workstations the user can login from. For no limit, enter 0.COLNAME=1 ROTATE="0" MOREROWS="0"Minimum password lengthCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the minimum password length.COLNAME=1 ROTATE="0" MOREROWS="0"NameCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. A value is required for this field. In the data file, enter any unique user name. For example, you can use a student or employee identification number as the login name. This field will be the user's login name in NDS.COLNAME=1 ROTATE="0" MOREROWS="0"Other namesCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. For example, if a user has two additional names that you want to import, enter both them in the data file and enter two field definitions in the import control file called "Other names".COLNAME=1 ROTATE="0" MOREROWS="0"PasswordCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter a unique password for the user. Numbers, letters, and special characters may be used.COLNAME=1 ROTATE="0" MOREROWS="0"Mailing label informationCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. This is a single property with up to six lines of information. If you want a user's entire address imported as a single property, use "Mailing label information" for each field that contains a part of the address. The first field will be the first line of the postal address, the second field will be the second line, etc.If you are going to define only four lines of the postal address in the data file, you only need to include four Mailing label information fields. Each line of the postal address in the data file must be a separate data string (i.e. separated by a comma or other separator).To import four lines of the postal address, you would type the following in the Fields section in the Control file:Fields   ...(other fields)  Mailing label information  Mailing label information  Mailing label information  ...(other fields)In the data file, you might enter a line similar to the following:...,"1234 Any Street","Torrance","CA","98550",...You can use the Mailing label information field in place of Postal code, Post office box, State or province, and City.COLNAME=1 ROTATE="0" MOREROWS="0"Postal (ZIP) codeCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. Enter in the data file the five- or ten-digit zip code. (84111 or 84111-1111). For a Canadian address this is the postal code.COLNAME=1 ROTATE="0" MOREROWS="0"Post office boxCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the user's post office box.COLNAME=1 ROTATE="0" MOREROWS="0"ProfileCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the name of the profile object to which this user belongs. This must include the complete Directory Services name of the profile object if the profile is in a different context than the user.COLNAME=1 ROTATE="0" MOREROWS="0"Remaining grace loginsCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. Normally this field is not imported. This is the number of grace logins still remaining. It is set to the same value as in "Grace logins allowed." If you want this number to be different than the "Grace logins allowed" number, you will have to use the modify option in UIMPORT.For those users whose Remaining grace logins should be the same as the Limit grace logins, either don't import this field or set it to the same number you entered for Limit grace logins.COLNAME=1 ROTATE="0" MOREROWS="0"Require a passwordCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter Y if a password is required. If no password is required for this user, enter N.COLNAME=1 ROTATE="0" MOREROWS="0"Require unique passwordsCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. If unique passwords are required, enter Y in the data file. If unique passwords are not required, in other words the user can reuse passwords, enter N.COLNAME=1 ROTATE="0" MOREROWS="0"See alsoCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. Enter in the data file any other related objects. Enter the complete Directory Services name of the object if it is not in the same context as the User object.COLNAME=1 ROTATE="0" MOREROWS="0"SkipCOLNAME=2 ROTATE="0" MOREROWS="0"This is a unique processing option for UIMPORT. The values in the data file that correspond to Skip fields are ignored by UIMPORT.For example, if you exported into the data file users' birthdays and you do not want this information imported into NDS, enter "Skip" as the field definition. So if you export data that you don't want to import, rather than reexporting the entire data file, you can simply specify "Skip" for the column that contains the information.Suppose you export to the data file a work and a home phone number, but you don't want to import the home phone number. Your data file may have a string like this:...,"801-555-4141","801-555-8677",...Your import control file would correspond like this:Fields  ...  Telephone  Skip  ...The 801-555-8677 field in the data file will be ignored.COLNAME=1 ROTATE="0" MOREROWS="0"Security equal toCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. In the data file, enter the name of the objects to which this user is security equivalent. This name must include the complete Directory Services name of the object if the object is in a different context than the user.COLNAME=1 ROTATE="0" MOREROWS="0"State or provinceCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the State or province of the user.COLNAME=1 ROTATE="0" MOREROWS="0"TelephoneCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. For example, if a user has three telephone numbers that you want to import, enter in the data file each of the three numbers. In the control file, you would need three "Telephone" field entries.COLNAME=1 ROTATE="0" MOREROWS="0"TitleCOLNAME=2 ROTATE="0" MOREROWS="0"Multivalue property. In the data file, enter the user's title.COLNAME=1 ROTATE="0" MOREROWS="0"Volume restrictionsCOLNAME=2 ROTATE="0" MOREROWS="0"Single-value property. In the data file, enter the name of the volume object and the space restrictions on that volume in the following format:Volume object name:Restriction amountTo remove volume restrictions, enter -1 (or any other negative number) for the restriction amount.ID="FM91032"ID="FM15977"PAGENUM=349 ID="BP313"RENDERAS="SECT2"UIMPORT Field Name ChangesUIMPORT data field names have changed in NetWare 4.1. Field names used in NetWare 4.02 are listed in the left column of the following table and new NetWare 4.1 names are listed in the right column.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"4.02 UIMPORT Field NameCOLNAME=2 ROTATE="0" MOREROWS="0"4.1 UIMPORT Field NameVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Minimum account balanceCOLNAME=2 ROTATE="0" MOREROWS="0"Low balance limitCOLNAME=1 ROTATE="0" MOREROWS="0"Login expiration timeCOLNAME=2 ROTATE="0" MOREROWS="0"Account has expiration dateCOLNAME=1 ROTATE="0" MOREROWS="0"Login grace limitCOLNAME=2 ROTATE="0" MOREROWS="0"Grace logins allowedCOLNAME=1 ROTATE="0" MOREROWS="0"Login maximum simultaneousCOLNAME=2 ROTATE="0" MOREROWS="0"Maximum connectionsCOLNAME=1 ROTATE="0" MOREROWS="0"Login disabledCOLNAME=2 ROTATE="0" MOREROWS="0"Account disabledCOLNAME=1 ROTATE="0" MOREROWS="0"Password expiration timeCOLNAME=2 ROTATE="0" MOREROWS="0"Date password expiresCOLNAME=1 ROTATE="0" MOREROWS="0"Password expiration intervalCOLNAME=2 ROTATE="0" MOREROWS="0"Days between forced changesCOLNAME=1 ROTATE="0" MOREROWS="0"Password minimum lengthCOLNAME=2 ROTATE="0" MOREROWS="0"Minimum password lengthCOLNAME=1 ROTATE="0" MOREROWS="0"Password requiredCOLNAME=2 ROTATE="0" MOREROWS="0"Require a passwordCOLNAME=1 ROTATE="0" MOREROWS="0"Password unique requiredCOLNAME=2 ROTATE="0" MOREROWS="0"Require a unique passwordCOLNAME=1 ROTATE="0" MOREROWS="0"Password allow changeCOLNAME=2 ROTATE="0" MOREROWS="0"Allow user to change passwordCOLNAME=1 ROTATE="0" MOREROWS="0"Postal addressCOLNAME=2 ROTATE="0" MOREROWS="0"Mailing label informationCOLNAME=1 ROTATE="0" MOREROWS="0"Security equalsCOLNAME=2 ROTATE="0" MOREROWS="0"Security equal toCOLNAME=1 ROTATE="0" MOREROWS="0"Facsimile telephone numberCOLNAME=2 ROTATE="0" MOREROWS="0"FAX numberCOLNAME=1 ROTATE="0" MOREROWS="0"Telephone numberCOLNAME=2 ROTATE="0" MOREROWS="0"TelephoneCOLNAME=1 ROTATE="0" MOREROWS="0"New fieldCOLNAME=2 ROTATE="0" MOREROWS="0"Foreign Email addressCOLNAME=1 ROTATE="0" MOREROWS="0"New fieldCOLNAME=2 ROTATE="0" MOREROWS="0"Foreign Email aliasCOLNAME=1 ROTATE="0" MOREROWS="0"New fieldCOLNAME=2 ROTATE="0" MOREROWS="0"Full nameCOLNAME=1 ROTATE="0" MOREROWS="0"New fieldCOLNAME=2 ROTATE="0" MOREROWS="0"Generational qualifierCOLNAME=1 ROTATE="0" MOREROWS="0"New fieldCOLNAME=2 ROTATE="0" MOREROWS="0"InitialsCOLNAME=1 ROTATE="0" MOREROWS="0"New fieldCOLNAME=2 ROTATE="0" MOREROWS="0"Mailbox IDCOLNAME=1 ROTATE="0" MOREROWS="0"New fieldCOLNAME=2 ROTATE="0" MOREROWS="0"Mailbox locationPAGENUM=350 ID="BP314"RENDERAS="SECT2"Examples of Files Used by UIMPORTIDXID="w8218"BOOK="_idx" COLLECTION="nw41" TIDREF="i1768"IDXID="w8219"BOOK="_idx" COLLECTION="nw41" TIDREF="i4628"The following examples are based on records taken from a database sample that uses these fields:TYPE="VERT"Last name:First name:Middle initial:Local address   Street:   City:   State or province:   Zip code:Student number:Year:Major:Cumulative grade point average:Department:PAGENUM=351 ID="BP315"RENDERAS="SECT3"IDXID="w8220"BOOK="_idx" COLLECTION="nw41" TIDREF="i1367"ID="FM32317"Data File Created from Exported Database FieldsIDXID="w8221"BOOK="_idx" COLLECTION="nw41" TIDREF="i924"IDXID="w8222"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"IDXID="w8223"BOOK="_idx" COLLECTION="nw41" TIDREF="i917"
When you export your database records to a comma-separated ASCII file, the records appear in the data file as shown here:"Jones","Adam","J","111 South 8th East","Salt Lake City","Utah","84007","2345","Sophomore","Environmental Engineering","2.8","Engineering Sciences""Smith","John","D","222 North Cerillos","Los Angeles","California","96000","2875","Senior","Accounting", "3.0","Business Administration"RENDERAS="SECT4"Corresponding Import Control FileIDXID="w8224"BOOK="_idx" COLLECTION="nw41" TIDREF="i1367"Using the data file as a guide, you could set up the import control file to import the data file fields as shown here. This example assumes that you are creating new users in the NDS database:TYPE="VERT"Import control   Name context=.administration.student_accts   User template=y   Create home directory=y   Home directory path="Students/Home"   Home directory volume=".SYSVOL.Student Records"Fields   Last name   Given name   Middle initial   Mailing label information   Mailing label information   Mailing label information   Mailing label information   Name   Skip   Skip   Skip   DepartmentPAGENUM=352 ID="BP316"Note how the Name field corresponds to a student ID number. When the ID number is imported into NDS, it will become the user's login name---which is the User object name.Managing numbers is difficult because they don't uniquely identify a user. To avoid having to manage numbers, you can create a field of unique login names in your data file.RENDERAS="SECT3"ID="FM13792"IDXID="w8225"BOOK="_idx" COLLECTION="nw41" TIDREF="i917"
Data File Edited to Update User ObjectsIDXID="w8226"BOOK="_idx" COLLECTION="nw41" TIDREF="i917"Suppose that later you wanted to update User object information and add properties that were not imported when the users were created.For example, if you wanted to delete values from the "Middle initial" field, import new values from the "Year," "Major," and "Grade point average" fields, and change the separator used for all user information after Adam Jones, you would edit the data file as shown here:MOREINFO="NONE""Jones","Adam","#DEL","111 South 8th East","Salt Lake City","Utah","84007","2345","Sophomore","Environmental Engineering","2.8","Engineering Sciences"MOREINFO="NONE"!Separator=/MOREINFO="NONE""Smith"/"John"/"#DEL"/"222 North Cerillos"/"Los Angeles"/"California"/ "96000"/"2875"/"Senior"/"Accounting"/"3.0"/"Business Administration"Import control parameters are initially set in the control file, but can be included in the data file. If you include control parameters in the data file, the parameter should be preceded by an exclamation point (!).For example, to place the users in the Engineering.Novell context, and to change the separator to a semicolon (;) you would add the following lines to the data file:!Name context=.Engineering.Novell. !Separator=;RENDERAS="SECT4"Corresponding Changes to the Import Control FileAfter editing the data file, you must change the import control file to reflect the changes you made.PAGENUM=353 ID="BP317"In the following example, the "delete property" and "replace value" control parameters have been added to delete the marked properties and specify that you want properties in both single and multivalue fields to be replaced by new properties. Fields marked "Skip" are replaced by "See also," so the properties will be imported to the "See also" field for the users.TYPE="VERT"Import controlName context=.administration.student_accts   User template=y   Create home directory=y   Home directory path=students/home   Home directory volume=.SYSVOL.Student Records   Delete property=#DEL   Replace value=yFields   Last name   Given name   Middle initial   Postal address   Postal address   Postal address   Postal address   Name   See also   See also   See also   DepartmentPAGENUM=354 ID="BP318"RENDERAS="SECT2"ID="FM51525"Creating User Objects with the UIMPORT UtilityIDXID="w8227"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"IDXID="w8228"BOOK="_idx" COLLECTION="nw41" TIDREF="i4629"IDXID="w8229"BOOK="_idx" COLLECTION="nw41" TIDREF="i4710"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation logged in to the network, running DOS 3.30 or above or OS/2 v2.x, and using NetWare 4.1 client softwareA minimum of 512 KB of memory available on the workstationThe Create or Supervisor object right to the container object where the User objects will be createdThe Create or Supervisor file system right to the directory where user home directories will be created (if applicable)RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Generate a data file from within your database application.For general instructions, see 
IDREF="FM96458""Generating the Data File" on page 331. For specific instructions, see the documentation accompanying your application.PERFORMANCE="REQUIRED"Create an import control file.If you have enough memory, save this file in the same directory in which you saved the data file. Otherwise, you will need to specify the path to both the data file and the import control file when you run UIMPORT.PERFORMANCE="REQUIRED"Run UIMPORT from the directory in which you saved the data file and the import control file.At the DOS command line, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"UIMPORT MOREINFO="NONE"[control_fileMOREINFO="NONE"] MOREINFO="NONE"[data_fileMOREINFO="NONE"] [/MOREINFO="NONE"C]MOREINFO="NONE" <Enter>Replace control_file with the name of the import control file you created. Replace 
data_file with the name of the data file you generated from your database application. Use 
MOREINFO="NONE"/C to run UIMPORT with continuous output.If you don't run UIMPORT from a directory that contains both the import control file and the data file, you must specify the path to each file.Importing hundreds or thousands of users may take several hours. Therefore, you might want to run UIMPORT at night.PAGENUM=355 ID="BP319"PERFORMANCE="REQUIRED"(Optional) Route import errors to a file
.If errors occur during the import process, messages appear on your workstation screen. If you want the messages sent to a file, add the DOS ">
filename" option to the command.For example, to route the messages to a file called uimport.log in your home directory, use a command similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"UIMPORT [control_file] [data_file] >home\paul\uimport.log MOREINFO="NONE"<Enter>When importing large groups of users, the performance of your server might begin to slow down. This reduction in performance is related to the amount of memory available for Directory Services and TTS to use with UIMPORT's numerous transactions. This reduction is related to the size of UIMPORT batches available server memory.If you will be importing large groups of users or experience decreased server performance while running UIMPORT, you can add server memory, process smaller batches of users, or process UIMPORT batches during periods of low server utilization.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Control parametersCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM76715"Table 5-1 on page 336COLNAME=1 ROTATE="0" MOREROWS="0"Creating import filesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83497""Repairing the NetWare Directory Database" on page 356COLNAME=1 ROTATE="0" MOREROWS="0"Field definitionsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM45494"Table 5-2 on page 341PAGENUM=356 ID="BP320"RENDERAS="SECT1"ID="FM83497"Repairing the NetWare Directory DatabaseIDXID="w8230"BOOK="_idx" COLLECTION="nw41" TIDREF="i1255"
IDXID="w8231"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"IDXID="w8232"BOOK="_idx" COLLECTION="nw41" TIDREF="i924"IDXID="w8233"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"
The IDXID="w8234"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
DSREPAIR utility is provided with NetWare 4TM software to repair problems with NetWare Directory Services on a single-server basis. It does not correct problems on other servers from a single, centralized location. It must be run on each server that you want to correct Directory database errors on.RENDERAS="SECT2"DSREPAIR OverviewIDXID="w8235"BOOK="_idx" COLLECTION="nw41" TIDREF="i1255"The DSREPAIR utility allows you to maintain and repair the local NetWare Directory database of a tree. This utility performs the following operations:MARK=BULLETRepairs the local databaseThe repair is performed for the DS.NLM file stored on the current server you are running the DSREPAIR utility on.Repairs local replicasYou are provided with tools to repair replicas, replica rings, and server objects. You can also view the purge time of each replica to ensure that data in each replica is the same.Analyzes each server in each local partition for synchronization errorsYou can view errors and list the partition name, server name, synchronization time, and error code for each error.Writes replica information to a log fileThe log file contains detailed information about local partitions and servers. This information helps you diagnose damage to the database.Creates a dump file of a damaged databaseThe dump file is saved in a compressed format. You can use DSREPAIR to diagnose and repair the damaged database.Checks the remote server ID listYou can access a list of the identification numbers for remote servers. You can use this list to verify the identification numbers of remote servers and modify the numbers if you need to.PAGENUM=357 ID="BP321"Searches for local database objectsA browser allows you to locate and synchronize objects in the local database.IDXID="w8236"BOOK="_idx" COLLECTION="nw41" TIDREF="i3786"
Some NDS database problems are not fatal, and Directory Services continues to operate. But if the database becomes corrupted, you get a message on the console that the server could not open the local database. In this case, run DSREPAIR or reinstall the NDS database to fix the problem so that the database can be opened.DSREPAIR affects only the parts of the database stored on the server where you run it. To fix the entire database, you must run the utility on each server which contains a part of the database.DSREPAIR changes inconsistent objects to Unknown objects when they do not have mandatory properties or are invalid in other respects (their properties don't meet minimum requirements for an object type). Unknown objects can be deleted but cannot be changed back to their original object type.In NetWare 4.1, Unknown objects are represented by question mark icons in the NetWare Administrator utility.RENDERAS="SECT2"DSREPAIR OptionsIDXID="w8237"BOOK="_idx" COLLECTION="nw41" TIDREF="i1255"After you load DSREPAIR, you can use the following options:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Use toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Unattended Full RepairCOLNAME=2 ROTATE="0" MOREROWS="0"Automatically perform all possible repair operations to the Directory database that do not require operator assistance.COLNAME=1 ROTATE="0" MOREROWS="0"Time SynchronizationCOLNAME=2 ROTATE="0" MOREROWS="0"Contact all servers within this server's local database to request information about Directory Services and time synchronization.If a replica of the root partition is contained on this server, then all servers in the Directory tree are contacted.COLNAME=1 ROTATE="0" MOREROWS="0"Replica SynchronizationCOLNAME=2 ROTATE="0" MOREROWS="0"Determine the status of synchronization for every replica in the replica table for the Directory tree.The status of synchronization can inform you of the current condition of the Directory tree.COLNAME=1 ROTATE="0" MOREROWS="0"View/Edit Repair Log FileCOLNAME=2 ROTATE="0" MOREROWS="0"Track all operations of the DSREPAIR utility to a single file. The default log file is SYS:SYSTEM\DSREPAIR.LOG.You can configure options for the log file by accessing "Log File And Login Configuration" in the "Advanced Options" menu.COLNAME=1 ROTATE="0" MOREROWS="0"Advanced Options MenuCOLNAME=2 ROTATE="0" MOREROWS="0"The "Advanced Options" menu allows you to manually perform individual or global repair operations on the Directory tree. You can also access diagnostic information about the Directory tree database to analyze the status of the tree.See IDREF="FM40436""Using the Advanced Options" on page 364 for more information.PAGENUM=358 ID="BP322"RENDERAS="SECT2"ID="FM79465"Running an Unattended Full RepairIDXID="w8238"BOOK="_idx" COLLECTION="nw41" TIDREF="i1255"
Use this procedure to perform an automatic repair of the Directory database. Any operation requiring an operator's assistance, such as managing partition replicas or editing remote server ID numbers,  is not performed.If you want to manually repair the Directory database, use options available in the "Advanced Options" menu. See IDREF="FM40436""Using the Advanced Options" on page 364 for more information.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to the server console or an established RCONSOLE session with the serverAll servers in a tree using the same time sourceThe Supervisor object right to the [Root] object of the Directory treeRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, load the module by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD DSREPAIR MOREINFO="NONE"<Enter>
PAGENUM=359 ID="BP323"If you have placed DSREPAIR in a directory other than SYS:SYSTEM, you must enter the full path to the utility.The utility locks the database.PERFORMANCE="REQUIRED"Choose "Unattended Full Repair."The "Repairing Directory on Server 
servername" screen appears. A window is available to observe the repairs in process.Following the automatic repair, a message window appears that informs you of the repair status, the total number of errors corrected, and the amount of time used to complete the repair operation.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to display the error log file.The error log is displayed within a full text editor. You can annotate or modify the DSREPAIR log if you want to.RENDERAS="SECT2"Checking Time Synchronization (DSREPAIR)IDXID="w8239"BOOK="_idx" COLLECTION="nw41" TIDREF="i1255"
Use this procedure on the server before or after performing a repair. It allows you to contact all servers within this server's local database to request information about Directory Services and time synchronization.If a replica of the root partition is contained on this server, then all servers in the Directory tree are contacted.Time synchronization is very important to Directory Services. All servers in a tree must be synchronized to the same time source. If they are not, collision will occur when synchronizing objects in replicas.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to the server console or an established RCONSOLE session with the serverAll servers in a tree using the same time sourcePAGENUM=360 ID="BP324"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, load the module by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD DSREPAIR MOREINFO="NONE"<Enter>If you have placed DSREPAIR in a directory other than SYS:SYSTEM, you must enter the full path to the utility.The utility locks the database.PERFORMANCE="REQUIRED"Choose "Time Synchronization."The "Collecting Time Synchronization and Server Status" screen appears. A window is available to observe the operations in process.Following the operation, the DSREPAIR log is displayed within a full text editor. You can annotate or modify the DSREPAIR log if you want to.The DSREPAIR log contains the following:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"FieldCOLNAME=2 ROTATE="0" MOREROWS="0"IndicatesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Server NameCOLNAME=2 ROTATE="0" MOREROWS="0"All of the server names known to the local Directory database. If this server contains a replica of the root partition, then this list contains all the servers in the tree.COLNAME=1 ROTATE="0" MOREROWS="0"VersionCOLNAME=2 ROTATE="0" MOREROWS="0"The version of DS.NLM running on the server.COLNAME=1 ROTATE="0" MOREROWS="0"Replica DepthCOLNAME=2 ROTATE="0" MOREROWS="0"The replica depth field reports "-1" if no replicas are stored on the server or "0" if the server contains a replica of the root partition. A positive integer indicates how many objects deep from the root the first replica is on that server.COLNAME=1 ROTATE="0" MOREROWS="0"Time SourceCOLNAME=2 ROTATE="0" MOREROWS="0"The time server type. This information helps you determine if time synchronization for all the trees in the server is configured properly.All servers in a tree must be using the same time source.For example, if there are two Single time servers then you know that all servers in the tree cannot be polling the same time source and there is a configuration problem.COLNAME=1 ROTATE="0" MOREROWS="0"Time in SyncCOLNAME=2 ROTATE="0" MOREROWS="0"The local time synchronization status on each server. The status should be "Yes." If the status is "No," then the server is not able to contact its time source. COLNAME=1 ROTATE="0" MOREROWS="0"Time +/-COLNAME=2 ROTATE="0" MOREROWS="0"The difference in time between the local server and the selected server in the list. All servers should be within one second of each other; if they are not, they have not been configured properly.This field reports up to 999 minutes and 59 seconds (which is approximately 16 hours and 30 minutes) in the form minutes:seconds. If the time difference is greater than 16 hours and 30 minutes, then the maximum value is displayed as: -999:59.If the difference in time is more than a few minutes, it might indicate that the servers are using different time source servers.PAGENUM=361 ID="BP325"RENDERAS="SECT2"Checking Replica SynchronizationIDXID="w8240"BOOK="_idx" COLLECTION="nw41" TIDREF="i1255"
Use this procedure on the server to determine the status of synchronization for every replica in the replica table for the Directory tree.The synchronization status can inform you of the current condition of the Directory tree.If you want to manually manage the Directory partitions and replicas, use the "Replica And Partition Operations" option in the "Advanced Options" menu. See IDREF="FM40436""Using the Advanced Options" on page 364 for more information.Normal partitioning operations should be done with one of the client utilities (NWADMIN or PARTMGR). The "Replica Synchronization" option should only be used when the master replica of a partition has been lost because of server or hardware failure and the server will be reinstalled into the NetWare Directory tree.You need to synchronize damaged replicas manually, using the PARTMGR utility or Partition Manager in the NetWare Administrator utility.Be careful when changing a secondary replica to a master. If a server containing a secondary is changed to a master and the server containing the original master is brought back up, there is a possibility that the partition will have two master replicas.PAGENUM=362 ID="BP326"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to the server console or an established RCONSOLE session with the serverThe Supervisor object right to the [Root] object of the Directory treeRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, load the module by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD DSREPAIR MOREINFO="NONE"<Enter>If you have placed DSREPAIR in a directory other than SYS:SYSTEM, you must enter the full path to the utility.The utility locks the database.PERFORMANCE="REQUIRED"Choose "Replica Synchronization."The "Log In as the Admin" screen appears.PERFORMANCE="REQUIRED"Enter the administrator name and password to log in to the tree.Log in as a user who has the Supervisor object right to the [Root] object of the tree. Enter your complete name (Distinguished Name), such as ADMIN.NOVELL or CN=ADMIN.O=NOVELL. Entering only ADMIN is invalid because it is not a complete name.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter>.The "Collecting Replica Synchronization And Server Status" screen appears. A window is available to observe the operations in process.Following this operation, the DSREPAIR log is displayed within a full text editor. You can annotate or modify the DSREPAIR log if you want to.
PAGENUM=363 ID="BP327"The error log contains the following fields:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"FieldCOLNAME=2 ROTATE="0" MOREROWS="0"IndicatesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Servers That Contain ReplicasCOLNAME=2 ROTATE="0" MOREROWS="0"The servers in the tree that contain replicas.COLNAME=1 ROTATE="0" MOREROWS="0"Replica TypeCOLNAME=2 ROTATE="0" MOREROWS="0"The type of replica for each server that contains replicas of partitions.Following is a list of the possible types of replicas.Master. This is a writable replica that can also handle partition operations. There is only one master replica per partition.   Only one partition operation is valid at any time for a partition, and the master enforces that requirement. For all nonpartition operations, this replica is equivalent to a read/write replica.Read/Write. This is a writable replica that can be updated from a client workstation. Both read/write and master replicas are valid for login and authentication requests.Read-Only. This is a replica that cannot be changed from a client workstation. It is updated with the changed data in the replica from another read/write or master. This replica cannot be used for bindery services because bindery services requires a writable replica to be contained on the server for bindery users.Subordinate Reference. This is a replica of the root partition which includes the replica list (ring). As a child partition, it resides on every server that holds a copy of it's parent partition.This replica is used to facilitate tree connectivity. COLNAME=1 ROTATE="0" MOREROWS="0"StatusCOLNAME=2 ROTATE="0" MOREROWS="0"The synchronization status of partition replicas for servers in the tree. The server running DSREPAIR does not synchronize to itself, so the status for the server's own replica is displayed as "Host".PAGENUM=364 ID="BP328"RENDERAS="SECT2"Viewing and Editing the Repair Log FileIDXID="w8241"BOOK="_idx" COLLECTION="nw41" TIDREF="i1255"
Use this procedure on the server to view and edit repair information for the local Directory tree.The default log file is SYS:SYSTEM\DSREPAIR.LOG. You can change the filename with the "Log File and Login Configuration" option in the "Advanced Options" menu. See IDREF="FM40436""Using the Advanced Options" on page 364 for more information.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to the server console or an established RCONSOLE session with the serverThe Supervisor object right to Directory objects in the local treeRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, load the module by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD DSREPAIR MOREINFO="NONE"<Enter>If you have placed DSREPAIR in a directory other than SYS:SYSTEM, you must enter the full path to the utility.The utility locks the database.RENDERAS="SECT2"ID="FM40436"Using the Advanced OptionsUse this procedure to access the "Advanced Options" for manual repair of the Directory database.If you want the Directory database to be repaired automatically, use the options available from the "Unattended Full Repair" option in the main menu. See IDREF="FM79465""Running an Unattended Full Repair" on page 358 for more information.PAGENUM=365 ID="BP329"The "Advanced Options" menu includes the following options:TYPE="VERT""Log File Login Configuration""Repair Local DS Database""Servers Known to this Database""View Remote Server ID List""Replica and Partition Operations""Security Equivalence Synchronization""Global Schema Update""View/Edit Repair Log File""Create a Database Dump File"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to the server console or an established RCONSOLE session with the serverThe Supervisor object right to the [Root] object in the treeRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, load the module by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD DSREPAIR MOREINFO="NONE"<Enter>If you have placed DSREPAIR in a directory other than SYS:SYSTEM, you must enter the full path to the utility.The utility locks the database.PERFORMANCE="REQUIRED"Choose "Advanced options menu."PERFORMANCE="REQUIRED"From the menu, select the repair operation you want to perform.
PAGENUM=366 ID="BP330"Refer to the online help in DSREPAIR for more information and instructions on how to use these options in the DSREPAIR utility.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Directory Services databaseCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NetWare Directory Services" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"DSREPAIR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"DSREPAIR" in Utilities ReferenceRENDERAS="SECT1"Merging NDS TreesIDXID="w8242"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"IDXID="w8243"BOOK="_idx" COLLECTION="nw41" TIDREF="i2002"IDXID="w8244"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
The DSMERGE utility allows you to merge the [Root] of two separate NDS trees. Only the [Root] objects are merged; container objects and their leaf objects maintain separate identities within the newly merged [Root].RENDERAS="SECT2"DSMERGE OverviewIDXID="w8245"BOOK="_idx" COLLECTION="nw41" TIDREF="i1252"
The two IDXID="w8246"BOOK="_idx" COLLECTION="nw41" TIDREF="i1252"
trees you merge are called the local source tree and the target tree. To merge two trees, you load DSMERGE on a server in the local tree.DSMERGE does not change Directory names or contexts within the containers. Object and property rights for the merged objects are retained.You can't merge container or leaf objects with DSMERGE. To move leaf objects, use the NetWare Administrator graphical utility or the NETADMIN text utility. To merge partitions, use the PARTMGR utility.RENDERAS="SECT3"Merging the Source into the Target TreeWhen you merge the trees, the servers in the source tree become part of the target tree. (The target tree is the tree that the local tree will be merged into.)The target [Root] object becomes the new [Root] for objects in the source tree, and the tree name of all servers in the source tree is changed to the target tree name.After the merge, the target tree name is retained.The objects that were subordinate to the local [Root] object become subordinate to the target [Root] object.PAGENUM=367 ID="BP331"RENDERAS="SECT3"Partition ChangesDuring the merge, all replicas of the root partition are removed from servers in the local tree. The server that contained the master replica of the local tree receives a replica of the target tree's root partition.During the merge, DSMERGE splits the objects below the local [Root] object into separate partitions.The following two figures illustrate the effect on partitions when you merge two trees.LABEL="5-3" FLOAT="0"Directory Trees Before a MergeFILEREF="n41su40a.tif"PAGENUM=368 ID="BP332"LABEL="5-4" FLOAT="0"Directory Tree After a MergeFILEREF="n41su41a.tif"RENDERAS="SECT2"Preparing the Source and Target TreesIDXID="w8247"BOOK="_idx" COLLECTION="nw41" TIDREF="i1252"
Before IDXID="w8248"BOOK="_idx" COLLECTION="nw41" TIDREF="i3378"
performing a merge operation, ensure that the state of synchronization for all servers affected by the operation is stable. The following table provides recommendations for preparing source and target trees for merging.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Necessary PreconditionCOLNAME=2 ROTATE="0" MOREROWS="0"Required ActionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"No aliases or leaf objects can exist at the [Root] of the source tree.COLNAME=2 ROTATE="0" MOREROWS="0"Delete any aliases or leaf objects at the  [Root] of the source tree.COLNAME=1 ROTATE="0" MOREROWS="0"No similar names can exist between the source and target trees.COLNAME=2 ROTATE="0" MOREROWS="0"Rename objects on the source and target trees if similar names exist.Move objects from one of the containers to a different container in its tree if you don't want to rename objects. Then delete the empty container before running DSMERGE. (See IDREF="FM37086""Moving Objects in the Directory Tree" on page 87 and IDREF="FM36317""Moving Container Objects Using NETADMIN" on page 94.)You can have identical container objects in both trees if they are not immediately subordinate to the [Root]. They are uniquely identified by their immediate container object.COLNAME=1 ROTATE="0" MOREROWS="0"No login connections can exist on either the source or target trees.COLNAME=2 ROTATE="0" MOREROWS="0"Close all connections on the source and target trees.COLNAME=1 ROTATE="0" MOREROWS="0"The NDS version must be the same on both source and target tree.COLNAME=2 ROTATE="0" MOREROWS="0"Upgrade all non-4.1 servers that have a replica of the [Root] object.COLNAME=1 ROTATE="0" MOREROWS="0"Any server that contains a replica of the [Root] object on both source and target trees must be up and running.COLNAME=2 ROTATE="0" MOREROWS="0"Ensure that all servers containing a replica of the [Root] partition on both source and target trees are up and running.Ensure that any WAN links affected are stable.COLNAME=1 ROTATE="0" MOREROWS="0"Schema on both source and target trees must be the same.COLNAME=2 ROTATE="0" MOREROWS="0"Ensure that the time on the source and target trees are synchronized within two seconds of each other.PAGENUM=370 ID="BP333"Because the merge operation is one single transaction, it is not subject to catastrophic failure caused by power outages or hardware failure. However, you should perform a regular backup of the Directory database before using DSMERGE. See IDREF="FM49062"Chapter 9, "Backing Up and Restoring Data."RENDERAS="SECT2"Time Synchronization before the MergeProper IDXID="w8249"BOOK="_idx" COLLECTION="nw41" TIDREF="i3378"
configuration of time synchronization is a very involved process. Make sure you allow enough time to synchronize both trees before you merge the trees.Directory Services will not work properly if two external time sources are used, or if all servers in a tree are not synchronized.Before you do the merge, make sure that all servers in both trees are synchronized, and use only one time source.There should be a maximum of one Reference or one Single Reference time server in a tree. Likewise, after the merge, the tree should contain only one Reference or one Single Reference time server.If each of the trees you are merging has either a Reference or one Single Reference time server, you must reassign one of them to refer to the Reference or Single Reference time server in the other tree so that the final tree contains only one Reference or Singe Reference time server (if any).For more information on time synchronization, see IDREF="FM74015""Managing Network Time Synchronization" on page 571.To view time synchronization information, see IDREF="FM40415""Checking Time Synchronization (DSMERGE)" on page 373.PAGENUM=371 ID="BP334"RENDERAS="SECT2"DSMERGE OptionsIDXID="w8250"BOOK="_idx" COLLECTION="nw41" TIDREF="i1252"
After you load DSMERGE, you can use the following options:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Use toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Check Servers in This TreeCOLNAME=2 ROTATE="0" MOREROWS="0"Contact all servers in the local tree to verify that each server has the correct version, status, and tree name.The server you are on must have a replica of the [Root] partition. It does not require the master replica.COLNAME=1 ROTATE="0" MOREROWS="0"Check Time SynchronizationCOLNAME=2 ROTATE="0" MOREROWS="0"Display a list of all servers in this tree, along with information about time sources and time synchronization.The server you are on must have a replica of the [Root] partition. It does not require the master replica.COLNAME=1 ROTATE="0" MOREROWS="0"Merge Two TreesCOLNAME=2 ROTATE="0" MOREROWS="0"Merge the [Root] of the local (source) tree to the [Root] of the target tree.The server you are on must have the master replica of the local tree's [Root] partition.COLNAME=1 ROTATE="0" MOREROWS="0"Rename TreeCOLNAME=2 ROTATE="0" MOREROWS="0"Rename the local tree. Use this option if you are merging two roots with the same name.You can rename only the local tree name. To rename the target tree name, load DSMERGE on a server in the target tree. Then load DSMERGE on the source tree to perform the merge.This option requires that the server you are on has the master replica of the  [Root] partition.RENDERAS="SECT2"ID="FM78228"Checking Servers in the TreeIDXID="w8251"BOOK="_idx" COLLECTION="nw41" TIDREF="i1252"
Before you rename or merge trees, use this option to contact all servers in the tree and verify that all servers have the same tree name.After you rename or merge trees, use this option to verify that all servers have the new tree name.PAGENUM=372 ID="BP335"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to a server console on the local tree or an established RCONSOLE session with the serverThe Supervisor object right to the [Root] object of the local treeRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load DSMERGE on the server where a replica of the [Root] partition of the local tree is stored.At the server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD DSMERGE MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Check servers in this tree."Each server in the tree is listed
 in the "Status of Servers in the Tree" screen. with their corresponding statu
s information. Any servers that have existing problems are flagged and then listed at the top of the server list.You should confirm that each server's status is marked as "Verified" before completing a merge of two trees.The following table describes the information provided in the 
"Status of Servers in the Tree" screen.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"FieldCOLNAME=2 ROTATE="0" MOREROWS="0"OperationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Server NameCOLNAME=2 ROTATE="0" MOREROWS="0"Lists the names of all servers DSMERGE contacted, and shows their context within the tree.COLNAME=1 ROTATE="0" MOREROWS="0"VersionCOLNAME=2 ROTATE="0" MOREROWS="0"Indicates the version of NetWare running on the server.COLNAME=1 ROTATE="0" MOREROWS="0"StatusCOLNAME=2 ROTATE="0" MOREROWS="0"MARK=BULLETUPIndicates that the server is in the right tree.MARK=BULLETErrornumberAll Directory Services errors are numbered between -600 and -699 in decimal notation.See BOOK="sysmsenu" COLLECTION="nw41"System Messages for an explanation of specific Directory Services error messages.UnknownIndicates the server is not responding. This is usually the cause of a downed server or of communication problems.Wrong TreeIndicates that this server does not belong to this Directory tree.This status might occur if the tree was recently merged or renamed because the server might take a few minutes to recognize the change.Or, this status can occur if the server was reinstalled in another tree, but not properly removed from this tree. If so, delete this server's object from this tree.PAGENUM=373 ID="BP336"RENDERAS="SECT2"ID="FM40415"Checking Time Synchronization (DSMERGE)IDXID="w8252"BOOK="_idx" COLLECTION="nw41" TIDREF="i1252"
Use this procedure on both of the trees before merging them.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to a server console on both the source and target trees or an established RCONSOLE session with the serversThe Supervisor object right to the [Root] object of both the source and target treesPAGENUM=374 ID="BP337"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load DSMERGE on the server where a replica of the [Root] partition of the local tree is stored that has the master replica.At the server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD DSMERGE MOREINFO="NONE"<Enter>If you don't know where th
e master replica is, load DSMERGE on any server. You will be prompted wit
h the name of the server that contains the master replica when it is required.PERFORMANCE="REQUIRED"Choose "Check time synchronization."The "Time Synchronization Information for Tree 
treename" screen appears.This option displays a list of all servers in the tree, along with information about their time sources and the server time.Verify that all servers in 
the tree are synchronized and that they are 
using the same time source
.The following table describes the information provided in the "Time Synchronization Information for Tree 
treename" screen.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"FieldCOLNAME=2 ROTATE="0" MOREROWS="0"OperationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Server NameCOLNAME=2 ROTATE="0" MOREROWS="0"Lists the name of each server recorded in the tree's [Root] partition. If the server could not be contacted, it is listed as "Unknown."COLNAME=1 ROTATE="0" MOREROWS="0"TypeCOLNAME=2 ROTATE="0" MOREROWS="0"Indicates the kind of time server the server is using.COLNAME=1 ROTATE="0" MOREROWS="0"In SyncCOLNAME=2 ROTATE="0" MOREROWS="0"MARK=BULLETYESIndicates that the server is in sync with the time server.MARK=BULLETNOIndicates that the server is in not sync with the time server.This option does not indicate if the local server is in sync with the server you have selected. Check the type of time server each server is using to determine if they are using different time servers.COLNAME=1 ROTATE="0" MOREROWS="0"Time DeltaCOLNAME=2 ROTATE="0" MOREROWS="0"Displays the difference in time between the local server and the selected server in the list.If the difference in time is more than a few minutes, it may indicate that the servers are using different time servers.PAGENUM=375 ID="BP338"RENDERAS="SECT2"Merging Two TreesIDXID="w8253"BOOK="_idx" COLLECTION="nw41" TIDREF="i2408"IDXID="w8254"BOOK="_idx" COLLECTION="nw41" TIDREF="i1252"
For complete functionality of all menu options in DSMERGE, load DSMERGE on a server that contains the master replica.If you don't know where the master replica is stored, you will be prompted with the correct server name when you attempt an operation that requires the master replica.To perform a merge operation, you must load DSMERGE on the local tree.When merging large trees, it's significantly faster to designate the source tree as the tree with fewer objects immediately subordinate to the [Root]. By doing this, you create fewer partition splits during the merge, since all target tree objects result in new partitions.PAGENUM=376 ID="BP339"Because the local tree name no longer exists after the merge, you must update the "PREFERRED TREE" statement in the NET.CFG files of all local client workstations.To minimize the number of client workstations you need to update, designate the tree with the most client workstations as the target tree, because the final tree retains the name of the target tree.Or, rename the tree after the merge operation so that the final tree name corresponds to the tree with the greater number of client workstations attaching to it. See IDREF="FM48447""Renaming the Tree" on page 377.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to the server console on the local tree or an established RCONSOLE session with that serverThe Supervisor object right to the [Root] object of both trees you want to mergeA regular backup of the Directory Services database for the two treesAll servers in both trees are synchronized and using the same time source(Optional) All servers in the tree are verifiedRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load DSMERGE on the server where the master replica on the local tree is stored.At the server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD DSMERGE MOREINFO="NONE"<Enter>If you don't know where the master replica is stored, you will be prompted with the correct server name when you attempt to merge the trees.PERFORMANCE="REQUIRED"Choose "Merge two trees."The "Merge Tree Information" screen appears.
PAGENUM=377 ID="BP340"PERFORMANCE="REQUIRED"Enter the administrator name and password to log in to the local (source) tree.Log in as a user who has the Supervisor object right to the [Root] object on the local tree. Enter the typeless or typeful Distinguished Name, such as ADMIN.NOVELL or CN=ADMIN.O=NOVELL. Entering only ADMIN is invalid because it is not the complete name of the User object.PERFORMANCE="REQUIRED"Choose "Target Tree" and select a target tree from the list servers in the "Available Trees" window.If the tree you want is not in the list, press 
MOREINFO="NONE"<Insert> and enter the target tree's network address.PERFORMANCE="REQUIRED"Enter the administrator name and password to log in to the target tree.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to perform the merge.A message stating that the trees have been merged successfully is displayed.RENDERAS="SECT2"ID="FM48447"Renaming the TreeIDXID="w8255"BOOK="_idx" COLLECTION="nw41" TIDREF="i1252"
You must rename a tree if the two trees you want to merge have the same name.IDXID="w8256"BOOK="_idx" COLLECTION="nw41" TIDREF="i3781"
You can IDXID="w8257"BOOK="_idx" COLLECTION="nw41" TIDREF="i3781"
rename only the local (source) tree name. To rename the target tree, run DSMERGE from a server on the target tree.After you change a tree's name, you must update the clients' "PREFERRED TREE" statement in their NET.CFG files.When you merge two trees, to minimize the number of client workstations that need to be updated, designate the tree with the most client workstations as the target tree because the final tree retains the name of the target tree.Or, rename the tree after the merge so that the final tree name corresponds to the tree name with the majority of client workstations.Another option is to rename the merged tree to the name of the original source tree. If you choose this option, then you must update the NET.CFG files on the target tree client workstations.PAGENUM=378 ID="BP341"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to a server console on the local tree or an established RCONSOLE session with the serverThe Supervisor object right to the [Root] object of the local tree(Optional) All servers in the tree are verifiedRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load DSMERGE on the server where a master replica of the [Root] partition is stored.At the server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD DSMERGE MOREINFO="NONE"<Enter>If you don't know where the master replica is, load DSMERGE on any server in the local tree. Then you will be prompted with the correct server name when you attempt to rename a tree.PERFORMANCE="REQUIRED"Choose "Rename this tree."PERFORMANCE="REQUIRED"Enter the administrator name and password to log in to the local (source) tree.Log in as a user who has the Supervisor object right to the [Root] object on the local tree. Enter your complete name, such as ADMIN.NOVELL or CN=ADMIN.O=NOVELL. Entering only ADMIN is invalid since it is not a complete name.PERFORMANCE="REQUIRED"Enter the new tree name
.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to perform the rename.
PAGENUM=379 ID="BP342"RENDERAS="SECT2"Completing the Tree MergeIDXID="w8258"BOOK="_idx" COLLECTION="nw41" TIDREF="i2408"
Following the merging of two trees, it might be necessary to complete the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"(Optional) Choose "Checking Servers in the Tree" in the DSMERGE main menu to confirm that all tree names were changed correctly. See IDREF="FM78228""Checking Servers in the Tree" on page 371.Check the new partitions that the merge operation created. If you have many small partitions in the new tree, or if you have partitions that contain related information, you might want to merge them. See IDREF="FM32409""Merging Partitions" on page 291.Copy a new replica to any non-NetWare 4.1 servers after the merge is complete, if you did not upgrade before running DSMERGE.Re-create any leaf objects or aliases at the [Root] that were deleted before you run DSMERGE.Evaluate partitioning of the Directory tree.Merging trees might significantly change replica placement on the source tree. You should carefully evaluate and change the partitioning as needed.Update client workstations' "PREFERRED TREE" statements in their NET.CFG files or rename the target tree.Only the target tree name is retained after the merge.To minimize the number of NET.CFG files you need to update, designate the tree with the most client workstations as the target tree because the final tree retains the name of the target tree.Or, rename the tree after the merge operation so that the final tree name corresponds to the majority of the client workstations' NET.CFG files. See IDREF="FM48447""Renaming the Tree" on page 377.The target [Root] object becomes the new [Root] for servers moved from the source tree. The Access Control List (ACL) for the [Root] object of the source tree are preserved. Therefore, the rights of the source tree's user ADMIN to the [Root] object are still valid.After the merge is complete, both ADMIN users still exist and are uniquely identified by different container objects.PAGENUM=380 ID="BP343"For security reasons, you might want to delete one of the two ADMIN User objects or restrict the rights of the two objects.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Object and property rightsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54098""Object Rights" on page 32and IDREF="FM98432""Property Rights" on page 33COLNAME=1 ROTATE="0" MOREROWS="0"Partitions and replicasCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM34584""Creating and Managing Directory Services Partitions" on page 284COLNAME=1 ROTATE="0" MOREROWS="0"[Root] objectCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="getstenu" COLLECTION="nw41"The Directory Tree"  in Introduction to NetWare Directory Services, and "BOOK="getstenu" COLLECTION="nw41"[Root] Object" in Introduction to NetWare Directory Services"BOOK="cncptenu" COLLECTION="nw41"Root object," "BOOK="cncptenu" COLLECTION="nw41"Directory tree," and "BOOK="cncptenu" COLLECTION="nw41"Objects" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Time synchronizationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74015""Managing Network Time Synchronization" on page 571COLNAME=1 ROTATE="0" MOREROWS="0"DSMERGECOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"DSMERGE" in Utilities ReferencePAGENUM=381 ID="BP344"RENDERAS="SECT1"IDXID="w8259"BOOK="_idx" COLLECTION="nw41" TIDREF="i2633"
Viewing and Managing NDS Synchronization StatusIDXID="w8260"BOOK="_idx" COLLECTION="nw41" TIDREF="i1256"
This section explains the IDXID="w8261"BOOK="_idx" COLLECTION="nw41" TIDREF="i1256"IDXID="w8262"BOOK="_idx" COLLECTION="nw41" TIDREF="i2634"
NDS Trace feature that you can use from the server console. You should use this feature:MARK=BULLETTo determine whether NDS synchronization processes are complete.To diagnose NDS errors. These errors may appear when you are manipulating NDS objects with the administration utilities. NDS errors also show up on the NDS Trace screen.You can identify NDS-related system messages by their numbering: -601 through -699 and F966 through F9FE.As with all NetWare system messages, an NDS system message does not necessarily indicate an error condition, but may simply indicate general NDS status. For more information, see the specific message in 
BOOK="sysmsenu" COLLECTION="nw41"System Messages.RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXAccess to the server console, or an established RCONSOLE session with the serverRENDERAS="SECT2"IDXID="w8263"BOOK="_idx" COLLECTION="nw41" TIDREF="i1256"
ProcedurePERFORMANCE="REQUIRED"Turn on the IDXID="w8264"BOOK="_idx" COLLECTION="nw41" TIDREF="i1256"
NDS Trace screen by typing the following at the server console:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NDS TRACE TO SCREEN = ON MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"(Optional) To copy NDS Trace messages to a file, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NDS TRACE TO FILE = ON MOREINFO="NONE"<Enter>By default, the messages are copied to the file DSTRACE.DBG in the SYS:SYSTEM directory.To copy the messages to a different directory and/or file on volume SYS:, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NDS TRACE FILENAME = path\filename MOREINFO="NONE"<Enter>Copying NDS Trace messages to a file may be helpful if you need to ask someone else for diagnostic help.PAGENUM=382 ID="BP345"PERFORMANCE="REQUIRED"To view NDS Trace screen messages, press MOREINFO="NONE"<Alt>+<Esc> until you see the "Directory Services" screen.Two types of messages are of particular interest:
MARK=BULLET"All processed = YES" indicates that all pending NDS synchronization actions have been processed.MARK=BULLETMessages numbered -601 through -699 and F966 through F9FE indicate NDS status or errors. For explanations and suggested actions, see 
BOOK="sysmsenu" COLLECTION="nw41"System Messages.PERFORMANCE="REQUIRED"To disable tracing, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NDS TRACE TO SCREEN = OFF MOREINFO="NONE"<Enter>COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NDS Trace optionsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"NetWare Directory Services Parameters" under SET in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"NDS system messagesCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="sysmsenu" COLLECTION="nw41"System MessagesLABEL="6"PAGENUM=383 ID="BP346"ID="FM16817"Migrating Data Using the High Capacity Storage SystemRENDERAS="SECT1"What is the High Capacity Storage System?The High Capacity Storage System (HCSS) is a utility that extends the 
storage capacity of a NetWare® server by integrating an optical disk library, or jukebox, into the NetWare file system.HCSS moves files between the server's faster, but limited-capacity, storage devices (hard disks) and the slower, high-capacity storage devices (magneto-optical disks) in a jukebox.This process, called data migration and demigration, is mostly hidden from the end user.HCSS uses a NetWare volume to cache frequently used files, and manages the migration of less frequently used files to media in a jukebox.Once a jukebox and the HCSS directories are set up, users and applications can access files stored on media by using the same NetWare commands and function calls with which they access files stored on the volume.After the initial configuration, you can use HCSS in the NetWare Administrator graphical utility toMARK=BULLETImport and export mediaFormat and reformat mediaDelete HCSS directoriesChange HCSS file storage parametersHCSS also gives you the flexibility to physically transport directory and file data. You can move 
media to another jukebox, or you can store media on a shelf for archiving.PAGENUM=384 ID="BP347"RENDERAS="SECT2"HCSS ConceptsTo understand the information in this chapter, you should be familiar with the following entries in Concepts:TYPE="VERT""BOOK="cncptenu" COLLECTION="nw41"Data migration""
BOOK="cncptenu" COLLECTION="nw41"High Capacity Storage System""
BOOK="cncptenu" COLLECTION="nw41"Jukebox"RENDERAS="SECT2"ID="FM11148"How the HCSS File System Is StructuredIDXID="w8265"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"An HCSS directory looks like other directories in the NetWare file system. However, certain levels in an HCSS directory are created and handled differently.IDREF="FM98503"Figure 6-1 illustrates these levels in a NetWare file system structure.LABEL="6-1" FLOAT="0"ID="FM98503"Sample HCSS File System StructureFILEREF="n41su38a.tif"You create HCSS domain directories off the root of an HCSS volume. Within these directories, you create pairs of media-label directories. Each media-label directory corresponds to one side of media (that is, to one side of magneto-optical media that is labeled "Formatted Rewriteable Optical Disk").Creating HCSS directories and non-HCSS directories on the same volume can cause problems for HCSS users. Non-HCSS directories can fill the volume to its migration threshold and trigger migration inefficiently.PAGENUM=385 ID="BP348"IDREF="FM40681"Figure 6-2 illustratesIDXID="w8266"BOOK="_idx" COLLECTION="nw41" TIDREF="i2361"
 the association between media in the jukebox and media-label directories in the HCSS volume on the server.LABEL="6-2" FLOAT="0"ID="FM40681"Labeled Media and Related DirectoriesFILEREF="n41su48a.tif"An HCSS volume can contain an unlimited number of HCSS domain directories, and each domain directory can have several media-label directories (in multiples of two only, one media-label directory for every side of media assigned to that domain directory).Each media-label directory can have multiple levels of subdirectories and files, like any other NetWare directory.You are limited, however, to only one HCSS volume per NetWare server and to two media-label directories for each piece of media (that is, two for each optical disk) your jukebox will hold.Although it is possible for HCSS domain directories and non-HCSS directories (regular NetWare directories) to coexist on the same volume, for management simplicity, we recommend you create and dedicate one volume exclusively for HCSS domain directories and their contents.PAGENUM=386 ID="BP349"RENDERAS="SECT2"What Happens When Data MigratesA file is 
considered migrated when the file data (everything inside of the file) has been moved from the volume to the corresponding labeled side of media in the jukebox.File information, such as the file name and file size, remains on the volume so you can view the complete directory structure and access a file at any time.The space the file data occupied on the NetWare volume is available after the file data has migrated, thus allowing more data to be stored in the volume. A 100MB volume, for example, has the potential to store many gigabytes as some of its files migrate to the jukebox.The triggers that start and stop migration are the upper and lower threshold parameters, which are set with HCSS commands.The least-recently-used file data migrates when the upper volume-capacity threshold is reached or at a set time of day, and migration continues until the lower volume-capacity threshold is reached.IDREF="FM24776"Figure 6-3 illustrates the upper and lower threshold concept. Assume that this is a 
100MB volume and that its upper threshold is set to 80 percent and its lower threshold to 30 percent.When 80 MB of the volume contain data, the oldest file data begins to migrate to the jukebox. The data continues to migrate until only 30 MB of data remain on the volume, making 50 MB of space on the volume available for more file data.PAGENUM=387 ID="BP350"LABEL="6-3" FLOAT="0"ID="FM24776"Volume Capacity Before and After Data MigrationFILEREF="n41su49a.tif"This migration process might happen several times a day, depending on the size of the volume.Migration occurs on a file-by-file basis according to the last time a file was accessed (least-recently-used files migrate first).The migration process doesn't allow file data to flow from one side of media to the other. If one side of media is nearly full, you are notified so you can decide whether to delete or move files.For information on how to determine if a file has been migrated, see "BOOK="utlrfenu" COLLECTION="nw41"NDIR" or "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.Migrated file data stays on the media until the file is accessed; then the file data is automatically demigrated to the volume. Migrated files are always available, but file access may be slower.RENDERAS="SECT2"PAGENUM=388 ID="BP351"Media Access ControlHCSS has options you can adjust to provide fair and efficient access to media in the jukebox. These options allow you to specify the amount of time a side of media is loaded in the jukebox drive to fill requests before the changer switches to another side of media.The way HCSS controls media access is called elevator queuing. Elevator queuing for a jukebox works like an elevator in a tall building. Requests for any given floor come in sporadically. Rather than filling the requests in a first-come-first-served order, the elevator system determines the most efficient way to fill every request.The number of people who can get on or off the elevator on any floor is determined by how long the doors remain open on a floor. If the elevator doors are closing and a person in the hallway pushes the elevator button, the doors will open again for a given period.Likewise with HCSS, all requests for a side of media are queued by the system. Once the side of media is loaded into the drive, the system tries to fill as many requests as possible within a given time limit.RENDERAS="SECT2"Media Export and Import OperationsHCSS can export (remove) media from the jukebox and later import (load) it into the same jukebox or into a different jukebox on another server with HCSS installed.Before exporting a piece of media, HCSS attempts to migrate all file data under the two affected media-label directories to the media.If all file data is migrated, the media, complete with the two media-label directories and files, is ejected from the jukebox while all references to the two directories are deleted from the volume.If the export operation fails and the media is not ejected from the jukebox, it may be because the contents of the media-label directories can't fit on the media. You may need to move or delete files and try to export again.When media is imported and assigned to an HCSS domain directory, the two media-label directories (including all subdirectories, files, and file attributes) are re-created in the domain directory just as they were before the media was exported.PAGENUM=389 ID="BP352"RENDERAS="SECT2"RestrictionsIDXID="w8267"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"The following restrictions apply when you use the HCSS utility.MARK=BULLETSupports only one volume per server.Only one NetWare volume on the server where HCSS is installed can have the migration attribute set.Do not have more than one volume with the migration attribute set on the server where HCSS is installed. This would compromise migration and may cause migration to fail.Restoring an HCSS volume requires completing a mixture of procedures using both the HCSS utility and the SBACKUP utility (or similar backup engine). For more information, see "BOOK="superenu" COLLECTION="nw41"Restoring Migrated Files" in Chapter 9.Supports only one jukebox per server.Supports only the DOS name space.Requires an MS Windows client.Requires use of NetWare Administrator to delete media-label and domain directories.You can delete HCSS domain directories and media-label directories only by using the HCSS tools in the NetWare Administrator graphical utility.Doesn't support modifying directory attributes.You shouldn't modify the directory attributes of an HCSS domain directory or any subdirectory under it.Doesn't support renaming of any subdirectory under a media-label directory.PAGENUM=390 ID="BP353"RENDERAS="SECT1"ID="FM39726"Overview of HCSS Setup and ManagementIDXID="w8268"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"IDREF="FM29684"Figure 6-4 illustrates the tasks required to integrate HCSS with your regular NetWare® file system.LABEL="6-4" FLOAT="0"ID="FM29684"HCSS TasksFILEREF="n41su50a.tif"PAGENUM=391 ID="BP354"RENDERAS="SECT2"How the HCSS File System Is ManagedAfter you install HCSS on the server, you can use the NetWare Administrator graphical utility (NWADMIN) at a workstation to perform all routine file system management tasks.IDREF="FM92506"Table 6-1 summarizes how you must create, set up, and manage the levels of the HCSS directory structure.Do not use other NetWare utilities to manage HCSS domain directories or media-label directories. Doing so could cause your file system to become corrupted.LABEL="6-1" PGWIDE=0 TOCENTRY="1"ID="FM92506" Managing the HCSS File SystemCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"File System LevelCOLNAME=2 ROTATE="0" MOREROWS="0"Management MethodVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"HCSS volumeCOLNAME=2 ROTATE="0" MOREROWS="0"Use the NetWare INSTALL module to create and modify volumes.Use HCSS commands either in NetWare Administrator or at the server console prompt (MSEngine prompt if you are running SFT III) to set data migration parameters for the volume.Requires Supervisor right, or equivalent, in the file system.COLNAME=1 ROTATE="0" MOREROWS="0"HCSS domain directory on the volumeCOLNAME=2 ROTATE="0" MOREROWS="0"Use HCSS commands in NetWare Administrator to create and manage HCSS domain directories.Requires Supervisor right, or equivalent, in the file system.COLNAME=1 ROTATE="0" MOREROWS="0"HCSS media-label directoryCOLNAME=2 ROTATE="0" MOREROWS="0"Use HCSS commands in NetWare Administrator to create and modify media-label directories.Requires Supervisor right, or equivalent, in the file system.COLNAME=1 ROTATE="0" MOREROWS="0"Subdirectories below media-label directoryCOLNAME=2 ROTATE="0" MOREROWS="0"Create and modify by using standard NetWare and DOS utilities and commands.Users with appropriate rights can work at this level the same as they do in the regular NetWare file system.PAGENUM=392 ID="BP355"RENDERAS="SECT2"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating HCSS volumesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM43676""Creating an HCSS Volume" on page 394"BOOK="instlenu" COLLECTION="nw41"Manage NetWare Volumes" in Chapter 3 of InstallationCOLNAME=1 ROTATE="0" MOREROWS="0"HCSS functionalityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"High Capacity Storage System" and "BOOK="cncptenu" COLLECTION="nw41"Data migration" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"HCSS system messagesCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="sysmsenu" COLLECTION="nw41"System MessagesRENDERAS="SECT1"Installing and Setting Up HCSSRENDERAS="SECT2"ID="FM23049"Installing HardwareThe NetWare 4.1 release of HCSS requires the following:MARK=BULLETHewlett-Packard 1718, 1715, or 1710 SCSI jukeboxes or compatible jukeboxes using the HPCHGR.DSK driver (which supports 512- or 1024- bytes/sector media)SCSI host bus adapters and drivers that support or emulate ASPITRANMagneto-optical media that have been low-level formatted (labeled "Formatted Rewriteable Optical Disk" by the manufacturer)A workstation running MS WindowsIDXID="w8269"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"
Install the 
jukebox and its adapter board according to the documentation that came with the products. We recommend that the jukebox be the only device connected to the SCSI adapter board.For more information on supported jukeboxes, call FAXBACK at 1-800-414-LABS.PAGENUM=393 ID="BP356"RENDERAS="SECT2"ID="FM58810"Loading HCSS DriversIf you are using NetWare 4.1 SFT IIITM on your network, load drivers using the procedures under IDREF="FM58036""Loading HCSS Drivers with SFT III" on page 429.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Ensure that the appropriate hardware has been installed as recommended by the hardware manufacturer.PERFORMANCE="REQUIRED"IDXID="w8270"BOOK="_idx" COLLECTION="nw41" TIDREF="i2153"
Load
IDXID="w8271"BOOK="_idx" COLLECTION="nw41" TIDREF="i2153"
 the applicable 
IDXID="w8272"BOOK="_idx" COLLECTION="nw41" TIDREF="i2155"
drivers
.Use the following synta
x:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD [path]controller_board_driver [option]MOREINFO="NONE"<MOREINFO="NONE"Enter>
LOAD HPCHGR 
MOREINFO="NONE"<Enter>HPCHGR is Novell's driver that ships with NetWare to operate the jukebox.For example, if you are using an Adaptec 1740 board, type the following
at the server console prompt, in the order given:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD C:AHA1740 DEV_ENABLE=0MOREINFO="NONE" <Enter>
LOAD HPCHGR
MOREINFO="NONE" <Enter>The AHA driver autoloads ASPITRAN.DSK
.Some adapter board drivers require specifying an option (such as "DEV_ENABLE=0" in the previous example) to prevent the driver from taking control of the jukebox.For more information about driver options, see the hardware manufacturer's documentation.For more information about loading drivers, see IDREF="FM93561""Loading Disk Drivers" on page 538.PERFORMANCE="REQUIRED"Type the following at the server console prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"SCAN FOR NEW DEVICES MOREINFO="NONE"<Enter>The SCAN FOR NEW DEVICES command checks for IDXID="w8273"BOOK="_idx" COLLECTION="nw41" TIDREF="i1027"IDXID="w8274"BOOK="_idx" COLLECTION="nw41" TIDREF="i1638" peripheral devices added since the 
IDXID="w8275"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
server was last booted, and then registers the added devices with the operating system.
PAGENUM=394 ID="BP357"PERFORMANCE="REQUIRED"(Optional) Verify that the device was successfully loaded.At the server consol
e prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LIST DEVICES MOREINFO="NONE"<Enter>A list is displayed of all activ
e IDXID="w8276"BOOK="_idx" COLLECTION="nw41" TIDREF="i1027"IDXID="w8277"BOOK="_idx" COLLECTION="nw41" TIDREF="i1638"
peripheral devices on your server, including the magneto-optical drives in the jukebo
x.RENDERAS="SECT2"ID="FM43676"Creating an HCSS VolumeAn IDXID="w8278"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"
HCSS IDXID="w8279"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"
volume must be in the NetWare Directory ServicesTM database, and the HCSS volume must not be in the SYS: volume.To simplify management of your HCSS system, we recommend that you create a dedicated HCSS volume for your domain directories and their contents.Make the HCSS volume capacity at least 10 percent of the full capacity of the jukebox. Consider adding hard disk space or moving existing directories if necessary. You should provide enough room for frequently accessed files, or access time may be slower due to file migration and demigration.An HCSS volume is created like any other NetWare volume, but it requires some specific settings.Create an HCSS volume using the procedure detailed in IDREF="FM64431""Creating Volumes" on page 499, but, before mounting it, do the following:MARK=BULLETChoose the volume and set the following parameters:TYPE="VERT"File Compression: OFF or ON (as appropriate)Block Suballocation: OFF or ON (as appropriate)Data Migration: ONTo change any of these parameters, select the parameter and press MOREINFO="NONE"<Enter> to toggle between off and on.Choose the volume and set the volume block size, using one of these supported settings, to match your average file size:Settings: 4 KB, 8 KB, 16 KB, 32 KB, or 64 KBIf Block Suballocation is ON, set "Volume Block Size" to 64 KB.Save all changesPAGENUM=395 ID="BP358"RENDERAS="SECT2"ID="FM87900"Loading HCSS on the ServerIf you are using SFT III on your network, load HCSS using the procedures under IDREF="FM64861""Loading HCSS on the MSEngine" on page 430.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXJukebox and adapter installed according to the hardware manufacturer's instructionsHCSS volume created and mountedHCSS drivers loaded, and scan for new devices done (see IDREF="FM58810""Loading HCSS Drivers" on page 393)RENDERAS="SECT3"IDXID="w8280"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"
ProcedureIDXID="w8281"BOOK="_idx" COLLECTION="nw41" TIDREF="i2155"PERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD HCSS MOREINFO="NONE"<Enter>The HCSS modul
e, as well as several othe
r loadable modules, autoloads RTDM.NLM
 (a module that enables migration).When HCSS is loaded, it takes inventory of the media in the jukebox and verifies a correlation between the media-label directories (directories created when importing media) and the media. Any 
media without corresponding media
-label 
directories begins ejecting.When HCSS has completed the inventory and verification, the message "HCSS is up and running" appears on the server console and is broadcast to user ADMI
N. (The message doesn't appear when HCSS is loaded for the first time.)When HCSS is loaded for the first time, it will not be up and running until you create the volume, domain directory, and media-label directories, in that order. (For information on the required flow of tasks, see IDREF="FM39726""Overview of HCSS Setup and Management" on page 390.)PERFORMANCE="REQUIRED"(Conditional) If the jukebox ejects media when you load HCSS, remove the media and, at the server consol
e prompt, type the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MEDIA REMOVED MOREINFO="NONE"<Enter>
PAGENUM=396 ID="BP359"Enter this command for each 
piece of media that is ejected.You can prevent more media from being ejected by typing the following command at the server console: HCSS Eject Media Override=On. See IDREF="FM97367""Setting Parameters at the Server Console" on page 425.PERFORMANCE="REQUIRED"(Optional) Add the commands to load the drivers and loadable modules to the server's AUTOEXEC.NCF file.You can load the drivers and modules automatically every time the server is booted by adding the commands to your AUTOEXEC.NCF file.For more information about adding commands to the .NCF file, se
e IDREF="FM33588""Creating or Editing a Server Batch (.NCF) File" on page 448.Two .NCF files are included in the HCSS module for unloading and reloading HCSS when needed. Run HUNLOAD.NCF if it becomes necessary to unload HCSS. Run HRELOAD.NCF to reload (reinitialize and set up) HCSS after a fatal error has occurred.PERFORMANCE="REQUIRED"At the workstation you plan to use to manage HCSS, edit the NWADMIN.INI file as described in the following section
, IDREF="FM79397""Setting Up a Workstation to Manage HCSS."RENDERAS="SECT2"ID="FM79397"ID="FM76167"Setting Up a Workstation to Manage HCSSMany HCSS management tasks can be done only through NetWare Administrator, which runs under MS Windows.In order for HCSS to appear in the "Tools" pull-down menu in NetWare Administrator, you must IDXID="w8282"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"
modifyIDXID="w8283"BOOK="_idx" COLLECTION="nw41" TIDREF="i2155"
 the NWADMIN.INI file on the workstation where you will do these tasks.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXHCSS hardware and server software installedA volume created and set up for the HCSS file systemA workstation running NetWare Administrator under MS WindowsPAGENUM=397 ID="BP360"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the workstation you plan to use to manage HCSS, log in as ADMIN to the server where HCSS is loaded.PERFORMANCE="REQUIRED"At the same workstation, change to the MS 
Windows directory where the NWADMIN.INI file is stored.If you ca
n't locate the NWADMIN.INI file, verify that you have successfully loaded NetWare Administrator in your MS 
Windows directory.For more information, see 

BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User Guide.PERFORMANCE="REQUIRED"Using a text editor, open the NWADMIN.INI file and add the following lines under the [Snapin Object DLLs] section heading:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Vis HCSSDecider=hdecsnap.dll
Vis HCSSObject=hobjsnap.dll
Vis HCSSMedia=hmedsnap.dllPERFORMANCE="REQUIRED"Save your changes and exit the NWADMIN.INI file.PERFORMANCE="REQUIRED"Create HCSS directories
, using the procedures in the following sectio
n.RENDERAS="SECT2"ID="FM54389"Setting Up the HCSS File SystemTo set IDXID="w8284"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"
up your HCSS file system:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Create one or more HCSS domain directories off the root of the HCSS volume. (See IDREF="FM68889""Creating an HCSS Domain Directory" on page 398.)Create media-label directories immediately below each domain directory. (See IDREF="FM71689""Creating HCSS Media-Label Directories" on page 400.)Because the domain directory and the media-label directory must be managed with HCSS commands, you might want to give them distinctive names to distinguish them from other NetWare directories.PAGENUM=398 ID="BP361"RENDERAS="SECT3"ID="FM68889"Creating an HCSS Domain DirectoryRENDERAS="SECT4"ID="FM53631"IDXID="w8285"BOOK="_idx" COLLECTION="nw41" TIDREF="i1172"
PrerequisitesIDXID="w8286"BOOK="_idx" COLLECTION="nw41" TIDREF="i874"MARK=CHECKBOXA workstation running NetWare Administrator with the NWADMIN.INI file modified for HCSSHCSS hardware and server software installedA volume created and set up for the HCSS file systemYou are logged in as ADMIN to the server on which HCSS is loadedRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the browser, select the HCSS volume where you want to create the HCSS domain directory.For information about moving around in the browser and selecting objects, choose "Help" from the menu bar and look up "Navigation."PERFORMANCE="REQUIRED"Verify that HCSS options appear in the "Tools" menu.The options include "HCSS Parameters" and "HCSS Create."If the HCSS options do not appear in the "Tools" menu, verify that you have met the prerequisites listed for this procedure.PERFORMANCE="REQUIRED"ID="FM91167"From the "Tools" menu, select "HCSS Create."(See IDREF="FM32590"Figure 6-5.)
PAGENUM=399 ID="BP362"LABEL="6-5" FLOAT="0"ID="FM32590"Selecting the "HCSS Create" OptionFILEREF="n41su63a.tif"The "HCSS Create Directory" dialog box appears. (See the example in IDREF="FM58585"Figure 6-6).LABEL="6-6" FLOAT="0"ID="FM58585""HCSS Create Directory" Dialog BoxFILEREF="n41su54a.tif"PERFORMANCE="REQUIRED"Complete the "HCSS Create Directory" dialog.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM92629"In the "HCSS Directory" text box, type a unique name for the HCSS domain directory.The name can be no longer than eight characters. Allowable characters are: uppercase A-Z and 0-9.PERFORMANCE="REQUIRED"(Optional) If you want to create more than one HCSS domain directory, select "Create Another Directory."
PAGENUM=400 ID="BP363"PERFORMANCE="REQUIRED"ID="FM34109"Choose "Create."If you selected "Create Another Directory," the dialog box remains on the screen so you can type in your next directory name.If you did not select (or have unselected) "Create Another Directory," you are returned to the browser, where the name or names of the new HCSS directories appear under the HCSS volume.You can now create HCSS media-label directories, as described in the following section.RENDERAS="SECT3"ID="FM71689"Creating HCSS Media-Label DirectoriesIDXID="w8287"BOOK="_idx" COLLECTION="nw41" TIDREF="i874"RENDERAS="SECT4"IDXID="w8288"BOOK="_idx" COLLECTION="nw41" TIDREF="i1172"
PrerequisitesMARK=CHECKBOXA workstation running NetWare Administrator with the NWADMIN.INI file modified for HCSSHCSS hardware and server software installedA volume created and set up for the HCSS file systemYou are logged in as ADMIN to the server on which HCSS is loadedYou create media-label directories when you assign labeled media to a domain directory.To label or assign new or existing media, use the following table and determine which procedures to follow.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you need toCOLNAME=2 ROTATE="0" MOREROWS="0"Complete these proceduresVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Load new media (or media that you intend to overwrite) into the jukebox and file systemCOLNAME=2 ROTATE="0" MOREROWS="0"1. IDREF="FM51472""Importing Media" on page 4012. IDREF="FM46501""Formatting Media" on page 4033. IDREF="FM28321""Assigning HCSS Media to Domain Directories" on page 405COLNAME=1 ROTATE="0" MOREROWS="0"Import previously formatted media, with files and directories intact, into the jukebox and file systemCOLNAME=2 ROTATE="0" MOREROWS="0"1. IDREF="FM51472""Importing Media" on page 4012. IDREF="FM28321""Assigning HCSS Media to Domain Directories" on page 405PAGENUM=401 ID="BP364"For an example of assigned media, see IDREF="FM40681"Figure 6-2.Always use the "HCSS Import" option to load media; don't load it into the jukebox manually.RENDERAS="SECT3"ID="FM51472"Importing MediaIDXID="w8289"BOOK="_idx" COLLECTION="nw41" TIDREF="i1648"RENDERAS="SECT4"ProcedureIDXID="w8290"BOOK="_idx" COLLECTION="nw41" TIDREF="i1770"PERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"ID="FM14648"From the browser, choose an HCSS domain directory.PERFORMANCE="REQUIRED"ID="FM25135"From the "Tools" menu, select "HCSS Media."(See 
IDREF="FM18371"Figure 6-7.)LABEL="6-7" FLOAT="0"ID="FM18371"Selecting the "Import Media" OptionFILEREF="n41su66a.tif"PERFORMANCE="REQUIRED"From the "HCSS Media" menu, select "Import Media."The "Import" dialog box appears
, prompting you to insert the media.Before inserting media, label the cartridges with the names of the two media-label directories you plan to create.PERFORMANCE="REQUIRED"ID="FM84281"Insert the media into the jukebox's mail slot.Use only media labeled "Formatted Rewriteable Optical Disk." PAGENUM=402 ID="BP365"PERFORMANCE="REQUIRED"ID="FM91214"Choose "OK."The "HCSS Media Management" dialog box 
(IDREF="FM11642"Figure 6-8) appears, displaying the state of the media that was loaded (either "Media is unformatted" or "Media is formatted and unassigned").LABEL="6-8" FLOAT="0"ID="FM11642""HCSS Media Management" Dialog BoxFILEREF="n41su61a.tif"If the media is unformatted, you must format it before proceeding. PERFORMANCE="REQUIRED"ID="FM79594"Choose a command from the dialog box and then go to the appropriate procedures
, as shown in the following table:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you need toCOLNAME=2 ROTATE="0" MOREROWS="0"ChooseCOLNAME=3 ROTATE="0" MOREROWS="0"Then go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Format or reformat media (when media is new or you plan to overwrite existing contents)COLNAME=2 ROTATE="0" MOREROWS="0"FormatCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM46501""Formatting Media" on page 403COLNAME=1 ROTATE="0" MOREROWS="0"Create HCSS media-label directories by assigning media to an HCSS domain directoryCOLNAME=2 ROTATE="0" MOREROWS="0"AssignCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM28321""Assigning HCSS Media to Domain Directories" on page 405COLNAME=1 ROTATE="0" MOREROWS="0"Eject media from the jukeboxCOLNAME=2 ROTATE="0" MOREROWS="0"CancelCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM84281"Step 5 if you want to import media, or continue to select "Cancel" to return to the browserPAGENUM=403 ID="BP366"RENDERAS="SECT3"ID="FM46501"Formatting MediaBefore files can be stored on media, the media must be high-level 
formatted by HCSS.RENDERAS="SECT4"ID="FM75857"PrerequisitesMARK=CHECKBOXHCSS hardware and server software installedA volume created and set up for the HCSS file systemYou are logged in as ADMIN to the server on which HCSS is loadedA workstation running NetWare Administrator with the NWADMIN.INI file modified for HCSSMagneto-optical media imported into the jukebox (see IDREF="FM51472""Importing Media" on page 401)RENDERAS="SECT4"IDXID="w8291"BOOK="_idx" COLLECTION="nw41" TIDREF="i1547"
ProcedureIDXID="w8292"BOOK="_idx" COLLECTION="nw41" TIDREF="i1648"PERFORMANCE="REQUIRED"Ensure that you meet the prerequisites.PERFORMANCE="REQUIRED"From the "HCSS Media Management" dialog box
, choose "Format."A message appears, warning you about erasing data and asking if you are sure you want to format the media. When you select 
"Yes,
" the dialog box i
n IDREF="FM82342"Figure 6-9 appear
s.If you are reformatting media, the previous media labels appear as defaults in the "Media Label" boxes.PAGENUM=404 ID="BP367"LABEL="6-9" FLOAT="0"ID="FM82342""HCSS Format Media" Dialog BoxFILEREF="n41su59a.tif"PERFORMANCE="REQUIRED"Enter the media label names
.Since labels should not be changed except by reformatting the media, you should plan your labels carefully.Type a unique label for each side of media in the "Media Label" boxes for side 1 and side 2.The labels must be different from all other labels in the HCSS volume. Labels can be no longer than eight characters. The following character sets are allowed: uppercase A-Z and 0-9.The media labels you enter here become the HCSS media-label directory names.PERFORMANCE="REQUIRED"Select one of the options from the following table:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If youCOLNAME=2 ROTATE="0" MOREROWS="0"ChooseCOLNAME=3 ROTATE="0" MOREROWS="0"Then go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Want to accept the format, label the media, and assign the media-label directoriesCOLNAME=2 ROTATE="0" MOREROWS="0"OKCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM28321""Assigning HCSS Media to Domain Directories" on page 405COLNAME=1 ROTATE="0" MOREROWS="0"Do not want to format or label the mediaCOLNAME=2 ROTATE="0" MOREROWS="0"CancelCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM79594"Step 7 in "Importing Media" on page 401 (where you can exit through the "HCSS Media Management" dialog box)PAGENUM=405 ID="BP368"RENDERAS="SECT3"ID="FM28321"Assigning HCSS Media to Domain DirectoriesThe existence of HCSS 
media-label directories implies the existence of media labeled with the same name.You can assign one or more pieces of media (and therefore media-label directories) under an HCSS domain directory. You are limited only to the number of media your jukebox will hold.RENDERAS="SECT4"IDXID="w8293"BOOK="_idx" COLLECTION="nw41" TIDREF="i1648"
ProcedurePERFORMANCE="REQUIRED"Ensure that the "HCSS Assign Media" dialog box is on the screen.IDREF="FM63031"Figure 6-10 shows an example of this dialog box.If you have just imported or formatted media, the box should already be displayed. (If the box isn't displayed, refer to the procedures i
n IDREF="FM51472""Importing Media" on page 401 and make the appropriate selections until the box appears.)LABEL="6-10" FLOAT="0"ID="FM63031""HCSS Assign Media" Dialog BoxFILEREF="n41su55a.tif"The two media labels you entered when you formatted the media appear in the "Media Label" list box.All domain directories assigned to the HCSS volume are listed in the 
"HCSS Directory
" drop box on the right side of the screen.PERFORMANCE="REQUIRED"From the "HCSS Directory" drop box, select an HCSS directory.PERFORMANCE="REQUIRED"Choose "OK."The HCSS media-label directories are assigned to the HCSS domain directory you selected.
PAGENUM=406 ID="BP369"PERFORMANCE="REQUIRED"(Optional) To return to the "HCSS Media Management" dialog box, select "Cancel."PERFORMANCE="REQUIRED"(Optional) To return to the browser, select "Cancel" one or more times.As you return to the browser, the unassigned 
piece of media is ejected.PERFORMANCE="REQUIRED"(Optional) To label media and assign other media-label directories to a domain directory, return to Step 3 in IDREF="FM51472""Importing Media" on page 401.Your HCSS directories and files should now be ready for migration.RENDERAS="SECT1"Managing the HCSS File SystemYou might need to perform some or all of the following tasks to manageIDXID="w8294"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"
 or maintain your HCSS file system:MARK=BULLETExport mediaReload (import) mediaDelete an existing HCSS directoryReformat mediaAlways use the HCSS options in the NetWare Administrator utility to change HCSS domain directories and media-label directories.Always use the "HCSS Import Media" and "HCSS Export Media" options in NetWare Administrator to load and unload media; do not manually load media into the jukebox until prompted by the software.Never rename subdirectories once they are created under media-label directories.PAGENUM=407 ID="BP370"RENDERAS="SECT2"ID="FM79821"Exporting MediaYou must use HCSS commands to export (remove) media from the jukebox.ExportingIDXID="w8295"BOOK="_idx" COLLECTION="nw41" TIDREF="i1391"
 mediaIDXID="w8296"BOOK="_idx" COLLECTION="nw41" TIDREF="i4666"
 removes the two associated HCSS media-label directories and their contents from the NetWare® file system. All files that were cached on the volume are first migrated to media, and then the media is ejected.You might want to export media toMARK=BULLETStore media with its directories and files intactAssign specific media-label directories and data to a different HCSS domain directoryReformat media or move it to a jukebox on a different serverIf the export operation fails, you get a message that HCSS cannot export the media.The export operation will fail if:MARK=BULLETFiles are openFiles are not archived and the Migrate Unarchived Files parameter is turned offFiles are flagged with the Execute Only file attributeSubdirectories under the media-label directory have the Don't Migrate attribute setThere is not enough room on the media to hold all of the unmigrated files that are assigned to itTo make sure files are not in use before exporting media, use the SEND utility at the server console (or at the MSEngine prompt if you are running SFT III) to notify users that you are exporting media.PAGENUM=408 ID="BP371"RENDERAS="SECT3"IDXID="w8297"BOOK="_idx" COLLECTION="nw41" TIDREF="i1648"
ProcedurePERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the browser, select the HCSS volum
e; then select the HCSS domain directory to which the media is assigned.For information about moving around in the browser and selecting objects, choose "Help" from the menu bar.PERFORMANCE="REQUIRED"From the "Tools" menu, select "HCSS Media."PERFORMANCE="REQUIRED"From the "HCSS Media
" menu, select "Export Media."(Se
e IDREF="FM30679"Figure 6-11.)LABEL="6-11" FLOAT="0"ID="FM30679"Selecting the "Export Media" OptionFILEREF="n41su67a.tif"A dialog box similar 
to IDREF="FM60490"Figure 6-12 appears.
PAGENUM=409 ID="BP372"LABEL="6-12" FLOAT="0"ID="FM60490""HCSS Export Media" Dialog BoxFILEREF="n41su58a.tif"PERFORMANCE="REQUIRED"Select the pair of HCSS media-label directories for the media you want to export.PERFORMANCE="REQUIRED"Choose "OK."The names of the HCSS directories are removed from the browser. If the HCSS files are currently located on the server's hard disk, you must wait while they are migrated back to 
the media
 in the jukebox.PERFORMANCE="REQUIRED"When the "Remove Media
" prompt is displayed, remove the media from the jukebox.Both the directory structure and 
the file data are removed from the file system.PERFORMANCE="REQUIRED"Choose "OK.
"The dialog box disappears and you are returned to the browser.RENDERAS="SECT2"Reloading MediaY
ou can IDXID="w8298"BOOK="_idx" COLLECTION="nw41" TIDREF="i1648"
reload the files on exported media, and add the corresponding HCSS media-label directories and contents to your file system, by importing the media with the NetWare Administrator utility.To import previously formatted media into the jukebox with files and directories intact, follow the procedures in IDREF="FM71689""Creating HCSS Media-Label Directories" on page 400.PAGENUM=410 ID="BP373"RENDERAS="SECT2"Deleting an HCSS Domain DirectoryDeleting IDXID="w8299"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"
an HCSS domain directory removes it from the NetWare file system.You must use NetWare Administrator to delete an HCSS domain directory. Using a command line delete or some other delete utility will confuse the jukebox inventory and might cause media to begin ejecting from the jukebox.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Export all media whose labels appear as HCSS media-label directories under the HCSS domain directory you are deleting.For instructions, se
e IDREF="FM79821""Exporting Media" on page 407.PERFORMANCE="REQUIRED"Delete or move any no
n-HCSS files and directories from the HCSS domain directory
, using standard NetWare commands.If yo
u had both HCSS and non-HCSS file
s in the same domain directory, th
e non-HCSS files are probably t
hose remaining after you have exported all media in the domain directory.PERFORMANCE="REQUIRED"From the browser, select the name of the HCSS domain directory you want to delete.PERFORMANCE="REQUIRED"From the "Tools" menu
, select "HCSS Delet
e" (IDREF="FM75926"Figure 6-13).LABEL="6-13" FLOAT="0"ID="FM75926"Selecting the "HCSS Delete" OptionFILEREF="n41su65a.tif"PAGENUM=411 ID="BP374"The 
"HCSS Delete Directory
" dialog box appears. (See the example i
n IDREF="FM13712"Figure 6-14.)LABEL="6-14" FLOAT="0"ID="FM13712""HCSS Delete Directory" Dialog BoxFILEREF="n41su57a.tif"PERFORMANCE="REQUIRED"Choose "Delete."The HCSS domain directory name is removed from the browser and the file system.RENDERAS="SECT2"ID="FM75455"ID="FM57162"Reformatting MediaReformatting
 media 
erases all files and directories stored on the media.You might want to reformat media toMARK=BULLETErase all files and directories stored on the mediaCreate new media labels (HCSS media-label directory names)Assign media to an HCSS directory or eject media and reserve it for future useTo reformat media:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Perform the IDXID="w8300"BOOK="_idx" COLLECTION="nw41" TIDREF="i1648"
procedures under IDREF="FM51472""Importing Media" on page 401.Perform the procedures under IDREF="FM46501""Formatting Media" on page 403.(Optional) If you want to assign media to domain directories at this time, perform the procedures under IDREF="FM28321""Assigning HCSS Media to Domain Directories" on page 405.PAGENUM=412 ID="BP375"RENDERAS="SECT1"Checking Media StatusIDXID="w8301"BOOK="_idx" COLLECTION="nw41" TIDREF="i2361"IDXID="w8302"BOOK="_idx" COLLECTION="nw41" TIDREF="i1648"HCSS provides a command you can use to check media status and verify that migration has occurred.To check HCSS media status, from the server console prompt (MSEngine prompt if you are running SFT III), type the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"HCSS Media Status = [path]The path should include the volume name.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"HCSS Media Status = HCSSVOL:\domain_dir\media-label_dirAfter you enter the command, the following information about the specified media appears:MARK=BULLETTotal Bytes: The total capacity of media, in bytes, for a media-label directoryUsed Bytes: How much space is currently being used in bytesMigrated Files: The number of files that have been migrated to this side of mediaRENDERAS="SECT1"ID="FM51870"Managing HCSS ParametersYou can IDXID="w8303"BOOK="_idx" COLLECTION="nw41" TIDREF="i1649"
customizeIDXID="w8304"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"
 your HCSS volume and define how the volume and jukebox interact by setting various HCSS parameters. You can set or change these parameters either through MS Windows, using NetWare Administrator, or at the server console prompt (MSEngine prompt if you are running a NetWare 4.1 SFT IIITM system).All HCSS parameters have default settings. You don't need to change these settings unless you want to customize HCSS operations.(For information on the default settings, see IDREF="FM72442""Setting Parameters Using NetWare Administrator" on page 418 or IDREF="FM97367""Setting Parameters at the Server Console" on page 425.)PAGENUM=413 ID="BP376"RENDERAS="SECT2"ID="FM54352"What the Parameters DoSeveral parameters work together and allow you to specifyMARK=BULLETIf and when data migration occurs (see IDREF="FM69471""Migration If/Then Parameters" on page 413)How media requests are handled (see IDREF="FM53222""Media and Media Request Parameters" on page 414)Which decision-making features are used, either by you or by HCSS (see IDREF="FM32485""Decision-Making Parameters" on page 416)RENDERAS="SECT3"ID="FM69471"Migration If/Then ParametersThe following HCSS parameters let you specify if and exactly when data will migrate to the jukebox.RENDERAS="SECT4"ID="FM84992"Disable MigrationTurn on this parameter when you need to disable migration for any reason---such as reducing demands on the processor or jukebox.RENDERAS="SECT4"ID="FM31020"Migrate Unarchived FilesTurn on this parameter to allow migration of files that have not been backed up. By default this parameter is turned off, which means that files won't migrate until they have been backed up.If you attempt to export media with the Migrate Unarchived Files parameter turned off, and the associated files are unarchived, the media will not be exported.RENDERAS="SECT4"ID="FM84464"Migrate Compressed Files OnlyIf this parameter is set, HCSS migrates only those files that have been compressed (files flagged with "Co") or files that can't be compressed (files flagged with "Cc"). Files that can't be compressed are those that would n't save any space if they were compressed.For more information on file flags, see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.PAGENUM=414 ID="BP377"RENDERAS="SECT4"ID="FM75215"Upper ThresholdThis parameter specifies how full the volume can become before file data begins migrating to the jukebox. This value can be set from 1% to 100%, but it must be higher than the lower threshold.The upper threshold should be set so that the most frequently used files remain cached on the volume.RENDERAS="SECT4"ID="FM33047"Lower ThresholdThis parameter specifies how full the volume can end up after migration ends. The value is a percentage of full, and it must be lower than the upper threshold percentage.RENDERAS="SECT4"ID="FM79293"Migrate to Lower Threshold Hour/MinuteThis parameter specifies a time when data will migrate, regardless of whether the upper threshold is reached.You can disable this parameter by setting the hour and minute to exactly midnight. Migration will still be initiated when the volume capacity reaches the upper threshold.RENDERAS="SECT3"Media and Media Request ParametersID="FM53222"RENDERAS="SECT4"ID="FM50022"Eject Media OverrideTurn on this parameter at the server console prompt to send a message to HCSS to stop media from ejecting.This parameter can be set only from the server console prompt.When HCSS is loaded, it performs a jukebox inventory that detects any inconsistencies between the media-label directories and the labeled media in the jukebox. HCSS will attempt to eject any media without corresponding media-label directories.PAGENUM=415 ID="BP378"If the jukebox begins ejecting media when you load HCSS, and you believe the media belongs in the jukeboxNUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Turn this parameter on, allow HCSS to finish loading, and then manually place the media back in the jukebox.Unload HCSS and the jukebox driver (HPCHGR) and determine the status of the volume and media-label directories.Correct the problem (for instance, if your volume wasn't mounted, mount it now) and reload the jukebox driver and then HCSS.RENDERAS="SECT4"ID="FM96076"Delete ThroughSetting this parameter turns off asynchronous delete requests (where response to the request is not synchronized with the actual deletion of files from media), and files are deleted from media before the delete request is completed.Normally, when you delete a file, the file is placed in a delete queue and the delete request is completed. It is not actually deleted from the media until other, higher priority requests have been completed (such as demigrations and renaming migrated files).Use this parameter if, for security purposes, you want to delete all the way through to the media and not be placed in a delete queue, even if the delete request takes longer.RENDERAS="SECT4"ID="FM18606"Minimum Time In DriveThis parameter works in conjunction with the Maximum Time in Drive parameter and the Request Idle Time parameter, and it specifies the minimum amount of time that the media remains in the drive for servicing (or waiting to service) requests for the loaded side of media.If the media is not already in the drive, part of the Minimum Time In Drive time is spent moving it into place.During the Minimum Time In Drive time, the media remains in the drive even if there are no additional requests for that side of media.PAGENUM=416 ID="BP379"RENDERAS="SECT4"ID="FM16571"Maximum Time In DriveThis parameter works in conjunction with the Minimum Time in Drive parameter and the Request Idle Time parameter, and it specifies the maximum amount of time media remains in the drive before being removed to allow a request on another side of media.However, the media will remain in the drive indefinitely if no other sides of media are needed.The Maximum Time In Drive time must be greater than the Minimum Time In Drive time.RENDERAS="SECT4"ID="FM79067"Request Idle TimeThis parameter works in conjunction with the Maximum Time in Drive parameter and the Minimum Time In Drive parameter, and it defines a short grace period to wait for additional requests for files on the media loaded in the drive.This grace period begins after the Minimum Time In Drive time has expired.If the grace period expires before a request is received, the media may be removed to service a request on another side of media.If a request is received during this grace period, the grace period begins again. This process continues until the Maximum Time In Drive time is reached.The Request Idle Time must be less than the difference of the Maximum Time In Drive and Minimum Time In Drive settings.RENDERAS="SECT3"ID="FM32485"Decision-Making ParametersHCSS periodically scans the HCSS domain directories and their subdirectories for migratable files, sorts the files by the least-recently-used (LRU) file, and builds an LRU list. The first file on the LRU list (the oldest file on the list) is the first file migrated when either the upper threshold or the preset migration time is reached.PAGENUM=417 ID="BP380"If you have a large number of files in the HCSS volume and HCSS is dominating your hard drive for an unacceptable period while building the LRU list, you can reduce the impact by doing one or both of the following.MARK=BULLETSetting or decreasing the Marked Files Limit parameter (default = no limit)Increasing the Marking Frequency parameterRENDERAS="SECT4"ID="FM73409"Marked Files LimitThis parameter is used to limit the number of files on the LRU list. When the limit is reached, HCSS stops scanning the HCSS volume for migratable files.If, for example, a file system had 10,000 migratable files with no Marked Files Limit (the setting was 0), the LRU list would have 10,000 files as candidates for migration. If the same system had a Marked Files Limit of 5000, then only the first 5000 migratable files found would go on the list. After the first 5000 files had migrated, the next list generated should include the remaining 5000 migratable files.Placing a limit on the LRU list means that the first file migrated is the least recently used of those on the list and not necessarily the least recently used file on the volume.Set this number to half of the number of existing migratable files and try it in a working environment. If your hard disk is tied up for an unacceptable period, reduce the limit.RENDERAS="SECT4"ID="FM91882"Marking FrequencyUse this to specify how often HCSS builds an LRU file list. The larger this number, the longer HCSS will rest between building LRU lists.RENDERAS="SECT4"ID="FM80502"Polling FrequencyThis parameter specifies how often you want HCSS to check if the upper threshold has been reached, indicating that it is time to migrate.RENDERAS="SECT4"ID="FM77813"Remaining Capacity Before WarningThis parameter specifies at what capacity you want to be notified that a side of media is almost full. For example, if you set the value to 20%, you will be notified when the media is 80% full.PAGENUM=418 ID="BP381"RENDERAS="SECT4"ID="FM51281"Warning FrequencyThis parameter specifies how often you want to be warned that sides of media are almost full. The warning is a broadcast message to user ADMIN.RENDERAS="SECT2"ID="FM72442"Setting Parameters Using NetWare AdministratorIDXID="w8305"BOOK="_idx" COLLECTION="nw41" TIDREF="i1649"For more information on HCSS parameters, see IDREF="FM54352""What the Parameters Do" on page 413.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXHCSS hardware and server software installedA volume created and set up for the HCSS file systemYou are logged in as ADMIN to the server on which HCSS is loadedA workstation running NetWare Administrator with the NWADMIN.INI file modified for HCSSRENDERAS="SECT3"IDXID="w8306"BOOK="_idx" COLLECTION="nw41" TIDREF="i1649"
ProcedureIDXID="w8307"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"PERFORMANCE="REQUIRED"From the MS Windows Program Manager, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"From the browser, select the HCSS volume.For information about moving around in the browser and selecting objects, choose "Help" from the menu bar.PERFORMANCE="REQUIRED"From the "Tools" menu
, select "HCSS Parameters."(Se
e IDREF="FM64036"Figure 6-15.)
PAGENUM=419 ID="BP382"LABEL="6-15" FLOAT="0"ID="FM64036"Selecting the "HCSS Parameters" OptionFILEREF="n41su64a.tif"The 
"HCSS Parameters
" dialog box appears. (See IDREF="FM60786"Figure 6-16.)LABEL="6-16" FLOAT="0"ID="FM60786"The "HCSS Parameters" Dialog BoxFILEREF="n41su62a.tif"PAGENUM=420 ID="BP383"PERFORMANCE="REQUIRED"In the "HCSS Parameters" dialog box, make changes to some or all of the parameters, as needed.See IDREF="FM37207"Table 6-2 for information on how to change individual parameter settings.Parameter settings marked with an asterisk (*) in the table are persistent (that is, the setting stays the same unless you change it). The nonpersistent parameter settings reset to the default setting every time HCSS is loaded.You can create an .NCF file to load and set the nonpersistent parameters to your desired settings. (For more information about creating an .NCF file, see IDREF="FM33588""Creating or Editing a Server Batch (.NCF) File" on page 448.)PERFORMANCE="REQUIRED"When you have finished setting the parameters, choose "OK."The new settings are activated. (Choosing "Cancel" returns you to the browser and does not save the new settings.)LABEL="6-2" PGWIDE=1 TOCENTRY="1"ID="FM37207"How to Set HCSS Parameters Using NetWare AdministratorCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="16*"COLNAME=3 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"PurposeCOLNAME=3 ROTATE="0" MOREROWS="0"Parameter Setting InformationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Disable MigrationCOLNAME=2 ROTATE="0" MOREROWS="0"Turns migration on or off.(For more information, see IDREF="FM84992""Disable Migration" on page 413.)COLNAME=3 ROTATE="0" MOREROWS="0"Select (place an X in the box) to turn off migration.Deselect (remove X from box) to reenable migration.Default setting: disabled (no X).COLNAME=1 ROTATE="0" MOREROWS="0"Migrate Unarchived FilesCOLNAME=2 ROTATE="0" MOREROWS="0"Allows migration of files that have not been backed up.(For more information, see IDREF="FM31020""Migrate Unarchived Files" on page 413.)COLNAME=3 ROTATE="0" MOREROWS="0"Select (place an X in the box) to allow migration of unarchived files.Deselect (remove X from box) to prevent migration of unarchived files.Default setting: disabled (no X).COLNAME=1 ROTATE="0" MOREROWS="0"Migrate Compressed Files OnlyCOLNAME=2 ROTATE="0" MOREROWS="0"Allows only compressed files to be migrated.(For more information, see IDREF="FM84464""Migrate Compressed Files Only" on page 413.)COLNAME=3 ROTATE="0" MOREROWS="0"Select (place an X in the box) to enable the parameter. Only compressed files, or files that can't compress, will be migrated.Deselect (remove X from box) to disable the parameter.Default setting: disabled (no X).COLNAME=1 ROTATE="0" MOREROWS="0"Upper Threshold*COLNAME=2 ROTATE="0" MOREROWS="0"Sets the upper threshold of volume space that can be used before files are migrated to media.(For more information, see IDREF="FM75215""Upper Threshold" on page 414.)COLNAME=3 ROTATE="0" MOREROWS="0"Click on the up or down arrow until you find the setting you want.Set anywhere from 1 to 100%, but higher than the lower threshold.Default setting: 80 (migration begins when the volume has 20% free volume space remaining).COLNAME=1 ROTATE="0" MOREROWS="0"Lower Threshold*COLNAME=2 ROTATE="0" MOREROWS="0"Sets the lower threshold of volume space at which files stop migrating to media.(For more information, see IDREF="FM33047""Lower Threshold" on page 414.)COLNAME=3 ROTATE="0" MOREROWS="0"Click on the up or down arrow until you find the setting you want.Set anywhere from 0 to 99%, but lower than the upper threshold.Default setting: 50 (migration stops when the volume has 50% free volume space remaining).COLNAME=1 ROTATE="0" MOREROWS="0"Migrate to Lower Threshold Time*COLNAME=2 ROTATE="0" MOREROWS="0"Sets the time when you want files to begin migrating automatically.(For more information, see IDREF="FM79293""Migrate to Lower Threshold Hour/Minute" on page 414.)COLNAME=3 ROTATE="0" MOREROWS="0"Click on the up or down arrow until you find the setting you want or select the "Off" box to disable this parameter.Select a time when file access is least likely to occur, but not to exactly midnight, unless you want to disable this parameter.Set the migration time to exactly 12:00 a.m. to disable the parameter.Default setting: 3:00 a.m. (migration begins at that time).COLNAME=1 ROTATE="0" MOREROWS="0"Delete Through to MediaCOLNAME=2 ROTATE="0" MOREROWS="0"Turns off asynchronous deletes, allowing deletion of data from the media to synchronize with the response to a requested delete(For more information, see IDREF="FM96076""Delete Through" on page 415.)COLNAME=3 ROTATE="0" MOREROWS="0"Select (place an X in the box) to enable the parameter, which allows data to be deleted from media before the delete request completes.Deselect (remove X from box) to disable the parameter.Default setting: disabled (no X).COLNAME=1 ROTATE="0" MOREROWS="0"Maximum Time In DriveCOLNAME=2 ROTATE="0" MOREROWS="0"Sets the maximum amount of time (in seconds) a side of media will remain active before changing to another side of media(For more information, see IDREF="FM16571""Maximum Time In Drive" on page 416.)COLNAME=3 ROTATE="0" MOREROWS="0"Select this parameter and type in the time (in seconds).Supported settings: 0 to 3600, but must be greater than the Minimum Time In Drive time.Can be set for 1 hour if converted into seconds (for example, 1 hour=3600.)Default setting: 30 seconds.COLNAME=1 ROTATE="0" MOREROWS="0"Minimum Time In DriveCOLNAME=2 ROTATE="0" MOREROWS="0"Sets the minimum amount of time (in seconds) a side of media will remain active before changing to another side of media.(For more information, see IDREF="FM18606""Minimum Time In Drive" on page 415.)COLNAME=3 ROTATE="0" MOREROWS="0"Select this parameter and type in the time (in seconds).Supported settings: 0 to 3600, but must be less than Maximum Time In Drive.Default setting: 20 seconds.COLNAME=1 ROTATE="0" MOREROWS="0"Request Idle TimeCOLNAME=2 ROTATE="0" MOREROWS="0"Sets the grace period during which additional requests for the media loaded in the drive will be accepted.(For more information, see IDREF="FM79067""Request Idle Time" on page 416.)COLNAME=3 ROTATE="0" MOREROWS="0"Select this parameter and type in the time (in seconds).Supported settings: Any fraction of the difference between the Maximum Time In Drive and Minimum Time In Drive times.Default setting: 2 seconds.COLNAME=1 ROTATE="0" MOREROWS="0"Remaining Capacity Before WarningCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies at what media capacity you want to be notified that a side of media is filling up.This works in conjunction with the Warning Frequency parameter to determine when you are notified.(For more information, see IDREF="FM77813""Remaining Capacity Before Warning" on page 417.)COLNAME=3 ROTATE="0" MOREROWS="0"Click on the up or down arrow until you find the setting you want.Supported settings: 0 to 100 percent.Default setting: 20.COLNAME=1 ROTATE="0" MOREROWS="0"Polling Frequency*COLNAME=2 ROTATE="0" MOREROWS="0"Specifies how often (in minutes) you want HCSS to check the thresholds you have set.(For more information, see IDREF="FM80502""Polling Frequency" on page 417.)COLNAME=3 ROTATE="0" MOREROWS="0"Set this anywhere from 1 minute to 24 days (days converted into minutes).Supported settings: 1 to 34560.Default setting: 1.COLNAME=1 ROTATE="0" MOREROWS="0"Marking Frequency*COLNAME=2 ROTATE="0" MOREROWS="0"Specifies how often (in minutes) HCSS builds a least-recently used (LRU) file list.(For more information, see IDREF="FM91882""Marking Frequency" on page 417.)COLNAME=3 ROTATE="0" MOREROWS="0"Set this anywhere from 1 minute to 24 days (days converted into minutes).Supported settings: 1 to 34560.Default setting: 30.COLNAME=1 ROTATE="0" MOREROWS="0"Warning Frequency*COLNAME=2 ROTATE="0" MOREROWS="0"Sets how often (in minutes) you want to be warned that the volume has exceeded its upper capacity threshold.(For more information, see IDREF="FM51281""Warning Frequency" on page 418.)COLNAME=3 ROTATE="0" MOREROWS="0"Set this anywhere from 1 minute to 24 days (days converted into minutes).Supported settings: 1 to 34560.Default setting: 2.COLNAME=1 ROTATE="0" MOREROWS="0"Marked Files LimitCOLNAME=2 ROTATE="0" MOREROWS="0"Limits the number of migratable files that are placed on the LRU list.(For more information, see IDREF="FM73409""Marked Files Limit" on page 417.)COLNAME=3 ROTATE="0" MOREROWS="0"Supported settings: Any number smaller than your total number of migratable files.Default setting: no limit (0).PAGENUM=425 ID="BP384"RENDERAS="SECT2"ID="FM97367"Setting Parameters at the Server ConsoleFor an overview of all the HCSS parameters, see IDREF="FM54352""What the Parameters Do" on page 413.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXHCSS hardware and server software installedA volume created and set up for the HCSS file systemYou are logged in as ADMIN to the server on which HCSS is loadedIf you are running an SFT IIITM system, you are logged in as ADMIN on the MSEngine. (See IDREF="FM26280""Using HCSS with SFT III" on page 429.)RENDERAS="SECT3"IDXID="w8308"BOOK="_idx" COLLECTION="nw41" TIDREF="i1649"
ProcedurePERFORMANCE="REQUIRED"(Optional) View the list of HCSS parameters and their current settings.At th
e server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"HCSS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"(Optional) Change any HCSS parameter, as needed, using the following syntax:
FORMAT="LINESPECIFIC"MOREINFO="NONE"HCSS [parameter] = [setting]Replace 
parameter and 
setting with a parameter name and the applicable settin
g found on IDREF="FM76586"Table 6-3.PAGENUM=426 ID="BP385"Parameters marked with an asterisk (*) in the table are persistent (that is, the setting stays the same unless you change it). The nonpersistent parameters reset to the default setting every time HCSS is loaded.You can create an .NCF file to load and set the nonpersistent parameters to your desired settings. (For more information about creating an .NCF file, see IDREF="FM33588""Creating or Editing a Server Batch (.NCF) File" on page 448.ID="FM19319"LABEL="6-3" PGWIDE=1 TOCENTRY="1"ID="FM76586" How to Set HCSS Parameters at the Server ConsoleCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="9*"COLNAME=3 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameter SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"Supported SettingsCOLNAME=3 ROTATE="0" MOREROWS="0"Purpose of ParameterVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"(no parameter)COLNAME=2 ROTATE="0" MOREROWS="0"(no setting)COLNAME=3 ROTATE="0" MOREROWS="0"Displays a list of HCSS parameters and current settings.COLNAME=1 ROTATE="0" MOREROWS="0"Eject Media Override = settingCOLNAME=2 ROTATE="0" MOREROWS="0"ON, OFF.Default: OFF.COLNAME=3 ROTATE="0" MOREROWS="0"Stops media in the jukebox from being ejected.(For more information, see IDREF="FM50022""Eject Media Override" on page 414.)COLNAME=1 ROTATE="0" MOREROWS="0"Delete Through = settingCOLNAME=2 ROTATE="0" MOREROWS="0"ON, OFF.Default: OFF.COLNAME=3 ROTATE="0" MOREROWS="0"When turned off, expedites requests for deletes.(For more information, see IDREF="FM96076""Delete Through" on page 415.)COLNAME=1 ROTATE="0" MOREROWS="0"Migrate Unarchived Files = settingCOLNAME=2 ROTATE="0" MOREROWS="0"ON, OFF.Default: OFF.COLNAME=3 ROTATE="0" MOREROWS="0"Allows migration of files that have not been backed up.(For more information, see IDREF="FM31020""Migrate Unarchived Files" on page 413.)COLNAME=1 ROTATE="0" MOREROWS="0"Migrate Compressed Files Only = settingCOLNAME=2 ROTATE="0" MOREROWS="0"ON, OFF.Default: OFF.COLNAME=3 ROTATE="0" MOREROWS="0"Allows only files that are compressed (or that can't compress) to be migrated.(For more information, see IDREF="FM84464""Migrate Compressed Files Only" on page 413.)COLNAME=1 ROTATE="0" MOREROWS="0"Maximum Time In Drive = settingCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 3600, but must be greater than the Minimum Time In Drive setting.Default: 30 (seconds).COLNAME=3 ROTATE="0" MOREROWS="0"Sets the maximum amount of time (in seconds) a side of media will remain active before changing to another side of media.(For more information, see IDREF="FM16571""Maximum Time In Drive" on page 416.)COLNAME=1 ROTATE="0" MOREROWS="0"Minimum Time In Drive = settingCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 3600, but must be less than the Maximum Time In Drive setting.Default: 20 (seconds).COLNAME=3 ROTATE="0" MOREROWS="0"Sets the minimum amount of time (in seconds) a side of media will remain active before changing to another side of media.(For more information, see IDREF="FM18606""Minimum Time In Drive" on page 415.)COLNAME=1 ROTATE="0" MOREROWS="0"Request Idle Time = settingCOLNAME=2 ROTATE="0" MOREROWS="0"Set this to a fraction of the difference between the Maximum Time In Drive and Minimum Time In Drive settings.Default: 2 (seconds).COLNAME=3 ROTATE="0" MOREROWS="0"Sets the grace period during which additional requests for the media loaded in the drive will be accepted.(For more information, see IDREF="FM79067""Request Idle Time" on page 416.)COLNAME=1 ROTATE="0" MOREROWS="0"Migration = settingCOLNAME=2 ROTATE="0" MOREROWS="0"ON, OFF.Default: ONCOLNAME=3 ROTATE="0" MOREROWS="0"Turns migration on or off.(For more information, see IDREF="FM84992""Disable Migration" on page 413.)COLNAME=1 ROTATE="0" MOREROWS="0"Upper Threshold = settingCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 100.*Default: 80 (percent).COLNAME=3 ROTATE="0" MOREROWS="0"Sets the upper threshold of volume space that can be used before files are migrated to media.(For more information, see IDREF="FM75215""Upper Threshold" on page 414.)COLNAME=1 ROTATE="0" MOREROWS="0"Lower Threshold = settingCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 99.*Default: 50 (percent).COLNAME=3 ROTATE="0" MOREROWS="0"Sets the lower threshold of volume space at which files stop migrating to media.(For more information, see IDREF="FM33047""Lower Threshold" on page 414.)COLNAME=1 ROTATE="0" MOREROWS="0"Migrate to Lower Threshold Hour = settingCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 23.*Default: 3 (3:00 a.m.).COLNAME=3 ROTATE="0" MOREROWS="0"Sets the hour when files begin migrating automatically.When set to exactly 0 (the equivalent of 12:00 a.m.), the parameter is disabled.(For more information, see IDREF="FM79293""Migrate to Lower Threshold Hour/Minute" on page 414.)COLNAME=1 ROTATE="0" MOREROWS="0"Migrate to Lower Threshold Minute = settingCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 59.*Default: 0 (12:00 a.m.).COLNAME=3 ROTATE="0" MOREROWS="0"Sets the minute of the hour when files begin migrating automatically.When set to exactly 0 (the equivalent of 12:00 a.m.), the parameter is disabled.(For more information, see IDREF="FM79293""Migrate to Lower Threshold Hour/Minute" on page 414.)COLNAME=1 ROTATE="0" MOREROWS="0"Remaining Capacity Before Warning = settingCOLNAME=2 ROTATE="0" MOREROWS="0"10 to 100.Default: 20 (percent).COLNAME=3 ROTATE="0" MOREROWS="0"Specifies when you want to be alerted about the volume's remaining capacity.(For more information, see IDREF="FM77813""Remaining Capacity Before Warning" on page 417.)COLNAME=1 ROTATE="0" MOREROWS="0"Polling Frequency = settingCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 34560.*Default: 1 (minute).COLNAME=3 ROTATE="0" MOREROWS="0"Specifies how often (in minutes) you want HCSS to check the upper and lower thresholds.(For more information, see IDREF="FM80502""Polling Frequency" on page 417.)COLNAME=1 ROTATE="0" MOREROWS="0"Marking Frequency = settingCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 34560.*Default: 30 (minutes).COLNAME=3 ROTATE="0" MOREROWS="0"Specifies how often (in minutes) a list of the least recently used directories that are managed by HCSS will be built.(For more information, see IDREF="FM91882""Marking Frequency" on page 417.)COLNAME=1 ROTATE="0" MOREROWS="0"Warning Frequency = settingCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 34560.*Default: 2 (minutes).COLNAME=3 ROTATE="0" MOREROWS="0"Specifies how often (in minutes) you will be warned that the volume has exceeded its upper capacity threshold.(For more information, see IDREF="FM51281""Warning Frequency" on page 418.)COLNAME=1 ROTATE="0" MOREROWS="0"Marked Files Limit = settingCOLNAME=2 ROTATE="0" MOREROWS="0"The total number of files flagged for migration, or any number smaller than the total.Default: 0 (no limit).COLNAME=3 ROTATE="0" MOREROWS="0"Limits the number of migratable files that are scanned for the LRU list with any setting other than zero (0).(For more information, see IDREF="FM73409""Marked Files Limit" on page 417.)PAGENUM=429 ID="BP386"RENDERAS="SECT1"ID="FM26280"Using HCSS with SFT IIIA NetWare 4.1 SFT IIITM system uses two mirrored NetWare servers to provide uninterrupted network services to clients. If one server fails, its mirrored partner automatically takes over. (For more information, see "BOOK="cncptenu" COLLECTION="nw41"System Fault Tolerance" in Concepts.)If you are using HCSS with an SFT III systemMARK=BULLETUse the following two sections---IDREF="FM58036""Loading HCSS Drivers with SFT III" and IDREF="FM64861""Loading HCSS on the MSEngine"---in place of the sections titled IDREF="FM58810""Loading HCSS Drivers" and IDREF="FM87900""Loading HCSS on the Server"in this chapter.Substitute "MSEngine prompt" for "server console prompt" where noted in this chapter.RENDERAS="SECT2"ID="FM58036"Loading HCSS Drivers with SFT IIIRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Ensure that the appropriate hardware has been installed as recommended by the hardware manufacturer.PERFORMANCE="REQUIRED"At the IOEngine console, 
IDXID="w8309"BOOK="_idx" COLLECTION="nw41" TIDREF="i2153"
load
IDXID="w8310"BOOK="_idx" COLLECTION="nw41" TIDREF="i2153"
 the applicable 
IDXID="w8311"BOOK="_idx" COLLECTION="nw41" TIDREF="i2155"
drivers
.Use the following synta
x:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD [path]controller_board_driver MOREINFO="NONE"[optionMOREINFO="NONE"] <Enter>
LOAD HPCHGR 
MOREINFO="NONE"<Enter>HPCHGR is the driver that ships with NetWare to operate the jukebox.For example, if you are using an Adaptec 1740 board
, type the following 
at the MSEngine prompt, in the order given:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD C:AHA1740 DEV_ENABLE=0MOREINFO="NONE" <Enter>
LOAD HPCHGR
MOREINFO="NONE" <Enter>The AHA driver autoloads ASPITRAN.DSK
.Some drivers require specifying an option (such as "DEV_ENABLE=0" in the previous example) to prevent the driver from taking control of the jukebox.PAGENUM=430 ID="BP387"For more information about driver options, see the hardware manufacturer's documentation.For more information about loading drivers, se
e IDREF="FM93561""Loading Disk Drivers" on page 538.PERFORMANCE="REQUIRED"Type the following at the MSEngine promp
t:FORMAT="LINESPECIFIC"MOREINFO="NONE"SCAN FOR NEW DEVICES MOREINFO="NONE"<Enter>The 
SCAN FOR NEW DEVICES command checks fo
r IDXID="w8312"BOOK="_idx" COLLECTION="nw41" TIDREF="i1638"
peripheral devices added since the 
IDXID="w8313"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
server was last booted, and then registers the added devices with the operating system.PERFORMANCE="REQUIRED"(Optional) Verify that the device was successfully loaded
.At the MSEngine prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LIST DEVICES MOREINFO="NONE"<Enter>A list is displayed of all activ
e IDXID="w8314"BOOK="_idx" COLLECTION="nw41" TIDREF="i1638"
peripheral devices on your server, including the 

magneto-optical drives in the jukebo
x.PERFORMANCE="REQUIRED"Return to the section titled IDREF="FM43676""Creating an HCSS Volume" on page 394.RENDERAS="SECT2"ID="FM64861"Loading HCSS on the MSEngineLoad the HCSS loadable modules.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXHCSS volume created and mountedApplicable drivers loaded at the IOEngine consoleRENDERAS="SECT3"IDXID="w8315"BOOK="_idx" COLLECTION="nw41" TIDREF="i1670"
ProcedureIDXID="w8316"BOOK="_idx" COLLECTION="nw41" TIDREF="i2155"PERFORMANCE="REQUIRED"At the MSEngine prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD HCSS MOREINFO="NONE"<Enter>The HCSS module (as well as several othe
r loadable modules) autoloads RTDM.NLM
 (a module that enables migration).
PAGENUM=431 ID="BP388"When HCSS is loaded, it takes inventory of the media in the jukebox and verifies a correlation between the media-label directories (directories created when importing media) and the media. Any noncorresponding media begins ejecting.When HCSS has completed the inventory and verification, the message "HCSS is up and running" appears on the MSEngine console and is broadcast to user ADMI
N. (The message doesn't appear when HCSS is loaded for the first time.)When HCSS is loaded for the first time, it will not be up and running until you create the volume, domain directory, and media-label directories in that order. (For information on the required flow of tasks, see IDREF="FM39726""Overview of HCSS Setup and Management" on page 390.)PERFORMANCE="REQUIRED"(Conditional) If the jukebox ejected media when you loaded HCSS, remove the media and, at the MSEngine prompt, type the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MEDIA REMOVED MOREINFO="NONE"<Enter>Enter this command for each piece of media that is ejected.You can prevent more media from being ejected by typing the following command at the MSEngine prompt: HCSS Eject Media Override=On. See IDREF="FM97367""Setting Parameters at the Server Console" on page 425.PERFORMANCE="REQUIRED"(Optional) Add the commands to load the drivers and loadable modules to the MSEngine'
s MSAUT
O.NCF file.You can load the drivers and modules automatically every time 
the MSEngine is booted by adding the commands to your MSA
UTO.NCF file.For more information about adding commands to the .NCF file, se
e IDREF="FM33588""Creating or Editing a Server Batch (.NCF) File" on page 448.Two .NCF files are included in the HCSS module for unloading and reloading HCSS when needed. Run HUNLOAD.NCF if it becomes necessary to unload HCSS. Run HRELOAD.NCF to reload (reinitialize and set up) HCSS after a fatal error has occurred.If you are running SFT III and the server to which the jukebox is attached fails, you must run HRELOAD after the mirrored servers resynchronize.PERFORMANCE="REQUIRED"At the workstation you plan to use to manage HCSS, edit the NWADMIN.INI file as described i
n IDREF="FM79397""Setting Up a Workstation to Manage HCSS" on page 396.LABEL="7"PAGENUM=433 ID="BP389"ID="FM63100"Maintaining the NetWare ServerThis chapter contains procedures designed to help you manage, optimize, and protect NetWare® servers. Procedures are grouped into the following sections:MARK=BULLETCommon Management Tasks---including basic procedures such as downing a server and creating server batch filesManaging Server Connections---including procedures to monitor connection problems and manage communications buffersMonitoring and Optimizing the Server---including ways to manage memory, improve performance, and monitor errorsMaintaining Volumes---including mounting and dismounting, creating, deleting, and renaming volumesManaging Server Hard Disks---including instructions for file compression, adding new disks, and mirroring or duplexing hard disksDisaster Prevention and Recovery---including procedures to prevent packet forgery, establish UPS monitoring, and protect the system's memoryManaging Network Time Synchronization---including how to configure time synchronization for large networksUsing Remote Console to Manage a Server---including procedures for executing remote console sessions over both a direct connection and a modemAdministering Accounting---including instructions for setting up accounting, calculating charge rates, and viewing accounting totalsPAGENUM=434 ID="BP390"RENDERAS="SECT1"Common Management TasksThis section describes typical network supervisor tasks and explains ways you can change the server environment you created during installation of the NetWare 4TM operating system.RENDERAS="SECT2"ID="FM96671"Sending Console Messages to WorkstationsIDXID="w8317"BOOK="_idx" COLLECTION="nw41" TIDREF="i2418"IDXID="w8318"BOOK="_idx" COLLECTION="nw41" TIDREF="i4020"
To send a message from the server console to all workstations or to a single user, use the SEND command.You can still use the BROADCAST command, as you may have done with previous versions of NetWare. The functionality is exactly the same as that of the SEND command.Unlike the client SEND command, groupname is not a valid parameter at the server.RENDERAS="SECT3"Sending a Message to a Specific UserRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Make sure you are at the server console prompt (:).If another screen is displayed (such as MONITOR), press 
MOREINFO="NONE"<Alt>+<Esc> to return to the console prompt.PERFORMANCE="REQUIRED"Type a message, or a series of messages, using the SEND command with the "TO" option.Messages can be up to 55 characters.For information on SEND command syntax, se
e "BOOK="utlrfenu" COLLECTION="nw41"SEND" in Utilities Reference.PERFORMANCE="REQUIRED"Enter the username or connection number in the SEND command.To determine the username or connection number of a user you want to send a message to, 
IDXID="w8319"BOOK="_idx" COLLECTION="nw41" TIDREF="i2506"
use the "Connection Information" screen in MONITOR
.PAGENUM=435 ID="BP391"The form of the user's name depends on whether the user is logged in as a NetWare Directory Service
sTM objec
t or as a bindery object, and on where the master replica database is stored.For example, there are three ways you could send a message to JSMITH, depending on the way the way the name appears in "Connection Information" in MONITOR.
MARK=BULLETIf the name appears as "JSMITH," type the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"SEND "REMEMBER THE MEETING." TO JSMITH MOREINFO="NONE"<Enter>If the name appears as "CN=JSMITH.OU=SALES.O=ABC_INC," type the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"SEND "REMEMBER THE MEETING." TO CN=JSMITH.OU=SALES.O=ABC_INC MOREINFO="NONE"<Enter>If JSMITH's connection number in the "Connection Information" display is "2," type the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"SEND "REMEMBER THE MEETING." TO 2 MOREINFO="NONE"<Enter>RENDERAS="SECT3"Sending a Message to All WorkstationsRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Make sure you are at the server console prompt (:).PERFORMANCE="REQUIRED"Type a message, or a series of messages, using the SEND command.Messages can be up to 55 characters.For example, to send a message to all workstations
, type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SEND "SERVER GOING DOWN" MOREINFO="NONE"<Enter>The message is sent to all workstations.
PAGENUM=436 ID="BP392"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the SEND utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"SEND" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Receiving and clearing messages at the workstationCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference " in NetWare Client for DOS and MS Windows Technical Reference or "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User GuideRENDERAS="SECT2"ID="FM10818"Bringing Down a ServerUse the IDXID="w8320"BOOK="_idx" COLLECTION="nw41" TIDREF="i1213"
DOWN utility at the server console to ensure data integrity before turning off power to the server.DOWN ensures data integrity by writing all cache buffers to disk, closing all files, and updating the appropriate Directory Entry Tables and File Allocation Tables.Bringing down a server during a remote console session terminates the session.If you bring down the server but do not exit to DOS, the server is still connected to the network, and it still receives packets. You can continue to execute console commands, such as TRACK ON and TRACK OFF, that deal with packets.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, use SEND to inform all users that they should close all files and log out.For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SEND "Please close files and log out from server servername." MOREINFO="NONE"<Enter>
SEND "Going down in 5 minutes."
MOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Bring down the server by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>
PAGENUM=437 ID="BP393"If files are still open, the console displays the files that are open, the user who opened them, and the workstation connection number.After executing the DOWN command, you may need to go to the workstation with open files and close them for the user if the workstation is not attended.You may now either return to DOS or 
IDXID="w8321"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
restart the server.PERFORMANCE="REQUIRED"(Optional) To return to 
IDXID="w8322"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
DOS, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8323"BOOK="_idx" COLLECTION="nw41" TIDREF="i1382"
EXIT MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"(Optional) To restart the server without returning to DOS, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8324"BOOK="_idx" COLLECTION="nw41" TIDREF="i3824"
RESTART SERVER MOREINFO="NONE"<Enter>RENDERAS="SECT2"Booting the Server with the EXIT CommandIDXID="w8325"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"IDXID="w8326"BOOK="_idx" COLLECTION="nw41" TIDREF="i3697"
The following procedure explains how to use the EXIT command to reboot the server. This procedure allows users who are using RCONSOLE to reboot the NetWare server remotely.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXCommands in the server AUTOEXEC.BAT to execute SERVER.EXE. (If these commands are not in the AUTOEXEC.BAT file, this procedure reboots the computer and displays the DOS prompt, but does not load the NetWare server software.)RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, remove DOS from memory by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"REMOVE DOSMOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Bring down the server by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>
PAGENUM=438 ID="BP394"PERFORMANCE="REQUIRED"Reboot the server by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"EXIT MOREINFO="NONE"<Enter>This
 reboots the computer, executes the SERVER.EXE file, and displays the server console prompt.RENDERAS="SECT2"IDXID="w8327"BOOK="_idx" COLLECTION="nw41" TIDREF="i2158"
Loading a NetWare Loadable ModuleIDXID="w8328"BOOK="_idx" COLLECTION="nw41" TIDREF="i2760"This procedure explains how to load a NetWare Loadable ModuleTM program (NLM) from the server console.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXDetermine the memory protection domain you want the NLMTM to run in. IDXID="w8329"BOOK="_idx" COLLECTION="nw41" TIDREF="i2760"
For a list of NetWare NLM programs and the domains they can run in, see Appendix C, "BOOK="utlrfenu" COLLECTION="nw41"Memory Domains for NLMs and Autoloaded NLMs," of Utilities Reference.You do not need to set up a memory domain if you want the NLM to run in the OS domain. If you want the NLM to run in a memory domain outside of the OS domain, see IDREF="FM98294""Protecting the Operating System's Memory" on page 560.If you are running a message file for the NLM in a language other than English, make sure the language is specified properly. See IDREF="FM37370""Specifying a Language for an NLM" on page 455.If the NLM is not in the SYS:SYSTEM directory, either move the NLM to the SYS:SYSTEM directory or add a server search path to the NLM. Otherwise, you must enter the path for the NLM when you execute the LOAD command. See IDREF="FM50447""Viewing and Adding Server Search Paths" on page 443.RENDERAS="SECT3"IDXID="w8330"BOOK="_idx" COLLECTION="nw41" TIDREF="i2158"
ProcedurePERFORMANCE="REQUIRED"At the server console prompt, enter the LOAD command.MARK=BULLETUse this format to load an NLM residing in SYS:SYSTEM and running in the OS domain:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NLM MOREINFO="NONE"<Enter>
PAGENUM=439 ID="BP395"Use this format to load an NLM with a specified memory domain:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD NLM DOMAIN=domain_name MOREINFO="NONE"<Enter>Use this format to load an NLM located on the A: drive:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD A:NLM MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"If you want the NLM to be loaded whenever the server boots, add the LOAD command to the AUTOEXEC.NCF file.RENDERAS="SECT3"Additional InformationMOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the LOAD utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"LOAD" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Loading NLM programs in different domainsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM98294""Protecting the Operating System's Memory" on page 560COLNAME=1 ROTATE="0" MOREROWS="0"Memory protectionCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Memory protection" in ConceptsRENDERAS="SECT2"ID="FM63159"Loading and Binding LAN DriversIDXID="w8331"BOOK="_idx" COLLECTION="nw41" TIDREF="i2035"After you add a network board to your NetWare server, you must load and bind the corresponding LAN driver. Loading a LAN driver establishes a network connection (if the server is physically connected to the network cabling). Binding a LAN driver links a network protocol to the driver and the network board.IDXID="w8332"BOOK="_idx" COLLECTION="nw41" TIDREF="i2153"
The LAN driver you choose depends on the cabling system and the network board you are using. Refer to IDREF="FM26918"Table 7-1 to determine which driver to load.LABEL="7-1" PGWIDE=1 TOCENTRY="1"IDXID="w8333"BOOK="_idx" COLLECTION="nw41" TIDREF="i2035"ID="FM26918" NetWare LAN DriversCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="14*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8334"BOOK="_idx" COLLECTION="nw41" TIDREF="i282"
ARCnet*COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8335"BOOK="_idx" COLLECTION="nw41" TIDREF="i3934"
RX-NetTMRX-Net IIRX-Net/2TMCOLNAME=3 ROTATE="0" MOREROWS="0"TRXNET.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8336"BOOK="_idx" COLLECTION="nw41" TIDREF="i1350"
EthernetCOLNAME=2 ROTATE="0" MOREROWS="0"NE/2TMNE/2TCOLNAME=3 ROTATE="0" MOREROWS="0"NE2.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE/2-32TMCOLNAME=3 ROTATE="0" MOREROWS="0"NE2_32.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE1000TM - ASSY 950-054401NE1000 - ASSY 810-160-001COLNAME=3 ROTATE="0" MOREROWS="0"NE1000.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE2000TM- ASSY 810-149NE2000T - ASSY 810-000220COLNAME=3 ROTATE="0" MOREROWS="0"NE2000.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE2100TM - ASSY 810-000209COLNAME=3 ROTATE="0" MOREROWS="0"NE2100.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE2100 - ASSY 810-000214(twisted-pair version of NE2100)COLNAME=3 ROTATE="0" MOREROWS="0"NE1500T.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE3200TMCOLNAME=3 ROTATE="0" MOREROWS="0"NE3200.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE32HUBTMCOLNAME=3 ROTATE="0" MOREROWS="0"NE32HUB.LANCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8337"BOOK="_idx" COLLECTION="nw41" TIDREF="i1741"
IBM* PC networkCOLNAME=2 ROTATE="0" MOREROWS="0"PCN2 broadbandPCN2/A broadbandPCN basebandPCNA basebandCOLNAME=3 ROTATE="0" MOREROWS="0"PCN2L.LANCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8338"BOOK="_idx" COLLECTION="nw41" TIDREF="i4525"
Token ringCOLNAME=2 ROTATE="0" MOREROWS="0"NTR2000COLNAME=3 ROTATE="0" MOREROWS="0"NTR2000.LANPAGENUM=441 ID="BP396"To load and bind LAN drivers, you can useMARK=BULLETThe INETCFG NLMUse INETCFG to load LAN drivers and bind them to any supported protocol. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.The LOAD and BIND commandsIf you know the parameters required by the communication protocol, you can use the LOAD and BIND commands to load and bind LAN drivers at the command line. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"LOAD" and "BOOK="utlrfenu" COLLECTION="nw41"BIND" in Utilities Reference.The INSTALL NLMYou can use INSTALL to load LAN drivers and bind them to the default protocol IPX
TM.IDXID="w8339"BOOK="_idx" COLLECTION="nw41" TIDREF="i465"
The following procedure explains how to use INSTALL to load a LAN driver and bind it to IDXID="w8340"BOOK="_idx" COLLECTION="nw41" TIDREF="i1953"
 IPX. IDXID="w8341"BOOK="_idx" COLLECTION="nw41" TIDREF="i3613"
To bind a LAN driver to another protocol, use INETCFG.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8342"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Driver Options" from the "Installation Option
s" menu.PERFORMANCE="REQUIRED"Select "Configure Network Drivers" from the "Driver Options" menu.PERFORMANCE="REQUIRED"Choose "Select an Additional Driver" from the "Additional Driver Actions" menu.The system displays a list of available drivers.PERFORMANCE="REQUIRED"Choose the driver you want to load or, if the driver is not on the list, press MOREINFO="NONE"<InsMOREINFO="NONE"ertMOREINFO="NONE">.If you press MOREINFO="NONE"<InsMOREINFO="NONE"ertMOREINFO="NONE"> to load an unlisted driver, follow the screen prompts. If you select a listed driver, continue with the following steps.
PAGENUM=442 ID="BP397"For some drivers, a message may appear indicating that the driver must be loaded manually (at the console prompt). To load these drivers, follow the screen prompts or press MOREINFO="NONE"<F1> for more information.PERFORMANCE="REQUIRED"Choose "Select/Modify Driver Parameters."The system displays a window where you can set values for driver parameters. If you selected an NE2000 driver, the system also displays a window containing protocol options. The cursor is active in the protocol options window, if it is displayed.PERFORMANCE="REQUIRED"If the window containing protocol choices is displayed, accept the default IPX protocol, by pressing th
e dow
narrow until the cursor moves to the parameter window
.The protocol choices window also lists TCP/IP and AppleTalk. These are nonrouting protocols which you may select instead of IPX. To configure standard TCP/IP, AppleTalk, or other non-IPX protocols, use INETCFG.PERFORMANCE="REQUIRED"Enter parameter values in the fields on the parameter window.Press MOREINFO="NONE"<F1> for help if necessary.In some cases, the system displays a pop-up list of values for the field from which you select the desired value. In other cases, you must type in a value and press MOREINFO="NONE"<Enter> to move to the next field.PERFORMANCE="REQUIRED"(Optional) To specify a frame type other than 802.2 for an Ethernet driver, press 
MOREINFO="NONE"<F3> to display a selection list of frame types. Select the frame type from the list and press
MOREINFO="NONE" <Enter>.IDXID="w8343"BOOK="_idx" COLLECTION="nw41" TIDREF="i1350"
Ethernet drivers fo
r NetWare 4 default to the Ethernet 
IDXID="w8344"BOOK="_idx" COLLECTION="nw41" TIDREF="i1570"
802.2 frame type. If you want compatibility with earlier versions of NetWare, load the LAN driver with frame type 802.3, as well.PERFORMANCE="REQUIRED"When finished, press 
MOREINFO="NONE"<F10> to save the values and exit the window.The system loads the LAN driver and then displays a 
confirmation windo
w containing the command line to bind IPX to the LAN driver with the specified frame type.At this point, you can either 
confirm bind
ing 
of the protocol 
with the specified frame type or change the frame type.PERFORMANCE="REQUIRED"To bind the protocol, press 
MOREINFO="NONE"<Enter>. T
o display the command line with a different frame type, press 
MOREINFO="NONE"<F3>.
PAGENUM=443 ID="BP398"Each time you press 
MOREINFO="NONE"<F3>, the system displa
ys the command lin
e with another of the available frame types
. Press MOREINFO="NONE"<F3> until the desired frame type is displayed.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"When the frame type you want is displayed, press 
MOREINFO="NONE"<Enter> to bind the LAN driver.INSTALL automatically places the LOAD and BIND commands in the AUTOEXEC.NCF file.RENDERAS="SECT3"ID="FM66573"Additional Information.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AppleTalk protocolCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"AppleTalk protocols" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Frame typesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Ethernet configuration" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"IPX protocolCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"IPX" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"TCP/IP protocolCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"TCP/IP" in ConceptsRENDERAS="SECT2"ID="FM50447"Viewing and Adding Server Search PathsIDXID="w8345"BOOK="_idx" COLLECTION="nw41" TIDREF="i3981"Adding a server search path allows you to run 
server utilities and NetWare Loadable Module (NLM) programs and to access server 
batch files (.NCF files) without specifying the full path to them. Whenever you run a utility or NLM from the server, the server searches for the utility in the current directory and also in the path you specified as a server search path.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"To view current search paths, type the following at the server console prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8346"BOOK="_idx" COLLECTION="nw41" TIDREF="i3982"
SEARCH MOREINFO="NONE"<Enter>The system displays the current search paths in a numbered list. For example,
FORMAT="LINESPECIFIC"MOREINFO="NONE"Search 1: [Server path] SYS:SYSTEMSearch 2: [Server path] A:Search 3: [Server path] VOL1:NCFPAGENUM=444 ID="BP399"PERFORMANCE="REQUIRED"To add a search path, use one of the following formats:
MARK=BULLETAdd a directory or drive as a search path by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"SEARCH ADD path MOREINFO="NONE"<Enter>For example, this command specifies a search path to VOL1:NCFFORMAT="LINESPECIFIC"MOREINFO="NONE"SEARCH ADD VOL1:NCF MOREINFO="NONE"<Enter>This command specifies a search path to drive A:FORMAT="LINESPECIFIC"MOREINFO="NONE"SEARCH ADD A: MOREINFO="NONE"<Enter>Add a search path in a particular place in the numbered list of search paths by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"SEARCH ADD number path MOREINFO="NONE"<Enter>For example, the following command both creates the search path to drive A: and places the path in the second position in the numbered list of search paths.FORMAT="LINESPECIFIC"MOREINFO="NONE"SEARCH ADD 2 A:MOREINFO="NONE" <Enter>The search path that was previously number 2 becomes number 3, and so on.PERFORMANCE="REQUIRED"To delete a search path, use the following format:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SEARCH DEL number MOREINFO="NONE"<Enter>Replace 
number with the number of the search path you want to delete
.For more information, see "BOOK="utlrfenu" COLLECTION="nw41"SEARCH" in Utilities Reference.PAGENUM=445 ID="BP400"RENDERAS="SECT2"Installing, Uninstalling, and Configuring a Server ProductIDXID="w8347"BOOK="_idx" COLLECTION="nw41" TIDREF="i4645"IDXID="w8348"BOOK="_idx" COLLECTION="nw41" TIDREF="i4056"The IDXID="w8349"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL NLM allows you to install, uninstall, and configure other NetWare products such as name space modules and Storage Management ServicesTM (SMS).If you have questions during the installation or configuration of a product, refer to the documentation that came with the product.Some products may not have configuration or uninstall options. A message explaining this is displayed if you try to perform unsupported operations.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALLMOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Choose "Product Options" from the "Installation Options" menu.PERFORMANCE="REQUIRED"Choose "View/Configure/Remove an Installed Product" from the "Other Installation Actions" menu.The 
"Currently Installed Products
" list appears. If no products are currently installed, the list is empty.PERFORMANCE="REQUIRED"Do one of the following:
MARK=BULLETTo install a product, press MOREINFO="NONE"<Insert> and follow the prompts.To uninstall a product, select the product from the list and press MOREINFO="NONE"<Delete>.To set IDXID="w8350"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"
configuration options for a product, select the product from the list and follow the prompts.RENDERAS="SECT2"Copying NetWare FilesIDXID="w8351"BOOK="_idx" COLLECTION="nw41" TIDREF="i1487"IDXID="w8352"BOOK="_idx" COLLECTION="nw41" TIDREF="i845"IDXID="w8353"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
When you do a simplified NetWare install, the system installs some, but not all, of the NetWare files. If desired, you can copy the rest of the installation files later by using the "Copy Files" option of the INSTALL NLM. Follow this procedure.PAGENUM=446 ID="BP401"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXNetWare 4 installation CD-ROMRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "Copy Files Option" from the "Installation Options" menu
.The system displays a box containing the default source path from which the files will be copied.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to accept the default path, or press 
MOREINFO="NONE"<F3>to specify a different path.If you press MOREINFO="NONE"<F3>, the system displays a prompt with the current source path. Backspace to delete the path and type in the new path. Press
MOREINFO="NONE" <Enter>.The syste
m display
s the prompt "Specify a server boot path (where SERVER.EXE will be):" This is the destination directory---the location to which the files will be copied. This directory must be the boot directory---the directory where SERVER.EXE is located. The default path is C:\NWSERVER.PERFORMANCE="REQUIRED"Accept the default or type in a new path if your bootup directory is not C:\NWSERVER.The system displays a list of file groups. An X next to each group means the group is preselected.PERFORMANCE="REQUIRED"Delete the X next to any group(s) you 
do not want to copy.T
o delete the X, use the arrow keys to move the cursor to the desired group a
nd press 
MOREINFO="NONE"<Enter>. The X
 next to the box disappears.To reselect a grou
p, move the cursor to the group and press MOREINFO="NONE"<Enter> again.PERFORMANCE="REQUIRED"When finished selecting groups, press 
MOREINFO="NONE"<F10>.The system copies the files.
PAGENUM=447 ID="BP402"RENDERAS="SECT2"IDXID="w8354"BOOK="_idx" COLLECTION="nw41" TIDREF="i1420"
Extracting NetWare Files from the Installation CD-ROMIDXID="w8355"BOOK="_idx" COLLECTION="nw41" TIDREF="i2739"IDXID="w8356"BOOK="_idx" COLLECTION="nw41" TIDREF="i1817"IDXID="w8357"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"
If a IDXID="w8358"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"
NetWare IDXID="w8359"BOOK="_idx" COLLECTION="nw41" TIDREF="i4379"
system file is accidentally deleted and purged from the network, you can use the IDXID="w8360"BOOK="_idx" COLLECTION="nw41" TIDREF="i3041"
NWXTRACT utility to extract the file from the NetWare 4.1 IDXID="w8361"BOOK="_idx" COLLECTION="nw41" TIDREF="i845"
installation CD-ROM or diskettes.NWXTRACT copies selected files from the installation CD-ROM or diskettes to their default locations on the network or to a user-specified destination.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterRights to copy files to the destination directoryThe NetWare 4.1 installation CD-ROM or diskettesName space support, if extracting Macintosh*, UNIX*, or OS/2* filesRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"If using diskettes, load the diskette containing the file or files you want to extract.PERFORMANCE="REQUIRED"To extract a file or group of files, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWXTRACT path filename | groupname [destination] [/option] MOREINFO="NONE"<Enter>Replace 
drive with the drive letter for the installation CD-ROM or the diskette.Replace 
filename with the name of the file you want to extract from the CD-ROM or diskette. Or, replace 
groupname with the name of the group of files you want to extract.Replace 
destination with the destination path for the extracted files, if different from the default destination.
PAGENUM=448 ID="BP403"Replace 
option with any of the following:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"/S=server | server objectCOLNAME=2 ROTATE="0" MOREROWS="0"Copies extracted files to their default location on the specified server.COLNAME=1 ROTATE="0" MOREROWS="0"/T=typeCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the type of file to be extracted. Valid types are DOS, MAC, OS2, SER (server), UNX, and WIN.COLNAME=1 ROTATE="0" MOREROWS="0"/?COLNAME=2 ROTATE="0" MOREROWS="0"Displays online help.PERFORMANCE="REQUIRED"To make sure the extracted system files are flagged Read Only, change to the destination directory and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG filename RO MOREINFO="NONE"<Enter>See "
BOOK="utlrfenu" COLLECTION="nw41"FLAG" in 
Utilities Reference for information on flagging files.RENDERAS="SECT2"ID="FM33588"Creating or Editing a Server Batch (.NCF) FileIDXID="w8362"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"When a server is booted, SERVER.EXE executes two files:MARK=BULLETIDXID="w8363"BOOK="_idx" COLLECTION="nw41" TIDREF="i4265"
STARTUP.NCF---This file loads the server's disk drivers and some SET parameters.IDXID="w8364"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"
AUTOEXEC.NCF---This file stores the server name and IPX internal IDXID="w8365"BOOK="_idx" COLLECTION="nw41" TIDREF="i2874"
network number, loads the LAN drivers and settings for the network boards, binds the protocol to the installed drivers, and loads other NLM programs.The following procedure explains how to edit either of these files.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8366"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "NCF Files Options" from the "Installation Options" menu.
PAGENUM=449 ID="BP404"The system displays a menu containing options to create or edit both the STARTUP.NCF and AUTOEXEC.NCF files.PERFORMANCE="REQUIRED"Select the desired option and press 
MOREINFO="NONE"<Enter>.If you select an option to edit one of the files, the selected file appears in a window.If you select an option to create one of the files, the system displays the existing file in one window and a new file with default entries in another window, so you can compare the two.The default entries include only essential contents of the file and reflect the current system setup. For example, the default entries include time zone information and load and bind commands for currently installed LAN drivers. The new file does not include custom configuration settings you may have in the original file.The cursor is active in the new file. Press 
MOREINFO="NONE"<Tab> to toggle between the two files.PERFORMANCE="REQUIRED"Edit the new or existing file as necessary.Editing and navigation keystrokes are listed at the bottom of the screen. For additional help, pressMOREINFO="NONE" <F1>.PERFORMANCE="REQUIRED"When finished, save the file by pressing 
MOREINFO="NONE"<F10> and selecting "Yes" when prompted. To exit without saving, press 
MOREINFO="NONE"<Alt>+<F10>.Each time you edit the AUTOEXEC.NCF file or the STARTUP.NCF file, NetWare saves the previous version as AUTONCF.OLD or STARTNCF.OLD.Changes to the file take effect once you reboot the server. RENDERAS="SECT2"ID="FM88816"Editing Text Files from the Server ConsoleIDXID="w8367"BOOK="_idx" COLLECTION="nw41" TIDREF="i4470"IDXID="w8368"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"
Although you usually edit server files from a workstation, sometimes it is more convenient to edit text files from the server console.The following procedure explains how to use the EDIT NLM to edit files. You can use EDIT to edit DOS text files on either DOS or NetWare partitions.PAGENUM=450 ID="BP405"EDIT allows you to edit only IDXID="w8369"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
DOS text files. Each time you save the file, you can increase the file size by up to 4 KB.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8370"BOOK="_idx" COLLECTION="nw41" TIDREF="i1287"
EDIT pathname MOREINFO="NONE"<Enter>If you do not specify a file pathname, the system prompts you to enter the pathname
. Type the pathname of the file to be edited and press 
MOREINFO="NONE"<Enter>.The file must be located on a mounted volume or a local drive of the server.If you enter only the fil
ename, the system assumes a default directory location of SYS:SYSTEM.If the file exists, it is displayed on the screen, ready for editing.If the file does not exist, EDIT displays a prompt that asks whether the file should be created. Respond as described i
n IDREF="FM61311"Step 2.PERFORMANCE="REQUIRED"ID="FM61311"Choose "Yes" to create the new file or "No" to redisplay the pathname prompt.A blank screen appears if this is a new file.PERFORMANCE="REQUIRED"Edit the file as needed.The keys used to edit text are described i
n IDREF="FM80141"Table 7-2.IDXID="w8371"BOOK="_idx" COLLECTION="nw41" TIDREF="i1287"LABEL="7-2" PGWIDE=0 TOCENTRY="1"ID="FM80141" Editing Keys Available in the EDIT NLMCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"KeyCOLNAME=2 ROTATE="0" MOREROWS="0"FunctionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Arrow keysCOLNAME=2 ROTATE="0" MOREROWS="0"Move up/down one line or left/right one character.COLNAME=1 ROTATE="0" MOREROWS="0"BackspaceCOLNAME=2 ROTATE="0" MOREROWS="0"Delete character to left of cursor.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Ctrl>+<PageUp>COLNAME=2 ROTATE="0" MOREROWS="0"Move to beginning of document.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Ctrl>+<PageDown>COLNAME=2 ROTATE="0" MOREROWS="0"Move to end of document.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Delete>COLNAME=2 ROTATE="0" MOREROWS="0"Delete the character at the cursor location or delete blocked text.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<End>COLNAME=2 ROTATE="0" MOREROWS="0"Move to end of line.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Esc>COLNAME=2 ROTATE="0" MOREROWS="0"Exit the file. You are prompted to save any changes.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<F5>COLNAME=2 ROTATE="0" MOREROWS="0"Highlight (block) text for copying or deleting. Toggles highlighting on and off.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<F6>COLNAME=2 ROTATE="0" MOREROWS="0"Copy highlighted (blocked) text to a buffer.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Home>COLNAME=2 ROTATE="0" MOREROWS="0"Move cursor to beginning of line.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Insert>COLNAME=2 ROTATE="0" MOREROWS="0"Insert text from buffer.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<PMOREINFO="NONE"aMOREINFO="NONE"gMOREINFO="NONE"eMOREINFO="NONE"Up>COLNAME=2 ROTATE="0" MOREROWS="0"Move up one pageCOLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<PMOREINFO="NONE"aMOREINFO="NONE"gMOREINFO="NONE"eMOREINFO="NONE"DMOREINFO="NONE"owMOREINFO="NONE"n>COLNAME=2 ROTATE="0" MOREROWS="0"Move down one page.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Tab>COLNAME=2 ROTATE="0" MOREROWS="0"Move cursor four spaces to the right.PAGENUM=451 ID="BP406"PERFORMANCE="REQUIRED"When finished editing, press 
MOREINFO="NONE"<Esc>. Select "Yes" to save the file or "No" to exit the file without saving changes.The system redisplays the pathname prompt.PERFORMANCE="REQUIRED"To edit another file, enter the file pathname. To redisplay the console prompt, press 
MOREINFO="NONE"<Esc>.RENDERAS="SECT2"ID="FM68389"Setting a Server's LanguageThe NetWare 4.1 operating system and its NLM programs and utilities use the language the server was installed in, unless you specify otherwise. The server languages supported for the initial release of NetWare 4.1 are French, Italian, German, Spanish, and English.This section explains how to specify a new server language. The first step is to copy the new language files to the server. The second step is to set the server to the new language.Subsequent sections explain how to change the language for the NLM programs you load on the server and how to change the keyboard type.PAGENUM=452 ID="BP407"RENDERAS="SECT3"ID="FM11615"Copying the Language Files to the ServerIDXID="w8372"BOOK="_idx" COLLECTION="nw41" TIDREF="i2046"IDXID="w8373"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"Before you can change the server language, you must copy the language files to the server from the installation CD-ROM or another server. Follow this procedure to copy the files.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXInstallation CD-ROM or access to another NetWare server containing the language filesRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Installation Options" menu, select "Product Options."PERFORMANCE="REQUIRED"From the "Other Installation Actions" menu, select "Choose an Item or Product Listed Above."PERFORMANCE="REQUIRED"From the "Other Installation Items/Products" menu, select "Install an Additional Server Language.
"The syste
m displays a box containin
g the path from which you last installed files. In most cases, this is the path to the language files for the current language. For example, if you last installed NetWare files in English, this is the path to the English files. You should accept the path to th
e current language file
s so that help and system messages 
are displayed in the current languag
e during the install procedure. If
, for some reason
, the path is not to the current language files, then you should ente
r the path to thecurrent language files. See the next step.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to accept th
e displayed pat
h, or pressMOREINFO="NONE" <F3> and type in the correct path to the current language files.The path to the current language files has this syntax:SERVER MOREINFO="NONE"| CDMOREINFO="NONE":\NW410\INSTALLMOREINFO="NONE"\current_languagePAGENUM=453 ID="BP408"If you are installing the files from another server, the system may prompt you for a username and password for that server. Follow the prompts.The system displays a windo
w list
ing 
groups of language files.PERFORMANCE="REQUIRED"Use the arrow keys to move the cursor to the language you want to install and press 
MOREINFO="NONE"<Enter>.The system marks the selected language with an 
"X." You can specify several languages, if desired
.To deselect a language, move the cursor to the language and press
MOREINFO="NONE" <Enter> again.PERFORMANCE="REQUIRED"When 
you have finished selecting languages, press 
MOREINFO="NONE"<F10>.The system copies the selected language files.After the files are copied, you can change the server language at any time.
 See the next section, IDREF="FM81386""Changing the Server's Language."RENDERAS="SECT3"ID="FM81386"Changing the Server's LanguageIDXID="w8374"BOOK="_idx" COLLECTION="nw41" TIDREF="i2046"IDXID="w8375"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"Follow this procedure to change the server language.This procedure requires you to reboot the NetWare server because you set the server language when executing SERVER.EXE. You may want to perform this procedure after business hours.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXLanguage files copied to the server. (See IDREF="FM11615""Copying the Language Files to the Server" on page 452.)RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Installation Options" menu, select "Product Options."
PAGENUM=454 ID="BP409"PERFORMANCE="REQUIRED"From the "Other Installation Actions" menu, select "Choose an Item or Product Listed Above."PERFORMANCE="REQUIRED"From the "Other Installation Items/Products" menu, select "Change Server Language.
"The system displays a box containing the path from which you last installed files. In most cases, this is the path to the language files for the current language. For example, if you last installed NetWare files in English, this is the path to the English files. You should accept the path to the current language files, so that help and system messages are displayed in the current language until you have completed the change to the new language. If, for some reason, the path is not to the current language files, then you should enter the path to the current files. See the next step.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to accept the displayed path, or press
MOREINFO="NONE" <F3> and type in the correct path to the current language files.The path to the current language files has this syntax:SERVERMOREINFO="NONE" | CDMOREINFO="NONE":MOREINFO="NONE"\NW410\INSTALLMOREINFO="NONE"\current_languageIf the current language files are on another server, the system may prompt you for a username and password for that server. Follow the prompts.The system displays a menu listing the available languages.PERFORMANCE="REQUIRED"Choose the desired language from the menu
.You must choose a language that you installed earlier with the "Install an Additional Server Language" option of INSTALL. (See IDREF="FM11615""Copying the Language Files to the Server" on page 452.)If this is the first time you have changed the language, the system displays a prompt specifying the default destination where the language files are to be placed. The default location is the bootup directory, C:\NWSERVER.The language files must be placed in your bootup directory.PERFORMANCE="REQUIRED"Accept the default or type a new path if your bootup directory is not C:\NWSERVER.Once you specify the bootup directory, the system loads the language files.PAGENUM=455 ID="BP410"PERFORMANCE="REQUIRED"Reboot the server to change the server language.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting language for a workstationCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User GuideBOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User GuideCOLNAME=1 ROTATE="0" MOREROWS="0"Languages for NetWareCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"International use of NetWare 4.1" in ConceptsRENDERAS="SECT3"ID="FM37370"Specifying a Language for an NLMIDXID="w8376"BOOK="_idx" COLLECTION="nw41" TIDREF="i2046"IDXID="w8377"BOOK="_idx" COLLECTION="nw41" TIDREF="i2158"IDXID="w8378"BOOK="_idx" COLLECTION="nw41" TIDREF="i2760"Use the LANGUAGE command to change the language for subsequently loaded NLM programs. The LANGUAGE command does not change the language for currently loaded modules. .For consistent language display, you should also change the server language as explained in the previous section, IDREF="FM68389""Setting a Server's Language," on page 451.If you change the NLM language without changing the server language, the NLM still displays some character strings and screen titles in the server language.To see a list of languages, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LANGUAGE LIST MOREINFO="NONE"<Enter>The system displays a list of languages and their ID numbers. (Not all languages in the list are supported. Additional languages may be available in the future.)To determine the currently specified NLM language, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LANGUAGE MOREINFO="NONE"<Enter>
PAGENUM=456 ID="BP411"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXThe name or number of the language you want to use. Use the LANGUAGE LIST command to determine the correct name and number. English, French, Italian, German, and Spanish - Latin America are supported with the initial release of NetWare 4.1.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"To change the language for subsequently loaded NLM programs, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8379"BOOK="_idx" COLLECTION="nw41" TIDREF="i2050"
LANGUAGE language_number | language_name MOREINFO="NONE"<Enter>For example, to change the language to German, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LANGUAGE 7 MOREINFO="NONE"<EnterMOREINFO="NONE">MOREINFO="NONE"orFORMAT="LINESPECIFIC"MOREINFO="NONE"LANGUAGE GERMAN MOREINFO="NONE"<Enter>RENDERAS="SECT4"Additional InformationMOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Languages for NetWareCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"LANGUAGE" in Utilities Reference"BOOK="cncptenu" COLLECTION="nw41"International use of NetWare 4.1" in ConceptsRENDERAS="SECT3"Changing the Server Keyboard TypeIDXID="w8380"BOOK="_idx" COLLECTION="nw41" TIDREF="i2018"IDXID="w8381"BOOK="_idx" COLLECTION="nw41" TIDREF="i2046"IDXID="w8382"BOOK="_idx" COLLECTION="nw41" TIDREF="i2800"
NetWare 4 allows you to use keyboard types other than U.S. English by loading the IDXID="w8383"BOOK="_idx" COLLECTION="nw41" TIDREF="i2013"
KEYB.NLM program. The language you specify with KEYB.NLM must match the language of your keyboard, not the server language.The keyboard type can be changed without rebooting the server.Changing the keyboard type causes some of the keys on your keyboard to represent different characters. Do not use this command unless you have the appropriate keyboard for the language you are specifying and you are familiar with the keyboard's use. Otherwise, you may not know which keys to use to change the keyboard back to its original language.PAGENUM=457 ID="BP412"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"To view a list of valid keyboard types, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD KEYB MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the list of keyboard types, find the keyboard type that matches the one you are using.PERFORMANCE="REQUIRED"To change the keyboard type to match your keyboard, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD KEYB <keyboard_type> MOREINFO="NONE"<Enter>For example,
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD KEYB GERMANY MOREINFO="NONE"<Enter>Keyboard types are dependent on the IDXID="w8384"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"IDXID="w8385"BOOK="_idx" COLLECTION="nw41" TIDREF="i668"
code page set by DOS. If you must change the DOS code page setting, see your DOS manual for more information.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Languages for NetWareCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"International use of NetWare 4.1" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Languages supported by KEYBCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"KEYB" in Utilities ReferenceRENDERAS="SECT2"Viewing and Setting Server Time and Time ZoneThree server commands allow you to view and set server time and time zone: TIME, SET TIME, and SET TIME ZONE.RENDERAS="SECT3"Viewing Server TimeIDXID="w8386"BOOK="_idx" COLLECTION="nw41" TIDREF="i4479"To display the date and time kept by the IDXID="w8387"BOOK="_idx" COLLECTION="nw41" TIDREF="i2800"
NetWare server's clock, type the following at the server console:FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8388"BOOK="_idx" COLLECTION="nw41" TIDREF="i4494"
TIME MOREINFO="NONE"<Enter>
PAGENUM=458 ID="BP413"In addition to the date and time, the TIME command displays the server's daylight-saving-time status and 
time synchronization status. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"TIME" in Utilities Reference and "BOOK="cncptenu" COLLECTION="nw41"Time synchronization" in Concepts.RENDERAS="SECT3"Setting Server TimeIDXID="w8389"BOOK="_idx" COLLECTION="nw41" TIDREF="i4479"Because time synchronization between servers is critical to NetWare Directory Services, make sure you understand time synchronization before you change the time or time zone on a server.If you change the time on a Primary, Reference, or Single Reference server, you affect the time on other servers that use it as a time source.Setting the time incorrectly can adversely affect the performance of NetWare Directory Services. For more information, see IDREF="FM74015""Managing Network Time Synchronization" on page 571 and "BOOK="utlrfenu" COLLECTION="nw41"SET TIME" in Utilities Reference.To set or change the IDXID="w8390"BOOK="_idx" COLLECTION="nw41" TIDREF="i939"
date and time kept by the NetWare server's clock, type the following at the server console prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8391"BOOK="_idx" COLLECTION="nw41" TIDREF="i4098"
SET TIME [mo/day/yr] [hr:min:sec] MOREINFO="NONE"<Enter>If you don't specify a.m. or p.m., NetWare 4.1 uses a 24-hour clock. For example, if you enter 1:00, the time is set to 1:00 a.m. If you enter 13:00, the time is set to 1:00 p.m.RENDERAS="SECT3"Changing the Server Time ZoneIDXID="w8392"BOOK="_idx" COLLECTION="nw41" TIDREF="i4479"Because time synchronization between servers is critical to NetWare Directory Services, make sure you understand time synchronization before you change the time or time zone on a server. Setting the time incorrectly can adversely affect the performance of NetWare Directory Services.The SET TIME ZONE command specifies the abbreviation for the local time zone and for daylight saving time. It also specifies the difference in hours between the local time zone and Coordinated Universal Time. Coordinated Universal Time (UTC) has historically been known as Greenwich Mean Time.The SET TIME ZONE command does not set the time or turn daylight saving time on and off. You turn on daylight saving time and set other related parameters by using the SET command. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.PAGENUM=459 ID="BP414"To display the current time zone setting, type the following at the server console prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET TIME ZONE MOREINFO="NONE"<Enter>RENDERAS="SECT4"ProcedureTo change the time zone information for your NetWare server, follow these steps.PERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"SET TIME ZONE zone [+|-]  hr:min:sec[daylight] MOREINFO="NONE"<Enter>Where
MARK=BULLETzone is a standard three-letter abbreviation for the time zone, such as PST for Pacific Standard Time.[+ | - ] is the number of hours east or west of the Coordinated Universal Time (UTC) meridian. If you do not specify + or -, the system defaults to +.hr:min:sec indicates the time difference between UTC and the local time zone. You can specify this difference simply in hours. Or, for extreme accuracy, specify hours, minutes, and seconds.daylight represents a standard three-letter abbreviation for daylight saving time, such as PDT for Pacific Daylight Time.For example, the following command line specifies PST as the standard time abbreviation, 8 as the number of hours to add to Coordinated Universal Time, and PDT as the abbreviation for daylight time:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET TIME ZONE PST8PDT MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Change the SET TIME ZONE command in the AUTOEXEC.NCF file to the new time zone.For more information, see "
BOOK="utlrfenu" COLLECTION="nw41"SET TIME ZONE" in 
Utilities Reference.
PAGENUM=460 ID="BP415"RENDERAS="SECT2"Changing a Server's Name or IPX Internal Network NumberIDXID="w8393"BOOK="_idx" COLLECTION="nw41" TIDREF="i1936"IDXID="w8394"BOOK="_idx" COLLECTION="nw41" TIDREF="i2571"
The server's IDXID="w8395"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
name and IPX internal network number are stored in the IDXID="w8396"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"IDXID="w8397"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"
AUTOEXEC.NCF file. You can edit this file by using IDXID="w8398"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"IDXID="w8399"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL or EDIT at the server console, or by using an ASCII text editor at the workstation.This procedure requires you to reboot the NetWare server. You may want to do it after business hours or when no one is accessing the server.To use INSTALL to change the settings, follow the procedure in this section. To use EDIT, see IDREF="FM88816""Editing Text Files from the Server Console" on page 449.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "NCF Files Options" from the "Installation Options" menu.PERFORMANCE="REQUIRED"Choose "Edit AUTOEXEC.NCF File" from the "NCF Files Options" menu.PERFORMANCE="REQUIRED"Change the following lines in the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"File Server Name  server_name
IPX Internal Netnet_number PERFORMANCE="REQUIRED"To exit and save the file, press 
MOREINFO="NONE"<F10>, and then select "Yes" from the "Save file AUTOEXEC.NCF?" box.PERFORMANCE="REQUIRED"To exit INSTALL, press 
MOREINFO="NONE"<Alt>+<F10>.PERFORMANCE="REQUIRED"Reboot the server to make the changes take effect.See 
IDREF="FM10818""Bringing Down a Server" on page 436 if you need help rebooting the server.
PAGENUM=461 ID="BP416"Using INSTALL to rename a server does not affect NDSTM server objects. You must use NETADMIN or NetWare Administrator to rename NetWare Server objects.Likewise, using INSTALL to rename a volume does not affect NDS volume objects. For more information, see IDREF="FM99112""Renaming Volumes" on page 504.Be sure to update any references to the former server name in the Directory tree and in the TIMESYNC.CFG file.RENDERAS="SECT1"Managing Server ConnectionsIDXID="w8400"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
This section explains how to enable and disable access to the server and how to monitor and solve common connection problems.RENDERAS="SECT2"Disabling and Enabling LoginsIDXID="w8401"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"IDXID="w8402"BOOK="_idx" COLLECTION="nw41" TIDREF="i792"If you need to make repairs to the server, use the DISABLE LOGIN command to prevent users from logging in.This does not affect users who are already logged in to the network. To reenable logins, or to enable the IDXID="w8403"BOOK="_idx" COLLECTION="nw41" TIDREF="i74"IDXID="w8404"BOOK="_idx" COLLECTION="nw41" TIDREF="i118"
ADMIN 
account when it has been IDXID="w8405"BOOK="_idx" COLLECTION="nw41" TIDREF="i2177"
locked by the intruder detection function, use ENABLE LOGIN.For more information about these commands, see "BOOK="utlrfenu" COLLECTION="nw41"DISABLE LOGIN" and "BOOK="utlrfenu" COLLECTION="nw41"ENABLE LOGIN" in Utilities Reference.For more information about the intruder detection function, see IDREF="FM24954"Table 1-8 and IDREF="FM11593"Table 1-10 in Chapter 1.RENDERAS="SECT2"Clearing a Workstation ConnectionIDXID="w8406"BOOK="_idx" COLLECTION="nw41" TIDREF="i792"You can use either the MONITOR utility or the CLEAR STATION command to clear a connection, as described in the following sections.Use either of these procedures to clear a workstation connection when the workstation has crashed and left open files on the server.If you clear the connection while the workstation is in the middle of a transaction or a file update, the files may be saved with incorrect data.PAGENUM=462 ID="BP417"RENDERAS="SECT3"Using MONITOR to Clear the ConnectionIDXID="w8407"BOOK="_idx" COLLECTION="nw41" TIDREF="i2506"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD MONITOR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "Connection Information" from the "Available Options" menu.A list of active connections appears.PERFORMANCE="REQUIRED"Select the connection you want to clear.PERFORMANCE="REQUIRED"(Optional) Press 
MOREINFO="NONE"<Enter> to view files that are open for the workstation.After viewing files, press MOREINFO="NONE"<Esc> to go back to the "Connection Information" screen.PERFORMANCE="REQUIRED"To clear the workstation connection, press 
MOREINFO="NONE"<Delete>.PERFORMANCE="REQUIRED"At the "Clear Connection?" box, select "Yes."The connection is no 
longer listed on the "Connection Information" screen.RENDERAS="SECT3"Using the CLEAR STATION Command to Clear the ConnectionIDXID="w8408"BOOK="_idx" COLLECTION="nw41" TIDREF="i636"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXThe IDXID="w8409"BOOK="_idx" COLLECTION="nw41" TIDREF="i784"
connection number for the workstation. You can determine the connection number by selecting "Connection Information" from the "Available Options" menu in MONITOR.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"CLEAR STATION n MOREINFO="NONE"<Enter>Replace 
n with the connection number of the workstation.
PAGENUM=463 ID="BP418"The system displays a message stating that the connection is cleared.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Connection numbersCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Connection number" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the CLEAR STATION commandCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"CLEAR STATION" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the MONITOR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities ReferenceRENDERAS="SECT2"Monitoring Workstation ConnectionsUse this procedure for early warning that a workstation connection has become inactive. This procedure changes the SET IDXID="w8410"BOOK="_idx" COLLECTION="nw41" TIDREF="i4819"
watchdog parameters, which a server sends to a workstation to determine if the workstation connection is still active.When the parameters are set to the values specified in the following procedure, the server sends 20 watchdog packets (twice the default value) but sends them in the shortest time allowed. If there is no response from the workstation, the IDXID="w8411"BOOK="_idx" COLLECTION="nw41" TIDREF="i792"
server disconnects the workstation and displays an alert on the console.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "Communications" from the "Categories" menu.PERFORMANCE="REQUIRED"Change the following watchdog parameters to the indicated values:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Number of Watchdog Packets=20
Delay Between Watchdog Packets=10
Delay Before First Watchdog Packet=16
Console Display Watchdog Logouts=ON
PAGENUM=464 ID="BP419"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the 
"Update Options
" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file.The system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file.If you do not update the AUTOEXEC.NCF file, the parameter changes last only until the server is rebooted.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Watchdog packetsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Watchdog" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"SET parametersCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using SERVMAN to set parametersCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities ReferenceRENDERAS="SECT2"Increasing the Maximum Number of Packet Receive BuffersIDXID="w8412"BOOK="_idx" COLLECTION="nw41" TIDREF="i792"IDXID="w8413"BOOK="_idx" COLLECTION="nw41" TIDREF="i3182"
Packet receive buffers store incoming data packets until they can be processed by the server.You should increase the maximum number of packet receive buffers only if the server is running out of buffers. The server is running out of buffers if it isMARK=BULLETSlowing down and losing workstation connectionsReceiving "No IDXID="w8414"BOOK="_idx" COLLECTION="nw41" TIDREF="i1283"
ECB available count" errorsThe "General Information" window of MONITOR displays the total number of currently allocated packet receive buffers.PAGENUM=465 ID="BP420"RENDERAS="SECT3"IDXID="w8415"BOOK="_idx" COLLECTION="nw41" TIDREF="i3182"
ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "Communications" from the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Maximum Packet Receive Buffers."PERFORMANCE="REQUIRED"Increase the value of this parameter and press 
MOREINFO="NONE"<Enter>.A good rule of thumb is to set this value to twice the size of the Minimum Packet Receive Buffer value
.For other suggestions, see the discussion of the Maximum Packet Receive Buffer parameter under "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.You are prompted to update the STARTUP.NCF file
.PERFORMANCE="REQUIRED"If the SET parameter is in the STARTUP.NCF file, press 
MOREINFO="NONE"<Enter> to update the value in the file. Otherwise press
MOREINFO="NONE" <Esc>.You are prompted to update the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press MOREINFO="NONE"<Enter> to update the value in the file. Otherwise, press 
MOREINFO="NONE"<Esc>.IDXID="w8416"BOOK="_idx" COLLECTION="nw41" TIDREF="i792"
If you press MOREINFO="NONE"<Enter> to update the file, the system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file.RENDERAS="SECT2"ID="FM64818"Increasing the Minimum Number of Packet Receive BuffersIDXID="w8417"BOOK="_idx" COLLECTION="nw41" TIDREF="i792"The operating system allocates a minimum number of packet receive buffers as soon as the server boots. The minimum number is specified by the Minimum Packet Receive Buffer SET parameter.PAGENUM=466 ID="BP421"IDXID="w8418"BOOK="_idx" COLLECTION="nw41" TIDREF="i2506"
Refer to the Packet Receive Buffer value in the "General Information" window of MONITOR to determine how many buffers the server is currently allocating.Use the following procedure to increase the minimum number of packet receive buffers ifMARK=BULLETThe allocated number is higher than 10 and the server doesn't respond immediately after bootingThe "No ECB available" count in MONITOR grows continuously.RENDERAS="SECT3"IDXID="w8419"BOOK="_idx" COLLECTION="nw41" TIDREF="i3182"
ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "Communications" from the 
MOREINFO="NONE""Categories" menu.PERFORMANCE="REQUIRED"Choose "Minimum Packet Receive Buffers."PERFORMANCE="REQUIRED"Increase the value of this parameter.As a rule of thumb, allocate at least two packet receive buffers for each workstation connection
.Fo
r other suggested settings, see the discussion of t
he Minimum Packet Receive Buffer parameter under "
BOOK="utlrfenu" COLLECTION="nw41"SET" in 
Utilities Reference.The Minimum Packet Receive Buffers value should be smaller than the Maximum Packet Receive Buffers value. If it is greater than the maximum value, the system changes the maximum value to match the minimum value.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears
, indicating the path to the STARTUP.NCF file.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to update the file.
PAGENUM=467 ID="BP422"The system places the parameter in the STARTUP.NCF file the next time the server boots. The parameter can be set only in the STARTUP.NCF file.PERFORMANCE="REQUIRED"When you want the changes to take effect, reboot the server.RENDERAS="SECT2"Avoiding Bottlenecks During Peak UsageIDXID="w8420"BOOK="_idx" COLLECTION="nw41" TIDREF="i507"IDXID="w8421"BOOK="_idx" COLLECTION="nw41" TIDREF="i3182"IDXID="w8422"BOOK="_idx" COLLECTION="nw41" TIDREF="i3182"
Use this procedure if your server is slow to respond during periods of heavy use.This procedure decreases the value of the New Packet Receive Buffer Wait Time SET parameter, which specifies how long the server must wait before granting a new packet receive buffer. By decreasing the value of this parameter you cause the system to grant buffers more quickly.You may also want to increase the value of the Minimum Packet Receive Buffers parameter. IDREF="FM64818""Increasing the Minimum Number of Packet Receive Buffers" on page 465.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "Communications" from the "Categories" menu.PERFORMANCE="REQUIRED"Choose "New Packet Receive Buffer Wait Time."PERFORMANCE="REQUIRED"Decrease the value of this parameter and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears
, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file.
PAGENUM=468 ID="BP423"If you press 
MOREINFO="NONE"<Enter>, the system writes the parameter to the AUTOEXEC.NCF file or updates the parameter if it is already in the file. The file is updated immediately. You do not need to reboot the server.If you do not press 
MOREINFO="NONE"<Enter>, the parameter chang
e lasts only until you reboot the server.RENDERAS="SECT1"Monitoring and Optimizing the ServerIDXID="w8423"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
This section describes how to prevent server problems that involve memory management, CPU utilization, process scheduling, and LAN traffic. There are also procedures to help improve server performance.RENDERAS="SECT2"ID="FM35766"Assessing Server RAMOne of the most common causes of a slow network is insufficient Random Access Memory (RAM) in the NetWare server. This procedure helps you determine if your server has enough RAM.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8424"BOOK="_idx" COLLECTION="nw41" TIDREF="i2506"
MONITOR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Cache 
IDXID="w8425"BOOK="_idx" COLLECTION="nw41" TIDREF="i4742"
Utilization" from the "Available Options" menu.PERFORMANCE="REQUIRED"Write down the percentage o
f Long Term Cache Hits shown in the lower window of the screen.Tracking 
IDXID="w8426"BOOK="_idx" COLLECTION="nw41" TIDREF="i570"
cache hits helps you predict when you need more RAM before you experience serious performance loss.If the percentage of Long Term Cache Hits falls below 90 percent, add more RAM to the server.
PAGENUM=469 ID="BP424"PERFORMANCE="REQUIRED"(Optional) To temporarily 
IDXID="w8427"BOOK="_idx" COLLECTION="nw41" TIDREF="i2392"
free up RAM, do 
either or both of the following:
MARK=BULLETUse the IDXID="w8428"BOOK="_idx" COLLECTION="nw41" TIDREF="i3770"
REMOVE DOS or SECURE CONSOLE command to make the memory used by DOS available to cache.Unload any NLM programs that are not critical.PERFORMANCE="REQUIRED"To exit MONITOR, press 
MOREINFO="NONE"<Esc>, or to return to the console prompt without exiting MONITOR, press 
MOREINFO="NONE"<Alt>+<Esc>.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Cache buffersCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Cache buffer" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"MONITOR utility COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"REMOVE DOS command COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"REMOVE DOS" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"SECURE CONSOLE commandCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"SECURE CONSOLE" in Utilities ReferenceRENDERAS="SECT2"Controlling Memory AllocationIDXID="w8429"BOOK="_idx" COLLECTION="nw41" TIDREF="i2392"IDXID="w8430"BOOK="_idx" COLLECTION="nw41" TIDREF="i2392"IDXID="w8431"BOOK="_idx" COLLECTION="nw41" TIDREF="i1455"IDXID="w8432"BOOK="_idx" COLLECTION="nw41" TIDREF="i1047"
This procedure explains how to limit the amount of memory available for file and directory caching, thus making more memory available for NetWare Loadable ModuleTM (NLM) programs and server processes. Use this procedure if you receive "IDXID="w8433"BOOK="_idx" COLLECTION="nw41" TIDREF="i150"
insufficient memory" alerts when trying to load NLMTM programs.To solve memory problems without limiting memory for file and directory caching, add more memory.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.
PAGENUM=470 ID="BP425"PERFORMANCE="REQUIRED"Choose "File Caching" from the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Minimum File Cache Buffers."This parameter specifies the minimum amount of memory the system will keep for file caching. Memory above this minimum amount is available for other processes.PERFORMANCE="REQUIRED"Reduce the value of this parameter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Directory Caching" from the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Maximum Directory Cache Buffers."This parameter specifies the maximum number of buffers that can be allocated for directory caching. Once allocated, the buffers remain allocated, even if they are not being used. Thus, they are not available for other processes
.By reducing this parameter, you prevent the system from allocating too many directory cache buffers 
and you ensure that more memory is available for other server processes
.Reducing the maximum number of directory cache buffers may impede system performance.PERFORMANCE="REQUIRED"Reduce the value of the "Maximum Directory Cache Buffers" parameter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears
, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to update the file.When you press 
MOREINFO="NONE"<Enter>, the system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file
.PERFORMANCE="REQUIRED"Reboot the server to free the memory
.PAGENUM=471 ID="BP426"Other temporary measures to free memory include using the REMOVE DOS or SECURE CONSOLE command to make the DOS partition memory available, and unloading noncritical NLM programs. See "BOOK="utlrfenu" COLLECTION="nw41"REMOVE DOS" and "BOOK="utlrfenu" COLLECTION="nw41"SECURE CONSOLE" in Utilities Reference.RENDERAS="SECT2"Speeding Directory SearchesIDXID="w8434"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"IDXID="w8435"BOOK="_idx" COLLECTION="nw41" TIDREF="i1047"
Use this procedure if the server responds slowly to directory searches.This procedure requires you to increase the number of directory cache buffers that can be allocated by the system. Memory allocated for directory cache buffers is no longer available for use by other processes.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "Directory Caching" from the "Categories" menu.PERFORMANCE="REQUIRED"Select "Directory Cache Allocation Wait Time."This parameter specifies how long the system must wait after allocating one directory cache buffer before it can allocate another buffer. If the value is too high, directory searches are slow.PERFORMANCE="REQUIRED"Decrease the value of this parameter.PERFORMANCE="REQUIRED"Select "Maximum Directory Cache Buffers."This parameter specifies the maximum number of cache buffers the system can allocate for directory caching. If the number is too low, directory searches are slow.PERFORMANCE="REQUIRED"Increase the value of this parameter.PERFORMANCE="REQUIRED"Select "Minimum Directory Cache Buffers."This parameter specifies the minimum number of directory cache buffers the system allocates. If the number is too low, directory searches are slow.
PAGENUM=472 ID="BP427"PERFORMANCE="REQUIRED"Increase the value of this parameter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears
, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file.If you press 
MOREINFO="NONE"<Enter>, the system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file. The file is updated immediately. You do not need to reboot the server.If you do not press 
MOREINFO="NONE"<Enter>, the parameter changes last only until you reboot the server.RENDERAS="SECT2"ID="FM23755"Prioritizing Server ProcessesIDXID="w8436"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"IDXID="w8437"BOOK="_idx" COLLECTION="nw41" TIDREF="i3559"IDXID="w8438"BOOK="_idx" COLLECTION="nw41" TIDREF="i3562"IDXID="w8439"BOOK="_idx" COLLECTION="nw41" TIDREF="i3960"
You can use SCHDELAY to prioritize server processes. SCHDELAY allows you to delay the execution of specific processes, thereby giving more CPU time---and higher priority---to other processes.The command syntax isFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SCHDELAY process_name = number [process_name = number] MOREINFO="NONE"<Enter>The process name value is the name of a process or thread that accesses the server CPU. You can specify the process value for multiple processes at one time.To view the list of processes that can be prioritized, along with their current SCHDELAY values, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SCHDELAY MOREINFO="NONE"<Enter>The number value determines how many times the process delays execution. A value of 0 causes no delay, while a value of 2 skips every other execution of the process.To delay a process, you can enter a value from 2 to 10000---the higher the value, the lower the priority of the process.PAGENUM=473 ID="BP428"The SCHDELAY values only have an effect if the system is busy and two or more processes are vying for the CPU's time.For example, if you want to assign a database NLM called DBNLM a lower priority than other processes so it won't monopolize the NetWare server's CPU, put a command similar to the following in the AUTOEXEC.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SCHDELAY DBNLM = 2To view the list of processes and determine which processes are hoarding CPU time, follow this procedure.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8440"BOOK="_idx" COLLECTION="nw41" TIDREF="i2506"
MONITOR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "Scheduling Information" from the "Available Options" menu.A list of server processes appears, with four columns of information about each process.
MARK=BULLETThe "Sch Delay" column shows the current SCHDELAY value assigned to the process. The default is 0.The "Time" column shows the CPU time spent executing the process code.The "Count" column shows how many times the process ran during the sample period. (The "Total Sample Time" is displayed at the bottom of the screen.)The "Load" column shows the percent of total CPU time spent on the process.PERFORMANCE="REQUIRED"Select a process that has a high number in the "Load" column.Look for processes that have consistently high values, rather than high peak values.PERFORMANCE="REQUIRED"Use the plus (+) or minus (-) key to increase or decrease the SCHDELAY value for the selected process.The value in the "Load" column changes accordingly.
PAGENUM=474 ID="BP429"PERFORMANCE="REQUIRED"Experiment with higher or lower SCHDELAY values until the CPU load, as displayed in the "Load" column, is within acceptable limits.What is acceptable depends upon your system and your needs. The goal is to balance the load so that processes run to your satisfaction
.To make the SCHDELAY value effective each time the server boots, put the SCHDELAY command in the IDXID="w8441"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"
AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"To exit the scheduling information window, press 
MOREINFO="NONE"<Esc>.You do not need to reboot the server.RENDERAS="SECT2"Checking a Server's Processor UtilizationIDXID="w8442"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"IDXID="w8443"BOOK="_idx" COLLECTION="nw41" TIDREF="i3562"IDXID="w8444"BOOK="_idx" COLLECTION="nw41" TIDREF="i4742"One possible cause of network problems is the monopolizing of the CPU by a single process. This procedure helps you determine which processes are using the CPU and how much load they are putting on the CPU's time.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8445"BOOK="_idx" COLLECTION="nw41" TIDREF="i2506"
MONITOR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Processor Utilization" from the "Available Options" menu.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F3> to view a list of the currently loaded 
IDXID="w8446"BOOK="_idx" COLLECTION="nw41" TIDREF="i3559"
processes and interrupts.For each item on the list, notice the percentage given in the "Load" column. This is the percentage of time the CPU spent servicing this process during the one-second sample period.Compare processes to determine which processes are taking the most CPU time.
PAGENUM=475 ID="BP430"PERFORMANCE="REQUIRED"(Optional) To 
IDXID="w8447"BOOK="_idx" COLLECTION="nw41" TIDREF="i3562"
redistribute processor utilization, you can do either or both of the following:
MARK=BULLETUnload noncritical NLM programs that are taking a large percentage of CPU time.Assign processes a lower priority, using SCHDELAY. For more information, see IDREF="FM23755""Prioritizing Server Processes" on page 472.RENDERAS="SECT2"Viewing a Server's Packet TrafficYou can view the packet IDXID="w8448"BOOK="_idx" COLLECTION="nw41" TIDREF="i4542"
traffic coming in and going out of the server by using TRACK ON at the server console prompt. Use TRACK OFF to stop viewing the packet traffic.See "BOOK="utlrfenu" COLLECTION="nw41"TRACK ON" and "BOOK="utlrfenu" COLLECTION="nw41"TRACK OFF" in Utilities Reference for more information about these commands.RENDERAS="SECT2"Viewing LAN Driver StatisticsIDXID="w8449"BOOK="_idx" COLLECTION="nw41" TIDREF="i2035"IDXID="w8450"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
Reviewing the LAN driver statistics on your server can help you regulate network traffic and troubleshoot system problems.For example, you can use the LAN driver statistics to determineMARK=BULLETThe total traffic since the LAN driver was loadedWhich drivers handle the most trafficThe frequency of various errorsMany statistics count the instances of a particular error. For example, the Send Packet Retry Count statistic indicates how many times the server tried to send a packet but failed because of a hardware problem.The number and kinds of statistics available depend on the LAN drivers installed on your system. For descriptions of the most common statistics, refer to Appendix B, "BOOK="utlrfenu" COLLECTION="nw41"LAN Driver Statistics," of Utilities Reference.Follow this procedure to view the statistics.PAGENUM=476 ID="BP431"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8451"BOOK="_idx" COLLECTION="nw41" TIDREF="i2506"
MONITOR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "LAN/WAN Information" from the "Available Options" menu.PERFORMANCE="REQUIRED"Select a LAN driver from the "LAN Driver Information" menu.The statistics for the selected LAN driver are displayed. Press 
MOREINFO="NONE"<PMOREINFO="NONE"aMOREINFO="NONE"gMOREINFO="NONE"eUp> and 
MOREINFO="NONE"<PMOREINFO="NONE"aMOREINFO="NONE"gMOREINFO="NONE"eDown> to scroll through the information in the window. For an explanation of the statistics, see Appendix B, "
BOOK="utlrfenu" COLLECTION="nw41"LAN Driver Statistics," of 
Utilities Reference.RENDERAS="SECT2"Improving Server PerformanceYou can increase server performance two ways:MARK=BULLETBy using magneto-optical media to extend server storage capacity. Such storage enables the server to migrate seldom-used files from the hard disk, freeing space needed by other files and processes.For procedures related to magneto-optical media, see IDREF="FM16817"Chapter 6, "Migrating Data Using the High Capacity Storage System."By 
increasing the size of the packets received by the server.The method of increasing packet size is explained in the following procedure.Use this procedure only if the network boards in your server can transmit more than 512 bytes of data per packet. Refer to the documentation that came with the network boards to determine the packet size.PAGENUM=477 ID="BP432"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXLarge-packet network boards installed in the server. Refer to the documentation that comes with the boards to determine the available packet size.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "Communications" from the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Maximum Physical Receive Packet Size" from the "Communications" menu.PERFORMANCE="REQUIRED"Increase the value and press 
MOREINFO="NONE"<Enter>.Refer to the documentation that comes with the boards to determine the maximum value.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears
, indicating the path to the STARTUP.NCF file.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to update the file
.PERFORMANCE="REQUIRED"When you want the changes to take effect, reboot the server.
PAGENUM=478 ID="BP433"RENDERAS="SECT2"Improving Disk WritesThe following sections describe methods for improving the speed of disk writes.RENDERAS="SECT3"Increasing the Number of Concurrent WritesIDXID="w8452"BOOK="_idx" COLLECTION="nw41" TIDREF="i1132"You can increase the speed and efficiency of disk cache writes by increasing the number of write requests that can be executed at one time.To determine if you need to increase the number of concurrent writes, first compare the number of dirty cache buffers to the total number of cache buffers. Dirty cache buffers contain data that has not yet been written to disk. These statistics are found on the "General Information" screen in MONITOR.If the number of dirty cache buffers is greater than 70 percent of total cache buffers, use the following procedure to increase the number of concurrent write requests.For an explanation of file caching and dirty cache buffers, refer to "BOOK="cncptenu" COLLECTION="nw41"Cache memory" in Concepts.Increasing the number of concurrent disk cache writes slows disk cache reads.You will want to balance the speed of disk writes and reads to meet your own needs.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "File Caching" from the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Maximum Concurrent Disk Cache Writes" from the "File Caching" menu.PERFORMANCE="REQUIRED"Increase the parameter value and press 
MOREINFO="NONE"<Enter>.If the parameter is currently at the default value of 50, try increasing it to 100.PAGENUM=479 ID="BP434"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears, indicating the path to 
the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file
.If you press 
MOREINFO="NONE"<Enter>, the system writes the parameter to the AUTOEXEC.NCF file or updates the parameter if it is already in the file. The file is updated immediately. You do not need to reboot the server.If you do not press 
MOREINFO="NONE"<Enter>, the parameter change lasts only until you reboot the server.RENDERAS="SECT3"Changing Disk and Directory Caching for Faster WritesIDXID="w8453"BOOK="_idx" COLLECTION="nw41" TIDREF="i1047"IDXID="w8454"BOOK="_idx" COLLECTION="nw41" TIDREF="i1132"
Use this procedure if network users frequently make many small write requests and the server is slow to respond to the requests.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "File Caching" from the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Dirty Disk Cache Delay Time" from the "File Caching" menu.PERFORMANCE="REQUIRED"Increase the value and press 
MOREINFO="NONE"<Enter>.This parameter specifies how long the system waits before writing a not-completely-dirty cache buffer to disk.If the value is low, the system writes to disk more frequently, but writes fewer requests each time. If the value is high, the system waits longer before writing to disk, but executes more write requests with each operation. A higher value provides greater efficiency in writing to disk.
PAGENUM=480 ID="BP435"If the parameter is currently at the default value of 3.3 seconds, try increasing the value to 7 seconds.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to reach the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Directory 
IDXID="w8455"BOOK="_idx" COLLECTION="nw41" TIDREF="i579"
Caching" from the "Categories" menu and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Dirty Directory Cache Delay Time."This parameter specifies how long the system keeps a directory table write request in memory before writing it to disk
.Increasing the parameter provides slightly faster performance, but may increase the chance of directory tables becoming corrupted.PERFORMANCE="REQUIRED"Increase the value and press 
MOREINFO="NONE"<Enter>.If the parameter is currently at the default value of
 0.5 secon
d, try increasing the value to 2 seconds
.PERFORMANCE="REQUIRED"Choose "Maximum Concurrent Directory Cache Writes."This parameter determines how many write requests from directory cache buffers are executed at one time. Increasing this value increases the efficiency of directory cache write requests.Increasing the number of concurrent directory cache writes decreases the speed of directory cache reads. You will want to balance the speed of writes and reads to meet your own needs.PERFORMANCE="REQUIRED"Increase the value and press 
MOREINFO="NONE"<Enter>.If the parameter is currently at the default value of 10, try increasing the value to 25
.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file.
PAGENUM=481 ID="BP436"If you press 
MOREINFO="NONE"<Enter>, the system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file. The file is updated immediately. You do not need to reboot the server.If you do not press 
MOREINFO="NONE"<Enter>, the parameter changes last only until you reboot the server.RENDERAS="SECT3"Turning Off Read-After-Write VerificationIDXID="w8456"BOOK="_idx" COLLECTION="nw41" TIDREF="i3690"IDXID="w8457"BOOK="_idx" COLLECTION="nw41" TIDREF="i1132"
Read-after-write verification is an important means of protecting the data on your system. Normally, you should not disable it.However, if your disks are mirrored and reliable, you may choose to disable read-after-write verification because disabling almost doubles the speed of disk writes.Turning off read-after-write verification may increase the risk of data corruption on the server's hard disk. You should use the following procedure only if your disks are mirrored and reliable, and you understand the risk.RENDERAS="SECT4"IDXID="w8458"BOOK="_idx" COLLECTION="nw41" TIDREF="i2506"
PrerequisitesMARK=CHECKBOXMirrored hard disksRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD MONITOR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Disk Information" from the "Available Options" menu and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Select a disk drive from the "System Disk Drives" menu.PERFORMANCE="REQUIRED"Select "Read After Write Verify" from the "Driver Status" menu.PERFORMANCE="REQUIRED"Select "Disable Verify" from the "Read After Write Status" menu.
PAGENUM=482 ID="BP437"You can also disable read-after-write verification by setting the Enable Disk Read After Write Verify SET parameter to OFF. However, this setting only affects those disks loaded after the parameter value is changed. It does not change the setting for currently loaded disks.RENDERAS="SECT2"Improving Disk ReadsThe following sections describe methods for improving the speed of disk reads.RENDERAS="SECT3"Changing Concurrent Disk and Directory Writes for Faster ReadsIDXID="w8459"BOOK="_idx" COLLECTION="nw41" TIDREF="i1127"IDXID="w8460"BOOK="_idx" COLLECTION="nw41" TIDREF="i1047"
Use this procedure if your server is slow to respond to read requests.This procedure requires you to decrease the values of the Maximum Concurrent Disk Cache Writes parameter and the Maximum Concurrent Directory Cache Writes parameter. Although decreasing these values increases the speed of read requests, it may decrease the speed and efficiency of write requests.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "File Caching" from the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Maximum Concurrent Disk Cache Writes."PERFORMANCE="REQUIRED"Decrease this value and press 
MOREINFO="NONE"<Enter>.If the parameter is currently set to the default value of 50, try setting the value to 10.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to reach the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Directory Caching" from the "Categories" menu.PERFORMANCE="REQUIRED"Choose "Maximum Concurrent Directory Cache Writes."PERFORMANCE="REQUIRED"Decrease this value and press 
MOREINFO="NONE"<Enter>.
PAGENUM=483 ID="BP438"If the parameter is currently set to the default value of 10, try setting the value to 5.PERFORMANCE="REQUIRED"Choose "Directory Cache Buffer NonReferenced Delay."This parameter specifies how long a directory entry must be cached before it can be overwritten. Increasing this value causes the system to allocate more directory cache buffers and thus speeds directory access.PERFORMANCE="REQUIRED"Increase this value and press 
MOREINFO="NONE"<Enter>.If the parameter is currently set to the default value of 5.5 seconds, try setting the value to 60 seconds.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file.If you press 
MOREINFO="NONE"<Enter>, the system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file. The file is updated immediately. You do not need to reboot the server.If you do not press 
MOREINFO="NONE"<Enter>, the parameter changes last only until you reboot the server.RENDERAS="SECT3"Changing the Turbo FAT Wait Time for Faster ReadsIDXID="w8461"BOOK="_idx" COLLECTION="nw41" TIDREF="i1448"IDXID="w8462"BOOK="_idx" COLLECTION="nw41" TIDREF="i1127"When a program randomly accesses a file that contains more than 64 File Allocation Table (FAT) entries, the system builds a turbo FAT index for the file so that the information in the file can be accessed quickly.The Turbo FAT Re-Use Wait Time parameter specifies how long a turbo FAT index remains in memory after the indexed file is closed. When the turbo FAT index is in memory, files can be opened and information accessed faster.If network users frequently access files larger than 64 blocks, use this procedure to increase the time the index is kept in memory.PAGENUM=484 ID="BP439"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "File System" from the "Categories" menu.PERFORMANCE="REQUIRED"Select "Turbo FAT Re-Use Wait Time."PERFORMANCE="REQUIRED"Increase this value and press MOREINFO="NONE"<Enter>.You must specify the value in seconds.If the parameter is currently set to the default value of 329.5 seconds (5 minutes 29.6 seconds), try setting the value to 600 seconds (10 minutes).PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file.If you press 
MOREINFO="NONE"<Enter>, the system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file. The file is updated immediately. You do not need to reboot the server.If you do not press 
MOREINFO="NONE"<Enter>, the parameter changes last only until you reboot the server.
PAGENUM=485 ID="BP440"RENDERAS="SECT2"Controlling Resource Allocation with LocksA lock prevents a file or record from being updated by more than one user at a time. By controlling the number of file and record locks available to a workstation or a server, you control access to files and records.You may choose to limit the number of locks to prevent overuse of file resources. Or you may choose to increase the number of locks if workstations can't open files.RENDERAS="SECT3"Keeping Workstations from Overusing File ResourcesIDXID="w8463"BOOK="_idx" COLLECTION="nw41" TIDREF="i3705"IDXID="w8464"BOOK="_idx" COLLECTION="nw41" TIDREF="i1466"
If workstations are overusing file resources by opening and locking too many files or records at one time, use the following procedure to limit the number of locks for the server and for each workstation.Before limiting file and record locks, make sure the workstations have an adequate number of locks to access the files and records they need. Limiting needed locks can cause applications to generate errors.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "Locks" from the "Categories" menu.PERFORMANCE="REQUIRED"Decrease the following parameter values to limit the total number of file and record locks allowed for the server:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Maximum Record Locks
Maximum File LocksPERFORMANCE="REQUIRED"Decrease the following parameter values to limit the total number of file and records locks allowed for each workstation:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Maximum Record Locks Per Connection
Maximum File Locks Per Connection
PAGENUM=486 ID="BP441"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file
.If you press 
MOREINFO="NONE"<Enter>, the system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file. The file is updated immediately. You do not need to reboot the server.If you do not press 
MOREINFO="NONE"<Enter>, the parameter changes last only until you reboot the server.RENDERAS="SECT3"Increasing File Record LocksIDXID="w8465"BOOK="_idx" COLLECTION="nw41" TIDREF="i2182"Use this procedure if IDXID="w8466"BOOK="_idx" COLLECTION="nw41" TIDREF="i259"
applications fail because they cannot open enough files or because not enough record locks are available.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "Locks" from the "Categories" menu.PERFORMANCE="REQUIRED"Increase the following parameter values to increase the number of file and record locks allowed for the server:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Maximum Record Locks
Maximum File LocksPERFORMANCE="REQUIRED"Increase the following parameter values to increase the number of file and record locks allowed for each workstation:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Maximum Record Locks Per Connection
Maximum File Locks Per Connection
PAGENUM=487 ID="BP442"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to update the file
.If you press 
MOREINFO="NONE"<Enter>, the system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file. The file is updated immediately. You do not need to reboot the server.If you do not press MOREINFO="NONE"<Enter>, the parameter changes last only until you reboot the server.RENDERAS="SECT2"Displaying Alert MessagesYou can use SET parameters to control the display of alert messages on the IDXID="w8467"BOOK="_idx" COLLECTION="nw41" TIDREF="i150"
server console.RENDERAS="SECT3"Turning on Hardware and NLM AlertsIDXID="w8468"BOOK="_idx" COLLECTION="nw41" TIDREF="i150"To display alerts about hardware devices and NLM programs, add the following SET commands to the beginning of the STARTUP.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8469"BOOK="_idx" COLLECTION="nw41" TIDREF="i4101"
SET Display Spurious Interrupt Alerts=ON
SET Display Lost Interrupt Alerts=ON
SET Display Relinquish Control Alerts=ON
SET Display Old API Names=ONTo temporarily IDXID="w8470"BOOK="_idx" COLLECTION="nw41" TIDREF="i150"
turn off an alert message display (when it is filling up the console screen, for example), use the SET command to change the relevant parameter setting to OFF. When you reboot the server, the setting is changed to ON again.PAGENUM=488 ID="BP443"RENDERAS="SECT3"Turning on Early Warning Alerts for Cache Buffer Memory AllocationIDXID="w8471"BOOK="_idx" COLLECTION="nw41" TIDREF="i549"IDXID="w8472"BOOK="_idx" COLLECTION="nw41" TIDREF="i570"IDXID="w8473"BOOK="_idx" COLLECTION="nw41" TIDREF="i2392"All memory not allocated for other processes is given to file caching. As memory is requested for other processes, the server gives up file cache buffers. However, there is a minimum number of file cache buffers that cannot be given up. This minimum is specified by the Minimum File Cache Buffers SET parameter.Use the following procedure to specify when the system will warn you that the number of buffers is approaching the minimum level.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "File 
IDXID="w8474"BOOK="_idx" COLLECTION="nw41" TIDREF="i579"
Caching" from the "Categories" menu.PERFORMANCE="REQUIRED"Select Minimum File Cache Buffers.View 
this parameter to learn th
e minimum 
number of file cache buffers currently set.PERFORMANCE="REQUIRED"Choose "Minimum File Cache Report Threshold" from the "File Caching" menu.This parameter specifies how many unused cache buffers must be left above the minimum value for the system to warn you that cache buffers are low
.PERFORMANCE="REQUIRED"Change the parameter value as needed and press 
MOREINFO="NONE"<Enter>.For example, if the Minimum File Cache Buffers parameter is set to 20 and the Minimum File Cache Report Threshold is set to 25, you are warned when all but 45 cache buffers are allocated for other processes
.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.
PAGENUM=489 ID="BP444"A window appears, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file.If you press 
MOREINFO="NONE"<Enter>, the system writes the parameter to the AUTOEXEC.NCF file or updates the parameter if it is already in the file. The file is updated immediately. You do not need to reboot the server.If you do not press 
MOREINFO="NONE"<Enter>, the parameter change lasts only until you reboot the server.RENDERAS="SECT3"Turning on Early Warning Alerts for a Full VolumeIDXID="w8475"BOOK="_idx" COLLECTION="nw41" TIDREF="i150"IDXID="w8476"BOOK="_idx" COLLECTION="nw41" TIDREF="i1584"IDXID="w8477"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"Use this procedure to enable early warning that a volume is nearly full.If a volume is becoming full, you may need to remove unnecessary files or add a new hard disk.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "File System" from the "Categories" menu.PERFORMANCE="REQUIRED"Select "Volume Low Warn All Users" and change the value to ON
.This causes the system to send a warning message to users when a volume is becoming full. The next two steps specify when the warning is sent and when it is remove
d.PERFORMANCE="REQUIRED"Select "Volume Low Warning Threshold" and set it to the desired value.This parameter determines when the system will warn users that the volume is becoming full
.The threshold specifies how much free space, in blocks, must be left on the volume for the warning to be issued.
PAGENUM=490 ID="BP445"PERFORMANCE="REQUIRED"Select "Volume Low Warning Reset Threshold" and set it to the desired value.This parameter determines when the warning will be removed
.It specifies the amount of space that must be freed on the volume for the warning message to be cleared and the warning mechanism to be reset
.For example, both the Volume Low Warning Threshold and the Volume Low Warning Reset Threshold might be set to 256 blocks. In this case, the system sends a warning when 256 blocks of free space is left on the volume. The volume must then gain an additional 256 blocks (for a total of 512 blocks of free space) before the warning message disappears and the warning mechanism is reset
.Once the mechanism is reset, the free space on the volume must dip below 256 blocks again before another warning is sent
.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to update the file
.If you press 
MOREINFO="NONE"<Enter>, the system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file. The file is updated immediately. You do not need to reboot the server.If you do not press 
MOREINFO="NONE"<Enter>, the parameter changes last only until you reboot the server.
PAGENUM=491 ID="BP446"RENDERAS="SECT2"Viewing the Server Error LogIDXID="w8478"BOOK="_idx" COLLECTION="nw41" TIDREF="i1340"IDXID="w8479"BOOK="_idx" COLLECTION="nw41" TIDREF="i2185"IDXID="w8480"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"The server error log is a text file called IDXID="w8481"BOOK="_idx" COLLECTION="nw41" TIDREF="i4417"
SYS$LOG.ERR in the server's SYS_servername:SYSTEM directory. All system messages and IDXID="w8482"BOOK="_idx" COLLECTION="nw41" TIDREF="i150"
alerts that appear on the server console are recorded in the SYS$LOG.ERR file. You should view this file periodically to see what kinds of errors are occurring on your server.NetWare security violations are also recorded in the SYS$LOG.ERR file. Check this file daily if you are concerned about security at your site.You should regularly clear the SYS$LOG.ERR file to keep it from using too much server disk space.You can view the server error log from a workstation using a text editor or from the console usingEDIT.NLM. For more information about using EDIT, see IDREF="FM88816""Editing Text Files from the Server Console" on page 449.You can also view or clear the server error log with the NETADMIN and FILER utilities, as described here.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later.A minimum of 512 KB of memory available on the workstation.Supervisor or equivalent directory right to SYS:SYSTEM.RENDERAS="SECT3"Procedure for NETADMINPERFORMANCE="REQUIRED"At the workstation prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "NetAdmin Options" screen, choose "Manage Object
s."PERFORMANCE="REQUIRED"From the browser, select the Server object whose error file you want to view and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "View or Edit Properties of This Object.
"PAGENUM=492 ID="BP447"PERFORMANCE="REQUIRED"Choose "View Server Error Log File.
"The server error log appears.PERFORMANCE="REQUIRED"To delete or exit the server error log, press 
MOREINFO="NONE"<Esc>.A prompt to clear the error log file appears.PERFORMANCE="REQUIRED"To clear the error log file, choose "Yes."PERFORMANCE="REQUIRED"To exit NETADMIN, press 
MOREINFO="NONE"<Alt>+<F10>.RENDERAS="SECT3"Procedure for FILERPERFORMANCE="REQUIRED"At the workstation prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Available Options" screen, choose "Manage Files and Directories."PERFORMANCE="REQUIRED"From the "Directory Contents" screen, browse the tree to select the SYS: volume on the Server object whose error file you want to view, and press MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose the error log file you want to view.PERFORMANCE="REQUIRED"From the "File Options" screen, choose "View File."The server error log appears.PERFORMANCE="REQUIRED"To exit the server error log, press MOREINFO="NONE"<Esc> twice.PERFORMANCE="REQUIRED"To clear the error log file, be sure the correct filename is highlighted and press MOREINFO="NONE"<Delete>A prompt to clear the error log file appears.PERFORMANCE="REQUIRED"To clear the error log file, choose "Yes."PERFORMANCE="REQUIRED"To exit FILER, press MOREINFO="NONE"<Alt>+<F10>.
PAGENUM=493 ID="BP448"RENDERAS="SECT2"Managing Error Log FilesIDXID="w8483"BOOK="_idx" COLLECTION="nw41" TIDREF="i1340"NetWare creates and maintains three error log files:MARK=BULLETSYS$LOG.ERR, for server errorsVOL$LOG.ERR, for volume errorsTTS$LOG.ERR, for data backed out by the Transaction Tracking SystemTMTo keep error log files from using too much disk space, NetWare 4 includes the following SET parameters:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Server Log File State
SET Server Log File Overflow Size
SET Volume Log File State
SET Volume Log File Overflow Size
SET Volume TTS Log File State
SET Volume TTS Log File Overflow SizeSee "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference for information on using these parameters to limit error log file size.PAGENUM=494 ID="BP449"RENDERAS="SECT2"Checking for Disk ErrorsIDXID="w8484"BOOK="_idx" COLLECTION="nw41" TIDREF="i1118"You should check for disk errors regularly. Any new errors should be cause for concern, because such errors can lead to a failed file system and loss of data.If you check for disk errors regularly, you can replace a disk before it causes data loss.If your server's disk drive performs read-after-write verification and automatically redirects bad blocks, the following procedure does not work. It only works if NetWare does the redirection, using Hot FixTM.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8485"BOOK="_idx" COLLECTION="nw41" TIDREF="i2506"
MONITOR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Disk Information" from the "Available Options" menu.PERFORMANCE="REQUIRED"ID="FM85697"Choose the disk drive you want to check from the "System Disk Drives" menu.The upper part of the screen displays information about the disk device that you selected
, including Hot Fix and Redirected Block statistics
.PERFORMANCE="REQUIRED"Write down the number of 
IDXID="w8486"BOOK="_idx" COLLECTION="nw41" TIDREF="i3715"
Redirected Blocks and the number of Redirection 
IDXID="w8487"BOOK="_idx" COLLECTION="nw41" TIDREF="i478"
Blocks shown in the upper window of the screen.When NetWare cannot reliably write a block of data to the disk, it marks the disk block as bad and writes the data to the 
IDXID="w8488"BOOK="_idx" COLLECTION="nw41" TIDREF="i1699"
Hot Fix Redirection Area.The Redirected Blocks count shown in MONITOR is the number of blocks redirected since the server was installed.The Redirection Blocks count is the number of blocks designated as the Hot Fix Redirection Area.PERFORMANCE="REQUIRED"Evaluate these statistics and proceed according to the following steps.
PAGENUM=495 ID="BP450"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Compare the current number of redirected blocks to the number you recorded the last time you checked this number.If the number of redirected blocks is the same as the previously noted number, you do not need to take any corrective action.If the number of redirected blocks has increased significantly, or if the number of redirected blocks is over half the number of redirection blocks, continue with IDREF="FM77744"Step 5b.If the number of redirected blocks has slightly increased over the previous number, monitor the server closely.PERFORMANCE="REQUIRED"ID="FM77744"Send a message to all users to close files and log out.PERFORMANCE="REQUIRED"Back up the server data and bring down the server.PERFORMANCE="REQUIRED"Troubleshoot the disk drive, driver, controller, and host bus adapter
, using the hardware documentation
.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Data protectionCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Data protection" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"MONITOR utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities ReferenceOnline help in MONITORCOLNAME=1 ROTATE="0" MOREROWS="0"Redirection, Hot Fix, and read- after-write verificationCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Hot Fix" in ConceptsPAGENUM=496 ID="BP451"RENDERAS="SECT2"IDXID="w8489"BOOK="_idx" COLLECTION="nw41" TIDREF="i4468"
Testing for Bad Disk BlocksIDXID="w8490"BOOK="_idx" COLLECTION="nw41" TIDREF="i407"Use the IDXID="w8491"BOOK="_idx" COLLECTION="nw41" TIDREF="i1118"IDXID="w8492"BOOK="_idx" COLLECTION="nw41" TIDREF="i4347"
surface test described in this section to check a NetWare partition's 
hard disk for bad blocks. The IDXID="w8493"BOOK="_idx" COLLECTION="nw41" TIDREF="i478"
surface test runs in the background, so you can access other hard disks during the test.Use the surface test only if your hardware is several years old. Newer hardware is of such reliability that the surface test is not helpful. Problems with newer hardware should be addressed according to the manufacturer's recommendations.Some drivers may not support this test.This test can take several hours.Test for bad blocks when there is no activity on the NetWare server. Otherwise, client workstations connected to the server may hang.You can run two types of tests on a NetWare partition:MARK=BULLETDestructive. This test destroys all data on the hard disk as it reads and writes test patterns. After the test is over, the disk still retains the test patterns. This method is much faster than the nondestructive surface test.Use this procedure if you are planning to install a new NetWare partition and you have backed up the data that is currently on the partition.Nondestructive. This surface test hot fixes the bad blocks. It is much slower than the destructive method, but it protects the data on the disk.This test pre-reads the data on the disk, writes and reads its test patterns, and then restores the original data. The nondestructive test takes 20 percent longer to run than the destructive test.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA NetWare partition to testA backup of all data on the hard disk to be testedAll volumes dismounted on the disk to be testedUnmirrored disk partitionsAll network users logged outPAGENUM=497 ID="BP452"RENDERAS="SECT3"ProcedureComplete the following steps to test your hard disk for bad blocks.PERFORMANCE="REQUIRED"At the server console prompt, dismount each volume on the hard disk by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"DISMOUNT volume_name MOREINFO="NONE"<Enter>Replace 
volume_name with a name of a volume on the disk. Repeat this step for each volume on the disk.PERFORMANCE="REQUIRED"Load 
IDXID="w8494"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "Disk Options" from the "Installation Options" menu.PERFORMANCE="REQUIRED"Select "Perform Surface Test" from the "Available Disk Options" menu.PERFORMANCE="REQUIRED"If you have more than one hard disk on your server, select the disk you want to test from the "Available Disk Drives" list.The system displays a "Disk Surface Test Status" window and a "Surface Test Options" menu, as shown in the following illustration.


FILEREF="n41su71a.tif"
PAGENUM=498 ID="BP453"As the test progresses, the "Test Type" field on the "Disk Surface Test Status" screen can show the following IDXID="w8495"BOOK="_idx" COLLECTION="nw41" TIDREF="i4347"
status information:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"StatusCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NoneCOLNAME=2 ROTATE="0" MOREROWS="0"The partition is not being tested.COLNAME=1 ROTATE="0" MOREROWS="0"DestructiveCOLNAME=2 ROTATE="0" MOREROWS="0"A destructive test was selected. Data on the hard disk will be lost.COLNAME=1 ROTATE="0" MOREROWS="0"NondestructiveCOLNAME=2 ROTATE="0" MOREROWS="0"A nondestructive test was selected. Data on the hard disk will be preserved.COLNAME=1 ROTATE="0" MOREROWS="0"FailedCOLNAME=2 ROTATE="0" MOREROWS="0"A disk error occurred that Hot Fix could not correct.COLNAME=1 ROTATE="0" MOREROWS="0"CompletedCOLNAME=2 ROTATE="0" MOREROWS="0"The test was completed successfully.COLNAME=1 ROTATE="0" MOREROWS="0"TerminatedCOLNAME=2 ROTATE="0" MOREROWS="0"The test was stopped before completion.PERFORMANCE="REQUIRED"Select "Begin Surface Test" from the "Surface Test Options" menu.PERFORMANCE="REQUIRED"Select the type of test to be performed (destructive or nondestructive).Do not exit INSTALL during the test. All testing stops if you exit, and your data may not be preserved.To stop the test before it finishes, select 
"Stop Surface Test
" from the 
"Surface Test Options
" menu. If you select this option, you must start the test from the beginning.To perform other NetWare server operations while the surface test is running (such as testing other hard disks), press MOREINFO="NONE"<Esc> to move to the other options in INSTALL, or press MOREINFO="NONE"<Alt>+<Esc> to go to the console prompt.At the end of the test, the 
"Disk Surface Test Status
" window displays the number of blocks tested, the number of bad blocks found, and the total blocks tested.The 
"Test Type
" field displays "Terminate
d" if the test was stopped before completion, "Faile
d" if a disk error occurred that could not be fixed, or "Complete
d" if the test was successful.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Alt>+<F10> to exit INSTALL.
PAGENUM=499 ID="BP454"RENDERAS="SECT1"ID="FM90777"Maintaining VolumesThis section describes how to create, delete, rename, mount, dismount, and repair NetWare volumes. It also includes procedures for adding volume segments and changing volume size.In NetWare Directory ServicesTM, each volume is also an object in the Directory. When you create a volume with IDXID="w8496"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL.NLM, it puts a IDXID="w8497"BOOK="_idx" COLLECTION="nw41" TIDREF="i4787"
Volume object in the same context as the NetWare Server object within the Directory tree. By default, INSTALL names the Volume object servername_volumename.You can change the context of Volume objects and rename Volume objects with either the NETADMIN text utility or the 
NetWare Administrator graphical utility.To rename or delete a volume, you must use INSTALL to rename or delete the volume on the server, and then use NETADMIN or NetWare Administrator to change the Volume object in the Directory.RENDERAS="SECT2"ID="FM64431"Creating VolumesIDXID="w8498"BOOK="_idx" COLLECTION="nw41" TIDREF="i873"IDXID="w8499"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"With NetWare 4.1, you can create a new volume on any hard disk that has a NetWare 4.1 
partition.You use INSTALL to create volumes.Your NetWare server can have from 1 to 64 NetWare volumes, depending on the needs of your users. NetWare requires only one volume, IDXID="w8500"BOOK="_idx" COLLECTION="nw41" TIDREF="i4394"
SYS:.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA NetWare partition on the disk where you want to create the volumeAn existing volume SYS:PAGENUM=500 ID="BP455"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL <MOREINFO="NONE"Enter>PERFORMANCE="REQUIRED"From the "Installation Options" menu, choose "Volume Options
."If any volumes exist, they are now listed.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert>.The "Volume Disk Segment List" is displayed.PERFORMANCE="REQUIRED"ID="FM82772"Select any existing free space and press 
MOREINFO="NONE"<Enter>.Free space is any NetWare disk partition space to which no volume assignment has been made.By default, a new volume takes up all remaining free space of a NetWare disk partition when it is created. However, you can decrease the volume size to leave some free space on the partition for adding NetWare volumes in the future.If no free IDXID="w8501"BOOK="_idx" COLLECTION="nw41" TIDREF="i1128"
space is available, you must add a new hard disk, or add magneto-optical disk storage, before you can create new volumes.PERFORMANCE="REQUIRED"ID="FM17012"Type a new 
IDXID="w8502"BOOK="_idx" COLLECTION="nw41" TIDREF="i2571"
volume name in the box provided and press 
MOREINFO="NONE"<Enter>.The volume name can be up to 15 characters long (A through Z, 0 through 9, and underscore characters are allowed).The newly created volume now appears in the "Volume Disk Segment List."If you want the new volume to use all of the free disk space, skip t
o IDREF="FM94798"Step 8. If not, continue wit
h IDREF="FM82171"Step 7.PERFORMANCE="REQUIRED"If you don't want the new volume to use all of the free disk space, do the following:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the volume you just created and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Enter a new volume size
, expressed in megabytes (MB), and press 
MOREINFO="NONE"<Enter>.
PAGENUM=501 ID="BP456"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> and save the settings.PERFORMANCE="REQUIRED"To assign the free 
IDXID="w8503"BOOK="_idx" COLLECTION="nw41" TIDREF="i1128"
space you just created to another volume, repea
t IDREF="FM82772"Step 4 an
d IDREF="FM17012"Step 5.PERFORMANCE="REQUIRED"Skip t
o IDREF="FM29031"Step 9.PERFORMANCE="REQUIRED"ID="FM82171"If you want the new volume to use all of the free disk space, either press 
MOREINFO="NONE"<Esc> to continue with other volume tasks or press 
MOREINFO="NONE"<F10> to save volume information to disk.PERFORMANCE="REQUIRED"ID="FM94798"From the menu, choose "Mount/Dismount an Existing Volume
."PERFORMANCE="REQUIRED"ID="FM29031"Choose "Mount
."RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating NetWare disk partitionsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM93483""Creating NetWare Disk Partitions" on page 541COLNAME=1 ROTATE="0" MOREROWS="0"Changing the size of a volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM72455""Modifying the Size of a Volume" on page 512COLNAME=1 ROTATE="0" MOREROWS="0"Adding a hard diskCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83121""Adding a Hard Disk to the NetWare Server" on page 532COLNAME=1 ROTATE="0" MOREROWS="0"Adding magneto-optical disk storageCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM16817"Chapter 6, "Migrating Data Using the High Capacity Storage System"RENDERAS="SECT2"ID="FM76228"Mounting and Dismounting VolumesIDXID="w8504"BOOK="_idx" COLLECTION="nw41" TIDREF="i1143"By mounting a IDXID="w8505"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"
volume, you make its information available to network users. You can mount or dismount one or all volumes while the NetWare server is running.You may want to leave rarely used volumes dismounted because each mounted volume takes up memory and reduces the memory available for file caching.PAGENUM=502 ID="BP457"You can mount and dismount volumes in two ways:MARK=BULLETUse the MOUNT and DISMOUNT console commands. (See "BOOK="utlrfenu" COLLECTION="nw41"MOUNT" and "BOOK="utlrfenu" COLLECTION="nw41"DISMOUNT" in Utilities Reference.)Use IDXID="w8506"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL as described in the following procedure.To mount CD-ROM volumes, use the CD command. For more information, see IDREF="FM57201""Using a CD-ROM as a NetWare Volume" on page 513.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8507"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALLPERFORMANCE="REQUIRED"From the "Installation Options" menu, choose "Volume Options" and press 
MOREINFO="NONE"<Enter>.A list of existing volumes is displayed.PERFORMANCE="REQUIRED"Select the volume you want to mount or 
IDXID="w8508"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"
dismount and press 
MOREINFO="NONE"<Enter>.The "Volume Information" screen is displayed.PERFORMANCE="REQUIRED"Using the arrow keys, highlight the "Status" field
.Depending on the status of the volume, this field displays "Mounted," "Not Mounted," or "New, not mounted."PERFORMANCE="REQUIRED"If the status is "New, not mounted," press 
MOREINFO="NONE"<Esc> and then 
MOREINFO="NONE"<F10> to save volume changes to disk before the volume can be mounted
.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to display a 
menu of available actions.PERFORMANCE="REQUIRED"Depending on your situation, select either "Mount" or "Dismount" and press 
MOREINFO="NONE"<Enter>.NetWare mounts or dismounts your volume.
PAGENUM=503 ID="BP458"If volumes fail to mount, you may not have enough IDXID="w8509"BOOK="_idx" COLLECTION="nw41" TIDREF="i2521"
RAM installed to accommodate the volume. For more information, see IDREF="FM35766""Assessing Server RAM" on page 468.RENDERAS="SECT2"ID="FM71983"ID="FM83010"Deleting VolumesIDXID="w8510"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"Deleting one volume segment deletes all existing data on the volume! You cannot delete only part of a volume.This procedure tells you how to delete an entire volume.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"If the volume you want to delete contains HCSS directories, unload the HCSS media. For information on unloading the media, see IDREF="FM75455""Reformatting Media" on page 411.PERFORMANCE="REQUIRED"Back up the data stored on the volume you want to delete.PERFORMANCE="REQUIRED"Dismount the volume you want to delete.PERFORMANCE="REQUIRED"At the server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8511"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL <MOREINFO="NONE"Enter>PERFORMANCE="REQUIRED"From the "Installation Options" menu, choose "Volume Options
" and press 
MOREINFO="NONE"<Enter>.A list of existing volumes is displayed
.PERFORMANCE="REQUIRED"From the list of existing volumes, select the volum
e you want to delete and pres
s MOREINFO="NONE"<Delete>.A warning similar to the following appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"Volume volume_nameMOREINFO="NONE" may contain valuable data that will be lost if you confirm "Yes" in the box that follows this message and if you save volume changes on exit from the volumes list.MOREINFO="NONE"<Press ENTER to continue>PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> 
if you want to continue.
PAGENUM=504 ID="BP459"PERFORMANCE="REQUIRED"When the "Delete existing volume?" 
prompt appears, select "Yes" and press 
MOREINFO="NONE"<Enter>.Deleting volumes with INSTALL does not affect IDXID="w8512"BOOK="_idx" COLLECTION="nw41" TIDREF="i4787"
Volume objects. You must use NETADMIN or NetWare Administrator to delete Volume objects.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"HCSS volumes COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM16817"Chapter 6, "Migrating Data Using the High Capacity Storage System"COLNAME=1 ROTATE="0" MOREROWS="0"Backing up a volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM49062"Chapter 9, "Backing Up and Restoring Data."COLNAME=1 ROTATE="0" MOREROWS="0"Deleting NDS Volume objectsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM48449""Deleting Objects from the Directory Tree" on page 96COLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator to delete a volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM45304""Deleting Objects Using NetWare Administrator" on page 98COLNAME=1 ROTATE="0" MOREROWS="0"Using NETADMIN to delete a volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM59133""Deleting Objects Using NETADMIN" on page 99RENDERAS="SECT2"ID="FM99112"IDXID="w8513"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"
Renaming VolumesRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Dismount the volume you want to rename.PERFORMANCE="REQUIRED"At the server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8514"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL <MOREINFO="NONE"Enter>PERFORMANCE="REQUIRED"From the "Installation Options" menu, choose "Volume Options
" and press 
MOREINFO="NONE"<Enter>.All existing volumes are listed.PERFORMANCE="REQUIRED"Select the volume whose name you want to change and press 
MOREINFO="NONE"<Enter>.The "Volume Information" screen is displayed.
PAGENUM=505 ID="BP460"PERFORMANCE="REQUIRED"Use the arrow keys t
o highlight the 
"Name
" field
, and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Backspace to erase the old name; then type in a new name and press 
MOREINFO="NONE"<Enter>.Do not change the name of volume SYS: to another name. A volume called SYS: is mandatory.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice; then press 
MOREINFO="NONE"<F10> to save the volume information
.If you have not dismounted the volume i
t is automatically dismounted 
now.PERFORMANCE="REQUIRED"When prompted, answer "Yes" to mount the volume with the new name.PERFORMANCE="REQUIRED"To set the Volume object name and context in NetWare Directory Services, you are prompted to log in to the Directory.PERFORMANCE="REQUIRED"After you log in, verify that the displayed context and Volume object name are correct.Renaming a volume with INSTALL creates a IDXID="w8515"BOOK="_idx" COLLECTION="nw41" TIDREF="i4787"
Volume object with the new name. It does not delete the Volume object with the old name.PERFORMANCE="REQUIRED"Use NETADMIN or NetWare Administrator to delete the old Volume object from the Directory tree
.PAGENUM=506 ID="BP461"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Dismounting volumesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM76228""Mounting and Dismounting Volumes" on page 501COLNAME=1 ROTATE="0" MOREROWS="0"Using the NetWare Administrator to delete the old Volume objectCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM45304""Deleting Objects Using NetWare Administrator" on page 98COLNAME=1 ROTATE="0" MOREROWS="0"Using NETADMIN to delete the old Volume object COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM59133""Deleting Objects Using NETADMIN" on page 99RENDERAS="SECT2"ID="FM43638"Setting Up a Volume to Store Non-DOS FilesIDXID="w8516"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"By default, NetWare volumes support DOS naming conventions. To store non-DOS files (such as for IDXID="w8517"BOOK="_idx" COLLECTION="nw41" TIDREF="i2263"
Macintosh, OS/2IDXID="w8518"BOOK="_idx" COLLECTION="nw41" TIDREF="i3134"
, or IDXID="w8519"BOOK="_idx" COLLECTION="nw41" TIDREF="i4656"
UNIX files) on a NetWare volume, you must load the appropriate IDXID="w8520"BOOK="_idx" COLLECTION="nw41" TIDREF="i2585"
name space NLM and add the add name space support to that volume.Each name space added to a volume requires additional 
server memory. If you add name space support to a volume and do not have enough memory, that volume cannot be mounted.RENDERAS="SECT3"Calculating Memory Required for Name Space SupportIDXID="w8521"BOOK="_idx" COLLECTION="nw41" TIDREF="i1554"Use the following formula to calculate the additional memory required for each added name space on a non-DOS volume:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"0.032 x volume_sizeMOREINFO="NONE"(in MB)/block_sizeMOREINFO="NONE"(in MB)Round the result to the next highest megabyte.For example, adding Macintosh name space to a 100MB volume with a block size of 4 KB would require 1 MB of additional memory, as shown:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"0.032 x 100 MB / 4 = 0.8 MMOREINFO="NONE"B
PAGENUM=507 ID="BP462"RENDERAS="SECT3"Adding a Name SpaceRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA mounted volumeSufficient memoryRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Load the appropriate name space NLM by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD [path]name_space MOREINFO="NONE"<Enter>For example, to load the name space module for Macintosh support, typ
eFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD MAC.NAMMOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Add name space support to the volume by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8522"BOOK="_idx" COLLECTION="nw41" TIDREF="i89"
ADD NAME SPACE name to volume_nameMOREINFO="NONE" <Enter>Replace 
name with the name space NLM. Replace
 volume_name with the name of the volume tha
t will stor
e th
e non-DOS files.For example, to add the Macintosh name space to the MACVOL volume, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"ADD NAME SPACE MAC TO MACVOL MOREINFO="NONE"<Enter>You only need to add a name space to a volume once. You don't need to add it each time the server comes up. The name space module autoloads each time the server comes up.To 
verify that the name space has been added, view a list of all added name spaces by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"ADD NAME SPACE MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"To see a list of current volumes and name spaces, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"VOLUMES MOREINFO="NONE"<EnterMOREINFO="NONE">
PAGENUM=508 ID="BP463"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ADD NAME SPACE commandCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"ADD NAME SPACE" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Name spaceCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Name space support" in ConceptsRENDERAS="SECT3"Removing Name Space SupportIDXID="w8523"BOOK="_idx" COLLECTION="nw41" TIDREF="i2585"IDXID="w8524"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"Once a IDXID="w8525"BOOK="_idx" COLLECTION="nw41" TIDREF="i3134"
name space is added to a volume, the IDXID="w8526"BOOK="_idx" COLLECTION="nw41" TIDREF="i1728"
name space can be IDXID="w8527"BOOK="_idx" COLLECTION="nw41" TIDREF="i2263"IDXID="w8528"BOOK="_idx" COLLECTION="nw41" TIDREF="i4656"
removed either by deleting the volume and re-creating it or by using IDXID="w8529"BOOK="_idx" COLLECTION="nw41" TIDREF="i4802"
VREPAIR.To use the VREPAIR method, see the next section, IDREF="FM90018""Repairing Volumes." To delete a volume, see IDREF="FM71983""Deleting Volumes" on page 503.RENDERAS="SECT2"IDXID="w8530"BOOK="_idx" COLLECTION="nw41" TIDREF="i2585"ID="FM90018"Repairing VolumesIDXID="w8531"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"Typically, you can't mount a volume if it has even minor damage. Occasionally, however, a damaged volume mounts, but causes errors in the process.Use IDXID="w8532"BOOK="_idx" COLLECTION="nw41" TIDREF="i4802"
VREPAIR to correct volume problems or to remove name space entries from IDXID="w8533"BOOK="_idx" COLLECTION="nw41" TIDREF="i1448"
File Allocation Tables (FATs) and IDXID="w8534"BOOK="_idx" COLLECTION="nw41" TIDREF="i1055"
Directory Entry Tables (DETs).You can run VREPAIR on a bad volume while other volumes are mounted. Following are typical instances when VREPAIR can help:MARK=BULLETA hardware failure either prevented a volume from mounting or caused a disk read error.Although VREPAIR can't fix hardware problems, VREPAIR can sometimes fix related volume damage.A power failure caused a corrupted volume.The server console displays a mirroring error when the server boots. This mirroring refers to the two copies of FATs and DETs that the operating system keeps (if disks are mirrored, NetWare keeps four copies).If a volume fails to mount as the server is booting, VREPAIR loads automatically and attempts to repair the volume.PAGENUM=509 ID="BP464"When VREPAIR autoloads, it uses the default options. If you want to use an alternate option, load VREPAIR manually and set the alternate option before running VREPAIR.If you don't want VREPAIR to automatically repair a volume that won't mount, use the "Automatically Repair Bad Volumes" SET parameter to change the default. (See "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.)RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXThe volume you want to repair must be dismounted.If the volume to be repaired has name space support, the corresponding VREPAIR name space module (V_namespace.NLM) must be located in either the SYS:SYSTEM directory or in a search path directory.Example modules include V_MAC.NLM and V_OS2.NLM.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD VREPAIR [volume name] [logfile name]MOREINFO="NONE" <Enter>(Optional) Replace 
volume name with the name of the volume to repair. If there is only one volume that is dismounted, you don't need to specify this parameter, since VREPAIR will attempt to repair that volume
.(Optional
) If you want to save the error log, replace the 
logfile name with the name of the file you want VREPAIR to create. VREPAIR 
creates a log of errors it finds. VREPAIR displays the errors on screen and will write them to a file if you specify a filename.When you load VREPAIR, an "Options" menu is displayed
.PERFORMANCE="REQUIRED"PAGENUM=510 ID="BP465"Accept the default options, or select alternate options, as appropriate.The f
irst time you try to repair a volume
, accept the default options. If the default options fail to repair the volume, select alternate options.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"To accept the default options
, continue with Step 3.PERFORMANCE="REQUIRED"To set alternate options at the "Options" menu, choose "Set VRepair Options" by ty
pingFORMAT="LINESPECIFIC"MOREINFO="NONE"2 MOREINFO="NONE"<Enter>For more information on the options that are displayed, see "BOOK="utlrfenu" COLLECTION="nw41"VREPAIR" in Utilities Reference.PERFORMANCE="REQUIRED"To begin the repair process, choose "Repair A Volume" from the "Options" menu.
MARK=BULLETIf more than one volume is dismounted, select the volume to repair from those listed.If only one volume is dismounted, VREPAIR assumes it is the volume that needs repairing and begins the repair.As the volume is being repaired, the server console screen displays a message indicating VREPAIR activity.PERFORMANCE="REQUIRED"ID="FM77404"(Optional) Modify error log settings after the repair has started
.If VREPAIR finds many errors during the repair process, you might want to chang
e some of th
e run-time error settings. To modify these settings after the repair has started, press 
MOREINFO="NONE"<F1> to display the "Current Error Settings" menu.
MARK=BULLETSelect Option 1 if you do not want VREPAIR to pause after each error.Select Option 2 if you want VREPAIR to log errors in a text file.Select Option 3 to stop the repair of the volume.Select Option 4 to continue with a volume repair after you have stopped it.PERFORMANCE="REQUIRED"When the repair is complete, answer 
"Y
" when prompted to write repairs to the disk.
PAGENUM=511 ID="BP466"PERFORMANCE="REQUIRED"If VREPAIR has found errors, ru
n VREPAIR again by repeating Step
s 2 throug
h 6. Repeat until VREPAIR finds no errors.If you are unable to mount the volume after running VREPAIR a number of times, you must delete the volume, r
e-create the volume usin
g INSTAL
L, and then restore the data fro
m backups.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using VREPAIRCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"VREPAIR" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Dismounting a volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM76228""Mounting and Dismounting Volumes" on page 501COLNAME=1 ROTATE="0" MOREROWS="0"Creating a volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM64431""Creating Volumes" on page 499COLNAME=1 ROTATE="0" MOREROWS="0"Setting the Automatically Repair Bad Volume parameterCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Setting and viewing the console search pathCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"SEARCH" in Utilities ReferenceRENDERAS="SECT2"ID="FM16666"Adding a Segment to an Existing VolumeIDXID="w8535"BOOK="_idx" COLLECTION="nw41" TIDREF="i4011"IDXID="w8536"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAn existing NetWare partition with free space. (To create a NetWare partition. see IDREF="FM93483""Creating NetWare Disk Partitions" on page 541.)RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8537"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Installation Options" menu choose "Volume Options
."PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert> 
or <MOREINFO="NONE"F3> t
o view existing volume segments.PAGENUM=512 ID="BP467"PERFORMANCE="REQUIRED"Select a segment that has free space (no volume assignment) and press 
MOREINFO="NONE"<Enter>.If no free space exists, you can't IDXID="w8538"BOOK="_idx" COLLECTION="nw41" TIDREF="i1128"
add a segment to a volume. PERFORMANCE="REQUIRED"To add this segment to an existing volume, select "Mak
e Thi
s Segmen
t Part o
f Anothe
r Volume" and press 
MOREINFO="NONE"<Enter>.A list of existing volumes appears.PERFORMANCE="REQUIRED"Select the volume you want to add this segment to
, and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Verify that the segment has been added in the "Volume Disk Segment List." Then press 
MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"To save volume assignments to disk, press 
MOREINFO="NONE"<F10>.RENDERAS="SECT2"ID="FM72455"Modifying the Size of a VolumeIDXID="w8539"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"A volume can have multiple segments spanning multiple hard disks. This arrangement allows you to add a hard disk when you need to expand a given volume.You can add segments to a volume without destroying data, but removing any segment from a volume destroys all of the data on the volume.Keep the following requirements in mind if you plan to expand volumes:MARK=BULLETThe maximum number of segments allowed per volume is 32.The maximum number of segments you can create on one hard disk is 8.The maximum number of volumes allowed is 64.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8540"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Installation Options" menu choose "Volume Options
."PAGENUM=513 ID="BP468"All existing volumes are listed.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert>.The 
"Volume Disk Segment
s List
" is displayed.PERFORMANCE="REQUIRED"Select the volume segment to modify and press 
MOREINFO="NONE"<Enter>.The status of that segment is displayed.PERFORMANCE="REQUIRED"From the status display, determine what kind of modification you can do:MARK=BULLETIf the status of the volume segment is "N" (new), you can change the size of the segment. For instructions, see IDREF="FM43810"Step 6.If the status of the volume segment is "E" (existing), you can't change the size of the segment.You can increase the volume size by adding new segments. (See IDREF="FM16666""Adding a Segment to an Existing Volume" on page 511.)If you want to reduce the size of the segment or volume, you must delete the entire volume with all segments, and then re-create the volume. See IDREF="FM83010""Deleting Volumes" on page 503.PERFORMANCE="REQUIRED"ID="FM43810"Type the new volume size in megabytes (or a fraction thereof) on the "Disk Segment Parameters" screen.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice; then press 
MOREINFO="NONE"<F10> to save the settings
.RENDERAS="SECT2"ID="FM57201"IDXID="w8541"BOOK="_idx" COLLECTION="nw41" TIDREF="i2521"
Using a CD-ROM as a NetWare VolumeCDROM allows the NetWare server to use a IDXID="w8542"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"
CD-ROM disc as a NetWare volume.Treat the IDXID="w8543"BOOK="_idx" COLLECTION="nw41" TIDREF="i607"
CD-ROM as a IDXID="w8544"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"
read-only volume. Do not IDXID="w8545"BOOK="_idx" COLLECTION="nw41" TIDREF="i475"
enable IDXID="w8546"BOOK="_idx" COLLECTION="nw41" TIDREF="i607"
block suballocation or use file IDXID="w8547"BOOK="_idx" COLLECTION="nw41" TIDREF="i607"
compressionIDXID="w8548"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"
 on the volume. These actions will corrupt the CD-ROM volume index data.If you do so by mistake, use the CD command to rebuild the volume's index file. For command syntax, see "BOOK="utlrfenu" COLLECTION="nw41"CD" in Utilities Reference or type CD HELP at the server console prompt.NetWare 4.1 supports CD-ROMs that are mounted with the MAC and NFS name spaces.PAGENUM=514 ID="BP469"The CDROM.NLM program supports High Sierra and ISO 9660 formats. It does not support HFS (Apple) file systems.RENDERAS="SECT3"Mounting a CD-ROM as a NetWare VolumeTo mount a CD-ROM disc as a NetWare volume, follow these steps.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXVolume SYS: mountedAn installed host bus adapter (HBA) that is NetWare compatible and supports CD-ROM devicesThere are no serial, parallel, or IDE device drivers for CD-ROM support. Use a SCSI adapter.The NetWare Peripheral ArchitectureTM (NPA) module, IDXID="w8549"BOOK="_idx" COLLECTION="nw41" TIDREF="i3032"
NWPA.NLM.The disk driver file and necessary support modulesSome disk drivers consist of more than one file and some HBA devices require additional support modules for CD-ROM functionality. These files should accompany the HBA. For specific file requirements, consult your adapter documentation.NetWare 4.1 includes the third-party HBA device drivers that are Novell- certified for NetWare 4.1. If the HBA is certified to support CD-ROM devices, the necessary support modules are also included with NetWare.You can copy these files during installation, or you can copy them from the NetWare distribution media using NWXTRACT. (For help, see "BOOK="utlrfenu" COLLECTION="nw41"NWXTRACT" in Utilities Reference.)RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"ID="FM77953"At the server console prompt, load the disk driver by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"  MOREINFO="NONE"LOAD [path]disk_driverMOREINFO="NONE" <Enter>Replace 
disk_driver with the name of the disk driver specified in the HBA documentation.
PAGENUM=515 ID="BP470"You may be prompted to supply command line values such as a port or slot number for the HBA. Consult your HBA documentation for this information.For example, to load the disk driver for the Adaptec AHA-1522 SCSI HBA, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD [path]MOREINFO="NONE"AHA1520.DSK MOREINFO="NONE"<Enter>
  LOAD [
path]ASPICD.DSK
MOREINFO="NONE" <Enter>Some files may be automatically loaded. In this example, ASPITRAN.DSK is automatically loaded whe
n AHA1520.DSK is loaded.If your disk driver autoloads the ASPITRAN.DSK driver, you need to load either one of the following: ASPICD.DSK or CDNASPI.DSK. In this example, we used ASPICD.DSK.PERFORMANCE="REQUIRED"Load the NWPA.NLM (NetWare Peripheral Architecture) driver by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NWPA.NLMMOREINFO="NONE" <Enter>This is the device-independent software that interfaces with the Media Manager.CDROM.NLM will not load unless the NWPA.NLM driver has been loaded. PERFORMANCE="REQUIRED"Loa
d IDXID="w8550"BOOK="_idx" COLLECTION="nw41" TIDREF="i600"
CDRO
M.NLM by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"  LOAD CDROMMOREINFO="NONE" <Enter>When a CD-ROM volume is being mounted or a CD-ROM disc is being changed, CD-ROM devices might be deactivated. Do not be alarmed. This deactivation occurs because device configuration information is being updated.PERFORMANCE="REQUIRED"Mount the CD-ROM as a volume by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"CD MOUNT [object number] | [volume name] [name space] [/option] MOREINFO="NONE"<Enter>The object number is the Media Manager object number (hereafter called the object number).PAGENUM=516 ID="BP471"Replace object number with the object number or replace 
volume name with the volume name of the CD-ROM disc. (You can use the 
CD DEVICE LIST or CD VOLUME LIST command to see the object numbers and volume names.)If appropriate, add name space support for the volum
e by replacing 
name space with
 /MAC or /NFS name space, or use both name spaces.If appropriate, replace 
option with any of the following
MARK=BULLET/R: Rebuilds the index file for a CD-ROM volume./G= group number: Sets the default volume group access rights while mounting the volume./X: Excludes a directory, at the root level, on the CD-ROM./I: Mounts the volume even if importing errors are found and not all files are available.For more information on the CD MOUNT command and its options, see "
BOOK="utlrfenu" COLLECTION="nw41"CD" in 
Utilities Reference.For example, to mount the NetWare_41 CD-ROM, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"CD MOUNT NETWARE_41 MOREINFO="NONE"<Enter>It may take several minutes to mount the volume, depending on the size of the CD-ROM and on the speed of your computer.PERFORMANCE="REQUIRED"(Optional) To mount the CD-ROM as a NetWare volume each time the 
server comes up, do the following:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Edit your STARTUP.NCF file to add the disk driver.For example, to load the driver described in IDREF="FM77953"Step 1, add the following lines to the STARTUP.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"  LOAD [path]disk_driver
LOAD [path]ASPICD.DSK
  LOAD [path]
MOREINFO="NONE" NWPA.NLMIf your disk driver autoloads the ASPITRAN.DSK driver, load either one of the following: ASPICD.DSK or CDNASPI.DSK. In this STARTUP.NCF file example, we used ASPICD.DSK.
PAGENUM=517 ID="BP472"PERFORMANCE="REQUIRED"Edit your AUTOEXEC.NCF by adding the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"  LOAD CDROM
  CD MOUNT [object number] | 
  [volume name] 
  [name space] 
  [option]RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the CD commandCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"CD" in Utilities Reference, or type CD HELP at the consoleCOLNAME=1 ROTATE="0" MOREROWS="0"Using CDROM.NLMCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"CDROM" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Editing .NCF filesCOLNAME=2 ROTATE="0" MOREROWS="0" IDREF="FM33588""Creating or Editing a Server Batch (.NCF) File" on page 448COLNAME=1 ROTATE="0" MOREROWS="0"Novell-certified device drivers for NetWare 4COLNAME=2 ROTATE="0" MOREROWS="0"Call 1-800-NETWARE (1-800-637-9273)RENDERAS="SECT3"Administering a CD-ROM as a NetWare VolumeUsing the CD console commands associated with CDROM, you can do the following:MARK=BULLETMonitor the status of CD-ROM devices and NetWare volumesChange the media in a CD-ROM deviceDisplay the root directory on a NetWare CD-ROM volumeMount and dismount CD-ROM volumesAdd and delete group namesFor information on command syntax and for examples of these procedures, see "BOOK="utlrfenu" COLLECTION="nw41"CD" in Utilities Reference.PAGENUM=518 ID="BP473"You can also typeMOREINFO="NONE"CD HMOREINFO="NONE"ELMOREINFO="NONE"P MOREINFO="NONE"<Enter>at the server console prompt to get information.RENDERAS="SECT1"ID="FM56019"Managing Server Hard DisksIDXID="w8551"BOOK="_idx" COLLECTION="nw41" TIDREF="i1128"This section describes how to determine available disk space, how to increase available disk space by compressing files and purging files, and how to add a hard disk to a NetWare server.RENDERAS="SECT2"Checking Available Disk Space with NDIRIDXID="w8552"BOOK="_idx" COLLECTION="nw41" TIDREF="i1128"IDXID="w8553"BOOK="_idx" COLLECTION="nw41" TIDREF="i2628"You should monitor available disk space regularly and keep a log so you can track disk usage over time. This information helps you make the best use of your disk space management options, such as adding a new hard disk, compressing files, and migrating data to an offline system such as an optical disc library.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later, or OS/2 v2.x.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the workstation, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NDIR volume: /VOL MOREINFO="NONE"<Enter>Statistics for the volume you selected appear on the screen
.For more information about the NDIR utility, see "
BOOK="utlrfenu" COLLECTION="nw41"NDIR" in 
Utilities Reference.PERFORMANCE="REQUIRED"Write down the percentage shown for Space remaining on volume
.PERFORMANCE="REQUIRED"Repeat this procedure weekly for each volume.Tracking this percentage over time helps you predict when a volume may run out of disk space.
PAGENUM=519 ID="BP474"You may want to enter the disk space information into a spreadsheet to create a graph of disk usage over time.RENDERAS="SECT2"ID="FM17385"Using File CompressionIDXID="w8554"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"
File compression allows you to store more information on a server hard IDXID="w8555"BOOK="_idx" COLLECTION="nw41" TIDREF="i1128"
disk.File compression is enabled or disabled at the volume level. Once enabled, it can be turned on and off for individual files and directories by setting compression 
attributes with FLAG, FILER, or the NetWare Administrator graphical utility.See IDREF="FM32479""Setting Compression for a File or Directory" on page 521.When you install NetWare 4.1, the default is to enable file compression. However, you can override the default and disable file compression during installation.If you disable file compression, you can enable it later. Once enabled, however, file compression cannot be turned off unless you first re-create the volume.RENDERAS="SECT3"Managing File Compression on Files and DirectoriesIt isn't necessary to separate applications from data for file compression, because the Days Untouched Before Compression SET parameter can eliminate the compression of applications that are used regularly.This parameter specifies the number of days that must pass without access to a file before the file can be compressed. The parameter uses the last accessed date to gauge whether a file should be compressed or not.To avoid the overhead of IDXID="w8556"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"
uncompressing files that don't compress well, the system calculates the compressed size of a file before actually compressing it.If no disk space will be saved by compression, or if the size difference does not meet the value specified by the Minimum Percentage Compression Gain SET parameter, the file is not compressed.For a file to be IDXID="w8557"BOOK="_idx" COLLECTION="nw41" TIDREF="i1128"
uncompressed, there must be enough free space on the volume to accommodate the uncompressed file size.PAGENUM=520 ID="BP475"RENDERAS="SECT2"Enabling File Compression on a VolumeIDXID="w8558"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"When you install NetWare or create a new volume, file compression is enabled by default. You may override the default and disable file compression when the volume is created.The following procedure explains how to enable file compression on a volume for which compression was disabled.Once file compression is enabled for a volume, you can't disable it unless you first re-create the volume.If you have a CD-ROM volume mounted as a NetWare volume, you should treat it as a IDXID="w8559"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"
read-only volume.Do not use file IDXID="w8560"BOOK="_idx" COLLECTION="nw41" TIDREF="i607"
compressionIDXID="w8561"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"
 on a CD-ROM volume. This will corrupt the CD-ROM volume index data. If you do so by mistake, use the CD command to rebuild the volume's index file. For command syntax, see "BOOK="utlrfenu" COLLECTION="nw41"CD" in Utilities Reference.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOX1 MB of available RAM on the server during the time file compression is running.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "Volume Options" from the "Installation Options" menu.A list of volumes appears.PERFORMANCE="REQUIRED"Select the volume for which you want to enable file compression.The Volume Information screen appears, showing the current settings for the volume.PERFORMANCE="REQUIRED"Use the Down-arrow key to move the cursor to the File Compression field and press 
MOREINFO="NONE"<Enter>. Change the setting from Off to On.
PAGENUM=521 ID="BP476"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to save the new value and redisplay the Installation Options menu.RENDERAS="SECT2"ID="FM32479"Setting Compression for a File or DirectoryIDXID="w8562"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"Once file compression is enabled for a volume, turn it on or off for individual files and directories by using FLAG, FILER, or NetWare Administrator.You may want to IDXID="w8563"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"
group the files you want to compress into different directories from those you don't want to compress. For example, if you have data you don't access often, such as quarterly reports, you can create a directory called QUARTER and set it for immediate compression. Then when files are moved into the QUARTER directory, they stay compressed until the next report time, taking up much less disk space.RENDERAS="SECT3"Using FLAG to Set Compression AttributesYou can use the FLAG utility from a workstation to set attributes for a directory or file. The attributes are Immediate Compress (IC) and Don't Compress (DC).RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later, or OS/2 v2.xFile compression enabled for the volumeModify File or Directory right to the file or directory you are settingRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the workstation, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8564"BOOK="_idx" COLLECTION="nw41" TIDREF="i1519"
FLAG MOREINFO="NONE"<Enter>The attributes for the current drive appear
.If you are not in the directory where you want to set the file compression attributes, enter the drive letter or the complete path after the FLAG command.
PAGENUM=522 ID="BP477"PERFORMANCE="REQUIRED"Enter the file compression option you want to apply to the file or directory.For example, if you want the files in the subdirectory LETTERS to b
e compressed each time a file is created or moved into the directory, type
 the Immediate Compress option:FORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG SYS:DOC\LETTERS IC MOREINFO="NONE"<Enter>If you have an APPS directory for files that you do not want compressed at any time, type
 the Don't Compress option:FORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG SYS:APPS DC MOREINFO="NONE"<Enter>For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.RENDERAS="SECT3"Using FILER to Set Compression AttributesYou can set file compression attributes with the FILER menu utility. The attributes are Immediate Compress (IC) and Don't Compress (DC).Online help appears at the bottom of each screen to help you use FILER, and you can press MOREINFO="NONE"<F1> for more detailed help.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later.A minimum of 512 KB of memory available on the workstation.File compression enabled for the volume.Modify File or Directory right to the file or directory you are setting.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the workstation, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FILER MOREINFO="NONE"<Enter>A list of available options appears.
PAGENUM=523 ID="BP478"PERFORMANCE="REQUIRED"Select "Manage Files and Directories" from the "Available Options" menu and press 
MOREINFO="NONE"<Enter>.A list of files appears in the "Directory Contents" window.PERFORMANCE="REQUIRED"Select the file you want to set file compression attributes for, and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Select "View/Set File Information" from the "File Options" menu and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Select the "Attributes" list in the "File Information" display and press 
MOREINFO="NONE"<Enter>.The "Current File Attributes" window appears.PERFORMANCE="REQUIRED"Pres
s MOREINFO="NONE"<Insert> t
o see other file attributes.PERFORMANCE="REQUIRED"Select "Immediate Compress" or "Don't Compress" from the "Other File Attributes" window and press 
MOREINFO="NONE"<Esc>.The compression attribute you selected (Ic or Dc) appears in the attributes list.PERFORMANCE="REQUIRED"To exit FILER, press 
MOREINFO="NONE"<Alt>MOREINFO="NONE"+MOREINFO="NONE"<F10>.RENDERAS="SECT3"Using NetWare Administrator to Set Compression AttributesYou can set file compression attributes with the NetWare Administrator. The attributes are Immediate Compress (IC) and Don't Compress (DC).RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running NetWare Administrator6 MB of available RAM on the Windows workstation, or 12 MB of available RAM on the OS/2 workstationFile compression enabled for the volumeModify File or Directory right to the file or directory you are settingPAGENUM=524 ID="BP479"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "NetWare Administrator" icon from the Windows Program Manager or the OS/2 desktop.PERFORMANCE="REQUIRED"Select the file you want to set file compression attributes for
.To see a file in the NetWare Administrator, choose a volume object and then choose the directory the file resides in.PERFORMANCE="REQUIRED"From the "Object" menu, choose "Details
."PERFORMANCE="REQUIRED"Choose the "Attributes" button
.PERFORMANCE="REQUIRED"From the "File Attributes" list, choose "Immediate Compress" or "Don't Compres
s."PERFORMANCE="REQUIRED"Choose "OK."RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Changing SET parametersCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"SET" and "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"File compressionCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"File compression" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Viewing file compression attributes for a directory or a fileCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM57663""Viewing Other Information about a Directory or File" on page 162"BOOK="utlrfenu" COLLECTION="nw41"FLAG" and "BOOK="utlrfenu" COLLECTION="nw41"NDIR" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Viewing file sizeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM57663""Viewing Other Information about a Directory or File"on page 162"BOOK="utlrfenu" COLLECTION="nw41"FILER" and "BOOK="utlrfenu" COLLECTION="nw41"NDIR" in Utilities ReferencePAGENUM=525 ID="BP480"RENDERAS="SECT2"ID="FM52541"Suspending File CompressionIDXID="w8565"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"You can suspend file compression temporarily by using the Enable File Compression  SET parameter. Follow this procedure.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, load SERVMAN by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"   Select 
"File System
" from the "Categories" menu.PERFORMANCE="REQUIRED"Select 
"Enable File Compression
" and change the value to OFF.If this parameter is set to OFF, any files that would normally be compressed are queued and will be compressed as soon as the parameter is reset to ON.If you have many files to compress, server performance may be affected when you turn file compression back on. If so, make sure you set file compression to be activated during nonpeak hours.
 See the Compression Daily Check Stop Hour and the Compression IDXID="w8566"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"
Daily Check Starting Hour parameters in IDREF="FM81531"Table 7-3.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to display the 
"Update Options
" menu
.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.You are prompted to update the STARTUP.NCF file
.PERFORMANCE="REQUIRED"If the SET parameters are in the STARTUP.NCF file, press 
MOREINFO="NONE"<Enter> to update the values in the file. Otherwise
, press
MOREINFO="NONE" <Esc>.You are prompted to update the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If the SET parameters are in the AUTOEXEC.NCF file, press 
MOREINFO="NONE"<Enter> to update the values. Otherwise, press 
MOREINFO="NONE"<Esc>.Changes to the parameters take effect immediately
.PAGENUM=526 ID="BP481"If you do not update either of the .NCF files, changes to the parameters last only until you reboot the server
.RENDERAS="SECT2"Using SET to Control File CompressionIDXID="w8567"BOOK="_idx" COLLECTION="nw41" TIDREF="i4101"IDXID="w8568"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"You can control various aspects of file compression by using the file compression SET parameters. For example, the Compression Daily Check Starting Hour parameter determines when the file compressor begins scanning volumes for files that need to be compressed. File compression SET parameters do not affect volumes on which compression is disabled.To change SET parameters, execute the SET command at the server console prompt, or use the SERVMAN utility.For more information about executing the SET command, see IDREF="FM64476""Using the SET Command to Change File Compression SET Parameters" on page 528.For more information about using SERVMAN, see IDREF="FM81811""Using SERVMAN to Change File Compression SET Parameters" on page 529.In most cases, the default values for the SET parameters are the most efficient. We recommend you read this section before changing the default values.Add the file compression SET parameters to your IDXID="w8569"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"
AUTOEXEC.NCF or STARTUP.NCF file so that they are executed whenever the server is brought up.You can use EDIT or INSTALL to edit the AUTOEXEC.NCF or the STARTUP.NCF file. You can use SERVMAN to change the value of parameters already in either file.PAGENUM=527 ID="BP482"IDREF="FM81531"Table 7-3 lists the file compression SET parameters and their default values. The settings apply to all files and directories in compression-enabled volumes on the server. For more detailed information about SET parameters, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.LABEL="7-3" PGWIDE=1 TOCENTRY="1"ID="FM81531" SET Parameters for File CompressionCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"SET Parameter and DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Compression Daily Check Stop Hour=6 (6:00 a.m.)COLNAME=2 ROTATE="0" MOREROWS="0"Sets the hour when the file compressor stops scanning volumes for files that need to be compressed. Hours are specified by a 24-hour clock. Supported values: 0 to 23.COLNAME=1 ROTATE="0" MOREROWS="0"Compression IDXID="w8570"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"
Daily Check Starting Hour=0 (midnight)COLNAME=2 ROTATE="0" MOREROWS="0"Sets the hour when the file compressor starts scanning volumes for files that need to be compressed. Hours are specified by a 24-hour clock. Supported values: 0 to 23.COLNAME=1 ROTATE="0" MOREROWS="0"Minimum Compression Percentage Gain=2 (%)COLNAME=2 ROTATE="0" MOREROWS="0"Specifies the minimum percentage a file must compress in order to remain compressed.COLNAME=1 ROTATE="0" MOREROWS="0"Enable File Compression=ONCOLNAME=2 ROTATE="0" MOREROWS="0"Allows file compression to occur on compression-enabled volumes. If you set this parameter to OFF, compression is suspended temporarily. Files flagged for compression are queued until the parameter is reset to ON.COLNAME=1 ROTATE="0" MOREROWS="0"Maximum Concurrent Compressions=2COLNAME=2 ROTATE="0" MOREROWS="0"Specifies the number of volumes that can compress files at the same time. Increasing this setting may slow server performance.COLNAME=1 ROTATE="0" MOREROWS="0"Convert Compressed To Uncompressed Option=1COLNAME=2 ROTATE="0" MOREROWS="0"Determines how the server stores a file after the file has been accessed.MARK=BULLETOption 0 always leaves the file compressed.Option 1 leaves the file compressed after the first access since a file compression. The second access leaves the file uncompressed.Option 2 always leaves the file uncompressed.COLNAME=1 ROTATE="0" MOREROWS="0"Decompress Percent Disk Space Free To Allow Commit=10(%)COLNAME=2 ROTATE="0" MOREROWS="0"Specifies the percentage of free disk space required on a volume before committing an uncompressed file to disk. This prevents newly uncompressed files from filling up the volume.COLNAME=1 ROTATE="0" MOREROWS="0"Decompress Free Space 
Warning Interval=31 minutes 18.5 secondsCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the interval for displaying warning alerts when the volume has IDXID="w8571"BOOK="_idx" COLLECTION="nw41" TIDREF="i150"
insufficient free IDXID="w8572"BOOK="_idx" COLLECTION="nw41" TIDREF="i1128"
disk space for uncompressed files. To turn off the alerts, set the parameter to 0.COLNAME=1 ROTATE="0" MOREROWS="0"Deleted Files Compression Option=1COLNAME=2 ROTATE="0" MOREROWS="0"Determines how the server handles unpurged deleted files.MARK=BULLETOption 0 doesn't compress deleted files.Option 1 compresses deleted files during the next search.Option 2 compresses deleted files immediately.COLNAME=1 ROTATE="0" MOREROWS="0"Days Untouched Before Compression=7COLNAME=2 ROTATE="0" MOREROWS="0"Specifies the number of days that must pass with no access to the file before the file can be compressed.PAGENUM=528 ID="BP483"RENDERAS="SECT3"ID="FM64476"Using the SET Command to Change File Compression SET ParametersIDXID="w8573"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXFile compression enabled for the volumeRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, use the following format to set a file compression parameter:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET parameter = value MOREINFO="NONE"<Enter>For example, the following command specifies 6 
am as the time when the system stops scanning for files to compress:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Compression Daily Check Stop Hour = 6 MOREINFO="NONE"<Enter>For more information, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.
PAGENUM=529 ID="BP484"RENDERAS="SECT3"ID="FM81811"Using SERVMAN to Change File Compression SET ParametersIDXID="w8574"BOOK="_idx" COLLECTION="nw41" TIDREF="i4083"IDXID="w8575"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXFile compression enabled for the volumeRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "File System" from the "Categories" menu.PERFORMANCE="REQUIRED"Change the values of the compression parameters in the "File System" menu as desired.Be sure to press 
MOREINFO="NONE"<Enter> after each change you make.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.You are prompted to update the STARTUP.NCF file
.PERFORMANCE="REQUIRED"If the SET parameters are in the STARTUP.NCF file, press 
MOREINFO="NONE"<Enter> to update the values in the file. Otherwise press
MOREINFO="NONE" <Esc>.You are prompted to update the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If the SET parameters are in the AUTOEXEC.NCF file, press 
MOREINFO="NONE"<Enter> to update the values. Otherwise, press 
MOREINFO="NONE"<Esc>.Changes to the parameters take effect immediately. You do not need to reboot the server.PAGENUM=530 ID="BP485"RENDERAS="SECT2"Purging Files from a DiskIDXID="w8576"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"Purging deleted files frees disk space on the NetWare server's hard disk. You can purge files manually, or you can set up automatic purging.Purged files cannot be salvaged. RENDERAS="SECT3"Manually Purging FilesTo purge deleted files manually, use the NetWare Administrator graphical utility, or the FILER or PURGE text utility. See IDREF="FM26561""Purging Files" on page 170.RENDERAS="SECT3"ID="FM34837"Setting Up Automatic Purging with SERVMANIDXID="w8577"BOOK="_idx" COLLECTION="nw41" TIDREF="i4083"IDXID="w8578"BOOK="_idx" COLLECTION="nw41" TIDREF="i985"
To set up automatic purging of all files on a NetWare server's hard disk, use the SERVMAN utility as described in this section.You can also use the SET utility to set each of the relevant SET parameters manually. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "File System" from the "Categories" menu.PERFORMANCE="REQUIRED"Change the following parameters 
in the "File System" menu to the indicated values:These settings cause the system to purge deleted files immediately. Therefore, the files cannot be salvaged. Be sure you have backups of important files.FORMAT="LINESPECIFIC"MOREINFO="NONE"Immediate Purge Of Deleted Files=ON
File Delete Wait Time=0
Minimum File Delete Wait Time=0
PAGENUM=531 ID="BP486"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu
MOREINFO="NONE".The system displays the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file.The new parameter values take effect immediately. You do not need to reboot the server.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Purging filesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Salvageable files" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Using the FILER utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using the PURGE utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"PURGE" in Utilities ReferenceRENDERAS="SECT2"Adding Optical Storage for File MigrationThe High Capacity Storage System (HCSS) extends the storage capacity of a NetWare server by integrating one or more optical library units, or jukeboxes, into the NetWare file system.HCSS moves files between the server's hard disk and optical disks in a jukebox. HCSS uses hard disk free space to cache the files stored on optical disk. When the hard disk free space reaches a configurable threshold, HCSS migrates files to optical disk.If you have installed an HCSS system on your network, you can set it to use as much or as little of the server's hard disk space as you want.HCSS procedures are described in IDREF="FM16817"Chapter 6, "Migrating Data Using the High Capacity Storage System."COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"HCSS functionalityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"High Capacity Storage System" and "BOOK="cncptenu" COLLECTION="nw41"Data migration" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"HCSS installation and operating proceduresCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM16817"Chapter 6, "Migrating Data Using the High Capacity Storage System"PAGENUM=532 ID="BP487"RENDERAS="SECT2"ID="FM83121"Adding a Hard Disk to the NetWare ServerThe procedures in this section explain how to add the following:MARK=BULLETAn additional IDE hard disk (IDREF="FM54321""Adding an Additional IDE Hard Disk" on page 532)An internal SCSI hard disk and adapter (IDREF="FM78084""Adding an Internal SCSI Hard Disk and Adapter" on page 533)A SCSI hard disk to an existing 
subsystem (IDREF="FM66497""Adding a SCSI Hard Disk to a Subsystem" on page 535)Select the procedure that fits your situation.RENDERAS="SECT3"ID="FM54321"ID="FM66971"Adding an Additional IDE Hard DiskTo add an additional internal 
IDE hard disk, complete the following steps.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXAll users logged out of the serverAccess to the documentation that came with the hard diskAccess to the documentation that came with the computerRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Bring down the server by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>
EXIT 
MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Turn off power to the server.PERFORMANCE="REQUIRED"Install and cable the hard disk.
PAGENUM=533 ID="BP488"Make sure that the jumpers are configured so that one disk is the master and one the slave.Refer to the documentation that came with the hard disk for more information.PERFORMANCE="REQUIRED"Configure the computer to recognize the new disk.For example, you may need to run the CMOS or EISA configuration utility. Refer to the documentation that came with the computer for information about configuration methods and requirements.PERFORMANCE="REQUIRED"Reboot the server.PERFORMANCE="REQUIRED"At the server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Use INSTALL to create a NetWare partition.If you need help, see 
IDREF="FM93483""Creating NetWare Disk Partitions" on page 541.PERFORMANCE="REQUIRED"Create a new volume or designate the partition as a new segment of an existing volume.If you need help, see 
IDREF="FM64431""Creating Volumes" on page 499 or 
IDREF="FM16666""Adding a Segment to an Existing Volume" on page 511.RENDERAS="SECT3"ID="FM78084"Adding an Internal SCSI
 Hard Disk and AdapterTo install an internal SCSI hard disk and new adapter, complete the following steps.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXAll users logged out of the serverAccess to the documentation that came with the hard disk and adapter boardAccess to the documentation that came with the computerPAGENUM=534 ID="BP489"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Bring down the server by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>
EXIT 
MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Turn off power to the server.PERFORMANCE="REQUIRED"Configure and install the new adapter.
MARK=BULLETSome adapters require you to set jumpers as part of the configuration process. Set jumpers on the adapter if necessary. Refer to the documentation that came with the board to learn what jumper settings may be required.Make sure both ends of the SCSI bus are terminated. Refer to the documentation that came with the adapter for more information.PERFORMANCE="REQUIRED"Install the hard disk, connect the power cable to the disk, and cable the disk to the new adapter.PERFORMANCE="REQUIRED"If necessary, configure the computer to recognize the new disk and adapter.Refer to the documentation that came with the computer for more information about configuration methods and requirements.PERFORMANCE="REQUIRED"Reboot the server.PERFORMANCE="REQUIRED"At the server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Use INSTALL to load the disk driver.For more information about loading drivers, see 
IDREF="FM93561""Loading Disk Drivers" on page 538.PERFORMANCE="REQUIRED"Use INSTALL to create a NetWare 

partition.If you need help, see 
IDREF="FM93483""Creating NetWare Disk Partitions" on page 541.
PAGENUM=535 ID="BP490"PERFORMANCE="REQUIRED"Do one of the following step
s:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Mirror the disk.For information about disk mirroring, see IDREF="FM88385""Mirroring and Duplexing a Hard Disk" on page 544.PERFORMANCE="REQUIRED"Create a new volume.If you need help, see IDREF="FM64431""Creating Volumes" on page 499.PERFORMANCE="REQUIRED"Designate the partition as a new segment of an existing volume.See IDREF="FM16666""Adding a Segment to an Existing Volume" on page 511.RENDERAS="SECT3"ID="FM66497"Adding a SCSI Hard Disk to a SubsystemA subsystem contains additional hard disks. To add a SCSI hard disk to an existing adapter in a subsystem, complete the following steps.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXAll users logged out of the systemAccess to the documentation that came with the hard diskAccess to the documentation that came with the computerRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Bring down the server by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>
EXIT 
MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Turn off power to the subsystem.PERFORMANCE="REQUIRED"Install the hard disk and cable it to the adapter.PERFORMANCE="REQUIRED"Set the SCSI ID for the drive and terminate the SCSI bus.Refer to the documentation that came with the hard disk for more information about SCSI IDs and termination requirements
.PAGENUM=536 ID="BP491"PERFORMANCE="REQUIRED"Turn on the power to the disk subsystem.PERFORMANCE="REQUIRED"Reboot the server.PERFORMANCE="REQUIRED"At the server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Use INSTALL to create a NetWare 

partition.If you need help, see 
IDREF="FM93483""Creating NetWare Disk Partitions" on page 541.PERFORMANCE="REQUIRED"Do one of the following steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Mirror the disk.For information about disk mirroring, see IDREF="FM88385""Mirroring and Duplexing a Hard Disk" on page 544.PERFORMANCE="REQUIRED"Create a new volume.If you need help, see IDREF="FM64431""Creating Volumes" on page 499.PERFORMANCE="REQUIRED"Designate the partition as a new segment of an existing volume.See IDREF="FM16666""Adding a Segment to an Existing Volume" on page 511.RENDERAS="SECT2"Replacing a Hard DiskIf a hard disk becomes unreliable or unusable, follow this procedure to remove the disk from the network.Once you start this procedure, you must complete it; otherwise, the system hangs as it looks for the missing hard disk.If you have been backing up your data consistently and verifying its integrity, you will be able to reload data for the volumes affected by the disk failure.PAGENUM=537 ID="BP492"Although some hard disks (called "hot plug" devices) can be removed while the system is running, we do not recommend this practice.If you do try to replace a mirrored hot-plug disk while the system is running, you must unmirror the disk first or run SCAN FOR NEW DEVICES as soon as the disk is removed. Failure to do one of these steps could cause the loss of all data on the disk's mirrored partner when you install the replacement disk.See IDREF="FM63930""Unmirroring Hard Disks" on page 547 and "BOOK="utlrfenu" COLLECTION="nw41"SCAN FOR NEW DEVICES" in Utilities Reference.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Make a backup copy of the data on the hard disk and verify its validity.Make sure the backup copy contains uncorrupted versions of all files and directories on the hard disk.PERFORMANCE="REQUIRED"If the disk is mirrored, dismount the volumes that reside on the disk by using either the DISMOUNT command or the INSTALL NLM.
MARK=BULLETTo use DISMOUNT, repeat the following command for each volume on the disk and then go to IDREF="FM38318"Step 3.FORMAT="LINESPECIFIC"MOREINFO="NONE"DISMOUNT [volume_name] MOREINFO="NONE"<Enter>To dismount the volume using INSTALL, follow the procedure in IDREF="FM76228""Mounting and Dismounting Volumes" on page 501. Repeat the process for all remaining volumes on the disk and then continue with IDREF="FM38318"Step 3.PERFORMANCE="REQUIRED"ID="FM38318"Unmirror the hard disk if it is mirrored.See 
IDREF="FM63930""Unmirroring Hard Disks" on page 547.PERFORMANCE="REQUIRED"At the server console, 
bring down the server by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>
EXIT 
MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Turn off the system containing the hard disk to be replaced.
PAGENUM=538 ID="BP493"PERFORMANCE="REQUIRED"Remove the hard disk and install the replacement.Use the instructions that came with the hard disk and see 
IDREF="FM83121""Adding a Hard Disk to the NetWare Server" on page 532.PERFORMANCE="REQUIRED"Turn on power and reboot the server.PERFORMANCE="REQUIRED"If the replacement disk has been used before, delete any existing partitions on the replacement disk.Deleting disk partitions destroys all data on the deleted partitions. Be sure you delete the partitions on the new disk, not an existing disk.PERFORMANCE="REQUIRED"Create a partition on the replacement disk.See 
IDREF="FM93483""Creating NetWare Disk Partitions" on page 541.PERFORMANCE="REQUIRED"Complete one of the following steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If the disk was not mirrored, create the volumes that previously resided on the hard disk and restore the data from a backup.See IDREF="FM64431""Creating Volumes" on page 499.PERFORMANCE="REQUIRED"If the hard disk was mirrored, remirror the disk.See IDREF="FM88385""Mirroring and Duplexing a Hard Disk" on page 544.If you replaced the "Not Mirrored" disk rather than the "Out of Sync" disk, recover the volume data from the "Out of Sync" disk before remirroring the disks.RENDERAS="SECT2"ID="FM93561"Loading Disk DriversIDXID="w8579"BOOK="_idx" COLLECTION="nw41" TIDREF="i1115"IDXID="w8580"BOOK="_idx" COLLECTION="nw41" TIDREF="i2153"After you add or replace a hard disk on your NetWare server, you must load the corresponding disk driver.Loading a disk driver enables communication between the disk controller and the server's CPU.Load the disk driver once for each adapter you want to support.PAGENUM=539 ID="BP494"Most NetWare 4 disk drivers have a IDXID="w8581"BOOK="_idx" COLLECTION="nw41" TIDREF="i999"
description file that appears on the screen as you select the driver. Refer to these descriptions or to IDREF="FM70552"Table 7-4 to determine which driver to load.LABEL="7-4" PGWIDE=1 TOCENTRY="1"IDXID="w8582"BOOK="_idx" COLLECTION="nw41" TIDREF="i1115"ID="FM70552" NetWare Disk DriversCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="6*"COLNAME=3 COLWIDTH="5*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Computer architectureCOLNAME=2 ROTATE="0" MOREROWS="0"Device InterfaceCOLNAME=3 ROTATE="0" MOREROWS="0"Disk driverVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Industry Standard Architecture (ISA)COLNAME=2 ROTATE="0" MOREROWS="0"AT, ESDI, MFMIDE (ATA)SCSIISA Vendor ProprietaryCOLNAME=3 ROTATE="0" MOREROWS="0"ISADISKIDESCSISee VendorCOLNAME=1 ROTATE="0" MOREROWS="0"Microchannel (MCA)COLNAME=2 ROTATE="0" MOREROWS="0"ESDI (PS/2)IBM SCSICOLNAME=3 ROTATE="0" MOREROWS="0"PS2ESDIPS2SCSICOLNAME=1 ROTATE="0" MOREROWS="0"Extended Industry Standard Architecture (EISA)COLNAME=2 ROTATE="0" MOREROWS="0"AT classIDE (ATA)SCSIEISA Vendor ProprietaryCOLNAME=3 ROTATE="0" MOREROWS="0"ISADISKIDESCSISee VendorCOLNAME=1 ROTATE="0" MOREROWS="0"Peripheral Component Interconnect(PCI)COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"See VendorCOLNAME=1 ROTATE="0" MOREROWS="0"Personal Computer Memory Card International Association (PCMCIA)COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"See VendorFor maximum performance, use the ISADISK driver only if your interface is the old-style AT, EDSI or MFM.RENDERAS="SECT3"ProcedureIDXID="w8583"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"PERFORMANCE="REQUIRED"At the server console prompt, load INSTALL by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "Driver Options" from the "Installation Options" menu.
PAGENUM=540 ID="BP495"PERFORMANCE="REQUIRED"Choose "Configure Disk and Storage Device Drivers" from the "Driver Options" menu.PERFORMANCE="REQUIRED"Choose "Load an Additional Driver" from the "Additional Drivers Actions" menu.PERFORMANCE="REQUIRED"Select the disk driver you want to load and press 
MOREINFO="NONE"<Enter>.For example, if you are using an AT controller, the disk driver filename is ISADISK.DSK and its description filename is ISADISK.DDI.Some drivers do not have a description file (a configuration file that's appended to the driver). These drivers have to be loaded manually, at the system console. To load these drivers, follow the screen prompts or press MOREINFO="NONE"<F1> for help.PERFORMANCE="REQUIRED"Choose "Select/Modify Driver Parameters."The cursor becomes active in the parameter window for the selected driver. Default parameters may be displayed in the fields.PERFORMANCE="REQUIRED"Use the arrow keys to move from field to field. Press MOREINFO="NONE"<Enter> to change a value in a field. When you move the cursor to a field, the system displays a help window that describes the field. When you press MOREINFO="NONE"<Enter> to change a value, the system usually displays a pop-up list of values from which you select the desired one.PERFORMANCE="REQUIRED"When finished setting parameter values, press MOREINFO="NONE"<F10MOREINFO="NONE">.PERFORMANCE="REQUIRED"Select "Save Parameters and Load Driver."The system displays a message asking if you want to load another driver.PERFORMANCE="REQUIRED"ID="FM79238"If yo
u want to load an additional driver
, select "Yes" and repeat Step
s 5 throug
h 9.You can load the same driver more than once if you have additional disk controller boards of the same type. (Remember to check controller board settings for conflicts).PERFORMANCE="REQUIRED"To exit INSTALL, press 
MOREINFO="NONE"<Alt>+<F10>.
PAGENUM=541 ID="BP496"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Expansion bus computer architectureCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Expansion bus" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"SCSI or IDE busesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"SCSI bus" and "BOOK="cncptenu" COLLECTION="nw41"IDE" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Novell-certified device drivers for NetWare 4COLNAME=2 ROTATE="0" MOREROWS="0"Call 1-800-NETWARE (1-800-637-9273)RENDERAS="SECT2"ID="FM93483"Creating NetWare Disk PartitionsIDXID="w8584"BOOK="_idx" COLLECTION="nw41" TIDREF="i873"IDXID="w8585"BOOK="_idx" COLLECTION="nw41" TIDREF="i3236"
NetWare partitions can be created on any hard drive and can coexist with other partitions such as DOS, OS/2, and UNIX.If you have partitions from previous versions of NetWare that you are no longer using, you can delete them and create a new NetWare partition. (See IDREF="FM13449""Deleting NetWare Disk Partitions" on page 543 for more information.)Some machine vendors such as COMPAQ* create a small partition that setup and configuration utilities can be run from. Don't delete this partition.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"IDXID="w8586"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "Disk Options" from the "Installation Options" menu.PERFORMANCE="REQUIRED"Select "Modify Disk Partitions and Hot Fix" from the "Available Disk Options" menu.If you have more than one disk, the 
"Available Disk Drives
" list appears
. If thi
s list appears, select the disk you want to partition.A list of existing partitions appears, along with the 
"Disk Partition Options
" menu.PERFORMANCE="REQUIRED"Select "Create NetWare Disk Partition" from the "Disk Partition Options" menu.
PAGENUM=542 ID="BP497"NetWare allows only one NetWare partition per disk (unless the machine vendor presents multiple hard drives as one logical drive). If the disk has more than one free partition area, select an area for the NetWare partition.A screen containing disk partition and Hot Fix information with their default values appears. The cursor is on the 
"Partition Size
" field.PERFORMANCE="REQUIRED"If you don't want to use the whole partition for NetWare, type a smaller value in the 
"Partition Size
" field.The difference between the original size and the smaller size is added to the free space on the disk.PERFORMANCE="REQUIRED"To change the size of the data area, use the arrow keys to move the cursor to one of the 
"Data Area
" fields, and then type in a new value.One field contains the size of the data area in blocks, the other in megabytes. When you change the value in one field, the system changes the corresponding value in the other field.PERFORMANCE="REQUIRED"To change the size of the Hot Fix Redirection Area, use the arrow keys to move the cursor to one of the 
"Hot Fix Redirection Area
" fields, and then type in a new value.One field contains the size of the area in blocks, the other as a percentage of the partition. When you change the value in one field, the system changes the corresponding value in the other field.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to display the "Create NetWare Partition?" window.PERFORMANCE="REQUIRED"Select "Yes."PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to redisplay the "Available Disk Options" menu.PERFORMANCE="REQUIRED"To create NetWare partitions on additional disks, repeat Step
s 3 throug
h 10 for each disk. When finished, go t
o IDREF="FM16437"Step 12.PERFORMANCE="REQUIRED"ID="FM16437"If you want to mirror a disk, see 
IDREF="FM88385""Mirroring and Duplexing a Hard Disk" on page 544. Otherwise, press 
MOREINFO="NONE"<Esc> to exit.
PAGENUM=543 ID="BP498"RENDERAS="SECT2"ID="FM13449"Deleting NetWare Disk PartitionsIDXID="w8587"BOOK="_idx" COLLECTION="nw41" TIDREF="i3236"The partition table displays partitions such as OS/2, UNIX, and XENIX* as "Unknown Partition Type #." Don't delete these unknown partition types unless you know what is on them.Some machine vendors such as COMPAQ create a small partition that setup and configuration utilities can be run from. Don't delete this partition.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA backup copy of data on the partition, if neededAll volumes on the partition dismounted and deletedRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"IDXID="w8588"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "Disk Options" from the "Installation Options" menu.PERFORMANCE="REQUIRED"Select "Modify Disk Partitions and Hot Fix" from the "Available Disk Options" menu.If you have more than one disk, the "Available Disk Drives" list appears
. If thi
s list appears, select the disk you want from the "Available Disk Drivers" list.A list of disk partitions on the selected disk appears at the top of the screen. The "Disk Partition Options" menu appears at the bottom of the screen.PERFORMANCE="REQUIRED"Select "Delete Any Disk Partition" from the menu.A list of the available disk partitions is displayed in a pop-up menu.PERFORMANCE="REQUIRED"Select the disk partition you want to delete.
PAGENUM=544 ID="BP499"If you did not delete existing volumes from the disk partition, a message similar to the following appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"WARNING: The selected disk partition may contain valuable data; all data on the partition will be lost.<Press ENTER to continue>PERFORMANCE="REQUIRED"If you are ready to delete the partition, pressMOREINFO="NONE" <EnterMOREINFO="NONE">; otherwise, press 
MOREINFO="NONE"<Esc>.If you press MOREINFO="NONE"<Enter>, a confirmation box is displayed containing the message "Delete Disk Partition?"PERFORMANCE="REQUIRED"Select "Yes."The space occupied by the deleted disk partition now appears as Free Space in the list of disk partitions at the top of the screen. You can create a new disk partition in this free space.RENDERAS="SECT2"ID="FM88385"Mirroring and Duplexing a Hard DiskIDXID="w8589"BOOK="_idx" COLLECTION="nw41" TIDREF="i1117"IDXID="w8590"BOOK="_idx" COLLECTION="nw41" TIDREF="i1267"IDXID="w8591"BOOK="_idx" COLLECTION="nw41" TIDREF="i1120"
NetWare 4 enables you to IDXID="w8592"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
protect data from hard disk failure by duplicating, or "mirroring," one hard disk's data on one or more other hard disks.When you mirror hard disks over different disk channels or host bus adapters, this is called duplexing.The IDXID="w8593"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
INSTALL processes for 
mirroring and duplexing are the same. The term "mirroring" is used in all menus to refer to both mirroring and duplexing.If you want mirroring with IDE/ATA disks, you must duplex them by mirroring them on separate host adapters or on different ports of a multiport IDE/ATA host adapter, with each port or adapter configured to support a single drive. This requirement is necessary because of a design limitation of the IDE drives that prevents them from continuing normally after one of the drives fails.Following are some considerations to keep in mind when using mirrored disks:MARK=BULLETMirroring requires the NetWare partitions to be exactly the same size. If they are not the same size, NetWare adjusts them to the same size during the mirroring process.PAGENUM=545 ID="BP500"Although you can mirror eight partitions together, IDXID="w8594"BOOK="_idx" COLLECTION="nw41" TIDREF="i3236"
mirroring two partitions is usually sufficient fault tolerance for most systems.If a hard disk fails and cannot be accessed by the server, you can unmirror the hard disks and salvage the volume from the functional disk. See IDREF="FM16801""Recovering Data from an Unmirrored (Out of Sync) Hard Disk" on page 570.If you want to remove a hot-plug mirrored disk without bringing down the server, you must unmirror the disk first. See IDREF="FM63930""Unmirroring Hard Disks" on page 547.When mirroring two disks, one of the disks should be blank. Delete all partitions from the blank disk and then create a new NetWare partition on it. Do not create any volumes. When you mirror the disks, the disk containing data will be mirrored to the blank disk.To mirror two disks to each other, follow these steps.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXOne blank disk containing one new NetWare partition with no volumesA disk containing data you want to mirrorRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Disk Options" from the "Installation Options" menu.PERFORMANCE="REQUIRED"Choose "Mirror/Unmirror Disk Partitions" from the "Available Disk Options" menu.A "Disk Partition Mirroring Status" window appears. This window lists each device and its mirrored status. For example:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Mirrored: Device 1Not Mirrored: Device 3Out of Sync: Device 4PAGENUM=546 ID="BP501"The meaning of each status is as follows:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"StatusCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"MirroredCOLNAME=2 ROTATE="0" MOREROWS="0"The partition is mirrored to another partition.COLNAME=1 ROTATE="0" MOREROWS="0"Not MirroredCOLNAME=2 ROTATE="0" MOREROWS="0"The partition is not mirrored to another partition.COLNAME=1 ROTATE="0" MOREROWS="0"Out of SyncCOLNAME=2 ROTATE="0" MOREROWS="0"The partition was mirrored to another partition, but is currently unmirrored.PERFORMANCE="REQUIRED"From the "Disk Partition Mirroring Status" list, choose 
one of the two devices (disk partitions) you want to mirror to each other.See "BOOK="cncptenu" COLLECTION="nw41"Device numbering" in 
Concepts for an explanation of how logical partitions relate to the installed hard disks.A "Mirrored Disk Partitions" list appears. This window displays any hard disks that are currently mirrored to the partition you selected.You must now specif
y another partition to be mirrored to th
e selected partition.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert>.The system displays the "Available Disk Partitions" list---a list of all partitions that can be mirrored to th
e first partition.PERFORMANCE="REQUIRED"Selec
t the other partition from the "Available Disk Partitions" list
.The system mirrors the two partitions to each other so that the blank partition contains the data from the other partition.If you are mirroring hard disks, the status on the "Mirrored Disk Partitions" list is now "Out of Sync" for one of the disks. As soon as mirroring is complete, the status of both disks changes to "In Sync."PAGENUM=547 ID="BP502"RENDERAS="SECT2"ID="FM63930"IDXID="w8595"BOOK="_idx" COLLECTION="nw41" TIDREF="i4673"
Unmirroring Hard DisksYou must unmirror mirrored hard disks before you can delete a partition or conduct surface tests on a disk.If you plan to replace a hot-plug mirrored disk while the system is running, you must first unmirror the disk. Failure to unmirror the disk could cause the loss of all data on its mirrored partner when you install a replacement disk.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"IDXID="w8596"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Disk Options" from the "Installation Options" menu.PERFORMANCE="REQUIRED"Choose "Mirror/Unmirror Disk Partitions" from the "Available Disk Options" menu.The system displays the 
"Disk Partition Mirroring Status
" list.PERFORMANCE="REQUIRED"Selec
t a mirrored partitio
n from the list.After you select a partition, the syste
m display
s the list of disk partitions in the mirrored set.PERFORMANCE="REQUIRED"Select the hard disk partition you want to unmirror from th
e first disk and press 
MOREINFO="NONE"<Delete>.The system displays a message warning that the partition contains volume information.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<EnterMOREINFO="NONE"> to clear the message.PERFORMANCE="REQUIRED"Choose "Yes" to salvage the information on the partition or "No" if you do not want to salvage the data.MARK=BULLETIf you choose "Yes," the system warns that the selected partition contains a volume with a name and segment number matching an existing volume. Continue with Steps 7a and 7b.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to clear the message.The system prompts you to enter a new name for the volume.PAGENUM=548 ID="BP503"PERFORMANCE="REQUIRED"Enter the new volume name.The "Mirrored Disk Partitions" list is redisplayed.MARK=BULLETIf you choose "No," the data is destroyed and the "Mirrored Disk Partitions" list is redisplayed.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<EscMOREINFO="NONE"> from the "Mirrored Disk Partitions" list.The "Partition Mirroring Status" list is displayed.
 The "Out of Sync" status appears next to the disk you unmirrored.You can now
MARK=BULLETFinish salvaging the information on the volume (if you chose to salvage information in Step 7) by pressing MOREINFO="NONE"<MOREINFO="NONE"F3> and following the prompts.Repair or replace the hard disk.Format the hard disk.Delete the partition on the hard disk.Allocate the unmirrored partition as a new volume segment.You must first remove any existing volume information from the partition, if necessary. See IDREF="FM16801""Recovering Data from an Unmirrored (Out of Sync) Hard Disk" on page 570 for information about removing existing volume information.Then see IDREF="FM64431""Creating Volumes" on page 499 for instructions on creating the new volume segment.RENDERAS="SECT2"ID="FM75884"Formatting a Hard DiskYou don't need to do a low-level format on the hard disk for a NetWare partition. A low-level format is done by the manufacturer.Perform a format on the hard disk only if the disk vendor recommends it! Use tools supplied by the vendor. If you perform a low-level format of a modern SCSI or IDE hard drive you may void the drive's warranty.PAGENUM=549 ID="BP504"If the manufacturer recommends it, consider formatting a hard disk in the following instances:MARK=BULLETYou have a hard disk that is unreliable and you hope to salvage the disk. Formatting destroys the data on the disk and may not solve the problem.You have changed the controller type on a hard disk, and the new controller uses a different format for data storage.RENDERAS="SECT1"ID="FM91092"IDXID="w8597"BOOK="_idx" COLLECTION="nw41" TIDREF="i1106"
Disaster Prevention and RecoveryThe NetWare 4TM operating system includes security and fault tolerance features to protect network data from intruders, 
power problems, and system failures. This section describes ways to prevent network data loss, reduce system vulnerability, and recover from failures.RENDERAS="SECT2"ID="FM94716"Securing the Server ConsoleThe server console is most secure when locked in a place where no one can reboot it. You can gain an additional level of IDXID="w8598"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
security by using the IDXID="w8599"BOOK="_idx" COLLECTION="nw41" TIDREF="i3992"
SECURE CONSOLE utility.SECURE CONSOLE provides the following security features, while still allowing authorized operators to use the console:MARK=BULLETPrevents NetWare Loadable Module programs from being loaded from any directory other than SYS:SYSTEM. This means no one can load an invasive NLM from a server's diskette drive or DOS partition.Prevents keyboard entry into the operating system debugger. This restricts the ability to access secure data directly.Prevents anyone from changing the date and time. Some security and accounting features depend on date and time for their enforcement.SECURE CONSOLE also removes DOS from the server.SECURE CONSOLE does not lock the server console; use the "Lock File Server Console" menu option in MONITOR to prevent keyboard entry at the console.PAGENUM=550 ID="BP505"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"SECURE CONSOLE MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"(Optional) To secure the console whenever the server is booted, add the SECURE CONSOLE command to the server's AUTOEXEC.NCF file.To remove SECURE CONSOLE, you must down the NetWare server and reboot it. If the SECURE CONSOLE command is in the AUTOEXEC.NCF file, you must first remove it.RENDERAS="SECT2"Preventing Virus InfectionIDXID="w8600"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"IDXID="w8601"BOOK="_idx" COLLECTION="nw41" TIDREF="i4775"Keep viruses off the network by educating users about virus dangers and by enforcing procedures that reduce virus risks, such as the following:MARK=BULLETBack up data frequently.Maintain layers of archived backups so you can retrieve a backup from a preinfected file.Keep a write-protected, bootable diskette with the latest virus scan and removal software for all servers and workstations.Keep a backup of executable files and flag them Execute Only.Educate yourself about the infection techniques of the latest viruses.Educate network users about how to detect viruses.Warn users of the dangers of viruses. Discourage them from using diskettes and files that have been in computers away from work.Teach users to power down their workstations immediately upon encountering a virus.PAGENUM=551 ID="BP506"Restrict access to a server's diskette drives by locking the server in a secure room. Put tape over the drive openings to remind you not to use them unnecessarily.Avoid using the Supervisor account when possible. The fewer privileges your login account has, the less power a virus has to destroy data and to spread.RENDERAS="SECT2"ID="FM65804"Preventing Packet ForgeryIDXID="w8602"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"IDXID="w8603"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
NetWare 4 includes a security feature called NCP Packet Signature that protects servers and clients using the NetWare Core ProtocolTM (NCP) services.NCPTM Packet Signature prevents packet forgery by requiring the server and the client to "sign" each NCP packet. The packet signature changes with every packet.NCP packets with incorrect signatures are discarded without breaking the client's connection with the server. However, an alert message about the invalid packet is sent to the error log, the affected client, and the server console. The alert message contains the login name and the station address of the affected client.RENDERAS="SECT3"IDXID="w8604"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
NCP Packet Signature OptionsBecause the packet signature process consumes CPU resources and slows performance both for the client and the NetWare server, 
NCP Packet Signature is optional.Several signature options are available, ranging from never signing NCP packets to always signing NCP packets. NetWare servers and NetWare clients each have four settable 
signature levels.The signature options for servers and clients combine to determine the level of NCP packet signature on the network.You can choose the packet signature level that best meets both your system performance needs and network security requirements.Some combinations of server and client packet signature levels may slow performance. However, low-CPU-demand systems may not show any performance degradation.PAGENUM=552 ID="BP507"RENDERAS="SECT3"When to Use NCP Packet SignatureIDXID="w8605"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"NCP Packet Signature is not necessary for every installation. You may choose not to use NCP packet signature if you can tolerate security risks in situations such asMARK=BULLETWhen only executable programs reside on the serverYou know and trust all network usersData on the NetWare server is not sensitive and loss or corruption of this data would not affect operationsNCP Packet Signature is recommended for security risks such asMARK=BULLETAn untrustworthy user at a workstation on the networkEasy physical access to the network cabling systemAn unattended, publicly accessible workstationRENDERAS="SECT3"ID="FM57325"Server Signature LevelsIDXID="w8606"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"Before changing the NCP Packet Signature level, read this entire section to understand all of the options.To determine the server's current signature level, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"SET NCP Packet Signature Option MOREINFO="NONE"<Enter>To set a server's packet signature level, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"SET NCP Packet Signature Option = number
PAGENUM=553 ID="BP508"Replace number with 0, 1, 2, or 3. The default is 1.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"NumberCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0COLNAME=2 ROTATE="0" MOREROWS="0"Server does not sign packets (regardless of the client level).COLNAME=1 ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"Server signs packets only if the client requests it (client level is 2 or higher).COLNAME=1 ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"Server signs packets if the client is capable of signing (client level is 1 or higher).COLNAME=1 ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"Server signs packets and requires all clients to sign packets or logging in will fail.You can use the SET console command to change the signature level from a lower to a higher level. You cannot change from a higher to a lower level unless you first reboot the server.For example, if the current signature level is 2, you can't set the signature level to 1 by using the SET command at the console.To change the signature level from 2 to 1, you must first reboot the server and then set the level to 1 by typing:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NCP Packet Signature Option = 1You can add this SET command to your AUTOEXEC.NCF file to set the signature level each time the server is brought up.RENDERAS="SECT3"Client Signature LevelsIDXID="w8607"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"To set DOS or MS Windows client signature levels, add the parameter to the workstation NET.CFG file. The format is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"signature level = numberTo set OS/2 client signature levels, add the parameter to the NET.CFG file under the NetWare Requester option. The format is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"signature level number
PAGENUM=554 ID="BP509"Replace number with 0, 1, 2, or 3. The default is 1.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"NumberCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0COLNAME=2 ROTATE="0" MOREROWS="0"Client does not sign packets.COLNAME=1 ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"Client signs packets only if the server requests it (server level is 2 or higher).COLNAME=1 ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"Client signs packets if the server is capable of signing (server level is 1 or higher).COLNAME=1 ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"Client signs packets and requires the server to sign packets or logging in will fail.RENDERAS="SECT3"Effective Packet SignatureIDXID="w8608"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"The NCP Packet Signature levels for the server and the client interact to create the effective packet signature for the network. Some combinations of server and client levels do not allow logging in.IDREF="FM54299"Figure 7-1 shows the interactive relationship between the server packet signature levels and the client signature levels.LABEL="7-1" FLOAT="0"ID="FM54299"Effective Packet Signature of Server and ClientFILEREF="n40su12a.tif"PAGENUM=555 ID="BP510"RENDERAS="SECT3"IDXID="w8609"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
Examples of Signature Levels in Different SituationsThe default NCP Packet Signature level is 1 for clients and 1 for servers. In general, this setting provides the most flexibility while still offering protection from forged packets. Following are some examples of situations requiring different signature levels.RENDERAS="SECT4"All Information on the Server Is SensitiveIf an intruder gains access to any information on the NetWare server, it could damage the company.Recommendation: Set the server to level 3 and all clients to level 3 for maximum protection.RENDERAS="SECT4"Sensitive and Nonsensitive Information Reside on the Same ServerThe NetWare server has a directory for executable programs and a separate directory for corporate finances (such as Accounts Receivable).Recommendation: Set the server to level 2 and the clients that need access to Accounts Receivable to level 3. All other clients remain at the default, level 1.RENDERAS="SECT4"Users Often Change Locations and WorkstationsYou are uncertain which employees will be using which workstations, and the NetWare server contains some sensitive data.Recommendation: Set the server to level 3. Clients remain at the default, level 1.RENDERAS="SECT4"A Workstation Is Publicly AccessibleAn unattended workstation is set up for public access to nonsensitive information, but another server on the network contains sensitive information.Recommendation: Set the sensitive server to level 3 and the unattended client to level 0.PAGENUM=556 ID="BP511"RENDERAS="SECT3"Changing the Signature Level for an NLM using CLIBIDXID="w8610"BOOK="_idx" COLLECTION="nw41" TIDREF="i644"NLM programs that use CLIB are assigned a default IDXID="w8611"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
NCP Packet Signature level that corresponds to the current signature level of the server.To change the packet signature level for all NLM programs using CLIB, use the following command format when you load CLIB:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD CLIB /LnumberReplace number with 0, 1, 2, or 3.To make sure CLIB uses the correct signature level when it is automatically loaded by other NLM programs, put the command in the AUTOEXEC.NCF file.To change the packet signature level for a single NLM, use the following command format when you load the NLM:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NLM [CLIB_OPT]/LnumberReplace number with 0, 1, 2, or 3.For information about Packet Signature Levels, see IDREF="FM57325""Server Signature Levels" on page 552.RENDERAS="SECT3"IDXID="w8612"BOOK="_idx" COLLECTION="nw41" TIDREF="i2000"
Packet Signature Considerations for Job ServersIDXID="w8613"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"IDXID="w8614"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
A job server is a server that performs a task and then returns the completed task. Most job servers are third-party products.You should be aware that some job servers do not support NCP Packet Signature. A job server may produce unsigned sessions ifMARK=BULLETIt does not operate on top of DOSIt does not use standard NetWare shellsIt is not an NLMIt uses its own implementation of the NCP engine (such as embedded print servers in printers)PAGENUM=557 ID="BP512"RENDERAS="SECT4"Minimizing RisksTo minimize security risks associated with job servers:MARK=BULLETInstall queues only on servers with signature level 3.Do not allow privileged users to put jobs in queues on servers with signature levels below 3.Make sure the job server's account is unprivileged.Disable the job server's ability to change to client rights.RENDERAS="SECT4"Disabling IDXID="w8615"BOOK="_idx" COLLECTION="nw41" TIDREF="i646"
Change to Client RightsTo prevent a job server from assuming the rights of a client, add the following SET command to the server's STARTUP.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Allow Change to Client Rights = OFFThe default is ON, because certain job servers and third-party applications cannot function without changing to client rights. Refer to the documentation that comes with the job server to determine whether the job server can function without client rights.RENDERAS="SECT3"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NCP Packet SignatureCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"NCP Packet Signature" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"SET parametersCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"SET" and "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities ReferencePAGENUM=558 ID="BP513"RENDERAS="SECT2"Activating UPS MonitoringIDXID="w8616"BOOK="_idx" COLLECTION="nw41" TIDREF="i4695"IDXID="w8617"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
An uninterruptible power supply (UPS) is an indispensable part of your network. Not only does it prevent damage to your computers by eliminating 
power surges and brownouts, but it also prevents data loss during 
power outages.Use the following procedure to load UPS.NLM, which allows you to configure the UPS monitoring feature in NetWare 4. You can specify the time the server functions on 
battery power and how long the battery needs to charge.UPS.NLM supports the following ports: mouse port, Novell® keycard, disk coprocessor board (DCB), and standalone UPS cards. If you are using a UPS machine connected to the server by serial port, you need NetWare-compatible third-party UPS software.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA UPS hardware driver must be loaded on the server before UPS is activated.The DCB.DSK device driver must be loaded if you are using a DCB to connect the UPS machine to the server.The UPS hardware must be installed according to the vendor's instruction manual.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, load the UPS NLM by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD UPS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Set the type value by enterin
gFORMAT="LINESPECIFIC"MOREINFO="NONE"TYPE = typename MOREINFO="NONE"<Enter>Replace 
typename with the appropriate adapter card that you have connected to the UPS machine. Valid type names includ
e DCB
, mouse
 (IBM PS/2*-style), standalone, 
and keycard
.For example, to loa
d UPS.NLM with 
the DCB device, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"TYPE = DCBMOREINFO="NONE" <Enter>
PAGENUM=559 ID="BP514"PERFORMANCE="REQUIRED"When prompted, enter a valid I/O port number
.Valid I/O port numbers vary depending on your hardware. A list of valid port numbers is displayed. Refer to "BOOK="utlrfenu" COLLECTION="nw41"UPS" in Utilities Reference for valid port numbers.PERFORMANCE="REQUIRED"Select a discharge time, a recharge time, and a wait time.For example, typ
eFORMAT="LINESPECIFIC"MOREINFO="NONE"DISCHARGE=20 RECHARGE=60 WAIT=15 MOREINFO="NONE"<Enter>See "
BOOK="utlrfenu" COLLECTION="nw41"UPS" i
n Utilities Reference f
or valid values for these fields.PERFORMANCE="REQUIRED"(Optional) To automatically load UPS.NLM when the server boots up, add th
e LOAD UPS
 command t
o your AUTOEXEC.NCF fi
le.You can edit the AUTOEXEC.NCF file by using INSTALL or EDIT.You can set all required parameters when you load UPS.NLM. For example, add the following statement to your AUTOEXEC.NCF file:LOAD UPS TYPE=DCB PORT=346 DISCHARGE=20 RECHARGE=120 WAIT=10PERFORMANCE="REQUIRED"(Optional) To view the status of your UPS after loadin
g UPS
.NLM, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8618"BOOK="_idx" COLLECTION="nw41" TIDREF="i4695"
UPS STATUS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"(Optional) To change the discharge or recharge settings fo
r UP
S.NLM, us
e MOREINFO="NONE"the UPS TIME
 command at the server console.For example, you might use a command similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8619"BOOK="_idx" COLLECTION="nw41" TIDREF="i4695"
UPS TIME DISCHARGE=10 RECHARGE=90 MOREINFO="NONE"<Enter>Remember to change the setting in the AUTOEXEC.NCF file if you want the server to retain the new setting after rebooting
.PAGENUM=560 ID="BP515"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using UPS.NLMCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"UPS" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using UPS STATUSCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"UPS STATUS" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using UPS TIMECOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"UPS TIME" in Utilities ReferenceRENDERAS="SECT2"ID="FM98294"ID="FM14848"Protecting the Operating System's MemoryIDXID="w8620"BOOK="_idx" COLLECTION="nw41" TIDREF="i3587"IDXID="w8621"BOOK="_idx" COLLECTION="nw41" TIDREF="i2392"NetWare 4 has memory protection features that guard the operating system memory from corruption by NetWare Loadable Module (NLM) programs. These features allow you to run such programs in a separate memory IDXID="w8622"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
domain called the OS_PROTECTED domain.Once you have loaded an NLM in the OS_PROTECTED
 domain and found it is safe, you can load it into the
 OS domain, where it can run more efficiently.If IDXID="w8623"BOOK="_idx" COLLECTION="nw41" TIDREF="i2760"
you have third-party IDXID="w8624"BOOK="_idx" COLLECTION="nw41" TIDREF="i1171"
NLM programs such as a database or backup NLM, check the documentation that came with the NLM to determine the recommended memory domain for the NLM.RENDERAS="SECT3"Using DomainsIDXID="w8625"BOOK="_idx" COLLECTION="nw41" TIDREF="i1171"Use the following procedure to enable the operating system memory protection and load an NLM in the OS_PROTECTED domain.This procedure requires you to reboot the NetWare server. You may want to do it after business hours or when no one is accessing the server.DOMAIN.NLM must be located in your boot directory and must be loaded from your STARTUP.NCF file before you load any other NLM programs or LAN drivers. DOMAIN will not load if any NLM files or LAN drivers have previously been loaded.To load DOMAIN from the STARTUP.NCF file, you must have the following files in your bootup directory: DOMAIN.NLM, NWTIL.NLM, NWTILR.NLM, and DOMAIN.MSG. (The server installation process places these files in the bootup directory.)PAGENUM=561 ID="BP516"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"IDXID="w8626"BOOK="_idx" COLLECTION="nw41" TIDREF="i1175"
Edit the STARTUP.NCF file to put the following command in the first line of the file:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD DOMAINPERFORMANCE="REQUIRED"Reboot the server.In NetWare 4.1, when you load DOMAIN.NLM, the following files are automatically loaded: NWTIL.NLM and NWTILR.NLM. Once all your NLM programs have been loaded, you can unload NWTIL.NLM to reclaim memory. NWTIL.NLM is only needed by DOMAIN.NLM when NLM programs are loaded into the OS_PROTECTED domain.PERFORMANCE="REQUIRED"Change to the OS_PROTECTED memory domain by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOMAIN=OS_PROTECTED MOREINFO="NONE"<Enter>You can place this command in the STARTUP.NCF or AUTOEXEC.NCF file, or you can type it at the server console.This command, and the DOMAIN commands that follow
, are 
available onl
y afte
r DOMAIN.NLM has been loaded.PERFORMANCE="REQUIRED"(Optional) Load an NLM in the OS_PROTECTED domain.Following is a sample load command:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD EXAMPLE.NLM MOREINFO="NONE"<Enter>The NLM is now loaded in the OS_PROTECTED domain.PERFORMANCE="REQUIRED"(Optional) To change back to the OS domain, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"DOMAIN=OS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"(Optional) To view memory domains and the NLM programs loaded into them, type FORMAT="LINESPECIFIC"MOREINFO="NONE"DOMAIN MOREINFO="NONE"<Enter>
PAGENUM=562 ID="BP517"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Loading an NLMCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"LOAD" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using DOMAINCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"DOMAIN" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Domains for Novell-specific NLMsCOLNAME=2 ROTATE="0" MOREROWS="0"Appendix C, "BOOK="utlrfenu" COLLECTION="nw41"Memory Domains for NLMs and Autoloaded NLMs," of Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"DomainsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Domains" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Memory protectionCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Memory protection" in Concepts"BOOK="cncptenu" COLLECTION="nw41"Paging" in ConceptsRENDERAS="SECT3"Loading a Misbehaved NLMIDXID="w8627"BOOK="_idx" COLLECTION="nw41" TIDREF="i1171"IDXID="w8628"BOOK="_idx" COLLECTION="nw41" TIDREF="i2760"This section is for the advanced network supervisor. Consider using one of the following procedures only if you have a general understanding of segmented memory.If you load an NLM, and you receive an abend that indicates a segmentation violation, the NLM may be accessing data that exists in the code segment in memory. IDREF="FM45606"Figure 7-2 illustrates such an NLM.PAGENUM=563 ID="BP518"LABEL="7-2" FLOAT="0"ID="FM45606"Logical Memory MapFILEREF="n41su15a.tif"Please inform the NLM vendor if you have an NLM that causes a domain to be quarantined or causes an abend.If you want to load the NLM despite this problem, you can use either of the two procedures that follow.Debugging the NLM is easier if you use Option 1 to load the NLM; however, this procedure affects memory management for all NLM programs that you load in the OS_PROTECTED domain.If you do not debug the NLM, or if you have already debugged it, load the NLM using Option 2. This procedure affects memory management only for the errant NLM.PAGENUM=564 ID="BP519"RENDERAS="SECT4"Option 1: Loading a Suspect NLMYou can load the NLM in the OS_PROTECTED domain by using the data segment register to access the code segment. IDREF="FM31874"Figure 7-3 illustrates this process.If you use this option, all NLM programs that are subsequently loaded in the OS_PROTECTED domain will use this method of memory management by allowing access to the code segment using the data segment register.LABEL="7-3" FLOAT="0"ID="FM31874"Logical Memory Map with the DOMAIN -E ParameterFILEREF="n41su17a.tif"PAGENUM=565 ID="BP520"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Create the OS_PROTECTED domain by placing the following command in the STARTUP.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD DOMAIN -EPERFORMANCE="REQUIRED"Reboot the server.PERFORMANCE="REQUIRED"Change to the OS_PROTECTED memory domain by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOMAIN=OS_PROTECTED MOREINFO="NONE"<Enter>You can place this command in the STARTUP.NCF or AUTOEXEC.NCF file, or you can type it at the server console.This command, and the DOMAIN commands that follow, are available only after DOMAIN.NLM has been loaded.PERFORMANCE="REQUIRED"From the OS_PROTECTED domain, load the NLM, using the following command
:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD nlm_name MOREINFO="NONE"<Enter>wher
enlm_name is the name of the NLM you want to load
.PAGENUM=566 ID="BP521"RENDERAS="SECT4"Option 2: Loading a Suspect NLMIn this procedure, the NetWare operating system loads the NLM code in the data segment. IDREF="FM97570"Figure 7-4 illustrates this process.If you use this option, you will affect memory management only for the NLM that you load with the -L parameter.LABEL="7-4" FLOAT="0"ID="FM97570"Logical Memory Map with the LOAD  -L ParameterFILEREF="n41su16a.tif"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Create the OS_PROTECTED domain by placing the following command in the STARTUP.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD DOMAIN
PAGENUM=567 ID="BP522"PERFORMANCE="REQUIRED"Change to the OS_PROTECTED memory domain by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOMAIN=OS_PROTECTED MOREINFO="NONE"<Enter>You can place this command in the STARTUP.NCF or AUTOEXEC.NCF file, or you can type it at the server console.This command, and the DOMAIN commands that follow, are available only after DOMAIN.NLM has been loaded.PERFORMANCE="REQUIRED"From the OS_PROTECTED domain, load the NLM, using the following command
:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD -L nlm_namewherenlm_name is the name of the NLM you want to load.RENDERAS="SECT4"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using DOMAINCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"DOMAIN" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Domains for Novell-specific NLMsCOLNAME=2 ROTATE="0" MOREROWS="0"Appendix C, "BOOK="utlrfenu" COLLECTION="nw41"Memory Domains for NLMs and Autoloaded NLMs," of Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"DomainsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Domains" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Memory protectionCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Memory protection" in Concepts"BOOK="cncptenu" COLLECTION="nw41"Paging" in ConceptsPAGENUM=568 ID="BP523"RENDERAS="SECT2"Protecting Database Integrity with TTSIDXID="w8629"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"IDXID="w8630"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
The IDXID="w8631"BOOK="_idx" COLLECTION="nw41" TIDREF="i4546"
Transaction Tracking System (TTS) can prevent data corruption by IDXID="w8632"BOOK="_idx" COLLECTION="nw41" TIDREF="i1781"
backing out of incomplete transactions and keeping a record of backed-out data.By default, TTSTM is enabled.The NetWare server automatically disables TTS if one of the following happens:MARK=BULLETThe SYS: volume becomes full. (The SYS: volume is the TTS backout volume.)The NetWare server has insufficient memory to operate TTS.If TTS has been disabled and you have solved the problems that led to its disabling, use the ENABLE TTS command to enable TTS again. Type the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"ENABLE TTS MOREINFO="NONE"<Enter>RENDERAS="SECT3"Automatically Backing Out of Incomplete TransactionsIDXID="w8633"BOOK="_idx" COLLECTION="nw41" TIDREF="i4546"Use this procedure to enable the server to automatically back out of any incomplete transactions, without being prompted.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXTTS enabledRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose 
"Server Parameters
" from the 
"Available Options
" menu.PERFORMANCE="REQUIRED"Choose 
"Transaction Tracking
" from the 
"Categories
" menu.
PAGENUM=569 ID="BP524"PERFORMANCE="REQUIRED"Choose 
"Auto TTS Backout Flag
" from the 
"Transaction Tracking
" menu.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to change the value to ON.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the 
"Update Options
" menu.PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears, indicating the path to the STARTUP.NCF file.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to update the file.PERFORMANCE="REQUIRED"When you want the changes to take effect, reboot the server.RENDERAS="SECT3"Keeping a Log of Backed-Out DataIDXID="w8634"BOOK="_idx" COLLECTION="nw41" TIDREF="i4546"Use this procedure to keep a log (TTS$LOG.ERR on volume SYS:) of all data that is backed out by IDXID="w8635"BOOK="_idx" COLLECTION="nw41" TIDREF="i1340"IDXID="w8636"BOOK="_idx" COLLECTION="nw41" TIDREF="i2185"
TTS.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXTTS enabledRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SERVMAN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Server Parameters" from the "Available Options" menu.PERFORMANCE="REQUIRED"Choose "Transaction Tracking" from the "Categories" menu.PERFORMANCE="REQUIRED"Choose "

TTS Abort Dump Flag" from the "Transaction Tracking" menu.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to change the value to ON.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to reach the "Update Options" menu.
PAGENUM=570 ID="BP525"PERFORMANCE="REQUIRED"Choose "Update AUTOEXEC.NCF and STARTUP.NCF Now" from the "Update Options" menu.A window appears, indicating the path to the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"If desired, press 
MOREINFO="NONE"<Enter> to update the file.The system writes the parameters to the AUTOEXEC.NCF file or updates the parameters if they are already in the file.If you do not update the AUTOEXEC.NCF file, the parameter changes last only until the server is rebooted.RENDERAS="SECT2"Mirroring and Duplexing to Protect DataNetWare 4 enables you to protect data from hard disk failure by duplicating, or "mirroring," one hard disk's data on one or more other hard disks.If a mirrored hard disk fails and cannot be accessed by the server, you can unmirror the hard disks and salvage the volume from the functional disk.How to mirror or duplex hard disks is explained under IDREF="FM88385""Mirroring and Duplexing a Hard Disk" on page 544. How to recover data from a mirrored disk is explained in the next section, IDREF="FM16801""Recovering Data from an Unmirrored (Out of Sync) Hard Disk."RENDERAS="SECT2"ID="FM16801"Recovering Data from an Unmirrored (Out of Sync) Hard DiskIDXID="w8637"BOOK="_idx" COLLECTION="nw41" TIDREF="i3150"Once a hard disk is unmirrored, its status is listed as either "Not Mirrored" or "Out of Sync" on the "Disk Partition Mirroring Status" list. To display this list, load INSTALL, select "Disk Options," and then choose "Mirror/Unmirror Disk Partitions."When a hard disk is listed as "Out of Sync," the operating system does not recognize any volume information on it. Use this procedure to recover data from an "Out of Sync" partition.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"IDXID="w8638"BOOK="_idx" COLLECTION="nw41" TIDREF="i1812"
At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALLMOREINFO="NONE" <Enter>
PAGENUM=571 ID="BP526"PERFORMANCE="REQUIRED"Select "Disk Options" in the "Installation Options" menu.PERFORMANCE="REQUIRED"Select "Mirror/Unmirror Disk Partitions" in the "Available Disk Options" menu.PERFORMANCE="REQUIRED"Select the "Out of Sync" partition and press 
MOREINFO="NONE"<F3>.The following warning may appear if another volume segment with the same name exists on another disk:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"Warning! The selected partition contains "volume <nameMOREINFO="NONE"> segment <numberMOREINFO="NONE">" and that volume is already defined.MOREINFO="NONE"<Press ESCAPE To Continue>PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> and respond "Yes" to the "Rename the Volume Segment?" prompt.PERFORMANCE="REQUIRED"Enter a unique name for the new volume segment.PERFORMANCE="REQUIRED"Respond "Yes" to the prompt to salvage the volume segment.Now the segment can be mounted as an independent volume
.RENDERAS="SECT1"ID="FM74015"Managing Network Time SynchronizationIDXID="w8639"BOOK="_idx" COLLECTION="nw41" TIDREF="i4490"
Time synchronization ensures that all servers in a Directory tree report the same time and order Directory Services events correctly.NetWare 4.1 uses the IDXID="w8640"BOOK="_idx" COLLECTION="nw41" TIDREF="i4499"
TIMESYNC NLM, which automatically loads when the server is booted, to control time synchronization. The TIMESYNC.CFG file in SYS:SYSTEM can contain the parameters for the TIMESYNC NLM, if the default settings are not adequate.To change the time synchronization configuration on a NetWare server, use the EDIT server utility to modify the parameters in the TIMESYNC.CFG file and then reboot the server.Do not put SET time synchronization parameters in the STARTUP.NCF file, because the TIMESYNC.CFG file is read after the STARTUP.NCF file.PAGENUM=572 ID="BP527"RENDERAS="SECT2"SET Parameters for TIMESYNCIDREF="FM99290"Table 7-5 shows the SET parameters used to configure time synchronization. The defaults are appropriate for most small networks. For large network TIMESYNC considerations, see IDREF="FM64326""Configuring Time Synchronization for Large Networks" on page 578.LABEL="7-5" PGWIDE=1 TOCENTRY="1"IDXID="w8641"BOOK="_idx" COLLECTION="nw41" TIDREF="i4499"IDXID="w8642"BOOK="_idx" COLLECTION="nw41" TIDREF="i4100"IDXID="w8643"BOOK="_idx" COLLECTION="nw41" TIDREF="i4490"ID="FM99290" TIMESYNC SET parametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="12*"COLNAME=2 COLWIDTH="22*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"SET parameter and defaultCOLNAME=2 ROTATE="0" MOREROWS="0"Recommended usageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC ADD Time SourceCOLNAME=2 ROTATE="0" MOREROWS="0"Use EDIT rather than this parameter to add a time server to the time source list in the TIMESYNC.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Configuration FileDefault = SYS:SYSTEM\COLNAME=2 ROTATE="0" MOREROWS="0"Use this parameter to specify the file path if the TIMESYNC.CFG file is not located in SYS:SYSTEM.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Configured SourcesDefault = OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Turn this parameter ON if you are using a custom-configured list of time sources.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC IDXID="w8644"BOOK="_idx" COLLECTION="nw41" TIDREF="i4073"
Directory Tree ModeDefault = ONCOLNAME=2 ROTATE="0" MOREROWS="0"Turning this parameter OFF allows 
SAP packets from other Directory trees to influence time synchronization on this server's Directory tree.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Hardware ClockDefault = ONCOLNAME=2 ROTATE="0" MOREROWS="0"Turn this parameter OFF only if this server uses an external time source (such as a radio clock). All servers in the same tree should have the same setting for this parameter.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Polling CountDefault = 3 (time packets)COLNAME=2 ROTATE="0" MOREROWS="0"Do not increase this setting. Doing so adds unnecessary traffic to the network.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Polling IntervalDefault = 600 (seconds)COLNAME=2 ROTATE="0" MOREROWS="0"Decrease this setting if you need to poll time servers more often than every 10 minutes. All servers in the same tree should have the same setting for this parameter.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC REMOVE Time SourceCOLNAME=2 ROTATE="0" MOREROWS="0"Use EDIT rather than this parameter to remove a time server from the time source list in the TIMESYNC.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC RESETDefault = OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Use EDIT rather than this parameter to reset values in the TIMESYNC.CFG file and to remove the list of time sources.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Restart FlagDefault = OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Turn this parameter ON only if you want to reload the TIMESYNC NLM (because you edited TIMESYNC.CFG) without rebooting the server.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Service AdvertisingDefault = ONCOLNAME=2 ROTATE="0" MOREROWS="0"Turn this parameter OFF if you are using a custom-configured list of time sources.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Synchronization RadiusDefault = 2000 (milliseconds)COLNAME=2 ROTATE="0" MOREROWS="0"Increase this parameter to allow a wider margin of error for time synchronization between servers. If you decrease the radius too much (below 1,000), some time servers may never achieve synchronization.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Time AdjustmentCOLNAME=2 ROTATE="0" MOREROWS="0"Use this parameter sparingly to correct network-wide time errors, or you may corrupt time synchronization and the order of events on your network.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Time SourceCOLNAME=2 ROTATE="0" MOREROWS="0"Use EDIT rather than this parameter to add a time server or to display the time source list in the TIMESYNC.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC TypeDefault = SecondaryCOLNAME=2 ROTATE="0" MOREROWS="0"Use EDIT rather than this parameter to change the default 
time server type in the TIMESYNC.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Write ParametersDefault = OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Use EDIT rather than this parameter to change the settings in the TIMESYNC.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"TIMESYNC Write ValueCOLNAME=2 ROTATE="0" MOREROWS="0"Use EDIT rather than this parameter to modify the TIMESYNC.CFG file.PAGENUM=573 ID="BP528"RENDERAS="SECT2"Editing the TIMESYNC.CFG FileIDXID="w8645"BOOK="_idx" COLLECTION="nw41" TIDREF="i4504"IDXID="w8646"BOOK="_idx" COLLECTION="nw41" TIDREF="i4490"
Time synchronization parameters are stored in their own configuration file, by default named TIMESYNC.CFG in the SYS:SYSTEM directory.To change the time synchronization configuration on a NetWare server, modify the parameters in the TIMESYNC.CFG file, and then reboot the server or use SET to turn ON the "TIMESYNC Restart Flag" parameter.You can use SET or SERVMAN to change the TIMESYNC parameters; however, unless you also edit the TIMESYNC.CFG file, changes made in SET or SERVMAN will be lost the next time the server boots.PAGENUM=574 ID="BP529"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXAccess to the server console, or a remote console session with the server.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD EDIT MOREINFO="NONE"<Enter>A prompt to "Enter file to edit or press 
MOREINFO="NONE"<Esc> to exit" appears.PERFORMANCE="REQUIRED"At the prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SYS:SYSTEM\TIMESYNC.CFG MOREINFO="NONE"<Enter>The current TIMESYNC.CFG file appears.PERFORMANCE="REQUIRED"Use the arrow keys to move the cursor to the lines you need to edit.PERFORMANCE="REQUIRED"ID="FM73056"Modify the settings for the TIMESYNC parameters you want to change.PERFORMANCE="REQUIRED"To save your edits, press 
MOREINFO="NONE"<Esc>.A "Do you want to save SYS:SYSTEM\TIMESYNC.CFG" prompt appears.PERFORMANCE="REQUIRED"To save the TIMESYNC.CFG file, choose "Yes."PERFORMANCE="REQUIRED"To exit EDIT, press 
MOREINFO="NONE"<Esc>.If you have several parameters in your TIMESYNC.CFG file, you may want to copy the file from server to server. Be sure that each copied TIMESYNC.CFG file contains the correct default time server type and configured-sources list for the server it configures.PAGENUM=575 ID="BP530"RENDERAS="SECT2"Creating a Custom Time Source ConfigurationIDXID="w8647"BOOK="_idx" COLLECTION="nw41" TIDREF="i4490"Time servers use one of two methods to find each other on the internetwork: SAP (IDXID="w8648"BOOK="_idx" COLLECTION="nw41" TIDREF="i4073"
Service Advertising Protocol) and custom time source configuration.RENDERAS="SECT3"IDXID="w8649"BOOK="_idx" COLLECTION="nw41" TIDREF="i4490"
SAP MethodBy default, Primary, Reference, and Single Reference time servers use SAP to announce their presence on the network. Secondary time servers do not advertise, but they do "listen to" SAP information to find the nearest time source.The SAP method allows for quick installation without regard to the network layout. It also allows automatic reconfiguration if new servers are added to the network.RENDERAS="SECT3"ID="FM33151"Custom Time Source MethodThe custom time source method lists specific, authorized time servers that each server contacts to determine network time. In a custom time configuration, servers do not listen for SAP information from other time servers, and they do not advertise with SAP.A configured-sources list resides in the TIMESYNC.CFG file of each time server on the internetwork. The order of the server names in the list is the polling order the server follows to get the correct time.The custom configuration method requires careful planning before NetWare installation, but it gives the network supervisor complete control of the time synchronization environment.In most circumstances, you can use the default SAP method and do not need to create a custom time source configuration. However, you may need a custom configuration ifMARK=BULLETYou have more than one Reference or more than one Primary time server on your network.You frequently have temporary or "test" servers added to or removed from your network.You need to prevent unauthorized time sources from determining network time.PAGENUM=576 ID="BP531"Use this procedure to create a custom time source IDXID="w8650"BOOK="_idx" COLLECTION="nw41" TIDREF="i4490"
configuration. These steps must be repeated for each time server on your network.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXAccess to the server console, or a remote console session with the server.Prioritized list of time sources.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD EDIT MOREINFO="NONE"<Enter>A prompt to "Enter file to edit or press 
MOREINFO="NONE"<Esc> to exit" appears.PERFORMANCE="REQUIRED"At the prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SYS:SYSTEM\TIMESYNC.CFG MOREINFO="NONE"<Enter>The current TIMESYNC.CFG file appears.PERFORMANCE="REQUIRED"Add the following parameters to the TIMESYNC.CFG file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Type = x
Service Advertising = OFF
Configured Sources = ONReplace 
x with this server's time server type (Reference, Single Reference, Primary, or Secondary).PERFORMANCE="REQUIRED"Add the list of time sources for this server as follows:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Time Source = x
Time Source = 
yTime Source = 
zReplace 
x with the first time server this server should contact (probably a Reference server or the nearest Primary time server). Replace 
y and 
z with the other time servers this server should contact, in order of importance.
PAGENUM=577 ID="BP532"The order of the time servers in the time source list determines their priority when advertising network time.PERFORMANCE="REQUIRED"To save your edits, press 
MOREINFO="NONE"<Esc>.A "Do you want to save SYS:SYSTEM\TIMESYNC.CFG" prompt appears.PERFORMANCE="REQUIRED"To save the TIMESYNC.CFG file, choose "Yes."PERFORMANCE="REQUIRED"To exit EDIT, press 
MOREINFO="NONE"<Esc>.If you have several parameters in your TIMESYNC.CFG file, you may want to copy the file from server to server. Be sure that each copied TIMESYNC.CFG file contains the correct default time server type and time source list for the server it configures.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SAPCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Service Advertising Protocol" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Time server typesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="getstenu" COLLECTION="nw41"Understanding Time Synchronization in NDS" in Chapter 4 of Introduction to NetWare Directory ServicesCOLNAME=1 ROTATE="0" MOREROWS="0"Time synchronizationCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Time synchronization" in ConceptsRENDERAS="SECT2"IDXID="w8651"BOOK="_idx" COLLECTION="nw41" TIDREF="i4490"
Adjusting a Fast or Slow Reference Time ServerIf your Reference time server is several minutes off, all other time servers on your network will be inaccurate also.To correct the time on the Reference Server and, therefore, network-wide, type the following SET command at the Reference Server's console:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET TIMESYNC Time Adjustment=[+|-] hour:minute:second at month/day/year hour:minute:second [AM|PM] MOREINFO="NONE"<Enter>For example, if your Reference Server is 10 minutes fast and you want to adjust the time at 2 a.m. on May 1, 1995, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"SET TIMESYNC Time Adjustment=-00:10:00 at 5/1/95 2:00:00 AM MOREINFO="NONE"<Enter>
PAGENUM=578 ID="BP533"Adjusting network time affects the order of Directory Services events. It is best to schedule time adjustments during low-usage periods, such as late evening or early morning.To cancel a time adjustment, type the following SET command at the Reference Server's console:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET TIMESYNC Time Adjustment = cancel MOREINFO="NONE"<Enter>The cancel command must be issued before the scheduled time adjustment and at the same server where the original time adjustment was set, or it will not cancel the time adjustment.RENDERAS="SECT2"ID="FM64326"Configuring Time Synchronization for Large NetworksSome of the default settings for TIMESYNC are not suitable for large networks. This section explains time synchronization considerations for IDXID="w8652"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"
configuring large installations.RENDERAS="SECT3"Time Providers and Time ConsumersTime synchronization servers are either time providers or time consumers. Secondary servers are time consumers. Single Reference, Reference, and Primary servers are time providers.Reference and Primary servers must be able to exchange information with another time provider in order to synchronize. A Reference or Primary server cannot claim to be synchronized if it is the only time provider on the network, because it requires at least one other time provider to synchronize with.The Single Reference server, as its name implies, is a special type of Reference server that does not need another time provider in order to synchronize.Secondary servers (time consumers) require at least one time provider.PAGENUM=579 ID="BP534"RENDERAS="SECT3"IDXID="w8653"BOOK="_idx" COLLECTION="nw41" TIDREF="i4490"
Time Synchronization and the Directory TreeIDXID="w8654"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"Although time synchronization and NetWare Directory Services are independent features of NetWare 4.1, time synchronization can be configured to follow the Directory tree structure.The default NetWare 4.1 installation makes the root server in a Directory tree a Single Reference time server and all other servers in the tree Secondary time servers.The default time synchronization parameter, "SET TIMESYNC Directory Tree Mode = ON," recognizes the Directory tree structure and only synchronizes time within that tree.In a large installation with more than one Directory tree, the network supervisor can change the defaults to configure time synchronization across Directory trees.The default does not require custom time synchronization parameters during installation. However, the default relies on a Single Reference server, thus permitting only a single point of failure and increasing network traffic at that server.In addition, the default installation relies on Service Advertising Protocol (SAP) packets to identify the time providers.On a large network, relying on SAP is not only inefficient, it can also lead to errors---especially if it is common for test servers (which may be misconfigured) to come and go on the network.The custom time source method described under IDREF="FM33151""Custom Time Source Method" on page 575 is recommended for large networks because it does not rely on SAP.The time synchronization algorithm always attempts to contact explicitly named time sources before listening to SAP. This makes it possible to synchronize across Directory trees, because the Directory Tree Mode only applies to SAP packets.Network supervisors with custom-configured time sources may choose to eliminate the use of SAP entirely.PAGENUM=580 ID="BP535"RENDERAS="SECT3"Using an .NCF File to Configure Multiple Time ServersOne easy way to configure several servers is to create a custom .NCF file containing the SET parameters required to configure time sources.Using the custom .NCF file avoids repetitive typing at each server console. Include the "SET TIMESYNC Write Parameters = ON" parameter in the custom .NCF file to save the time source parameters to each server's TIMESYNC.CFG file.Most servers will have identical TIMESYNC configuration parameters with the exception of the time source list, where the first entry in the list likely varies from server to server.To change the first server in the time source list, edit the TIMESYNC.CFG file or issue the "SET TIMESYNC Time Source" parameter from the server console before saving the configuration parameters.RENDERAS="SECT3"Avoiding SET TIMESYNC Parameter InconsistenciesSeveral of the SET TIMESYNC parameters interact with each other. Because these parameters are set on each server, it is important to configure the entire network consistently.Understanding the relationship of the parameters described here can help avoid IDXID="w8655"BOOK="_idx" COLLECTION="nw41" TIDREF="i4490"
time synchronization problems on large networks.RENDERAS="SECT4"SET TIMESYNC Service Advertising = ON/OFFWhen ON, time providers advertise using SAP. This parameter has no effect on time consumers (Secondary time servers). When OFF, time providers do not advertise.We recommend all servers be configured the same (ON or OFF) for this parameter to be effective.RENDERAS="SECT4"SET TIMESYNC Configured Sources = ON/OFFWhen ON, time servers do not listen to SAP information. They listen only to the time providers in the configured sources list (initially read from the TIMESYNC.CFG file). When OFF, time servers listen for SAP information.PAGENUM=581 ID="BP536"RENDERAS="SECT4"SET TIMESYNC Directory Tree Mode = ON/OFFWhen ON, time providers do not advertise under the name of the host server. Instead, they advertise under the name of their Directory Services tree. When ON, servers listening for SAP packets will reject packets that are not from within their own tree.When OFF, time providers advertise under their host server name, and listening servers will accept packets from any time provider.This parameter also interacts with the "SET TIMESYNC Service Advertising" and the "SET TIMESYNC Configured Sources" parameters. Directory Tree Mode has no effect if Service Advertising is OFF and Configured Sources is ON.RENDERAS="SECT4"SET TIMESYNC Time Source and SET TIMESYNC Add Time SourceThese parameters identify a time provider by server name. When configured sources are listed in a server's TIMESYNC.CFG file, their time information is always used before any SAP information is considered.RENDERAS="SECT4"SET Default Time Server TypeThis parameter provides a method to override the default TIMESYNC type, which is Secondary, without using a TIMESYNC.CFG file.However, when present, the "SET TIMESYNC Type" parameter always overrides the "SET Default Time Server Type" parameter.If you use INSTALL to change the default type, it may have no effect if you have already created a TIMESYNC.CFG file with the overriding "TIMESYNC Type" parameter in it.RENDERAS="SECT3"IDXID="w8656"BOOK="_idx" COLLECTION="nw41" TIDREF="i4490"
Example of Synchronizing Two Directory TreesIDXID="w8657"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"Suppose you have two Directory trees on your network and you want all the servers in both trees to synchronize to the same time.You used the default installation, so the root servers of each tree (ROOT1 and ROOT2) are Single Reference servers, Tree Mode is ON, and Service Advertising is ON.PAGENUM=582 ID="BP537"Each tree is synchronized within itself, but time between the trees differs by a few minutes. To synchronize both trees together, create a custom .NCF file containing the following commands and execute it on the respective servers:Server ROOT1FORMAT="LINESPECIFIC"MOREINFO="NONE"SET TIMESYNC Type = REFERENCE
SET TIMESYNC Time Source = ROOT2
SET TIMESYNC Write Value = 3SET TIMESYNC Write Parameters = ONServer ROOT2FORMAT="LINESPECIFIC"MOREINFO="NONE"SET TIMESYNC Type = PRIMARY
SET TIMESYNC Time Source = ROOT
1SET TIMESYNC Write Value = 3SET TIMESYNC Write Parameters = ONThe root servers of both trees will synchronize, which in turn will synchronize all of the other servers in both trees.Since the roots are now both time providers, it is necessary to change the "TIMESYNC Types" from "Single" to "Reference" on Server ROOT1 and "Primary" on Server ROOT2.Server ROOT1 is a Reference server so that there will be a central point for controlling time on the network.The Write Parameters command causes the TIMESYNC.CFG file to be rewritten so the changes will be in place if the servers are rebooted.PAGENUM=583 ID="BP538"When you synchronize two Directory trees, you basically double the size of the time synchronization network. You should examine the physical layout of the network and add other Primary servers, or consider hand-configuring the time sources and eliminating the use of SAP.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Time server typesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="getstenu" COLLECTION="nw41"Understanding Time Synchronization in NDS" in Chapter 4 of Introduction to NetWare Directory ServicesCOLNAME=1 ROTATE="0" MOREROWS="0"Time synchronizationCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Time synchronization" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"SAPCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Service Advertising Protocol" in ConceptsRENDERAS="SECT1"Using Remote Console to Manage a ServerIDXID="w8658"BOOK="_idx" COLLECTION="nw41" TIDREF="i3762"IDXID="w8659"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
The NetWare 4 operating system allows you to use a workstation as a server console when needed. A workstation functioning as a console is called a remote console.IDXID="w8660"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
A remote console gives you greater server security because you can lock servers in a safe place and remove the keyboards and monitors. You can then start a remote console session from a workstation whenever you need to accomplish console tasks.When finished, you can exit the remote console session so the computer functions as a workstation again.You can perform the following functions from a remote console:MARK=BULLETUse console commands as you would at the server console.Scan directories and edit text files in both NetWare and DOS partitions on a server.Transfer files to, but not from, a server.Bring down or reboot a server.Install or upgrade NetWare.PAGENUM=584 ID="BP539"This section describes how to establish a remote console session and how to accomplish some essential management tasks from a remote console.RENDERAS="SECT2"ID="FM94031"Understanding Connection TypesIDXID="w8661"BOOK="_idx" COLLECTION="nw41" TIDREF="i3676"Remote console sessions can be run on the network or through a modem.MARK=BULLETA network connection is called a direct connection.A connection through a modem or null modem cable is called an IDXID="w8662"BOOK="_idx" COLLECTION="nw41" TIDREF="i309"
asynchronous connection. A null modem cable is a direct serial connection between two computers, as opposed to a network connection.RENDERAS="SECT2"ID="FM61980"Running a Remote Console Session Through a Direct ConnectionIDXID="w8663"BOOK="_idx" COLLECTION="nw41" TIDREF="i3676"IDXID="w8664"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"
To run a remote console session over a direct connection you must do the following:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDXID="w8665"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"
Load the REMOTE NLM and IDXID="w8666"BOOK="_idx" COLLECTION="nw41" TIDREF="i3924"
RSPX NLM on the server.Run RCONSOLE.EXE from the workstation to access the server.Each of these tasks is described in the following proceduresRENDERAS="SECT3"ID="FM75377"Loading the REMOTE NLM and RSPX NLM on the serverRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXThe REMOTE NLM, the remote password, and the RSPX NLM. You don't need the Supervisor object right to the remote server because RCONSOLE does not use NetWare Directory Services.A server running NetWare 3.11 or a later version75 KB of available memoryRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8667"BOOK="_idx" COLLECTION="nw41" TIDREF="i3752"
REMOTE [password] MOREINFO="NONE"<Enter>
PAGENUM=585 ID="BP540"IDXID="w8668"BOOK="_idx" COLLECTION="nw41" TIDREF="i3243"
If you do not specify a password as a parameter, you are prompted to enter one. A 
IDXID="w8669"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"IDXID="w8670"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"
password is required. The password you establish here must be entered again when the remote console session is established.PERFORMANCE="REQUIRED"At the server console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IDXID="w8671"BOOK="_idx" COLLECTION="nw41" TIDREF="i3924"
RSPX MOREINFO="NONE"<Enter>You must load the RSPX NLM before you can run a remote console session through a direct connection.When you load RSPX, you have the option to require packet signatures to ensure security. The default is ON, which means that packet signatures are required.However, packets with signatures are not compatible with NetWare 3.11. If you run NetWare 3.11, set packet signatures OFF when you load RSPX. To set 
IDXID="w8672"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
packet signatures OFF, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD RSPX SIGNATURES OFF MOREINFO="NONE"<Enter>For more information about packet signatures, see 
IDREF="FM65804""Preventing Packet Forgery" on page 551.RENDERAS="SECT3"ID="FM46781"Running RCONSOLE.EXE from a Network WorkstationOnce the REMOTE NLM and RSPX NLM are loaded on the server, you can start a remote session from a workstation by executing the RCONSOLE.EXE file and specifying the remote password. You don't need the Supervisor object right to the remote server, since RCONSOLE does not use NetWare Directory Services.The following procedure explains how to run RCONSOLE from a network drive. You can also run RCONSOLE from your local hard drive.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later versionA search drive mapped to the directory where the RCONSOLE.EXE file is located (usually SYS:SYSTEM)300 KB of available memory on the workstationPAGENUM=586 ID="BP541"The remote console passwordPAGENUM=587 ID="BP542"In NetWare 4.1, when you run RCONSOLE, you must enter the password that you establish when you load REMOTE.NLM. The supervisor password does not allow remote access, unless it is set as the password when you load REMOTE.NLM.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Log in to the network.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If you are logging in to a NetWare 4 network, typeMOREINFO="NONE"LOGIN usernameMOREINFO="NONE" <Enter>If you do not have a context specified in your NET.CFG file, see "BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities Reference.PERFORMANCE="REQUIRED"If you are logging in to a NetWare 3 server, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOGIN servername/usernameMOREINFO="NONE" <Enter>Enter your password when prompted.PERFORMANCE="REQUIRED"Make sure you have a drive mapped to the directory where the RCONSOLE.EXE file is located (usually SYS:SYSTEM).If you don't have a drive mapped, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S16:=sys:system MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Start RCONSOLE by completing one of the following steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If you know the name of the server, type the following command, and then skip t
o IDREF="FM18747"Step 6:FORMAT="LINESPECIFIC"MOREINFO="NONE"RCONSOLE servername MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"If you know part of the server name, type the partial name followed by an asterisk:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"RCONSOLE partial_servername*Select a server from the displayed list and then continue with IDREF="FM18747"Step 6.PERFORMANCE="REQUIRED"If you do not know the name of the server, type the following command, and then continue with Step
s 4 and 5:
FORMAT="LINESPECIFIC"MOREINFO="NONE"RCONSOLE MOREINFO="NONE"<Enter>
PAGENUM=588 ID="BP543"PERFORMANCE="REQUIRED"Select SPX from the 
"Connection Type
" menu.A list of servers available for a remote console session appears.PERFORMANCE="REQUIRED"Connect to the server, using one of the following methods:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select a server from the list, and then go t
o IDREF="FM18747"Step 6.PERFORMANCE="REQUIRED"Type the name of the server, and then go t
o IDREF="FM18747"Step 6.PERFORMANCE="REQUIRED"If you know the IPX internal network number of the server, do the following:
MARK=BULLETPress MOREINFO="NONE"<Insert>.Enter the IPX internal network number in hexadecimal notation, then continue with IDREF="FM18747"Step 6.PERFORMANCE="REQUIRED"ID="FM18747"Type the server's remote console password at the prompt.This is the password you established when you loaded REMOTE.NLM.The remote console session is now open. The workstation screen displays the same information you would see on the server console screen.PERFORMANCE="REQUIRED"ID="FM42714"To view a menu of options for the remote session, press 
MOREINFO="NONE"<Alt>+
MOREINFO="NONE"<F1>.
PAGENUM=589 ID="BP544"The remote console 
"Available Options
" menu appears.


FILEREF="n41su51a.tif"IDXID="w8673"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"
During an 
IDXID="w8674"BOOK="_idx" COLLECTION="nw41" TIDREF="i3676"
RCONSOLE session you can use the keys described i
n IDREF="FM76287"Table 7-6. All the other keys function as if you were at the server console.LABEL="7-6" PGWIDE=0 TOCENTRY="1"ID="FM76287" RCONSOLE KeysCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"KeyCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<F1>COLNAME=2 ROTATE="0" MOREROWS="0"Access the "Available Options" menu.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<F2>COLNAME=2 ROTATE="0" MOREROWS="0"Exit Remote Console.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<F3>COLNAME=2 ROTATE="0" MOREROWS="0"Cycle backward through the current console screens.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<F4>COLNAME=2 ROTATE="0" MOREROWS="0"Cycle forward through the current console screens.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<F5>COLNAME=2 ROTATE="0" MOREROWS="0"Show the address of the workstation you are using for this session.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<F1>COLNAME=2 ROTATE="0" MOREROWS="0"Display Remote Console help when the Remote Console "Available Options" menu is on the screen. (When another screen is showing, this key displays the relevant server help information.)PAGENUM=590 ID="BP545"RENDERAS="SECT3"Ending a Remote Console SessionIDXID="w8675"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"You can exit the remote session from either the "Available Options" menu or the console prompt.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the "Available Options" menu, select "End Remote Session With Server," or from the console prompt, press MOREINFO="NONE"<Alt>+<F2>.PERFORMANCE="REQUIRED"Choose "Yes" from the "Quit Remote Console Session?" box.The next screen to appear depends upon how you invoked RCONSOLE.If you specified the name of a specific server as a parameter when you executed RCONSOLE, the remote session with that server is ended and the DOS prompt is redisplayed.If you selected the server from a list of available servers, the available servers list is redisplayed. To exit from the list of servers, press 
MOREINFO="NONE"<Esc> and then select "Yes" from the "Exit Remote Console?" menu.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PasswordsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Password" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"RCONSOLE.EXECOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"RCONSOLE" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Remote consoleCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Remote console" in ConceptsPAGENUM=591 ID="BP546"RENDERAS="SECT2"ID="FM72853"Running a Remote Console Session Over a ModemIDXID="w8676"BOOK="_idx" COLLECTION="nw41" TIDREF="i2485"IDXID="w8677"BOOK="_idx" COLLECTION="nw41" TIDREF="i3676"
IDXID="w8678"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"This section explains how to run a remote console session over an asynchronous connection---a connection using a modem or null modem cable. To run the session, you must complete the following steps:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDXID="w8679"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"
On the server, load REMOTE.NLM, AIO.NLM, and RS232.NLM. Also load the appropriate communications port driver, such as AIOCOMX.NLM.Create a callback file, if desired.Load necessary workstation files.Execute RCONSOLE.EXE from the workstation and, on first execution, configure the modem.Each of these tasks is explained in the following procedures.RENDERAS="SECT3"ID="FM68199"Loading Modules on the ServerRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXThe following NLM files:REMOTE.NLMRS232.NLMAIO.NLMA communications port driver such as AIOCOMXRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD REMOTE [password] MOREINFO="NONE"<Enter>Enter the password you want to use when accessing the server from the remote workstation. A password is required.
PAGENUM=592 ID="BP547"PERFORMANCE="REQUIRED"Complete the following steps to load the communications interface module and driver:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Load the communications 
IDXID="w8680"BOOK="_idx" COLLECTION="nw41" TIDREF="i146"
port interface module by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD AIO MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Load the 
IDXID="w8681"BOOK="_idx" COLLECTION="nw41" TIDREF="i148"IDXID="w8682"BOOK="_idx" COLLECTION="nw41" TIDREF="i703"
communications port driver by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD AIOCOMX MOREINFO="NONE"<Enter>This driver is provided with NetWare. You can replace it with an equivalent driver if you choose.PERFORMANCE="REQUIRED"Load the 
IDXID="w8683"BOOK="_idx" COLLECTION="nw41" TIDREF="i309"
asynchronous connection NLM by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8684"BOOK="_idx" COLLECTION="nw41" TIDREF="i3926"
LOAD RS232 [comm_port] [modem_speed] [N] [C] MOREINFO="NONE"<Enter>Replace comm_ port with the communications port number (1 or 2).Replace modem _speed with the baud rate (2400, 4800, or 9600).Use the "N" parameter if you are using a IDXID="w8685"BOOK="_idx" COLLECTION="nw41" TIDREF="i2485"
null modem cable.Use the "C" parameter if you want to use the callback option. The callback option is explained in the next procedure.RENDERAS="SECT3"ID="FM43917"Creating a Callback ListIDXID="w8686"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"A callback list enables you to create a list of authorized modem numbers that can be used to access the server.When a connection attempt is made, the server notes the number of the modem that is calling and then terminates the connection. The server then compares the number to the numbers in the callback list.If the number is in the list, the server calls the modem at that number and reestablishes the connection. If it is not in the list, the server ignores the call.PAGENUM=593 ID="BP548"If you included the callback parameter when you loaded RS232.NLM in the preceding section (IDREF="FM68199""Loading Modules on the Server"), complete the following steps:RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Create a IDXID="w8687"BOOK="_idx" COLLECTION="nw41" TIDREF="i581"
CALLBACK.LST file in the SYS:SYSTEM directory on the server.Use a text editor or the EDIT utility to create the file. If you need help creating the file, see 
IDREF="FM88816""Editing Text Files from the Server Console" on page 449.PERFORMANCE="REQUIRED"In the file, enter a list of modem numbers that are authorized to start a remote console session.For example, you might list three modem numbers:
TYPE="VERT"1801555225755543214269The first number authorizes a modem for a long distance number (with an area code), the second number is a local telephone number, and the third number is for a modem where only the extension number is required.PERFORMANCE="REQUIRED"Save the text file.
PAGENUM=594 ID="BP549"RENDERAS="SECT3"ID="FM19601"Preparing the WorkstationRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Prepare the workstation as a remote console by creating a directory and copying the following RCONSOLE run files to it:TYPE="VERT"IDXID="w8688"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"
RCONSOLE.EXERCONSOLE.HEPRCONSOLE.MSGIBM_RUN.OVL_RUN.OVLIBM_AIO.OVL_AIO.OVLTEXTUTIL.HEPTEXTUTIL.IDXTEXTUTIL.MSGIt doesn't matter where you place the directory or what you name it. The run files come with your NetWare system.RENDERAS="SECT3"ID="FM17536"Running RCONSOLE.EXE and Configuring the ModemRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation with a Hayes*-compatible modem (2400, 4800, or 9600 baud) or a null modem cable connected to the server300 KB of available memory on the workstationREMOTE.NLM, AIO.NLM, RS232.NLM, and the communications port driver (such as AIOCOMX) loaded on the serverAll necessary files loaded on the workstationThe remote console passwordPAGENUM=595 ID="BP550"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the workstation, change to the directory you created for the remote files (described in the preceding section, IDREF="FM19601""Preparing the Workstation") and typeFORMAT="LINESPECIFIC"MOREINFO="NONE"RCONSOLE MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select 
"Asynchronous
" from the 
"Connection Type
" menu.PERFORMANCE="REQUIRED"If this is the first session from this workstation, set up your modem by selecting 
"Configuration
" from the 
"Asynchronous Options
" menu, 
and then complete Step
s 4 throug
h 6. Otherwise, skip t
o IDREF="FM80734"Step 7.PERFORMANCE="REQUIRED"IDXID="w8689"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"
In the 
"Current Modem Configuration
" window, set the options according to your modem and workstation specifications.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Use the arrow keys to highlight a field, and press 
MOREINFO="NONE"<Enter>.Either the cursor becomes active in the field or a selection list is displayed.PERFORMANCE="REQUIRED"If the cursor is active in the field, type in the appropriate information. If a selection list is displayed, select the appropriate item. Press 
MOREINFO="NONE"<Enter>.The "UserID" and the "Call Back" fields must be filled in.Choose any string for the UserID. For example, you may use your name or your phone number. This ID is displayed on the server console during the remote session.In the "Call Back" field, enter the phone number you are calling from. If the "callback" option is used, this number must be in the callback list.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to exit the window.PERFORMANCE="REQUIRED"Choose "Yes" from the "Save Changes?" box to save your configuration.PERFORMANCE="REQUIRED"ID="FM80734"Choose "Connect to Remote Location" from the "Asynchronous Options" menu.A list of available servers is displayed.
PAGENUM=596 ID="BP551"PERFORMANCE="REQUIRED"Select a server.If you are using the callback option, the server terminates the connection and compares the number in the modem configuration file with the numbers in the callback list.If the number in the modem configuration file is in the list, the server dials the number to establish the connection and then displays the console prompt. If the number is not in the list, the server displays an 

error message.PERFORMANCE="REQUIRED"Once the console prompt is displayed, press 
MOREINFO="NONE"<Alt>+<F1> to view the 
"Available Options
" menu for the remote console session.During the RCONSOLE session, you may use the keystrokes shown i
n IDREF="FM76287"Table 7-6 on page 589. All other keys function as if you were at the server console.RCONSOLE does not provide guaranteed packet delivery. When sending or receiving packets from a server with extensive disk or LAN activity, IDXID="w8690"BOOK="_idx" COLLECTION="nw41" TIDREF="i3676"
RCONSOLE may "IDXID="w8691"BOOK="_idx" COLLECTION="nw41" TIDREF="i4482"
time out."If this happens, you receive a "No response from server" or an "Unable to send request to server" message. If you receive one of these 
messages, retry the operation.RENDERAS="SECT3"ID="FM56288"Ending a Remote Console SessionYou can exit the remote session from either the "Available Options" menu or the console prompt.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the "Available Options" menu, select "End Remote Session," or from the console prompt, press MOREINFO="NONE"<Alt>+<F2>.PERFORMANCE="REQUIRED"Select 
"Yes
" from the 
"Quit Remote Console Session?
" box.
PAGENUM=597 ID="BP552"RENDERAS="SECT2"ID="FM20424"Loading Remote Modules on BootupIDXID="w8692"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"You can put commands in the AUTOEXEC.NCF file to load remote console modules each time the server is booted.Since these modules require the remote password, you may choose to place an encrypted version of the password in the file, too. The encrypted password secures the server console by hiding the remote console password from users who access the AUTOEXEC.NCF file.The following procedure explains how to set an encrypted password and what commands to place in the AUTOEXEC.NCF file.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXThe remote console passwordRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"IDXID="w8693"BOOK="_idx" COLLECTION="nw41" TIDREF="i3243"
To encrypt a password, type the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD REMOTE MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"IDXID="w8694"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"
Execute the following command:
FORMAT="LINESPECIFIC"MOREINFO="NONE"REMOTE ENCRYPT MOREINFO="NONE"<Enter>The server prompts you to enter the password to be encrypted.PERFORMANCE="REQUIRED"Enter the password you want to use for remote console sessions.The system displays the encrypted value and a message asking if the LOAD REMOTE command should be written to the SYS:SYSTEM\LDREMOTE.NCF file.PERFORMANCE="REQUIRED"Respond "Yes."When you respond "Yes," the system places a LOAD REMOTE command into this file with the encrypted password as a parameter.
PAGENUM=598 ID="BP553"You can execute this file whenever you want to load the REMOTE NLM
, or you can place the command to execute the file into your AUTOEXEC.NCF file. This feature saves you from having to type in the encrypted password, which is often quite long.PERFORMANCE="REQUIRED"Use either INSTAL
L or EDI
T to open the AUTOEXEC.NCF file.For information about editing .NCF files, see 
IDREF="FM33588""Creating or Editing a Server Batch (.NCF) File" on page 448.PERFORMANCE="REQUIRED"Move the cursor to the end of the file and type the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LDREMOTEPERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"For direct connections, type the following after LDREMOTE:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD RSPXPERFORMANCE="REQUIRED"For asynchronous connections, type the following after LDREMOTE:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD AIO
MOREINFO="NONE"LOAD AIOCOMXThe AIOCOMX driver is provided with NetWare. You can replace it with an equivalent driver if you choose.FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD RS232 [comm_portMOREINFO="NONE"] [modem_speedMOREINFO="NONE"]MOREINFO="NONE" [N] [C]Replace comm_ port with the communications port number (1 or 2).Replace modem _speed with the baud rate (2400, 4800, or 9600).Use the "N" parameter if you are using a IDXID="w8695"BOOK="_idx" COLLECTION="nw41" TIDREF="i2485"
null modem cable.Use the "C" parameter if you want to use the callback option. For information and instructions, see IDREF="FM43917""Creating a Callback List" on page 592.PERFORMANCE="REQUIRED"Exit and save the AUTOEXEC.NCF file.The server will now automatically load the necessary remote modules whenever it is booted.
PAGENUM=599 ID="BP554"RENDERAS="SECT3"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"EDIT utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"EDIT" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"LOAD commandCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"LOAD" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"RCONSOLE utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"RCONSOLE" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"REMOTE utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"REMOTE" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"RS232 utilityCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"RS232" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"RSPX utility (including the Packet Signatures option)COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"RSPX" in Utilities ReferenceRENDERAS="SECT2"IDXID="w8696"BOOK="_idx" COLLECTION="nw41" TIDREF="i2739"IDXID="w8697"BOOK="_idx" COLLECTION="nw41" TIDREF="i3748"IDXID="w8698"BOOK="_idx" COLLECTION="nw41" TIDREF="i4685"
Upgrading Files on a Remote ServerIDXID="w8699"BOOK="_idx" COLLECTION="nw41" TIDREF="i3762"You can use a remote console to copy new NetWare files to a server. Files can be copied from diskettes, a CD-ROM drive, a local drive, or from a network directory. To copy new NetWare files to volume SYS: on a remote server, follow these steps.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXNetWare diskettes or CD-ROM drive, if needed.Workstation and server prepared for remote console sessions. See IDREF="FM61980""Running a Remote Console Session Through a Direct Connection" on page 584 and IDREF="FM72853""Running a Remote Console Session Over a Modem" on page 591.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Start a remote console session with the server.To start a session over a LAN, see 
IDREF="FM46781""Running RCONSOLE.EXE from a Network Workstation" on page 585.To start a session over a modem connection, see 
IDREF="FM17536""Running RCONSOLE.EXE and Configuring the Modem" on page 594.
PAGENUM=600 ID="BP555"PERFORMANCE="REQUIRED"At the remote console, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Choose "Copy Files Option" from the "Installation Options" menu.PERFORMANCE="REQUIRED"Choose a remote path.This is the path from which the files will be installed. You may load files from NetWare diskettes, a local drive, 
a CD-ROM, or a network drive.PERFORMANCE="REQUIRED"Follow the subsequent prompts.RENDERAS="SECT2"Installing or Reconfiguring Applications on a Remote ServerIDXID="w8700"BOOK="_idx" COLLECTION="nw41" TIDREF="i3762"You can use a remote console session to install or reconfigure Novell or third-party products on a remote server. Follow these steps.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXApplication diskettes, if necessary.Workstation and server prepared for remote console sessions. See IDREF="FM61980""Running a Remote Console Session Through a Direct Connection" on page 584 and IDREF="FM72853""Running a Remote Console Session Over a Modem" on page 591.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Start a remote console session with the server.To start a session over a LAN, see 
IDREF="FM46781""Running RCONSOLE.EXE from a Network Workstation" on page 585.To start a session over a modem connection, see 
IDREF="FM17536""Running RCONSOLE.EXE and Configuring the Modem" on page 594.PERFORMANCE="REQUIRED"At the remote console, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>
PAGENUM=601 ID="BP556"PERFORMANCE="REQUIRED"Choose "Product Options" from the "Installation Options" menu.PERFORMANCE="REQUIRED"Select "View/Configure/Remove Installed Products" from the "Other Installation Actions" menu.A list of currently installed products (if any) appears.PERFORMANCE="REQUIRED"To reconfigure an installed product, select that product and press 
MOREINFO="NONE"<Enter>. Follow screen instructions.PERFORMANCE="REQUIRED"To install a new product, press 
MOREINFO="NONE"<Insert>.A message states that the product will be installed from the A: drive, unless otherwise indicated.PERFORMANCE="REQUIRED"If necessary, insert the product installation diskette into the drive.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to accept the default, drive A:, or press 
MOREINFO="NONE"<F3> to enter a different installation source path.PERFORMANCE="REQUIRED"Follow the prompts to install the product.RENDERAS="SECT2"Rebooting a Remote ServerIDXID="w8701"BOOK="_idx" COLLECTION="nw41" TIDREF="i499"IDXID="w8702"BOOK="_idx" COLLECTION="nw41" TIDREF="i3697"IDXID="w8703"BOOK="_idx" COLLECTION="nw41" TIDREF="i499"
You can IDXID="w8704"BOOK="_idx" COLLECTION="nw41" TIDREF="i3762"
reboot a NetWare server from a remote console by first modifying the server's AUTOEXEC.BAT file and then executing another .NCF file that you create for this purpose.RENDERAS="SECT3"Preparing the ServerRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXCommands in the server AUTOEXEC.NCF file that load the remote modules. See IDREF="FM20424""Loading Remote Modules on Bootup" on page 597.PAGENUM=602 ID="BP557"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"To automatically reboot the server, put commands to change to the NetWare 4.1 directory and execute SERVER.EXE in the server's IDXID="w8705"BOOK="_idx" COLLECTION="nw41" TIDREF="i359"
AUTOEXEC.BAT file.For example, if the SERVER.EXE file is in the NET_4.1 directory on drive C:, put the following lines in the server's AUTOEXEC.BAT file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"CD C:\NET_4.1
SERVER.EXEPERFORMANCE="REQUIRED"Start a remote console session with the server.To start a session over a LAN, see 
IDREF="FM46781""Running RCONSOLE.EXE from a Network Workstation" on page 585.To start a session over a modem connection, see 
IDREF="FM17536""Running RCONSOLE.EXE and Configuring the Modem" on page 594.PERFORMANCE="REQUIRED"Load the EDIT NLM on the server by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD EDIT MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Create an .NCF file and include the following commands in the order given:
FORMAT="LINESPECIFIC"MOREINFO="NONE"REMOVE DOS
DOWN
EXITSee 
IDREF="FM33588""Creating or Editing a Server Batch (.NCF) File" on page 448.PERFORMANCE="REQUIRED"Save the file in the SYS:SYSTEM directory.
PAGENUM=603 ID="BP558"RENDERAS="SECT3"Rebooting the ServerRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Start a remote console session with the server.To start a session over a LAN, see 
IDREF="FM46781""Running RCONSOLE.EXE from a Network Workstation" on page 585.To start a session over a modem connection, see 
IDREF="FM17536""Running RCONSOLE.EXE and Configuring the Modem" on page 594.PERFORMANCE="REQUIRED"Send a message to all users to inform them that the server is going down.See 
IDREF="FM96671""Sending Console Messages to Workstations" on page 434 if you need help sending a message.PERFORMANCE="REQUIRED"At the system prompt on the remote console, enter the name of the .NCF file you created.This reboots the server. The keyboard is disabled for a few minutes while the file is processed.When the file has finished processing, a "connection is lost" message appears.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to exit the remote session.PERFORMANCE="REQUIRED"Open a new remote console connection with the server.
PAGENUM=604 ID="BP559"RENDERAS="SECT1"Administering AccountingThis section describes how to set up NetWare accounting, calculate charge rates for using server resources, and view various system statistics.RENDERAS="SECT2"ID="FM83385"Setting Up AccountingAccounting allows you to monitor IDXID="w8706"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
NetWare server usage and charge users for server resources.RENDERAS="SECT3"Setting Up Accounting Using the NetWare AdministratorIDXID="w8707"BOOK="_idx" COLLECTION="nw41" TIDREF="i70"PrerequisitesMARK=CHECKBOXA 386 or 486 workstation running Windows 3.1 or OS/2 v2.x and NetWare Administrator.6 MB of available memory on the Windows workstation, or 12 MB of available memory on the OS/2 workstation.Supervisor object right to the Server object where you are setting up accounting.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the Windows Program Manager or the OS/2 desktop, choose the "NetWare Administrator" icon.PERFORMANCE="REQUIRED"Select the Server object you want to set up accounting for.PERFORMANCE="REQUIRED"From the "Object" menu, Choose "Detail
s."PERFORMANCE="REQUIRED"From the bottom of the dialog box, choose "Accounting.
"PERFORMANCE="REQUIRED"To confirm that you want to install accounting on this server, choose "Yes.
"Accounting page buttons appear on the right side of the dialog box with the other page buttons.
PAGENUM=605 ID="BP560"PERFORMANCE="REQUIRED"Use the accounting buttons to edit the accounting pages.PERFORMANCE="REQUIRED"Choose "OK."RENDERAS="SECT3"Setting Up Accounting Using NETADMINIDXID="w8708"BOOK="_idx" COLLECTION="nw41" TIDREF="i70"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later.A minimum of 512 KB of memory available on the workstation.Supervisor object right to the Server object you want to set up accounting for.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the workstation prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "NetAdmin Options" menu, choose "Manage Object
s."PERFORMANCE="REQUIRED"Select the Server object you want to set up accounting for by completing the following steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If the server appears on the list, select it and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"If the server is not on the list, browse the directory by selecting objects and pressing 
MOREINFO="NONE"<Enter> until you see the server you want. Select it and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Choose "View or Edit Properties of this Objec
t."PERFORMANCE="REQUIRED"Choose "Accountin
g."PERFORMANCE="REQUIRED"From the "Install Accounting" prompt, choose "Ye
s."PERFORMANCE="REQUIRED"Choose "Accounting Server
s."PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert>.
PAGENUM=606 ID="BP561"PERFORMANCE="REQUIRED"From the list of possible servers, choose "NetWare Serve
r."PERFORMANCE="REQUIRED"Enter the name of the server, or press 
MOREINFO="NONE"<Insert> and select a server from the list.PERFORMANCE="REQUIRED"To return to the "Accounting Options" menu, press 
MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"Choose the options you want to set up from the menu.Press 
MOREINFO="NONE"<F1> if you need help with any of the options.PERFORMANCE="REQUIRED"To exit NETADMIN, press 
MOREINFO="NONE"<Alt>MOREINFO="NONE"+MOREINFO="NONE"<F10>.RENDERAS="SECT2"Calculating Charge Rates for AccountingIDXID="w8709"BOOK="_idx" COLLECTION="nw41" TIDREF="i621"Charge rates for using server resources are specified as multipliers and divisors. To set the charge amount to "No Charge," enter 0 as the multiplier. Use the following IDXID="w8710"BOOK="_idx" COLLECTION="nw41" TIDREF="i1554"
formula to IDXID="w8711"BOOK="_idx" COLLECTION="nw41" TIDREF="i70"
calculate a charge rate:FILEREF="n40su13a.tif"For example, if you want to charge $200 per month for server disk storage, and there are usually 100,000 blocks used each month on your hard drive:MARK=BULLET20,000 would be the multiplier ($200 in cents)100,000 would be the divisor (disk block usage per month)Therefore, users would be charged two-tenths of one cent per disk block used.FILEREF="n40su14a.tif"PAGENUM=607 ID="BP562"RENDERAS="SECT2"Viewing Accounting TotalsIDXID="w8712"BOOK="_idx" COLLECTION="nw41" TIDREF="i70"The ATOTAL utility provides a total for the accounting services used on your network. ATOTAL compiles information from the system accounting records and lists the following:MARK=BULLETTotal connect time in minutesTotal service requestsTotal blocks readTotal blocks writtenTotal disk storage in blocks per dayRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later, or OS/2 v2.x.Accounting set up on the NetWare server. (See IDREF="FM83385""Setting Up Accounting" on page 604.)Supervisor object right to the Server object you want to see accounting information for.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Change to the SYS:SYSTEM directory.PERFORMANCE="REQUIRED"To view daily and weekly totals for accounting services, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w8713"BOOK="_idx" COLLECTION="nw41" TIDREF="i318"
ATOTALMOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"To redirect ATOTAL data to a file, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"ATOTAL > filename MOREINFO="NONE"<EnterMOREINFO="NONE">LABEL="8"PAGENUM=609 ID="BP563"ID="FM77303"Auditing Network EventsRENDERAS="SECT1"What Is NetWare  Auditing?IDXID="w8714"BOOK="_idx" COLLECTION="nw41" TIDREF="i344"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. A transaction is defined here as any action that changes the NetWare Directory ServicesTM (NDS) database or a volume's content.Auditors can audit NDSTM events as well as those specific to a file system volume or a server. Some of the events that can be audited are shown in the following figure.LABEL="8-1" FLOAT="0"IDXID="w8715"BOOK="_idx" COLLECTION="nw41" TIDREF="i344"ID="FM70384"Events You Can AuditFILEREF="n40su21a.tif"PAGENUM=610 ID="BP564"Auditors can track events and activities on the network, but they do not have rights to open or modify network files, other than Audit 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 for auditing of NDS events.The 
AUDITCON program files are installed automatically on your system when you install or upgrade to NetWare 4TM.The procedures in this chapter address two audiences. IDREF="FM12287""Enabling Auditing" on page 612 is for the network supervisor. IDREF="FM67818""Auditor Procedures" on page 617 and IDREF="FM45557""Creating Audit Reports" on page 632 are for those assigned to audit NDS events or changes to NetWare volumes.IDREF="FM74793"Figure 8-2 illustrates the responsibilities of the network supervisor and the auditor.PAGENUM=611 ID="BP565"LABEL="8-2" FLOAT="0"IDXID="w8716"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"ID="FM74793"Network Supervisor and Auditor TasksFILEREF="n40su23a.tif"Audit 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 entered into the Audit files.PAGENUM=612 ID="BP566"The files continue to accept records until auditing is disabled or the file gets full.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AuditingCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Auditing" in Concepts"BOOK="utlrfenu" COLLECTION="nw41"AUDITCON" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Audit files and how they workCOLNAME=2 ROTATE="0" MOREROWS="0" IDREF="FM43852""Maintaining Audit Files" on page 638RENDERAS="SECT1"ID="FM12287"Enabling AuditingRENDERAS="SECT2"Creating a Directory and an Auditor User ObjectIDXID="w8717"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"IDXID="w8718"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"
IDXID="w8719"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterThe Supervisor or equivalent rights in the file system where you want to create the auditor's directoryThe Create object right in the container where you will create the auditor as a User objectRENDERAS="SECT3"ProcedureIDXID="w8720"BOOK="_idx" COLLECTION="nw41" TIDREF="i344"PERFORMANCE="REQUIRED"Create a directory in the file system for the auditor to use.The auditor needs space to store audit reports. Consider creating a directory in SYS:HOME or wherever you have created other user account directories.PERFORMANCE="REQUIRED"Create the auditor as a User object.If the auditor will audi
t NetWare Directory Services events, assign him or her the Browse object right in the container objects to be audited.
PAGENUM=613 ID="BP567"PERFORMANCE="REQUIRED"Give the auditor trustee rights to the directory you created for th
e auditor.You can grant the auditor the Supervisor trustee right to the directory, or you can assign the auditor all rights but the Supervisor right. Either method produces the same result
.PERFORMANCE="REQUIRED"Map a drive to the directory containing the audit program files.If you have not included a search drive mapping to SYS:PUBLIC in the system login script, create a user login script for the auditor and map a drive to this directory.Also give the auditor the Browse object right and the File Scan directory trustee right to SYS:PUBLIC. (AUDITCON and Unicode files are in SYS:PUBLIC, unless you move them).RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Assigning rights to directories and filesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99516""Understanding File and Directory Rights" on page 138 and IDREF="FM40052""Adding a Trustee to a Directory or File" on page 141COLNAME=1 ROTATE="0" MOREROWS="0"Creating a file system directoryCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM42808""Creating Directories and Copying Files" on page 117COLNAME=1 ROTATE="0" MOREROWS="0"Creating a User objectCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM76532""Creating Leaf Objects" on page 47COLNAME=1 ROTATE="0" MOREROWS="0"Assigning trustee rights to a userCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM40052""Adding a Trustee to a Directory or File" on page 141COLNAME=1 ROTATE="0" MOREROWS="0"Creating user login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM36951""Creating, Modifying, Copying, and Printing Login Scripts" on page 182COLNAME=1 ROTATE="0" MOREROWS="0"Modifying the system login scriptCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM36951""Creating, Modifying, Copying, and Printing Login Scripts" on page 182COLNAME=1 ROTATE="0" MOREROWS="0"Assigning rights to objectsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM92449""Rights Needed to Create and Manage Objects" on page 31.PAGENUM=614 ID="BP568"RENDERAS="SECT2"ID="FM12641"Enabling Auditing for a VolumeIDXID="w8721"BOOK="_idx" COLLECTION="nw41" TIDREF="i344"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 470 KB of memory available on the workstationSupervisor object right to the Volume object where you are enabling auditingRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Access the auditing utility by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"AUDITCON MOREINFO="NONE"<Enter>Your current server and volume are displayed at the top of the screen. If you want a different server or volume than the one shown, complete Ste
p 2.PERFORMANCE="REQUIRED"(Optional) Change the server or volume.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "Change Current Server" or "Change Current Volume" from the "Available Audit Options" menu.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert> to see a list of available server
s.PERFORMANCE="REQUIRED"Select the serve
r, and then select the volume.PERFORMANCE="REQUIRED"Select "Enable Volume Auditing" from the "Available Audit Options" menu.PERFORMANCE="REQUIRED"Enter a password for the volume.PERFORMANCE="REQUIRED"Enter the password again when prompted.PERFORMANCE="REQUIRED"Notify the auditor of the password.After auditing is enabled, the independent auditor assumes control of the program. If the auditor changes the password, the supervisor no longer has access to auditing information.Se
e IDREF="FM67818""Auditor Procedures" on page 617.PAGENUM=615 ID="BP569"RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AuditingCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Auditing" in Concepts"BOOK="utlrfenu" COLLECTION="nw41"AUDITCON" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"PasswordsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Password" in ConceptsRENDERAS="SECT2"Enabling Auditing for a NetWare Directory Services ContainerIDXID="w8722"BOOK="_idx" COLLECTION="nw41" TIDREF="i3114"IDXID="w8723"BOOK="_idx" COLLECTION="nw41" TIDREF="i3114"
IDXID="w8724"BOOK="_idx" COLLECTION="nw41" TIDREF="i807"IDXID="w8725"BOOK="_idx" COLLECTION="nw41" TIDREF="i344"When you enable auditing for a container object (Organization or Organizational Unit), it does not enable auditing for subordinate container objects.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 470 KB of memory available on the workstationSupervisor object rights to the container holding the Server objectRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Log in to the network from the workstation.PERFORMANCE="REQUIRED"Access the auditing utility by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"AUDITCON MOREINFO="NONE"<Enter>Your current server and volume are displayed at the top of the screen.PERFORMANCE="REQUIRED"Select "Audit Directory Services" from the "Available Audit Options" menu.Your current context is displayed at the top of the screen. If you want a different context than the one shown, complete Ste
p 4.
PAGENUM=616 ID="BP570"PERFORMANCE="REQUIRED"(Optional) Change the context.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "Change Session Context" from the "Audit Directory Services" menu.PERFORMANCE="REQUIRED"Enter the context for the container where auditing is being enabled, and press 
MOREINFO="NONE"<Enter>.Type the Organizational Unit name before the displayed organization name, and separate the two by a period. For example, a graphical representation of a directory tree with the "Sales" Organizational Unit is shown below.LABEL="8-3" FLOAT="0"Sample Directory TreeFILEREF="n41su18a.tif"The context for the container is:FORMAT="LINESPECIFIC"MOREINFO="NONE"SALES.NOVELLPERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to get back to the "Available Audit Option
s" menu.PERFORMANCE="REQUIRED"Select "Audit Directory Tree" from the "Audit Directory Services" menu.PERFORMANCE="REQUIRED"Browse the Directory tree to locate the container where you are enabling auditing, and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Select "Enable Container Auditing" from the "Available Audit Options" menu.PERFORMANCE="REQUIRED"Enter a password for the container.PERFORMANCE="REQUIRED"Enter the password again when prompted.
PAGENUM=617 ID="BP571"PERFORMANCE="REQUIRED"Notify the auditor of the password.PERFORMANCE="REQUIRED"Select "Display Audit Status."PERFORMANCE="REQUIRED"Verify tha
t "Auditing Status" is On.After auditing is enabled, the independent auditor assumes control of the program. If the auditor changes the password, the supervisor no longer has access to auditing information.Auditor procedures begin in the following section.RENDERAS="SECT3"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information aboutCOLNAME=2 ROTATE="0" MOREROWS="0"Refer toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AuditingCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Auditing" in Concepts"BOOK="utlrfenu" COLLECTION="nw41"AUDITCON" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"PasswordsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Password" in ConceptsRENDERAS="SECT1"ID="FM67818"IDXID="w8726"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"
Auditor ProceduresIDXID="w8727"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"
To keep your audit information secure, we suggest that you perform the following tasks before you begin auditing:MARK=BULLETChange the auditing password given to you by the network supervisor. (See IDREF="FM26418""Setting Passwords" on page 618.)Log in to the volume or container using the new password. (See IDREF="FM78992""Logging In" on page 621.)Set your preferences for the auditing environment. (See IDREF="FM66616""Setting Up Your Work Environment" on page 624.)From this point, you can select what you want to audit and create reports based on the audit records you collect. (See IDREF="FM34956""Selecting Items to Audit" on page 628.)PAGENUM=618 ID="BP572"RENDERAS="SECT2"ID="FM26418"Setting PasswordsIDXID="w8728"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"RENDERAS="SECT3"Changing the Password for a VolumeIDXID="w8729"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 470 KB of memory available on the workstationThe password assigned to the volume by the network supervisor or the password currently being usedThe Browse right to the volume you are auditingRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Log in to the network from the workstation.PERFORMANCE="REQUIRED"Access the auditing utility by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"AUDITCON MOREINFO="NONE"<Enter>Your current server and volume are displayed at the top of the screen. If you want a different server or volume than the one shown, complete Step 3.PERFORMANCE="REQUIRED"(Optional) Change the server or volume.
MARK=BULLETTo change to a different server, select "Change Current Server" from the "Available Audit Options" menu, and then select the server you want.To change to a different volume, select "Change Current Volume" from the "Available Audit Options" menu, and then select the volume you want.PERFORMANCE="REQUIRED"Selec
t "Auditor Volume Login" from the "Available Audit Options" menu.A password prompt for the volume appears.PERFORMANCE="REQUIRED"Type in the current auditing password for the volume.
PAGENUM=619 ID="BP573"PERFORMANCE="REQUIRED"Select "Auditing Configuration" from the "Available Audit Options" menu.PERFORMANCE="REQUIRED"Select "Change Audit Password" from the "Auditing Configuration" menu.PERFORMANCE="REQUIRED"Enter the current password.PERFORMANCE="REQUIRED"Enter the new password.PERFORMANCE="REQUIRED"Retype the new password.The password is changed.RENDERAS="SECT3"Changing the Auditor Password for a NetWare Directory Services ContainerIDXID="w8730"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"IDXID="w8731"BOOK="_idx" COLLECTION="nw41" TIDREF="i807"
IDXID="w8732"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 470 KB of memory available on the workstationThe password assigned to the containerThe Browse right to the container you are auditing.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Log in to the network from the workstation.PERFORMANCE="REQUIRED"Access the auditing utility by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"AUDITCON MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select 
"Audit Directory Services
" from the "Available Audit Options" menu.Your current context is displayed at the top of the screen. If you want a different context than the one shown, complete Ste
p 4.
PAGENUM=620 ID="BP574"PERFORMANCE="REQUIRED"(Optional) Change the current context.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "Change Session Context" from the "Audit Directory Services" menu.PERFORMANCE="REQUIRED"Enter the context to the container where you are enabling auditing, and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Select 
"Audit Directory Tree
" from the 
"Audit Directory Services
" menu.PERFORMANCE="REQUIRED"Locate the container where you are enabling auditing by pressing 
MOREINFO="NONE"<Enter> to move around in the Director
y tree.PERFORMANCE="REQUIRED"Select the container you want and press 
MOREINFO="NONE"<F10>.You will see only containers to which you have been given the Browse right. If you do not see the container you want to audit, contact the network supervisor.PERFORMANCE="REQUIRED"Select "Auditor Container Login" from the "Available Audit Options" menu.PERFORMANCE="REQUIRED"Enter the current container password.PERFORMANCE="REQUIRED"Select "Auditing Configuration" from the "Available Audit Options" menu.PERFORMANCE="REQUIRED"Select "Change Audit Password" from the "Auditing Configuration" menu.PERFORMANCE="REQUIRED"Type in the current password for the container.PERFORMANCE="REQUIRED"Enter the new password.PERFORMANCE="REQUIRED"Retype the new password.The password is changed.
PAGENUM=621 ID="BP575"RENDERAS="SECT3"Setting and Changing Second-Level PasswordsIDXID="w8733"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"IDXID="w8734"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"As an auditor, you can set an additional level of security for your audit records by enabling a second-level password.If you set this option, a second password is required before any changes to the audit configurations or report filters can be made.Instructions for enabling and changing a second-level password are in IDREF="FM66616""Setting Up Your Work Environment" on page 624.RENDERAS="SECT2"ID="FM78992"Logging InRENDERAS="SECT3"Logging In to a VolumeIDXID="w8735"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"IDXID="w8736"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 470 KB of memory available on the workstationThe password assigned to the volumeRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Log in to the network.PERFORMANCE="REQUIRED"Access the auditing utility by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"AUDITCON MOREINFO="NONE"<Enter>Your current server and volume are displayed at the top of the screen. If you want a different server or volume than the one shown, complete Ste
p 3.
PAGENUM=622 ID="BP576"PERFORMANCE="REQUIRED"(Optional) Change the server or volume.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"To change to a different server, select "Change Current Server" from the "Available Audit Options" menu, and then select the server you want.PERFORMANCE="REQUIRED"To change to a different volume, select "Change Current Volume from the "Available Audit Options" menu, and then select the volume you want.PERFORMANCE="REQUIRED"Select "Auditor Volume Login" from the "Available Audit Options" menu.A password prompt for the volume appears.PERFORMANCE="REQUIRED"Type the auditing password for the volume.RENDERAS="SECT3"Logging in to a NetWare Directory Services ContainerIDXID="w8737"BOOK="_idx" COLLECTION="nw41" TIDREF="i3114"IDXID="w8738"BOOK="_idx" COLLECTION="nw41" TIDREF="i3114"
IDXID="w8739"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"IDXID="w8740"BOOK="_idx" COLLECTION="nw41" TIDREF="i807"
IDXID="w8741"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 470 KB of memory available on the workstationThe password assigned to the container by the network supervisor or the password currently being usedBrowse right to the container you want to auditRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Log in to the network.PERFORMANCE="REQUIRED"Access the auditing utility by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"AUDITCON MOREINFO="NONE"<Enter>The current server and volume are displayed at the top of the screen.
PAGENUM=623 ID="BP577"PERFORMANCE="REQUIRED"Select "Audit Directory Services" from the "Available Audit Options" menu.Your current context is displayed at the top of the screen. If you want a different context than the one shown, complete Ste
p 4.PERFORMANCE="REQUIRED"(Optional) Change the current context.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "Change Session Context" from the "Audit Directory Services" menu.PERFORMANCE="REQUIRED"Enter the context to the container where you are enabling auditing, and press 
MOREINFO="NONE"<Enter>.Type the Organizational Unit name before the displayed organization name, and separate the two by a period.For example, a graphical representation of a Directory tree with the "Sales" Organizational Unit is shown below.LABEL="8-4" FLOAT="0"Sample Directory TreeFILEREF="n41su18a.tif"The context for the container is:FORMAT="LINESPECIFIC"MOREINFO="NONE"SALES.NOVELLPERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to get back to the "Available Audit Option
s" menu.PERFORMANCE="REQUIRED"Select "Audit Directory Tree" from the "Audit Directory Services" menu.PERFORMANCE="REQUIRED"Locate the container where you are enabling auditing by using the Up- and Down-arrow keys and pressing 
MOREINFO="NONE"<Enter> to move around in the Directory tree.
PAGENUM=624 ID="BP578"PERFORMANCE="REQUIRED"Select the container you want and press 
MOREINFO="NONE"<F10>.You will see only containers to which you have been given the Browse right. If you do not see the container you want to audit, contact the network supervisor.PERFORMANCE="REQUIRED"Select "Auditor Container Login" from the "Available Audit Options" menu.A password prompt for the container appears.PERFORMANCE="REQUIRED"Type the auditing password for the container.You are now logged in to the container.RENDERAS="SECT2"ID="FM66616"Setting Up Your Work EnvironmentIDXID="w8742"BOOK="_idx" COLLECTION="nw41" TIDREF="i1330"IDXID="w8743"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"
IDXID="w8744"BOOK="_idx" COLLECTION="nw41" TIDREF="i344"You can set several options that determine how auditing will work in the volume or container you are auditing. You canMARK=BULLETSpecify the size of the Audit Data fileDetermine what action is taken if the Audit Data file reaches the maximum sizeSet a second-level password for additional securityRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 470 KB of memory available on the workstationBrowse right to the container, if you want to audit NetWare Directory Services eventsRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Log in to the volume or container.If you need help, se
e IDREF="FM78992""Logging In" on page 621.PERFORMANCE="REQUIRED"Select "Auditing Configuration" from the "Available Audit Options" menu.
PAGENUM=625 ID="BP579"PERFORMANCE="REQUIRED"Select "Audit Options Configuration" from the "Auditing Configuration" menu.The "Audi
t Configuration" screen appears.PERFORMANCE="REQUIRED"Select the applicable options and enter the settings you want for your work environment.The fields are explained in 
IDREF="FM65940"Table 8-1.PERFORMANCE="REQUIRED"To save the settings, press 
MOREINFO="NONE"<Esc> and choose "Yes" at the prompt
.
IDXID="w8745"BOOK="_idx" COLLECTION="nw41" TIDREF="i1330"LABEL="8-1" PGWIDE=1 TOCENTRY="1"ID="FM65940" Setup Options for the Auditing EnvironmentCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8746"BOOK="_idx" COLLECTION="nw41" TIDREF="i339"
Audit File Maximum SizeCOLNAME=2 ROTATE="0" MOREROWS="0"Enter the file size limit (in bytes) you want for the Audit Data file. Discuss this issue with the network supervisor before changing the default size because this affects available disk space for other network services.COLNAME=1 ROTATE="0" MOREROWS="0"Audit File Threshold SizeCOLNAME=2 ROTATE="0" MOREROWS="0"Enter the file size threshold (in bytes) beyond which AUDITCON sends warning messages to the server console and the system log file. The threshold setting should be 90% of the maximum size. For example, a maximum setting of 1,000,000 bytes should have a threshold setting of 900,000 bytes.COLNAME=1 ROTATE="0" MOREROWS="0"Automatic Audit File ArchivingCOLNAME=2 ROTATE="0" MOREROWS="0"Auto-archiving provides automated backup of your audit files. Automating the process provides protection of your audited information; it also requires large (duplicate) amounts of disk space, depending on the number of old audit files you decide to keep on the server. Use in conjunction with the next three options.Discuss this option with the network supervisor, since it affects available disk space on the server. Make sure the network supervisor has not set your storage limits too low.COLNAME=1 ROTATE="0" MOREROWS="0"Days Between Audit Archives (1-255)COLNAME=2 ROTATE="0" MOREROWS="0"Set the number of days to collect data before the file is automatically archived. You can select between 1-255 days; the default is 7 days. This option is valid only when the "Automatic Audit File Archiving" option is set to Yes.COLNAME=1 ROTATE="0" MOREROWS="0"Hour of Day to Archive (0-23)COLNAME=2 ROTATE="0" MOREROWS="0"Select the hour of the day for the auto-archive to take place. You can select any hour of the day, using a 24 hour clock (0-23). The default is 0 (midnight).This option is valid only after you have turned on the auto-archive option and selected the number of days between archives. Discuss this option with the network supervisor because it affects network traffic.COLNAME=1 ROTATE="0" MOREROWS="0"Number of Old Audit Files to Keep (1-15)COLNAME=2 ROTATE="0" MOREROWS="0"This option works in conjunction with the "Automatic Audit File Archiving" option and also with the error recovery feature of the "Archive Audit File" option. Either option closes the current audit files, archives copies of the current files, then opens new copies of the audit files. Those files that are archived are automatically stored on the server. When the maximum number of old audit files is reached, the oldest of the old files is deleted.Discuss this option with the network supervisor to determine possible disk storage limitations.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8747"BOOK="_idx" COLLECTION="nw41" TIDREF="i347"
Allow Concurrent Auditor LoginsCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Yes" if you want to allow more than one auditor to log in to a volume or container at the same time. All auditors use the same password.COLNAME=1 ROTATE="0" MOREROWS="0"Broadcast Error Messages to All UsersCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "No" if you want error messages sent only to the server console. We recommend that you do not broadcast these messages, because they increase network traffic and lock users' workstation screens until they press MOREINFO="NONE"<Ctrl>+<Enter>.COLNAME=1 ROTATE="0" MOREROWS="0"Force Dual-Level Audit PasswordsCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Yes" if you want to require two passwords. You are prompted to enter a password when you set this field to "Yes" for the first time. Whenever you change an auditing setting, you are prompted for a second password before the change is made.COLNAME=1 ROTATE="0" MOREROWS="0"Archive Audit FileCOLNAME=2 ROTATE="0" MOREROWS="0"This is one of three options available when the Audit Data file is full. The three options are: "Archive Audit File," "Dismount Volume," and "Disable Event Recording." Discuss these options with the network supervisor.Consider the "Number of Old Audit Files to Keep" option when selecting this option. When the Audit Data file reaches its maximum size, it is automatically closed, archived, and replaced with a new Audit Data file. No audit data is lost, and users continue to access the container or volume.Compare the "Archive Audit File" option with the "Dismount Volume" and "Disable Event Recording" options before deciding which to use.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8748"BOOK="_idx" COLLECTION="nw41" TIDREF="i344"
Dismount IDXID="w8749"BOOK="_idx" COLLECTION="nw41" TIDREF="i1143"
Volume (volume auditing only)COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8750"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"
Dismounts the audited volume if the Audit Data file reaches the maximum size limit or an unrecoverable write error occurs. Do not set this option to "Yes" without discussing it with the network supervisor, because dismounting a volume locks out all users. If the volume is dismounted, the network supervisor must remount it.NOTE: If the volume has been dismounted and the auditor has changed the assigned password, the network supervisor must have the auditor's password to remount the volume.See IDREF="FM13843""Remounting a Volume Dismounted by Auditing" on page 640 for more information. The default option is "Disable Event Recording."COLNAME=1 ROTATE="0" MOREROWS="0"Disable Audited Events (NetWare Directory Services auditing only)COLNAME=2 ROTATE="0" MOREROWS="0"When this option is set to "Yes," all audited events applicable to the container object are disabled when the Audit Data file reaches the maximum size limit or an unrecoverable write error occurs. Do not set this option to "Yes" without discussing it with the network supervisor, because disabling NDS events prevents users from performing any task that is being audited. For example, if logins are being audited, all attempts to log in to the container fail. The default option is "Disable Event Recording."COLNAME=1 ROTATE="0" MOREROWS="0"Disable Event RecordingCOLNAME=2 ROTATE="0" MOREROWS="0"This is the default of the three possible options. The program stops entering new records into the Audit Data file when the maximum size limit is reached or an unrecoverable write error occurs. You must reset the file to enable event recording again.Until you reenable event recording, no further auditing information is recorded. However, this option allows users to continue to access the volume and perform their work.When you reset the file, the information is saved in the old Audit Data file, and the auditing function resumes.COLNAME=1 ROTATE="0" MOREROWS="0"Minutes Between Warning MessagesCOLNAME=2 ROTATE="0" MOREROWS="0"Warnings are sent to the server console at this frequency if the Audit Data file is full and the "Disable Event Recording" option is set to "Yes."PAGENUM=628 ID="BP580"RENDERAS="SECT2"ID="FM34956"Selecting Items to AuditIDXID="w8751"BOOK="_idx" COLLECTION="nw41" TIDREF="i344"
This section explains how to set auditing to gather the information you want from a volume or container.After you have logged in and accessed the "Available Auditing Options" menu, you can move between volumes and containers to customize auditing procedures for all areas to which you have a valid password and the appropriate rights.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later.A minimum of 470 KB of memory available on the workstation.Have AUDITCON started and be logged in to the volume or container with the appropriate password. (See IDREF="FM78992""Logging In" on page 621 if you need help.)RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Select "Auditing Configuration" from the "Available Auditing Options" menu.PERFORMANCE="REQUIRED"Select the appropriate options from the "Auditing Configuration" menu.You might need to set auditing in more than one are
a to get the results you want. If you need help understanding the options and how they interact, read the following explanations, and then see 
IDREF="FM74177"Figure 8-5.
MARK=BULLETUser and File means you have limited the auditing of an event to a specific user and file. An auditing record will be entered only if a file in the audited directory is opened or written to by the audited user.User or File means you want to audit all occurrences of an event in a directory regardless of the user who performed the event, or you want to audit all occurrences of an event by a user regardless of the directory in which the event took place.Global means you are auditing for all instances of an event throughout the volume.PAGENUM=629 ID="BP581"See IDREF="FM21843""Auditing Examples" on page 641 to see how "User and File" and "User or File" options are used.LABEL="8-5" FLOAT="0"ID="FM74177"User, File, and Global OptionsFILEREF="n41su20a.tif"PAGENUM=630 ID="BP582"Options you can select for auditing volumes are described in IDREF="FM21683"Table 8-2. Options for auditing NetWare Directory Services events are described in IDREF="FM86400"Table 8-3.LABEL="8-2" PGWIDE=1 TOCENTRY="1"ID="FM21683" Auditing Options for VolumesCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="19*"NAMEST=2 NAMEEND=3 SPANNAME=SPAN2T3 ALIGN=LEFTVALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Audit by IDXID="w8752"BOOK="_idx" COLLECTION="nw41" TIDREF="i1463"
Event SPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Allows you to select the types of events to audit. If you select this option, AUDITCON prompts you to select from the event types explained below. Events are dependent on the files/directories and users audited. Unless you are auditing an event globally, you must also turn on auditing for the files/directories and users you want to audit for the event. For more information, see IDREF="FM21843""Auditing Examples" on page 641.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"File EventsCOLNAME=3 ROTATE="0" MOREROWS="0"Includes file or directory activities such as directory create or delete, and file create, open, close, read, write, and salvage requests. Events can be audited globally (all files/directories are audited for the event regardless of user), by user or file (the event is recorded only when it applies to an audited user or file), or user and file (the event is recorded when it applies to an audited user in an audited file or directory). For more information about how file events interact with users and files, see IDREF="FM21843""Auditing Examples" on page 641.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"QMS 
EventsCOLNAME=3 ROTATE="0" MOREROWS="0"Includes activities affecting queues, such as requests to create or destroy a print queue.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Server EventsCOLNAME=3 ROTATE="0" MOREROWS="0"Includes requests that affect a specific server, such as mounting a volume or bringing down a server. Server events are audited globally (all instances of the audited event are recorded).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"User EventsCOLNAME=3 ROTATE="0" MOREROWS="0"Includes activities such as logins and logouts, trustee assignment changes, and creating or deleting users.COLNAME=1 ROTATE="0" MOREROWS="0"Audit by File/DirectorySPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Gives you a list of all files and directories from which you can select those you want to audit. If you audit a file or directory, a record is added to the Audit Data file each time an audited event occurs for that file. If you set a parent directory to "Audited," it has the same effect as browsing up one level in the Directory tree and setting the actual directory name as audited. For more information, see IDREF="FM21843""Auditing Examples" on page 641.COLNAME=1 ROTATE="0" MOREROWS="0"Audit by UserSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Gives you a list of users from which you can select those you want to audit. If you turn on auditing for a user, a record is entered in the Audit Data file each time the user performs a user event that is audited.COLNAME=1 ROTATE="0" MOREROWS="0"Audit Options ConfigurationSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Allows you to configure the audit file parameters and specify what action will be taken if the Audit Data file reaches the specified size limit. For instructions on using this option to set up your working environment, see IDREF="FM66616""Setting Up Your Work Environment" on page 624.COLNAME=1 ROTATE="0" MOREROWS="0"Change Audit PasswordSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Allows you to change the auditor password for the volume.COLNAME=1 ROTATE="0" MOREROWS="0"Disable Volume AuditingSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Disables auditing for this volume. If you select "Yes," the network supervisor will have to enable auditing again if it is needed in the future.COLNAME=1 ROTATE="0" MOREROWS="0"Display Audit StatusSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Displays information about a volume's Audit Data and Audit History files.PAGENUM=631 ID="BP583"If you are auditing NetWare Directory Services events, use the options explained in IDREF="FM86400"Table 8-3 to set up auditing.LABEL="8-3" PGWIDE=1 TOCENTRY="1"ID="FM86400" Auditing Options for NetWare Directory ServicesCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Audit by DS EventCOLNAME=2 ROTATE="0" MOREROWS="0"Lists NetWare Directory Services events from which you can select those you want to audit. When you turn on auditing for an event, all occurrences of the event within the container are recorded.COLNAME=1 ROTATE="0" MOREROWS="0"Audit by UserCOLNAME=2 ROTATE="0" MOREROWS="0"Lists Directory tree objects. You can select the users to audit from the list by selecting the user's name and pressing MOREINFO="NONE"<F10>. If you turn on auditing for a user, a record is entered in the Audit Data file each time the user performs a NetWare Directory Services event that is audited.COLNAME=1 ROTATE="0" MOREROWS="0"Audit Options ConfigurationCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to configure the audit file parameters and specify what action is taken if the Audit Data file reaches the specified size limit. For instructions on using this option to set up your working environment, see IDREF="FM66616""Setting Up Your Work Environment" on page 624.COLNAME=1 ROTATE="0" MOREROWS="0"Change Audit PasswordCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to change the auditor password for the container.COLNAME=1 ROTATE="0" MOREROWS="0"Change Audit Password TwoCOLNAME=2 ROTATE="0" MOREROWS="0"Only shows if "Force dual-level password" has been set in the Auditing Configuration screen. Allows you to change the second-level password for the container.COLNAME=1 ROTATE="0" MOREROWS="0"Disable Container AuditingCOLNAME=2 ROTATE="0" MOREROWS="0"Disables auditing for this container. If you select "Yes", the network supervisor must reenable auditing if it is needed in the future.If "Force Dual Level Password" was set to "Yes," the second password is required to reenable auditing.COLNAME=1 ROTATE="0" MOREROWS="0"Display Audit StatusCOLNAME=2 ROTATE="0" MOREROWS="0"Displays general information about the Audit Data file for the container.PAGENUM=632 ID="BP584"RENDERAS="SECT1"ID="FM45557"Creating Audit ReportsIDXID="w8753"BOOK="_idx" COLLECTION="nw41" TIDREF="i341"IDXID="w8754"BOOK="_idx" COLLECTION="nw41" TIDREF="i339"
You 
have several options available for creating and viewing reports 
from the records in the audit files. When creating a report, you canMARK=BULLETSee all records in the 
Audit Data fileCreate filters to extract specific information from the Audit Data fileWhen viewing a report, you canMARK=BULLETSee a report on your screenSend the report to a file in your default directory or to a local driveRENDERAS="SECT2"ID="FM52979"Creating Report FiltersIDXID="w8755"BOOK="_idx" COLLECTION="nw41" TIDREF="i1463"IDXID="w8756"BOOK="_idx" COLLECTION="nw41" TIDREF="i341"AUDITCON lets you create filters so you can select information from the Audit Data file to create reports. If you view a report without applying a filter, the entire contents of the file are included.IDXID="w8757"BOOK="_idx" COLLECTION="nw41" TIDREF="i4204"
You can create as many filters as you want to screen information in the Audit Data file. Then, you can select and apply the filter you want when you generate a report.PAGENUM=633 ID="BP585"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later.A minimum of 470 KB of memory available on the workstation.Have AUDITCON running and be logged in to the volume or container with the appropriate password. (See IDREF="FM78992""Logging In" on page 621 if you need help.)RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Select "Auditing Reports" from "Available Auditing Options."PERFORMANCE="REQUIRED"Select 
"Edit Report Filters
" fro
m "Available Auditing Options
."The "Edit Filter" list appears, which includes all filters previously created.PERFORMANCE="REQUIRED"Select a filter from the list or press 
MOREINFO="NONE"<Insert> to create a new filter.The "Edit Report Filter" menu appears.PERFORMANCE="REQUIRED"Select options you want to include in the filter from the "Edit Report Filter" menu.The options are explained i
n IDREF="FM90894"Table 8-4. For help with any of the options, press 
MOREINFO="NONE"<F1>.If a filter contains conflicts between "include" and "exclude" options, the "exclude" always takes priority.LABEL="8-4" PGWIDE=1 TOCENTRY="1"ID="FM90894" Options for Creating Report FiltersCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="19*"NAMEST=2 NAMEEND=3 SPANNAME=SPAN2T3 ALIGN=LEFTVALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Report by Date/TimeSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Allows you to enter a time period for which you want to create a report. All recorded events that fall within the dates and times entered appear in the report.COLNAME=1 ROTATE="0" MOREROWS="0"Report By Event SPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Allows you to select the types of audited events to include in the report. If you select this option, AUDITCON prompts you to select from the events that have been audited. Events are dependent on the files/directories and users included in or excluded from the report. Event types you can select are:MARK=BULLETFile EventsQMS EventsServer EventsUser EventsCOLNAME=1 ROTATE="0" MOREROWS="0"Report Exclude Paths/FilesSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Allows you to specify files or directories you do not want to include in the report. Press MOREINFO="NONE"<Insert> and enter the name of the file or directory you want to exclude. All other audited files and directories are included.COLNAME=1 ROTATE="0" MOREROWS="0"Report Exclude UsersSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Allows you to specify the name of an audited user that you do not want to include in the report. Press MOREINFO="NONE"<Insert> and enter the name of the user you want to exclude, or press MOREINFO="NONE"<Insert> again to select from a list. All other users are included.COLNAME=1 ROTATE="0" MOREROWS="0"Report Include Paths/FilesSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Allows you to specify an audited directory path or file that you want to include in the report. Press MOREINFO="NONE"<Insert> and enter the directory path (or the filename, if the file is in the default directory) that you want to include, or press MOREINFO="NONE"<Insert> again to select from a list. The default is that all audited directories and files are included. This is indicated by the asterisk (*). All other paths and files are excluded.COLNAME=1 ROTATE="0" MOREROWS="0"Report Include UsersSPANNAME=SPAN2T3 ROTATE="0" MOREROWS="0"Allows you to specify the name of an audited user that you want to include in the report. The default is that all users are included. This is indicated by the asterisk (*). If you don't want to include all users, press MOREINFO="NONE"<Insert> and enter the name of the user you want to include; all other users are excluded.PAGENUM=634 ID="BP586"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until you get back to the "Edit Report Filter" menu.
PAGENUM=635 ID="BP587"PERFORMANCE="REQUIRED"At the "Save Filter Changes" prompt, complete one of the following steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"To save the change, select "Yes" and press 
MOREINFO="NONE"<Enter>.If you have created a new filter, backspace to delete "_no_filter_" from the list and enter a name (maximum eight characters) for the filter.PERFORMANCE="REQUIRED"To exit the filter without saving the changes, select "No" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"MOREINFO="NONE"To continue editing the filter, press 
MOREINFO="NONE"<Esc>.RENDERAS="SECT2"Sending Reports to a FileIDXID="w8758"BOOK="_idx" COLLECTION="nw41" TIDREF="i339"IDXID="w8759"BOOK="_idx" COLLECTION="nw41" TIDREF="i341"AUDITCON lets you send auditing information to a directory on the network.You can send the information to your default network directory, a directory where you have [RWCEMF] rights, or a local or floppy drive at your workstation.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later.A minimum of 470 KB of memory available on the workstation.Have AUDITCON running and be logged in to the volume or container with the appropriate password. (See IDREF="FM78992""Logging In" on page 621 if you need help.)RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Select" Auditing Reports" from the "Available Auditing Options" menu.PERFORMANCE="REQUIRED"Select "Report Audit File" fro
m "Available Auditing Options
."PAGENUM=636 ID="BP588"PERFORMANCE="REQUIRED"Specify where you want the file to be sent by completing one of the followin
g:If you send reports to a network directory, a user with Supervisor rights in the file system can see the file. If you want to secure your reports, you should send them to a local drive or a floppy drive on your workstation.MARK=BULLETPress MOREINFO="NONE"<Enter> to copy the report to a file in your default directory.The default filename is AUDITDAT.TXT.Enter the directory path and filename where you want the file to be sent, and then press MOREINFO="NONE"<Enter>.Specify an existing directory path and filename. (The program will not create a default file for you.)PERFORMANCE="REQUIRED"Select a filter from the "Select Filter List" and press 
MOREINFO="NONE"<Enter>. To create a report without a filter, select "no_filter."PERFORMANCE="REQUIRED"(Optional) Create or edit a filter. To edit a filter in the list, press 
MOREINFO="NONE"<F10>. To create a filter, press 
MOREINFO="NONE"<Insert>.The list item "_no_filter" cannot be edited.For help creating and editing filters, se
e IDREF="FM52979""Creating Report Filters" on page 632 or press 
MOREINFO="NONE"<F1> for help.PERFORMANCE="REQUIRED"Specify how you want the filter to be used by completing one of the following steps:
MARK=BULLETTo save the filter changes, select "Save Filter Changes."If it is a new filter, enter a name (maximum eight characters).To use the filter once without permanently changing the filter, select "Use Filter without Saving Changes."The report is generated with the new filter settings, and then the filter reverts to its original settings. New filters are not saved.To discard filter changes, select "Discard Filter Changes".Edited filters revert to the original settings. New filters are deleted.The filtered report is sent to the directory and file you specified. Reports are in DOS text file format. The report file can be edited or printed using the same methods you use for other DOS text files.PAGENUM=637 ID="BP589"RENDERAS="SECT2"Viewing a Report on the ScreenIDXID="w8760"BOOK="_idx" COLLECTION="nw41" TIDREF="i341"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or later.A minimum of 470 KB of memory available on the workstation.Have AUDITCON running and be logged in to the volume or container with the appropriate password. (See IDREF="FM78992""Logging In" on page 621 if you need help.)RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Select "View Audit File" from the "Auditing Reports Menu."PERFORMANCE="REQUIRED"Select a filter from the "Select Filter List" and press 
MOREINFO="NONE"<Enter>. To see a report without a filter, select "no_filter" from the list.PERFORMANCE="REQUIRED"(Optional) Create or edit a filter. To edit a filter in the list, press 
MOREINFO="NONE"<F10>. To create a filter, press 
MOREINFO="NONE"<Insert>.The list item 
"_no_filter
" cannot be edited.For help creating and editing filters, se
e IDREF="FM52979""Creating Report Filters" on page 632, or press 
MOREINFO="NONE"<F1> for online help.PERFORMANCE="REQUIRED"Specify how you want the filter to be used by completing one of the followin
g:MARK=BULLETTo save new changes to the filter, select "Save Filter Changes."If you created a new filter, enter a name (maximum eight characters).To use the filter for this report only, select "Use Filter Without Saving Changes."The report is generated with the new filter settings, and then the filter reverts to its original settings. New filters are not saved.To discard filter changes, select "Discard Filter Changes."Edited filters revert to the original settings. New filters are deleted.PERFORMANCE="REQUIRED"Press the arrow keys to scroll through the report. To exit, press 
MOREINFO="NONE"<Esc> and answer "Yes" at the "Exit View"' prompt.
PAGENUM=638 ID="BP590"RENDERAS="SECT2"ID="FM43852"Maintaining Audit FilesRENDERAS="SECT3"Understanding the Audit FilesAUDITCON automatically creates audit files when it is enabled. Each volume or container using AUDITCON will have its own audit files.RENDERAS="SECT4"The 
Audit IDXID="w8761"BOOK="_idx" COLLECTION="nw41" TIDREF="i339"
Data FileThis file keeps records of all audited transactions. The auditing configuration you set determines the type of records entered into the data file.This file operates like a system log or error file. Records are automatically entered into the file whenever an audited event occurs.When you audit container objects for NetWare Directory Services events, the audit history information is combined with audit data into this file.RENDERAS="SECT4"The Audit IDXID="w8762"BOOK="_idx" COLLECTION="nw41" TIDREF="i340"
History 
FileThis file keeps a record of the auditor's activities in a volume, such as auditing configuration changes and auditor logins and logouts.In NetWare Directory Services, the auditor's activities are recorded in the Audit data file. There is no separate file for this information.You can, however, use the menu options such as "View Audit History" to see auditor records just as you would if you were auditing a volume.When you reset an audit file, existing records are moved to an Old Audit Data or Old Audit History file. The original audit file continues to function as it did before.PAGENUM=639 ID="BP591"The maintenance options for the audit files are explained in the following table.LABEL="8-5" PGWIDE=1 TOCENTRY="1" Audit Files Maintenance OptionsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8763"BOOK="_idx" COLLECTION="nw41" TIDREF="i339"
Close Old Audit FileCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to close an Old Audit Data file. All Audit Data files are kept open by the system for security reasons. To copy or delete an old audit file, first close it, then copy or delete it.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8764"BOOK="_idx" COLLECTION="nw41" TIDREF="i339"
Copy Old Audit FileCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to copy an Old Audit Data file to a file or directory as a compressed, nonreadable file. You must first close the old audit file. You are prompted for the name of the destination file. The default name is AUDITOLD.DAT.COLNAME=1 ROTATE="0" MOREROWS="0"Delete Old Audit FileCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to delete the Old Audit Data file. You must first close the old audit file.COLNAME=1 ROTATE="0" MOREROWS="0"Display Audit StatusCOLNAME=2 ROTATE="0" MOREROWS="0"Displays basic information about the audit files, such as file size and file size limitsCOLNAME=1 ROTATE="0" MOREROWS="0"Reset Audit Data FileCOLNAME=2 ROTATE="0" MOREROWS="0"Resets the Audit Data file and moves the data in the file to the Old Audit Data file. Old audit files are limited to 15 at a time. When the maximum number of old audit files is reached, the oldest old file is deleted and number 14 becomes number 15, and so forth. The Audit Data file continues to collect records based on the configuration settings, as it did before it was reset.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8765"BOOK="_idx" COLLECTION="nw41" TIDREF="i339"
Reset Audit History FileCOLNAME=2 ROTATE="0" MOREROWS="0"For auditing volumes only. Resets the Audit History file and moves the data in the file to the Old Audit History file. Old audit files are limited to 15 at a time. When the maximum number of old audit files is reached, the oldest old file is deleted and number 14 becomes number 15, and so forth. The Audit History file continues to collect records, as it did before it was reset.RENDERAS="SECT3"Resetting the Audit Data FileRENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA workstation running DOS 3.30 or laterA minimum of 470 KB of memory available on the workstationHave AUDITCON running and be logged in to the volume or container with the appropriate password. (See IDREF="FM78992""Logging In" on page 621 if you need help.)PAGENUM=640 ID="BP592"RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Select "Audit Files Maintenance" from the "Available Auditing Options" menu.PERFORMANCE="REQUIRED"Select "Reset Audit Data File" from the "Audit Files Maintenance" menu.A warning message appears on the screen to notify you that the current contents of the file will be moved to the Ol
d Audi
t Data file. If you already have data in an old file, it will be moved to the next old audit file.PERFORMANCE="REQUIRED"Select 
"Yes
" to reset the file.The Audit Data file clears existing entries and then continues to record new entries based on your auditing configuration.The following fields on the 
"Audi
t Status
" screen are reset to zero:
MARK=BULLETAudit file sizeAudit record countRENDERAS="SECT3"ID="FM13843"Remounting a Volume Dismounted by AuditingIDXID="w8766"BOOK="_idx" COLLECTION="nw41" TIDREF="i344"
IDXID="w8767"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"IDXID="w8768"BOOK="_idx" COLLECTION="nw41" TIDREF="i2521"If a volume is dismounted because the Audit Data file reached its maximum size limit and the "Dismount Volume" option is set, the network supervisor must remount the volume and enable auditing again.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXAccess to the server console, or a remote console session with the server whose volume was dismounted.The auditing password to the volume.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the server console, mount the volume by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"MOUNT volume_name MOREINFO="NONE"<Enter>To continue, you must enter the audi
ting password for that volume.
PAGENUM=641 ID="BP593"PERFORMANCE="REQUIRED"At the console, enter the current auditing password for the volume.This is the password the auditor assigned to the volume.PERFORMANCE="REQUIRED"Reenable auditing.Follow the instructions i
n IDREF="FM12641""Enabling Auditing for a Volume" on page 614.The auditor then needs to log in and change the password again by following the instructions i
n IDREF="FM26418""Setting Passwords" on page 618.RENDERAS="SECT1"ID="FM21843"Auditing ExamplesIDXID="w8769"BOOK="_idx" COLLECTION="nw41" TIDREF="i344"
Examples in this section are taken from the following scenario. You may need to refer to the illustrations and explanations as you work through the examples.The examples assume that you have logged in to a volume as the auditor and are at the "Available Audit Options" menu.Suppose you are auditing a company called XYZ Sales. The records you will audit are on volume SYS:, which is set up as shown in IDREF="FM49846"Figure 8-6:LABEL="8-6" FLOAT="0"ID="FM49846"File System for XYZ Sales (Example)FILEREF="n40su09a.tif"You have four users: Thomas, who is the network supervisor, Ann, Fred, and Sue.PAGENUM=642 ID="BP594"SYS:RECORDS is used by the network supervisor to keep confidential employee records.SYS:ACCOUNTS has subdirectories containing information about each company that does business with XYZ Sales. Ann, Fred, and Sue maintain these files.RENDERAS="SECT2"Examples of Selecting Items to AuditRENDERAS="SECT3"Auditing Events by User and FileIDXID="w8770"BOOK="_idx" COLLECTION="nw41" TIDREF="i4204"Suppose you have a directory with sensitive and critical information in it. Even thought you have given Write and Erase rights to Ann, Fred, and Sue, you want to audit all their file open and file write requests in the SYS:ACCOUNTS directory.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Select "Auditing Configuration" from the "Available Audit Options" menu.PERFORMANCE="REQUIRED"Select 
"Audit b
y Event.
"PERFORMANCE="REQUIRED"Select the file events you want to audit.Since you want to audit file events in a particular directory by certain users, select "File ope
n---user and file
" and "File wri
te---user and file" options.For this example, you would select the events shown i
n IDREF="FM43909"Figure 8-7:PAGENUM=643 ID="BP595"LABEL="8-7" FLOAT="0"ID="FM43909"Auditing File Events (Example)FILEREF="n41su06a.tif"User and File means you have limited the auditing of an event to a specific user and file. An auditing record will be entered only if a file in the audited directory is opened or written to by the audited user.User or File means you want to audit all occurrences of an event in a directory regardless of the user who performed the event, or you want to audit all occurrences of an event by a user regardless of the directory in which the event took place.ID="FM19808"Global means that you are auditing for all instances of an event throughout the volume.Examples of these options and how they affect the type of information you gather are shown in more detail i
n IDREF="FM78485"Figure 8-8.PAGENUM=644 ID="BP596"LABEL="8-8" FLOAT="0"ID="FM78485"Auditing File/Directory Options (Example)FILEREF="n41su03a.tif"PERFORMANCE="REQUIRED"Select the subdirectories you want to audit.For this example, you want to audit the SYS:ACCOUNTS directory
. IDREF="FM77799"Figure 8-9 shows how to select this directory.When you audit a directory, existing subdirectories do not inherit the Audited attribute. Subdirectories created after the directory is audited do inherit the attribute.PAGENUM=645 ID="BP597"LABEL="8-9" FLOAT="0"ID="FM77799"Auditing Directories (Example)FILEREF="n41su07a.tif"Since these subdirectories were already created, select each of them for auditing.To audit subdirectories that might be created in the future under SYS:ACCOUNTS, also select the ACCOUNTS directory (parent) as audited. Any subdirectories created after that time would automatically be audited.PERFORMANCE="REQUIRED"Select the users you want to audit.For this example, you want to audit the three users who maintain records about the companies who do business with XYZ Sales
. IDREF="FM99778"Figure 8-10 shows how t
o select these users.LABEL="8-10" FLOAT="0"ID="FM99778"Auditing Users (Example)FILEREF="n41su08a.tif"PAGENUM=646 ID="BP598"RENDERAS="SECT3"Auditing All Activities in a DirectoryIDXID="w8771"BOOK="_idx" COLLECTION="nw41" TIDREF="i4204"Suppose you want to audit the RECORDS directory and all activities that occur in that directory.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Select "Auditing Configuration" from the "Available Audit Options" window.PERFORMANCE="REQUIRED"Turn on auditing for file/directory events.Audit all of the events that have a User or File option as shown i
n IDREF="FM75159"Figure 8-11.LABEL="8-11" FLOAT="0"ID="FM75159"Auditing All Events in a Directory (Example)FILEREF="n41su22a.tif"Since the network supervisor (Thomas) is the only user who has rights to the RECORDS directory, you coul
d select all events by user and file, and then audit Thomas.However, to make sure you get a complete record of all activities in the directory, you ca
n select all events to be audited by user or file. Then records would be entered for the audited events regardless of the user.
PAGENUM=647 ID="BP599"PERFORMANCE="REQUIRED"Turn on auditing for the directory.On the "Audit by File/Directory" screen, go to the SYS:RECORDS directory (SYS:RECORDS appears at the top of the screen).In this directory, SYS:RECORDS is the parent, meaning all of the files in the list belong to it. Turn on auditing for SYS:RECORDS by auditing (parent) as show
n in IDREF="FM70888"Figure 8-12.LABEL="8-12" FLOAT="0"ID="FM70888"Auditing a Parent Directory (Example)FILEREF="n41su24a.tif"RENDERAS="SECT2"Examples of Creating a Report FilterIDXID="w8772"BOOK="_idx" COLLECTION="nw41" TIDREF="i341"RENDERAS="SECT3"Sorting Information about Activity in a SubdirectorySuppose you want to see the activities of the three users who use the Acme Products directory. You could create a report filter to extract this information from the Audit Data file.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Select "Auditing Reports" from the "Available Audit Options" menu.PERFORMANCE="REQUIRED"Select "Edit Report Filters" from the "Auditing Reports" menu.A list of filters appears. When you create and name new filters, they will be added to this list.The "
_no_filter" item in the list is the one you select when you want to see the entire contents of the Audit Data file.
PAGENUM=648 ID="BP600"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert> to create a new filter.Since the default for filters is to include all audited users, select "Edit Report Filters" and then press 
MOREINFO="NONE"<Insert> from the filter list to create a new filter. (The "
_no_filter" option means you want your report to include the entire contents of the Audit Data file.)PERFORMANCE="REQUIRED"Select the appropriate users and files.Since you want to see the activities of the three users, you only need to exclude the network supervisor (Thomas) from the report. Selecting "Report Exclude Users" and pressing 
MOREINFO="NONE"<Insert> twice brings up a list of users, where you can select Thomas to be excluded. Se
e IDREF="FM81947"Figure 8-13.LABEL="8-13" FLOAT="0"ID="FM81947"Creating a Report Filter (Example)FILEREF="n40su25a.tif"Since you want to see the users' activities in only the Acme Products files, include the ACME subdirectory, which excludes all other directories by default.Select "Report Include Paths/Files," and then select ACME from the list that appears. Se
e IDREF="FM11979"Figure 8-14.PAGENUM=649 ID="BP601"LABEL="8-14" FLOAT="0"ID="FM11979"Including a Directory in a Report (Example)FILEREF="n40su26a.tif"PERFORMANCE="REQUIRED"Select the file event
sInclude the file events you audited in the report filter. Se
e IDREF="FM68810"Figure 8-15.LABEL="8-15" FLOAT="0"ID="FM68810"Including File Events in a Report (Example)FILEREF="n41su27a.tif"PERFORMANCE="REQUIRED"Save the Filter.Now that you have selected the items you want for the report, press 
MOREINFO="NONE"<Esc> until you get to the "Save Filter Changes?" prompt. Save your changes and name the filter by replacing "_no_filter_" with the filter name.The filter is added to the list for you to use whenever you want to create a report with this information. For this example, we've called the filter "ACMEUSER", as shown i
n IDREF="FM21815"Figure 8-16.PAGENUM=650 ID="BP602"RENDERAS="SECT3"Sorting Information about a User's ActivityIDXID="w8773"BOOK="_idx" COLLECTION="nw41" TIDREF="i4204"If you want to extract information about the network supervisor's audited activities, you can create another filter for this purpose.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Select "Edit Report Filters" from the "Auditing Reports" menu.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert> to create a filter.PERFORMANCE="REQUIRED"Include the appropriate items.When you select "Report Include Users" and press 
MOREINFO="NONE"<Insert>, a l
ist of users appears. Turn on auditing for user Thomas, the network supervisor, by selecting his name from the list. (Make sure the asterisk is deleted from the beginning of his name.) All of the other users are automatically excluded.The following figure illustrates this procedure.LABEL="8-16" FLOAT="0"ID="FM21815"Including Users in a Report (Example)FILEREF="n40su28a.tif"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>.Continue pressing 
MOREINFO="NONE"<Esc> until you get to the "Save Filter Changes?" prompt. Save your changes and name the filter by replacing "_no_filter_" with the filter name.The new filter is added to your list. For this example, we've called the filter "SUPERVIS" as shown i
n IDREF="FM80863"Figure 8-17.PAGENUM=651 ID="BP603"RENDERAS="SECT2"Example of Using a Filter without Saving the ChangesIDXID="w8774"BOOK="_idx" COLLECTION="nw41" TIDREF="i341"RENDERAS="SECT3"Using an Existing Filter to Sort Information by Date and TimeSuppose you want to see Thomas's activities for the past two days, but you don't want to permanently alter the filter you created to sort the network supervisor's activity.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Select "View Audit File" from the "Auditing Reports" menu.PERFORMANCE="REQUIRED"Select the filter you want to use and press 
MOREINFO="NONE"<F10>.In this case, select the filter you created to sort network supervisor Thomas's activities in the previous example. (See the example in the following figure.)LABEL="8-17" FLOAT="0"ID="FM80863"Using an Existing Report Filter (Example)FILEREF="n40su29a.tif"PERFORMANCE="REQUIRED"Select "Report by Date/Time" and press 
MOREINFO="NONE"<Enter>; then press 
MOREINFO="NONE"<Insert>.Enter the beginning and ending days and times for the period you want to include in the report, as shown i
n IDREF="FM16236"Figure 8-18.PAGENUM=652 ID="BP604"LABEL="8-18" FLOAT="0"IDXID="w8775"BOOK="_idx" COLLECTION="nw41" TIDREF="i4204"ID="FM16236"Sorting Data by Date and Time (Example)FILEREF="n40su30a.tif"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to leave the time settings, and then back out to the "Save Filte
r Menu" by pressing 
MOREINFO="NONE"<Esc> twice.The 
"Save Filte
r Menu
" appears. Since you want to use the modified filter fo
r this report only, select the option as shown i
n IDREF="FM92095"Figure 8-19.LABEL="8-19" FLOAT="0"ID="FM92095"Using a Filter without Saving Changes (Example)FILEREF="n40su31a.tif"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter>.Your report appears on the screen, showing only the supervisor's activity for the days you specified.LABEL="9"PAGENUM=653 ID="BP605"ID="FM49062"Backing Up and Restoring DataRENDERAS="SECT1"ID="FM68513"What SBACKUP DoesSBACKUP is a NetWare® Loadable ModuleTM (NLM) that allows you to back up and restore data for NetWare® 2, 3, and 4 (including NetWare Directory ServicesTM, bindery, and volume restrictions), and OS/2 network servers, as well as workstations or other services you select.SBACKUP copies data that you select, stores the data on the storage media of your choice (see IDREF="FM48670""Supported Storage Devices and Drivers" on page 658), and retrieves the data later. SBACKUP also allows you toMARK=BULLETChoose from four different backup types: full, incremental, differential, or custom. (See IDREF="FM14384""Backup Types" on page 671 for definitions.)Perform backups immediately or schedule them for a later time.Back up a server or workstation even when other users are working on it. (However, files in use are not backed up.)Back up and restore multiple name space formats defined on a volume (including DOS, FTAM, Macintosh, NFS, and OS/2 files), retaining file attributes associated with each format.Restore all or part of your data to either its original location or to an alternate location in the directory structure.PAGENUM=654 ID="BP606"RENDERAS="SECT2"ID="FM79417"Backup and Restore ConceptsBefore using SBACKUP, you should be familiar with the following concepts (see Concepts):TYPE="VERT""BOOK="cncptenu" COLLECTION="nw41"Backup""
BOOK="cncptenu" COLLECTION="nw41"Data set""
BOOK="cncptenu" COLLECTION="nw41"Host""
BOOK="cncptenu" COLLECTION="nw41"Major resource""
BOOK="cncptenu" COLLECTION="nw41"Media Manager""
BOOK="cncptenu" COLLECTION="nw41"Minor resource""
BOOK="cncptenu" COLLECTION="nw41"Modify bit""
BOOK="cncptenu" COLLECTION="nw41"Restore""
BOOK="cncptenu" COLLECTION="nw41"Storage Management Services" "
BOOK="cncptenu" COLLECTION="nw41"Target""
BOOK="cncptenu" COLLECTION="nw41"Target Service Agent""
BOOK="cncptenu" COLLECTION="nw41"Target Service Agent resources" RENDERAS="SECT2"ID="FM57695"How SBACKUP Presents ChoicesBecause every network environment is different, SBACKUP offers many different ways of performing a backup or restore. In some cases, SBACKUP streamlines the process for you.You can have one or more targets, Target Service Agents, storage devices, or storage media. If there is only one of any item, or if a choice you previously made precludes other choices that exist under other circumstances, SBACKUP selects the default and then continues without asking you to make a specific selection.IDREF="FM81074"Figure 9-1 shows an example of this kind of operation.PAGENUM=655 ID="BP607"LABEL="9-1" FLOAT="0"ID="FM81074"SBACKUP Decision ProcessFILEREF="n41sb17a.tif"PAGENUM=656 ID="BP608"RENDERAS="SECT1"ID="FM63064"Rules for Using SBACKUPThe next two sections, IDREF="FM60644""Using SBACKUP" and IDREF="FM87672""Using Target Service Agents," list rules that will help you avoid problems and confusion when using SBACKUP and its 
Target Service Agents.RENDERAS="SECT2"ID="FM60644"Using SBACKUPMARK=BULLETUse the latest version of NLM programs: Use the NetWare 4.1 version to ensure that SBACKUP loads and works properly.For example, to back up a NetWare 3.11 target server, use the TSA311.NLM and SMDR.NLM files that shipped with NetWare 4.1.Log in as ADMIN: When connecting to a target (server, workstation, or database), log in as ADMIN, or as a network-supervisor equivalent for that target.For security reasons, many SBACKUP options are limited to the network supervisor. You will have limited success performing backups and restores if you log in without supervisor rights.Set common context: Set targets to the same context as the host server to avoid having to specify the context during a backup or restore session.Reserve disk space for temporary files: Make sure you have disk space available (1 to 2 MB) on the target server's volume SYS: to accommodate temporary files.SBACKUP creates temporary files on the target server during backup. If you have linked IDXID="w8776"BOOK="_idx" COLLECTION="nw41" TIDREF="i4656"
UNIX files or files with extended attributes, the temporary files might be larger than a megabyte.Avoid restoring Netware Directory Services from media when possible: We recommend using replicas instead. (See IDREF="FM57530"Chapter 5, "Managing the NetWare Directory Tree.")Don't mount or dismount volumes during a session: The data might be corrupted or an abend might occur at the host server.Use the correct name space and name space formats: If you don't use the correct name space and name space formats when entering paths and filenames, files can't be restored.PAGENUM=657 ID="BP609"You can only restore to a new location in the name space that is supported by the drive you are restoring to.On an HPFS drive you can only rename in the OS/2 name space, and on a File Allocation Table (FAT) file system you can only rename in the DOS name space. However, SBACKUP displays both in the log file even though only one is valid.Name spaces:IDXID="w8777"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
 DOS, IDXID="w8778"BOOK="_idx" COLLECTION="nw41" TIDREF="i1579"
FTAM, IDXID="w8779"BOOK="_idx" COLLECTION="nw41" TIDREF="i2263"
Macintosh, IDXID="w8780"BOOK="_idx" COLLECTION="nw41" TIDREF="i2919"
NFS, and IDXID="w8781"BOOK="_idx" COLLECTION="nw41" TIDREF="i3134"
OS/2.IDXID="w8782"BOOK="_idx" COLLECTION="nw41" TIDREF="i2585"
Name space formats:MARK=BULLETFor Macintosh, use Volume::directory:directory:filenameFor all others, use Volume:/directory/directory/filenameExit SBACKUP before unloading drivers: If you unload a manually loaded driver (such as AHA1740.DSK or ASPITRAN.DSK) before exiting SBACKUP, you might cause the host server to abend.Use original case for non-DOS names: Non-DOS pathnames and filenames are case-sensitive. NetWare recognizes DOS pathnames and filenames in uppercase, lowercase, or mixed case. If you're not sure of the original case, refer to your log file.RENDERAS="SECT2"ID="FM87672"Using Target Service AgentsThis section highlights a few things you should make note of before using Target Service Agents to back up or restore workstations or databases.When you are backing up or restoring a workstation or database, some of the screens you see will vary from those displayed in this document, which are examples of NetWare 4.1 target server screens; however, the same general principles apply.MARK=BULLETIDXID="w8783"BOOK="_idx" COLLECTION="nw41" TIDREF="i4426"Load Target Service Agents automatically: You can load these files automatically each time a workstation is booted by placing the load commands in the workstation's AUTOEXEC.BAT file (for DOS workstations) or the Startup file (for OS/2 workstations).IDXID="w8784"BOOK="_idx" COLLECTION="nw41" TIDREF="i4426"Restore NetWare Directory Services (NDS) from replicas: The only absolute way to ensure that NDSTM can be fully restored is through partition replication, with one master partition and associated replicas on multiple servers.PAGENUM=658 ID="BP610"For more information on partitions and replicas, see IDREF="FM57530"Chapter 5, "Managing the NetWare Directory Tree."IDXID="w8785"BOOK="_idx" COLLECTION="nw41" TIDREF="i4426"Avoid using SBACKUP to restore NDS: Restoration from SBACKUP should be used only in the event of a catastrophic data loss, where all replicas have become corrupted.If you must restore NDS from SBACKUP, load the NDS Target Service Agent (TSANDS) on the same server as SBACKUP (the host server).RENDERAS="SECT1"Installing and Setting Up SBACKUPThis section explains storage device and driver support as well as memory requirements you should be aware of before loading SBACKUP files on a server or workstation.RENDERAS="SECT2"ID="FM48670"Supported Storage Devices and DriversIDXID="w8786"BOOK="_idx" COLLECTION="nw41" TIDREF="i396"The NetWare 4.1 version of SBACKUP supports 0.25-inch, 4mm, and 8mm storage devices. However, we recommend pretesting any tape drive device.To ensure reliable operations, pretest all media storage devices that are not Novell® certified with the appropriate NetWare device driver and SBACKUP backup/restore utility.If you are using 4mm tape, use only DDS certified, computer grade tapes.The following driver files are included with NetWare 4.1. Use the files recommended by your hardware manufacturer.MARK=BULLETTAPEDAI.DSK: This is the Novell generic tape device driver file. It works with most ASPI-compatible SCSI controllers, but contains specific driver information for the tape drives listed in the following table. These drives may or may not be Novell certified, but they are more likely to offer correct functionality than those not listed.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ManufacturerCOLNAME=2 ROTATE="0" MOREROWS="0"ProductVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ArchiveCOLNAME=2 ROTATE="0" MOREROWS="0"PythonCOLNAME=1 ROTATE="0" MOREROWS="0"CipherCOLNAME=2 ROTATE="0" MOREROWS="0"T826 (0.5 inch, 2.6 GB), T860 (0.5 inch, 6 GB)COLNAME=1 ROTATE="0" MOREROWS="0"ExabyteCOLNAME=2 ROTATE="0" MOREROWS="0"EXB-8500 (This is the only Exabyte tape drive that works with TAPEDAI.DSK.)COLNAME=1 ROTATE="0" MOREROWS="0"Hewlett-PackardCOLNAME=2 ROTATE="0" MOREROWS="0"HP35450A, HP35470A, HP35480ACOLNAME=1 ROTATE="0" MOREROWS="0"TandbergCOLNAME=2 ROTATE="0" MOREROWS="0"TDC 3800, TDC 4100, TDC 4200COLNAME=1 ROTATE="0" MOREROWS="0"WANGDATCOLNAME=2 ROTATE="0" MOREROWS="0"1300, 3200COLNAME=1 ROTATE="0" MOREROWS="0"WANGTEKCOLNAME=2 ROTATE="0" MOREROWS="0"5525ES, 6130, WANGTEK_6130_HSPAGENUM=659 ID="BP611"The generic driver included in TAPEDAI.DSK may not provide the optimal performance from the tape device. Follow the tape driver manufacturer's instructions for specific driver information.MNS16S.DSK, MNS8MM.DSK, and MNSDAT.DSK: These files work with Mountain Network Solutions, Inc. SCSI controllers and tape systems, when they are used with SBACKUP.NLM.PS2SCSI.DSK: This file works with IBM 2.2GB, 8mm tape devices that use PS2 SCSI controller boards, when they are used with SBACKUP.NLM.AHA1540.DSK, AHA1640.DSK, AHA1740.DSK, and ASPITRAN.DSK: These files work with Adaptec 1540, 1640, and 1740 controllers, when they are used with SBACKUP.NLM.For more information on devices and driversMARK=BULLETContact your Novell Authorized ResellerCLM representative or consultant, or call 1-800-NETWARE for the list of currently supported devices.Download, from NetWireSM forum, a list of currently supported devices. (For more information about NetWire, see "BOOK="cncptenu" COLLECTION="nw41"NetWire" in Concepts or contact your Novell Authorized Reseller.)Call the Novell LabsTM facility at 1-801-429-5544 for a list of tape drives that are certified as "Yes, Tested and Approved" with NetWare 4.1.PAGENUM=660 ID="BP612"RENDERAS="SECT2"IDXID="w8787"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
MemoryTo run SBACKUP, the host server requires a minimum of 3 MB of memory in addition to the memory required to run NetWare.If an additional 3 MB of memory is not available, you might be able to set the storage buffers lower than the default and still run SBACKUP.For memory and buffer settings, see IDREF="FM72288""Enhancing Host Server Performance" on page 753.RENDERAS="SECT1"ID="FM85148"Loading Files Needed to Run SBACKUPIDXID="w8788"BOOK="_idx" COLLECTION="nw41" TIDREF="i2159"Use the appropriate procedure in the following table to load device and controller drivers and to load files on your target. When file loading is completed, the SBACKUP "Main Menu" is displayed on your host server's console.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"To back upCOLNAME=2 ROTATE="0" MOREROWS="0"See these proceduresVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ServersCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM90669""Loading Procedures for Drivers" on page 661 and IDREF="FM18303""Loading Procedures for Servers" on page 662COLNAME=1 ROTATE="0" MOREROWS="0"WorkstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM90669""Loading Procedures for Drivers" on page 661 and IDREF="FM57809""Loading Procedures for Workstations" on page 663COLNAME=1 ROTATE="0" MOREROWS="0"NetWare Directory ServicesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM90669""Loading Procedures for Drivers" on page 661 and IDREF="FM55742""Loading Procedures for NetWare Directory Services" on page 667COLNAME=1 ROTATE="0" MOREROWS="0"SFT IIICOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM67643""Loading Procedures for SFT III Users" on page 668A summary of all load commands can be found in IDREF="FM71287"Table 9-2, but the table should be used only after you are familiar with the procedure for each target.PAGENUM=661 ID="BP613"RENDERAS="SECT2"ID="FM90669"Loading Procedures for DriversIDXID="w8789"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"IDXID="w8790"BOOK="_idx" COLLECTION="nw41" TIDREF="i2153"
IDXID="w8791"BOOK="_idx" COLLECTION="nw41" TIDREF="i2153"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have installed your controller and storage device according to the hardware manufacturer's instructions before proceeding.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load the drivers for controller and storage devices.To load device driver(s), at the serve
r console prompt, type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD controller_device_driver_name(s) MOREINFO="NONE"<Enter>
LOA
D storage_device_driver_name 
MOREINFO="NONE"<Enter>For example, to load AHA1540.DSK and TAPEDAI.DSK, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"   LOAD C:AHA1540 MOREINFO="NONE"<Enter>
LOAD C:TAPEDAI 
MOREINFO="NONE"<Enter>T
o have these device drivers 
load automatically, place these commands in the server's STARTUP.NCF file.PERFORMANCE="REQUIRED"To register the storage device with the system, type the following at the serve
r console prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"SCAN FOR NEW DEVICES MOREINFO="NONE"<Enter>If you load TAPEDAI.DSK from within the STARTUP.NCF file, you do not need the command "SCAN FOR NEW DEVICES."PAGENUM=662 ID="BP614"RENDERAS="SECT2"ID="FM18303"Loading Procedures for ServersIDXID="w8792"BOOK="_idx" COLLECTION="nw41" TIDREF="i2159"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have installed your controller and storage device according to the hardware manufacturer's instructions before proceeding.Ensure that your host server's controller and storage device drivers have been loaded. (See IDREF="FM90669""Loading Procedures for Drivers" on page 661.)Ensure that you have registered the new device with the system by typing "SCAN FOR NEW DEVICES" at the server console prompt.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"ID="FM25215"Using the following table, load the necessary files for your target server (NetWare 4.1, 4.0, 3.12, or 3.11).COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="7*"COLNAME=3 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"To back up thisCOLNAME=2 ROTATE="0" MOREROWS="0"At this consoleCOLNAME=3 ROTATE="0" MOREROWS="0"Enter this commandVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"4.1 host serverCOLNAME=2 ROTATE="0" MOREROWS="0"4.1 host server4.1 host serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSA410LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"4.1 target serverCOLNAME=2 ROTATE="0" MOREROWS="0"Target server4.1 host serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSA410LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"4.0 target serverCOLNAME=2 ROTATE="0" MOREROWS="0"Target server4.1 host serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSA400LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"3.12 target serverCOLNAME=2 ROTATE="0" MOREROWS="0"Target server4.1 host serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSA312LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"3.11 target serverCOLNAME=2 ROTATE="0" MOREROWS="0"Target server4.1 host serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSA311LOAD SBACKUP [options]PAGENUM=663 ID="BP615"TheID="FM28932"SBACKUP options are buffer size and number of buffers. To use these options, at the host server console, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD [path]SBACKUP SIZE=XXX BUFFER=X MOREINFO="NONE"<Enter>The x's represent the buffer size and number of buffers.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Supported ValuesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SizeCOLNAME=2 ROTATE="0" MOREROWS="0"16, 32, 64, 128, or 256 KB (Default=64 KB)COLNAME=1 ROTATE="0" MOREROWS="0"BuffersCOLNAME=2 ROTATE="0" MOREROWS="0"2 to 10 (Default=4)If you type "LOAD SBACKUP" without specifying options
, SBACKUP loads the default buffer size (64 KB) and the default number of buffers (4).For more on changing buffer sizes and numbers, see IDREF="FM76095""Enhancing SBACKUP Performance" on page 752.T
o have the files load automatically, place the commands in the server's STARTUP.NCF file, and in the workstation's NET.CFG file or AUTOEXEC.BAT file (for DOS) or Startup folder (for OS/2)
.RENDERAS="SECT2"ID="FM57809"Loading Procedures for WorkstationsIDXID="w8793"BOOK="_idx" COLLECTION="nw41" TIDREF="i2159"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have installed your controller and storage device according to the hardware manufacturer's instructions before proceeding.Ensure your host server's controller and storage device drivers have been loaded. (See IDREF="FM90669""Loading Procedures for Drivers" on page 661.)Ensure that you have registered the new device with the system by typing "SCAN FOR NEW DEVICES" at the server console prompt.PAGENUM=664 ID="BP616"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Using the following table and procedures, load the necessary files for your target workstation.COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"To back up thisCOLNAME=2 ROTATE="0" MOREROWS="0"At this consoleCOLNAME=3 ROTATE="0" MOREROWS="0"Enter this commandVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DOS workstationCOLNAME=2 ROTATE="0" MOREROWS="0"Host serverTarget workstationHost serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSADOSTSASMS [parameters]LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"OS/2 workstationCOLNAME=2 ROTATE="0" MOREROWS="0"Host serverTarget workstationHost serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSAPROXYTSAOS2LOAD SBACKUP [options]PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"At the host server, load either TSADOS or TSAPROXY, depending on your target workstation.PERFORMANCE="REQUIRED"At the target workstation, reject all incoming messages.Receiving messages break the SPXTM connection and all activity on a workstation stops until you press MOREINFO="NONE"<Ctrl>+<Enter>.To reject all messages and avoid breaking the SPX connection, at the target workstation prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"SEND /A=N MOREINFO="NONE"<Enter>After completing a backup, a counter-command is necessary to allow the workstation to receive messages. See IDREF="FM88278""Unloading SBACKUP Files" on page 751 for unloading procedures.PERFORMANCE="REQUIRED"At th
e same workstation, change to the client software directory where TSASMS.COM 
or TSAOS2 resides.An example of a NetWare client software directory is "C:\NWCLIENT".PERFORMANCE="REQUIRED"At th
e same workstation, enter 
the load 
IDXID="w8794"BOOK="_idx" COLLECTION="nw41" TIDREF="i4426"
comman
dIDXID="w8795"BOOK="_idx" COLLECTION="nw41" TIDREF="i4426"
 fo
r your Target Service Agent (either TSASMS [
parameters] or TSAOS2).
PAGENUM=665 ID="BP617"To load TSASMS, use the following syntax and IDREF="FM91263"Table 9-1.FORMAT="LINESPECIFIC"MOREINFO="NONE"TSASMS /SE=host_server_name
 /P=workstation_password (or /T) /D=drive_letter /N=workstation_nameIDREF="FM91263"Table 9-1 explains how to use the TSASMS parameters at DOS workstations.LABEL="9-1" PGWIDE=0 TOCENTRY="1"IDXID="w8796"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w8797"BOOK="_idx" COLLECTION="nw41" TIDREF="i4426"ID="FM91263" TSASMS ParametersCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="12*"COLNAME=3 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"Rules for UseCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"/SE[rver]=server_nameCOLNAME=2 ROTATE="0" MOREROWS="0"Must specify the host server.COLNAME=3 ROTATE="0" MOREROWS="0"Specifies the name of the NetWare server you want the target workstation to connect to for backup and restore services.COLNAME=1 ROTATE="0" MOREROWS="0"/P[assword]=IDXID="w8798"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"passwordCOLNAME=2 ROTATE="0" MOREROWS="0"Required if /T[rust] parameter is not used. Limited to 10 characters.COLNAME=3 ROTATE="0" MOREROWS="0"Identifies the target workstation's unique password, or is used initially to specify a password.COLNAME=1 ROTATE="0" MOREROWS="0"/T[rust]COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w8799"BOOK="_idx" COLLECTION="nw41" TIDREF="i4590"
Required if /P=password parameter is not used. Use only if bindery services are used on host server. User must be ADMIN or a supervisor equivalent.COLNAME=3 ROTATE="0" MOREROWS="0"Allows a supervisor equivalent to back up and restore without the workstation password if bindery services are used on the server (if "Set bindery services" is in the AUTOEXEC.NCF or on the server console).COLNAME=1 ROTATE="0" MOREROWS="0"/D[rive]=x[xx]COLNAME=2 ROTATE="0" MOREROWS="0"Must specify at least one (x=C, D or E). If two or more, do not space between letters (example: /D=CD).COLNAME=3 ROTATE="0" MOREROWS="0"Specifies the hard drive(s) being backed up or restored. TSASMS will not back up floppy drives or network drives.COLNAME=1 ROTATE="0" MOREROWS="0"/B[uffers]=nCOLNAME=2 ROTATE="0" MOREROWS="0"Not required, but can be changed (n =1 through 30).COLNAME=3 ROTATE="0" MOREROWS="0"Increases the number of buffers, which increases throughput speed but requires more IDXID="w8800"BOOK="_idx" COLLECTION="nw41" TIDREF="i3668"
RAM on the workstation. The default is one buffer.COLNAME=1 ROTATE="0" MOREROWS="0"/N[ame]=workstation_nameCOLNAME=2 ROTATE="0" MOREROWS="0"Required the first time TSASMS is loaded for a particular server. Limited to 10 characters.COLNAME=3 ROTATE="0" MOREROWS="0"Identifies the target workstation's unique name, or is used initially to name a workstation.COLNAME=1 ROTATE="0" MOREROWS="0"/ST[ack]=nnnCOLNAME=2 ROTATE="0" MOREROWS="0"Not required. Use only if RAM is extremely limited or you receive "Stack Overflow" messages. Replace nnn with a number (512 through 4096).COLNAME=3 ROTATE="0" MOREROWS="0"Specifies IDXID="w8801"BOOK="_idx" COLLECTION="nw41" TIDREF="i4249" stack size. The default is 2048 bytes.COLNAME=1 ROTATE="0" MOREROWS="0"/U[nload]COLNAME=2 ROTATE="0" MOREROWS="0"Can be used only at the workstation command line.COLNAME=3 ROTATE="0" MOREROWS="0"Unloads TSASMS from the workstation's memory.COLNAME=1 ROTATE="0" MOREROWS="0"/H[elp]COLNAME=2 ROTATE="0" MOREROWS="0"Can be used only at the workstation command line.COLNAME=3 ROTATE="0" MOREROWS="0"Displays all parameters.PAGENUM=666 ID="BP618"For example, to load TSASMS where the following is true for the workstation being backed up,(1) CHICAGO is the host server name(2) The /T[rust] parameter is used(3) Drive C is specified as the target drive(4) BASEBALL is the workstation nameat the workstation command line, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"TSASMS /SE=CHICAGO /T /D=C /N=BASEBALLMOREINFO="NONE" <Enter>If loading multiple terminate-and-stay resident (TSR) programs on a DOS workstation, load TSASMS last.To avoid loading the workstation Target Service Agent with each session, place it in the workstation's AUTOEXEC.BAT file or NET.CFG file (for DOS), or Startup folder (for OS/2).If you decide to use NET.CFG, be aware that(1) You must be using IPXODI and LSL.(2) Command line parameters override the NET.CFG.(3) /H and /U are only available at the command line.For more information on the NET.CFG file, see 
BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User Guide.PERFORMANCE="REQUIRED"At the host server, load SBACKUP
, using the following synta
x:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SBACKUP [options]
PAGENUM=667 ID="BP619"If you type "LOAD SBACKUP" without specifying options, SBACKUP will assume you want the default buffer size (64 KB) and the default number of buffers (4).To avoid loading the commands with each session, place them in either the server's AUTOEXEC.NCF or STARTUP.NCF file.For information on SBACKUP options, see IDREF="FM18303""Loading Procedures for Servers" on page 662.RENDERAS="SECT2"ID="FM55742"Loading Procedures for NetWare Directory ServicesIDXID="w8802"BOOK="_idx" COLLECTION="nw41" TIDREF="i2159"Before using these procedures to back up your NetWare Directory Services (NDS) database, you should understand the importance of having both replicas and media backup sessions available.RENDERAS="SECT3"Restore NDS from ReplicasIDXID="w8803"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"IDXID="w8804"BOOK="_idx" COLLECTION="nw41" TIDREF="i2730"The only absolute way to ensure that the NDS database can be fully restored is through partition replication, with one master partition and associated replicas on multiple servers.For more information on partitions and replicas, see IDREF="FM57530"Chapter 5, "Managing the NetWare Directory Tree."RENDERAS="SECT3"Restore NDS from Media Backup SessionIDXID="w8805"BOOK="_idx" COLLECTION="nw41" TIDREF="i2730"IDXID="w8806"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"Restore an NDS database by using SBACKUP only in the event of a catastrophic data loss, where all replicas have become corrupted.If you must restore NDS from SBACKUP, load the NDS Target Service Agent (TSANDS) on the same server as SBACKUP (the host server).RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have installed your controller and storage device according to the hardware manufacturer's instructions before proceeding.Ensure that your host server's controller and storage device drivers have been loaded. (See IDREF="FM90669""Loading Procedures for Drivers" on page 661.)PAGENUM=668 ID="BP620"Ensure that you have registered the new device with the system by typing "SCAN FOR NEW DEVICES" at the server console prompt.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"At the host server console prompt, enter the load commands for an NDS Target Service Agent:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD TSANDS MOREINFO="NONE"<MOREINFO="NONE"Enter>
LOAD SBACKUP [options]MOREINFO="NONE"<MOREINFO="NONE"Enter>RENDERAS="SECT2"ID="FM67643"Loading Procedures for SFT III UsersIDXID="w8807"BOOK="_idx" COLLECTION="nw41" TIDREF="i2159"IDXID="w8808"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"The NetWare 4.1 SFT IIITM operating system handles device input/output and file system operations in separate engines, the IOEngine and the MSEngine. Enter load commands in the engine indicated.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Change to the IOEngine prompt of the SFT III server where the storage device is installed.PERFORMANCE="REQUIRED"Load the device drivers for the controller and storage device. (Se
e IDREF="FM90669""Loading Procedures for Drivers" on page 661.)For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD AHA1740MOREINFO="NONE" <MOREINFO="NONE"Enter>
LOAD TAPEDAIMOREINFO="NONE" <MOREINFO="NONE"EnterMOREINFO="NONE">To have the drivers 
load automatically, put the LOAD commands in the IOSTART.NCF file of the server with the storage device.PERFORMANCE="REQUIRED"Change to the MSEngine prompt.PERFORMANCE="REQUIRED"Enter the load commands for your target. (See IDREF="FM96819""LOAD Commands Summary" on page 669.)For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SCAN FOR NEW DEVICES MOREINFO="NONE"<Enter>
LOAD TSA410MOREINFO="NONE" <MOREINFO="NONE"Enter>
LOAD SBACKUPMOREINFO="NONE" <MOREINFO="NONE"Enter>PAGENUM=669 ID="BP621"To have the modules load automatically, put the commands in the MSAUTO.NCF file.RENDERAS="SECT2"ID="FM96819"LOAD Commands SummaryIDXID="w8809"BOOK="_idx" COLLECTION="nw41" TIDREF="i2159"IDREF="FM71287"Table 9-2 is a summary of the load commands for backup or restore targets. Use this table for reference only after you are familiar with the target's loading procedures.Type the commands at the specified console in the order given.LABEL="9-2" PGWIDE=1 TOCENTRY="1"ID="FM71287" LOAD Commands for Servers, Workstations, or NDS DatabasesCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="11*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"To back up thisCOLNAME=2 ROTATE="0" MOREROWS="0"At this consoleCOLNAME=3 ROTATE="0" MOREROWS="0"Enter this commandVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"4.1 host serverCOLNAME=2 ROTATE="0" MOREROWS="0"4.1 host server4.1 host serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSA410LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"4.1 target serverCOLNAME=2 ROTATE="0" MOREROWS="0"Target server4.1 host serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSA410LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"4.0 target serverCOLNAME=2 ROTATE="0" MOREROWS="0"Target server4.1 host serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSA400LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"3.12 target serverCOLNAME=2 ROTATE="0" MOREROWS="0"Target server4.1 host serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSA312LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"3.11 target serverCOLNAME=2 ROTATE="0" MOREROWS="0"Target server4.1 host serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSA311LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"DOS workstationCOLNAME=2 ROTATE="0" MOREROWS="0"Host serverTarget workstationHost serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSADOSTSASMS [parameters]LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"OS/2 workstationCOLNAME=2 ROTATE="0" MOREROWS="0"Host serverTarget workstationHost serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSAPROXYTSAOS2LOAD SBACKUP [options]COLNAME=1 ROTATE="0" MOREROWS="0"NDS databaseCOLNAME=2 ROTATE="0" MOREROWS="0"Host serverHost serverCOLNAME=3 ROTATE="0" MOREROWS="0"LOAD TSANDSLOAD SBACKUP [options]PAGENUM=670 ID="BP622"For information on SBACKUP options (changing buffer size and number of buffers), see IDREF="FM79118""Changing the Size and Number of Buffers" on page 753. For information on TSASMS parameters, see IDREF="FM91263"Table 9-1 on page 665.If loading multiple TSRs on a DOS workstation, load the DOS workstation Target Service Agent (TSASMS) last. For example, load IPXODI before TSASMS.For SFT III 3.11, TSA311 loads at the MSEngine prompt, and SBACKUP loads in the IOEngine associated with the tape device.RENDERAS="SECT1"ID="FM72637"Backing Up DataRENDERAS="SECT2"Introduction to Backing Up DataThis section provides an introduction toMARK=BULLETBackup filesBackup typesBackup optionsBackup logbookBackup schedulesEffect of backup type and schedule on the backup and restore processPAGENUM=671 ID="BP623"RENDERAS="SECT3"Backup FilesEach backup session produces three types of IDXID="w8810"BOOK="_idx" COLLECTION="nw41" TIDREF="i395"
files:MARK=BULLETData files: Copied to the selected storage media.Log file: Placed in a directory on the host server and accessed through the SBACKUP "Main Menu" screen.Error file: Placed in a directory on the host server and accessed through the SBACKUP "Main Menu" screen.The log and error files are labeled with the same description you give the session and are automatically updated with every session.Both log and error files contain pertinent information, such as the session's date, time, and media identification, but the error file also contains a list of any errors that occurred during the backup session, such as files that were not backed up.RENDERAS="SECT3"ID="FM14384"Backup TypesSBACKUP has four IDXID="w8811"BOOK="_idx" COLLECTION="nw41" TIDREF="i403"
types of IDXID="w8812"BOOK="_idx" COLLECTION="nw41" TIDREF="i395"
backup sessions, which affect each file's modify bit in different ways.When the modify bit (or Archive Needed attribute) is set, it indicates that the file or directory needs archiving. When the modify bit is cleared, the file will be passed over during certain types of backups.MARK=BULLETFull backup:
Backs up all data and clears the modify bit.Differential backup: 
Backs up all data modified since the last full backup and does not clear the modify bit.Incremental backup: 
Backs up all data modified since the last full or incremental backup (whichever was last) and clears the modify bit.Custom backup:
Backs up only the data you specify and allows you to specify whether to clear the modify bit. Use this option when you want to select portions of the directory structure as the target, using include and exclude options.PAGENUM=672 ID="BP624"Differential and incremental backup are not interchangeable. See IDREF="FM95249""Backup Schedules" on page 679 for examples of use.RENDERAS="SECT3"Backup OptionsFor a custom backup, you can specify exactly what to back up by selecting options from the "Custom Backup Options" screen.A custom backup session allows you toMARK=BULLETChoose subsets of data to back upScan what you are backing upRENDERAS="SECT4"Choosing Subsets of Data to Back UpYou can IDXID="w8813"BOOK="_idx" COLLECTION="nw41" TIDREF="i402"
choose specific subsets of a data set to exclude from or include in the backup session by selecting major resources (such as volumes) or minor resources (such as directories, paths, or files) to exclude from or include in the backup.RENDERAS="SECT4"Understanding the Exclude and Include OptionsWhenever you 
perform a custom backup, you can use the exclude and include options to select subsets of what you want to back up.RENDERAS="SECT4"Using ExcludeTo back up IDXID="w8814"BOOK="_idx" COLLECTION="nw41" TIDREF="i1371"
most of the directory structure while omitting only a small part, use the exclude option to omit the part you don't want to back up. Everything that you don't specifically exclude is included.After you exclude part of the directory structure (like a volume or directory), you cannot include any subdirectories or files beneath that excluded volume or directory.PAGENUM=673 ID="BP625"RENDERAS="SECT4"Using IncludeTo back up a relatively small part of the directory structure, use the include option to specify the data you want. Everything you don't specifically include is excluded.When you select only IDXID="w8815"BOOK="_idx" COLLECTION="nw41" TIDREF="i1774"
part of the directory structure to include (such as a volume), all directories, subdirectories, and files under that selection are included in the backup by default.IDREF="FM32204"Figure 9-2 illustrates this use of the include option. In the figure, volume SYS: is selected as an include option. All other areas of the directory structure will be excluded from the backup.However, you can specifically exclude some subdirectories or files beneath your selection if you need to.LABEL="9-2" FLOAT="0"ID="FM32204"SBACKUP Include Option: Specific Volume Included, All Others ExcludedFILEREF="n41sb02a.tif"The same principle applies when you specify a directory with the include option. IDREF="FM77103"Figure 9-3 shows that all directories, subdirectories, and files under the NetUsers directory will be included in the backup. All other areas of the directory structure are excluded from the backup.PAGENUM=674 ID="BP626"LABEL="9-3" FLOAT="0"ID="FM77103"SBACKUP Include Option: Specific Directory Included, All Others ExcludedFILEREF="n41sb03a.tif"The reverse is true when you select a major Target Service Agent resource, a directory, or a file as an exclude option. All other areas of the directory structure will be included in the backup.RENDERAS="SECT4"Using Include and Exclude Options TogetherBy IDXID="w8816"BOOK="_idx" COLLECTION="nw41" TIDREF="i1774"
combining the IDXID="w8817"BOOK="_idx" COLLECTION="nw41" TIDREF="i1371"
include and exclude options, you can more precisely control what is backed up.For example, the following command sequence results in volume HOME: being included in the backup, with the exception of the MARY directory and the WIDGET.EXE file.FORMAT="LINESPECIFIC"MOREINFO="NONE"Include major TSA resources HOME:
Exclude directories (full path): HOME:NETUSERS/MARY
Exclude path/files HOME:NETUSERS/KARL/PROJECT/WIDGET.EXE
PAGENUM=675 ID="BP627"IDREF="FM45484"Figure 9-4 illustrates this example.LABEL="9-4" FLOAT="0"ID="FM45484"Combining SBACKUP Include and Exclude OptionsFILEREF="n41sb04a.tif"RENDERAS="SECT4"ID="FM79836"Scanning Data SetsYou can specify different types of data sets to be scanned.A data set is a group of data that can be manipulated by SBACKUP. Each data set in the directory structure can be classified as a parent or a child, and each class includes different types of data items.Within SBACKUP, a IDXID="w8818"BOOK="_idx" COLLECTION="nw41" TIDREF="i3217"parent might be a server, a volume, or a directory. A IDXID="w8819"BOOK="_idx" COLLECTION="nw41" TIDREF="i629"child is a file, which is the lowest level of the directory structure.As shown in IDREF="FM66337"Figure 9-5, the unit below a parent is not necessarily a child; it might be another parent, or the line might end with the parent. The unit above a child must always be a parent.PAGENUM=676 ID="BP628"LABEL="9-5" FLOAT="0"ID="FM66337"Parent and Child Levels in a Directory StructureFILEREF="n41sb05a.tif"Items in a data set for either a parent or child should be items that do not frequently change. You may choose to exclude from the backup session one or more of the items in your target's data set.PAGENUM=677 ID="BP629"IDREF="FM27634"Figure 9-6 shows typical NetWare data sets.LABEL="9-6" FLOAT="0"ID="FM27634"Data Sets Containing Different Types of Data ItemsFILEREF="n40sb15a.tif"RENDERAS="SECT3"Backup LogbookYou should keep a IDXID="w8820"BOOK="_idx" COLLECTION="nw41" TIDREF="i402"
hard-copy log of your backups in case your online log and error files become corrupted. The log should contain the following information:MARK=BULLETSource backed up (such as the server or workstation name)Full path for session log and error files directoryFull path for backed-up dataLabel of the media on which the backup is storedDescription of the sessionName or initials of the person performing the backupDate and time of the backup sessionIDREF="FM39259"Figure 9-7 shows a sample backup log page.PAGENUM=678 ID="BP630"LABEL="9-7" FLOAT="0"IDXID="w8821"BOOK="_idx" COLLECTION="nw41" TIDREF="i397"ID="FM39259"A Sample Backup Log PageFILEREF="n40sb18a.tif"PAGENUM=679 ID="BP631"RENDERAS="SECT3"ID="FM95249"Backup SchedulesBefore you begin actual backup procedures, plan a backup IDXID="w8822"BOOK="_idx" COLLECTION="nw41" TIDREF="i402"
schedule based on your needs, considering such factors as the number of users and frequency of changes to files.You may want to perform different types of backups on different schedules. For example,MARK=BULLETDaily: Perform an incremental or differential backup after the close of business. If revisions are heavy and rapid, consider several backup sessions each day.Weekly: Perform an incremental or differential backup after the close of business on the last day of the week for three of the four weeks in the month.Monthly: Perform a full backup on the last business day of the month (for example, the first or last Friday).Major changes: Perform a full backup before and after you change your configuration, and before and after you upgrade your server to a new version of NetWare.Application changes: Perform a custom backup before and after you modify applications.RENDERAS="SECT3"Effect of Backup Type and Schedule on the Backup and Restore ProcessEach typeIDXID="w8823"BOOK="_idx" COLLECTION="nw41" TIDREF="i403"
 of backup has a different effect on the backup and restore process. In planning your backup schedule, consider all of the variables in IDREF="FM96538"Table 9-3 before determining the schedule that is right for you.Don't interchange differential backups and incremental backups. If you do, the differential backup won't contain all changes since the last full backup. Use full backups interspersed with differential backups, or full backups interspersed with incremental backups.LABEL="9-3" PGWIDE=0 TOCENTRY="1"ID="FM96538" Comparative Speed and Media Use of Different Backup TypesCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="8*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"VariableCOLNAME=2 ROTATE="0" MOREROWS="0"Incremental and Full Backups InterspersedCOLNAME=3 ROTATE="0" MOREROWS="0"Differential and Full Backups InterspersedVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Media usage for storageCOLNAME=2 ROTATE="0" MOREROWS="0"Less media usedCOLNAME=3 ROTATE="0" MOREROWS="0"More media usedCOLNAME=1 ROTATE="0" MOREROWS="0"Backup speedCOLNAME=2 ROTATE="0" MOREROWS="0"FasterCOLNAME=3 ROTATE="0" MOREROWS="0"SlowerCOLNAME=1 ROTATE="0" MOREROWS="0"Restore speedCOLNAME=2 ROTATE="0" MOREROWS="0"SlowerCOLNAME=3 ROTATE="0" MOREROWS="0"FasterPAGENUM=680 ID="BP632"Media usage and backup speed: Each differential backup uses more media and is slower than an incremental backup because it backs up more files. However, this helps increase the speed of the restore.Restoring after incremental backups: If you have done full and incremental backups and IDXID="w8824"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"
need to restore data, you must restore the last full backup as well as all subsequent incremental backups.Restoring after differential backups: If you have done full and differential backups and IDXID="w8825"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"need to restore data after an unexpected loss, you need to restore only the last full and the last differential backup.IDREF="FM61319"Table 9-4 illustratesIDXID="w8826"BOOK="_idx" COLLECTION="nw41" TIDREF="i403"
 what happens in a series of full and incremental backups.LABEL="9-4" PGWIDE=1 TOCENTRY="1"ID="FM61319" A Typical Backup Schedule of Full and Incremental BackupsCOLS=5 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="5*"COLNAME=3 COLWIDTH="4*"COLNAME=4 COLWIDTH="4*"COLNAME=5 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Date (day)COLNAME=2 ROTATE="0" MOREROWS="0"TypeCOLNAME=3 ROTATE="0" MOREROWS="0"Total Number of FilesCOLNAME=4 ROTATE="0" MOREROWS="0"New or Revised Files Since Last Full or Incremental BackupCOLNAME=5 ROTATE="0" MOREROWS="0"Total Number of Files Backed UpVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Sept 4 (Fri)COLNAME=2 ROTATE="0" MOREROWS="0"FullCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"50COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"N/ACOLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"50COLNAME=1 ROTATE="0" MOREROWS="0"Sept 7 (Mon)COLNAME=2 ROTATE="0" MOREROWS="0"IncrementalCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"60COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"25COLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"25COLNAME=1 ROTATE="0" MOREROWS="0"Sept 8 (Tue)COLNAME=2 ROTATE="0" MOREROWS="0"IncrementalCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"80COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"25COLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"25COLNAME=1 ROTATE="0" MOREROWS="0"Sept 9 (Wed)COLNAME=2 ROTATE="0" MOREROWS="0"IncrementalCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"100COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"30COLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"30COLNAME=1 ROTATE="0" MOREROWS="0"Sept 10 (Thu)COLNAME=2 ROTATE="0" MOREROWS="0"IncrementalCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"125COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"40COLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"40COLNAME=1 ROTATE="0" MOREROWS="0"Sept 11 (Fri)COLNAME=2 ROTATE="0" MOREROWS="0"FullCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"150COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"N/ACOLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"150PAGENUM=681 ID="BP633"Incremental backup sessions back up only files that have the modify bit set, which are files that have changed since the last full or incremental backup session (when the modify bit was cleared).For example, if your backup IDXID="w8827"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"
schedule resembled IDREF="FM61319"Table 9-4 and you experienced a loss of data before completing the full backup on Sept 11, you would have to restore the sessions listed 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"Date of Backup SessionCOLNAME=2 ROTATE="0" MOREROWS="0"Type of BackupCOLNAME=3 ROTATE="0" MOREROWS="0"Number of Files Backed UpCOLNAME=4 ROTATE="0" MOREROWS="0"Cumulative Number of Files RestoredVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Sept 4 (Fri)COLNAME=2 ROTATE="0" MOREROWS="0"FullCOLNAME=3 ROTATE="0" MOREROWS="0"50COLNAME=4 ROTATE="0" MOREROWS="0"50COLNAME=1 ROTATE="0" MOREROWS="0"Sept 7 (Mon)COLNAME=2 ROTATE="0" MOREROWS="0"IncrementalCOLNAME=3 ROTATE="0" MOREROWS="0"25COLNAME=4 ROTATE="0" MOREROWS="0"75COLNAME=1 ROTATE="0" MOREROWS="0"Sept 8 (Tue)COLNAME=2 ROTATE="0" MOREROWS="0"IncrementalCOLNAME=3 ROTATE="0" MOREROWS="0"25COLNAME=4 ROTATE="0" MOREROWS="0"100COLNAME=1 ROTATE="0" MOREROWS="0"Sept 9 (Wed)COLNAME=2 ROTATE="0" MOREROWS="0"IncrementalCOLNAME=3 ROTATE="0" MOREROWS="0"30COLNAME=4 ROTATE="0" MOREROWS="0"130COLNAME=1 ROTATE="0" MOREROWS="0"Sept 10 (Thu)COLNAME=2 ROTATE="0" MOREROWS="0"IncrementalCOLNAME=3 ROTATE="0" MOREROWS="0"40COLNAME=4 ROTATE="0" MOREROWS="0"170IDREF="FM15011"Table 9-5 illustratesIDXID="w8828"BOOK="_idx" COLLECTION="nw41" TIDREF="i403"
 what happens in a series of full and differential backups.LABEL="9-5" PGWIDE=1 TOCENTRY="1"ID="FM15011" A Backup Schedule of Full and Differential BackupsCOLS=5 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="5*"COLNAME=3 COLWIDTH="4*"COLNAME=4 COLWIDTH="4*"COLNAME=5 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Date (Day)COLNAME=2 ROTATE="0" MOREROWS="0"TypeCOLNAME=3 ROTATE="0" MOREROWS="0"Total Number of FilesCOLNAME=4 ROTATE="0" MOREROWS="0"New or Revised Files Since Last Full BackupCOLNAME=5 ROTATE="0" MOREROWS="0"Total Number of Files Backed UpVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Sept 4 (Fri)COLNAME=2 ROTATE="0" MOREROWS="0"FullCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"50COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"N/ACOLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"50COLNAME=1 ROTATE="0" MOREROWS="0"Sept 7 (Mon)COLNAME=2 ROTATE="0" MOREROWS="0"DifferentialCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"60COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"25COLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"25COLNAME=1 ROTATE="0" MOREROWS="0"Sept 8 (Tue)COLNAME=2 ROTATE="0" MOREROWS="0"DifferentialCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"80COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"25COLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"50COLNAME=1 ROTATE="0" MOREROWS="0"Sept 9 (Wed)COLNAME=2 ROTATE="0" MOREROWS="0"DifferentialCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"100COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"30COLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"80COLNAME=1 ROTATE="0" MOREROWS="0"Sept 10 (Thu)COLNAME=2 ROTATE="0" MOREROWS="0"DifferentialCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"125COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"40COLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"120COLNAME=1 ROTATE="0" MOREROWS="0"Sept 11 (Fri)COLNAME=2 ROTATE="0" MOREROWS="0"FullCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"150COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"N/ACOLNAME=5 ALIGN="CENTER" ROTATE="0" MOREROWS="0"150PAGENUM=682 ID="BP634"When you perform a differential backup, the modify bit isn't cleared after the backup, as it is after a full or incremental backup. So, all files modified since the last full backup are included in the backup (unless they have been deleted).For example, if your backup IDXID="w8829"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"
schedule resembled IDREF="FM15011"Table 9-5 and you experienced a loss of data before completing the full backup on Sept 11, you would have to restore the sessions listed 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"Date of Backup SessionCOLNAME=2 ROTATE="0" MOREROWS="0"Type of BackupCOLNAME=3 ROTATE="0" MOREROWS="0"Number of Files Backed UpCOLNAME=4 ROTATE="0" MOREROWS="0"Cumulative Number of Files RestoredVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Sept 4 (Fri)COLNAME=2 ROTATE="0" MOREROWS="0"FullCOLNAME=3 ROTATE="0" MOREROWS="0"50COLNAME=4 ROTATE="0" MOREROWS="0"50COLNAME=1 ROTATE="0" MOREROWS="0"Sept 10 (Thu)COLNAME=2 ROTATE="0" MOREROWS="0"DifferentialCOLNAME=3 ROTATE="0" MOREROWS="0"120COLNAME=4 ROTATE="0" MOREROWS="0"170Compare this example with the previous example. In both cases the total number of files restored is 170. However, to restore all of the lost data, five backup sessions have to be restored in the first example compared with only two backup sessions in the second.For more on backup scheduling, see "BOOK="cncptenu" COLLECTION="nw41"Backup" in Concepts.RENDERAS="SECT2"ID="FM84714"Prerequisites to Backing UpMARK=CHECKBOXUnderstand the terms listed in IDREF="FM79417""Backup and Restore Concepts" on page 654.Understand the rules and guidelines for using SBACKUP. (See IDREF="FM63064""Rules for Using SBACKUP" on page 656)If you are backing up an OS/2 or DOS workstation, know the workstation's password if the Target Service Agent was originally loaded with the "/Password" parameter instead of the "/Trust" parameter, as explained in IDREF="FM91263"Table 9-1 on page 665.Make sure the required files for your target are loaded. (See IDREF="FM71287"Table 9-2 on page 669.)Know what type of backup you want to perform: Full, Differential, Incremental, or Custom. (See IDREF="FM14384""Backup Types" on page 671.)PAGENUM=683 ID="BP635"Have Read and File Scan rights to the directories/files you are backing up.For a custom backup, know the directory structure of the target you are backing up. You will be prompted for the paths to the volumes and directories you want to include or exclude from your backup.RENDERAS="SECT2"ID="FM33249"Procedures for Full, Differential, or Incremental BackupsThe following IDXID="w8830"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"
steps detail a 
full, 
differential, and /or 
incremental backup from beginning to end.For a custom backup, see IDREF="FM92502""Procedures for Custom Backups" on page 692.The figures and choices in this section depict choices available to you when using the NetWare 4.1 File System Target Service Agent (TSA410). If you are backing up a workstation or database, rather than a NetWare 4.1 server, your screen displays will vary slightly.SBACKUP displays prompts and messages at the bottom of the screen. For instance, you can press MOREINFO="NONE"<F1> for help at any time.If you are performing a series of backups and need to change your target, follow the procedures in IDREF="FM34972""Changing Targets" on page 749 before proceeding.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have met the prerequisites detailed in IDREF="FM84714""Prerequisites to Backing Up" on page 682.Ensure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.PAGENUM=684 ID="BP636"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Backup" (IDREF="FM19928"Figure 9-8).LABEL="9-8" FLOAT="0"ID="FM19928"SBACKUP "Main Menu"FILEREF="n40sb20a.tif"PERFORMANCE="REQUIRED"Choose a NetWare server running your backup/restore Target Service Agent (similar to IDREF="FM85822"Figure 9-9).LABEL="9-9" FLOAT="0"ID="FM85822"List of Servers Available for Backup (Typical)FILEREF="n40sb31a.tif"This screen will not appear if you have only one server with a TSA loaded. If you don't see the 
IDXID="w8831"BOOK="_idx" COLLECTION="nw41" TIDREF="i395"
target
IDXID="w8832"BOOK="_idx" COLLECTION="nw41" TIDREF="i4430"
 you want on the list, check for these possible causes:
MARK=BULLETThe proper Target Service Agent isn't loaded on either the host or the target. (See IDREF="FM71287"Table 9-2 on page 669 for LOAD commands.)The host and target are physically far apart, or network traffic is heavy. Press MOREINFO="NONE"<Esc> to return to the "Main Menu," and then press MOREINFO="NONE"<Enter> again. Your target should now be listed.
PAGENUM=685 ID="BP637"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="17*"COLNAME=2 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"Go ToVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Your chosen target has more than one Target Service Agent loadedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM76209"Step 3COLNAME=1 ROTATE="0" MOREROWS="0"Your chosen target has only one Target Service Agent loadedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM64558"Step 4PERFORMANCE="REQUIRED"ID="FM76209"From the Target Services list (similar to IDREF="FM13463"Figure 9-10), choose a target.If the target you choose has more than on
e Target Service Agent loaded, SBACKUP will show you a list of th
eir full names.For example, IDREF="FM13463"Figure 9-10 shows that the NetWare server named SALES is running the following Target Service Agents:
TYPE="VERT"DOS Workstation (TSADOS)NetWare 2.2 File System (TSA220)NetWare 4.1 Directory (TSANDS)NetWare [4.1] File System (TSA410)OS/2 Workstation (TSAPROXY).You can back up data residing in any of these environments.LABEL="9-10" FLOAT="0"ID="FM13463"Display of Multiple Target Service Agents on a TargetFILEREF="n41sb39a.tif"PAGENUM=686 ID="BP638"PERFORMANCE="REQUIRED"ID="FM64558"Whe
n prompted for the Target username, enter your username (and context if required) as network supervisor for the target.If SBACKUP rejects the supervisor usernam
e you entered, you probably need to include the context of where the user object is located. For example, instead of entering "ADMIN" as the username, enter ".CN=ADMIN.O=
company_name".You must include the context in the username at this point if the username you use exists in a directory container that is different from the context set on the server running SBACKUP.PERFORMANCE="REQUIRED"If a password is requested, enter the password for the target.SBACKUP will take a few moments to attach to the 
IDXID="w8833"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
target. Wait for the confirmation box, then press any key to continue.PERFORMANCE="REQUIRED"Select the device and medi
a for the bac
kup.MARK=BULLETIf your host has only one storage device attached, SBACKUP selects the device for you and notifies you of the device and media that will be used.If your device has more than one storage device attached, choose an available device from those listed.If the device contains media, SBACKUP automatically selects it for the backup.If the storage media does not have a label, SBACKUP displays a message saying that the media cannot be identified. SBACKUP continues, but prompts you later to enter the media label.PERFORMANCE="REQUIRED"Specify a location for your session log and error files (se
e IDREF="FM14922"Figure 9-11).LABEL="9-11" FLOAT="0"IDXID="w8834"BOOK="_idx" COLLECTION="nw41" TIDREF="i1093"ID="FM14922"The Default Directory for SBACKUP Log FilesFILEREF="n40sb33a.tif"PAGENUM=687 ID="BP639"You can create different IDXID="w8835"BOOK="_idx" COLLECTION="nw41" TIDREF="i2187"
directories to log backup or restore sessions done for different types of targets, such as one directory for workstation backups and another for server backups. Or you might want to keep backup logs for different organizational units in different directories.To specify a location, use one or more of the following methods.
MARK=BULLETPress MOREINFO="NONE"<Enter> to accept the default location; then go to IDREF="FM85344"Step 8.Press MOREINFO="NONE"<Insert> to choose from a list of network directories (see IDREF="FM21940"Figure 9-12), choose a directory, and press MOREINFO="NONE"<Esc> to return to the previous window; then go to IDREF="FM85344"Step 8.Backspace over the IDXID="w8836"BOOK="_idx" COLLECTION="nw41" TIDREF="i1093"
path shown (or a portion of the path), then IDXID="w8837"BOOK="_idx" COLLECTION="nw41" TIDREF="i2187"
either type in a IDXID="w8838"BOOK="_idx" COLLECTION="nw41" TIDREF="i962"
new directory or path, or press MOREINFO="NONE"<Insert> to choose from a list; then go to IDREF="FM85344"Step 8.LABEL="9-12" FLOAT="0"ID="FM21940"Specifying a Different Location for Log and Error FilesFILEREF="n40sb34a.tif"PERFORMANCE="REQUIRED"ID="FM85344"From the "Type of Backup" menu 
(IDREF="FM41631"Figure 9-13), choose "Full," "Differential," or "Incremental
" backup.LABEL="9-13" FLOAT="0"ID="FM41631""Type of Backup" MenuFILEREF="n40sb35a.tif"PAGENUM=688 ID="BP640"If you want to customize your backup with include and exclude features, see IDREF="FM92502""Procedures for Custom Backups" on page 692.MARK=BULLETA full backup backs up the entire file system, regardless of whether the data has been changed since the last backup, and clears the modify bit after the backup.If you have installed a migration system built on RTDM, such as Novell's High Capacity Storage System (HCSS), you will have two full backup options: (1) "Full: All of the Target Including Migrated Data" and (2) "Full: All of the Target Except Migrated Data." If you choose to include migrated data, ensure your backup media capacity matches the jukebox media capacity.A differential backup backs up only data that has been changed since the last full backup and leaves the modify bit set after the backup.An incremental backup backs up only data that has been changed since the last full or incremental backup (whichever was last) and clears the modify bit after the backup.For more information on the types of backup, se
e IDREF="FM14384""Backup Types" on page 671.PERFORMANCE="REQUIRED"ID="FM42446"At the "Backup Options" screen (
IDREF="FM82941"Figure 9-14), complete the form.LABEL="9-14" FLOAT="0"ID="FM82941"The "Backup Options" ScreenFILEREF="n40sb36a.tif"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Type a description for the backup session.The description should help you identify the specific backup session so that, if a restore is necessary, you can easily identify the session you need.SBACKUP automatically adds the date, time, number of the media in the media set series, and source (such as the NetWare server or workstation name, but not the volumes, directories, etc.) of the data backed up.PAGENUM=689 ID="BP641"Although no requirements exist for what to enter as the session description, you may want to include the full path of the data, such as SYS:HOME\REPORTS\APRIL.95, which you need to know if a restore session is necessary.PERFORMANCE="REQUIRED"ID="FM97887"(Optional) If your form has an "Append to Previous Session
s on Media" option, specify whether or not to append.The option will appear on your "Backup Options" form only if your device supports appending to previous sessions on the media.Accept the default "No" if you want to label new media, or change the media label and overwrite all sessions on the media. The media rewinds and existing data is overwritten by the next backup.If you want to append this session, press MOREINFO="NONE"<Y> and then MOREINFO="NONE"<MOREINFO="NONE"Enter>. The backup session is appended to the media at the end of the previous session. Each appended session has separate backup and error logs.If you are appending a backup session to a media set (two or more tapes), insert the last tape in the set. If you try to append to a tape other than the last one, you may not be able to restore the data on the later tapes in the set.Labeled media is not considered empty media. There need not be any sessions on the media for you to be able to set the "Append" option to "Yes."Delete the log and error files for any session you overwrite to avoid trying to restore a session that no longer exists.PERFORMANCE="REQUIRED"ID="FM11572"Press 
MOREINFO="NONE"<F10> to save your options and continue with the backup.The "Proceed With The Backup?" box is displayed 
(IDREF="FM36756"Figure 9-15).LABEL="9-15" FLOAT="0"ID="FM36756"Specifying When to Back UpFILEREF="n40sb40a.tif"PAGENUM=690 ID="BP642"PERFORMANCE="REQUIRED"Choose when you want the backup to start, and then go to the step indicated below.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="17*"COLNAME=2 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you choseCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0""No, Return to the Options Form."COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM42446"Step 9, or continue to exit by pressing MOREINFO="NONE"<Esc>.COLNAME=1 ROTATE="0" MOREROWS="0""Start the Backup Now."COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM56074"Step 14COLNAME=1 ROTATE="0" MOREROWS="0""Start the Backup Later."COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM90831"Step 12PERFORMANCE="REQUIRED"ID="FM90831"When the dialog box shown i
n IDREF="FM23971"Figure 9-16 is displayed, set the date and time for the backup to begin.LABEL="9-16" FLOAT="0"ID="FM23971"Specifying the Time for a Delayed BackupFILEREF="n40sb41a.tif"You can choose the default date and time shown for the backup to begin, or you can 
IDXID="w8839"BOOK="_idx" COLLECTION="nw41" TIDREF="i939"
type a new date and tim
e. 
IDXID="w8840"BOOK="_idx" COLLECTION="nw41" TIDREF="i974"
The default is midnight of the current day
.Press 
MOREINFO="NONE"<F1> for help with the format for entering a date and 
IDXID="w8841"BOOK="_idx" COLLECTION="nw41" TIDREF="i4478"
time for the delayed backup.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10>, 
and then press
MOREINFO="NONE" <Enter> to save your changes
.To help safeguard your network, SBACKUP exits when a delayed backup is complete. IDXID="w8842"BOOK="_idx" COLLECTION="nw41" TIDREF="i974"
If the delayed backup session cannot fit on the media, SBACKUP prompts you to insert additional media.If additional media is not inserted, the backup does not finish and SBACKUP does not exit, thus compromising security.PERFORMANCE="REQUIRED"ID="FM56074"(Optional) If you set the "Append t
o Previous Sessions on Media" option to "No" i
n IDREF="FM97887"Step 9b, after the media is mounted enter the media label.
PAGENUM=691 ID="BP643"If you set this option to "No," the data in the current session and the new label you are prompted to enter will overwrite the existing data and label. All previous sessions contained on the media will be lost.Note the media label on the media cartridge so that you can find it easily when SBACKUP asks for it during a restore session.If the media does not have enough empty space to hold the entire backup session, SBACKUP prompts you to insert additional media when the current media is full.SBACKUP breaks the session after completing a file and "spans" the next file to the next media. SBACKUP then copies the media label from the previous one and increments the media number.PERFORMANCE="REQUIRED"(Optional) To abort a backup any time during the session, press 
MOREINFO="NONE"<EscMOREINFO="NONE"> and choose "Yes" from the "Abort Menu."SBACKUP finishes backing up the current data set and then displays a "Dismounting Media" message. Dismounting will take a few minutes.When the media has been dismounted, the "Backup Terminated" message is displayed. Press 
MOREINFO="NONE"<EnterMOREINFO="NONE"> to return to the "Type of Backup" menu.When a backup session is aborted, SBACKUP finishes backing up any files in progress at the time of the abort.PERFORMANCE="REQUIRED"Verify that the backup was successful.When the backup has finished, your screen 
display should look similar to IDREF="FM92688"Figure 9-17.If an error message is displayed, check the error file for more specific information about the backup session.If you have performed a delayed backup, you will not see this screen. For security reasons, SBACKUP exits to the "Main Menu" after a delayed backup.PAGENUM=692 ID="BP644"LABEL="9-17" FLOAT="0"ID="FM92688"The Backup Process Completed (Typical Display)FILEREF="n41sb42a.tif"PERFORMANCE="REQUIRED"To return to the "Main Menu," press 
MOREINFO="NONE"<EnterMOREINFO="NONE"> a
nd then 
MOREINFO="NONE"<MOREINFO="NONE"Esc>.The
MOREINFO="NONE" <Esc> key allows you to exit SBACKUP one screen at a time until you reach the "Main Menu.
" If you want to exit SBACKUP, press 
MOREINFO="NONE"<Esc> once again and answer the confirmatio
n prompt.RENDERAS="SECT2"ID="FM92502"Procedures for Custom BackupsThe following steps detail a single, 
customIDXID="w8843"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"
 backup from beginning to end.A custom backup allows you to specify exactly what you want to back up, such as a server, volume, directory database, workstation, directory, or file. You can even specify subsets of groups.The figures and choices in this section depict choices available to you when using the NetWare 4.1 File System Target Service Agent (TSA410). If you are backing up a workstation or database, rather than a NetWare 4.1 server, your screen displays will vary slightly.SBACKUP displays prompts and messages at the bottom of the screen. For instance, you can press MOREINFO="NONE"<F1> for help at any time.If you are performing a series of backups or restores and need to change your target, follow the procedures in IDREF="FM34972""Changing Targets" on page 749 before proceeding.PAGENUM=693 ID="BP645"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have met the prerequisites detailed in IDREF="FM84714""Prerequisites to Backing Up" on page 682.Ensure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Backup" (IDREF="FM53166"Figure 9-18).LABEL="9-18" FLOAT="0"ID="FM53166"SBACKUP "Main Menu"FILEREF="n40sb20a.tif"PERFORMANCE="REQUIRED"Choose a NetWare server running your backup/restore Target Service Agent (similar to 
IDREF="FM73468"Figure 9-19).
PAGENUM=694 ID="BP646"LABEL="9-19" FLOAT="0"ID="FM73468"List of Servers Available for BackupFILEREF="n40sb31a.tif"If you don't see the 
IDXID="w8844"BOOK="_idx" COLLECTION="nw41" TIDREF="i395"
target
IDXID="w8845"BOOK="_idx" COLLECTION="nw41" TIDREF="i4430"
 you want on the list, check for these possible causes:
MARK=BULLETThe proper Target Service Agent isn't loaded on either the host or the target. (See IDREF="FM71287"Table 9-2 on page 669 for LOAD commands.)The host and target are physically far apart, or network traffic is heavy. In these circumstances, it might take SBACKUP a few moments to detect all of the targets. Press MOREINFO="NONE"<Esc> to return to the "Main Menu," and then press MOREINFO="NONE"<Enter> again. Your target should now be listed.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="17*"COLNAME=2 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Your chosen target has more than one Target Service Agent loaded.COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM93572"Step 3COLNAME=1 ROTATE="0" MOREROWS="0"Your chosen target has only one Target Service Agent loaded.COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM73147"Step 4PERFORMANCE="REQUIRED"ID="FM93572"From the Target Services list (similar t
o IDREF="FM92464"Figure 9-20) choose a target.If the target you ch
ose has more than on
e Target Service Agent loaded, SBACKUP will show you a list o
f their full names.
PAGENUM=695 ID="BP647"IDREF="FM92464"Figure 9-20 shows that the NetWare server named SALES is running the followin
g Target Service Agents:
TYPE="VERT"DOS Workstation (TSADOS)NetWare 2.2 File System (TSA220)NetWare 4.1 Directory (TSANDS)NetWare [4.1] File System (TSA410)OS/2 Workstation (TSAPROXY).LABEL="9-20" FLOAT="0"ID="FM92464"Display of Multiple Target Service Agents on a TargetFILEREF="n41sb39a.tif"PERFORMANCE="REQUIRED"ID="FM73147"Whe
n prompted for the Target username, enter your username as network supervisor (and context if required) for the target.If SBACKUP rejects the supervisor usernam
e you entered, you probably need to include the context of where the user object is located. For example, instead of entering "ADMIN" as the username, enter ".CN=ADMIN.O=
company_name".You must include the context in the username at this point if the usernam
e exists in a directory container that is different from the context set on the server running SBACKUP.PERFORMANCE="REQUIRED"If a password is requested, enter the password for the target.SBACKUP will take a few moments to attach to the 
IDXID="w8846"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
target. Wait for the confirmation bo
x; then press any key to continue.
PAGENUM=696 ID="BP648"PERFORMANCE="REQUIRED"Select the device and medi
a for the bac
kup.MARK=BULLETIf your host has only one storage device attached, SBACKUP selects the device for you and notifies you of the device and media that will be used. Press any key to continue.If your device has more than one storage device attached, choose an available device from those listed.If the device contains media, SBACKUP automatically selects it for the backup.If the storage media does not have a label, SBACKUP displays a message saying that the media cannot be identified. SBACKUP continues but prompts you later to enter the media label.PERFORMANCE="REQUIRED"Specify a location for your session log and error file
s (see IDREF="FM13730"Figure 9-21).LABEL="9-21" FLOAT="0"ID="FM13730"The Default Directory for SBACKUP Log FilesFILEREF="n40sb33a.tif"You can create different IDXID="w8847"BOOK="_idx" COLLECTION="nw41" TIDREF="i1340"
directories to log backup or restore sessions done for different types of targets (such as one directory for workstation backups and another for server backups), for different media series, or for different organizational units.To specify a location, use one or more of the following methods.
MARK=BULLETPress MOREINFO="NONE"<Enter> to accept the default location; then go to IDREF="FM24802"Step 8.Press MOREINFO="NONE"<Insert> to choose from a list of network directories (see IDREF="FM72174"Figure 9-22), choose a directory, and press MOREINFO="NONE"<Esc> to return to the previous window; then go to IDREF="FM24802"Step 8.Backspace over the path shown (or a portion of the path), then IDXID="w8848"BOOK="_idx" COLLECTION="nw41" TIDREF="i2187"
type in a IDXID="w8849"BOOK="_idx" COLLECTION="nw41" TIDREF="i962"
new directory or path; then go to IDREF="FM24802"Step 8.You can also press MOREINFO="NONE"<Insert> during this process to choose existing parts of the path from a list.PAGENUM=697 ID="BP649"LABEL="9-22" FLOAT="0"ID="FM72174"Choosing a Different Location for Log and Error FilesFILEREF="n40sb34a.tif"PERFORMANCE="REQUIRED"ID="FM24802"From the "Type of Backup" menu, choose "Custom Backu
p" (IDREF="FM21643"Figure 9-23).LABEL="9-23" FLOAT="0"ID="FM21643""Type of Backup" MenuFILEREF="n41sb51a.tif"PERFORMANCE="REQUIRED"ID="FM77834"At the "Custom Backup Options" screen (similar t
o IDREF="FM15220"Figure 9-24), complete the form.
PAGENUM=698 ID="BP650"LABEL="9-24" FLOAT="0"IDXID="w8850"BOOK="_idx" COLLECTION="nw41" TIDREF="i395"ID="FM15220""Custom Backup Options" ScreenFILEREF="n41sb23a.tif"At least two levels of help screens are available to you in the "Custom Backup Options" screen. To see help for a specific line item, select the item and press MOREINFO="NONE"<Enter> to get in editing mode, and then press MOREINFO="NONE"<F1>.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Specify what you want to back u
pDo not use the following characters in the "What To Back Up" field: ?/, */, or C:/ */. SBACKUP accepts them but does not back up anything.You can type the path to your target and press MOREINFO="NONE"<Enter>, or press MOREINFO="NONE"<Enter> to see the backup default. If the default is what you want to back up, press MOREINFO="NONE"<Esc> and go to IDREF="FM28495"Step 9b.If you want to see a selection list, press MOREINFO="NONE"<Insert>. A screen similar to IDREF="FM76103"Figure 9-25 is displayed.PAGENUM=699 ID="BP651"LABEL="9-25" FLOAT="0"ID="FM76103""Select" List Screen from "What to Back Up" ScreenFILEREF="n40sb43a.tif"When you press MOREINFO="NONE"<Insert>, the selection list will vary depending on your target. The selections represent the top of each directory structure for either the server, NDS database, or workstation.The "NetWare Server" option backs up the entire server, except the NDS database. If you want the NDS database backed up, you must change your target to "NetWare 4.1 Directory."The "DOS Workstation" or "OS/2 Workstation" will be the default option if either of these is your target. Each one backs up the entire workstation.You can (1) type a path in the box and press MOREINFO="NONE"<Enter>; (2) select an item, press MOREINFO="NONE"<Esc>, and press MOREINFO="NONE"<EnterMOREINFO="NONE">; or (3) continue down the directory structure by pressing MOREINFO="NONE"<EnterMOREINFO="NONE"> until you find a particular branch of the directory to select, then press MOREINFO="NONE"<Esc> and then press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"ID="FM28495"(Optional) Choose 
IDXID="w8851"BOOK="_idx" COLLECTION="nw41" TIDREF="i4325"
subsets of what you are backing up.At the "Custom Backup Options" screen, choose "Subsets of What You Are Backing Up" to see a list of available subsets of the directory structure (similar to IDREF="FM54827"Figure 9-26).The subset options are related to the Target Service Agent on the target to be backed up.PAGENUM=700 ID="BP652"LABEL="9-26" FLOAT="0"ID="FM54827"Subsets of DataFILEREF="n40sb65a.tif"The "Default" setting means that everything in the "What to Back Up" screen (IDREF="FM76103"Figure 9-25) is backed up---nothing specific has been included or excluded.ID="FM52065"To specify subsets of what you are backing up, choose any subset to get an "Exclude..." or "Include..." screen; then use the options at the bottom of the screen to add the subset to the "Exclude..." or "Include..." screen.You can add, delete or modify an entry. For example, to exclude a directory in volume SYS: from the backup(1) From the "Choose Subsets of What You Are Backing Up" screen, choose "Include Major TSA Resources."(2) PressMOREINFO="NONE" <Insert>, choose "Volume SYS:," and press MOREINFO="NONE"<Esc>. (When you press MOREINFO="NONE"<Insert>, a screen similar to IDREF="FM35961"Figure 9-27 is displayed.)(3) Choose "Exclude Directories (Full Path)" and press MOREINFO="NONE"<Insert>.(4) If requested, enter name space type (DOS, FTAM, Macintosh, NFS, or OS/2).(5) Type the full path to the directory, including the volume name. For example, a Macintosh path is "Volume::directory:subdirectory:filename."PAGENUM=701 ID="BP653"LABEL="9-27" FLOAT="0"ID="FM35961"Select a Major Target Service Agent Using Options Listed at the Bottom of the ScreenFILEREF="n41sb52a.tif"The target server's directories and files are not affected by what is specified in the Include or Exclude field.When you are finished, press MOREINFO="NONE"<Esc> or MOREINFO="NONE"<F10> to return to the "Custom Backup Options" screen.PERFORMANCE="REQUIRED"(Optional) Specify how SBACKUP should 
IDXID="w8852"BOOK="_idx" COLLECTION="nw41" TIDREF="i3958"
scan the dat
a to be backed up.Press MOREINFO="NONE"<Enter>. The list of data set items available to scan is displayed, similar to IDREF="FM13894"Figure 9-28.Your screen might appear different, depending on which subsets you chose and which Target Service Agent you are using.The data set contains various types of data, as listed on the screen. You can exclude user account information or types of files and directories (such as hidden files).The default "No" means that nothing will be excluded. If you want to accept the default, press MOREINFO="NONE"<Esc>.If you have installed a migration system built on RTDM, such as Novell's High Capacity Storage System (HCSS), you can choose to exclude the migrated file data in the "How To Scan What You Are Backing Up" field.PAGENUM=702 ID="BP654"LABEL="9-28" FLOAT="0"ID="FM13894"List of Data Set Items for ScanningFILEREF="n41sb25a.tif"If you want to exclude a particular type of data from the backup, move the cursor to the appropriate line, press MOREINFO="NONE"<Enter> to access an edit mode (blinking cursor), and type MOREINFO="NONE""Y." Press MOREINFO="NONE"<Enter> to save the settings. (The "No" is replaced with "Yes.")For information about how SBACKUP scans data, see "BOOK="cncptenu" COLLECTION="nw41"Data set" in Concepts.If you have compressed files or a compressed volume that you might want to restore to a noncompressed volume, choose the "Backup Compressed Files as Expanded Files" option.When all data items are set as you want them to be, press MOREINFO="NONE"<Esc> or MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"Type a description for the backup session.A session description helps you locate a session when you restore data. This description becomes the header for log and error files.SBACKUP automatically records the date and time of the session and the source of the data (such as the server or workstation name), as well as the number of this media in the media set series.Although no mandatory rules exist for what you enter as the session description, you should include the full path of the data (such as SYS:HOME\REPORTS\APRIL.95).PAGENUM=703 ID="BP655"PERFORMANCE="REQUIRED"Specify whether to clear the 
IDXID="w8853"BOOK="_idx" COLLECTION="nw41" TIDREF="i277"
modify bit 

on 
IDXID="w8854"BOOK="_idx" COLLECTION="nw41" TIDREF="i2493"
the selected data after the backup.If you clear the modify bit, these files will not be recognized as having been changed at the time of the next backup, unless they are changed again between this backup and the next one.(For more information, see IDREF="FM14384""Backup Types" on page 671, or see "BOOK="cncptenu" COLLECTION="nw41"Modify bit" and "BOOK="cncptenu" COLLECTION="nw41"Backup" in Concepts.)The default is "No." If the entry in this field is "No," the modify bit is not changed after files are backed up. Files are backed up in the next backup session, even if they were not modified.If you want to reset the modify bit, type "Y" and press MOREINFO="NONE"<Enter>. If the entry in this field is "Yes," the modify bit is cleared after files are backed up.PERFORMANCE="REQUIRED"ID="FM48173"(Optional) If your form has an "Append to Previous Session
s on Media" option, specify whether or not to append.The option will appear on your "Custom Backup Options" form only if your device supports appending to previous sessions on the media.Press MOREINFO="NONE"<Enter> to accept the default "No" if you want to label new media, or change the media label and overwrite all sessions on the media. The media rewinds and existing data is overwritten by the next backup.If you want to append this session, type "Y" and press MOREINFO="NONE"<Enter>. The backup session is appended to the media at the end of the previous session. Each appended session has separate backup and error logs.If you are appending a backup session to a media set (two or more tapes), insert the last tape in the set. If you try to append to a tape other than the last one, you may not be able to restore the data on the later tapes in the set.Labeled media is not considered empty media. There need not be any sessions on the media for you to be able to set the "Append" option to "Yes."Delete the log and error files for any session you overwrite to avoid trying to restore a session that no longer exists.PAGENUM=704 ID="BP656"PERFORMANCE="REQUIRED"When you have finished editing the screen, press 
MOREINFO="NONE"<F10> to save your options and continue.The 
"Proceed With The Backup?
" prompt is displayed
 (IDREF="FM46407"Figure 9-29).LABEL="9-29" FLOAT="0"ID="FM46407"Specifying When to Back UpFILEREF="n40sb40a.tif"PERFORMANCE="REQUIRED"Choose when you want the backup to start
, 
and then go to the step indicated below.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="17*"COLNAME=2 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you choseCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0""No, Return to the Options Form"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM77834"Step 9, or continue to exit by pressing MOREINFO="NONE"<Esc>MOREINFO="NONE".MOREINFO="NONE"COLNAME=1 ROTATE="0" MOREROWS="0""Start the Backup Now"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM20385"Step 14COLNAME=1 ROTATE="0" MOREROWS="0""Start the Backup Later"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM15653"Step 12PERFORMANCE="REQUIRED"ID="FM15653"When the 
"Start the Backup at
" dialog bo
x is displayed
 (IDREF="FM13252"Figure 9-30), set the date and time for the backup to begin.LABEL="9-30" FLOAT="0"ID="FM13252"Specifying When to Start a Delayed BackupFILEREF="n40sb41a.tif"You can choose the default date and time shown for the backup to begin, or you can 
IDXID="w8855"BOOK="_idx" COLLECTION="nw41" TIDREF="i939"
type a new date and tim
e. 
IDXID="w8856"BOOK="_idx" COLLECTION="nw41" TIDREF="i974"
The default is midnight of the current day
.Press 
MOREINFO="NONE"<F1> for help with the format for entering a date and 
IDXID="w8857"BOOK="_idx" COLLECTION="nw41" TIDREF="i4478"
time for the delayed backup.
PAGENUM=705 ID="BP657"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10>, and t
hen pressMOREINFO="NONE" <Enter> to save your changes.To help safeguard your network, SBACKUP exits when a delayed backup is complete. If the delayed backup session cannot fit on the media, SBACKUP prompts you to insert additional media. If additional media is not inserted, the backup does not finish and SBACKUP does not exit, thus compromising security.PERFORMANCE="REQUIRED"ID="FM20385"(Optional) If you set the "Append t
o Previous Sessions on Media" option to "No" (i
n IDREF="FM48173"Step 9f), after the media is mounted enter the media label.If you set "Append to To Previous Sessions on Media" to "No," the data in the current session and the new label you are prompted to enter will overwrite the existing data and label. All previous sessions contained on the media will be lost.If the media does not have enough empty space to hold the entire backup session, SBACKUP will prompt you to insert additional media when the current one is full. SBACKUP will break the session after completing a file and will "span" the next file to the next media. Then SBACKUP will copy the media label from the previous one and increment the media number.PERFORMANCE="REQUIRED"(Optional) To abort a backup session any time during the session, press 
MOREINFO="NONE"<Esc> and choose "Yes" from the "Abort Menu."SBACKUP finishes backing up the current data se
t and then displays a "Dismounting Media" message. Dismounting will take a few minutes.When the media is dismounted, the "Backup Terminated" message is displayed. Press 
MOREINFO="NONE"<Enter> to return to t
he "Type of Backup" menu.When a backup session is aborted, SBACKUP finishes backing up any files in progress at the time of the abort.PERFORMANCE="REQUIRED"Verify that the backup was successful.When the backup has finished, your screen 
display should loo
k similar to IDREF="FM73246"Figure 9-31.PAGENUM=706 ID="BP658"LABEL="9-31" FLOAT="0"ID="FM73246"The Backup Process Completed (Typical Display)FILEREF="n41sb42a.tif"If an error message 
is displa
yed, view the error file for more specific information about the backup session.If you have performed a delayed backup, you will not see this screen. For security reasons, SBACKUP exits to the "Main Menu" after a delayed backup.PERFORMANCE="REQUIRED"To return to the "Main Menu," press 
MOREINFO="NONE"<Enter> an
d then MOREINFO="NONE"<Esc>.The 
MOREINFO="NONE"<Esc> key allows you to exit SBACKUP one screen at a time until you reach the "Main Menu." If you want to exit SBACKUP, press 
MOREINFO="NONE"<Esc> once again and answer the confirmatio
n prompt.To unload SBACKUP and applicable Target Service Agents, see IDREF="FM88278""Unloading SBACKUP Files" on page 751.PAGENUM=707 ID="BP659"RENDERAS="SECT1"Restoring DataRENDERAS="SECT2"Introduction to Restoring DataThis section provides an introduction toTYPE="VERT"Restore sessionsRestore optionsChoosing subsets of data to restoreScanning data setsRestoring to a different locationOverwriting a parent or childRestoring NetWare Directory Services
TMHow Subsets, Scan, and Overwrite Work TogetherRENDERAS="SECT3"Restore SessionsUse SBACKUP to retrieve and reinstate data you have backed up to a storage media. Typically, you would perform a restore if data has been lost or corrupted since the backup was made.A 
restore session restores data from a backup. The restore session produces the requested data, which is retrieved from the storage media and restored to the location you specify. If an IDXID="w8858"BOOK="_idx" COLLECTION="nw41" TIDREF="i1340"
error occurs during the restore session, an error message is appended to the error file on the host server, if an error file exists.The error file is labeled with the same description that you give the backup session (such as "Friday's Full Backup") and is accessed through the "Log/Error File Administration" option of the SBACKUP "Main Menu."The error file might be located in the default directory or in another directory that you specified during the backup or restore session.PAGENUM=708 ID="BP660"RENDERAS="SECT3"Restore OptionsIDXID="w8859"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"ID="FM38079"For a custom restore, you can specify exactly which data to restore. Several options work together to allow you maximum flexibility in your restore session. These options allow you to do the following:TYPE="VERT"Choose subsets of data to restore.Scan what you are restoring.Restore to a different location
.Restore migrated files.Overwrite an existing parent (such as a directory) or child (such as a file).RENDERAS="SECT3"ID="FM63944"Choosing Subsets of Data to RestoreIDXID="w8860"BOOK="_idx" COLLECTION="nw41" TIDREF="i3827"You can choose specific subsets of a backup session to include in or exclude from the restore session by selecting major resources (such as volumes) or minor resources (such as directories, paths, or files).RENDERAS="SECT4"Understanding the Exclude and Include OptionsWhenever you 
perform a custom restore, you can use the exclude and include options to select subsets of what you want to restore.RENDERAS="SECT4"Using ExcludeTo restore IDXID="w8861"BOOK="_idx" COLLECTION="nw41" TIDREF="i1371"
most of the directory structure while omitting only a small part, use the exclude option to omit the part you don't want to restore. Everything that you don't specifically exclude is included.After you exclude part of the directory structure (such as a volume or directory), you cannot include any subdirectories or files beneath that excluded volume or directory.PAGENUM=709 ID="BP661"RENDERAS="SECT4"Using IncludeTo restore a relatively small part of the directory structure, use the include option to specify the data you want. Everything you don't specifically include is excluded.When you select only IDXID="w8862"BOOK="_idx" COLLECTION="nw41" TIDREF="i1774"
part of the directory structure to include (such as a volume), all directories, subdirectories, and files under that selection are included in the restore by default. However, you can specifically exclude some of the subdirectories or files beneath your selection if you need to.IDREF="FM92351"Figure 9-32 illustrates this use of the include option. The figure shows a directory structure with volume SYS: selected as an include option. All other areas of the directory structure will be excluded from the restore.LABEL="9-32" FLOAT="0"ID="FM92351"SBACKUP Include Option: Specific Volume Included, All Others ExcludedFILEREF="n41sb02a.tif"The same principle applies when you specify a directory with the include option. IDREF="FM66739"Figure 9-33 shows that all directories, subdirectories, and files under the NetUsers directory will be included in the restore. All other areas of the directory structure are excluded from the restore.PAGENUM=710 ID="BP662"LABEL="9-33" FLOAT="0"ID="FM66739"SBACKUP Include Option: Specific Directory Included, All Others ExcludedFILEREF="n41sb03a.tif"The reverse is true when you select a major resource, directory, or file as an exclude option. All other areas of the directory structure will be included in the restore.RENDERAS="SECT4"Using Include and Exclude Options TogetherBy IDXID="w8863"BOOK="_idx" COLLECTION="nw41" TIDREF="i1774"
combining the IDXID="w8864"BOOK="_idx" COLLECTION="nw41" TIDREF="i1371"
include and exclude options, you can more precisely control what is restored.For example, the following command sequence results in volume HOME: being included in the restore, with the exception of the MARY directory and the WIDGET.EXE file.FORMAT="LINESPECIFIC"MOREINFO="NONE"Include major TSA resources HOME:
Exclude directories (full path): HOME:NETUSERS/MARY
Exclude path/files HOME:NETUSERS/KARL/PROJECT/WIDGET.EXE
PAGENUM=711 ID="BP663"IDREF="FM15041"Figure 9-34 illustrates this example.LABEL="9-34" FLOAT="0"ID="FM15041"Combining SBACKUP Include and Exclude OptionsFILEREF="n41sb04a.tif"RENDERAS="SECT3"Scanning Data SetsYou can specify different types of data sets to be scanned.A data set is a group of data that can be manipulated by SBACKUP. Each data set in the directory structure can be classified as a parent or a child, and each class includes different types of data items.Within SBACKUP, a IDXID="w8865"BOOK="_idx" COLLECTION="nw41" TIDREF="i3217"
parent might be a server, a volume, or a directory. A IDXID="w8866"BOOK="_idx" COLLECTION="nw41" TIDREF="i629"
child is a file, which is the lowest level of the directory structure.PAGENUM=712 ID="BP664"As shown in IDREF="FM31954"Figure 9-35, the unit below a parent is not necessarily a child; it might be another parent, or the line might end with the parent. The unit above a child must always be a parent.LABEL="9-35" FLOAT="0"ID="FM31954"Parent and Child Levels in a Directory StructureFILEREF="n41sb05a.tif"Items in a data set for either a parent or child should be items that do not frequently change. You may choose to exclude from the restore session one or more of the items in your target's data set.PAGENUM=713 ID="BP665"Data sets can contain different types of data items. IDREF="FM20920"Figure 9-36 shows typical NetWare data sets.LABEL="9-36" FLOAT="0"ID="FM20920"Data Sets Containing Different Types of Data ItemsFILEREF="n40sb15a.tif"RENDERAS="SECT3"Restoring to a Different LocationYou have the option of restoring data to the same location in the directory structure as the backup source, or IDXID="w8867"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"
of restoring data to a new location.To specify a new location, you must specify the full directory path. If the location specified does not exist, SBACKUP will create the new directory structure.RENDERAS="SECT3"PAGENUM=714 ID="BP666"ID="FM98350"Restoring Migrated FilesYou can restore migrated files if you:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Ensure HCSS (or your migration system) is not loaded on the server.Load SBACKUP and restore the migratable directories using SBACKUP while excluding the files from the restore (see IDREF="FM15991"Figure 9-46 on page 728).Load HCSS (or your migration system) at the server console prompt.Return to SBACKUP and restore the migratable files using SBACKUP while including the files in the restore. You can choose to exclude files from the restore by using an option in the "How to Scan the Session to be Restored" screen (see IDREF="FM15991"Figure 9-46 on page 728).RENDERAS="SECT3"ID="FM25391"Overwriting a Parent or ChildIDXID="w8868"BOOK="_idx" COLLECTION="nw41" TIDREF="i402"
SBACKUP IDXID="w8869"BOOK="_idx" COLLECTION="nw41" TIDREF="i629"
allows you to overwrite all IDXID="w8870"BOOK="_idx" COLLECTION="nw41" TIDREF="i3161"
existing IDXID="w8871"BOOK="_idx" COLLECTION="nw41" TIDREF="i3217"
parents or children.It also allows you toIDXID="w8872"BOOK="_idx" COLLECTION="nw41" TIDREF="i3161"
specify that children be overwritten only if the date of the data set on the hard disk is more recent than the date of the data set that was backed up.RENDERAS="SECT3"Restoring NetWare Directory ServicesThe only absolute way to ensure that your IDXID="w8873"BOOK="_idx" COLLECTION="nw41" TIDREF="i2730"
NetWare Directory Services (NDS) database can be fully restored is through partition replication, with replicas of the entire database on multiple servers. For more information on replicas and partitions, and on creating partitions, see IDREF="FM57530"Chapter 5, "Managing the NetWare Directory Tree."Use SBACKUP to IDXID="w8874"BOOK="_idx" COLLECTION="nw41" TIDREF="i2730"
restore the NDSTM database only in the event of a catastrophic data loss where all replicas have become corrupted.PAGENUM=715 ID="BP667"If data has become corrupted, you shouldNUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Delete the corrupted NDS dataAllow time for the deletion to propagate throughout the networkRestore the NDS dataIf the objects are not deleted before the restoration, the NDS database will be corrupted by the old data.RENDERAS="SECT3"How Subsets, Scan, and Overwrite Work TogetherDuring a restore session, SBACKUP reads the backup storage media and the Target Service Agent compares the media data set to the existing hard disk data set. The Target Service Agent evaluates each data set according to the following criteria:MARK=BULLETIs this data set a subset of what is being restored?Is this data set found on the hard disk?Which parts of the data set are subject to restoring?Is this data set a parent or a child, and is the Overwrite parameter set to "Yes," "No," or "Overwrite Only if Newer?"If the parameters for a child are set to "Overwrite Only if Newer," does the backup copy have a more recent date than the existing copy?IDREF="FM71901"Figure 9-37 shows how SBACKUP evaluates data sets before performing a restore.PAGENUM=716 ID="BP668"LABEL="9-37" FLOAT="0"ID="FM71901"ID="FM25934"How SBACKUP Evaluates Data Being RestoredID="FM35417"FILEREF="n41sb16a.tif"PAGENUM=717 ID="BP669"RENDERAS="SECT2"ID="FM59126"Prerequisites to RestoringIDXID="w8875"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"MARK=CHECKBOXUnderstand the entries listed in IDREF="FM79417""Backup and Restore Concepts" on page 654.Understand the SBACKUP rules. (See IDREF="FM63064""Rules for Using SBACKUP" on page 656.)Have network supervisor rights (such as user ADMIN) or equivalent rights to the directories/files you are restoring.If you are restoring to an OS/2 or DOS workstation, know the workstation's password if the Target Service Agent was originally loaded with the "/Password" parameter instead of the "/Trust" parameter, as explained in IDREF="FM91263"Table 9-1 on page 665.Have all required files loaded. (See IDREF="FM71287"Table 9-2 on page 669.)Know the username and password for the target server or workstation to which you want to restore data.Know the session description that you want to restore. You can get this information from your session log and error files. (See IDREF="FM79342""Log and Error Files" on page 733.)For a custom restore, know the directory structure of the data you are restoring. You will be prompted for specific paths and filenames while setting the restore options. (For more information, see IDREF="FM72288""Enhancing Host Server Performance" on page 753.)If you want to restore data to a new IDXID="w8876"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"
location (different from where the original data was located), you must specify the full path to both the original data and the new location. If the new location does not exist, SBACKUP will create a new directory structure.You can get the original path from your backup logbook or from the session log files if you noted the path at the time the backup was performed.PAGENUM=718 ID="BP670"RENDERAS="SECT2"Procedures for a RestoreIDXID="w8877"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"IDXID="w8878"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"
The following steps detail a single restore from beginning to end.The figures and choices in this section depict choices available to you when using the NetWare 4.1 File System Target Service Agent (TSA410). If you are restoring a workstation or database, rather than a NetWare 4.1 server, your screen displays will vary slightly.SBACKUP displays prompts and messages at the bottom of the screen. For instance, you can press MOREINFO="NONE"<F1> for help at any time.For field-specific help, use the arrow keys to move the cursor to the field you want, press MOREINFO="NONE"<Enter>, then press MOREINFO="NONE"<F1>.If you are performing a series of restores and need to change your target, follow the procedures in IDREF="FM34972""Changing Targets" on page 749 before proceeding.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have met the prerequisites detailed in IDREF="FM59126""Prerequisites to Restoring" on page 717.Ensure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.PAGENUM=719 ID="BP671"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"ID="FM63305"From the SBACKUP "Main Menu," choose "Restore" (IDREF="FM43147"Figure 9-38).LABEL="9-38" FLOAT="0"ID="FM43147"SBACKUP "Main Menu"FILEREF="n40sb27a.tif"PERFORMANCE="REQUIRED"Choose a NetWare server running your backup/restore Target Services (similar t
o IDREF="FM78889"Figure 9-39).LABEL="9-39" FLOAT="0"ID="FM78889"List of Servers Available as Targets (Running Target Services)FILEREF="n40sb31a.tif"PAGENUM=720 ID="BP672"If you don't see the target
IDXID="w8879"BOOK="_idx" COLLECTION="nw41" TIDREF="i4430"
 you want on the list, check for these possible causes:
MARK=BULLETThe proper Target Service Agent isn't loaded on either the host or the target. (See IDREF="FM71287"Table 9-2 on page 669 for loading instructions.)The host and target are physically far apart, or network traffic is heavy. In these circumstances, it might take SBACKUP a few moments to detect all of the targets. Press MOREINFO="NONE"<Esc> to return to the "Main Menu," and then press MOREINFO="NONE"<Enter> again. Your target should now be listed.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="17*"COLNAME=2 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Your chosen target has more than one Target Service Agent loadedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM20316"Step 3COLNAME=1 ROTATE="0" MOREROWS="0"Your chosen target has only one Target Service Agent loadedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM47714"Step 4PERFORMANCE="REQUIRED"ID="FM20316"From the Target Services lis
t (similar t
o IDREF="FM40765"Figure 9-40), choose a target.If the target you choose has more than on
e Target Service Agent loaded, SBACKUP will show you a list o
f their full names.IDREF="FM40765"Figure 9-40 shows that the NetWare server named SALES is running the followin
g Target Service Agents:
TYPE="VERT"DOS Workstation (TSADOS)NetWare 2.2 File System (TSA220)NetWare 4.1 Directory (TSANDS)NetWare [4.1] File System (TSA410)OS/2 Workstation (TSAPROXY).PAGENUM=721 ID="BP673"LABEL="9-40" FLOAT="0"ID="FM40765"Display Multiple Target Service Agents on a TargetFILEREF="n41sb39a.tif"You ca
n restore data to any of these environments.PERFORMANCE="REQUIRED"ID="FM47714"Whe
n prompted for the Target username, enter your username (and context if required) as network supervisor for the target.I
f SBACKUP rejects the supervisor usernam
e you entered, you probably need to include the context of where the user object is located. For example, instead of entering "ADMIN" as the username, enter ".CN=ADMIN.O=
company_name".You must include the context in the username at this point if the usernam
e exists in a directory container that is different from the context set on the server running SBACKUP.PERFORMANCE="REQUIRED"If a password is requested, enter the password for the target.SBACKUP will take a few moments to attach to the 
IDXID="w8880"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
target. Wait for the confirmation bo
x; then press any key to continue.
PAGENUM=722 ID="BP674"PERFORMANCE="REQUIRED"ID="FM49218"From the "Restore Menu," selec
t a restore option
, using the 
information in the following tabl
e to make your choice.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="14*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Choose one of the followingCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Select "Choose a Session to Restore" if you want to select a session from a list of session log headers.COLNAME=2 ROTATE="0" MOREROWS="0"Go to IDREF="FM95780"Step 6a.COLNAME=1 ROTATE="0" MOREROWS="0"Select "Restore Without Session Files" if you need to select a session directly from the backup media. This is necessary when log and error files are corrupted or accidentally deleted.COLNAME=2 ROTATE="0" MOREROWS="0"Go to IDREF="FM76326"Step 7 (Later in the restore session, SBACKUP will display session headers that you can accept or reject one at a time.)PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM95780"When the prompt shown in IDREF="FM64612"Figure 9-41 is displayed, specify the path to the session log file of the session you want to restore.LABEL="9-41" FLOAT="0"ID="FM64612"Specify the Path to the Backup SessionFILEREF="n40sb49a.tif"To specify a path, use one or more of the following methods.MARK=BULLETPress MOREINFO="NONE"<Enter> to accept the default; then go to IDREF="FM89321"Step 6b.Press MOREINFO="NONE"<Insert> to choose from a list of directories, press MOREINFO="NONE"<Esc> to return to the previous window, and then go to IDREF="FM89321"Step 6b.Backspace over the IDXID="w8881"BOOK="_idx" COLLECTION="nw41" TIDREF="i1093"
path shown (or a portion of the path), IDXID="w8882"BOOK="_idx" COLLECTION="nw41" TIDREF="i2185"
type in a IDXID="w8883"BOOK="_idx" COLLECTION="nw41" TIDREF="i962"
new directory or path, and then go to IDREF="FM89321"Step 6b.Press MOREINFO="NONE"<Insert> anytime during this process to choose parts of the existing path from a list.PAGENUM=723 ID="BP675"PERFORMANCE="REQUIRED"ID="FM89321"When a list of sessions is displayed (similar t
o IDREF="FM30817"Figure 9-42), choose the one you want to restore, and 
then skip t
o IDREF="FM74937"Step 8.Don't restore an NDS session from a tape backup session unless all replicas have been corrupted.LABEL="9-42" FLOAT="0"ID="FM30817"Specifying Sessions to RestoreFILEREF="n40sb50a.tif"PERFORMANCE="REQUIRED"ID="FM76326"If you are restoring without session files, set the location of log and error files.You can use one or more of the following methods.
MARK=BULLETPress MOREINFO="NONE"<Enter> to accept the location; then go to IDREF="FM74937"Step 8.Press MOREINFO="NONE"<Insert> to choose from a list of network directories, choose a directory, press MOREINFO="NONE"<Esc> to return to the previous window, and then go to IDREF="FM74937"Step 8.Backspace over the path shown (or a portion of the path), then IDXID="w8884"BOOK="_idx" COLLECTION="nw41" TIDREF="i2185"
type in a new directory or path, and then go to IDREF="FM74937"Step 8.Press 
MOREINFO="NONE"<Insert> anytime during this process to choose parts of the existing path from a list.PERFORMANCE="REQUIRED"ID="FM74937"Press any key to see your selection of device and media, and decide where you want to restore from.If the media on which the data resides is not loaded on the device you choose, you will be prompted to insert the correct media.PAGENUM=724 ID="BP676"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If a list of devices and media is displayed, choose the one containing the session you want to restore.PERFORMANCE="REQUIRED"If only one device is attached, a message is displayed indicating the default device and media. Press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"ID="FM82972"From the "Restoring From 
Backup_Session_Name" screen, choose the type of restore 
you want, and then go to the step indicated on the following table.TSA410 backs up files in compressed or uncompressed format, as specified by the user. However, if you try to restore a compressed file to a volume without compression, the file is corrupted and no error message is given.If you have installed a migration system built on RTDM (such as HCSS) and need to restore data after a catastrophic data loss, refer to the steps in IDREF="FM98350""Restoring Migrated Files" on page 714, and then choose "Perform a Custom Restore" and specify when to exclude and include files in the "Subsets of the Session to be Restored" field.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="16*"COLNAME=2 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you selectCOLNAME=2 ROTATE="0" MOREROWS="0"Then go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0""Restore One File or Directory"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM75287"Step 10COLNAME=1 ROTATE="0" MOREROWS="0""Restore an Entire Session"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM37712"Step 11COLNAME=1 ROTATE="0" MOREROWS="0""Perform a Custom Restore"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM45825"Step 12PERFORMANCE="REQUIRED"ID="FM75287"To restore one file or directory, complete the form in the "Restore Options" screen 
(IDREF="FM18704"Figure 9-43).LABEL="9-43" FLOAT="0"ID="FM18704"Restore Options when Restoring One File or DirectoryFILEREF="n41sb01a.tif"PAGENUM=725 ID="BP677"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM35824"To restore one file(1) Enter the exact name at "Name of file."(2) Enter the full path to the file, including directory and volume names.(3) Skip the "Include Subdirectories" line.PERFORMANCE="REQUIRED"To restore one directory(1) Skip the "Name of file" line.(2) Enter the full directory path, including volume name.(3) Specify whether or not to include subdirectories.PERFORMANCE="REQUIRED"ID="FM58580"(Optional) To restore to a new locatio
n, enter the full path to the target directory, including the volume name
.(1) Enter the full directory path, including volume name, to the new location (a location different from where the data was backed up). For example, type "Volume:/directory/directory."If the new location you are restoring to is a IDXID="w8885"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"
different NetWare server:(1) Back up the data from the server where it resides(2) Exit to the "Main Menu"(3) Choose "Change Target to Back Up From or Restore To" to change your target to the server you want to restore the data to.PERFORMANCE="REQUIRED"Enter the nam
e space for the nam
e space format you used when entering the file or directory name.The name space allows SBACKUP to correctly interpret the path information entered earlier in this menu in either the directory field or the location field.If files are restored to a new location, the name spaces must be the same or an error message will occur.You can only restore to a new location in the name space that is supported by the drive you are restoring to.On an HPFS drive you can only rename in the OS/2 name space, and on a "fat file" system you can only rename in the DOS name space. However, SBACKUP displays both in the log file when only one is valid.The supported name spaces are DOS, FTAM, Macintosh, NFS, and OS/2.PAGENUM=726 ID="BP678"SBACKUP provides a list of the name spaces currently loaded on the target you are restoring to.For example, if restoring to a new Macintosh location, enter a path formatted like "SYS::TEST:MONDAY," then enter "Macintosh" as your name space.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to begin the restore.PERFORMANCE="REQUIRED"At the "Proceed With the Restore?" prompt, choose "Yes." Skip to IDREF="FM46037"Step 13.PERFORMANCE="REQUIRED"ID="FM37712"To restore an entire session, at the "Proceed With the Restore?" prompt, choose "Yes." Skip to IDREF="FM46037"Step 13.PERFORMANCE="REQUIRED"ID="FM45825"To perform a custom restore, at the "Restore Options" screen 
(IDREF="FM15057"Figure 9-44), complete the form.LABEL="9-44" FLOAT="0"ID="FM15057""Restore Options" ScreenFILEREF="n41sb28a.tif"At least two levels of help screens are available to you while you are in the "Restore Options" screen. To see help for a specific line item, select the item, press MOREINFO="NONE"<Enter> to get in editing mode, then press MOREINFO="NONE"<F1>.For more information on a specific option, see IDREF="FM38079""Restore Options" on page 708.PAGENUM=727 ID="BP679"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"(Conditional) If you want to restore a subset of a backup session only, choose "Subsets of the Session to be Restored" and 
then edit the form (similar to IDREF="FM74283"Figure 9-45).The screen lists major and minor resources. The word "DEFAULT" indicates that none of that type of subset has been specified. To specify a subset(1) Choose any item on the screen.(2) Edit the "Include" or "Exclude" screen using MOREINFO="NONE"<Insert>, MOREINFO="NONE"<Delete> and/or MOREINFO="NONE"<Enter>MOREINFO="NONE".(3) Press MOREINFO="NONE"<F10> to save your changes.LABEL="9-45" FLOAT="0"ID="FM74283"Subsets of a SessionFILEREF="n41sb30a.tif"For more information about major and minor resources, see "BOOK="cncptenu" COLLECTION="nw41"Major resource" in Conceptsand "BOOK="cncptenu" COLLECTION="nw41"Minor resource" in Concepts.You can IDXID="w8886"BOOK="_idx" COLLECTION="nw41" TIDREF="i1774"
include or IDXID="w8887"BOOK="_idx" COLLECTION="nw41" TIDREF="i1371"
exclude any or all items listed. For more information about including and excluding items, see IDREF="FM63944""Choosing Subsets of Data to Restore" on page 708.PERFORMANCE="REQUIRED"(Conditional) If you want to exclude certain types of data from the restore, choose "How to Scan the Session to be Restored" and then edit the form (similar to IDREF="FM15991"Figure 9-46).The backed-up data set contains the various types of data items listed on the screen. By default, all types of data items are included in the restore.PAGENUM=728 ID="BP680"LABEL="9-46" FLOAT="0"ID="FM15991"Scanning a SessionFILEREF="n41sb29a.tif"If you want to exclude any item, highlight it, type "Y," and press MOREINFO="NONE"<Enter> to save your changes. Press MOREINFO="NONE"<F10> when you are finished editing the form.If you have installed a migration system built on RTDM, such as Novell's High Capacity Storage System (HCSS) and you have already restored your HCSS directory and choose to include migrated files in the restore, choose "Include File Data From Secondary Storage" and change the "No" to "Yes."PERFORMANCE="REQUIRED"(Optional) To restore data to a different workstation or location
 on a 
IDXID="w8888"BOOK="_idx" COLLECTION="nw41" TIDREF="i3828"
different NetWare server,(1) Back up the data from the server where it resides.(2) Exit to the "Main Menu."(3) Choose "Change Target to Back Up From or Restore To" to change your target to the server you want to restore the data to. (See IDREF="FM34972""Changing Targets" on page 749.)PERFORMANCE="REQUIRED"ID="FM14313"(Optional) To restore data to a different workstation or location within the backed-up server's directory structure, use the following procedures.PAGENUM=729 ID="BP681"Some important rules about restoring to a new location:(1) When you specify a particular portion of the directory structure as the source location, it does not necessarily mean that this will be the only data restored. You can influence what is restored by using the "Include" and "Exclude" options on the "Choose Subsets Of What You're Restoring" screen.(2) You can only restore to a new location in the name space that is supported by the drive you are restoring to.(3) On an HPFS drive you can only rename in the OS/2 name space, and on a "fat file" system you can only rename in the DOS name space. However, SBACKUP displays both in the log file when only one is valid.(4) If you do not want to overwrite any subdirectories that might exist in the area you have included, you must specifically exclude them by their full path.To restore to a new location,(1) Select the option, type "Y" and press MOREINFO="NONE"<Insert>.(2) Enter the full directory path of the source, including the volume name.(3) Enter the full directory path to the new destination.(4) Press MOREINFO="NONE"<Esc> to save your changes.The NetWare Directory Services Target Service Agent (TSANDS) does not support restoration of data to a different area of the directory structure.PAGENUM=730 ID="BP682"PERFORMANCE="REQUIRED"Specify whether or not to overwrite the existing parent or child.A IDXID="w8889"BOOK="_idx" COLLECTION="nw41" TIDREF="i3217"
parent might be a server, a volume, or a directory. A IDXID="w8890"BOOK="_idx" COLLECTION="nw41" TIDREF="i629"
child is a file, which is the lowest level of the directory structure.Use the table below to help you decide.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="14*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"You want to overwrite the parent or child that exists on the hard disk, regardless of whether the existing version or the backed-up version has the latest dateCOLNAME=2 ROTATE="0" MOREROWS="0"Accept the "Yes" default for parent or child or both.COLNAME=1 ROTATE="0" MOREROWS="0"You don't want to overwrite the parent or child that exists on the hard disk, regardless of whether the existing version or the backed-up version has the latest dateCOLNAME=2 ROTATE="0" MOREROWS="0"Select the option (parent or child or both), type MOREINFO="NONE""N" and press MOREINFO="NONE"<Enter>.COLNAME=1 ROTATE="0" MOREROWS="0"You want to overwrite the child that exists on the hard disk only if the date of the backed-up copy on the media is later than the date of the copy on the hard diskCOLNAME=2 ROTATE="0" MOREROWS="0"Highlight "Overwrite Existing Child," press MOREINFO="NONE"<Enter>, and choose the option.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to save your changes and begin the restor
e.PERFORMANCE="REQUIRED"At the 
"Proceed With The Restore?
" prompt, press 
MOREINFO="NONE"<Enter>MOREINFO="NONE".Three windows are displayed.PERFORMANCE="REQUIRED"ID="FM46037"(Conditional) If you selected "Restore Without Session Files" earlier 
(IDREF="FM49218"Step 6), select a session
 now.Although this method of selecting a session (selecting it directly from the media) is more time consuming, it is useful when log and error files are corrupted or deleted for some reason.Don't restore an NDS session from a tape backup session unless all replicas have been corrupted.PAGENUM=731 ID="BP683"SBACKUP goes through the media and displays the session headers one at a time
, prompting you to specify whether to restore the displayed session or skip to the next session (assuming other sessions have been appended).Use the table below to assist you.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The session you want is displayedCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Yes, Restore This Session" to begin the restore. After a short delay (perhaps as much as a few minutes) the ongoing status is displayed in the windows. Go to IDREF="FM95391"Step 14.COLNAME=1 ROTATE="0" MOREROWS="0"The session you want is not displayedCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "No, Go On to the Next Session on the Media," and repeat this step until the session you want is displayed.COLNAME=1 ROTATE="0" MOREROWS="0"You want to quit the restore sessionCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "No, Quit Restore." The "Restoring From Backup_Session_Name" screen displays. Go back to IDREF="FM82972"Step 9 or continue to exit SBACKUP by pressing MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"ID="FM95391"(Optional) To abort a restore sessio
n after choosing "Yes, Restore This Session," press 
MOREINFO="NONE"<Esc> and choose "Yes" from the "Abort Menu."SBACKUP finishes restoring the current data set, then displays a "Dismounting Media" message. Dismounting might take a few minutes.When the media is dismounted, the "Restore Terminated" message is displayed. Press 
MOREINFO="NONE"<Enter> and the "Restore Menu" is displayed
.PAGENUM=732 ID="BP684"PERFORMANCE="REQUIRED"Verify that the restore was successful.When the restore has finished, your screen 
display should loo
k similar to IDREF="FM63188"Figure 9-47.LABEL="9-47" FLOAT="0"ID="FM63188"The Restore Process Completed (Typical Display)FILEREF="n41sb64a.tif"PERFORMANCE="REQUIRED"To return to the "Main Menu," press 
MOREINFO="NONE"<Enter> an
d then MOREINFO="NONE"<Esc>.The 
MOREINFO="NONE"<Esc> key allows you to exit SBACKUP one screen at a time until you reach the "Main Menu." If you want to exit SBACKUP, press 
MOREINFO="NONE"<Esc> once again and answer the confirmatio
n prompt.To unload SBACKUP and applicable Target Service Agents, seeIDREF="FM88278""Unloading SBACKUP Files" on page 751.PAGENUM=733 ID="BP685"RENDERAS="SECT1"ID="FM79342"ID="FM96031"ID="FM63704"Log and Error FilesRENDERAS="SECT2"Introduction to Log and Error FilesSBACKUP generates IDXID="w8891"BOOK="_idx" COLLECTION="nw41" TIDREF="i397"
a log file and an error file IDXID="w8892"BOOK="_idx" COLLECTION="nw41" TIDREF="i1340"
each time a backup session is performed and records information in these files specifically about the session.SBACKUP 
also creates a IDXID="w8893"BOOK="_idx" COLLECTION="nw41" TIDREF="i2187"
default IDXID="w8894"BOOK="_idx" COLLECTION="nw41" TIDREF="i962"
directory (such as IDXID="w8895"BOOK="_idx" COLLECTION="nw41" TIDREF="i4416"
SYS:SYSTEM/TSA/LOG) for the log and error files. If you prefer, you can create any directory for the log and error files before the backup session or restore session, as long as it resides on the host server.You might want to create individual log directories for the different types of backup or restore session targets or different organizational units. For example, you could create one directory for workstation backups and another for server backups.SBACKUP keeps a list of all the log and error files. These lists showMARK=BULLETThe description you enter for the sessionThe date and time the session was begun or, in the case of a delayed backup session, the time the session was scheduledThe name of the target the data was backed up fromRENDERAS="SECT3"The Log FileThe IDXID="w8896"BOOK="_idx" COLLECTION="nw41" TIDREF="i2187"
log 
file is created on the host the first time a particular set of data is backed up. This log containsMARK=BULLETThe session date and time, and the description you enteredThe target from which the data was backed upMedia set identification informationThe area of the directory structure that was backed up (such as the volume name, directory name, etc.)The names of files that were backed upThe numerical location of the data on the storage mediaPAGENUM=734 ID="BP686"RENDERAS="SECT3"The Error FileThe IDXID="w8897"BOOK="_idx" COLLECTION="nw41" TIDREF="i1340"
error 
file is created on the host the first time a particular set of data is backed up. It contains a list of any errors that occurred during a backup or restore session.This file containsMARK=BULLETThe session date and time, and the description you enteredThe target from which the data was backed upMedia set identification informationThe area of the directory structure that was backed upThe total number of parents and children that were backed upThe names of files that were not backed up, along with any error messages or informationSkipped data sets (any file that is opened when a backup session begins is not backed up and is listed as a skipped data set, unless opened in a read-only mode)RENDERAS="SECT2"ID="FM95479"Viewing a Log FileIDXID="w8898"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.PAGENUM=735 ID="BP687"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Log/Error File Administration." The menu shown in IDREF="FM70257"Figure 9-48 is displayed.LABEL="9-48" FLOAT="0"ID="FM70257""Log/Error File Administration" MenuFILEREF="n41sb06a.tif"PERFORMANCE="REQUIRED"ID="FM96582"Choose "View a Log File."PERFORMANCE="REQUIRED"If necessary, set the location of 
the log and error files.If you have already set the location, go t
o IDREF="FM30805"Step 4.To set the location, use one or more of the following methods.
MARK=BULLETPress MOREINFO="NONE"<Enter> to accept the default location, and then go to IDREF="FM30805"Step 4.Press MOREINFO="NONE"<Insert> to choose from a list of network directories, choose a directory, and press MOREINFO="NONE"<Esc> to return to the previous window; then go to IDREF="FM30805"Step 4.Backspace over the path shown (or a portion of the path), then type in a new directory or path, and go to IDREF="FM30805"Step 4.You can also press MOREINFO="NONE"<Insert> during this process to choose existing parts of the path from a list.PERFORMANCE="REQUIRED"ID="FM30805"From the list presented, choose the log file you want to view.A backup log is displayed, similar to the log 
shown i
n IDREF="FM45059"Figure 9-49.PAGENUM=736 ID="BP688"LABEL="9-49" FLOAT="0"ID="FM45059"Sample Backup Log for Weekly Full BackupFILEREF="n41sb07a.tif"Use the Up- and Down-arrow keys to view the file, and 
the MOREINFO="NONE"<Ctrl>+<PageUp> or 
MOREINFO="NONE"<Ctrl>+<PageDown> 
keys to get to the top or bottom of the file.The backup log displays all supported nam
e space types. The DOS nam
e space is the first in the group. A right angle bracket (>) appears next to the file's creator name-space type.If you have linked UNIX files, SBACKUP retains both symbolic and hard 
IDXID="w8899"BOOK="_idx" COLLECTION="nw41" TIDREF="i2124"
links created under the 
IDXID="w8900"BOOK="_idx" COLLECTION="nw41" TIDREF="i2585"
NFS name-space type, but links are not listed in the backup log. Restoring the original file restores associated links.PERFORMANCE="REQUIRED"To return to the "Main Menu," press 
MOREINFO="NONE"<Enter> an
d then MOREINFO="NONE"<Esc>.The
MOREINFO="NONE" <Esc> key allows you to exit SBACKUP one screen at a time until you reach the "Main Menu." If you want to exit SBACKUP, press 
MOREINFO="NONE"<Esc> once again and answer the confirmatio
n prompt.To unload SBACKUP and applicable Target Service Agents, see IDREF="FM88278""Unloading SBACKUP Files" on page 751.PAGENUM=737 ID="BP689"RENDERAS="SECT2"ID="FM11640"Viewing an Error FileIDXID="w8901"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"IDXID="w8902"BOOK="_idx" COLLECTION="nw41" TIDREF="i1340"An error file records any errors that occurred during the backup or restore session.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Log/Error File Administration."The "Log/Error File Administration" menu is displayed
 (IDREF="FM77420"Figure 9-50).LABEL="9-50" FLOAT="0"ID="FM77420""Log/Error File Administration" MenuFILEREF="n41sb06a.tif"PERFORMANCE="REQUIRED"ID="FM77639"Choose "View an Error File."
PAGENUM=738 ID="BP690"PERFORMANCE="REQUIRED"If necessary, set the location of log and error files.If you have already set the location, go t
o IDREF="FM11348"Step 4.To set the location, use one or more of the following methods.
MARK=BULLETPress MOREINFO="NONE"<Enter> to accept the default location, and then go to IDREF="FM11348"Step 4.Press MOREINFO="NONE"<Insert> to choose from a list of network directories, choose a directory, and press MOREINFO="NONE"<Esc> to exit; then go to IDREF="FM11348"Step 4.Backspace over the path shown (or a portion of the path), and type a new directory or path; then go to IDREF="FM11348"Step 4.You can also press MOREINFO="NONE"<Insert> during this process to choose existing parts of the path from a list.PERFORMANCE="REQUIRED"ID="FM11348"From the list presented, choose the error file you want to view.An error file is displayed, similar to the file shown i
n IDREF="FM70971"Figure 9-51.LABEL="9-51" FLOAT="0"ID="FM70971"Sample Error File for Weekly Full BackupFILEREF="n41sb08a.tif"Use the Up- and Down-arrow keys to view the file, and 
the MOREINFO="NONE"<MOREINFO="NONE"Ctrl>+<PageUp> or 
MOREINFO="NONE"<Ctrl>+<PageDown> 
keys to get to the top or bottom of the file.
PAGENUM=739 ID="BP691"IDXID="w8903"BOOK="_idx" COLLECTION="nw41" TIDREF="i3827"IDXID="w8904"BOOK="_idx" COLLECTION="nw41" TIDREF="i1340"
Restore errors are appended to a session's backup error file. A "Restore Session Begins" message marks the beginning of the restore errors, if any exist.If you have linked UNIX files, symbolic and hard 
IDXID="w8905"BOOK="_idx" COLLECTION="nw41" TIDREF="i2124"
links created under the 
IDXID="w8906"BOOK="_idx" COLLECTION="nw41" TIDREF="i2585"
NFS name-space type can fail to be restored if the path name is not recognized. When this happens, the error file contains messages similar to the following:
MOREINFO="NONE"Error restoring name space specific information of "XXXX:tmp/hosts" in NFS name space, error 0x7!MOREINFO="NONE"Unable to allocate directory handle for "XXXX:tmp/test"!PERFORMANCE="REQUIRED"When you are finished viewing the file, press 
MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"To return to the "Main Menu," pres
s MOREINFO="NONE"<MOREINFO="NONE"EscMOREINFO="NONE"> three times
.The 
MOREINFO="NONE"<Esc> key allows you to exit SBACKUP one screen at a time until you reach the "Main Menu." If you want to exit SBACKUP, press 
MOREINFO="NONE"<Esc> once again and answer the confirmatio
n prompt.To unload SBACKUP and applicable Target Service Agents, see IDREF="FM88278""Unloading SBACKUP Files" on page 751.RENDERAS="SECT2"Setting Location of Log and Error FilesIDXID="w8907"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"Every time you do a backup or restore, you are required to set a location (or directory path) for the log and error files.You can either set the location when requested in the backup or restore procedures, or you can use the following method prior to beginning the backup or restore procedures.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)PAGENUM=740 ID="BP692"Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Log/Error File Administration."The "Log/Error File Administration" menu is displayed
.PERFORMANCE="REQUIRED"ID="FM83086"Choose "Set Location of Log and Error Files," and set the location.To set the location, use one or more of the following methods.
MARK=BULLETPress MOREINFO="NONE"<Enter> to accept the default location, and then press MOREINFO="NONE"<Esc> to return to the "Main Menu."Press MOREINFO="NONE"<Insert> to choose from a list of network directories, choose a directory, and press MOREINFO="NONE"<Esc> twice to return to the "Main Menu."Backspace over the path shown (or a portion of the path), type a new directory or path, press MOREINFO="NONE"<Enter>, and then press MOREINFO="NONE"<Esc> to return to the "Main Menu."You can also press MOREINFO="NONE"<Insert> during this process to choose existing parts of the path from a list.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> when finished to return to the "Main Menu."RENDERAS="SECT2"ID="FM96305"ID="FM27566"Deleting the Log Files for Overwritten SessionsSBACKUPIDXID="w8908"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"
 allows IDXID="w8909"BOOK="_idx" COLLECTION="nw41" TIDREF="i3161"
you to IDXID="w8910"BOOK="_idx" COLLECTION="nw41" TIDREF="i402"
overwrite sessions and reuse IDXID="w8911"BOOK="_idx" COLLECTION="nw41" TIDREF="i2187"
storage media.When you delete the log file for a session, using the following procedures, you automatically delete the corresponding error file as well.To prevent outdated IDXID="w8912"BOOK="_idx" COLLECTION="nw41" TIDREF="i3161"
session information from taking up disk space and to help prevent confusion when you select sessions to view or restore, delete the session log files of any sessions that have been overwritten.PAGENUM=741 ID="BP693"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Log/Error File Administration."The "Log/Error File Administration" menu is displayed.PERFORMANCE="REQUIRED"Choose "View a Log File."PERFORMANCE="REQUIRED"If you have not set the location of log and error files, do so now.You can use one or more of the following methods.
MARK=BULLETPress MOREINFO="NONE"<Enter> to accept the default location; and then go to IDREF="FM92726"Step 4.Press MOREINFO="NONE"<Insert> to choose from a list of directories, choose a directory, and pressMOREINFO="NONE" <Esc> to return to the previous window; then go to IDREF="FM92726"Step 4.Backspace over the path shown (or a portion of the path), and type a new directory or path; then go to IDREF="FM92726"Step 4.You can also press 
MOREINFO="NONE"<Insert> during this process to choose existing parts of the path from a list.PERFORMANCE="REQUIRED"ID="FM92726"Select the description of the session that you have overwritten (or plan to overwrite) and press 
MOREINFO="NONE"<Delete>.To delete several session files at once
, select each one
, using 
MOREINFO="NONE"<F5>; t
hen, when finished marking, pressMOREINFO="NONE" <Delete>.A confirmatio
n prompt is displayed.
PAGENUM=742 ID="BP694"PERFORMANCE="REQUIRED"To delete the 
IDXID="w8913"BOOK="_idx" COLLECTION="nw41" TIDREF="i402"
log and error file for that session, choose "Yes."PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> when finished to return to the "Main Menu."RENDERAS="SECT1"ID="FM35978"Storage Device AdministrationYou can see a list of available storage devices by choosing "Storage Device Administration" from the SBACKUP "Main Menu." For each listed device, you can access the following information, using the options listed at the bottom of the screen:MARK=BULLETViewing media listsChecking status of a deviceChecking status of media in a deviceMedia utilitiesRenaming a storage deviceManaging storage mediaRENDERAS="SECT2"Viewing Media ListsIDXID="w8914"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"This option lists the available media for the highlighted device, and provides the location and media name.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.PAGENUM=743 ID="BP695"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Storage Device Administration."The "List of Devices" screen is displayed.PERFORMANCE="REQUIRED"Select one device name, and press 
MOREINFO="NONE"<Insert>.If a message is displayed saying that no media is in the device, but you know that there is, return to the device list and press 
MOREINFO="NONE"<Enter>. This will force the media to be read.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> when finished to return to the "Main Menu."RENDERAS="SECT2"Checking Status of a DeviceIDXID="w8915"BOOK="_idx" COLLECTION="nw41" TIDREF="i396"IDXID="w8916"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Storage Device Administration."The "List of Devices" screen is displayed.
PAGENUM=744 ID="BP696"PERFORMANCE="REQUIRED"Select one device, and press 
MOREINFO="NONE"<Tab>.The "Status of: 
Device_Name" screen is displayed, listing the following:
MARK=BULLETCurrent operation: This option indicates whether the device is currently reading, writing, formatting the media, or none of these.Device mode: This option indicates whether the device is selected for reading, writing, or both.Maximum capacity: This option indicates total storage capacity of the media currently in the device.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> when you are finished to return to the "Main Menu."RENDERAS="SECT2"ID="FM44682"Checking Status of Media in a DeviceIDXID="w8917"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"IDXID="w8918"BOOK="_idx" COLLECTION="nw41" TIDREF="i398"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Storage Device Administration."The "List of Devices" screen is displayed.PERFORMANCE="REQUIRED"Select one device name, and press 
MOREINFO="NONE"<Insert>.The "Media for: 
Device_Name" screen is displayed, listing the names of any media in the device you selected.
PAGENUM=745 ID="BP697"If, instead, a message is displayed saying that no media is in the device, but you know that there is, return to the device list and press 
MOREINFO="NONE"<Enter>. This will force the media to be read.PERFORMANCE="REQUIRED"Select one media name, and press 
MOREINFO="NONE"<Tab>.The "Status of: 
Media_Name" screen is displayed, listing the following:
MARK=BULLETMedia owner: If the media in the device is blank or if it was written to in a data format other than SIDF, the owner is listed as "Unidentified."If the media is written by an SIDF application, the media owner is not displayed on the status screen.Number in media set: This number indicates the sequential number of this media within a particular media set.SBACKUP automatically labels and appends an incrementing number to any backup sessions that spans multiple media.Creation time: This shows the time that the current media label was first used on this media.Mount status: This indicates whether the media is "Mounted" (ready for reading or writing), "Mount Pending" (request to mount is waiting to be processed), or "Not Mounted."Media mode: This indicates whether the media is selected for reading, writing, or both, or whether the mount request is pending.Media type: This indicates the type of media in the device, such as 4mm DDS (Digital Data Storage) tape, 8mm tape, etc.Total capacity: This indicates the total capacity of this media.PERFORMANCE="REQUIRED"Press
MOREINFO="NONE" <Esc> when you are finished to return to the "Main Menu."
PAGENUM=746 ID="BP698"RENDERAS="SECT2"Media UtilitiesIDXID="w8919"BOOK="_idx" COLLECTION="nw41" TIDREF="i398"IDXID="w8920"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"Use the following procedures to erase media headers, to erase all data on the media, or to retension media in tape devices.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Storage Device Administration."The "List of Devices" screen is displayed.PERFORMANCE="REQUIRED"Select one device name, and press 
MOREINFO="NONE"<Insert>.The "Media for: 
Device_Name" screen is displayed, listing the names of any media in the device you selected.If, instead, a message is displayed saying that no media is in the device, but you know that there is, return to the device list and press 
MOREINFO="NONE"<Enter>. This will force the media to be read.PERFORMANCE="REQUIRED"Select one media name, and press 
MOREINFO="NONE"<Insert>.
PAGENUM=747 ID="BP699"PERFORMANCE="REQUIRED"From the "Utilities For: 
Media_Name" menu, choose one option.The following table explains each option.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="12*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8921"BOOK="_idx" COLLECTION="nw41" TIDREF="i2369"
"Erase the Media Header"COLNAME=2 ROTATE="0" MOREROWS="0"This is a quick method of making the media appear blank. Although this is less secure than erasing all of the data, this method is quick and effective.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8922"BOOK="_idx" COLLECTION="nw41" TIDREF="i2369"
"Erase all Data on the Media"COLNAME=2 ROTATE="0" MOREROWS="0"This is a security measure that might take up to 2 hours, depending on the size of the media.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w8923"BOOK="_idx" COLLECTION="nw41" TIDREF="i2369"
"Retension this Media"COLNAME=2 ROTATE="0" MOREROWS="0"This option is for tape devices that allow retensioning (0.25-inch cartridges, for example). This will fast- forward and rewind the tape, which might resolve a problem reading the tape.RENDERAS="SECT2"Renaming a Storage DeviceIDXID="w8924"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"The default names for IDXID="w8925"BOOK="_idx" COLLECTION="nw41" TIDREF="i396"
storage devices are controlled by the devices. These names often are not descriptive. If you have several devices, it might be difficult to remember which name goes with which device. For this reason, renaming storage devices might be helpful.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnsure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that the SBACKUP "Main Menu" is displayed on your server console.PAGENUM=748 ID="BP700"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Storage Device Administration."The "List of Devices" screen is displayed.PERFORMANCE="REQUIRED"Select the device name that you want to rename, and press 
MOREINFO="NONE"<F3>.PERFORMANCE="REQUIRED"Type a new name or identifier for the device, 
and then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> when finished to return to the "Main Menu."Any new device names that you assign are lost if the NetWare server goes down. When you load the SBACKUP module after the server has been down, the device names revert to the default.RENDERAS="SECT2"Managing Storage MediaIf the storage media you are using does not have enough IDXID="w8926"BOOK="_idx" COLLECTION="nw41" TIDREF="i398"
empty space for the entire backup, SBACKUP will span IDXID="w8927"BOOK="_idx" COLLECTION="nw41" TIDREF="i398"
media, prompting you to insert additional media when the first is full.Always have IDXID="w8928"BOOK="_idx" COLLECTION="nw41" TIDREF="i398"
extra media on hand in case the backup session IDXID="w8929"BOOK="_idx" COLLECTION="nw41" TIDREF="i178"
spans more than one media.SBACKUP designates the first media that has a particular IDXID="w8930"BOOK="_idx" COLLECTION="nw41" TIDREF="i398"
label as #1 and increments by 1 any IDXID="w8931"BOOK="_idx" COLLECTION="nw41" TIDREF="i398"
subsequent media with the same label.To help safeguard your network, SBACKUP exits when a delayed backup is complete. If the delayed backup session cannot fit on the media, SBACKUP prompts you to insert additional media. If additional media is not inserted, the backup does not finish and SBACKUP does not exit, thus compromising security.PAGENUM=749 ID="BP701"RENDERAS="SECT1"ID="FM34972"IDXID="w8932"BOOK="_idx" COLLECTION="nw41" TIDREF="i4430"IDXID="w8933"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"
Changing TargetsAnytime you are performing a series of backup or restore sessions, you may need to change your target. This is easily done from the SBACKUP "Main Menu."If you don't specify a new target, SBACKUP automatically selects the target used during the last session and continues without asking you to make a selection.RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXEnsure that you have loaded the drivers for your specific device and controller board.Ensure that you have loaded the SBACKUP files for your specific target. (See IDREF="FM85148""Loading Files Needed to Run SBACKUP" on page 660.)Ensure that media is inserted into your storage device.Ensure that the SBACKUP "Main Menu" is displayed on your server console.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"From the SBACKUP "Main Menu," choose "Change Target to Back Up From or Restore To."The "NetWare Servers Running Your Backup/Restore Target Services" screen is displayed.PERFORMANCE="REQUIRED"Choose one server.PERFORMANCE="REQUIRED"From the list o
f Target Service Agents, similar to 
IDREF="FM64340"Figure 9-52, choose a target.
PAGENUM=750 ID="BP702"LABEL="9-52" FLOAT="0"ID="FM64340"Display of Multiple Target Service Agents on a TargetFILEREF="n41sb39a.tif"If the target you choose has more than on
e Target Service Agent loaded, SBACKUP will show you a list of 
their full names.IDREF="FM64340"Figure 9-52 shows that the NetWare server named SALES is running the followin
g Target Service Agents:
TYPE="VERT"DOS Workstation (TSADOS)NetWare 2.2 File System (TSA220)NetWare 4.1 Directory (TSANDS)NetWare [4.1] File System (TSA410)OS/2 Workstation (TSAPROXY).You can back up from or restore data to any of these environments.PERFORMANCE="REQUIRED"Type in the username and password for t
he target
 you just selected.PAGENUM=751 ID="BP703"RENDERAS="SECT1"ID="FM88278"Unloading SBACKUP FilesIDXID="w8934"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"IDXID="w8935"BOOK="_idx" COLLECTION="nw41" TIDREF="i4666"You can unload SBACKUP if you want to have more memory available on your host or target.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Exit SBACKUP.Press 
MOREINFO="NONE"<Esc> until you reach 
the SBACKUP "Main Menu"; then press 
MOREINFO="NONE"<Esc> again and choose "Yes" at the confirmatio
n prompt.PERFORMANCE="REQUIRED"Unload the server files.To unload the server files, type th
e following commands at the server console prompt in the order show
n:The SMSDI, WSMAN, and SMDR files are automatically loaded by SBACKUP and other Storage Management Services modules, but they need to be manually unloaded.FORMAT="LINESPECIFIC"MOREINFO="NONE"UNLOAD SMSDI MOREINFO="NONE"<Enter>
UNLOAD TSA410 MOREINFO="NONE"<Enter>
UNLOAD TSADOS MOREINFO="NONE"<Enter>(if applicable)
UNLOAD TSAPROXY MOREINFO="NONE"<Enter>(if applicable)
UNLOAD TSANDS MOREINFO="NONE"<Enter>(if applicable)
UNLOAD SMDR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Unload the workstation files, if applicable.To unload the DOS workstation file, type the following command at the workstation prompt.
FORMAT="LINESPECIFIC"MOREINFO="NONE"TSASMS /U MOREINFO="NONE"<Enter>If the workstation had the message reception turned off (using the command 
"SEND /A=N
"), turn the message reception back on using the following comman
d:FORMAT="LINESPECIFIC"MOREINFO="NONE"SEND /A=A MOREINFO="NONE"<Enter>
PAGENUM=752 ID="BP704"RENDERAS="SECT1"ID="FM76095"ID="FM20277"Enhancing SBACKUP PerformanceRENDERAS="SECT2"Compressed FilesIDXID="w8936"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"
When a NetWare®4.1 volume is 
mounted, file compression is set to ON by default. When you perform a backup using TSA410, you can specify whether to keep already compressed files in a compressed state for the backup, or to back them up in an IDXID="w8937"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"
uncompressed state.File compression is specified on the form "How To Scan What You Are Backing Up" found in IDREF="FM13894"Figure 9-28 on page 702.To help you make your decision, remember these points:MARK=BULLETThe backup is faster if files already compressed are left compressed.Compression is not supported in some environments (for example, on a NetWare 3.11 server, or a DOS workstation). Therefore, if you intend to restore a file that is currently compressed to an environment that does not support compression, you should back it up in an uncompressed state.SBACKUP itself has no compression feature, so it cannot compress a file that is currently uncompressed.If volume compression is turned on and you try to back up compressed files in an IDXID="w8938"BOOK="_idx" COLLECTION="nw41" TIDREF="i1456"
uncompressed state, restore speed is degraded if you overwrite existing files. To improve restore speed, delete the files you no longer want from the hard disk before restoring them from the backup media. If you leave compressed files in a compressed state to restore them, speed is not affected.You might run out of disk space if you restore uncompressed files to a volume that compresses them.SBACKUP and file compression should not be run simultaneously. However, the default time for both delayed SBACKUP sessions and compression is midnight.If you want to perform a IDXID="w8939"BOOK="_idx" COLLECTION="nw41" TIDREF="i974"
delayed backup that includes files flagged for compression, schedule the delayed backup after the compression time to allow time for the completion of compression.PAGENUM=753 ID="BP705"RENDERAS="SECT2"ID="FM72288"ID="FM10083"ID="FM26857"ID="FM18131"Enhancing Host Server PerformanceIDXID="w8940"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"The speed of SBACKUP depends upon the host server's configuration and whether or not the server is backing up its own data or that of another server or workstation.For information on server configuration and setting parameters, see "BOOK="utlrfenu" COLLECTION="nw41"Communication Parameters" and "BOOK="utlrfenu" COLLECTION="nw41"File Caching Parameters" under "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.A server backing up its own data runs about twice as fast as a server backing up data from another server.This section includes four options using LOAD and SET commands that can enhance your host server's performance:MARK=BULLETChanging the size or number of buffersSetting minimum packet receive buffersSetting subdirectory levels and minimum cache buffersSetting reserved buffers below 16 MBRENDERAS="SECT3"ID="FM79118"Changing the Size and Number of BuffersIf your server has insufficient free memory, or if it has memory not being used, you can speed up a backup session by increasing the number and size of the host server's buffers when you load SBACKUP.You can change the size and number of buffers when you load SBACKUP. To do this, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD SBACKUP SIZE=XXX BUFFER=X MOREINFO="NONE"<Enter>
PAGENUM=754 ID="BP706"Select the size and number of buffers from the following chart:If you use an 8-bit or 16-bit host adapter and a driver that does not force the use of memory below 16 MB, do not specify a buffer-size and memory-size combination that exceeds 16 MB. If you do, corrupted data is copied to the backup media.IDXID="w8941"BOOK="_idx" COLLECTION="nw41" TIDREF="i4101"IDXID="w8942"BOOK="_idx" COLLECTION="nw41" TIDREF="i549"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"RangeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SizeCOLNAME=2 ROTATE="0" MOREROWS="0"16, 32, 64, 128, or 256 KB (Default=64 KB)COLNAME=1 ROTATE="0" MOREROWS="0"BuffersCOLNAME=2 ROTATE="0" MOREROWS="0"2 to 10 (Default=4)For more about changing the size or number of buffers, see your device driver's documentation.RENDERAS="SECT3"Setting Minimum Packet Receive BuffersThe packet receive buffers represent the space in the server memory dedicated to handling network traffic. If the buffers are set too low, the server performance may degrade.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Include the following SET command in your STARTUP.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET MINIMUM PACKET RECEIVE BUFFERS = XXXThe x's represent the number of buffers. S
et two b
uffers for each user on the system. The minimum is 10.PERFORMANCE="REQUIRED"To activate the changes, 
bring down the server (type DOWN at th
e server console prompt) and reboot it.
PAGENUM=755 ID="BP707"RENDERAS="SECT3"Setting Maximum Subdirectory Level and Minimum Cache BuffersIDXID="w8943"BOOK="_idx" COLLECTION="nw41" TIDREF="i4101"IDXID="w8944"BOOK="_idx" COLLECTION="nw41" TIDREF="i549"If you change the maximum subdirectory level in the server's STARTUP.NCF file, you must also change the minimum cache buffers. The maximum subdirectory level default is 25.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Include the following commands in the AUTOEXEC.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET MINIMUM FILE CACHE BUFFERS=X
SET MAXIMUM DIRECTORY CACHE BUFFERS=
XReplac
e the x w
ith a number equal to or greater than the subdirectory level you set in the STARTUP.NCF file. The default is 20 for the file buffers and 500 for the directory buffers.PERFORMANCE="REQUIRED"To activate the changes, down the server (type DOWN at the serve
r console prompt) an
d bring it back up.RENDERAS="SECT3"ID="FM79794"Setting Reserved Buffers Below 16 MBIf your storage device driver requires memory below 16 MB and the server has more than 16 MB available to it, you must reserve memory below 16 MB for the driver.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Include the following command in the STARTUP.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET RESERVED BUFFERS BELOW 16 MEG=XReplac
e the x w
ith a number between 8 and 300. The default is 200.PERFORMANCE="REQUIRED"To activate the changes, 
bring down the server (type DOWN at the serve
r console prompt) and reboot it.
PAGENUM=756 ID="BP708"RENDERAS="SECT1"ID="FM51877"TroubleshootingIf you have IDXID="w8945"BOOK="_idx" COLLECTION="nw41" TIDREF="i3956"
trouble while using IDXID="w8946"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
SBACKUP, check IDREF="FM92579"Table 9-6 to see if you can solve the problem.LABEL="9-6" PGWIDE=1 TOCENTRY="1"ID="FM92579" Troubleshooting Guide for SBACKUP ProblemsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="12*"COLNAME=3 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ProblemCOLNAME=2 ROTATE="0" MOREROWS="0"Possible CauseCOLNAME=3 ROTATE="0" MOREROWS="0"For more information, seeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The media owner is "Unidentified."COLNAME=2 ROTATE="0" MOREROWS="0"Media is blank or was written in a non-SIDF format.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM44682""Checking Status of Media in a Device" on page 744COLNAME=1 ROTATE="0" MOREROWS="0"Backup speed is slow.COLNAME=2 ROTATE="0" MOREROWS="0"Compressed files are being backed up in an uncompressed format.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM76095""Enhancing SBACKUP Performance" on page 752COLNAME=1 ROTATE="0" MOREROWS="0"Restore speed is slow.COLNAME=2 ROTATE="0" MOREROWS="0"File compression and SBACKUP are running at the same time.Compressed files are being overwritten with uncompressed files.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM72288""Enhancing Host Server Performance" on page 753COLNAME=1 ROTATE="0" MOREROWS="0"Data is corrupted.COLNAME=2 ROTATE="0" MOREROWS="0"Volumes were mounted or dismounted or drivers were unloaded during a session.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM63064""Rules for Using SBACKUP" on page 656COLNAME=1 ROTATE="0" MOREROWS="0"Data is corrupted, but no error message was given.COLNAME=2 ROTATE="0" MOREROWS="0"Compressed files were restored to a volume without compression.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM59126""Prerequisites to Restoring" on page 717COLNAME=1 ROTATE="0" MOREROWS="0"The server is in an abend condition.COLNAME=2 ROTATE="0" MOREROWS="0"Volumes were mounted or dismounted or drivers were unloaded during a session.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM63064""Rules for Using SBACKUP" on page 656COLNAME=1 ROTATE="0" MOREROWS="0"The specified file or directory cannot be found.COLNAME=2 ROTATE="0" MOREROWS="0"Wrong spelling or wrong case was used for case-sensitive name spaces.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM63064""Rules for Using SBACKUP" on page 656COLNAME=1 ROTATE="0" MOREROWS="0"The target you want is not listed.COLNAME=2 ROTATE="0" MOREROWS="0"The Target Service Agent isn't loaded on the desired target.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM72637""Backing Up Data" on page 670COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"SBACKUP has not had time to "find" the target.COLNAME=3 ROTATE="0" MOREROWS="0"(Not applicable)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"The host and target are physically far apart and network traffic is heavy.COLNAME=3 ROTATE="0" MOREROWS="0"(Not applicable)COLNAME=1 ROTATE="0" MOREROWS="0"You (network supervisor) can't back up a workstation.COLNAME=2 ROTATE="0" MOREROWS="0"The "/Password" option is set and is denying access to data on the workstation.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM91263"Table 9-1 on page 665  COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Other CPU-intensive applications were running, and they did not allow the workstation TSR to obtain resources.COLNAME=3 ROTATE="0" MOREROWS="0"(Not applicable)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Backup was attempted from two different servers at the same time. One succeeded and the other one failed.COLNAME=3 ROTATE="0" MOREROWS="0"(Not applicable)COLNAME=1 ROTATE="0" MOREROWS="0"A backup does not contain all changes.COLNAME=2 ROTATE="0" MOREROWS="0"Differential and incremental backups were combined. Use one or the other of these types in conjunction with full backups.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM14384""Backup Types" on page 671COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"The modify bit was cleared after the last custom backup, so changed files are not recognized.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM14384""Backup Types" on page 671COLNAME=1 ROTATE="0" MOREROWS="0"You cannot find the session log file you want.COLNAME=2 ROTATE="0" MOREROWS="0"It might be in a different directory, or you might have deleted it accidentally.COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM96305""Deleting the Log Files for Overwritten Sessions" on page 740COLNAME=1 ROTATE="0" MOREROWS="0"Pressing MOREINFO="NONE"<Insert> on device list does not produce a media list.COLNAME=2 ROTATE="0" MOREROWS="0"No medium has been selected.COLNAME=3 ROTATE="0" MOREROWS="0""Select" option at the bottom of the screen.COLNAME=1 ROTATE="0" MOREROWS="0""The time form is invalid" message is displayed when you try to schedule a delayed backup.COLNAME=2 ROTATE="0" MOREROWS="0"The date has been incorrectly entered in the time form. Press MOREINFO="NONE"<F1> for help with the time or date format.COLNAME=3 ROTATE="0" MOREROWS="0"(Not applicable)COLNAME=1 ROTATE="0" MOREROWS="0"Files were restored but the error file contains a message specifying which name space formats were not restored.COLNAME=2 ROTATE="0" MOREROWS="0"The file attributes and name-space formats are not configured on the volume you restored to.COLNAME=3 ROTATE="0" MOREROWS="0"(Not applicable)ID="FM49128"LABEL="A"PAGENUM=759 ID="BP709"ID="FM76952"Troubleshooting the NetworkThis appendix provides general hardware and network troubleshooting information for resolving equipment-related errors on a server running NetWare 4TM networking software.RENDERAS="SECT1"Troubleshooting Hardware and Network ProblemsIDXID="w8947"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"RENDERAS="SECT2"Making Computer Memory Available for Network DriversIDXID="w8948"BOOK="_idx" COLLECTION="nw41" TIDREF="i2393"
IDXID="w8949"BOOK="_idx" COLLECTION="nw41" TIDREF="i2035"To increase the amount of workstation memory available for network drivers:MARK=BULLETAdd more memory.Unload unneeded TSR (terminate-and-stay-resident) programs (DOS clients only).Modify the NET.CFG file to load only necessary drivers.Modify the CONFIG.SYS file to load only necessary drivers.For more information about freeing up memory on a workstation, see IDREF="FM53844""Resolving Workstation Memory Problems" on page 770.For information about freeing up memory on a server, see IDREF="FM37746""Resolving Server Memory Problems" on page 767.PAGENUM=760 ID="BP710"RENDERAS="SECT2"ID="FM98024"Resolving Server Hardware ProblemsIDXID="w8950"BOOK="_idx" COLLECTION="nw41" TIDREF="i1638"Before servicing the NetWare® server, notify users that the server is going down and they may lose data if they don't log out. If possible, do a complete system backup.To diagnose and resolve problems with NetWare server hardware:MARK=BULLETMake sure the server's configuration settings and network address are correct.Make sure the servers and workstations are using the same packet frame type (such as Ethernet 802.2 or Ethernet 802.3).If hardware was recently installed on the server, remove the hardware and reboot the server.If the error does not reoccur, run diagnostics on the removed hardware. Check for conflicts (interrupts, memory addresses, I/O ports, DMA, etc.) between the new and existing computer hardware.Check the system board, memory board, memory chips/hard disk.The following IDXID="w8951"BOOK="_idx" COLLECTION="nw41" TIDREF="i1031"
toolsIDXID="w8952"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
 provide server diagnostic capabilities:MARK=BULLETLANalyzer®MONITOR.NLMSERVMAN.NLMManufacturer's diagnostic programsRENDERAS="SECT2"Resolving Network ProblemsIDXID="w8953"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"IDXID="w8954"BOOK="_idx" COLLECTION="nw41" TIDREF="i705"To diagnose and resolve network communications problems:MARK=BULLETMake sure configuration settings and network numbering are configured correctly.List server and workstation settings in a binder. Include a printout of the current configuration files.PAGENUM=761 ID="BP711"Make sure network numbering is set up correctly on the network.MARK=BULLETEach network segment must have a unique IPXTM external network number.On that network segment, each node must have the same IPX external network number and a unique node number.(For more information, see "BOOK="cncptenu" COLLECTION="nw41"Network numbering" in Concepts.)Make sure the servers and workstations are using the same packet frame type (for example, Ethernet 802.2 or Ethernet 802.3).Maintain an error log recording previous errors and problems experienced by the servers and workstations on the network. Whenever possible, get a screen dump when an error occurs and include it in the binder.RENDERAS="SECT2"Resolving Cabling ProblemsIDXID="w8955"BOOK="_idx" COLLECTION="nw41" TIDREF="i567"MARK=BULLETUse the proper cabling for your network topology as specified by IEEE. Make sure cable segments do not exceed the recommended lengths.Make sure cable segments are properly terminated for the type of cabling being used.Make sure terminators and in-line cable connectors are working properly.If you are not sure whether a terminator or connector is working properly, replace it. If the new components work properly, discard the old ones.Make sure there are no breaks in the cable or shield. Use a time delay reflectometer (TDR), a LANalyzer, or a volt ohm meter (VOM) to test cabling for breaks in the cable conductor or shield.Make sure cabling is routed away from devices that produce high electric or magnetic fields, such as fluorescent lights, microwaves, radar, X-rays, copy machines, etc.PAGENUM=762 ID="BP712"RENDERAS="SECT2"ID="FM45002"Power Supply ErrorsIDXID="w8956"BOOK="_idx" COLLECTION="nw41" TIDREF="i3362"An inconsistent power source is the most common cause of hardware problems. It also produces the most devastating results.Power outages cause workstations, network servers, print servers, and backup devices to reboot. When this happens, all information stored in RAM is lost, and sometimes hardware is damaged.Power spikes and "brownouts" can also cause a variety of hardware errors.You can have reliableIDXID="w8957"BOOK="_idx" COLLECTION="nw41" TIDREF="i1106"
 network performance only if you plan for power outages and fluctuations and protect against them. The following tips can help you do this:MARK=BULLETAdd a dedicated power feed and ground line from your breaker box to critical equipment. Make sure the ground line connects to earth ground.Install an uninterruptible power supply (UPS) or a standby power system (SPS) to provide power to critical equipment for 15 minutes after a power outage.The capacity of such power supplies is limited, so you may not want to plug nonvital hardware (such as monitors or printers) into the UPS or SPS line.Train users to save data and log out of the network when the lights go out. Then you can bring down the NetWare server in an orderly fashion without forcing users off the system while the server is running on UPS or SPS power.Install a surge suppressor or power conditioner on all power lines that are used by computers. Many UPS and SPS devices already have this feature.Do not allow anyone to plug fans, printers, copy machines, vacuum cleaners, or other motor-driven appliances into the dedicated line or into any power line with computers.Insert dummy plugs into open outlets to prevent people from plugging such appliances into computer power sources.PAGENUM=763 ID="BP713"RENDERAS="SECT1"Troubleshooting the NetWare ServerIDXID="w8958"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"IDXID="w8959"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"This section provides troubleshooting suggestions for typical NetWare® server problems such as disk I/O errors, insufficient disk space, and insufficient memory.RENDERAS="SECT2"ID="FM37619"Resolving AbendsIDXID="w8960"BOOK="_idx" COLLECTION="nw41" TIDREF="i41"IDXID="w8961"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"RENDERAS="SECT3"Overview of Server Abend MessagesThe NetWare 4TM operating system is very resilient, but errors can and will arise. Serious problems are usually accompanied by abend (abnormal end) messages.Abend messages are usually caused by consistency check errors, but they also can be caused by insufficient memory, DMA (Direct Memory Access) conflicts, or hardware and software interrupts.Abend messages are displayed in a format similar to the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"Abend: SERVER-4.10-message_number message_stringAbend messages are documented in 
BOOK="sysmsenu" COLLECTION="nw41"System Messages.RENDERAS="SECT3"Consistency Check ErrorsConsistency check errors are internal tests placed in the NetWare operating system by Novell software engineers.The primary function of consistency checks is to ensure the stability and integrity of internal operating system data.Numerous consistency checks are interlaced throughout NetWare to validate critical disk, memory, and communications processes.Consistency check errors might be caused by a corrupted operating system file, by corrupted or outdated drivers and NetWare Loadable ModuleTM (NLM) programs, or by hardware failure.These errors can also be associated with defective memory chips, static discharges, faulty power supplies, or power surges or spikes.PAGENUM=764 ID="BP714"RENDERAS="SECT3"What to Do When You Get an AbendIf an abend occurs, note the abend message for reference. Then try one or more of the followingMARK=BULLETReboot the server.Make sure the server has sufficient memory. See IDREF="FM37746""Resolving Server Memory Problems" on page 767.Check the system board, memory chips, power supplies, and power conditioning equipment. Replace any faulty hardware.Make sure the server has the latest drivers and NLMTM programs. Update everything that is not current.If new hardware has been recently installed in the server, remove the hardware. If the error does not recur, run diagnostics on the removed hardware.Make sure there are no conflicts (interrupts, memory addresses, I/O ports, DMA) between the hardware in the computer and the new hardware.If the hardware is good, unload individual NLM programs, reboot, and repeat the procedures that created the original abend. You may be able to isolate an NLM that is causing the problem.Reinstall the operating system, drivers, or NLM programs from the master diskettes. If the server gets a serialization error (abend messages 1418, 1419, 1420, and 1421), reinstall SERVER.EXE from the master diskettes.Make sure the copy of NetWare being installed is a correct, legal (nonpirated) original.If none of these remedies resolve the problem, record all the hardware installed on the server and all actions you have taken to correct the problem. Then contact your Novell Authorized ResellerCLM representative for technical support.PAGENUM=765 ID="BP715"RENDERAS="SECT3"Preparing a Core DumpIDXID="w8962"BOOK="_idx" COLLECTION="nw41" TIDREF="i852"Upon contacting your Novell Authorized Reseller representative, you may be asked for a "core dump" that may be analyzed in Novell's diagnostic laboratory. A core dump is a "snapshot" of the server's memory at the time of the abend.Often, though not always, Novell's technicians can diagnose the problem by analyzing the core dump, searching in memory for clues as to what caused the abend.If you are asked to prepare a core dump, make sure you have sufficient diskettes on hand to copy all of the computer's memory.For example, to copy 12 MB of memory, you need nine 3.5-inch high-density (1.44MB) diskettes.Also, if you can recreate the problem and describe exactly what steps led up to the abend, you should record this information and send it in along with the diskettes.If Novell's technicians are able to correct the problem, and if the problem has been caused by a NetWare software bug, they debug the program and send a patch for the problem.RENDERAS="SECT2"ID="FM30310"Resolving Server I/O ErrorsIDXID="w8963"BOOK="_idx" COLLECTION="nw41" TIDREF="i1997"IDXID="w8964"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"To resolve a general disk I/O error on the server, try one or more of the following remedies:MARK=BULLETCheck the disk subsystems to make sure the power is on and the cables are correctly connected between the controller and the subsystems.Make sure the subsystem cables are terminated correctly.Make sure the disks are installed correctly.Make sure you have current NetWare  4-certified disk driver loaded. Many drivers can be found on the NetWare CD-ROM or on the master diskettes. Updated drivers may also be available from third-party disk driver manufacturers.PAGENUM=766 ID="BP716"Make sure the interrupt parameters, I/O port settings, slot settings, etc. for the driver match those for the hardware. Also, make sure custom parameters have been set correctly for your hardware.At the server console, type the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"SCAN FOR NEW DEVICES MOREINFO="NONE"<Enter>This causes the operating system to request controller information about all devices.Load INSTALL, selecting "Maintenance/Selective Install," "Disk Options," and then "Modify Disk Partitions and Hot Fix." Make sure the device is visible and has a valid partition.Increase the Hot FixTM Redirection Area, using INSTALL.NLM.To change the Hot Fix Redirection Area on an existing drive, back up all the data on the partition, delete the volumes on the partition, and delete the partition; then re-create it.Assign the partition a different percentage for the Hot Fix Redirection Area; then recreate the volumes and restore the data.If you have tried all the preceding suggestions without success, contact your Novell Authorized Reseller representative or drive manufacturer.RENDERAS="SECT2"Resolving Server Disk Space ProblemsIDXID="w8965"BOOK="_idx" COLLECTION="nw41" TIDREF="i1128"IDXID="w8966"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"To resolve an insufficient disk space error, you should do one or more of the following:MARK=BULLETDelete unnecessary files and directories from the volume.Change the Minimum File Delete Wait Time SET parameter in your server's AUTOEXEC.NCF file equal to 0 so that files can be purged immediately rather than being retained in a salvageable state on the volume.Use the FILER or NetWare Administrator utility to purge deleted files if they cannot be purged automatically. (The purged files are using up directory table space.)Increase the volume size and/or add more disks to the volume.PAGENUM=767 ID="BP717"Increase the percentage of disk space that can be used by a directory.If the disk or volume has space available, check the disk drives and disk channel to see if a failure has occurred.Use SET to increase the percentage of disk space that can be used by a directory.Delete NLM programs that you no longer use.Check and adjust or remove any volume restrictions placed upon users.If the disk or volume has space available, check the disk drives and disk channel to see if a failure has occurred.For information on SET parameters, see IDREF="FM56019""Managing Server Hard Disks" on page 518 and "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.RENDERAS="SECT2"ID="FM37746"Resolving Server Memory ProblemsIDXID="w8967"BOOK="_idx" COLLECTION="nw41" TIDREF="i2392"IDXID="w8968"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
IDXID="w8969"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"To free up server memory temporarily (until you can add more memory to the server), do one or more of the following:MARK=BULLETUse the FILER or NetWare Administrator utility to purge deleted files on the specified directory that cannot be purged automatically. (Deleted files are using up directory table space.)Use REMOVE DOS or SECURE CONSOLE to free the memory in the server that has been reserved for DOS.Unload NLM programs, such as INSTALL or MONITOR, that are not currently needed.Dismount volumes that are not being used.Reduce the size or number of volumes that the server supports.Delete unused files and directories on the specified volume.Change the Minimum File Delete Wait Time SET parameter in the AUTOEXEC.NCF file so that files can be purged immediately rather than being retained in a salvageable state on the volume.PAGENUM=768 ID="BP718"As a last resort, back up all files in your volume, bring down your server, and use INSTALL to reinitialize the volume. Specify block size of 64 KB and turn the "Block Suballocation" option to "Off."(This setting uses a lot of disk space but increases the amount of memory available.)For more information, see IDREF="FM63100"Chapter 7, "Maintaining the NetWare Server," and "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.RENDERAS="SECT2"ID="FM73029"Resolving Locked Device ErrorsIDXID="w8970"BOOK="_idx" COLLECTION="nw41" TIDREF="i2178"To resolve a locked device error, try one or more of the following:MARK=BULLETWait for a while; the task in process may complete and free the device.Retry the action that resulted in the error.Load MONITOR.NLM, delete all user connections, and disable logins.For a disk device error, unload NLM programs (other than the device driver) that may be using the disk. Dismount all volumes on the disk.If you have tried all of the above without success, contact your Novell Authorized Reseller representative or the drive manufacturer.RENDERAS="SECT2"ID="FM66390"Resolving File I/O ErrorsIDXID="w8971"BOOK="_idx" COLLECTION="nw41" TIDREF="i1997"To resolve a file I/O error, try one or more of the following:MARK=BULLETCheck to see that the volume (especially volume SYS:) is mounted. To check volumes, type VOLUMES at the server console prompt.If the volume is out of disk space, error messages will appear on the console screen indicating that the volume is almost out of disk space. Check the console screen.Type DIR at a DOS workstation to see how much space remains.PAGENUM=769 ID="BP719"To increase the amount of free space, do one or more of the following:MARK=BULLETDelete extraneous files (if you can log in from a workstation).Type SET IMMEDIATE PURGE OF DELETED FILES = ON at the console prompt, and retry the action.If you have an additional disk, increase the size of the volume by creating an additional segment of the volume on the disk.See also IDREF="FM10885""Resolving Volume I/O Errors" on page 769.RENDERAS="SECT2"ID="FM10885"Resolving Volume I/O ErrorsIDXID="w8972"BOOK="_idx" COLLECTION="nw41" TIDREF="i1997"To resolve a volume I/O error, try one or more of the following:MARK=BULLETMake sure all devices that contain the volume are online. (Volumes may span multiple devices.) See IDREF="FM30310""Resolving Server I/O Errors" on page 765.Load and execute VREPAIR.Load INSTALL, selecting "Selective Install/Maintain" and "Volume Options." Make sure the volume is visible.If you have tried all of the above without success, contact your Novell Authorized Reseller representative or disk drive manufacturer.RENDERAS="SECT2"ID="FM86922"Resolving Event Control Block Allocation ErrorsIDXID="w8973"BOOK="_idx" COLLECTION="nw41" TIDREF="i1359"IDXID="w8974"BOOK="_idx" COLLECTION="nw41" TIDREF="i1997"Event control block allocation system messages can occur when you first bring up the server or after the server has been running for some time.These messages indicate that the server was unable to acquire sufficient packet receive buffers, usually called event control blocks (ECBs). Running out of ECBs is not a fatal condition.Servers that run for several days where high loads occur in peaks might exceed the set maximum number of ECBs, causing the system to generate ECB system messages.PAGENUM=770 ID="BP720"If these situations are caused by occasional peaks in the memory demand, you should probably maintain your current maximum ECB allocation and allow the message to be generated at those times.On the other hand, if your server memory load is very high and you receive frequent ECB allocation errors, you should probably set your maximum ECB allocation higher. Use the following SET command in the STARTUP.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET MAXIMUM PACKET RECEIVE BUFFERS=numberMemory allocated for ECBs cannot be used for other purposes. The minimum number of buffers available for the server can also be set in the STARTUP.NCF file with the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET MINIMUM PACKET RECEIVE BUFFERS=numberRENDERAS="SECT1"Troubleshooting WorkstationsIDXID="w8975"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"This section provides troubleshooting suggestions for typical NetWare® client (workstation) problems, including ways to resolve workstation memory problems. This section also lists common NetWare workstation error messages (the 900 series of messages).RENDERAS="SECT2"ID="FM53844"Resolving Workstation Memory ProblemsRENDERAS="SECT3"DOS WorkstationsTo free up DOS workstation memory temporarily (until you can add more memory to the workstation), do one or more of the following.MARK=BULLETUnload any unneeded TSR (terminate-and-stay-resident) programs.Optimize memory usage by loading DOS and other programs into high memory.Modify the CONFIG.SYS file to reduce the number of files that can be open at the same time, the number of buffers allocated for disk drives, and the memory size allocated by the shell for the DOS environment (the /E option).PAGENUM=771 ID="BP721"The following settings are sufficient for normal workstation operation, but the values can be reduced further until problems occur:FORMAT="LINESPECIFIC"MOREINFO="NONE"FILES=20
BUFFERS=20
SHELL=C:\COMMAND.COM /E:640 /PBe sure to reboot the machine after modifying the CONFIG.SYS file.RENDERAS="SECT3"OS/2 WorkstationsCheck the CONFIG.SYS file to see if there are any devices that can be unloaded; then try to load the driver again.(For more information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.)RENDERAS="SECT2"Resolving Workstation Disk Space ProblemsIDXID="w8976"BOOK="_idx" COLLECTION="nw41" TIDREF="i1128"To resolve an insufficient disk space error, do one or both of the following:MARK=BULLETDelete unnecessary files and directories from the volume.Unload TSR (terminate-and-stay-resident) programs that have swap files on the hard disk.LABEL="B"PAGENUM=773 ID="BP722"Managing NetWare Server for OS/2RENDERAS="SECT1"IDXID="w8977"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w8978"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w8979"BOOK="_idx" COLLECTION="nw41" TIDREF="i2322"
NetWare Server for OS/2 and NetWare 4Use NetWare® Server for OS/2* like any other NetWare 4TM server, with a few exceptions:MARK=BULLETThe server is loaded using NWOS2.EXE instead of SERVER.EXE.Different keystrokes are used for navigating through server screens.DOMAIN.NLM is not supported and will not load.The PMMON utility is available in addition to MONITOR for monitoring the server.This appendix provides an explanation of these differences.RENDERAS="SECT1"IDXID="w8980"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w8981"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"ID="FM48221"Loading NetWare Server for OS/2Load NetWare Server for OS/2 using IDXID="w8982"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
NWOS2.EXE instead of SERVER.EXE.RENDERAS="SECT2"Using NWOS2.EXE to Load the Server from the Command LineRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open an OS/2 full screen or OS/2 window session.PERFORMANCE="REQUIRED"Change to th
e directory where the server files are installed.If you used the defaults during the installation, the directory is \NWSERVER and is located on your OS/2 boot drive. If you did not use the defaults, the directory has the name and location you assigned to it.
PAGENUM=774 ID="BP723"PERFORMANCE="REQUIRED"At the command prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWOS2 MOREINFO="NONE"<Enter>NetWare 
Server for OS/
2 loads in the full screen or window session you opened.RENDERAS="SECT2"Using the OS/2 Graphical Interface to Load the ServerRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose the "Novell" group icon on your desktop.The "Novell" 
group icon was created when you installed NetWare Server for OS/2 or NetWare Client for OS/2.PERFORMANCE="REQUIRED"Choose the "NetWare Server for OS/2" icon.By default, NetWare Server for OS/2 loads in a full screen session. NetWare Server for OS/2 can b
e loaded in an OS/2 window by using the OS/2 "Settings
" feature on the "NetWare Server for OS/2" icon
.For more information about the 
"Settings
" feature, see your OS/2 documentation.RENDERAS="SECT1"IDXID="w8983"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
Navigating in NetWare Server for OS/2Use the following key sequences for accessing screens and menus in NetWare Server for OS/2:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TaskCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare Server for OS/2 Key SequenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Switching between screensCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<N>COLNAME=1 ROTATE="0" MOREROWS="0"Accessing selection menuCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Ctrl>+<N>If you release the MOREINFO="NONE"<Alt> key too quickly (without pressing another key), you will activate the OS/2 system menu for the window session rather than the next NetWare screen.PAGENUM=775 ID="BP724"RENDERAS="SECT1"ID="FM17404"IDXID="w8984"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
Using Loadable Modules in NetWare Server for OS/2All NetWare Loadable ModuleTM (NLM) programs and console utilities work with NetWare Server for OS/2 the same as they do on any NetWare 4 server except for the following:MARK=BULLETDOMAIN.NLM. This NLMTM does not work with NetWare Server for OS/2 and cannot be loaded. Memory management is handled by OS/2.NPRINTER.EXE. If your computer is running NetWare Server for OS/2 and NetWare Client for OS/2, we recommend that you use IDXID="w8985"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
NPRINTER.NLM rather than NPRINTER.EXE for printing. NPRINTER.EXE will work, but NPRINTER.NLM will work better for you. Don't load NPRINTER.NLM and NPRINTER.EXE on a computer that is running both the client and server.VGADISP.NLM. This NLM is used to display Japanese characters on a monitor screen. VGADISP.NLM does not work on NetWare Server for OS/2 and should not be loaded. OS/2 will take care of Japanese characters.RENDERAS="SECT1"ID="FM34376"IDXID="w8986"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
Monitoring NetWare Server for OS/2To monitor NetWare Server for OS/2, you can use MONITOR or IDXID="w8987"BOOK="_idx" COLLECTION="nw41" TIDREF="i3325"
PMMON. (PMMON is a monitoring utility that runs under the OS/2 Presentation Manager.)Although MONITOR works with NetWare Server for OS/2, the server utilization information is not correct. For a more accurate report of server utilization, use PMMON.An icon for PMMON is placed in the "Novell" group icon on the desktop when you install NetWare Server for OS/2.PAGENUM=776 ID="BP725"RENDERAS="SECT2"IDXID="w8988"BOOK="_idx" COLLECTION="nw41" TIDREF="i3325"IDXID="w8989"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"ID="FM33825"Loading PMMONPMMON can be loaded either by choosing the "PMMON" icon or by entering the command at the command line.RENDERAS="SECT3"Using the OS/2 DesktopRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose the "Novell" group icon.This opens the Novell Icon View.PERFORMANCE="REQUIRED"Choose th
e "PMMON" icon.Th
e PMMON screen appears (se
e IDREF="FM80808"Figure B-1).LABEL="B-1" FLOAT="0"ID="FM80808"PMMON Graphical Server MonitorFILEREF="n41su19a.tif"PAGENUM=777 ID="BP726"RENDERAS="SECT3"Using the Command LineRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Open an OS/2 full screen or OS/2 window session.PERFORMANCE="REQUIRED"Change to the directory where the server files from the NetWare Server for OS/2 installation are installed.If you used the defaults during the installation, the directory is \NWSERVER and is located on your OS/2 boot drive. If you did not use the defaults, the directory has the name and location you assigned to it.PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"PMMON MOREINFO="NONE"<Enter>Th
e PMMON screen appears
.RENDERAS="SECT1"ID="FM58699"IDXID="w8990"BOOK="_idx" COLLECTION="nw41" TIDREF="i3325"IDXID="w8991"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
Using PMMONPMMON includes pull-down menus that can be used to set memory sharing options, set performance tuning, free base server memory, access online help, and close the utility.The following statistics are gathered and displayed in PMMON:TYPE="VERT"NetWare Server for OS/2 utilizationOriginal cache buffersTotal cache buffersPacket receive buffersDirectory cache buffersService processesThe percent of OS/2 CPU usageThe percent of NetWare CPU usageDirty cache buffersConnections in useOpen filesPAGENUM=778 ID="BP727"There are six buttons on the right side of the PMMON screen. These buttons are used to set values and "watermarks" for the bar graphs at the bottom of the utility. For more information about each button, see the online help.PMMON tracks many of the same statistics as MONITOR, but there is approximately a 5-percent performance loss when PMMON is running instead of MONITOR.MONITOR does not correctly account for sharing the server with OS/2. For example, in MONITOR the server use may constantly read 100 percent even though the server is not busy.RENDERAS="SECT2"ID="FM36599"Setting Performance TuningIDXID="w8992"BOOK="_idx" COLLECTION="nw41" TIDREF="i3293"IDXID="w8993"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"You can use PMMON to set the performance tuning level for NetWare Server for OS/2.Setting the performance tuning level allows you to specify how much processing time is allocated to NetWare. The higher the performance tuning level, the more processing time is allocated to the server.Whatever processing time is not allocated to NetWare Server for OS/2 is used by OS/2.The default setting should work fine for your needs. However, you may want to lower the performance tuning level if OS/2 operation is too slow because of the amount of traffic on the server.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose "Performance Tuning" from the "Configuration" menu.This activates a submenu listing 10 levels of performance tuning
.PERFORMANCE="REQUIRED"Choose the level you want for your server.The performance tuning default level i
s 8. Changing the level i
n PMMON overrides the default while the server is running
.If the server is 
brought dow
n, the default performance tuning level will return t
o 8 whe
n the server is brought back up (unless you have another level set in the NET.CFG file).
PAGENUM=779 ID="BP728"Performance tuning can also be set in the NET.CFG file. (Se
e IDREF="FM82661""Performance Tuning" on page 789.)RENDERAS="SECT2"Setting Memory SharingIDXID="w8994"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w8995"BOOK="_idx" COLLECTION="nw41" TIDREF="i2391"You can use PMMON to set manual and automatic 
memory sharing options for NetWare Server for OS/2 and OS/2.MARK=BULLETManual memory sharing allows you to allocate more or less memory to NetWare Server for OS/2 or OS/2 while the server is running. You determine the amount of memory each operating system needs.For example, if the NetWare® operating system is used significantly more on your computer than OS/2, you would allocate more memory to NetWare Server for OS/2.Automatic memory sharing determines the proper amounts of memory NetWare Server for OS/2 or OS/2 will need as the server is running.RENDERAS="SECT3"IDXID="w8996"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
Manual Memory SharingUse the "Memory Sharing" dialog box to allocate memory manually to NetWare Server for OS/2 or to OS/2.The allocation changes you make in the "Memory Sharing" dialog box will override any memory settings in the NET.CFG file while the server is running. When the server is brought down and back up, the memory settings in the NET.CFG file will again take effect.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Load PMMON.PERFORMANCE="REQUIRED"Choose "Memory Sharing" from the "Configuration" menu.
"The "Memory Sharing" dialog box appears (se
e IDREF="FM85292"Figure B-2).
PAGENUM=780 ID="BP729"LABEL="B-2" FLOAT="0"ID="FM85292""Memory Sharing" Dialog BoxFILEREF="n41su47a.tif"This box displays the current memory settings and the amount of memory used by NetWare 
Server for OS/2 and OS/2.PERFORMANCE="REQUIRED"Click on the slider and move the mouse to th
e left or right until you get the allocation ratio you want.The amount of memory allocated to NetWare 
Server for OS/2 and to OS/2 changes as indicated in the "Allocation Amounts
" field of the "Memory Sharing
" 
dialog box.You can also click on the left and right arrow buttons next to the slider to change memory settings.PERFORMANCE="REQUIRED"Choose "Set.
"The changes you make to memory allocation do not tak
e effect until the 
"Set
" button is selected.Choosing "Reset
" switches the memory allocation to the amount of memory that the server had when you opened the "Memory Sharing
" 
dialog box.PERFORMANCE="REQUIRED"Choose "Close
" to close the "Memory Sharing
" 
dialog box.
PAGENUM=781 ID="BP730"RENDERAS="SECT3"Automatic Memory SharingIDXID="w8997"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"Automatic memory sharing is active as a default. Automatic memory sharing can be deactivated in the "Memory Sharing" dialog box or in the NET.CFG file.To deactivate automatic memory sharing, choose "Manual" in the "Memory Sharing" dialog box.To deactivate automatic memory sharing in the NET.CFG file, enter the following lines in the NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"NETWARE FOR OS/2
   AUTOMATIC MEMORY SHARING OFFIf you deactivate automatic memory sharing from the "Memory Sharing" dialog box, that setting overrides the default ON setting in the NET.CFG file while the server is running. If the server is brought down and back up, the setting in the NET.CFG file again takes effect.For more information about setting automatic memory sharing in the NET.CFG file, see IDREF="FM35141""Automatic Memory Sharing" on page 792.RENDERAS="SECT3"Freeing Base Server MemoryIDXID="w8998"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w8999"BOOK="_idx" COLLECTION="nw41" TIDREF="i2391"You can use PMMON to free the base server memory that NetWare Server for OS/2 allocates from OS/2. The memory is released back to OS/2 when the server is brought down.You can also free the server memory by using the REMOVE BASE SERVER MEMORY option in the NET.CFG file (see IDREF="FM22771""Remove Base Server Memory" on page 791).RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load PMMON.PERFORMANCE="REQUIRED"Choose "Fre
e Bas
e Serve
r Memory
" from the "Configuration" menu.When "Free Base Server Memory" is active, a check mark appears next to it on the menu. To deactivate it, choose "Free Base Server Memory" again from the menu and the check mark will disappear.
PAGENUM=782 ID="BP731"RENDERAS="SECT2"Releasing Server MemoryYou can use PMMON to release the base server memory immediately back to OS/2 if the server is not running.For example, if BASE SERVER MEMORY in your NET.CFG file is set at 8, OS/2 will allocate an 8 MB block of memory to NetWare Server for OS/2 when the computer boots. If you do not run the server, OS/2 will not be able to use that 8 MB block of memory because it is reserved for NetWare Server for OS/2.If you want OS/2 to be able to use this memory when the server is not running, use PMMON to release it.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load PMMON when the server is not running.A message will appear indicating that the server is down.PERFORMANCE="REQUIRED"Choose "Cancel" to cancel the message from the screen.Do not choose "OK" to close the message because that will close PMMON.PERFORMANCE="REQUIRED"Choose "Release Server Memory" from the "Options" menu.A message appears that reads, "If you select OK, memory for the server will be given to OS/2."PERFORMANCE="REQUIRED"Choose "OK" in the message box to release the memory back to OS/2.
PAGENUM=783 ID="BP732"RENDERAS="SECT1"Supporting WorkstationsNetWare Server for OS/2 supports all NetWare® clients.If you are using the OS/2 High Performance File System (HPFS), you need to load the OS/2 and Macintosh name spaces in order for the server to support OS/2 and Macintosh clients. For information about loading name spaces, see IDREF="FM43638""Setting Up a Volume to Store Non-DOS Files" on page 506.If you run Extended Attributes on your OS/2 workstation, enter the following SET parameters at the server console:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET maximum Extended Attributes per file or path = 32FORMAT="LINESPECIFIC"MOREINFO="NONE"SET maximum percent of volume space allowed for Extended Attributes = 10For information about SET parameters, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.RENDERAS="SECT1"IDXID="w9000"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w9001"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
Configuring NetWare Server for OS/2This section contains instructions for changing the configuration of NetWare Server for OS/2 using the NET.CFG file. It also includes an alphabetical listing of the options used for NetWare Server for OS/2 in the NET.CFG file.The information in this section is also found in the configuration help screens in the NetWare Server for OS/2 installation program.You may want to change the configuration of NetWare Server for OS/2 for any of the following reasons:MARK=BULLETTo allow NetWare Server for OS/2 and NetWare Client for OS/2 to use the same network boardTo allocate a specific amount of memory to NetWare Server for OS/2To remove the memory that NetWare Server for OS/2 has allocated from OS/2 when the server is brought downPAGENUM=784 ID="BP733"To specify the proportion of processing time allocated to NetWare Server for OS/2To activate or deactivate automatic memory sharing between NetWare Server for OS/2 and OS/2RENDERAS="SECT1"ID="FM45501"NET.CFG File FormatIDXID="w9002"BOOK="_idx" COLLECTION="nw41" TIDREF="i2793"Modify the NetWare® Server for OS/2 configuration by entering options and settings in the NET.CFG file.The NET.CFG file contains options and settings that define how NetWare Server for OS/2 and NetWare Client for OS/2 will function on the network.Each NET.CFG option has settings. If you use the NetWare Server for OS/2 installation program to modify the NET.CFG file, these settings are alphabetized under the option to which they apply in the "NET.CFG Options" window.If you use an OS/2 text editor to modify NET.CFG, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide for more about each option and setting.RENDERAS="SECT2"ID="FM67211"Conventions for Entering NET.CFG OptionsIDXID="w9003"BOOK="_idx" COLLECTION="nw41" TIDREF="i2793"You can create or edit the NET.CFG file through the NetWare Server for OS/2 installation program or by using an OS/2 text editor.Use the following rules to create or modify the NET.CFG file. These rules are illustrated in IDREF="FM94552"Figure B-3.MARK=BULLETType options at the left margin with no spaces before or after them.Type options in either uppercase or lowercase (they are not case-sensitive).Type one option per line.Type settings, one per line, below the option to which they apply.Use the Spacebar to indent these settings. Settings must be indented at least one space.PAGENUM=785 ID="BP734"Do not use MOREINFO="NONE"<Tab> to indent the setting if you are using the graphical NetWare Server for OS/2 utility to edit the NET.CFG file. Pressing MOREINFO="NONE"<Tab> activates different windows and buttons in the NET.CFG Options box.Press MOREINFO="NONE"<Enter> at the end of every line in the file, including the last line. If you don't press MOREINFO="NONE"<Enter> at the end of the last line, the line is ignored.Precede comments with a semicolon.LABEL="B-3" FLOAT="0"ID="FM94552"Format of NET.CFG FileFILEREF="n41su46a.tif"PAGENUM=786 ID="BP735"RENDERAS="SECT2"ID="FM13597"Editing the NET.CFG File Using the Installation ProgramRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Start the installation program by choosing the "Install" icon in the "Novell" group on the OS/2 desktop.PERFORMANCE="REQUIRED"In th
e installation program, choose "This Workstation
" from the "Configuration
" menu
.The 
"Default Location for NET.CFG File
" 
dialog box appears. This 
dialog box indicates where on your hard disk the NET.CFG file will be placed. (The NET.CFG file is usually placed at the root of the OS/2 boot drive.)PERFORMANCE="REQUIRED"Choose "Edit
" from the "Default Location for NET.CFG File
" dialog box.A 
dialog box allowing you to edit the NET.CFG file appears.PERFORMANCE="REQUIRED"Use the 
"Edit NET.CFG" dialog box to add configuration options (se
e IDREF="FM56144"Figure B-4).
PAGENUM=787 ID="BP736"LABEL="B-4" FLOAT="0"ID="FM56144""Edit NET.CFG" Dialog BoxFILEREF="n41su44a.tif"PAGENUM=788 ID="BP737"RENDERAS="SECT2"ID="FM97610"Editing the NET.CFG File Using an OS/2 Text EditorRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open an OS/2 full screen or window session.PERFORMANCE="REQUIRED"At the command line prompt, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"EPM NET.CFG MOREINFO="NONE"<Enter>An OS/2 text editor appears
 (see IDREF="FM27334"Figure B-5).LABEL="B-5" FLOAT="0"ID="FM27334"OS/2 Text EditorFILEREF="n41su72a.tif"PERFORMANCE="REQUIRED"Use the editor to add the configuration options you need.
PAGENUM=789 ID="BP738"RENDERAS="SECT1"ID="FM83224"ID="FM28802"NET.CFG Options and SettingsThe following sections explain the NET.CFG options and settings you can use to enhance NetWare Server for OS/2 performance. Each example includes a description of the option and setting, the default setting, and an example of the proper syntax for entering the option and setting in the NET.CFG file.RENDERAS="SECT2"ID="FM13094"The NetWare for OS/2 OptionUse this option to set memory and performance features for NetWare Server for OS/2.RENDERAS="SECT3"SyntaxIDXID="w9004"BOOK="_idx" COLLECTION="nw41" TIDREF="i2793"FORMAT="LINESPECIFIC"MOREINFO="NONE"NETWARE FOR OS/2
   PERFORMANCE TUNING number
   INITIALIZATION SCREEN DELAY number
   BASE SERVER MEMORY number
   REMOVE BASE SERVER MEMORY
   ALLOCATE MEMORY value
   AUTOMATIC MEMORY SHARING value
   MAXIMUM SERVER MEMORY number
   BLOCK ALLOCATION SIZE numberRENDERAS="SECT3"ID="FM68253"SettingsRENDERAS="SECT4"ID="FM82661"Performance TuningIDXID="w9005"BOOK="_idx" COLLECTION="nw41" TIDREF="i3293"IDXID="w9006"BOOK="_idx" COLLECTION="nw41" TIDREF="i2793"MOREINFO="NONE"Use this setting to specify how much processing time is allocated to NetWare Server for OS/2. Whatever is not allocated to NetWare Server for OS/2 is left for OS/2.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"NETWARE FOR OS/2MOREINFO="NONE"  PERFORMANCE TUNING number Replace number with a number from 1 to 10.The higher the number, the more processing time is allocated to NetWare Server for OS/2 and the faster your NetWare server will run.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"8COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the performance tuning level to 7:MOREINFO="NONE"NETWARE FOR OS/2MOREINFO="NONE"  PERFORMANCE TUNING 7The default setting should be acceptable for your needs. However, you may want to lower the performance tuning level if OS/2 operation is too slow because of the amount of traffic on the server.PAGENUM=790 ID="BP739"RENDERAS="SECT4"ID="FM14085"Initialization Screen DelayIDXID="w9007"BOOK="_idx" COLLECTION="nw41" TIDREF="i2793"Use this setting to specify the number of seconds you want the NetWare Server for OS/2 configuration options screen to remain displayed when OS/2 boots. (The screen displays information about device driver configuration. This screen cannot be used to change the configuration; it is for information only.)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"NETWARE FOR OS/2MOREINFO="NONE"  INITIALIZATION SCREEN DELAY number Replace number with a number expressed in seconds between 0 and 180.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"8COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set a 3-second delay:MOREINFO="NONE"NETWARE FOR OS/2MOREINFO="NONE"  INITIALIZATION SCREEN DELAY 3PAGENUM=791 ID="BP740"RENDERAS="SECT4"Base Server MemoryIDXID="w9008"BOOK="_idx" COLLECTION="nw41" TIDREF="i2793"MOREINFO="NONE"Use this setting to allocate a base amount of memory for the server at boot time. If volumes on your server do not mount, increase the amount of base server memory using this setting.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"NETWARE FOR OS/2MOREINFO="NONE"  BASE SERVER MEMORY numberReplace number with a number expressed in megabytes. Be sure the number you specify is large enough to run the server, but small enough to leave adequate memory for OS/2.If NetWare Server for OS/2 cannot allocate the amount of memory you specify, it displays a warning message and uses the highest amount it can obtain.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"4COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allocate 8.5 MB of base server memory for NetWare Server for OS/2:MOREINFO="NONE"NETWARE FOR OS/2MOREINFO="NONE"  BASE SERVER MEMORY 8.5RENDERAS="SECT4"ID="FM22771"Remove Base Server MemoryIDXID="w9009"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"MOREINFO="NONE"Use this setting to release the base server memory allocated to NetWare Server for OS/2 so the memory will be available for OS/2 to use. The memory is released when the server is brought down.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"NETWARE FOR OS/2MOREINFO="NONE"  REMOVE BASE SERVER MEMORY.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Base server memory is not released.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To release base server memory upon bringing down the server:MOREINFO="NONE"NETWARE FOR OS/2MOREINFO="NONE"  REMOVE BASE SERVER MEMORYPAGENUM=792 ID="BP741"RENDERAS="SECT4"Allocate MemoryIDXID="w9010"BOOK="_idx" COLLECTION="nw41" TIDREF="i161"IDXID="w9011"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w9012"BOOK="_idx" COLLECTION="nw41" TIDREF="i2391"Use this setting to request that memory allocated from OS/2 to the server be allocated above or below the first 16 MBMOREINFO="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"NETWARE FOR OS/2MOREINFO="NONE"  ALLOCATE MEMORY valueReplace value with HIGH or LOW.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"None.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allocate the memory above 16 MB:MOREINFO="NONE"NETWARE FOR OS/2MOREINFO="NONE"  ALLOCATE MEMORY HIGHTo allocate the memory below 16 MB:MOREINFO="NONE"NETWARE FOR OS/2MOREINFO="NONE"  ALLOCATE MEMORY LOWRENDERAS="SECT4"ID="FM35141"Automatic Memory SharingIDXID="w9013"BOOK="_idx" COLLECTION="nw41" TIDREF="i2793"Use this setting to deactivate automatic memory sharing (it is active as a default). When automatic memory sharing is active, the system determines the proper amounts of memory for NetWare Server for OS/2 or OS/2 as the server is runningMOREINFO="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"NETWARE FOR OS/2MOREINFO="NONE"  AUTOMATIC MEMORY SHARING valueReplace value with OFF.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"ONCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To deactivate automatic memory sharing:MOREINFO="NONE"NETWARE FOR OS/2MOREINFO="NONE"  AUTOMATIC MEMORY SHARING OFFPAGENUM=793 ID="BP742"RENDERAS="SECT4"Maximum Server MemoryIDXID="w9014"BOOK="_idx" COLLECTION="nw41" TIDREF="i2793"Use this setting to set the maximum amount of memory that NetWare Server for OS/2 can allocate from OS/2 when manual or automatic memory sharing is active. This prevents NetWare Server for OS/2 from taking too much memory from OS/2.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"NETWARE FOR OS/2MOREINFO="NONE"  MAXIMUM SERVER MEMORY numberReplace number with a number expressed in megabytes.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"None.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the maximum amount of memory that can be used by NetWare Server for OS/2 to 12 MB:MOREINFO="NONE"NETWARE FOR OS/2MOREINFO="NONE"  MAXIMUM SERVER MEMORY 12RENDERAS="SECT4"Block Allocation SizeIDXID="w9015"BOOK="_idx" COLLECTION="nw41" TIDREF="i2793"Use this setting to specify the number of memory pages you want to include in a total block of memory that NetWare Server for OS/2 allocates from OS/2. One memory page is equal to 4 KB of memory.For example, if you use the default of 8, NetWare Server for OS/2 allocates 8 memory pages in each block of memory. This means that the total size of the memory block is 32 KB (8 memory pages at 4 KB each = 32 KB).PAGENUM=794 ID="BP743"When memory sharing is active, NetWare Server for OS/2 allocates blocks of memory from OS/2 in this size.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"NETWARE FOR OS/2MOREINFO="NONE"  BLOCK MOREINFO="NONE"ALLOCATION SIZE numberReplace number with a number between 4 and 1024.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"8COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the Block Allocation Size so that NetWare Server for OS/2 allocates 200 KB in each memory block:MOREINFO="NONE"NETWARE FOR OS/2MOREINFO="NONE"  BLOCK ALLOCATION SIZE 50(50 x 4 KB = 200 KB)PAGENUM=795 ID="BP744"RENDERAS="SECT2"ID="FM22144"The NetWare Requester OptionUse this option to control network requests from your workstation to a NetWare server.There are several settings that can be used with the NetWare RequesterTM option. Only the ones that you may want to use with NetWare Server for OS/2 are described in this section.For information about all the available NET.CFG options and settings, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.RENDERAS="SECT3"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"NETWARE REQUESTER
   NONDED SERVER
   PACKET BURST OFFRENDERAS="SECT3"SettingsRENDERAS="SECT4"IDXID="w9016"BOOK="_idx" COLLECTION="nw41" TIDREF="i2906"IDXID="w9017"BOOK="_idx" COLLECTION="nw41" TIDREF="i1291"
Nonded IDXID="w9018"BOOK="_idx" COLLECTION="nw41" TIDREF="i2793"
ServerUse this setting to allow NetWare Server for OS/2 and NetWare Client for OS/2 to use the same network board.If you specify this setting, NetWare Server for OS/2 must be running on your computer before you can attach to the network using NetWare Client for OS/2 (otherwise, the client displays a connection error).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"NETWARE REQUESTERMOREINFO="NONE"  NONDED SERVERCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare Server for OS/2 and NetWare Client for OS/2 use separate network boards.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow NetWare Client for OS/2 and NetWare Server for OS/2 to use the same board:MOREINFO="NONE"NETWARE REQUESTERMOREINFO="NONE"  NONDED SERVERNote: If your client software will not attach to a NetWare network, it may be because option has not been set.PAGENUM=796 ID="BP745"RENDERAS="SECT4"Packet Burst OffUse this setting to disable the Packet Burst feature. For more information about Packet Burst, see "BOOK="ws_osenu" COLLECTION="nw41"Improving Speed by Using Packet Burst " in NetWare Client for OS/2 User Guide.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"NETWARE REQUESTERMOREINFO="NONE"  PACKET BURST OFFCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Packet Burst is enabled.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To disable Packet Burst:MOREINFO="NONE"NETWARE REQUESTERMOREINFO="NONE"  PACKET BURST OFFID="FM23482"LABEL="C"PAGENUM=797 ID="BP746"SFT III Management TipsThis appendix describes tips for managing and troubleshooting a NetWare® 4.1 SFT IIITM network. The information is divided into these categories:TYPE="VERT"Server SynchronizationMirrored Server Link (MSL)Server Configuration (.NCF) FilesServer MemoryServer ConsolesServer Hard DisksNetwork ClientsNetwork PerformanceTroubleshootingThe SET command is mentioned frequently in these sections. For more information on the SET command and its parameters, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.RENDERAS="SECT1"Server SynchronizationThis section discusses possible solutions to software failures related to SFT III server synchronization.RENDERAS="SECT2"Detecting Server Synchronization ErrorsFor a comprehensive check of IDXID="w9019"BOOK="_idx" COLLECTION="nw41" TIDREF="i2543"
MSEngine outputs on each server, turn on the Comprehensive MSEngine Synchronization Check SET parameter. By default, a less intrusive check is performed. Using the comprehensive check may affect server performance.PAGENUM=798 ID="BP747"Because this parameter must be set before the servers are activated (only settable at startup), put this command in the IOSTART.NCF file for each server:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Comprehensive MSEngine Synchronization Check=ONRENDERAS="SECT2"Handling Secondary Restarts Immediately After SynchronizationIf the IDXID="w9020"BOOK="_idx" COLLECTION="nw41" TIDREF="i3988"IDXID="w9021"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
secondary server restarts immediately after synchronization, increase the IPX Internet Down Wait Time and the MSL Deadlock Detect Wait Time SET parameters, using the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET IPX Internet Down Wait Time=variable
SET MSL Deadlock Detect Wait Time=
variableIf this does not solve the problem, halt the server by changing all mirrored servers' error recovery options to 0. See IDREF="FM83712""Servers Restart for No Apparent Reason" on page 822 for specific options. After halting the server, contact your support representative.RENDERAS="SECT2"ID="FM28771"Notifying Users of Server SynchronizationTo send a broadcast message to all logged-in network users when the mirrored servers begin synchronizing, type the following.FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Notify All Users Of Mirrored Server Synchronization=ONThe default setting for this parameter is OFF.RENDERAS="SECT2"Reducing the Time for Resynchronizing and RemirroringIDXID="w9022"BOOK="_idx" COLLECTION="nw41" TIDREF="i3837"To shorten server synchronization time, reduce the amount of memory that must be synchronized, using the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET New End Address For Unclaimed Memory Block=variableUsing this SET parameter to reduce the amount of unclaimed memory may prevent some loadable modules from loading in the MSEngine. If the MSEngine memory is too small, some volumes may not mount.PAGENUM=799 ID="BP748"If you have disk arrays, you may be able to speed up disk mirroring with the Concurrent Remirror Requests SET parameter.RENDERAS="SECT2"Responding to "Invalid Mirrored Server Initialization" MessagesIf this message appears when the servers are in test mode, no action is necessary as long as the servers continue to synchronize.To prevent server initialization problems, increase the Restart Minimum Delay Amount, using the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Restart Minimum Delay Amount=variableAlso, verify that the MSL boards and cables are functional. Then unload and reload the MSL driver on each server.If you are using NE2000TM boards as MSL boards, make sure that the interrupt settings on the MSL boards have a higher priority than the network boards, and that the MSL boards are cabled correctly.Interrupt priorities from high to low are 0, 1, 2 or 9, A, B, C, D, E, F, 3, 4, 5, 6, 7, and 8. Interrupt 2 is the highest priority you can assign to an MSL board because interrupts 0 and 1 are reserved.RENDERAS="SECT2"Responding to "Mirrored Server Engine Already Loaded" MessagesThis message means you have already executed the ACTIVATE SERVER console command, either at the IOEngine console or in the IOSTART.NCF file of the other server. Delete "ACTIVATE SERVER" from the IOSTART.NCF file.Putting ACTIVATE SERVER in the IOSTART.NCF file may cause synchronization problems. If both servers execute ACTIVATE SERVER simultaneously, the utility may load two separate, unsynchronized IDXID="w9023"BOOK="_idx" COLLECTION="nw41" TIDREF="i2543"
MSEngines, and both servers would assume the IDXID="w9024"BOOK="_idx" COLLECTION="nw41" TIDREF="i3387"IDXID="w9025"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
primary server role.PAGENUM=800 ID="BP749"RENDERAS="SECT1"IDXID="w9026"BOOK="_idx" COLLECTION="nw41" TIDREF="i2472"IDXID="w9027"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
Mirrored Server Link (MSL)This section discusses possible solutions to hardware and software failures related to the high-speed cable links between the mirrored SFT IIITM servers.RENDERAS="SECT2"Determining Appropriate MSL Cable LengthsThe maximum IDXID="w9028"BOOK="_idx" COLLECTION="nw41" TIDREF="i2472"
cable length between MSL boards is determined by the cable manufacturer. Ranges are from 30 to 100 meters for coaxial cable, and from 1 to 40 kilometers for fiber optic cable.RENDERAS="SECT2"Handling MSL Cable or MSL Board FailureWhen an MSL IDXID="w9029"BOOK="_idx" COLLECTION="nw41" TIDREF="i2472"
cable or board fails, the secondary server restarts but cannot synchronize with the primary server until the MSL problem is corrected.To prevent future MSL problems and loss of server mirroring, install 
redundant, IDXID="w9030"BOOK="_idx" COLLECTION="nw41" TIDREF="i2547"IDXID="w9031"BOOK="_idx" COLLECTION="nw41" TIDREF="i167"
alternate MSL boards and cabling in each server. The alternate MSL driver must be loaded before it can take over for an active MSL that fails.Put the LOAD command for the alternate MSL driver in the IOSTART.NCF files of both servers, after the LOAD command for the first MSL driver. Use the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD alternate_driver_nameThe order the drivers are loaded determines which MSL is the default and which is the first alternate, second alternate, and so forth.RENDERAS="SECT2"Responding to MSL Communications Error MessagesCheck the MSL cable and board connections to make sure they are properly connected and that the boards are firmly seated. Also check for kinks or damage in the cabling.RENDERAS="SECT2"Responding to "MSL Deadlock Delivering Data" MessagesIDXID="w9032"BOOK="_idx" COLLECTION="nw41" TIDREF="i2548"IDXID="w9033"BOOK="_idx" COLLECTION="nw41" TIDREF="i952"This message means that neither MSL can transmit data because of a "holdoff." A holdoff occurs when the IOEngine receives a packet but cannot process it, or when one MSL sends a packet but doesn't receive an acknowledgment.PAGENUM=801 ID="BP750"Increase the MSL Deadlock Detect Wait Time, using the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET MSL Deadlock Detect Wait Time=variableIf the servers are very busy, increase this parameter in 1-second increments until the error disappears.Make sure the value of the MSL Deadlock Detect Wait Time parameter is at least1second longer than the IPX Internet Down Wait Time parameter.RENDERAS="SECT1"Server Configuration (.NCF) FilesIDXID="w9034"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"SFT III reads from these server IDXID="w9035"BOOK="_idx" COLLECTION="nw41" TIDREF="i746"IDXID="w9036"BOOK="_idx" COLLECTION="nw41" TIDREF="i2616"
configuration files, in the following order, when you power on or restart the servers:MARK=BULLETIDXID="w9037"BOOK="_idx" COLLECTION="nw41" TIDREF="i1903"
IOSTART.NCF (two files---one for each server)IDXID="w9038"BOOK="_idx" COLLECTION="nw41" TIDREF="i2553"
MSSTART.NCFIDXID="w9039"BOOK="_idx" COLLECTION="nw41" TIDREF="i2541"
MSAUTO.NCFIDXID="w9040"BOOK="_idx" COLLECTION="nw41" TIDREF="i1899"
IOAUTO.NCF (two files---one for each server)Most of these files are created during the installation process. Use INSTALL to create or edit server configuration files. You can also use EDIT to edit .NCF files.Example: IOSTART.NCF file (on DOS partition)FORMAT="LINESPECIFIC"MOREINFO="NONE"ioengine name SFT3_IO1
ioengine ipx internal net 7654321
load isadisk port=1f0 int=e
load nmslExample: MSSTART.NCF file (on DOS partition)FORMAT="LINESPECIFIC"MOREINFO="NONE"set Concurrent Remirror Requests=11
PAGENUM=802 ID="BP751"Example: MSAUTO.NCF file (on volume SYS:)FORMAT="LINESPECIFIC"MOREINFO="NONE"set Time Zone=MST7MDT
set Daylight Savings Time Offset=1:00:00
set Start Of Daylight Savings Time=(APRIL SUNDAY FIRST 2:00:00 AM)
set End Of Daylight Savings Time=(OCTOBER SUNDAY LAST 2:00:00 AM)
set Default Time Server Type=SINGLE
set Bindery Context=O=Novell
msengine name SFT3
msengine ipx internal net 1234567
mount allExample: IOAUTO.NCF file (on DOS partition or volume SYS:)FORMAT="LINESPECIFIC"MOREINFO="NONE"sys:etc\io1\initsys.ncf
load tcpipTo edit INITSYS.NCF, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. PAGENUM=803 ID="BP752"RENDERAS="SECT1"Server MemoryIDXID="w9041"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"IDXID="w9042"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"This section discusses how to install additional server memory without disrupting the network and how to respond to the message "Secondary server is missing RAM."RENDERAS="SECT2"Adding Memory Without Bringing the MSEngine DownIDXID="w9043"BOOK="_idx" COLLECTION="nw41" TIDREF="i2392"A NetWare 4.1 SFT III system allows you to upgrade server hardware without loss of service to clients.Use the procedure below to add memory to your servers without bringing down the MSEngine.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Halt the secondary server and turn it off.The primary server is still running.PERFORMANCE="REQUIRED"Add memory to the secondary server and turn it on.PERFORMANCE="REQUIRED"Reconfigure the hardware, using the hardware-specific configuration procedure specified by the manufacturer.PERFORMANCE="REQUIRED"From the DO
S prompt 
for drive C: on the secondary server, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"MSERVER MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Wait for resynchronization to complete.During resynchronization, the primary server does not recognize the additional memory in the secondary server.PERFORMANCE="REQUIRED"After the disks are remirrored, halt the primary server and turn it off.The secondary server becomes the new primary server.PERFORMANCE="REQUIRED"Add memory to the new secondary server and turn it on.
PAGENUM=804 ID="BP753"PERFORMANCE="REQUIRED"Reconfigure the hardware, using the hardware-specific configuration procedure specified by the manufacturer.To ensure synchronization, install the same amount of memory in both SFT III servers.PERFORMANCE="REQUIRED"From the DOS 
prompt for drive C
: on the secondary server, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"MSERVER MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Wait for resynchronization to complete.During synchronization, the primary server now recognizes the additional memory in the secondary server.RENDERAS="SECT2"Responding to "Secondary Server Is Missing RAM" MessagesIDXID="w9044"BOOK="_idx" COLLECTION="nw41" TIDREF="i2481"IDXID="w9045"BOOK="_idx" COLLECTION="nw41" TIDREF="i3988"IDXID="w9046"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"This message means that the primary server cannot synchronize memory with the secondary server for one of the following reasons:MARK=BULLETThe primary server has more RAM than the secondary server.The primary and secondary have the same amount of RAM installed, but the memory is noncontiguous and the memory "holes" don't match.In this situation, do one of the following:MARK=BULLETAdd memory to the secondary server so that its RAM is equal to the RAM in the primary server.Run the EISA configuration utility (if applicable) so that both servers are in the same mode (linear or compatible mode).IDXID="w9047"BOOK="_idx" COLLECTION="nw41" TIDREF="i2392"
Align the server memory holes using the procedure below.PAGENUM=805 ID="BP754"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Change to the IOEngine prompt on the secondary server.PERFORMANCE="REQUIRED"Check the memory addresses by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w9048"BOOK="_idx" COLLECTION="nw41" TIDREF="i2380"
MEMORY IDXID="w9049"BOOK="_idx" COLLECTION="nw41" TIDREF="i2380"
MAPMOREINFO="NONE" <Enter>A 
IDXID="w9050"BOOK="_idx" COLLECTION="nw41" TIDREF="i4638"IDXID="w9051"BOOK="_idx" COLLECTION="nw41" TIDREF="i2392"
display similar to the following appears.
FORMAT="LINESPECIFIC"MOREINFO="NONE"System memory map:0 - 12288 (DOS)12288 - 159744 (DOS)159744 - 654336 (IOEngine)1048576 - 5767168 (IOEngine)5767168 - 17170432 (Unclaimed)PERFORMANCE="REQUIRED"From th
e "Unclaimed
" range on the last line of the display, 
ID="FM17615"write down the "start" and "end" memory addresses.Unclaimed memory is used by the IDXID="w9052"BOOK="_idx" COLLECTION="nw41" TIDREF="i2543"IDXID="w9053"BOOK="_idx" COLLECTION="nw41" TIDREF="i4638"
MSEngine, so it must be identical on both servers.PERFORMANCE="REQUIRED"From the IOEngine console on the 
primary server, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"HALTMOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Add the following commands to the primary server's IOSTART.NCF file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET New Start Address for IDXID="w9054"BOOK="_idx" COLLECTION="nw41" TIDREF="i1325"IDXID="w9055"BOOK="_idx" COLLECTION="nw41" TIDREF="i4638"
Unclaimed Memory Block=x
SET New 
IDXID="w9056"BOOK="_idx" COLLECTION="nw41" TIDREF="i2392"
End Address for 
IDXID="w9057"BOOK="_idx" COLLECTION="nw41" TIDREF="i1325"IDXID="w9058"BOOK="_idx" COLLECTION="nw41" TIDREF="i4638"
Unclaimed Memory Block=
xThe values following the = 
(equals) sign are the start and end of the unclaimed 
IDXID="w9059"BOOK="_idx" COLLECTION="nw41" TIDREF="i2543"
memory range on the secondary server (the numbers you wrote down in 
IDREF="FM17615"Step 3).PERFORMANCE="REQUIRED"Restart the primary server.Now that the unclaimed memory is aligned on both servers, they can synchronize. SFT III allocates any extra memory to the IOEngine on that server.PAGENUM=806 ID="BP755"RENDERAS="SECT1"Server ConsolesThis section discusses solutions for keeping track of the three NetWare 4.1 SFT III server consoles---the two IOEngines and the MSEngine---and for managing errors displayed at these consoles.RENDERAS="SECT2"Logging and Viewing All Console MessagesSome IDXID="w9060"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"
SFT III console messages are never seen because you can't view all three consoles (two IDXID="w9061"BOOK="_idx" COLLECTION="nw41" TIDREF="i1901"
IOEngines and one MSEngine) at once.To keep track of these messages, use CONLOG to capture all console messages and to write them to SYS:\ETC\CONSOLE.LOG.To log messages from all three consoles, add the line LOAD CONLOG to the IOSTART.NCF files of both servers and to the MSAUTO.NCF file.The LOAD CONLOG command must be the first line in each .NCF file from which you want to log messages.To view the CONSOLE.LOG file, use EDIT or INETCFG.RENDERAS="SECT2"Handling Lost Interrupt Alerts on the ConsoleIDXID="w9062"BOOK="_idx" COLLECTION="nw41" TIDREF="i2239"IDXID="w9063"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"If lost interrupt alerts are filling up the console screen, at the appropriate IOEngine console, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"SET Display Lost Interrupt Alerts=OFF MOREINFO="NONE"<Enter>A lost interrupt message indicates a problem driver or faulty hardware. To find the driver with the interrupt problem, turn on the Display Lost Interrupt Alerts parameter as shown above. Then unload all the drivers from the appropriate IOEngine, and reload them one at a time. Contact the vendor of the problem driver.RENDERAS="SECT2"Responding to "Loader Cannot Find..." MessagesIDXID="w9064"BOOK="_idx" COLLECTION="nw41" TIDREF="i2151"IDXID="w9065"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"This message means you tried to load an NLM in the wrong engine (IOEngine or MSEngine), or that the NLM you tried to load depends on other NLMs that aren't loaded.PAGENUM=807 ID="BP756"Use the MOREINFO="NONE"<Alt>+<Esc> keys to toggle to the other engine's console, and attempt to load the NLM again.If the message still appears, you may have loaded an outdated or unsupported NLM.RENDERAS="SECT2"Shortening the Console PromptLong SET parameter names may scroll behind the console prompt if you have a long IOEngine or MSEngine name in the prompt. However, scrolling does not affect the execution of the SET utility.If you want a two-character console prompt (IO: or MS:), type the following at the appropriate console:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET IDXID="w9066"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"
Replace Console Prompt With Server Name=OFFMOREINFO="NONE" <Enter>RENDERAS="SECT1"Server Hard DisksThis section discusses solutions for hard disk errors and storage shortages on a NetWare 4.1 SFT III server.RENDERAS="SECT2"Controlling the Size of Log Files on Volume SYS:To limit the size of IDXID="w9067"BOOK="_idx" COLLECTION="nw41" TIDREF="i4118"
SFT III log files, IDXID="w9068"BOOK="_idx" COLLECTION="nw41" TIDREF="i1905"
IO$LOG.ERR and IDXID="w9069"BOOK="_idx" COLLECTION="nw41" TIDREF="i2555"
MSSTATUS.DMP, use the following commands:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET IDXID="w9070"BOOK="_idx" COLLECTION="nw41" TIDREF="i1901"
IOEngine Error Log File Overflow Size= number
SET Status Dump File Overflow Size= 
numberReplace number with the size limit in bytes.The system will delete or rename the log files when they meet or exceed the size limit, depending on the SET IOEngine Error Log File State and SET Status Dump File State parameter values.PAGENUM=808 ID="BP757"RENDERAS="SECT2"Handling Primary Hard Disk FailureThe IDXID="w9071"BOOK="_idx" COLLECTION="nw41" TIDREF="i3387"
primary server remains active if a primary hard disk fails.In this situation, clients continue to communicate with the primary server, but disk requests use only the secondary server's disk (instead of splitting the seeks between the servers).Use the procedure below to restore fault tolerance to your server storage.Make sure the failed disk is on the primary server and that the secondary server's disk is functional before attempting this procedure, or you may lose data.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Change to the primary server's IOEngine console.PERFORMANCE="REQUIRED"Force a server switchover by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"HALT MOREINFO="NONE"<Enter>The secondary server takes over the primary server role.PERFORMANCE="REQUIRED"Correct the hard disk problems and resynchronize the servers.PERFORMANCE="REQUIRED"Use the Server Failure Notification Name SET parameter to notify you immediately in case of another server disk failure. Add this parameter to the MSAUTO.NCF file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Server Failure Notification Name=group_name | user_nameRENDERAS="SECT2"ID="FM47919"Mounting a CD-ROM as a NetWare 4.1 SFT III VolumeAccess to data on a CD-ROM volume will be lost if the SFT III servers switch from primary to secondary unless you mount the same CD on both servers.To mount a CD-ROM disc as a NetWare 4.1 SFT III volume, follow these steps.PAGENUM=809 ID="BP758"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA mounted volume SYS:An installed Host Bus Adapter (HBA) that is NetWare compatible and supports CD-ROM devicesThe NPAIO.DSK and NPAMS.NLM NetWare Peripheral Architecture (NPA) modulesThe disk driver files and necessary support modules for the CD-ROM deviceSome disk drivers consist of more than one file and some HBA devices require additional support modules for CD-ROM functionality. These files should accompany the HBA. For specific file requirements, consult your adapter documentation.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Change to the IOEngine prompt of the SFT III server where the HBA is installed.PERFORMANCE="REQUIRED"Load the disk driver by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD [path]disk_driverMOREINFO="NONE" <Enter>Replace 
disk_driver with the name of the disk driver specified in the HBA documentation.For example, to load the disk driver for the Adaptec AHA-1522 SCSI HBA, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD [path]MOREINFO="NONE"AHA1520.DSK MOREINFO="NONE"<Enter>
  LOAD [
path]ASPICD.DSK
MOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Load CDROM.NLM by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD CDROMMOREINFO="NONE" <Enter>This auto-loads the NPAMS module.When a CD-ROM is mounted or a CD-ROM disc is changed, some CD-ROM devices may be deactivated. This deactivation occurs because device configuration information is being updated.PERFORMANCE="REQUIRED"View the device number and volume name by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"CD DEVICE LIST MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Mount the CD-ROM as a volume by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"CD MOUNT [device number] | [volume name] MOREINFO="NONE"<Enter>Replace 
device number with the device number or replace 
volume name with the volume name of the CD-ROM disc.For example, to mount the NetWare_41 CD-ROM, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"CD MOUNT NETWARE_41 MOREINFO="NONE"<Enter>It may take several minutes to mount the volume the first time, depending on the size of the CD-ROM and the speed of your computer.The standard volume mount messages appear.PERFORMANCE="REQUIRED"To mount the CD-ROM as a NetWare volume each time the server comes up, edit the IOSTART.NCF file of the SFT III server where the HBA is installed. Add these commands to the IOSTART.NCF file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD [path]disk_driverPERFORMANCE="REQUIRED"Edit the MSAUTO.NCF file, adding these commands:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD CDROM
CD MOUNT
 [
device number] | [
volume name]
PAGENUM=811 ID="BP760"RENDERAS="SECT2"Notifying Users of Disk or Server FailureTo notify a user or group of users about a disk or server failure, use the Server Failure Notification Name SET parameter in the MSEngine. Also put this parameter in the MSAUTO.NCF file. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET SERVER FAILURE NOTIFICATION NAME = ADMINWhen a failure happens, the specified user or group receives a broadcast message. To send this broadcast message to all logged-in users, use group EVERYONE.RENDERAS="SECT2"Recovering an Orphaned PartitionID="FM65713"Use the following procedure to recover an orphaned IDXID="w9072"BOOK="_idx" COLLECTION="nw41" TIDREF="i3236"IDXID="w9073"BOOK="_idx" COLLECTION="nw41" TIDREF="i1120"
partition:RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load INSTALL.PERFORMANCE="REQUIRED"From the "Installation Options" menu, choose "Disk Options."PERFORMANCE="REQUIRED"From the "Available Disk Options" menu, choose "Mirror/Unmirror."The 
"Partition Mirroring Status
" appears, showing one mirrored and one out of sync. The out-of-sync partition is the "orphan."PERFORMANCE="REQUIRED"Choose the mirrored partition.The "Mirrored Disk Partitions" menu displays the partition number and device number of each mirrored set. The device number for the out-of-sync partition is an 
"unavailable device.
"PERFORMANCE="REQUIRED"Remove the partition from the set by highlighting the out-of-sync partition and pressing 
MOREINFO="NONE"<DelMOREINFO="NONE"eteMOREINFO="NONE">.PERFORMANCE="REQUIRED"Return to "Disk Partition Mirroring Status" by 
ID="FM30685"pressing 
MOREINFO="NONE"<Esc>."Not mirrored" appears by the good partition, and "Out of sync" appears by the other partition. Note the number of the "not mirrored" partition.
PAGENUM=812 ID="BP761"PERFORMANCE="REQUIRED"Highlight the out-of-sync partition and press 
MOREINFO="NONE"<F3>.A warning message similar to the following appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Warning!! The selected partition contains "Volume SYS Segment 0" and that volume is already defined.PERFORMANCE="REQUIRED"Select the "No Salvage" option.PERFORMANCE="REQUIRED"Select the good partition (as noted in 
IDREF="FM30685"Step 6).PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Insert> for a list of the available partitions.PERFORMANCE="REQUIRED"Highlight the previously orphaned partition and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue by pressing 
MOREINFO="NONE"<Esc>.The unavailable partition is deleted. After a brief delay, the remirroring process begins. Because the entire partition is remirrored, the process takes several minutes or hours, depending on the partition size.
 You can check remirroring status with the MIRROR STATUS command or by watching the install screen.RENDERAS="SECT1"Network ClientsThis section discusses solutions for workstation problems that may be encountered on NetWare 4.1 SFT III networks.RENDERAS="SECT2"Finding a Server from an Ethernet WorkstationIDXID="w9074"BOOK="_idx" COLLECTION="nw41" TIDREF="i1350"Some Ethernet clients may have problems finding or attaching to a server.If you use the 802.3 frame type, change the value of the Enable IPX Checksums SET parameter to 0 in the MSEngine by typing the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Enable IPX Checksums = 0 MOREINFO="NONE"<Enter>The default setting is 0. Also, make sure volume SYS: is mounted.PAGENUM=813 ID="BP762"RENDERAS="SECT2"Finding the SFT III Server FirstIDXID="w9075"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"If another NetWare server is on the same network segment as an SFT III server, clients will not find the SFT III server first.Because the IOEngine routes the get-nearest-server request to the MSEngine, the SFT III server appears to be two hops away while the other NetWare server appears to be closer.To find the SFT III server first, include the following statement in the client's NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"Preferred Server=<MSEngine_name>RENDERAS="SECT2"Handling DOS IPX Session Timeouts During Server SwitchoverIf DOS IPXTM clients are timing out or losing connections when the servers switch over, increase the IPX retry count parameter in the NET.CFG file on clients using IPX. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"ipx retry count 40RENDERAS="SECT2"Logging in ARCnet or Token Ring Clients Immediately After a HaltSome clients on token-passing networks may have problems logging in after a server has been halted. Wait for the client to time out; then try to log in again.RENDERAS="SECT2"Responding to "LAN Driver Loopback Error Detected" MessagesThis message indicates that two or more ARCnet boards have the same node address. Reconfigure each board to a unique address.RENDERAS="SECT2"Turning Off the IPX Checksum Option for Token RingToken ring doesn't support the enabling of IPX checksums. If you are on a token ring network, change the value of the Enable IPX Checksums SET parameter in the MSEngine to 0 by typing the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Enable IPX Checksums = 0 MOREINFO="NONE"<MOREINFO="NONE"Enter>
PAGENUM=814 ID="BP763"RENDERAS="SECT1"IDXID="w9076"BOOK="_idx" COLLECTION="nw41" TIDREF="i4840"IDXID="w9077"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
Network PerformanceThis section discusses methods of optimizing network performance.RENDERAS="SECT2"Handling Frequent Ups and Downs of the IPX InternetThis situation indicates a faulty network connection or a problem with communication between the servers.Use SET to increase the IPX Internet Down Wait Time and the MSL Deadlock Detect Wait Time parameters by 0.5 second or more.FORMAT="LINESPECIFIC"MOREINFO="NONE"SET IPX Internet Down Wait Time = variable
SET MLS deadlock Wait Time = 
variableThe value of variable should be 0.5 second greater than the current value. If this solves the problem, put the SET commands in the IOSTART.NCF files. If it does not solve the problem, increase variable again.Also, check the network cabling attached to each server and the network connections (including routers and bridges) between the servers.Make sure the interrupt priority of the MSL board is higher than the interrupt priority of the network boards in each NetWare server.In most cases, this means setting the MSL interrupt to a lower number. (See the MSL board manufacturer's documentation for more information on setting interrupts.)Interrupt priorities from high to low are 0, 1, 2 or 9, A, B, C, D, E, F, 3, 4, 5, 6, 7, and 8. Interrupt 2 is the highest priority you can assign to an MSL board because interrupts 0 and 1 are reserved.PAGENUM=815 ID="BP764"RENDERAS="SECT2"Responding to "IPX Network No Longer Returning Status" MessagesThis message indicates a problem with a network connection: either a faulty network board in one of the servers, a cabling problem in the network, or an incorrectly bound network protocol.If this server is the primary server, and the system determines that the other server has more functional network boards, that server will become the primary.To determine if a server's network board has failed, type the CONFIG command at each server's IOEngine prompt.A "not sending" or "not receiving" message indicates a bad board or a faulty network connection.If this message frequently recurs with the message, "IPX Network is now returning status check packets," increase the IPX Internet Down Wait Time SET parameter to give the system a little more time before determining that a network board has failed. Use the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET IPX Internet Down Wait Time = variableRENDERAS="SECT2"Handling Primary Network Board FailureIf a network board in the IDXID="w9078"BOOK="_idx" COLLECTION="nw41" TIDREF="i3387"
primary server stops transmitting or receiving packets, the secondary server assumes the primary role only if the following conditions are true:MARK=BULLETThe secondary server's network boards are more functional than the primary's network boards.The servers are fully synchronized and their disks are completely mirrored.Three SET parameters in the IOEngine can help detect and prevent downtime caused by network board failure: Check LAN Option, Check LAN Extra Wait Time, and Use Diagnostic Responder to Validate LAN Functionality.RENDERAS="SECT3"SET Check LAN Option=2This setting (2 is the default) forces a server switchover by restarting the primary server if a network board fails in the primary.PAGENUM=816 ID="BP765"RENDERAS="SECT3"SET Check LAN Extra Wait Time=10This setting adds 10 extra seconds to the time the system waits before forcing a switchover because of a bad network board in the primary server.By default this setting is 0, but if you have a large network or heavy traffic on the network, you may want to increase the wait time to prevent a premature server switchover.RENDERAS="SECT3"SET Use Diagnostic Responder to Validate LAN Functionality=ONThis setting broadcasts an IPX diagnostic request to verify that a network board is functional.By default this setting is OFF because the diagnostic request adds traffic overhead and can hurt performance of large networks.However, if you want to know whether a network board is bad or just slow, set this parameter to ON.PAGENUM=817 ID="BP766"RENDERAS="SECT1"TroubleshootingThis section suggests solutions to various problems that can occur with NetWare 4.1 SFT III networks.RENDERAS="SECT2"Both Servers Are Primary; No Secondary Console DisplayIDXID="w9079"BOOK="_idx" COLLECTION="nw41" TIDREF="i3387"IDXID="w9080"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"ACTIVATE SERVER was executed from both IOEngines, and both servers have assumed the primary server role. Delete "ACTIVATE SERVER" from the IDXID="w9081"BOOK="_idx" COLLECTION="nw41" TIDREF="i82"
IOSTART.NCF file. Restart one server.Make sure the node addresses on the network boards are unique to each server.RENDERAS="SECT2"Disks Won't Mirror After Servers SynchronizeVerify that the correct disk driver is loaded in each server's IOEngine. Also, put the load command for the disk driver in each server's IOSTART.NCF file.Check the mirror status in the INSTALL.NLM for orphaned drives.RENDERAS="SECT2""Error IPX internet may be too slow" Message AppearsA busy IPX network or busy routers between SFT III servers can cause this message:FORMAT="LINESPECIFIC"MOREINFO="NONE"IPX internet may be too slow to notify secondary server if MSL fails... increase secondary take over delay amount.If "I'm alive" packets take too long to travel between the servers over IPX, the secondary server may prematurely take over for the primary server.To prevent this, use the SET command in the IOEngine to increase the Secondary Take Over Wait Time. Use the following syntax.FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Secondary Take Over Wait Time = variableAlso check for problems with network connection that may be slowing IPX.PAGENUM=818 ID="BP767"RENDERAS="SECT2""Error transferring IOEngine error log to MSEngine" Message AppearsVolume IDXID="w9082"BOOK="_idx" COLLECTION="nw41" TIDREF="i4394"IDXID="w9083"BOOK="_idx" COLLECTION="nw41" TIDREF="i4794"IDXID="w9084"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
SYS: may not have mounted. If the volume is mounted, check the file attributes of the IO$LOG.ERR file to verify the file isn't flagged as Read Only.If the problem persists, there may not be room for the file on volume SYS:. Delete or rename the IO$LOG.ERR file on the DOS partition.RENDERAS="SECT2""Inactive device associated with mirror partition" Message AppearsThis message is caused by one of the following situations:MARK=BULLETThe MSEngine was brought down, but only one server was brought back up.The disk driver on one server didn't load correctly.A hard disk or controller failed.Correct any hardware problems associated with the failure and bring both servers back up.RENDERAS="SECT2"IOEngine Network Number Prompt Appears After Executing IOSTART.NCFCheck both IOSTART.NCF files to make sure they assign unique internal network numbers to each IDXID="w9085"BOOK="_idx" COLLECTION="nw41" TIDREF="i1901"IDXID="w9086"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
IOEngine.Check the spelling and syntax of the IDXID="w9087"BOOK="_idx" COLLECTION="nw41" TIDREF="i1936"IDXID="w9088"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
IPX internal network number command. There should not be an equal sign (=) in the command.Make sure the IOSTART.NCF file is in the same directory as the MSERVER.EXE file on each server.RENDERAS="SECT2"Keyboard Is Slow or Frozen After Loading ARCnet on IRQ 2Make sure there are no I/O port or memory address conflicts.PAGENUM=819 ID="BP768"RENDERAS="SECT2"LOGIN Fails, Even If Correct Password Is GivenIf checksumming is disabled at the workstation, it must also be disabled at the server. Change the value of the Enable IPX Checksums SET parameter in the MSEngine to 0, using the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Enable IPX Checksums = 0This may also indicate a problem with the user's Directory context.RENDERAS="SECT2"LOGIN Fails for an NLM in the IOEngineThis happens only in the case of a backup NLM that logs in to the server using a different user name and would happen only on the secondary IOEngine. Type the following.FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Reply To Get Nearest Server = ON MOREINFO="NONE"<EnMOREINFO="NONE"ter>RENDERAS="SECT2"IDXID="w9089"BOOK="_idx" COLLECTION="nw41" TIDREF="i2543"IDXID="w9090"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
MSEngine Name Prompt Appears Even Though MSAUTO.NCF ExistsVolume SYS: did not mount, or the command was typed incorrectly in the MSAUTO.NCF file.There should not be an equal sign (=) in the MSEngine name command.Type in the MSEngine name and IPX internal network number. Edit the MSAUTO.NCF file if necessary.Make sure the disk drivers are loaded in both IOEngines. Mount volume SYS: from the command line or with INSTALL. If volume SYS: is unable to mount, run VREPAIR and try mounting it again.RENDERAS="SECT2"MSL Drivers Are Loaded But Servers Do Not SynchronizeYou might have installed the IDXID="w9091"BOOK="_idx" COLLECTION="nw41" TIDREF="i2547"IDXID="w9092"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
MSL boards incorrectly. Check the following on each server:MARK=BULLETInterrupt settings on the MSL boards (for conflicts with the network boards)MSL cables and board connectionsMSL drivers (both servers must have the same version of the driver)PAGENUM=820 ID="BP769"RENDERAS="SECT2"MSL Isn't ActivatedVerify that the same MSL driver is loaded on each server and that the MSL boards and cables are installed correctly.RENDERAS="SECT2"MSL Times Out When a Device Driver is LoadedLoad the device driver before loading the MSL driver, or use the SET utility in the IOEngine to increase the MSL Error Wait Time value. Use the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET MSL Error Wait Time = variableIf this solves the problem, put the SET command shown above in the IOSTART.NCF file, above the LOAD command for the MSL driver.RENDERAS="SECT2""Other Server Requested This Server to Halt" Message AppearsThe following sequence of events causes this message to appear:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The secondary server stops receiving "I'm alive" packets IDXID="w9093"BOOK="_idx" COLLECTION="nw41" TIDREF="i1994"IDXID="w9094"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
 from the primary server over the IPX network.The MSL between the two servers fails.The secondary server begins to take over as primary (because of no "I'm alive" packets).The secondary server then receives an "I'm alive" packet from the primary server.Because two primary servers can't coexist, the secondary server halts.Check for hardware problems on the IPX network and the MSL connection. If there are no hardware problems, use SET in the IOEngine to increase the Secondary Take Over Wait Time, using the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Secondary Take Over Wait Time = variable
PAGENUM=821 ID="BP770"RENDERAS="SECT2"IDXID="w9095"BOOK="_idx" COLLECTION="nw41" TIDREF="i3387"IDXID="w9096"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
Primary Server Doesn't Know IPX Route to Secondary ServerVerify thatMARK=BULLETBoth IOEngines are activeThe LAN drivers are loaded in both IOEnginesThe protocols are bound to the network boards in both serversUse SET to increase the IPX Internet Down Wait Time and the MSL Deadlock Detect Wait Time parameters, using the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET IPX Internet Down Wait Time = variable
SET MSL Deadlock Detect Wait Time = 
variableCheck the network cabling and the network boards and routers between the SFT III servers to verify they are functioning properly.RENDERAS="SECT2"Queue Overrun Abend OccursDecrease the number of seconds in the IPX Internet Down Wait Time and the MSL Deadlock Wait Time SET parameters in the IOEngine, using the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET IPX Internet Down Wait Time = variable
SET MSL Deadlock Detect Wait Time = 
variableRENDERAS="SECT2"Secondary Doesn't Switch Over When Primary LAN Driver Is UnloadedThe secondary server is designed to take over for the IDXID="w9097"BOOK="_idx" COLLECTION="nw41" TIDREF="i3387"
primary server if the secondary server detects a network board failure in the primary.However, an unloaded LAN driver is not considered a hardware failure, since it was explicitly requested by a user at the server console.Therefore, if a LAN driver in the primary server is unloaded, both the primary and the secondary server will report they aren't receiving "I'm alive" packets, but the secondary server will not switch over.When the LAN driver is reloaded, the primary server will continue to function as primary.PAGENUM=822 ID="BP771"Any activity in progress when the LAN driver is unloaded from the primary server will be suspended, and client connections will time out unless the driver is promptly reloaded.RENDERAS="SECT2"Server Failure OccursBecause the MSEngines on both IDXID="w9098"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"IDXID="w9099"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
SFT III servers are mirrored and the IOEngines are not, you can assume the following about most server failures:MARK=BULLETIf both servers fail or have an abend condition, the failure is probably related to software running in the MSEngine.If one server fails and the remaining server assumes the role of IDXID="w9100"BOOK="_idx" COLLECTION="nw41" TIDREF="i3387"
primary server, the failure is probably related to hardware, or to a driver or NLM loaded in the failed server's IOEngine.RENDERAS="SECT2"ID="FM83712"Servers Restart for No Apparent ReasonYou may have the wrong values for the recovery option SET parameters, or server IDXID="w9101"BOOK="_idx" COLLECTION="nw41" TIDREF="i4467"
test mode is causing constant switchovers. Check the IO$LOG.ERR and MSSTATUS.DMP files for the cause of the problem.Use these SET parameter values in both IOEngines to halt the server (without restarting it) so you can see the error:FORMAT="LINESPECIFIC"MOREINFO="NONE"Test Mode=0
Secondary Server MSL Send Blocked Recovery Option=0
Primary Server MSL Send Blocked Recovery Option=0
MSEngine Abend And Processor Exception Recovery Option=0
IOEngine Abend And Processor Exception Recovery Option=0
Machine Check Recovery Option=0
Memory Parity Error Recovery Option=0
Secondary Server MSL Hardware Failure Recovery Option=0
Primary Server MSL Hardware Failure Recovery Option=0
MSEngine Outputs Different Recovery Option=1
Secondary Server MSL Consistency Error Recovery Option=0
Primary Server MSL Consistency Error Recovery Option=0
PAGENUM=823 ID="BP772"Secondary Server MSL Deadlock Recovery Option=0
Primary Server MSL Deadlock Recovery Option=0RENDERAS="SECT2"SFT III Error Log FilesIDXID="w9102"BOOK="_idx" COLLECTION="nw41" TIDREF="i4118"When a failure occurs, SFT III updates three error log files in the SYS:SYSTEM directory:MARK=BULLETIO$LOG.ERR records the activity of both IOEngines.SYS$LOG.ERR records the IDXID="w9103"BOOK="_idx" COLLECTION="nw41" TIDREF="i2543"IDXID="w9104"BOOK="_idx" COLLECTION="nw41" TIDREF="i1340"
MSEngine activity.MSSTATUS.DMP records status dumps of engine states, synchronization and communications states, IOEngine to MSEngine requests, and other information following a failure or server switchover.Use these error log files to track the events that occurred prior to a failure or following a switchover.The IO$LOG.ERR file on the failed server is written to its DOS partition until the servers come back up. Then, the IO$LOG.ERR file from the DOS partition is appended to the IO$LOG.ERR file on volume SYS:.RENDERAS="SECT2""Should This Machine Become the Primary Server?" Message AppearsIDXID="w9105"BOOK="_idx" COLLECTION="nw41" TIDREF="i3387"The message above appears on the secondary server's console preceded byFORMAT="LINESPECIFIC"MOREINFO="NONE"All communication channels with the primary server have failed. Since the IPX network communication channel failed before the IDXID="w9106"BOOK="_idx" COLLECTION="nw41" TIDREF="i2472"
mirrored server link failed, the secondary is unable to determine if the primary server is still active.Verify that the primary server has failed, and then type "Y." If the primary server is still active, type "N."PAGENUM=824 ID="BP773"RENDERAS="SECT2"IDXID="w9107"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"IDXID="w9108"BOOK="_idx" COLLECTION="nw41" TIDREF="i4467"IDXID="w9109"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"
Test Mode Is No Longer WorkingYou can set the Test Mode parameter from the command line. For exampleFORMAT="LINESPECIFIC"MOREINFO="NONE"SET Test Mode = variableHowever, Test Mode resets to the default (no test) the first time that server is automatically downed and rebooted.To keep the server in test mode, put the SET command line shown above, using the appropriate parameter, in the IDXID="w9110"BOOK="_idx" COLLECTION="nw41" TIDREF="i1903"
IOSTART.NCF file of both SFT III servers.If your drives are not mirrored, the primary server will not initiate test mode. In this case use INSTALL to remirror the drives.RENDERAS="SECT2""Unknown Command" Message AppearsIDXID="w9111"BOOK="_idx" COLLECTION="nw41" TIDREF="i4660"IDXID="w9112"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"Use the MOREINFO="NONE"<Alt>+<Esc> keys to toggle to the other engine's console; then execute the command again.Use the LOAD command to execute modules (such as INSTALL and MONITOR).RENDERAS="SECT2""Unknown SET Parameter Name" Message AppearsUse the MOREINFO="NONE"<Alt>+<Esc> keys to toggle to the other engine's IDXID="w9113"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"
console; then retype the SET command.Check the spelling and syntax of the SET parameter and retype it correctly.PAGENUM=825 ID="BP774"RENDERAS="SECT2"ID="FM10709"Volume SYS: Does Not MountIDXID="w9114"BOOK="_idx" COLLECTION="nw41" TIDREF="i4394"IDXID="w9115"BOOK="_idx" COLLECTION="nw41" TIDREF="i4794"IDXID="w9116"BOOK="_idx" COLLECTION="nw41" TIDREF="i4583"Load VREPAIR. If VREPAIR does not load, halt the primary server by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"HALT MOREINFO="NONE"<Enter>Execute MSERVER with the -ns parameter. Then reload the disk driver and load VREPAIR.When VREPAIR is loaded, Option 2 must be set to "Write all directory and FAT entries out to disk" and Option 3 must be set to "Write changes immediately to disk."Make sure you are using the latest disk driver.RENDERAS="SECT2"Workstations Cannot Find or Attach to a ServerMake sure thatMARK=BULLETVolume SYS: is mountedThe appropriate network drivers are loaded on each SFT III serverNetWare Directory ServicesTM (DS.NLM) is loadedThe LAN protocols are bound to the network boardsThe workstation and server are using the same frame typeRENDERAS="SECT2"Workstations Time Out During Server ResynchronizationChange the IPX retry count in the NET.CFG file on the workstations to a higher value. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"ipx retry count 40Turn on the SET parameter Notify All Users Of Mirrored Server Synchronization in the MSEngine to broadcast a message to all users when synchronization occurs. Use the following syntax.FORMAT="LINESPECIFIC"MOREINFO="NONE"SET Notify All Users Of Mirrored Server Synchronization = <group name>